Home
My MATRIXX Help
Policy Configuration
Policy configuration components are used by MATRIXX Charging Application and MATRIXX Policy Application for charging and rating.
Spending Limit Configuration
Configure the spending limit control components when using a Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) that is external to MATRIXX Engine. For 5G MATRIXX environments, the spending limit control configuration reference point (N28) is located between your external PCF and MATRIXX Engine as a Charging Function (CHF). For 3G/4G environments, the spending limit control configuration reference point (Diameter Sy) is located between an external PCRF and MATRIXX Engine as an OCS.
Spending Limit Policy Components
A spending limit policy component implements the business logic that decides which counter status to return to the Policy and Charging Rules Function (PCRF) (3G/4G) or Policy Control Function (PCF) (5G) for a given set of circumstances. Pricing administrators define the business rules and decisions by creating policy tables inside the policy counter components.
Spending Limit Policy Component Properties
Use the Edit Spending Limit Policy Component tab of the Spending Limit Policy Components interface to change spending limit components general properties.

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.
- Policy Configuration
  Policy configuration components are used by MATRIXX Charging Application and MATRIXX Policy Application for charging and rating.
  - Policy Overview
    You must have the Pricing User domain role to access this menu and all its components. For more information, see the discussion about technical user roles.
  - Policy Session Mappings
    In MATRIXX 3G, 4G, and 5G environments using MATRIXX Policy Application, each policy session includes an Attr field of type MtxPolicySessionExtension that includes any custom policy session fields. You can map fields in the incoming network message to these Attr fields, or to any custom MATRIXX Data Container (MDC) fields that extend it, to save the field value throughout Gx, N40, Sy, and N28 policy sessions. This allows you to set up rating based on that value.
  - Policy Components
    The 5G MATRIXX policy components include spending limit configuration components. The 3G/4G MATRIXX policy components include spending limit configuration components, session management policy components, policy session mappings, event trigger groups, and event triggers.
  - Event Trigger Groups
    Diameter Gx event triggers define when the PCEF is notified of changing network conditions. An event trigger group is a collection of event triggers that are assigned to a policy profile.
  - Event Triggers
    Gx event triggers tell the Policy and Charging Enforcement Function (PCEF) which network events must send a new Credit-Control Response (CCR) to the Policy and Charging Rules Function (PCRF) for a possible policy change. Each event trigger has a string value name and an associated non-negative integer value.
  - Spending Limit Configuration
    Configure the spending limit control components when using a Policy and Charging Rules Function (PCRF) or Policy Control Function (PCF) that is external to MATRIXX Engine. For 5G MATRIXX environments, the spending limit control configuration reference point (N28) is located between your external PCF and MATRIXX Engine as a Charging Function (CHF). For 3G/4G environments, the spending limit control configuration reference point (Diameter Sy) is located between an external PCRF and MATRIXX Engine as an OCS.
    - Spending Limit Policy Components
      A spending limit policy component implements the business logic that decides which counter status to return to the Policy and Charging Rules Function (PCRF) (3G/4G) or Policy Control Function (PCF) (5G) for a given set of circumstances. Pricing administrators define the business rules and decisions by creating policy tables inside the policy counter components.
      - Create a Spending Limit Policy Component
        A policy component implements the business logic that decides which policy to apply for a given set of circumstances. It consists of one or more policy tables.
      - Configure Spending Limit Policy Table General Properties
        Perform this task to configure spending limit policy table general properties.
      - Add Data Modify Details to a Policy Table
        Add metadata and the default data modify profile to a spending limit policy table on the Data Modify tab in the Edit Spending Limit Policy Table pane.
      - Change a Spending Limit Policy Component
        You can change any aspect of a spending limit component, including service type, policy tables, decision tables, and normalizers.
      - Create a Revision of an Spending Limit Policy Component
        A new revision of a policy component creates a new copy of a selected revision or version. The operation does not create a new pricing file in the pricing plan.
      - Delete a Spending Limit Policy Component
        Deleting a Spending Limit component removes it from the pricing plan.
      - Spending Limit Policy Component Properties
        Use the Edit Spending Limit Policy Component tab of the Spending Limit Policy Components interface to change spending limit components general properties.
      - Spending Limit Policy Table Properties
        Use the Edit Spending Limit Policy Table interface to edit spending limit policy table properties listed in policy_mgmt/r_spending_limit_policy_table_props.html#reference_zp1_35h_rtb__table_4F5FD62E024349A28379789F1547F2F5.
    - Spending Limit Policy Counters
      Spending limit policy counters represent the information that can be returned to the _glossary/pcrf.html (3G/4G) or PCF (5G) by MATRIXX Policy Application during a session.
    - Spending Limit Policy Profiles
      Spending limit policy profiles specify the policy counter status when a profile is selected in a policy session.
    - Spending Limit Policy Templates
      Spending limit policy templates define the basic rules for a spending limit instance. Each template identifies the counters that are associated with the policy profiles created in the template.
  - Session Management Policy Configuration
    The Gx session management policy reference point is located between a Policy and Charging Enforcement Function (PCEF) and the Policy and Charging Rules Function (PCRF) internal to MATRIXX.
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Spending Limit Policy Component Properties

Use the Edit Spending Limit Policy Component tab of the Spending Limit Policy Components interface to change spending limit components general properties.

Spending Limit Component Properties lists the spending limit component properties.

Table 1. Spending Limit Component Properties
Property	Description
Name	A descriptive name of the policy component.
Description	Information about the purpose of the policy component.
External ID	(Optional) Use this field to identify this item in MATRIXX pricing items. An External ID is saved to the pricing configuration file and loaded into the Pricing Database. Set the External ID value to any alphanumeric character that is meaningful to your implementation. An External ID can be used, for example, to relate offers in the MATRIXX system to products in an external pricing plan. It can be used, for example, by the Subscriber Management API to query and purchase product offers and bundle IDs.
Start Date	The date that the policy component is available in the system. You must provide a start date for the first version of a policy component that exists in a pricing plan. Revisions to the component do not require a start date. You can use a future start date to create a revisions to a policy component that become active at the specified time, without having to redeploy the pricing plan for each revision.