Last updated on JULY 25, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On BRM 7.5,
1. On Oct 15th 2014 at 23:56:06, the subscriber starts a data session triggering a call to the PCM_OP_TCF_AAA_AUTHORIZE opcode
2. On Oct 16th 2014 at 00:54:56, the network triggers a call to the PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE opcode because the quota granted during authorization has been consumed.
3. On Oct 16th 2014 at 00:55:00, the subscriber ends the data session triggering a call to the PCM_OP_TCF_AAA_STOP_ACCOUNTING opcode.
At step 1, the active session has been created in BRM with a start time on Oct 15th 2014 at 23:56:06 which is expected.
At step 2, the start time of the active session has been modified to Oct 16th 2014 at 00:54:56.
Start time of the active session is expected to not be modified after the active session created by the PCM_OP_TCF_AUTHORIZE opcode.
At step 3, the data usage event has been created with a start time on Oct 16th 2014 at 00:54:56 which corresponded to the start time of the active session that has been modified at step 2. This is incorrect as the data usage was actually started on Oct 15th 2014 at 23:56:06.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms