ESMPP Always Expects PPS_CHARGE_NOTIFY (Doc ID 2273861.1)

Last updated on JUNE 09, 2017

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 to 6.0.1 [Release 6.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Convergent Charging Controller (OC3C), the optional component Enhanced Short Message Fee Deduction (ESMPP) component is available as an interface to Short Message Fee Deduction (SMPP+) protocol compliant Short Message Service Centers (SMSCs).

ESMPP acts as a gateway between SMPP+ and the internal Intelligent Network Application Part (INAP) protocol used by Advanced Control Services (ACS) when triggering service logic configured in Control Plans (CPs).

In SMPP+, there are four message types:

In theory, the first two messages are sufficient for the successful charging of an SMS (assuming the delivery of the SMS was successful).

ESMPP assumes all four messages are necessary and will therefore either:

Whether a PPS_CHARGE_NOTIFY will be sent by the SMSC depends on the notify_mode value in the PPS_USER_CHECK_RESP from the SLC.  The possible values are:

ESMPP should use this value to determine whether to:

This will prevent excessive resource usage as resources are released as soon as they are no longer necessary and allow for the possibility of a successful refund.

Changes

 

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