Issues to be Aware of when Enabling Mid-Session Commits for Charging Control Services
(Doc ID 1308294.1)
Last updated on DECEMBER 03, 2019
Applies to:
Oracle Communications Network Charging and Control - Version 4.2.0 and laterInformation in this document applies to any platform.
Goal
We would like to enable mid-session commits on voice/data calls and use the real-time notifications to trigger actions while a call/session is in progress. Are there any issues with doing this?
Note:
Mid-session commits are a feature of the VWS/UBE machines and not relevant for customers with BRM or third-party billing solutions. Mid-session commits allows the billing engine to periodically commit the outstanding charge for a service before the call or data session has finished, thereby generating additional EDRs.
Real-time notifications are also a feature of the VWS/UBE machines that can be triggered while a session is in progress if used in conjunction with mid-session commits. They normally trigger when the final charge is committed, which is at the end of the session when mid-session commits are not in use.
As an example of using mid-session commits with real-time notifications, an "auto top-up" service could be set up for data calls that triggers a low-balance real-time notification when the customer's data balance falls below a threshold (when a mid-session commit occurs) and this notification is used to trigger a recharge of the data balance of the customer's account, possibly from their general cash and it could also charge them a small amount.
Mid-session commits are a feature of the VWS/UBE machines and not relevant for customers with BRM or third-party billing solutions. Mid-session commits allows the billing engine to periodically commit the outstanding charge for a service before the call or data session has finished, thereby generating additional EDRs.
Real-time notifications are also a feature of the VWS/UBE machines that can be triggered while a session is in progress if used in conjunction with mid-session commits. They normally trigger when the final charge is committed, which is at the end of the session when mid-session commits are not in use.
As an example of using mid-session commits with real-time notifications, an "auto top-up" service could be set up for data calls that triggers a low-balance real-time notification when the customer's data balance falls below a threshold (when a mid-session commit occurs) and this notification is used to trigger a recharge of the data balance of the customer's account, possibly from their general cash and it could also charge them a small amount.
Solution
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
| Goal |
| Solution |