Open APIs

Expand all | Collapse all

TMF679 - How to specify consequences for a POQItem

  • 1.  TMF679 - How to specify consequences for a POQItem

    TM Forum Member
    Posted 21 days ago

    Hi All,

    we are using the TMF679 Product Offering Qualification API to qualify offerings for our e-shops. We are now working on providing the possibility to qualify broadband offerings. One of the things we need the POQ API to include in its qualification is the consequences of the given choice. For example, if a customer chooses to switch 50 Mbps for a faster 300 Mbps connection, but the modem in place does not support chosen speed. We would like to pass the information to the customer in for of a simple message. There is nothing the customer can do about it, but we want him to know that he will have to wait for the new modem.

    We were thinking that we could pass this info in the Note entity. But it does not seem like the right place for it. Is there an entity or way in the TMF679 that we could use?

    Thank you and best regards

    Vojtech Pustowka
    Telia Company



    ------------------------------
    Vojtech Pustowka
    Telia Company
    ------------------------------


  • 2.  RE: TMF679 - How to specify consequences for a POQItem

    TM Forum Member
    Posted 18 days ago
    Hello Vojtech

    Probably because it is technical eligibility, serviceQualification should be use instead of POQ.... but anyway the structure is close and we'll face same issue.

    Are you leveraging multi item &relationship in your request? I mean if you ask for a 300 MBps connection product (or service if you use SQ) in one item (action add), another item with the modem (action noChange)  with a relationship to this modem item to the connection  then I assume in the response you could have a qualified result for the connection (Yes this speed is available a this place) and an unqualified/alternate for the moden (No this moden cannot be use for this speed but this other one could be). You have the unavailaibilityReason in the modem item to explain the issue.

    for you info we'll align the POQ API structure to the SQ one in future by splitting in 2 resources: check and query. It will not change a lot the API but make distinction between precise request vs loose one.

    Hope it help

    Ludovic

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



  • 3.  RE: TMF679 - How to specify consequences for a POQItem

    TM Forum Member
    Posted 10 days ago

    Hi Ludovic and thank you kindly for your answer,

    the way you propose to handle this by using the eligibility unavailability reasons is the way we handle similar cases and it makes sense. But in this particular case, the consumer asks us to NOT make the offerings unavailable, but just to mark that there are certain consequences for the choice/change. We want the customer to be able to buy it nevertheless the consequences. We also cannot just get this from Service Qualification, because these consequences are base on rules stored in the POQ at the time.

    Do you think it is a good idea to create a new field in the POQ item (like the notes) to add these consequences?

    Thanks again

    Vojtech



    ------------------------------
    Vojtech Pustowka
    Telia Company
    ------------------------------