Hello TMForum,
I'm working on an API layer that would be first useful from customer self care perspective.
In order to retrieve customer products, e.g: Internet Subscription product, and Digital TV subscription product, I'd use TMF637:
GET / product?billingAccount.id=123
to receive something like this:
[{ "id": "456",
"billingAccount": { "id": "123"},
"isCustomerVisible":true,
"productSpecification": {"id": "TV product 1"}
},
{ "id": "789",
"billingAccount": {"id": "123"},
"isCustomerVisible":true,
"productSpecification": {"id": "Internet product 1"}
},
...]
For retreiving customer premises equipment I was thinking about TMF639, but I'm not sure how to include relation of equipment to product, e.g.: Internet product requires a Home Gateway, Digital TV product requires a SetTopBox.
One option (
option a) that I see is to use relationship of product to list of realizingResource, so this part of product object from TMF637 19.0 Swagger:
"realizingResource": {
"type": "array",
"items": {"$ref": "#/definitions/ResourceRef"} },
But when looking at TMF637 definition I do not see reference from PhysicalResource to Product.
On the other hand it seems that the way to do it (
option b) would be to navigate though a hierarachy (like in the Order Management concept):
Product -> Realizing Service (CFS) -> Realizing Service (RFS) -> Physical Resource
Should I assume that navigation directly from Product->Realizing resource is for material products (like "I Phone X - 128 GB, color white") and the option b, navigation through CFS and RFS is for subscription prodcuts?
I'd like also to query PhysicalResources by BillingAccount, but I do not see such option - there is link to relatedParty.
Is it planned to add billingAccount to Resource/PhysicalResource?
Cheers,
Bartosz
------------------------------
Bartosz Kluzek
UPC Poland
Liberty Global Services B.V.
------------------------------