Open APIs

 View Only
  • 1.  API for change MSISDN

    TM Forum Member
    Posted Oct 06, 2020 09:26
    Hi

    To implement Change MSISDN use case , which Open API we should use? Will it be PATCH /service/{id}. Can this call be directly made from CRM->Order Mgt.
    And Order Mgt will submit the request to Provisioning system, Billing and Charging system?


    ------------------------------
    Sarbari Saha
    Tech Mahindra Limited
    ------------------------------


  • 2.  RE: API for change MSISDN

    TM Forum Member
    Posted Oct 06, 2020 17:26
    It sounds more like TMF 640 patch request to the provisioning system.

    ------------------------------
    Varun Nair
    Telstra Corporation
    Note: This is an opinion based on my research and not an official TMF response.
    ------------------------------



  • 3.  RE: API for change MSISDN

    TM Forum Member
    Posted Oct 07, 2020 01:29
    Yes.

    Now, change MSISDN request may have payment to make. And this request will come from customer portal.
    Should it come as product order, where a price will be associated with simple product named change MSISDN , and a product order will be submitted.
    Then patch service request->patch resource request.

    ------------------------------
    Sarbari Saha
    Tech Mahindra Limited
    ------------------------------



  • 4.  RE: API for change MSISDN
    Best Answer

    TM Forum Member
    Posted Oct 07, 2020 03:14
    Hi

    I would deisgn it as a product order since it changes attributes of a customer's product (namely, the voice product).
    This information will typically be stored in CRM system, it may have impact on Billing, it will surely have impact on network provisioning etc. So it appears like a "normal" product change order (TMF622), not merely a service activation / configuration (TMF 640).

    BR THomas

    ------------------------------
    Thomas Dupré
    Deutsche Telekom AG
    ------------------------------



  • 5.  RE: API for change MSISDN

    TM Forum Member
    Posted Oct 07, 2020 08:10
    Typically such change where there is a commercial impact and also there is entitlements change, it needs to flow through a proper commercial order management. So whether is initiated from customer portal or commercial order manager,  a product order and subsequent service request (Patch on TMF 640) will be required.

    ------------------------------
    Varun Nair
    Telstra Corporation
    Note: This is an opinion based on my research and not an official TMF response.
    ------------------------------



  • 6.  RE: API for change MSISDN

    TM Forum Member
    Posted Oct 11, 2020 10:14
    Agreed with Varun and Thomas that TN change should start with product order. Apart from anything else the process needs to be managed with the customer, including interacting with the logical resource system (resource pool) to secure the proposed TN.
    After accept and submit of the product order, the internal implementation needs to decide how to implement the change in the network (whether by TMF640 or TMF641), and also to deal with the logical resource inventory.
    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.
    ------------------------------



  • 7.  RE: API for change MSISDN

    TM Forum Member
    Posted Jun 29, 2023 05:53

    If we want to add  MSISDN as part of order, should be use productInventory order or ServiceInventory Order.

    In case of Service Inventory and Resource Inventory what does the term Service.ID or Resource.ID refer?

    Can we have MSISDN or a DSL ID be tagged as Service.ID ?



    ------------------------------
    Ashish Sharma
    Bharti Airtel Ltd
    ------------------------------



  • 8.  RE: API for change MSISDN

    TM Forum Member
    Posted Jul 02, 2023 01:37

    Hi Ashish

    As I wrote in October 2020, you would always start with a Product Order. MSISDN assignment or change can be associated with charges (product price), e.g. for vanity number, which you would want to expose to the customer up-front before committing the order.

    Regarding the ID, the design guidelines (TMF630) are very clear - never use a business field as an ID. IDs are technical fields (such as database sequence, GUID, etc.) and are invariable. If you were to use an MSISDN or IP address as a key for service or resource, consider the chaos caused in entities that have references to the service or resource (foreign key) when the MSISDN or IP address changes.

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