TM Forum Community

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Got you. 

OK, so looking at the API and the use case part I see that a channel can be set for a top up "Operators can provide multiple recharge channels to top up these buckets to increase the balance to use for services."

Looking at the Top Up Schema there is a 0..1 relationship to ChannelRef and that is used as a resource reference to the channel. Have a look at it as ,if I understand it correctly, you would be able to use it to define different types of channels as per your examples above. <o:p></o:p>

ChannelRef relationship<o:p></o:p>

The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..<o:p></o:p>

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Hi  Elisabeth,

Thanks  a log for suggesting ChannelRef relationship. with detail explanation. 

May we know which schema object suitable, if we will get these additional attributed other than channel reference, like legacy system demographics attributes ?

Here we also need to take care that all the  attributes should be under single schema object.

Got you. 

OK, so looking at the API and the use case part I see that a channel can be set for a top up "Operators can provide multiple recharge channels to top up these buckets to increase the balance to use for services."

Looking at the Top Up Schema there is a 0..1 relationship to ChannelRef and that is used as a resource reference to the channel. Have a look at it as ,if I understand it correctly, you would be able to use it to define different types of channels as per your examples above. <o:p></o:p>

ChannelRef relationship<o:p></o:p>

The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..<o:p></o:p>

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Hi Chetan, 

I am not sure that I understand exactly, but I assume that what you are looking for is the definition of channels and then associated payment methods with the logistics to execute on the refill? I looked on the API table and you have the Payment Method API TMF670 and of course the Payment API TMF676. 

Hi  Elisabeth,

Thanks  a log for suggesting ChannelRef relationship. with detail explanation. 

May we know which schema object suitable, if we will get these additional attributed other than channel reference, like legacy system demographics attributes ?

Here we also need to take care that all the  attributes should be under single schema object.

Got you. 

OK, so looking at the API and the use case part I see that a channel can be set for a top up "Operators can provide multiple recharge channels to top up these buckets to increase the balance to use for services."

Looking at the Top Up Schema there is a 0..1 relationship to ChannelRef and that is used as a resource reference to the channel. Have a look at it as ,if I understand it correctly, you would be able to use it to define different types of channels as per your examples above. <o:p></o:p>

ChannelRef relationship<o:p></o:p>

The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..<o:p></o:p>

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Hi Elisebeth,

Thanks a lot for your time & explanation.

Let me brief about my requirement.

Here we are going for TMF compliance conversation of existing solution. We need to prepare one TMF comply API layer that will communicate southbound APIGateway/Middleware layer and further it will call existing legacy billing/charging/CRM system.

So my TMF API layer will trigger single API of APIGateway/Middleware layer while it will be distributed in multiple API call behind the middleware.

PFB sample required object that we need to incorporate in TMF compliance for TMF654 Topupbalance

Hi Chetan, 

I am not sure that I understand exactly, but I assume that what you are looking for is the definition of channels and then associated payment methods with the logistics to execute on the refill? I looked on the API table and you have the Payment Method API TMF670 and of course the Payment API TMF676. 

Hi  Elisabeth,

Thanks  a log for suggesting ChannelRef relationship. with detail explanation. 

May we know which schema object suitable, if we will get these additional attributed other than channel reference, like legacy system demographics attributes ?

Here we also need to take care that all the  attributes should be under single schema object.

Got you. 

OK, so looking at the API and the use case part I see that a channel can be set for a top up "Operators can provide multiple recharge channels to top up these buckets to increase the balance to use for services."

Looking at the Top Up Schema there is a 0..1 relationship to ChannelRef and that is used as a resource reference to the channel. Have a look at it as ,if I understand it correctly, you would be able to use it to define different types of channels as per your examples above. <o:p></o:p>

ChannelRef relationship<o:p></o:p>

The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..<o:p></o:p>

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object

Look at the user guide for adjustment and transfer. What you will see in the datamodel is that there are different ways of relating to the action through relatedParty and you also have the owning Party as well as a logical reference that often is the identifier (MSISDN/IMSI or such) 

Hi Elisebeth,

Thanks a lot for your time & explanation.

Let me brief about my requirement.

Here we are going for TMF compliance conversation of existing solution. We need to prepare one TMF comply API layer that will communicate southbound APIGateway/Middleware layer and further it will call existing legacy billing/charging/CRM system.

So my TMF API layer will trigger single API of APIGateway/Middleware layer while it will be distributed in multiple API call behind the middleware.

PFB sample required object that we need to incorporate in TMF compliance for TMF654 Topupbalance

Hi Chetan, 

I am not sure that I understand exactly, but I assume that what you are looking for is the definition of channels and then associated payment methods with the logistics to execute on the refill? I looked on the API table and you have the Payment Method API TMF670 and of course the Payment API TMF676. 

Hi  Elisabeth,

Thanks  a log for suggesting ChannelRef relationship. with detail explanation. 

May we know which schema object suitable, if we will get these additional attributed other than channel reference, like legacy system demographics attributes ?

Here we also need to take care that all the  attributes should be under single schema object.

Got you. 

OK, so looking at the API and the use case part I see that a channel can be set for a top up "Operators can provide multiple recharge channels to top up these buckets to increase the balance to use for services."

Looking at the Top Up Schema there is a 0..1 relationship to ChannelRef and that is used as a resource reference to the channel. Have a look at it as ,if I understand it correctly, you would be able to use it to define different types of channels as per your examples above. <o:p></o:p>

ChannelRef relationship<o:p></o:p>

The channel to which the resource reference to. e.g. channel for selling product offerings, channel for opening a trouble ticket etc..<o:p></o:p>

Hi Elisabeth,

It will be single top-up balance either min or data or SMS but here they are expecting supporting attributes to this top-up. For example Recharge through External Party, Recharge against Loan, Recharge Against Credit/Debit Transfer, and few futuristic expected attributes. 

Hi Chetan, 

Are you talking about a composite top up - aka a top up that is composed of multiple balances? For example 100min, 1GBData, 1000 SMS

/Elisabeth

Hi All,

We need to manage additional attributes with balance refill regular information. As per our understanding, we are looking below options. Please suggest which one will be appropriate for us.

Additional attributes like : AddData1, AddData2, AddInt1,AddInt2 etc

Option 1 : Use existing "product" schema object and define attribute name-value pairs in List[ProductRef]

Option 2: Extend topupBalance operation with "characteristic" schema object