Gxx AVPs
Gxx (application id: 16777266)
Gxx interface facilitates communication between the Policy and Charging Rules Function (PCRF) and the Bearer Binding and Event Reporting Function (BBERF). The Gxx interface is particularly important in scenarios involving Access Network Gateways, such as the Serving Gateway (S-GW) in LTE networks, or in trusted non-3GPP access networks.
BBERF is implemented within the Access Network Gateway, such as the S-GW in LTE networks or a similar gateway in non-3GPP networks. The BBERF enforces the QoS policies and charging rules received from the PCRF, managing bearer binding and reporting events related to bearer management, such as establishment, modification, and release.
In a non-roaming scenario, the PCRF directly communicates with the BBERF within the same network. The Gxx interface is used to enforce policies based on the decisions made by the PCRF.
In the Roaming with Home Routed Access scenario, the V-PCRF (Visiting PCRF) in the visited network communicates with the H-PCRF (Home PCRF) in the home network. The H-PCRF makes the policy decisions, and the Gxx interface is used to enforce these decisions at the BBERF in the visited network.
In the Roaming with Visited Access scenario, the V-PCRF in the visited network is responsible for making policy decisions. The Gxx interface in the visited network is used to enforce the policies locally.
Gxx interface workflow
Session Initialization:
- When a user initiates a session, the PCRF determines the necessary QoS policies based on input from the Application Function (AF) and user subscription data. These policies are communicated to the BBERF via the Gxx interface.
QoS Rule Provisioning:
- The PCRF sends QoS rules to the BBERF using the Gxx interface. The BBERF enforces these rules by applying them to the relevant bearers, ensuring that the session's traffic adheres to the specified QoS parameters.
Bearer Binding:
- The BBERF binds the bearers to the appropriate QoS rules as instructed by the PCRF. This binding ensures that the traffic for each session is managed according to the specified policies.
Event Reporting:
- The BBERF reports significant events, such as the establishment, modification, or release of bearers, to the PCRF via the Gxx interface.
Session Modification:
- If there are changes in the session requirements (e.g., an upgrade in service quality), the PCRF sends updated QoS rules to the BBERF via the Gxx interface.
Session Termination:
- When the session ends, the PCRF instructs the BBERF to release the resources associated with the session and stop enforcing the QoS rules.
For complete technical specification of Gxx interface in Diameter protocol please refer to: [3GPP TS 29.212]
package com.mobius.software.telco.protocols.diameter.primitives.gxx
|
Name |
AVP Code |
Data Type |
Vendor |
|
QoS-Rule-Base-Name |
1074 |
UTF8String |
3GPP |
|
Used to specify the name of a pre-defined group of Quality of Service (QoS) rules stored at the Bearer Binding and Event Reporting Function (BBERF). It allows referencing a collection of QoS rules without having to explicitly list each rule individually. |
|||
|
QoS-Rule-Definition |
1053 |
Grouped |
3GPP |
|
Defines a QoS rule for a service data flow. It is sent by the Policy and Charging Rules Function (PCRF) to the Bearer Binding and Event Reporting Function (BBERF) to manage and enforce QoS policies for specific flows. The AVP structure is defined as follows: QoS-Rule-Name (OctetString): Uniquely identifies the QoS rule within a Gateway Control session between the PCRF and BBERF. Flow-Information (Grouped): Describes the traffic flow parameters that define the service data flow. Multiple instances can be specified, replacing previous flow information if updated. Contains:
QoS-Information (Grouped): Provides specific QoS parameters for the rule, such as: Guaranteed Bitrate (GBR) for uplink and downlink. Maximum Bitrate (MBR) for uplink and downlink.
Precedence (Unsigned32): Defines the priority level for enforcing QoS rules. Lower values indicate higher priority. Required-Access-Info (Enumerated): Specifies whether user access network information is required by the Application Function (AF). Values:
Sharing-Key-DL (Unsigned32): Identifies a downlink resource sharing key for grouping flows that share the same QoS resources. Sharing-Key-UL (Unsigned32): Identifies an uplink resource sharing key for shared QoS enforcement. Content-Version (Unsigned32): Tracks the version of the QoS rule content to synchronize updates and modifications. |
|||
|
QoS-Rule-Install |
1051 |
Grouped |
3GPP |
|
Used to activate, install, or modify Quality of Service (QoS) rules as instructed by the PCRF to the BBERF. It supports dynamic QoS management and configuration for service flows. This AVP enables operations such as adding, modifying, or activating QoS rules, specifying tunnel information, defining charging identifiers, and managing activation and deactivation schedules for QoS enforcement. The AVP structure is defined as follows: QoS-Rule-Definition (Grouped): Defines the QoS rule parameters, including flow information, precedence, and sharing keys. Contains:
QoS-Rule-Name (OctetString): References a predefined QoS rule at the BBERF for activation. Multiple instances can be specified. QoS-Rule-Base-Name (UTF8String): References a group of predefined QoS rules at the BBERF for bulk activation. Tunnel-Information (Grouped): Describes tunnel header information for the associated QoS rules. Contains:
Access-Network-Charging-Identifier-Value (OctetString): Provides a charging identifier for correlation with PCC rules. Resource-Allocation-Notification (Enumerated): Indicates whether resource allocation confirmation is required for the specified rules. Value:
Rule-Activation-Time (Time): Specifies the start time for QoS rule enforcement based on NTP time. Rule-Deactivation-Time (Time): Specifies the end time for QoS rule enforcement based on NTP time. 3GPP-GGSN-Address (Address): IPv4 address of the GGSN (Gateway GPRS Support Node) for QoS enforcement. 3GPP-GGSN-Ipv6-Address (Address): IPv6 address of the GGSN for QoS enforcement. AN-GW-Address (Address): Address of the Access Network Gateway (ANGW) used in the session. Up to two instances allowed. UDP-Source-Port (Unsigned32): Specifies the UDP source port number for trusted S2c cases or NAT traversal scenarios. If no new sub-AVPs (e.g., Tunnel-Information) are provided during modification, previous values remain valid. |
|||
|
QoS-Rule-Name |
1054 |
OctetString |
3GPP |
|
Used to uniquely identify a Quality of Service (QoS) rule within a Gateway Control session or within the BBERF for predefined rules. It serves as a key identifier to activate, reference, or modify specific QoS rules. |
|||
|
QoS-Rule-Remove |
1052 |
Grouped |
3GPP |
|
Used to deactivate or remove specific QoS rules within a Gateway Control session. It allows the PCRF (Policy and Charging Rules Function) to manage QoS rule lifecycles by referencing the rules that need to be modified or deleted. This AVP is crucial in scenarios requiring dynamic updates to QoS policies, such as user session termination, service changes, or resource optimization. The AVP structure is defined as follows: QoS-Rule-Name (1054, OctetString): Uniquely identifies a specific QoS rule to be removed. Can reference rules predefined at the BBERF (Bearer Binding and Event Reporting Function) or dynamically provisioned by the PCRF. QoS-Rule-Base-Name (1074, UTF8String): References a group of predefined QoS rules at the BBERF to be deactivated. Allows bulk rule deactivation based on pre-configured groupings. Required-Access-Info (1092, Enumerated): Indicates if access network information is required by the PCRF when removing the QoS rules. Enumerated Values:
|
|||
|
QoS-Rule-Report |
1055 |
Grouped |
3GPP |
|
Used to report the status of QoS rules within a Gateway Control session. It provides detailed feedback on whether a QoS rule or group of rules has been successfully installed, modified, activated, deactivated, or removed, or if the rule failed to be enforced along with the reason for the failure. This AVP is essential for monitoring QoS rule enforcement and troubleshooting rule application issues. It supports dynamic updates and reporting capabilities, ensuring accurate communication between the BBERF and PCRF. The AVP structure is defined as follows: QoS-Rule-Name (1054, OctetString): Identifies a specific QoS rule to be reported. Can reference both dynamic rules and predefined rules at the BBERF. QoS-Rule-Base-Name (1074, UTF8String): References a group of predefined QoS rules at the BBERF. Used for reporting the status of multiple rules as a group. PCC-Rule-Status (1017, Enumerated): Specifies the current status of the QoS rule. Enumerated Values:
Rule-Failure-Code (1031, Enumerated): Provides the reason for a failure to install, activate, or enforce a QoS rule. Enumerated Values:
Content-Version (1056, Unsigned32): Specifies the content version for the QoS rule if versioning is supported. Used to ensure version consistency during rule modifications or installations. |
|||
|
Session-Linking-Indicator |
1064 |
Enumerated |
3GPP |
|
Used to control the linking behavior between a Gateway Control Session and an existing Gx session. It is sent by the PCRF to indicate whether the session linking process should be performed immediately or deferred. In scenarios where this AVP is absent, the default behavior is SESSION_LINKING_IMMEDIATE. This ensures compatibility with existing implementations while allowing flexibility in session handling. Enumerated Values: SESSION_LINKING_IMMEDIATE (0): Indicates that the PCRF should immediately link the new Gateway Control Session with an existing Gx session. SESSION_LINKING_DEFERRED (1): Specifies that the PCRF should defer the linking process for the new Gateway Control Session. Useful in cases where temporary isolation of sessions is needed for validation or resource preparation before linking. Behavior notes:
|
|||
Start innovating with Mobius
What's next? Let's talk!