Subscribing to Fixed Date PCs on the Reference Date Extends the PC by the Periodicity Irrespective of chargeTimeGMTHours Parameter (Doc ID 1406334.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 2.4.0 and later
Information in this document applies to any platform.

Symptoms

One could want to have a Periodic Charge (PC) occurring every Month at midnight on a fixed date in the country in which the Mobile Network Operator is.

All the Network Charging and Control servers and applications have been designed considering that the Server's Operating System is running in GMT time.

The parameter chargeTimeGMTHourschargeTimeGMTHours can be defined in the eserv.config configuration file to give a certain offset to the actual charge time at which the charging of the periodic charge will occur.

The eserv.config configuration file is usually located at /IN/service_packages/eserv.config

 

For further details about the chargeTimeGMTHourschargeTimeGMTHours parameter, refer to the Network Charging and Control (NCC) Charging Control Services (CCS) technical guide. A link to a document describing how to download the Network Charging and Control documentation is available in this document's references.


However, anyone using the chargeTimeGMTHourschargeTimeGMTHours parameter must do so with caution.

The chargeTimeGMTHours is used for calculation of the charging time, but it is not taken into consideration for calculation of the first occurrence of the charge.

If there is a fixed Periodic Charge on a given date (say the 14th day of each Month) and an offset for the charge (say 12 hours) set up with the chargeTimeGMTHourschargeTimeGMTHours parameter, the first_charge date of the periodic charge will be on the next month, even if the subscriber subscribes in the time lapse between 0:00 and the chargeTimeGMTHourschargeTimeGMTHours offset (between 0:00 and 12:00 in our example).

Sample behavior for the following scenario:

Changes

Introduction of the chargeTimeGMTHours parameter in the eserv.config configuration file on the Vouchers and Wallet Servers.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms