Home
My MATRIXX Help
Charging Configuration
Charging Configuration has the interfaces you use to create and manage balance, pricing, product offer and bundle, general, and application-related components.
Normalizer Configuration
Normalizer Configuration contains interfaces you use to create and manage normalizers, normalizer templates, and normalizer value lists.
Normalization
MATRIXX Engine uses a process called normalization to condense large sets of discrete field values into a manageable set of parameters. Each single normalizer parameter value represents an aggregate value set, so that assigning a result to every possible field value is not required.
Date Set Match Normalizer
The date set match normalizer compares the time of an operation, such as the event time in a Diameter message, with a list of dates or datetimes saved in a _glossary/mdc.html, such as a custom subscriber or device MDC. If the operation is on a date included in the list in the specified MDC field, the normalizer evaluates to a match.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
- About My MATRIXX Help
  My MATRIXX Help provides information about My MATRIXX, a web application that offers a central location for creating pricing plans and configuring MATRIXX charging and rating behaviors. My MATRIXX is intended for pricing administrators who are responsible for creating and maintaining pricing plans and for IT administrators or developers who configure the rating and charging behavior of the online charging system.
- Introducing My MATRIXX
  The following information describes the My MATRIXX interface.
- Using My MATRIXX
  You use My MATRIXX to validate and compile the pricing configuration file, compile pricing, and set up and manage user roles and domains; create and manage catalog items and catalogs, manage eligibility features and rules, and manage the Normalizers interface; create and manage balances, pricing, offers and bundles, general components, and application-related components; and policies for charging and rating. Use General Configuration to create components that support pricing items and charging functionality such as announcements pricing components, attribute definitions, denial codes, products, decision tables, Final Unit Indication (FUI) profiles and generators, general ledger transaction types, notification profiles, normalizer templates, and subscriber information query actions, profiles, and generators.
- Home Menu
  The following information describes the tasks that can be performed using the My MATRIXX Home menu.
- Catalog Configuration
  Catalog Configuration contains the Catalog Items interface that you use to create, change, or delete catalog items; the Eligibility interface to manage eligibility features and rules to determine whether a subscriber, group, or device is eligible for a catalog item; and the Normalizers interface you use to edit normalizers.
- Charging Configuration
  Charging Configuration has the interfaces you use to create and manage balance, pricing, product offer and bundle, general, and application-related components.
  - Balance Configuration
    Balance Configuration contains interfaces you use to create and manage price components including aggregation selectors, balances and balance classes, balance state update profiles and components, meters, and rollover profiles and components.
  - Pricing Configuration
    Pricing Configuration contains interfaces you use to create pricing plan components. Pricing plan components managed through this interface include decision tables, finance and service contracts, filters, price components including charges, discounts, grants, refunds, and forfeitures, and rate tags.
  - Offer and Bundle Configuration
    Offer and Bundle Configuration contains interfaces you use to create and manage pricing and rating components including bundles, offer priority generators, product offers, and product service types and attributes.
  - Normalizer Configuration
    Normalizer Configuration contains interfaces you use to create and manage normalizers, normalizer templates, and normalizer value lists.
    - Normalization
      MATRIXX Engine uses a process called normalization to condense large sets of discrete field values into a manageable set of parameters. Each single normalizer parameter value represents an aggregate value set, so that assigning a result to every possible field value is not required.
      - Balance Difference Normalizer
        A balance difference normalizer chooses a result by comparing the following values to ranges of balance differences specified in the normalizer:
      - Balance Distribution Normalizer
        The balance distribution normalizer compares a balance or meter quantity to ranges of quantity values defined in the normalizer and matches the quantity to one range. The ranges must cover from negative infinity to infinity, with no gaps, and are used to choose a result.
      - Balance Spendable Normalizer
        The balance spendable normalizer determines whether any amount of a balance (or set of balances of the same class) is available for usage charging. The balance spendable normalizer is similar to a balance distribution normalizer in that normalization is based on an available balance amount with two ranges, the first range being less than or equal to zero and the second range being greater than zero.
      - Closed User Group Normalizer
        The closed user group normalizer, depending on configuration, either compares whether the subscription initiating an event is in the same group as the subscription receiving the event, or whether the subscription initiating an event is on the same same sub-domain as the subscription receiving the event.
      - Date Set Match Normalizer
        The date set match normalizer compares the time of an operation, such as the event time in a Diameter message, with a list of dates or datetimes saved in a _glossary/mdc.html, such as a custom subscriber or device MDC. If the operation is on a date included in the list in the specified MDC field, the normalizer evaluates to a match.
      - Difference Range Normalizer
        The difference range normalizer compares the following numeric values (integer or decimal) to ranges of differences specified in the normalizer:
      - Eligibility Feature Match Normalizer
        The eligibility feature match normalizer compares the feature defined in the normalizer with all the features of all the catalog items owned by a subscription, group, or device, to look for a match.
      - IP Address Normalizers
        IP address normalizers specify one or more IP addresses, defined by the normalizer as strings using the Classless Inter-Domain Routing (CIDR) notation, with which to compare an IP address value in the network message. If a match is found, the index associated with that IP address is used. A specified IP address can be an exact address or it can contain an optional network mask to denote a range of IP addresses.
      - Multiplexing Normalizer
        Multiplexing normalizers reference one or more other normalizers. During authorization and rating, a multiplexing normalizer checks the fields used by its referenced normalizers. If a field used by one of the referenced normalizers is a valid field in the message being processed, then the referenced normalizer is selected and executed for rating. A normalizer that does not normalize on MATRIXX Data Container (MDC) fields should not be referenced by a multiplexing normalizer.
      - Numeric Equality Normalizer
        Numeric equality normalizers have two types, one for signed integers and one for unsigned integers. Each one chooses a result by comparing the numeric value in a specified MATRIXX Data Container (MDC) field to one or more values of the same type specified in the normalizer. If a match is found, rating uses the index associated with that numeric value.
      - Numeric Range Normalizer
        Numeric range normalizers have three types, one for signed integers, one for unsigned integers, and one for decimals. Each one chooses a result by comparing a numeric value in a specified MATRIXX Data Container (MDC) field to numeric ranges specified in a normalizer. On finding a match, rating uses the index associated with that range.
      - Phone Number Match Normalizer
        The phone number normalizer compares a phone number value in the network message to one or more phone number prefixes specified as normalizer parameters. If the leading digits of the phone number matches one of the specified phone number prefixes, the index associated with that value is used.
      - Phone Number Pattern Match Normalizer
        The phone number pattern match normalizer uses complex strings (patterns) with ranges to represent a set of one or more phone numbers. It then compares a phone number value in the network message to each pattern specified as a normalizer parameter. If the phone number value matches one of the specified number patterns, the index associated with that value is used. The phone number pattern match normalizer can match strings that contain more than 15 digits, or that include the following characters: #, *, a, b, c, A, B, C, D, or E.
      - Phone Number Set Contains Normalizer
        This normalizer compares a phone number or string field in any MDC, for example, in the Diameter message, with a set of phone numbers stored in any MATRIXX Data Container (MDC), such as an extended subscriber object or group object MDC to see if the set contains the exact same phone number.
      - Quantity Distribution Normalizer
        The quantity distribution normalizer defines ranges of usage quantities that can be associated with different rating results. It operates on the aggregated session quantity.
      - String Match Normalizer
        A string match normalizer compares a string value in a specified field to a list of strings specified as normalizer parameters. The comparison can be configured to match characters starting at the beginning of the string (a prefix match) or the end of the string (a suffix match). If a match is found, the result associated with that string is used. Each specified string value can be configured to be an exact match or a closest match. In the case of a closest match, the string with the longest matching characters is used.
      - String Set Matches Normalizer
        The string set matches normalizer compares a value in a MATRIXX Data Container (MDC) field with a value in another MDC field. Both fields can either be a single string/phone number or a list/array of strings/phone numbers. The comparison could be an exact match, prefix match, or suffix match. If one field is an array/list and one field is a single value, then the system checks if anything in the list/array matches the single value (using the match mode). If a match is found, then the normalizer evaluates to true. It does not matter which field is the list/array and which is the single value. If both are arrays/lists, then the system checks if a value in one list/array matches any value in the other list/array.
      - Time Normalizer
        The time normalizer determines a result by comparing the start time of an event with multiple time ranges and matches the time into one range. A different result can be selected if the event spans multiple time ranges.
      - Time Interval Range Normalizer
        A time interval range normalizer chooses a result by comparing a time interval to time interval ranges specified in the normalizer. For each matching range, rating uses the index associated with that range.
      - Zoning Normalizer
        The zoning normalizer determines a result by comparing two specified field values with a list of paired values listed in From and To fields.
    - Normalizer Templates
      Normalizer templates identify the MATRIXX Data Containers (MDCs) and MDC fields, balances, quantities, or times that rating uses for normalization when deciding which rates to apply. Normalizer templates that perform normalization based on one or more field values require you to specify the field and the MDC containing it.
    - 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.
    - Normalizer Value Lists
      A normalizer value list is used to define a list of values available to a normalizer. The values in a normalizer value list can be shared between multiple normalizers, ensuring that they all have the same list of values and indices in a matrix. For example, all the normalizers referenced in a multiplexing normalizer must use the same normalizer value list to ensure that they all have the same values.
    - Normalizer MDCs
      The following MATRIXX Data Containers (MDCs) have fields that can be used during normalization:
  - Tax Configuration
    Tax Configuration contains interfaces you use to create and manage tax classes and selectors, and US taxation. You must have the Manage Tax domain user role to enable this menu.
  - General Configuration
    General Configuration has interfaces you use to create pricing plan components. Pricing plan components managed through this interface include announcements, product and system attributes and definitions, currency codes for rate tables, denial codes, field definitions for use in normalizers and rate tables, Diameter Final-Unit-Indication (FUI) profiles and generators, General Ledger (GL) transaction types and info generators, grace period profiles, languages, notification profiles, parameter definitions, pre/post-rating profiles and generators, SH Repository data, Subscriber Information Query components, tax classes for offer categorization, usage quota profiles and components, purge profiles, virtual fields, and usage triggers.
  - Application Configuration
    Application Configuration components are used by My MATRIXX for creating pricing plan items and are used by MATRIXX Charging Application and MATRIXX Policy Application for charging and rating.
- Policy Configuration
  Policy configuration components are used by MATRIXX Charging Application and MATRIXX Policy Application for charging and rating.
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Date Set Match Normalizer

The date set match normalizer compares the time of an operation, such as the event time in a Diameter message, with a list of dates or datetimes saved in a MATRIXX Data Container (MDC), such as a custom subscriber or device MDC. If the operation is on a date included in the list in the specified MDC field, the normalizer evaluates to a match.

The date set match normalizer has two possible parameter values, true and false. If the value matches one of the dates in the list, the index associated with the true parameter value is used. Otherwise, the index associated with the false parameter value is used. For example, the normalizer could compare a date-time field in the incoming network message with the value in a custom field in an extended subscriber MDC that has a list of special dates. If the event occurs on a date in the list, the index associated with the true parameter is used.

You define the time zone for the comparison in the normalizer template using one of the following options:

event — Uses the time zone indicated by the incoming network message, which is impacted by the 3GPP-MS-Timezone and Event-Timestamp AVPs. This is the time zone where the event is initiated and is dependent on the initiator's current location, which can vary. It is the default.
initiator — Uses the time zone stored with the subscriber's profile information. This time zone is static and is typically the time zone of the subscriber's residence. It is not necessarily the same time zone in which an event is initiated.
system — Uses the time zone configured for the MATRIXX Engine. This time zone is also static. It is not necessarily the same time zone in which the system is physically located or indicated by the network message for the event.
utc — Based on the time of day of the event, interpreted in the UTC offset contained in the event message.

Note: If the year, time of day, or timezone, or UTC offset are included in the field value to normalize, they are ignored during the comparison.