Spending-Status-Notification-Request Not Getting Generated After Policy Counter Tier Breach

(Doc ID 2399351.1)

Last updated on MAY 28, 2018

Applies to:

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

Symptoms

On Oracle Communications Elastic Charging Engine(ECE), 11.3.0.4.0 version, External notification (JMS)

Actual Behavior:

The Spending-Status-Notification-Request(SNR) is not getting generated after policy counter tier is breached.

Issue is that even though having active Spending-Limit-Request(SLR) and the policy counter tier has breached in the Update request, SNR is not getting generated.

Expected Behavior:

SNR has to be generated from ECE and sent back to the Policy and Charging Rules Function(PCRF) Node with the Policy counter status.

Steps to Reproduce the issue:

BRM Changes
1.A policy counter "Data_Global_Usage" with a single tier starting from -4666666666664 to 0 has to be created in BRM and synced through the IFW_SYNC.
2.A provisioning tag is associated and loaded into the BRM and synced using the syncPDC process.
3.Create a product and associated to the provisioning tag and sync the product to BRM as well as ECE.
3.Create a customer with the product

ECE Changes
1.Enable spendingLimitNotificationMode="ASYNCHRONOUS"

Process the SY,GY Request
1.Initiate the SLR
2.Initiate the CCR-I/U/T request
3.Send the request with Used units of 1048576


Changes

 

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