My Oracle Support Banner

Release Of Oracle Communications BRM Elastic Charging Engine (ECE) Version 11.3 Patch Set 8 (Doc ID 2422625.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version to [Release 11.3.0]
Information in this document applies to any platform.


Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) 11.3 Patch Set 8 ( is released on 13 July 2018.

This announcement lists the enhancements and fixes delivered in Elastic Charging Engine 11.3 Patch Set 8.

Patch ID: <Patch 28133198>

Important Note:

Ensure that you do the following if you are performing a rolling upgrade through ECE 11.3 Patch Set 7 to ECE 11.3 Patch Set 8. It is important this is done before you perform the rolling upgrade for ECE 11.3 Patch Set 7:

  1. Install ECE 11.3 Patch Set 7.
  2. Install the ECE 11.3 Patch Set 7 interim patch 27976672 (IP2) <Patch 27976672>.
  3. Install ECE 11.3 Patch Set 8.
  4. Delete the Coherence libraries in the ECE_11.3_PS7_IP2_home/oceceserver/lib directory.
  5. Copy the Coherence libraries manually from the ECE_11.3_PS8_home/oceceserver/lib directory to the ECE_11.3_PS7_IP2_home/oceceserver/lib directory.
  6. Perform the rolling upgrade for ECE 11.3 Patch Set 7 IP2.
  7. Perform the rolling upgrade for ECE 11.3 Patch Set 8.

Failure to apply the ECE 11.3 Patch Set 7 IP2 and update the coherence libraries before upgrading to Patch Set 7 will mean that a Rolling Upgrade to Patch Set 8 will not be possible, and it will be required to do an offline upgrade with an ECE cluster restart



When upgrading you must ensure that you install the following in the following order:

  1. The ECE Patch Set.
  2. A compatible version of BRM(Oracle Communications Billing and Revenue Management). See the corresponding BRM Installation Guide for installing BRM.
  3. A compatible version of PDC(Oracle Communications Pricing Design Center). See PDC Installation and System Administration Guide for installing PDC.
See "ECE System Requirements" in ECE Documentation for the compatible version of BRM and PDC.

Key Enhancements

The following are some of the significant enhancements delivered into ECE 11.3 Patch Set 8.

Group Notifications to Subscribers: In previous releases, ECE was sending the credit limit and threshold breach notifications only to individual subscribers. For example, in case of sharing groups, when a credit threshold was breached, ECE sent the threshold breach notification only to the individual subscriber associated with the breach and not to all members in that sharing group. With this enhancement, you can enable ECE to send group notifications for Threshold Breach Notifications, Credit Ceiling Breach Notifications and Credit Floor Breach Notifications. Group Notifications are configurable allowing the group members can either opt-in or opt-out.

SCTP Attributes Configuration in Diameter Gateway: In previous releases, to use Stream Control Transmission Protocol (SCTP) for network communication, you had to configure SCTP at the operating system (OS) level. With this patch release, ECE now contains the attributes for configuring SCTP. You can configure SCTP when you configure the Diameter Gateway nodes in ECE. 

Incremental and Cumulative Accounting in Diameter Gateway: In previous releases, Diameter Gateway was supporting only the incremental-based accounting. ECE now supports both incremental-based and cumulative-based accounting when processing usage requests.

Purging of Inactive and Dormant Accounts from the ECE Cache: In previous releases, deleting a customer account (including prepaid calling cards) in BRM was not purging the account from the ECE cache. The deleted account still remained in the ECE cache affecting the memory usage. To optimize and efficiently manage the memory, ECE now allows you to purge inactive and dormant accounts from the ECE cache. You can purge the accounts synchronously from both BRM and ECE in real time.
Adding and Deleting Rating Periods in Post-Rating Extension: You can now implement a custom logic to add or delete rating periods after rating by using the post-rating extension. For more information on using the post-rating extension, see ECE Extensions.

For more information please see the Elastic Charging Engine documentation.


Summary of Customer Issues Fixed in ECE 11.3 Patch Set 8


Customer Issues Fixed in ECE

SR Number

Bug Number

Issues Fixed



In a high-availability (HA) system, after performing the rolling upgrade, the HA status was not properly reset to NODE-SAFE.



Discounts were not evaluated based on the start time of a session.



The timeout exception in EM Gateway was causing issues in real-time synchronization between ECE and BRM.



The rounding function was incorrectly rounding when using the post-rating extension.



When the CohQL query tool was stopped manually using the Quit command in normal circumstances, ECE was unnecessarily logging an error.



JMS connection issues were logged as debug messages instead of warning messages.



The EBAL functionality was not supported in ECE for aggregated distribution processing.



EM Gateway was taking a longer time to start.



After reloading the customer into the ECE cache, ECE was unnecessarily creating another item for the bill in progress.



When a login was disassociated in BRM, the same was not disassociated in ECE.



The current balance was an exponential value even though it was configured to be a decimal value with a specific precision.



There were issues with the handling of zero duration sessions.



There was an issue in updating the correct life cycle state of subscribers when the ECE extensions were used.



Modifying or setting tax rate was not available in the ECE extensions workflow.



The PCM_OP_BAL_CHANGE_VALIDITY opcode was not synchronizing the validity information of resources when called during the accounting workflow.



Whenever the redirection rule was triggered, if the next update request did not include the Reporting-Reason value, ECE was returning Final Unit Indicator (FUI) and Granted-Service-Unit (GSU) instead of Validity-Time.



When an account was moved from the PRE-ACTIVE or ACTIVE state, it was not possible to detect the transition in Diameter Gateway or ECE extensions for any further customization.



Some FUI scenarios were not working. When there was a Diameter CCR-U request and ECE did not have resource balance to grant, an FUI with URL was returned along with status incorrectly set as FAILURE. Also when there was no resource balance available, a CCR-I request was failing, instead of responding with an FUI with URL and SUCCESS status.







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
 Key Enhancements
 Summary of Customer Issues Fixed in ECE 11.3 Patch Set 8

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.