Name

AVP Code

Data Type

Vendor

Aggregated-Congestion-Info

4000

Grouped

3GPP

Used for network congestion control in Diameter-based applications. It aggregates information about user identifiers (IMSI) and optionally includes a congestion location identifier to specify where these users are located. 

The AVP structure is defined as follows:

Congestion-Location-Id: Identifies the location experiencing congestion, such as a cell, network node, or area.

IMSI-List: A list of IMSI values representing affected users in the congested area.

Allows inclusion of additional AVPs for extensibility.

Aggregated-RUCI-Report

4001

Grouped

3GPP

Used to report congestion levels for a set of users sharing the same Policy and Charging Rules Function (PCRF) for the same PDN ID. It allows tracking and enforcement of congestion control policies by grouping users based on their IMSI and PDN ID, while providing the congestion level value or a congestion level set identifier to define network behavior.

The AVP structure is defined as follows:

Aggregated-Congestion-Info (Mandatory): Contains congestion information, such as the IMSI list and location IDs of affected users.

Called-Station-Id (Optional): Provides the PDN ID associated with the reported congestion.

Congestion-Level-Value (Optional): Indicates the current congestion level for the user group if no prior restriction was provided.

Congestion-Level-Set-Id (Optional): Specifies the congestion level set identifier for pre-configured restrictions between PCRF and RCAF.

Allows additional AVPs for future extensibility.

Conditional-Restriction

4007

Unsigned32 (Bitmask)

3GPP

Used to specify conditional reporting restrictions in Diameter messages. Each bit in the mask represents a specific restriction. The least significant bit (bit 0) defines whether User Equipment (UE) location information should be excluded from RUCI reports.

This AVP is primarily used in congestion reporting or QoS enforcement scenarios where certain data (e.g., UE location) should be omitted for privacy, optimization, or compliance purposes.

0 UE_LOCATION_INFO_NOT_INCLUDED_IN_RUCI: Indicates that UE location information should not be included in the RUCI report.

Congestion-Level-Definition

4002

Grouped

3GPP

Defines a congestion level set along with corresponding congestion levels to be used by the RCAF (Resource Control and Admission Function) for a specific user ID and PDN ID during congestion reporting. When included in the MUR (Modify User Request) command, it specifies reporting restrictions for congestion levels.

If absent, no restrictions apply to the user ID and PDN ID.

The AVP structure is defined as follows:

Congestion-Level-Set-Id: Unique identifier for the congestion level set associated with the user ID and PDN ID.

Congestion-Level-Range: Specifies the range of congestion levels applicable for the defined set.

Optional AVPs can be added based on implementation-specific extensions or future standards.

Congestion-Level-Range

4003

Unsigned32 (Bitmask)

3GPP

Defines a bitmask used to indicate congestion levels bound to a specific congestion level set between the PCRF (Policy and Charging Rules Function) and the RCAF (Resource Control and Admission Function). It specifies congestion levels applicable to a particular user ID and PDN ID. Each bit corresponds to a specific congestion level, starting with bit 0 for no congestion and incrementing for higher congestion levels. Assumes no congestion reporting if the AVP is absent. Supports bitmask values for congestion levels 0–31 (32 levels maximum).

Bitmask Definitions

0 - No congestion: Reports the congestion level set ID when there is no congestion.

1 - Congestion level 1: Reports the congestion level set ID when level 1 congestion is reached.

1+n - Congestion level 1+n: Reports the congestion level set ID when level 1+n congestion occurs.

Congestion-Level-Set-Id

4004

Unsigned32

3GPP

Uniquely identifies a congestion level set between the PCRF (Policy and Charging Rules Function) and the RCAF (Resource Control and Admission Function). It is used to track congestion state mappings between PCRF and RCAF for specific user IDs and PDN IDs.

The identifier acts as a reference for applying congestion control policies based on predefined congestion level ranges. Assumes no congestion reporting if the AVP is absent.

Congestion-Level-Value

4005

Unsigned32

3GPP

Used to indicate the congestion level associated with a specific user ID and PDN ID. It helps manage network congestion by providing an integer value that represents the severity of congestion for a given user or service.

Congestion Level Values:

0 - No congestion: No congestion detected.

1–31 - Congestion levels: Indicates congestion severity (1 = lowest, 31 = highest).

Congestion-Location-Id

4006

Grouped

3GPP

Used to identify the location of congestion affecting a specific user equipment (UE). It defines the congested area in which the UE is currently located, such as an eNodeB, an E-UTRAN cell, or a Service Area. Must include eNodeB-Id or Extended-eNodeB-Id when 3GPP-User-Location-Info is absent.

The AVP structure is defined as follows:

3GPP-User-Location-Info: Provides location details of the UE, including cell ID and tracking area code (TAC).

eNodeB-Id: Contains the 18-bit or less identifier for the eNodeB serving the UE.

Extended-eNodeB-Id: Contains the 19-21 bit identifier for the eNodeB in cases where longer IDs are used.

eNodeB-Id

4008

OctetString

3GPP

Identifies the eNodeB (Evolved Node B) where the User Equipment (UE) is currently located. It is primarily used in scenarios involving congestion management, location-based services, and mobility management in LTE and 5G networks. The AVP is encoded as specified in clause 8.51 of 3GPP [TS 29.274].

Encoding Format: OctetString: Encoded as 4 octets or 21 bits depending on whether it is an eNodeB-ID or Extended-eNodeB-ID.

Cannot be combined with Extended-eNodeB-Id: Use Extended-eNodeB-Id only for 18-21 bit identifiers.

Extended-eNodeB-Id

4013

OctetString

3GPP

Identifies the eNodeB (Evolved Node B) where the User Equipment (UE) is currently located, specifically supporting Extended Macro eNodeB identifiers. It provides compatibility for networks that utilize 18-bit or 21-bit identifiers required for extended eNodeB formats. This AVP is encoded as specified in clause 8.51 of 3GPP [TS 29.274].

Encoding Format: OctetString: Encoded as 5 octets for 18- or 21-bit identifiers.

Must be included when reporting Extended eNodeB IDs.

Cannot be present alongside eNodeB-Id within the same message.

IMSI-List

4009

OctetString

3GPP

Contains a list of User IDs identified by IMSI (International Mobile Subscriber Identity) values. Each IMSI is encoded using TBCD (Telephony Binary Coded Decimal) digits as defined in ITU-T Recommendation [E.212]. This encoding supports up to 15 digits for each IMSI, with special padding rules for 14- or 15-digit values.

The IMSI-List AVP allows multiple IMSIs to be grouped together for processing in scenarios such as congestion management, user mobility tracking, and reporting.

Encoding Format:

Each IMSI is encoded as 8 octets using TBCD encoding:

Digits 0–9 → Encoded as "0000" to "1001" (4-bit nibble).

Odd-length IMSIs: Padded using 1111 in the unused nibble.

14-digit IMSI: Last octet padded with 1111 1111.

15-digit IMSI: Final nibble padded as 1111.

Example Encoding for Multiple IMSIs:

123456789012345 (15) 21 43 65 87 09 21 43 F5

98765432109876 (14) 79 56 34 12 90 87 65 FF

112233445566778 (15) 11 22 33 44 55 66 77 F8

RCAF-Id

4010

DiameterIdentity

3GPP

Used to represent the Routing and Congestion Awareness Function (RCAF) identity. It uniquely identifies the RCAF entity involved in congestion management and policy enforcement within the network.

Reporting-Restriction

4011

Enumerated

3GPP

Specifies the reporting restrictions applicable between the PCRF (Policy and Charging Rules Function) and the RCAF (Routing and Congestion Awareness Function). This AVP determines whether congestion reporting should follow conditional, unconditional, or no restrictions. Cannot be used with Congestion-Level-Definition AVP in the same message.

Enumerated Values

0 - No Reporting Restriction: Indicates no restrictions on congestion reporting for a specific user and PDN ID.

1 - Conditional Reporting Restriction: Imposes conditional restrictions based on specific criteria (e.g., thresholds, rules).

2 - Unconditional Reporting Restriction: Imposes strict, unconditional restrictions, prohibiting any congestion reporting.

RUCI-Action

4012

Enumerated

3GPP

Specifies whether RUCI (Radio Usage Congestion Information) reporting between the PCRF (Policy and Charging Rules Function) and the RCAF (Routing and Congestion Awareness Function) should be enabled, disabled, or released for a specific user ID and PDN ID. If AVP is not provided, no RUCI action is assumed (depends on prior configurations).

Enumerated Values

0 - Disable RUCI Reporting: Disables RUCI reporting for a specific user and PDN ID, preventing further data transmission.

1 - Enable RUCI Reporting: Enables RUCI reporting, allowing data exchange between the PCRF and RCAF.

2 - Release Context: Releases the RUCI context, effectively terminating the session for the specified user and PDN ID.