Home
MATRIXX Pricing and Rating
Rating
The following information describes MATRIXX Charging Application rating functionality.
Service Types
Each network message received for subscriber usage is associated with a service type, and each category of usage within the network message is associated with a service context.
Service Context
A service context is a service type of a service specific to a certain service type. Each service context can be rated differently.

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
- About Pricing and Rating
  MATRIXX Pricing and Rating provides an introduction to MATRIXX pricing and rating functionality and describes how to define the catalog components necessary for rating and policy selection. It also provides an overview of the MATRIXX rating process and an introduction to My MATRIXX, a web-based user interface application you use to create and manage product catalogs.
- Rating
  The following information describes MATRIXX Charging Application rating functionality.
  - Rating Overview
    MATRIXX Charging Application can perform both online and offline rating in support of next-generation networks and legacy systems. It can also handle hybrid sets of convergent, prepaid, and postpaid services, enabling service providers to have a diverse subscriber base.
  - Usage and Non-Usage Rates
    Rates can be based on service usage and on activities not related to service usage, such as cycle processing, first use of a balance, catalog item purchases, and product offer cancelations.
  - Event Types
    MATRIXX Engine supports multiple built-in event types that are defined in a tree hierarchy based on pricing configuration and stored in the pricing database. You can define custom subordinate event types (sub events) for an event type.
  - Operation Types
    Use operation types to customize non-usage events. The operation type in an event mapping must match an event type. For example, the recurring_subscriber operation can only correspond to a recurring event, such as SubscriberCustomRecurringEvent.
  - Service Types
    Each network message received for subscriber usage is associated with a service type, and each category of usage within the network message is associated with a service context.
    - Service Context
      A service context is a service type of a service specific to a certain service type. Each service context can be rated differently.
      - Service Context Rating
        Define general rating information for a service context type in My MATRIXX Help. MATRIXX Charging Application and MATRIXX Policy Application use these properties during rating.
      - Service Context Aggregation
        Define aggregation settings for a service context type in My MATRIXX. Define properties to configure whether usage is aggregated across the duration of the context session. If aggregation is configured, you can define how usage is aggregated and whether this is a limit to the aggregation. An Event Detail Record (EDR) for aggregated usage is generated based on these settings.
      - Service Context Quota Settings
        Define general quota properties and Adaptive Quota Management (AQM) properties for a service context type in My MATRIXX.
      - Service Context Authorized Quantities
        Define authorization information for a service context type in My MATRIXX Help.
      - Service Context Final Unit Indication
        Define final unit indication (FUI) information for a service context type in My MATRIXX. Select properties to define information for the Diameter Final-Unit-Indication grouped AVP. You can configure FUI to be set dynamically during runtime based on valid pricing or you can specify values that are set to the same static value during runtime, without regard to any pricing.
      - Service Context PreRating Queries
        MATRIXX Engine uses pre-rating query data for determining when to perform a call out request for subscriber information to an external server or database. You configure pre-rating to be dynamic, so a different result occurs based on conditions that are valid at the time of rating. You can select a PreRating generator for a service context type in My MATRIXX.
      - Service Context PostRating
        MATRIXX Engine uses post-rating profiles and generators for determining a set of actions to apply to a message after it has been processed by rating. You configure post-rating to be dynamic, so a different result occurs based on conditions that are valid at the time of rating. You can select a PostRating generator for a service context type in My MATRIXX.
  - Device Types
    The MATRIXX Engine supports mobile and login devices. A mobile device uses one or more associated phone numbers to identify the subscription associated with the device. Login devices use a string value (SIP URI (Session Initiation Protocol Uniform Resource Identifier), an NAI (Network Address Identifier), or a PrivateId) for identification.
  - 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.
  - Rating One-Time Events
    MATRIXX Charging Application supports 3GPP Immediate Event Charging (IEC) to authorize and charge for one-time events, such as SMS, MMS, or other messaging services (such as purchases of ring tones, media, or mobile Apps) and in-app micro-transactions. Typically the data for event-based requests maps to debit, refund, query, and price checking operation types. If configured, after a successful IEC operation, a notification (MtxEventChargeNotification) is triggered.
  - Rating Sessions
    MATRIXX Charging Application supports the 3GPP Session Charging with Unit Reservation (SCUR) and Event Charging with Unit Reservation (ECUR) to handle authorization and accounting for subscriber usage.
  - How Rating Is Performed
    When events are received in MATRIXX Engine, a list of candidate product offers is created and examined for each event segment to determine which ones apply. Determining the candidates involves identifying the valid price components, which is dependent on the validity of the balances and normalization values.
  - Advice of Charge
    MATRIXX Engine supports Advice of Charge (AoC) for usage and non-usage rating.
  - Detecting Duplicate Network Messages
    MATRIXX Engine can detect when a duplicate network message is received and does not repeat the processing for the duplicate message.
  - Using Time Zones for Rating
    You can configure rates based on the time zone of MATRIXX Engine, the time zone of the subscription, or the UTC offset in the network message.
  - Generating Notifications During Rating
    Real-time notifications enable you to alert subscribers and group administrators immediately when product offers are purchased, canceled, or expire, when balances expire, and when balances are nearing credit limits and assets are about to expire, so they are aware of their current spending situations.
  - MATRIXX Event Detail Records
    MATRIXX Engine generates an _glossary/edr.html for all activities that can trigger rating, such as usage, catalog item purchases and cancelations, recurring cycle processing, or the first use of a balance. MATRIXX Engine also generates EDRs for non-rated events such as forfeitures. You configure event generation in My MATRIXX, including the events to generate and whether to add a custom container with additional mapped fields.
  - Processing Call Detail Records
    The MATRIXX Engine can rate call detail records (CDRs) in Solution42 format and save the results to MATRIXX Event Detail Records (EDRs) so the information can be imported into a third-party system for billing or analytical processing.
  - MATRIXX Event Files
    MATRIXX Event Files (MEFs) contain a list of usage and non-usage event types generated during transaction processing. MEFs are meant to be published to, and consumed outside of, MATRIXX, and can be input to third-party applications.
  - Multi-Tenancy Support
    MATRIXX supports multi-tenancy for service providers who want to host more than one tenant on the same sub-domain, where a tenant is a subset of the subscribers within a subscriber base that use the same pricing configuration and that have the same set of business behaviors, such as prepaid or postpaid, or the same Mobile Virtual Network Operator (MVNO).
  - 5G AMF Charging
    MATRIXX supports charging for usage related to the 5G Access and Mobility Management Function (AMF).
  - Other 5G Service Charging
    MATRIXX supports charging for the following services in the 5G Release 17 Specification:
  - Network Exposure Function Charging
    MATRIXX supports charging for the Network Exposure Function (NEF).
  - Cycle Processing
    The Charging Server supports balance cycles, billing cycles, and purchased item cycles.
- Pricing
- Appendices
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Service Context

A service context is a service type of a service specific to a certain service type. Each service context can be rated differently.

When a service is created, it includes an empty default service context type in which you define fallback values for the rating settings, aggregation settings, quota settings, authorized quantities, and Diameter final unit information (FUI) categories. The settings within each category are treated as a unit. The default service context type serves as a fallback. During rating, a custom service context type is selected to rate a session. If the custom context type does not have any parameters in a particular category, all the parameters in the corresponding category of the default service context type are used. You can also specify a PreRating generator and a PostRating generator in the default service context.

Configure the options in this section on a per-service context basis as part of the service type definition.

Note: The PreRating generator and PostRating generator can only be changed on the default service context and are inherited by all custom context type definitions.