Home
MATRIXX Policy
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.
Spending-Status-Notification Command Request
This section describes the Sy application Spending-Status-Notification command Request AVPs.

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
- 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 MATRIXX Policy Application provides the business logic and integration into a third-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 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 session management and spending limit configuration.
- 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. Policy profiles are collected for Sy and N28 policy counters, Gx command-level QoS, and N40 TIME_LIMIT and VOLUME_LIMIT usage triggers.
- Policy Processing Based on Quota Action
  You can configure a product offer so that Spending Limit Control/Sy policy components and Session Management/Gx components are applied when quota is authorized or denied.
- Spending Limit Policy Counter APIs
  The Sy policy counter APIs include MtxRequestDeviceEvaluatePolicyCounterSet and MtxRequestDeviceQuerySession.
- 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.
    - Spending-Limit Command Request
      This section describes the Sy application Spending-Limit command Request AVPs.
    - Spending-Limit Command Answer
      This section describes the Sy application Spending-Limit command Answer AVPs.
    - Session-Terminate Command Request
      This section describes the Sy application Session-Terminate command Request AVPs.
    - Session-Terminate Command Answer
      This section describes the Sy application Session-Terminate command Answer AVPs.
    - Spending-Status-Notification Command Request
      This section describes the Sy application Spending-Status-Notification command Request AVPs.
    - Spending-Status-Notification Command Answer
      This section describes the Sy application Spending-Status-Notification command Answer AVPs.
  - Gx Interface
    This section lists the Gx interface AVPs by command name.
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
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Spending-Status-Notification Command Request

This section describes the Sy application Spending-Status-Notification command Request AVPs.

Command details:

Command name: Spending-Status-Notification
Code: 8388636
Proxiable: True
MDC name:MtxDiamSySNMsg

Note: Unless otherwise noted, all AVPs are required and the maximum occurrence is "1".

Table 1. Spending-Status-Notification Request
AVP Name	AVP Code	MDC Field Name (Struct Name)	Description
Session-Id	263	SessionId
Origin-Host	264	SourceHost
Origin-Realm	296	SourceRealm
Destination-Realm	283	DestinationRealm
Destination-Host	293	DestinationHost
Auth-Application-Id	258	AuthApplicationId	In a Gx RAR, the AuthApplicationId = 16777238.
DRMP	301	DiamRoutingMsgPriority
Origin-State-Id	278	SourceStateId
OC-Supported-Features	621	OcSupportedFeatures (MtxDiamOcSupportedFeaturesData)
-- OC-Feature-Vector	622	-- OcFeatureVector
Policy-Counter-Status-Report	2903	PolicyCounterStatusList (MtxPolicyCounterStatusData)	Maximum occurs = 256
-- Policy-Counter-Identifier	2901	-- Id
-- Policy-Counter-Status	2902	-- Status
-- Pending-Policy-Counter-Information	2905	-- PendingPolicyCounterList (MtxPendingPolicyCounterData)	Maximum occurs = 256
-- -- Policy-Counter-Status	2902	-- -- PolicyCounterStatus
-- -- Pending-Policy-Counter-Change-Time	2906	-- -- PendingPolicyCounterChangeTime
SN-Request-Type	2907	DiamSySNRequestType
Proxy-Info	284	ProxyInfoList (MtxDiamProxyInfoData)	Maximum occurs = 256
-- Proxy-Host	280	-- ProxyHost
-- Proxy-State	33	-- ProxyState
Route-Record	282	RouteInfoList	Maximum occurs = 256
MtxTrafficRouteData	22	TrafficRouteData