Open APIs

Hi All, @Sylvie Demarest

Within the TMF677 Usage Consumption API v5, the UsageVolumeProduct entity has been introduced to align with SID v23+.

SID states that "A UsageVolumeProductSpec defines buckets of usage, such as 2 hours national calls. A UsageVolumeProductSpec requires one or many NetworkProductSpecs from which Usages will debit the bucket."

This aligns with the ODA use case 8 model for a postpaid mobile line, where both the recurring package and one-time package can provide multiple buckets of usage (allowances), e.g. for voice, sms and data.

However, the new Usage Consumption API has introduced a usageType field (voice, sms, data) within the UsageVolumeProduct entity and has referred to this entity as a single "bucket" as below.  This would mean that in order to support recurring packages, one-time packages, supporting multiple buckets (usage types) we would need to implement this as a bundle within ODA use case 8 instead.

Is the Usage Consumption API inconsistent with SID, or is this the original intent of the UsageVolumeProduct concept?

Thanks in advance!

Hi @Dan d'Albuquerque :it means the usage ind type is voice under the subtype (Voice Mo) or Voice MT, the specific calls like national, international and roaming will be fetched !!