UsedServiceUnit With ReportingReason=QUOTA_EXHAUSTED Handling

(Doc ID 2378925.1)

Last updated on APRIL 09, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.3.0 and later
Information in this document applies to any platform.

Goal

On : 11.3.0.3.0 version, Balance Management

In the below scenario,Why ECE interpreted ReportingReasons from CCR.MSCC Update-2 different than from Update-3?
First UsedServiceUnit.ReportingReason=QUOTA_EXHAUSTED(3) looks like it was omitted by ECE but second was treated as Final event it was QUOTA_EXHAUSTED?

Scenario:

Initial
rsu.cc-total-octets=0
gsu.cc-total-octets=0

Update-1
rsu.cc-total-octets=1049600
gsu.cc-total-octets=1049600
usu.cc-total-octets=787980

Still valid quota 1049600-787980=261620

Update-2
rsu.cc-total-octets=261620
usu.cc-total-octets=261620 and 3gpp-reporting-reason=3 (Quota Exhausted)
  UsedServiceUnit.TotalOctets=261620
  UsedServiceUnit.InputOctets=37666
  UsedServiceUnit.OutputOctets=223954
  UsedServiceUnit.ReportingReason=QUOTA_EXHAUSTED(3)
  ServiceId=12
  RatingGroup=100000]
gsu.cc-total-octets=261620

Still valid quota 261620+261620-261620=261620

Update-3
rsu.cc-total-octets=261620
usu.cc-total-octets=133258 and 3gpp-reporting-reason=3 (Quota Exhausted)
  UsedServiceUnit.TotalOctets=133258
  UsedServiceUnit.InputOctets=13952
  UsedServiceUnit.OutputOctets=119306
  UsedServiceUnit.ReportingReason=QUOTA_EXHAUSTED(3)
  ServiceId=12
  RatingGroup=100000
  ReportingReasons=[FINAL(2)]]
gsu.cc-total-octets=0

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms