Untitled :: OCS.io Documentation

In OCS.io, different Usage Types can be configured to handle the rating and charging of usage. Each Usage Type can have specific behavior concerning storing events, aggregation, duplicate checking, and more.

For example, you may have one Usage Type configured for rating and charging voice calls and another for rating and charging data usage. Each Usage Type can be configured with specific rules and behavior, such as storing the events for a certain amount of time, aggregating usage data over a specific period, or performing duplicate checking to prevent erroneous billing.

To configure Usage Types, follow these steps:

Access the Core Configuration perspective in the OCS.io user interface.
Select the Rating & Charging Usage Types.
On this screen, you can view the existing Usage Types, but you cannot add new ones or delete the current ones. The Usage Types are associated with products and configured during product configuration.
The following information is displayed for each Usage Type:

Item	Description
Name	Name of the Usage Type.
Description	Optionally, a description of the Usage Type.
Code	Code of the Usage Type. The code is entered during product configuration and cannot be changed on this screen. This code is used in the results of rating, charging, and billing.
Product	Product name to which the Usage Type belongs. The value cannot be entered on this screen.
Product Service	Product’s Service name to which the Usage Type belongs. The value cannot be entered on this screen.
UOM	Units of Measurement for the Usage Type.
Aggregation Level	Optionally, you can set how the Usage will be aggregated.
Chargeable Event Stored	Check this box if the Chargeable Event should be stored and may be printed on the Invoice.
Duplicity Checked	Check this box if the Duplicity should be checked for Usage based on Request ID coming in Charging Request.
Rejected Event Stored	Check this box if, in case the Event is rejected (e.g., Subscriber unknown), the Event should be stored and may be further investigated in the GUI.
Request Stored	Check this box if the Request should be stored and may be printed on the Invoice.
Rating Result Stored	Check this box if the Result of the Rating & Charging process should be stored.
Balances Responded	Check this box if the impacted Balances (Free units, Monetary balances, etc.) should be propagated to the Rating & Charging Response.
ECUR / SCUR Allowed	Check this box if the Usage is allowed to be charged in ECUR / SCUR model (Event/Session Charging with Unit Reservation).

Item

Description

Name

Name of the Usage Type.

Description

Optionally, a description of the Usage Type.

Code

Code of the Usage Type. The code is entered during product configuration and cannot be changed on this screen. This code is used in the results of rating, charging, and billing.

Product

Product name to which the Usage Type belongs. The value cannot be entered on this screen.

Product Service

Product’s Service name to which the Usage Type belongs. The value cannot be entered on this screen.

UOM

Units of Measurement for the Usage Type.

Aggregation Level

Optionally, you can set how the Usage will be aggregated.

Chargeable Event Stored

Check this box if the Chargeable Event should be stored and may be printed on the Invoice.

Duplicity Checked

Check this box if the Duplicity should be checked for Usage based on Request ID coming in Charging Request.

Rejected Event Stored

Check this box if, in case the Event is rejected (e.g., Subscriber unknown), the Event should be stored and may be further investigated in the GUI.

Request Stored

Check this box if the Request should be stored and may be printed on the Invoice.

Rating Result Stored

Check this box if the Result of the Rating & Charging process should be stored.

Balances Responded

Check this box if the impacted Balances (Free units, Monetary balances, etc.) should be propagated to the Rating & Charging Response.

ECUR / SCUR Allowed

Check this box if the Usage is allowed to be charged in ECUR / SCUR model (Event/Session Charging with Unit Reservation).

Please note that on this screen, you can only view and manage the existing Usage Types associated with products. The configuration of new Usage Types or deletion of current ones should be done during product configuration.