Open APIs

Dear Members,

I have question regarding product inventory.

If we sell postpaid mobility,  we have  two entities postpaid mobility as connection line and plan (example 399 monthly).

Question is do we consider postpaid mobility connection as product offering along with plan or not? 

If yes please confirm below interpretation of product inventory model(s) is correct

MODEL A

[
   {
      "id": "PRODUCT_INVENTORY_POSTPAID_MOBILTY_1",
      "productOffering": {
         "id": "POSTPAID_MOBILTY"
      }
   },
   {
      "id": "PRODUCT_INVENTORY_POSTPAID_MOBILTY_PLAN_1",
      "productOffering": {
         "id": "POSTPAID_MOBILTY_PLAN"
      },
      "productRelationShip": [
         {
            "id": "PRODUCT_INVENTORY_POSTPAID_MOBILTY_1",
            "type": "reliesOn"
         }
      ]
   }
]

or 

Model B

 {
   "id": "PRODUCT_INVENTORY_POSTPAID_MOBILTY_1",
   "productOffering": {
      "id": "POSTPAID_MOBILTY"
   },
   "product": [
      {
         "id": "PRODUCT_INVENTORY_POSTPAID_MOBILTY_PLAN_1",
         "productOffering": {
            "id": "POSTPAID_MOBILTY_PLAN"
         }
      }
   ]
}

Making postpaid mobility as product inventory is correct approach?

As per IG1228 Use Case UC008 

We are creating product inventory in case if post paid connection but handling of plan/recharge is not mentioned. 

Would be great help if  similar user case of  purchasing new plan for postpaid mobile subscriber is available.

Or I say suggest best fit  inventory data model for mobility connection and mobility plan since both have its own life cycle.