Thanks for the quick response as usual, Jonathan. Yes, I already had a look through IG1228 to help me come up with this model I've provided.
And I agree & understand TMF 622 is only to do with product ordering at runtime and hence in my diagram, it is provided separately on the LHS separate from the catalog.
Original Message:
Sent: Jul 13, 2023 14:11
From: Jonathan Goldberg
Subject: Modelling a use case for a Mobile Offer using TMF 620 and TMF 622
Hi Remya
There are many ways to structure specifications, offerings, and prices, depending on best business practice and the requirements of the specific telco. TMF ODA use cases can give you some guidance, search for the most up-to-date IG1228, where use case UC008 gives catalog models (product, service, resource) for mobile 4G and 5G. Other use cases e.g. UC003 give models for different lines of business. These might assist you in structuring your model proposal.
P.S. The modeling that you have described uses purely TMF620 Product Catalog at design time. It has nothing to do with TMF622 Product Order. Product Order becomes relevant at runtime when customers start ordering the offerings exposed in the catalog.
------------------------------
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.
Original Message:
Sent: Jul 12, 2023 19:56
From: Remya Rajesh
Subject: Modelling a use case for a Mobile Offer using TMF 620 and TMF 622
Hello TMFORUM community,
I am posting this message to validate the usage of TMF 620 and TMF 622 in this use case.
The use case I am about to go through in detail below is how to make a particular offer available via a variety of options:
Use case: "If we want to sell customers mobile offers for example let's say someone wants to buy an offer with 10 GB & 100 minutes of monthly recurring entitlements and some money (50 USD) which he/she can use based on some usage rules (eg: a dollar per GB of usage) "
Please have a look through and let me know if this seems like a valid configuration and use of the TMF APIs. Or if there are any other suggestions to comply to TMF for this use case.
-----------------------------------
From reading TMF620 and TMF622, the basic structure that I've come up with is:
SECTION 1 - Product and Service Specifications:
1. Create a data monthly recurring product specification with product characteristics "recurring" and "expiry" as monthly and "unit of measure" as GB and "eligibility" as data and define "allocation" as a characteristic without providing a value.
2. Create a data usage POP (Product Offering Price) entity with data usage PLAs in this case, a dollar per 2 GB of usage. But there can be multiple PLAs.
3. Create a voice monthly recurring product specification with product characteristics "recurring" and "expiry" as monthly and "unit of measure" as minutes and "eligibility" as voice and define "allocation" as a characteristic without providing a value.
4. Create a voice usage POP entity with voice usage PLAs in this case, maybe a dollar per 5 minutes of usage. Again, there can be multiple PLAs associated to the POP.
5. Create a one off product specification with with product characteristics "unit of measure" as currency, and eligibility as voice, data or SMS. Add characteristics called allocation and currency with no value specified.
6. Create a connectivity product specification with the service specification and characteristics of MSISDN, IMSI, etc and provide no values for the characteristics.
7. Create an SMS POP too since the money can be used for SMS too.
SECTION 2 - Pricing Plans made available for selection in the top level offer.
1. Create a product offer with the Connectivity pricing plan referring to the connectivity product specification (setting min cardinality allowed to 1)
2. Create 3 product offers for the data plans with say, (setting max cardinality allowed to 1)
a) 10 GB per month plan (setting the product characteristic of allocation in the offer to 10GB)
b) 20 GB per month plan (setting to 20 GB)
c) 30 GB per month plan (setting to 30 GB)
3. Create 2 product offers for the voice plans with say, (setting max cardinality allowed to 1)
a) 100 minutes per month plan (setting the product characteristic of allocation in the offer to 100 mins)
b) 200 minutes per month plan (setting to 200 mins)
4. Create a product offer for the one off product specification with allocation as 50 and currency as USD. (setting min cardinality allowed to 1)
SECTION 3 - Product (Provides all available options with a default)
1. Create a bundled product offer for data with the 3 product offers for data specified above. (Data Product) . Include the Data POP in this offering
2. Create a bundled product offer voice with the 2 voice offers specified above. (Voice Product) . Include the Voice POP in this offering.
3. Create a bundled product offer with Connectivity Pricing Plan (Connectivity Product).
4. Create a bundled product offer with the money. Include Voice, Data and SMS POPs here. (Currency Product)
SECTION 4 - Actual offer (used as the top level offer in the product order)
1. Create a "Mobile Offer" which will include all the products above, making the offerings available in section 2 when sold.
SECTION 5 - Creating a product order for a related party with product order items.
Item 100 : Top level offer selected will be "Mobile Offer" bundles Items 101, 102, 103, 104
Item 101: Connectivity Pricing Plan - MSISDN: 0237823783
Item 102: 10 GB per month Data Pricing Plan - relies on Item 101
Item 103: 100 min per month Voice Pricing Plan - relies on Item 101
Item 104: 50 USD one off currency - relies on Item 101.
Another pictorial illustration is also in the attachment
------------------------------
Remya
------------------------------