Real Time Rating Not Done According To Event START_T
(Doc ID 1340003.1)
Last updated on JUNE 29, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In a customer setup, based on the understanding about rating (using op_tcf_aaa_authorize ) as below :
1. If we don't pass START_T, pin_virtual_time(PVT) is taken into account for rating.
2. If we do send START_T, the value in the bracket is used for rating without considering the timezone.
one is sending START_T to op_tcf_aaa_authorize opcode, however the rating is not happening as per the value sent in the bracket. For example, sending START_T as 11:09 p.m., but it is taking BRM server PVT which is 00:19 a.m.
In the above case, the source (network element) of the event was set to UTC, and BRM was set to UTC+1. Now, when the event time stamp was received from network, it was in UTC, hence it was concluded that since one is passing this event time stamp as START_T in input, rating should happen as per UTC. However, it picked up UTC+1 which was set on BRM server.
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