Oracle Communications Policy Management
 

PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
 

In this Document

Goal

Solution

Created from <SR 3-11291331281>

Applies to:

Goal

POLICY 10.5.5 version, Wireless (Non-Production)

Revalidation timeout

The trace log`s CCA was seen after the device attached at the network. It looks like the Revalidation-Times configuration is different from what has been configured in the Dynamic quota`s expiration date and time. This document explains the reason for this mismatch.


 




 

Solution

Step by step answer, including full documentation titles or abstracts of any notes referenced.


I understand that you want to apply rule 1 during timframe1 (TOD1) and rule 2 during time-frame 2(TOD2). Also the end of time-frame 1 is the start of time-frame 2 along with the subscriber quota reset time.

First we will explain the mechanism with which ToD works in this scenario. Re-validation time in CCA is always will be subscriber quota reset time(upto + 45 mins- staggering) , however if ToD is configured, then whenever new ToD time-frame triggers - in this case like at 00:00 hrs, MPE internally generates the RAR and throws that RAR via the policy engine. Your policy should have the conditions to be evaluated under re-auth, and if the condition is there, then MPE will trigger that policy and will install new rule by sending RAR at that exact time when the time-frame starts( which is 00:00). It does not matter what time the subscriber quota is going to reset, as that will be staggered up to 45 mins (by default).

I tested the scenario in 10.5.5 in lab and confirmed there is a bug in the code wherein when the ToD triggers ( in your case at 00:00 hrs), MPE internally generate RAR but policies still fail in evaluating the condition of re-auth. The issue looks to be fixed in 11.5.x however I have still filed the bug to be 100% sure. I ran the test on 11.5.x system few times and it worked. Please upgrade to 11.5 in lab - so that you can test this with customer policies.

This solution has no attachment