Home
MATRIXX Policy
Diameter AVPs for MATRIXX Policy Application
MATRIXX Engine supports the Sy and Gx interfaces for policy control.

Welcome
Release Notes
Architecture Overview
MATRIXX Cloud Native Installation and Configuration
MATRIXX Cloud Native Integration
Implementing MATRIXX in a Cloud
Installation and Configuration
MATRIXX Digital Commerce Upgrade
MATRIXX Security
MATRIXX Engine Administration
MATRIXX Web App Administration
MATRIXX Engine Integration
Call Control Framework Integration
MATRIXX Diameter Integration
MATRIXX 5G Integration
MATRIXX Monitoring and Logging
Pricing and Rating
MATRIXX Pay Now
MATRIXX Policy
- About MATRIXX Policy
  MATRIXX Policy describes the tasks that must be completed to configure MATRIXX Policy Application functionality and provides overviews, recommendations, and conceptual discussions to help you understand these tasks. In addition, it describes the supported Diameter policy AVPs and MATRIXX Policy Application SubMan APIs.
- 5G Policy Overview
  The 5G MATRIXX Policy Application provides the business logic and integration into a 3rd party policy control function (PCF) to support real-time policy decisions and rules. It enables your PCF to deliver flexible policy and charging control rules to your 5G network.
- 3G/4G Policy Overview
  The 3G/4G MATRIXX Policy Application runs on top of the Application module and provides the business logic to support real-time policy decisions and rules. It allows charging and network quality of service (QoS) to be flexibly and dynamically linked to customer, service, and network parameters.
- 3G/4G Policy Configuration
  Policy configuration in My MATRIXX includes both Gx and Sy configuration.
- 3G/4G Policy Session APIs
  The SubMan APIs include session query, session validation, and session delete APIs for charging and policy sessions.
- Sy Policy Counter APIs
  The Sy policy counter APIs include MtxRequestDeviceEvaluatePolicyCounterSet and MtxRequestDeviceQuerySession.
- 3G/4G MATRIXX Policy Failover
  A MATRIXX Policy failover can be due to a hard failure or can be planned.
- Policy Profile Selection
  During policy profile selection, product offers are evaluated in descending order from highest to lowest priority and policy profiles collected for Sy and N28 policy counters, Gx command-level QoS, and N40 TIME_LIMIT and VOLUME_LIMIT usage triggers.
- Diameter AVPs for MATRIXX Policy Application
  MATRIXX Engine supports the Sy and Gx interfaces for policy control.
  - Sy Interface
    This section lists the Sy interface AVPs by command name.
  - Gx Interface
    This section lists the Gx interface AVPs by command name.
MATRIXX Event Streaming
Subscriber Management
Subscriber Management (SubMan) API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
Third-Party Licenses
Glossary

Diameter AVPs for MATRIXX Policy Application

MATRIXX Engine supports the Sy and Gx interfaces for policy control.

The MATRIXX Diameter Dictionary is defined in the diameter_dictionary.xml file and contains definitions for the Diameter AVPs, functions, and Diameter-to-MDC mappings implemented in MATRIXX Engine.

Note: Most AVPs are mapped to an MDC field, but this is not required. If the AVP is not mapped, it will not be used during processing. One reason not to map an AVP to an MDC field is when the AVP is sent to MATRIXX Engine but it is not used during rating. The presence of the AVP makes it known to MATRIXX Engine, so an error message about an unknown AVP will not get logged. Another reason not to map an AVP is when it is in a Grouped AVP and is not used.

AVPs that are received by the Diameter Gateway but not specified in the appropriate <request> or <answer> section in the diameter_dictionary.xml file are logged as an error in the mtx_debug.log file.

Grouped AVPs are indented under their parent AVPs in the following tables.

Note: For more information about MATRIXX Engine Diameter support, see Diameter Integration.