Script to Report OCNCC Traffic Rate Statistics as Transaction Units Per Second (TUPS)
(Doc ID 1905433.1)
Last updated on AUGUST 20, 2019
Applies to:Oracle Communications Network Charging and Control
Information in this document applies to any platform.
For Oracle Communications Network Charging and Control (OCNCC or NCC for short) a Transaction Unit (TU) consists of one request and one or more related responses from a licensed Application, as evidenced by the statistics generated by NCC components. This may include call, message, data session, voucher redemption, and charging attempts - depending on the NCC implementation. A request unit may originate from an application program and the corresponding response may originate from the network, or alternatively, the request unit may originate from the network and the corresponding response may originate from an NCC application.
This information is useful for Operators in a number of ways:
- Licensing based on traffic volumes, the main ones being Call Attempts Per Second (CAPS), Short Message Attempts Per Second (SMAPS), and Data Attempts Per Second (DAPS)
- Traffic volume/rate trends
- Capacity planning
- Fault analysis (traffic spikes or unusual patterns)
The following article details a statistic reporting script that queries the SMF_STATISTICS table and calculates traffic rates as Transaction Units Per Second (TUPS).
There are a large number of statistics gathered by the NCC applications. The purpose of this article is not to document them. For information on individual statistics and their meaning refer to the application's documentation.
In regards to NCC statistics and its configuration and storage refer to the following documentation:
- OCNCC Service Management System User's Guide
- OCNCC Service Management System Technical Guide
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