AAA Reservation Logic Is Incorrect (Doc ID 786688.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 19-Jan-2012


Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.3.1.0.0 version, the Current AAA reservation logic is incorrect as per 3GPP standards.

The current reservation logic creates a reservation object with quantity specified in Authorize opcode (pcm_op_tcf_aaa_authorize).

Consider an example where 50 sec is reserved as requested in initial request. After that the Network says that the used quantity is 30 and requested (re-authorization) quantity is 50. Now BRM reserves total 100 sec quantity. BRM does not release 20 sec quantity from reservation. As per 3GPP standards, in re-authorization, BRM should release 20 sec (in this example ) from reservation and maintain 80 sec (after reauthorization)

Steps to Reproduce:

1) Create a customer with balance 1 $ (100 seconds).
2) Authorize amount 50 seconds ( 0.5 $ ) by using pcm_op_tcf_aaa_authorize.
3) check the reservation object created for this authorization , it must have 50 seconds.
4) Update and reauthorize amount with used=30 seconds, requested = 50 seconds.
    (pcm_op_tcf_aaa_update_and_reauthorize).

Current Behavior : After calling opcode update&reauthorize, reservation quantity is 100 sec. Unused 20 seconds not released from reservation.

Expected Behavior : Before re-authorization, the remaining unused quantity 20 seconds should release from reservation.

Cause

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