My Oracle Support Banner

DSG Scenario SNR Got Triggered Before Complete Data is Consumed (Doc ID 2961037.1)

Last updated on JULY 25, 2023

Applies to:

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

Symptoms

In the Discount Sharing Group (DSG) scenario (parent and 2 members), while starting usage in parallel sessions with few data available in pool (active reservation) for the customer, the policy got changed to OutAllowance. Because of this behavior, the customer is left with data, but not able to consume them.

Scenario:

1. Create primary account with base, roaming and RCC bundle
2. Created 2 member account with dummy, roaming and RCC bundle
3. Created DSG with primary and 2 member accounts
4. With 50Mb left in my allowance started parallel session on all 3 accounts
5. Received GSU of 10MB on parent (GPRS_1685620430)
6. Received GSU of 10MB on member1 (GPRS_1685620470)
7. Received GSU of 10MB on meber2 (GPRS_1685620508)
8. Consumed 10MB from member2 and received GSU of 10MB
9. Consumed 10MB again from member2 and received GSU of 10MB ---> policy reservation started with session ID GPRS_1685620508
10. Consumed 10MB from member1 (policy dnt change)
11. Consumed 10MB from member1 and policy changed now with 10MB available on parent (active reservation)

Actual Behavior:
SNR received for parent, member1 and member2 with 10MB available in the pool (active reservation).

Expected behavior:
SNR to be triggered for parent, member1, member2 after the complete data is consumed.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.