About Implementation Of Out Of The Box OCMC-BRM Integration (Doc ID 1580756.1)

Last updated on SEPTEMBER 08, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

The business offers 3 different services to their mobile subscribers: telephony, sms, and data.

With these 3 services, mobile subscribers can perform 6 different types of usage which have different rating rules:
1.  With the telephony service:
     - Voice calls rated on duration
     - Voice mail to text rated on occurrence
2.  With the sms service:
     - SMS rated on occurrence
3.  With the data service:
     - Data usage rated on volume
     - MMS rated on occurrence
     - Content purchase rated according to the content price

As rating is event driven in BRM, the usual way to rate these different usage types with different rating rules is to have a specific event type for each usage type. However, in the implementation of out of box OCMC-BRM integration, the OCMC always send "gsm" in the PIN_FLD_OBJ_TYPE field of the AAA requests to BRM whatever is the usage type. This means that on BRM any usage type would be rated using the "/event/session/telco/gsm" event type.

In this condition, the business cannot use the service to differentiate the usage types because several usage types share the same service.
How BRM is supposed to rate the different usage types differently since they all share the same "/event/session/telco/gsm" event type?
How an out of the box implementation of the OCMC-BRM integration is supposed to work to support such business?

 

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