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.
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.
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 Type Properties
A service type definition includes information about the service quantity, service context types, beats, fields to add to an _glossary/edr.html, and fields to add to a session object. A service context can be configured with usage aggregations, quota management and authorization behavior, and final unit indication behavior.
Service Context Type Properties
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 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 specific 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.
Service Context – Rating Properties
The general rating information in pricing/c_service_context_props_rating.html#reference_6D8EB3710A90439088805EF2603D765E__table_8A59BD14626A44C89580C85EFCCC9FED can be defined for a service context. It is used in MATRIXX Charging Application and MATRIXX Policy Application during rating. The Session Meter IDs and Context End Notification properties are optional.

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.
  - 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.
    - Billing Profile Templates
      The bill cycle specification associated with a subscription is retrieved from a predefined billing profile template in the subscription's wallet. The template is created as part of pricing configuration and forces all bill cycle pricing associated with the subscription to be applied with the same cycle settings. Each wallet can contain only one billing profile template, which defines the bill cycle specifications.
    - Currency Codes
      Currency balance classes are identified by an ISO standard currency code. You must define currency codes in My MATRIXX so pricing administrators can select one when creating a currency balance class.
    - Event Lifespan Codes
      The Event Purge utility uses event lifespan codes to determine when an event should be deleted from the Event Repository.
    - Event Mapping
      Subscription, user, group, and device operations, such as a subscription creation, usage refund, or device suspension, have a one-to-one mapping to respective events and define the fields to be included in the Event Detail Record (EDR).
    - 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.
    - Field Definitions
      You can add _glossary/mdc.html fields to your pricing plan and use them as a quantity type on which to base rating or to define the tiers used for closed user group normalizers.
    - Inbound Roamer
      In Inbound Roamer, you define the agreements with third-party operators that allow usage and policy requests for subscribers that are not identified in MATRIXX. You can define agreements for roaming requests and emergency requests.
    - Notification Types
      In Notification Types you can define which fields from device, subscriber, group, wallet, and session objects are included in notification messages. You can also add filters to a notification type that determine when a notification message should not be sent.
    - Offer Life Cycle Profiles
      An offer life cycle profile consists of a set of offer statuses, a set of policies associated with each offer status that describe behavior that can be executed in this status, and a set of transitions that can have conditions defined that can trigger a transition and actions defined that are executed after the transition is performed. Both offers and bundles can have an offer life cycle profile defined. Use offer life cycle profiles to customize the behavior of MATRIXX for your business processes.
    - Offer Life Cycle Status Codes
      Offer life cycle status codes are linked to offer life cycle status definitions in an offer life cycle.
    - Roles
      A role defines the relationship between a user and its subscriptions and groups.
    - 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.
      - Create a Service Type
        You can add new usage service types to your base configuration that contain configurations specific to that service, including contexts for that service. Services support the Diameter Multiple-Services-Credit-Control (MSCC) Diameter AVP and allow you to define service contexts and quota information. The quantity information for each context can include configurations for event usage aggregation and Adaptive Quota Management (AQM).
      - Create a Context Type
        (Optional) Add one or more custom service contexts to the service type. Custom service contexts are used by the rating engine to rate events. For details about the service context parameters, see the discussion about service type context properties.
      - Change a Service Type
        You can change service types and sub service types, and their event and audit data field mappings. Changes to service type names also changes the path of that service type and any the paths of its sub services.
      - Delete a Service Type
        When you delete a service type, it is no longer available for rating. Do not delete a service type that is associated with a product offer.
      - Service Type Properties
        A service type definition includes information about the service quantity, service context types, beats, fields to add to an _glossary/edr.html, and fields to add to a session object. A service context can be configured with usage aggregations, quota management and authorization behavior, and final unit indication behavior.
        General Service Type Properties
        pricing/c_service_props_general.html#reference_6D8EB3710A90439088805EF2603D765E__table_46B08B320397415585801F796A2B15D2 lists the properties that define standard attributes of the service.
        Service Context Type Properties
        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 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 specific 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.
        Service Context – Rating Properties
        The general rating information in pricing/c_service_context_props_rating.html#reference_6D8EB3710A90439088805EF2603D765E__table_8A59BD14626A44C89580C85EFCCC9FED can be defined for a service context. It is used in MATRIXX Charging Application and MATRIXX Policy Application during rating. The Session Meter IDs and Context End Notification properties are optional.
        Service Context – Aggregation Settings Properties
        You can define the properties in pricing/c_service_context_props_aggregation.html#reference_6D8EB3710A90439088805EF2603D765E__table_F1917ED4CAE14DDE88A016D002AC5D86 for a service context to configure whether usage is aggregated across the duration of the context session.
        Service Context – Quota Settings Properties
        You can define general quota properties and Adaptive Quota Management (AQM) properties for a service context.
        Service Context – Authorized Quantities Properties
        The authorization information in pricing/c_service_context_props_authorization.html#reference_6D8EB3710A90439088805EF2603D765E__table_7075CDC13E1F4325ABF161BDF016CE44 can be defined for a service context. If any authorization values are specified for a service context, it is assumed that all attributes are set. Therefore, all authorization attributes set for the default service context are ignored. It is an all-or-nothing specification.
        Service Context – Final Unit Indication Properties
        The following Final Unit Indication (FUI) values can be defined for a service context type. They 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 get set to the same static value during runtime, without regard to any pricing.
        Service Context – PreRating Queries Properties
        Select a PreRating generator from the menu. You can only make this selection on the default service context, and it is inherited by all custom service contexts.
        Service Context – PostRating Properties
        Select a PostRating generator from the menu. You can only make this selection on the default service context, and it is inherited by all custom service contexts.
        Beat Definition Properties
        Beat definitions listed in pricing/c_service_props_beat_definitions.html#reference_6D8EB3710A90439088805EF2603D765E__table_27AA630D59384D79A8A5E70EBBFD05F4 are only used in My MATRIXX and are not compiled into the service context directly. The information is used to populate the available beats that can be used in a price component's rate table.
        Service Context Beat Group Properties
        Beat groups enable a group of service contexts to share the same amount rounded up for a beat when usage is less than the beat amount. The beat amount cached for one service context can be used by the other service contexts before their balances are charged a full beat amount.
        Event and Failed Event Field Mapping Properties
        Event field maps defined in a parent service type are inherited by child service types and are included in the Event Detail Record (EDR). Field Mapping Properties lists the properties you can set.
        Audit Data Field Mapping Properties
        During MATRIXX Engine configuration, you can extend the MtxAuditData MATRIXX Data Container (MDC) to create custom MDCs with additional fields that are populated with audit data that is written to transaction log files.
        Session Field Mapping Properties
        Session field mappings have the properties listed in pricing/r_service_props_session_field_mapping.html#reference_6D8EB3710A90439088805EF2603D765E__table_ux4_dkj_cjb.
        Session Monitor Event Field Mappings
        Any event field maps defined in a parent service type are inherited by any child service type and included in its Event Detail Record (EDR). rating/r_session_monitor_event_field_mapping.html#reference_nk2_dbm_xwb__table_C5A5B6BA730C47ECA71A14F3357010E7 lists the properties that can be set.
    - Status Life Cycles
      A status life cycle is a collection of object states, policies, and transition rules that are defined for a specific object type. You can define a status life cycle for user, device, subscription, group, and offer objects to customize the behavior of MATRIXX for your business processes. For example, a device life cycle can begin with a provisioned status, transition to an active status, and finally transition to an inactive status.
    - Tenant Profiles
      Use a tenant profile to configure the unique ID for identifying a tenant across sub-domains, and to configure optional extensions to the tenant profile.
- 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

Service Context – Rating Properties

The general rating information in Rating Properties can be defined for a service context. It is used in MATRIXX Charging Application and MATRIXX Policy Application during rating. The Session Meter IDs and Context End Notification properties are optional.

Table 1. Rating Properties
Property	Description
ID	The ID of the service context. This value is set in the ServiceName field in the DiameterRoMsg MATRIXX Data Container (MDC).
Name	The name of the service context. This value is set in the ServiceContextId field in the DiameterRoMsg MDC, which maps to the Service-Context-Id AVP.
Rating Quantity Type	The quantity type that is measured for the service usage by this service context, on which to base rates. Only price components with this quantity type are considered applicable during rating. One of: None actual_duration active_duration monetary total_data in_data out_data service_specific
Session Meter IDs	The ID of any meters tracking this service context. Add session meter IDs as a comma-separated list. Session meter IDs are located in the meter template definition in My MATRIXX.
Context End Notification	When selected, triggers a notification to be sent when the service context session ends.
Used Service Units are Cumulative	For duration services (such as voice). When selected, each message reports usage cumulatively since the start of the session. The default option expects incremental usage from the previous message (the Diameter standard).
Granted Service Units are Cumulative	For actual duration services (such as voice). When selected, each message reports cumulatively the amount of granted service units since the start of the session. The default option expects incremental usage from the previous message (the Diameter standard).
Disable Sending RARs	For Gy and N40 usage, specifies if RARs are disabled for this specific service type. Out-of-the-box, RARs are always sent when triggered. Note: Some RARs do not consider the specific service context; to ensure all RARs are disabled, disable all service contexts by answering `y` to the following global configuration question:`Global:Session:Charging:Notify:Disable Re-Authorization Requests (y/n)?`