Home
MATRIXX Policy
3G/4G Policy Configuration
Policy configuration in My MATRIXX includes both session management and spending limit configuration.
Session Management Policy Configuration
MATRIXX Policy Application for Gx monitors normalized subscriber parameters and indicates which policies should be applied in one or more Policy and Charging Enforcement Functions (PCEFs).
Returning Network Location Information
The MATRIXX Policy Application can return network location information captured by the packet core. You can configure MATRIXX Policy Application to check if the policy session supports NetLoc before sending a request for access network information.

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.
  - Session Management Policy Configuration
    MATRIXX Policy Application for Gx monitors normalized subscriber parameters and indicates which policies should be applied in one or more Policy and Charging Enforcement Functions (PCEFs).
    - Look Ahead Window for Session Management Policies
      You use a policy look ahead window to determine if any Gx policy changes occur after the current policy period. By default, policy look ahead is configured and set to 24 hours.
    - Returning Network Location Information
      The MATRIXX Policy Application can return network location information captured by the packet core. You can configure MATRIXX Policy Application to check if the policy session supports NetLoc before sending a request for access network information.
    - Policy Rule Installation Failure Handling
      By default, MATRIXX Policy Application ignores Gx policy rule installation failures on the PCEF.
    - Rx Session Retention
      Out-of-the-box, when a Gx Session fails, the PCRF initiates termination of an associated Rx session by sending an Rx ASR to the AF.
  - Spending Limit Control Policy Configuration
    MATRIXX Policy Application monitors balance ranges from balance normalizers. A policy is rechecked when balances are updated or when any attribute of a subscriber or device is updated. MATRIXX Policy Application is optimized to detect if a balance update affects a policy.
  - Session Management RAR and Spending Limit SNR Messages
    Gx RARs are sent to the Policy and Charging Enforcement Function (PCEF) or Sy SNRs are sent to the Policy and Charging Rules Function (PCRF) when MATRIXX Policy Application determines that there has been a policy change.
  - Gy Re-Auth-Request (RAR) Message
    MATRIXX Engine sends a Re-Auth Request (RAR) to the network for a subscriber-management (SubMan) request, when an open session is perceived as inactive, or on content quota expiration.
  - Sh Repository Configuration
    When using the Sh protocol, the PCRF sends an Sh SNR. MATRIXX Engine assumes one active Sh subscription per device, consisting of one Sh SNR per subscription (with the same Session-Id). If a subscription is already active, a second Sh SNR for that same subscription is handled as a duplicate of the original, while an SNR for a different subscription logs a warning and replaces the current one. Re-using the Session-Id of a currently-inactive subscription activates a new subscription with that same ID.
- 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.
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

Returning Network Location Information

The MATRIXX Policy Application can return network location information captured by the packet core. You can configure MATRIXX Policy Application to check if the policy session supports NetLoc before sending a request for access network information.

The AF can subscribe to the ACCESS_NETWORK_INFO_REPORT in the Specific-Action AVP to request that the PCRF report access network information (such as user location or user time zone information). The type of required access network information is indicated in the Required-Access-Info AVP. The AF can request the ACCESS_NETWORK_INFO_REPORT at any time in an Rx AA-Request (AAR) and the PCRF provides the requested details in a Rx Re-Auth-Request (RAR).

Figure 1 shows a typical successful message sequence.

access-network-info-request results in access-network-info-report — Figure 1. Successful Message Sequence

To request access network information, the Specific-Action AVP must be set to the enumerated value ACCESS_NETWORK_INFO_REPORT (12) to indicate a one time specific action. One time specific actions are reported after the required action is fulfilled and are not reported again unless the AF sends a new request.

The Required-Access-Info identifies the type of access network information required by the AF with one of the following values.

USER_LOCATION (0)
MS_TIME_ZONE (1)

The information returned is determined by Policy and Charging Control (PCC); 3gpp 29.212 R15.

A PCEF might return a failure indication if the session does not support the information required as described in Policy and charging control over Rx reference point; 3GPP TS 29.214 R15

For more information, see the 3GPP documentation.

The Supported-Feature AVP supplied by the PCEF in the CCR indicates if NetLoc is supported. An Rx AAR containing a request for access network information is permitted only if NetLoc is supported. If your implementation does not use NetLoc, disable the compatibility check by answering n to the following create_config.info question so that the access network information request is forwarded to the PCEF.

create_config.info question: Global:Session:Application:Notify:Check the policy session supports the NetLoc feature before sending a request for access network information?

Figure 2 shows a typical sequence where the request is unsupported using an Rx AAR.

NETLOC_ACCESS_NOT_SUPPORTED — Figure 2. Unsupported Message Request