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.
Event Lifespan Codes
The Event Purge utility uses event lifespan codes to determine when an event should be deleted from the Event Repository.

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.
      - Create an Event Lifespan Code
        You can create a new event lifespan code that you can assign to an event type in Event Types.
      - Change an Event Lifespan Code
        You can change the name of an event lifespan code.
      - Delete an Event Lifespan Code
        You can delete an event lifespan code if there are no event types that reference it.
    - 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.
    - 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

Event Lifespan Codes

The Event Purge utility uses event lifespan codes to determine when an event should be deleted from the Event Repository.

When the Charging Server generates an event, the DeleteCode field in the event includes the ID of the event lifespan code configured in the event type. For example, here is part of an MtxVoiceEvent EDR which includes a DeleteCode for the event lifespan code named short_term.

<EventTime>2016-10-31T20:18:02.000000Z</EventTime>
      <Duration>10000000</Duration>
      <EventId>GAEQA_0:1:52:41</EventId>
      <DeleteCode>1</DeleteCode>

During configuration of the Event Purge utility, you can configure the lifespan duration in days for each event lifespan code. For example, the event lifespan code short_term can be configured with a duration of 90 days. The Event Purge utility deletes the event in the example 90 days after the EventTime.

For information about assigning event lifespan codes to events, see the discussion about event types. For more information about the Event Purge utility, see MATRIXX Integration.