My Oracle Support Banner

Release Of Oracle Communications BRM Elastic Charging Engine (ECE) Version 11.3 Patch Set 9 (Doc ID 2475551.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 9 ( is released on 21 November 2018.
This announcement lists the enhancements and fixes delivered in Elastic Charging Engine 11.3 Patch Set 9.

Patch ID: <Patch 28738541>



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 9.

Improved Resiliency with Continued Elastic Charging Engine Operations without BRM

In previous releases, ECE was using the Portal Object IDs (POIDs) generated in BRM for tracking rated events and bill items created in ECE. In case of any connectivity failures between BRM and ECE, ECE was unable to continue with charging for the incoming usage requests. With this enhancement, ECE can generate POIDs necessary for charging without depending on a running BRM instance and hence makes the charging functionality resilient. This also helps during operational maintenance that may require a restart of BRM.

Automatic retry of failed Customer Updater Startup

In the previous releases, if Customer Updater failed to connect to the BRM database during startup, restart, or failover, you had to manually restart Customer Updater.

With this enhancement, you can configure Customer Updater to automatically retry the BRM database connection and restart the process by specifying the number of retries allowed after it fails. This ensures that Customer Updater is started automatically without any manual intervention.

High Availability Support for ECE Components

In the previous releases ECE components viz., Rated Event Formatter, BRM Gateway, Customer Updater and Pricing Updater were not highly available components and if in case any of these components were down for any reason, that we affecting the ECE functionality.

With this enhancement, you can configure and start multiple additional instances of Rated Event Formatter, BRM Gateway, Customer Updater and Pricing Updater components in the same system or different ECE systems (such as backup machines) to ensure high availability.

Improved BRM-to-ECE Data Synchronization

In the previous releases, sometimes there was a lag between the BRM database and the ECE cache update when the BRM data commit failed. During the lag, the BRM and ECE data were unsynchronized. With this enhancement even if there is a data commit failure, the data consistency between BRM and ECE are maintained.

Diameter Peer Connections:

The ECE Monitoring Agent now monitors all the Diameter peers connected to the Diameter Gateway instances at regular intervals and logs the details of the peers. You can also view the peers in the JMX Console through ECE MBeans. Logging of Diameter peers is a new feature introduced in this Patch Set, that provides details of all other Diameter nodes in your deployment.

Wildcard support for service and event names in rating: During design time, Pricing Design Center now supports wildcard (*) in item type selectors for services and events. You can use the wildcard to substitute one more characters in the service or event name to indicate that any value is acceptable, for example, /service/telco/gsm*.  The following elements are added in PDC to support wildcard: applicableToAllChildServices and applicableToAllChildEvents. By setting the true or false value to these elements, you can indicate whether the item type selector is applicable to child services or events.

The charging functionality in ECE is now enhanced to support wildcard in item type selectors for services and events. If wildcard is used in the services and events, ECE uses the applicableToAllChildServices and applicableToAllChildEvents values to identify if the services or events are applicable for all child services or events. If the value is set to true, the item type selector is considered for all the child services and events. If the value is set to false, the child services or events are not considered.


For more information please see the Elastic Charging Engine documentation.



Summary of Customer Issues Fixed in ECE 11.3 Patch Set 9

Customer Issues Fixed in ECE

SR Number

Bug Number




ECE displayed errors with null pointer exceptions when the billing process was in progress. 

This has been fixed. With this fix, ECE will continue with charging without any such exceptions even when the billing is in progress in BRM.



When there were many JMX-enabled server nodes in the ECE cluster, Elastic Charging Controller (ECC) was taking considerable time to start the server nodes.

This has been fixed. With this, in our testing lab, for an ECE multi node setup with 30 JMX enabled nodes the startup time is reduced from 20 minutes to 3 minutes.



During rating for a subscriber having sharing agreements, after consuming all available resources till credit ceiling breach, the subsequent update session with zero requested units to ECE was not causing ECE to disconnect the active session with a terminate call. This was blocking the active session. This was because, the rating was failing due to the incorrect balance retrieved from the alteration agreements for the subscriber. This has been fixed.



The connection retry configuration for Pricing Updater was inconsistent compared to other similar processes.

This has been fixed and now the configuration for Pricing Updater is similar to that of other configurations in ECE.



Pricing Updater was failing with an error due to unicode characters. This issue was seen since PS6.

This has been fixed. Pricing Updater can now successfully parse unicode characters.



When multiple member services were purchased for a subscriber, and after expiration of one such member service, if an old backdated CDR was processed for the expired service, ECE was throwing a null pointer exception.

This has been fixed. With this fix, you can process the late CDRs for an expired service, provided the CDRs have a timestamp earlier than the service expiry date.



There was an increase in the CPU utilization after Customer Loader failed to load customer data into the ECE cache.

This has been fixed.



ECE stopped processing requests due to a deadlock encountered while accessing the recurring bundle history.

This has been fixed.



The service transfer functionality from one account to another account was not working, when the payload to EM Gateway did not include alias lists for the service.

This has been fixed.



In a BRM system integrated with ECE, External Manager (EM) Gateway, any BRM initiated operation that requires to update ECE cache, updates the data in BRM and in the same transaction updates it in ECE cache through EM Gateway; once it is committed in ECE, the transaction is committed in BRM database. During this, if there was an error during the pre-commit phase of BRM transaction, then there used to be data inconsistency between BRM and ECE.

This has been fixed. The ECE commit is now triggered only after the BRM commit succeeds.

For this the following updates are necessary in the pin.conf of CM:

- cm em_group ece PCM_OP_ECE_POST_COMMIT 
- cm ece_post_commit_enabled 1

Also the following updates are necessary for ECE to participate in the post commit trigger for transactions from BRM. This requires BRM to be upgraded to to a minimum.

  1. Edit ECE_HOME/config/management/charging-settings.xml file and add the 
       below biz config parameters. 
  2. Edit the ECE_HOME/config/charging-cache-config.xml file and add below 
       cache mapping entry 




The ECE Monitoring Agent was not logging the Diameter messages in the Diameter Gateway statistics report.

This has been fixed. With this you will be able to monitor the statistics related to Diameter event request messages from JMX Console.



Diameter Gateway was returning the success result though the corresponding user ID was not present in the identity repository.

This has been fixed. With this Diameter Gateway will first verify for the corresponding user ID in the identity repository and accordingly return the results.



The pre-rating extension returned a null pointer exception when extensionContext.getSharedProfiles() method was invoked.

This has been fixed. This fix allows you to invoke the above method to get the shared profiles from the pre-rating extension without any error or exceptions.



When you delete an account in BRM, the corresponding account data must be deleted in ECE. It was observed that the customer data was deleted from ECE cache, but, the balance information was not deleted if it was not associated at the product level or if it was not the default balance for the account.

This has been fixed. With this all information pertaining to the customer is deleted in ECE cache.



The Diameter Gateway(DGW) response did not include the Multiple-Services-Credit-Control (MSCC) block and this resulted in an intermittent null pointer exception. This was a concurrency issue when multiple services credit control requests are handled concurrently by multi-threaded DGW.

This has been fixed. The MSCC scenario works properly without any null pointer exception or concurrency issues.



The notifications were not getting published to the WebLogic JMS queue, after the upgrading to or versions.

This has been fixed.



When a patch set was installed in a disaster recovery deployment, the ECE_home/oceceserver/config/management/charging-settings.xml file in the secondary site was not automatically updated with the latest configurations. This was observed with an upgrade to PS8.

This has been fixed. All configurations are now correctly updated in the secondary site.



In BRM, after creating a sharing group, calling the opcode PCM_OP_SUBSCRIPTION_SHARING_GROUP_SET_PARENT to update the sharing group parent, it failed in ECE when processing ModifyGroupSharingDiscounts notification, if the parent account did not have any charge share offer.

This has been fixed.



During failover, BRM Gateway could not reconnect to the WebLogic JMS queue.

This has been fixed. BRM Gateway was updated to do retries if there were any JMS look up failures during the connection initialization function.



The Customer Service Representative (CSR) Accounts are typically service only accounts in BRM and not associated with any offerings. In a deployment, updating the status of a CSR account using PCM_OP_CUST_SET_STATUS opcode was failing in ECE with a rating context error, throwing an exception indicating “No valid product can be found to apply tariff for”.

This has been fixed. If a CSR account is updated for its status, it will not generate the above mentioned exception.




In ECE, performance issues were caused by the parse method of the TimeUtil class for datetime conversions to string and vice-versa.

This has been fixed.





After top-up, rating was failing with the credit floor breach error.

This has been fixed. A new application configuration skipCreditFloorBreachCheck has been introduced with default value as false. When set to true, floor breach 
check will not happen during balance update and usage. 







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

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