Policy Rule Variables for Rx Requests

In addition to the basic policy rule variables, you can use the following request variables defined for the Diameter Rx protocol to get charging-related information.

Variable Name
Description
{Request.ChargingCharacteristics}
Wireless
Replaced with a six-octet string containing (in octets 3–6) the application-based charging characteristics for the IP-CAN bearer. Corresponds to the field 3GPP-Charging-Characteristics of the 3GPP vendor-specific attribute defined in 3GPP TS 29.061. The AVP has the M bit cleared.
{Request.​​​CreditManagementStatusMask}
Wireless
Replaced with an unsigned 32-bit mask representing the credit management status for application-based charging. Corresponds to the field Credit-Management-Status defined in 3GPP TS 29.212. Bit 0 is the least significant bit. When set, the bit values indicate:
  • 0 — END_USER_SERVICE_DENIED (0x1): The charging system denied the service request (for example, to terminate a rating group) due to service restrictions or limitations related to the end user (for example, the end-user's account could not cover the requested service).
  • 1 — CREDIT_CONTROL_NOT_APPLICABLE (0x2): The charging system determined that the service can be granted to the end user but no further credit control is needed for the service (for example, the service is free of charge or is treated for offline charging).
  • 2 — AUTHORIZATION_REJECTED (0x4): The charging system denied the service request in order to terminate the service for which credit is requested.
  • 3 — USER_UNKNOWN (0x8): The specified end user could not be found in the charging system.
  • 4 — RATING_FAILED (0x16): The charging system cannot rate the service request due to insufficient rating input, incorrect AVP combination, or an AVP value that is not recognized or supported in rating.
  • 5 — NO_GYN_SESSION_SERVICE_ALLOWED (0x20): The Gyn session was terminated (for example, because of network failure), but the OCS allowed the service to continue. Applicable only over Sd reference point.
  • 6 — NO_GYN_SESSION_SERVICE_NOT_ALLOWED (0x40): The Gyn session was terminated (for example, because of network failure) and the OCS did not allow the service to continue. Applicable only over Sd reference point.
{Request.DynamicAddressFlag}
Wireless
Replaced with an integer indicating whether the PDP context/PDN address is statically (0) or dynamically (1) allocated. Corresponds to the field Dynamic-Address-Flag defined in 3GPP TS 32.299. If the AVP is not present, the address is statically allocated.
{Request.​DynamicAddressFlagExtension}
Wireless
Replaced with a boolean value indicating whether the IPv4 PDN address is statically (0) or dynamically (1) allocated for that particular IP-CAN bearer (PDN connection) of PDN type IPv4v6. Corresponds to the field Dynamic-Address-Flag-Extension defined in 3GPP TS 32.299. If the address is in IPv6 format and dynamically allocated, it is indicated in Dynamic Address Flag. This field is missing if the IPv4 address is static.
{Request.GgsnAddress3GPP}
Wireless
Replaced with a six-octet value containing the GGSN address in IPv4 format. Corresponds to the field 3GPP-GGSN-Address defined in 3GPP TS 29.061. The AVP has the M bit cleared.
{Request.GgsnIPv6Address3GPP}
Wireless
Replaced with an 18-octet value containing the GGSN address in IPv6 format. Corresponds to the field 3GPP-GGSN-IPv6-Address defined in 3GPP TS 29.061. The AVP has the M bit cleared.
{Request.PdnConnectionChargingID}
Wireless
Replaced with an unsigned 32-bit value containing the charging identifier to identify different records belonging to same PDN connection. Includes the Charging ID of the first IP-CAN bearer activated within the PDN connection (the EPS default bearer for GTP-based connectivity or the unique Charging ID for PMIP-based connectivity). Corresponds to the field PDN-Connection-Charging-ID defined in 3GPP TS 32.299. The AVP has the M bit cleared.
{Request.SelectionMode3GPP}
Wireless
Replaced with an integer representing whether this service data flow or bearer can get resources that were already assigned to another service data flow with a lower priority level:
  • 0 — MS or network provided APN, subscription verified
  • 1 — MS provided APN, subscription not verified
  • 2 — Network provided APN, subscription not verified
  • 3 — Reserved for future use, not sent; if received interpreted as 2
Corresponds to the field 3GPP-Selection-Mode defined in 3GPP TS 29.061. The AVP has the M bit cleared.
{Request.UserCSGInformation.​CSGAccessMode}
Wireless
Replaced with an integer representing information on how the user is accessing a closed subscriber group cell:
  • 0 — Closed mode
  • 1 — Hybrid mode
Corresponds to the AVP CSG-Access-Mode of the field User-CSG-Information defined in 3GPP TS 32.299.
{Request.UserCSGInformation.​CSGId}
Wireless
Replaced with a value representing the user's closed subscriber group identifier. Corresponds to the AVP CSG-Id of the field User-CSG-Information defined in 3GPP TS 32.299.
{Request.UserCSGInformation.​CSGMembershipIndication}
Wireless
Replaced with an integer representing whether or not the user is a member of a closed subscriber group cell in hybrid mode:
  • 0 — Not CSG member
  • 1 — CSG member
Corresponds to the AVP CSG-Membership-Indication of the field User-CSG-Information defined in 3GPP TS 32.299.