This chapter is an overview of the usage-charging related configurations you must implement for Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE), such as charging business rules and runtime configurations.
The usage events for which you charge your customers must be defined in the ECE system. You define chargeable usage events by defining the events in BRM and adding additional information required for processing usage requests in the event definition in Pricing Design Center (PDC). For more information, see the discussion about enriching event definitions in PDC User's Guide.
For information about how Diameter charging applications use request specification data in the event definition for building usage requests, see "Integrating Charging Clients with ECE".
Most of the configuration that influences how usage requests are charged is done in PDC by defining your ECE pricing components. You can configure usage-charging business rules at the ECE system level to influence the usage-charging flows of specific charging operations. For example, you can configure how ECE will round a charging result for currency and non-currency resources.
For information about configuring usage-charging business rules, see "Configuring Business Rules for Charging".
You must set runtime configuration options that influence how ECE processes data when processing usage requests. For example, you must configure taxation. You can also configure ECE to publish notifications for sending data to other applications in the charging system. For information about configuring runtime charging options, see "Configuring Charging Runtime Options".