Open APIs

 View Only
  • 1.  Multiple type mobile plans and product inventory

    Posted Jul 17, 2023 10:13

    Hi,

    we have multiple mobile plans like prepaid, postpaid and hybrid. One product specification is not suitable for all mobile plans. So we created prepaid mobile plan prod spec, hybrid prod spec and postpaid plan spec. Multiple prepaid plan offers are based on the prepaid prod spec. Multiple postpaid plan offers are based on the postpaid prod spec as well. Only one mobile plan can be active for msisdn. When one plan is being changed, we should inactive the current plan and activate new plan in product inventory. So, I don't know how we register the plans in the inventory. Because product instance has no category, we can't classify offers like mobile plan. Product offer relationship is one methods. But how should we set relationship between the mobile plans? Or should we create one general product instance that has multiple sub product instances express mobile plans? What

     should we design?



    ------------------------------
    Myagaa Nm
    MOBICOM CORPORATION LLC
    ------------------------------


  • 2.  RE: Multiple type mobile plans and product inventory

    Posted Jul 20, 2023 03:54

    Hi Myagaa

    The plans are Products in the inventory, instantiated from the corresponding ProductOffering. So ...

    • If customer moves between one plan and another of the same type (prepaid or postpaid), you would presumably preserve the Product that was instantiated from the ProductSpec, but make it a sub-Product of the new plan instance. Depending on the details of the offering (plan) you may or may not need to interact with the network and/or charging (e.g. allowance sizes might have changed so need to be re-provisioned). But the basics of the underlying service in the network presumably remain the same.
    • If you allow customer to move between plans of different types (e.g. from prepaid to postpaid), you will need to create new Products from both the plan (offering) and the spec. The underlying service may need to be re-provisioned (e.g. to add or remove policies monitoring usage limits), but you'll still want to keep other aspects of the underlying service (e.g. voice-mail box).

    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: Multiple type mobile plans and product inventory

    Posted Jul 20, 2023 09:25

    Hi Jonathan,

    You mean we should have one product spec for all type plans. Prepaid and postpaid offers should based on same product spec. Then we register producet spec as parent product. All offers based on that should be child products in product inventory. Is it right?



    ------------------------------
    Myagaa Nm
    MOBICOM CORPORATION LLC
    ------------------------------



  • 4.  RE: Multiple type mobile plans and product inventory

    Posted Jul 23, 2023 02:25

    You stated categorically that "One product specification is not suitable for all mobile plans".

    I don't have a strong opinion on whether you should have one product spec for all types of mobile plan, or a different spec for each type. You need to be aware of the implications, and it may depend on how your provisioning system behaves, and how you need to model the underlying network services.

    I was trying to point out the implications in my previous reply, e.g. the need to create new Product (because ProductSpec is different) while at the same time preserving underlying services and resources (where needed) for the customer.

    Good luck



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



  • 5.  RE: Multiple type mobile plans and product inventory

    Posted Jul 21, 2023 07:32

    Hi,

    it seems you describe a "change offer" scenario, when customer up/downgrade  from one active product (in product inventory) to another offer.
    productofferingrelationship could be used to define allowable change offer scenario (e.g. you can change from postpaid to prepaid but not from prepaid to postpaid) and you can use AllowedProductAction.
    change (upgrade or downgrade) offer is usually a much more complicated story and the information model (SID) offer no guidance on how to model it. I didn't found any very useful entities in the SID for that purpose.

    I think most modern BSS should have business capabilities to define "upgrade path". Each path should also specify what to do with:

    • termination fee, change offer fee
    • commitment period
    • identical products available in both offers
    • notice  and cooling off period
    • existing credit/payment plan
    • loyalty points
    • promotions
    • discounts
    • etc

    But how should we set relationship between the mobile plans? Or should we create one general product instance that has multiple sub product instances express mobile plans? 

    since you mention "sub-product", I assume "general product instance" is a bundle  that contains prepaid and postpaid offer defined as BundledProdOfferOption
    I don't recommend it.
    composite bundle is meant to sell products of different cateogories (TV + Internet) together, not to group or categorise similar products.



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Lyse Platform
    ------------------------------