Normalizers

You use normalizers to select a balance, rating formula, or policy profile, or to prioritize product offers in real-time during rating. You can reuse normalizers in balance filters, rate tables, policy tables, GL transaction type tables, GL account tables, and product offer priority generators.

Note: For multiplexing normalizers, normalization is done using the multiplexing normalizer's referenced normalizers. The compared values are defined in the referenced normalizers. The multiplexing normalizer does not have any values defined for comparison.
MATRIXX Engine supports several normalizer types, each of which uses a math algorithm to calculate results. Each normalizer compares one value to one or more specified values that are defined as normalization parameters to get a result. The condition set defined in the associated normalizer(s) are examined and the result assigned to the valid set is chosen. The comparison can be based on a balance quantity, meter quantity, usage quantity, a MATRIXX Data Container (MDC) field value, or a catalog item parameter. For field values, the field can be present in any of the following:
  • Network message
  • Subscriber MDC
  • Device MDC
  • Group MDC
  • User MDC
  • Purchased offer MDC
  • Extended offer MDC
  • Wallet owned by the event initiator
Note: Normalizers have a size limit of 65535 rows. This limit also applies to decision tables, rate tables, and policy tables.
Normalizers based on MDC field values require you to specify both the MDC and MDC field in the normalizer template. If fields are defined in the template, a table called MDC Fields displays when you edit the normalizer.
Note: Normalize on either MDC fields or parameters. Do not normalize on both.

For fields in the group MDC, you supply the group tier in addition to the comparison field. If you configure a normalizer template to have a result_field element that maps a field name and description to MDC fields, this information is also displayed in the normalizer in My MATRIXX. The MDC, MDC field, and result_field information, displayed in My MATRIXX as a reference when setting up parameter values, is for display purposes only and is not editable.

Normalizers use the field values and eligibility features from the caller (the A number) for normalization by default. For normalizers used in rate tables for usage application, you can specify to use fields obtained from the called subscriber (the B number) instead. You configure to use the B number by setting the Use Called Station Field to true in the normalizer template assigned to the normalizer, and then by specifying which MDC and MDC field to use to retrieve the B number data. For more information about using the B number for normalizations, see the discussion about normalizing on B number.

Normalizers based on a catalog item parameter require you to specify the parameter in the normalizer template. If parameters are defined in the template, a table called Parameters displays when you edit the normalizer. The following normalizer types support normalizing on parameters:
  • Date Set Match
  • IPv4 and IPv6 Address Match
  • Numeric Equality
  • Numeric Range
  • Phone Number Match and Phone Number Pattern Match
  • String Match and String Set Match
  • Time Interval Range
  • Zoning

The catalog item gets values for its parameters when the catalog item is purchased. The PurchaseOffer SubMan API specifies the values for the parameters used by the catalog item:

  • parameter ID or name
  • parameter value

For parameters, normalization can only be done for the following data types:

  • decimal
  • int32
  • int64
  • uint32
  • uint64
  • boolean
  • string
  • datetime

Create and change normalizer templates and normalizer instances in the Normalizer Configuration interface in My MATRIXX.