Name

AVP Code

Data Type

Vendor

Access-Availability-Change-Reason

2833

Enumerated

3GPP

Used in the Gx interface to specify the reason for changes in the availability of an access network as determined by the PCEF (Policy and Charging Enforcement Function). It helps in signaling access availability events to the PCRF (Policy and Charging Rules Function), enabling policy adaptation based on network access conditions. Values:

0 Access stratum indication: Availability changed due to Access Stratum Indication (layer-specific event).

1 Access usable/unusable: Access is either unusable or has become usable again.

Access-Network-Charging-Identifier-Gx

1022

Grouped

3GPP

Used in the Gx interface between the PCEF (Policy and Charging Enforcement Function) and PCRF (Policy and Charging Rules Function). It carries charging-related identifiers to correlate charging sessions between the PCEF and AF (Application Function).

The AVP structure is defined as follows:

Access-Network-Charging-Identifier-Value: (1023, OctetString): Contains the charging identifier (e.g., GCID) assigned by the network.

Charging-Rule-Base-Name: (1003, UTF8String): List of base names associated with the PCC rules for this identifier.

Charging-Rule-Name: (1004, OctetString): List of specific rule names linked to the charging identifier.

IP-CAN-Session-Charging-Scope: (1005, Enumerated): Specifies the scope (entire session or bearer-specific).

Enumerated Values for IPCAN-Session-Charging-Scope:

0 Entire Session Scope: Applies to the entire IP-CAN session.

1 Default Bearer Scope: Limited to the default bearer only.

2 Dedicated Bearer Scope: Applies only to specific PCC rules within dedicated bearers.

Allocation-Retention-Priority

1034

Grouped

3GPP

Used to specify the priority level for resource allocation and retention in the Policy and Charging Control (PCC) architecture, particularly in QoS (Quality of Service) enforcement. The AVP structure is defined as follows:

Priority-Level: (1035, Unsigned32): Specifies the priority level for resource allocation (lower values indicate higher priority).

Pre-emption-Capability: (1036, Enumerated): Indicates whether the session can pre-empt other lower-priority sessions (default: disabled).

Pre-emption-Vulnerability: (1037, Enumerated): Indicates whether the session can be pre-empted by higher-priority sessions (default: enabled).

Enumerated Values for Pre-emption-Capability:

0 Enabled: Session can pre-empt others.

1 Disabled: Session cannot pre-empt others.

Enumerated Values for Pre-emption-Vulnerability:

0 Enabled: Session can be pre-empted.

1 Disabled: Session cannot be pre-empted.

AN-GW-Address

1050

Address

3GPP

Contains the control plane IP address (IPv4 and/or IPv6) of the Access Node Gateway (AN-GW). It applies to both 3GPP and non-3GPP access types:

3GPP Networks: Represents the SGW (Serving Gateway) address.

Non-3GPP Networks: Represents the AGW (Access Gateway) or ePDG (Evolved Packet Data Gateway) address.

AN-GW-Status

2811

Enumerated

3GPP

Used in the Gx interface and sent by the Policy and Charging Enforcement Function (PCEF) to the Policy and Charging Rules Function (PCRF) to indicate the status of the Access Node Gateway (AN-GW), such as the Serving Gateway (SGW) in 3GPP-EPS access types.

Values:

0 AN_GW_FAILED: Indicates that the AN-Gateway has failed. Notifies the PCRF to stop sending policy decisions to the PCEF until recovery of the AN-Gateway is reported.

This value is not used if the IP-CAN Session Modification procedure is initiated solely for PCC rule removal.

APN-Aggregate-Max-Bitrate-DL

1040

Unsigned32

3GPP

Specifies the maximum aggregate bit rate in bits per second for the downlink (DL) direction across all non-Guaranteed Bit Rate (non-GBR) bearers associated with the same Access Point Name (APN). This AVP is used to manage bandwidth allocation and enforcement for downlink traffic at the APN level in Diameter-based systems. It supports various use cases depending on its inclusion in Credit-Control Requests (CCR) or Credit-Control Answers (CCA). When the Extended-BW-NR feature is supported and the value exceeds 2^32-1, the Extended-APN-AMBR-DL AVP must be used instead. Refer to 3GPP [TS 29.212] subclauses 4.5.30 and 5.3.134 for details.

APN-Aggregate-Max-Bitrate-UL

1041

Unsigned32

3GPP

Specifies the maximum aggregate bit rate in bits per second for the uplink (UL) direction across all non-Guaranteed Bit Rate (non-GBR) bearers associated with the same Access Point Name (APN). This AVP is critical for managing bandwidth allocation and enforcing QoS policies for uplink traffic in Diameter-based systems. It serves as a control mechanism to ensure adherence to subscription limits and dynamically determined QoS configurations.

When the Extended-BW-NR feature is supported and the value exceeds 2^32-1, the Extended-APN-AMBR-UL AVP must be used instead. Refer to 3GPP [TS 29.212] subclauses 4.5.30 and 5.3.135 for details.

Application-Detection-Information

1098

Grouped

3GPP

Used to notify the start or stop of application traffic detected by the Traffic Detection Function (TDF). This AVP is sent to the Policy and Charging Rules Function (PCRF) when the PCRF has subscribed to the APPLICATION_START or APPLICATION_STOP event triggers. The AVP contains relevant information about the detected application, including its identifier, flow details, and instance-specific identifiers. It also supports scenarios where notifications are muted through the Mute-Notification AVP, as defined in the corresponding Charging-Rule-Definition AVP.

The AVP structure is defined as follows:

TDF-Application-Identifier (Required): Identifies the detected application traffic.

Unique for each application and used to map application-specific policies.

TDF-Application-Instance-Identifier (Optional): Specifies the instance of the application.

Included when the APPLICATION_START event is notified and must also be included for the corresponding APPLICATION_STOP event.

Flow-Information (Optional, Multiple): Provides details about the detected application flow(s).

Each Flow-Information AVP includes:

• Flow-Description AVP: Describes the IP flow characteristics.

• Flow-Direction AVP: Indicates the direction of the flow (uplink, downlink, or bidirectional).

Allows extensibility for vendor-specific attributes or additional parameters.

When the event trigger is APPLICATION_START, the Flow-Information AVP is included if the flow details are deducible.

The corresponding Event-Trigger (APPLICATION_START or APPLICATION_STOP) must also be provided to the PCRF.

If the Mute-Notification AVP is present in the associated charging rule, this AVP is not sent to the PCRF.

Bearer-Control-Mode

1023

Enumerated

3GPP

Specifies the bearer control mode selected by the PCRF, determining how bearer resources are established, modified, or terminated within a session. This AVP is crucial in defining the level of control exercised by the UE (User Equipment) or network nodes during bearer management.

Values:

0 UE_ONLY: The UE is solely responsible for bearer resource requests (establishment, modification, termination).

1 RESERVED: Reserved for future use. Not applicable in this release.

2 UE_NW: Both UE and PCEF can request bearer resource modifications (add, modify, remove traffic flows).

Bearer-Identifier

1020

OctetString

3GPP

Used to uniquely identify a bearer within an IP CAN session (IP Connectivity Access Network). It is specifically applicable to 3GPP-GPRS access types. The PCEF (Policy and Charging Enforcement Function) selects and assigns the bearer identifier during bearer creation.

Bearer-Operation

1021

Enumerated

3GPP

Specifies the bearer event that triggers a request for Policy and Charging Control (PCC) rules in a 3GPP-GPRS access network. This AVP is provided when the bearer event is initiated by the UE (User Equipment). Values:

0 TERMINATION: Bearer is being terminated.

1 ESTABLISHMENT: A new bearer is being established.

2 MODIFICATION: An existing bearer is being modified (QoS update, etc.).

Bearer-Usage

1000

Enumerated

3GPP

Used to specify how a bearer is being utilized in 3GPP-GPRS and 3GPP-EPS access types. When the Bearer-Usage AVP is absent, it implies no specific information about the bearer usage is available. If present, the value remains valid until updated. Values:

0 GENERAL: Indicates no specific bearer usage information is available.

1 IMS_SIGNALLING: Indicates the bearer is used exclusively for IMS signaling.

Charging-Correlation-Indicator

1073

Enumerated

3GPP

Specifies whether the Access-Network-Charging-Identifier-Gx AVP associated with dynamic PCC rules must be reported by the PCEF to the PCRF. Values:

0 CHARGING_IDENTIFIER_REQUIRED: The Access-Network-Charging-Identifier-Gx AVP must be reported.

Charging-Rule-Base-Name

1004

UTF8String

3GPP

Specifies the name of a predefined group of PCC (Policy and Charging Control) rules stored at the PCEF (Policy and Charging Enforcement Function).

Charging-Rule-Definition

1003

Grouped

3GPP

Defines a PCC (Policy and Charging Control) rule sent by the PCRF (Policy and Charging Rules Function) to the PCEF (Policy and Charging Enforcement Function). It specifies traffic flow handling, QoS settings, and charging parameters for an IP-CAN session.

The AVP structure is defined as follows: 

Charging-Rule-Name (Mandatory), (UTF8String): Uniquely identifies the rule within the session. Acts as a reference for updates and modifications.

Service-Identifier (Optional), (Unsigned32): Identifies the specific service associated with the rule, e.g., video streaming or VoIP.

Rating-Group (Optional), (Unsigned32): Groups flows for billing purposes based on service usage.

Flow-Information (Optional, Multiple), (Grouped): Describes IP flows based on flow descriptions (e.g., source/destination IP, ports, protocols). Used for traffic filtering and rule enforcement.

Default-Bearer-Indication (Optional), (Enumerated): Indicates whether the rule applies to the default bearer.

• 0: Bind to default bearer.

• 1: Independent bearer.

TDF-Application-Identifier (Optional), (OctetString): Associates the rule with a Traffic Detection Function (TDF) application.

Flow-Status (Optional): (Enumerated), Specifies whether flows are enabled or disabled:

• ENABLED (0)

• DISABLED (1)

• REMOVED (2)

QoS-Information (Optional), (Grouped): Defines Quality of Service (QoS) parameters for the PCC rule: Guaranteed and maximum bandwidth. Priority levels.

PS-to-CS-Session-Continuity (Optional), (Enumerated): Indicates whether the flow supports session continuity between Packet-Switched (PS) and Circuit-Switched (CS) networks.

Reporting-Level (Optional), (Enumerated): Defines the level at which traffic reporting is required:

• SESSION (0)

• BEARER (1)

• FLOW (2)

Online (Optional), (Enumerated): Specifies whether online charging is enabled for the rule.

Offline (Optional), (Enumerated): Specifies whether offline charging is enabled for the rule.

Max-PLR-DL/UL (Optional), (Unsigned32): Maximum Packet Loss Rate (PLR) for Downlink (DL) and Uplink (UL).

Metering-Method (Optional), (Enumerated): Defines the method for metering traffic usage:

• DURATION (0) – Measures session time.

• VOLUME (1) – Measures data volume.

Precedence (Optional), (Unsigned32): Rule priority relative to other rules. Lower values indicate higher priority.

AF-Charging-Identifier (Optional), (OctetString): Links the rule to a specific application for charging purposes.

Flows (Optional, Multiple), (Grouped): Contains additional flow filters and identifiers tied to this rule.

Monitoring-Key (Optional), (OctetString): Unique key for monitoring data usage associated with the rule.

Redirect-Information (Optional, Multiple), (Grouped): Provides redirect details such as URLs or IPs for traffic redirection.

Mute-Notification (Optional), (Enumerated): Controls notifications for rule updates:

• MUTE (0) – Suppresses updates.

• UNMUTE (1) – Allows updates.

AF-Signalling-Protocol (Optional), (Enumerated): Specifies the signaling protocol used by the Application Function (AF).

Sponsor-Identity (Optional), (UTF8String): Identifies the sponsor paying for the service or data usage.

Application-Service-Provider-Identity (Optional), (UTF8String): Identifies the service provider responsible for delivering the application.

Required-Access-Info (Optional, Multiple), (Enumerated): Requests access network information (e.g., RAT type or location).

Sharing-Key-DL/UL (Optional), (Unsigned32): Enables resource sharing for Downlink (DL) and Uplink (UL) flows.

Traffic-Steering-Policy-Identifier-DL/UL (Optional), (OctetString): Indicates specific routing policies for Downlink (DL) and Uplink (UL) traffic.

Content-Version (Optional), (Unsigned32): Specifies the version of content rules for consistency.

Calling-Party-Address (Optional, Multiple), (UTF8String): Contains the caller’s address for VoIP services.

Callee-Information (Optional), (Grouped): Provides information about the callee in a session, including identifiers and signaling info.

Validation Rules:

• Charging-Rule-Name must always be provided.

• Either Flow-Information or TDF-Application-Identifier must be present, not both.

• Precedence settings should not conflict with other rules.

Charging-Rule-Install

1001

Grouped

3GPP

Used to install, activate, or modify PCC rules (Policy and Charging Control rules) as instructed by the PCRF to the PCEF. It supports:

• Installing new PCC rules or modifying existing rules via Charging-Rule-Definition.

• Activating predefined rules in the PCEF using Charging-Rule-Name or Charging-Rule-Base-Name.

• Specifying bearer identifiers for rules bound to a specific IP CAN bearer.

• Setting activation and deactivation times for rules.

• Controlling monitoring actions, resource allocation notifications, and charging correlation identifiers.

The AVP structure is defined as follows:

Charging-Rule-Definition (Optional, Multiple), (Grouped): Contains the detailed definition of a PCC rule, including QoS settings, flow descriptions, and charging parameters. See the Charging-Rule-Definition AVP for its detailed structure.

Charging-Rule-Name (Optional, Multiple), (UTF8String): Specifies a predefined PCC rule name stored in the PCEF to be activated.

Charging-Rule-Base-Name (Optional, Multiple), (UTF8String): Refers to a group of PCC rules that are predefined at the PCEF and need to be activated collectively.

Bearer-Identifier (Optional), (OctetString): Indicates the bearer to which the PCC rules are bound. If omitted, the PCEF selects an appropriate bearer.

Monitoring-Flags (Optional), (Unsigned32): Defines the monitoring actions for data usage and flow tracking. The value applies to all rules within this AVP until updated.

Rule-Activation-Time (Optional), (Time): Specifies the time when the PCC rule(s) should be activated. Applied to all rules in this AVP.

Rule-Deactivation-Time (Optional), (Time): Specifies the time when the PCC rule(s) should be deactivated. Applied to all rules in this AVP.

Resource-Allocation-Notification (Optional), (Enumerated): Indicates whether the PCEF should notify about resource allocation changes for this rule:

• NOTIFY_ENABLED (0) – Notify on resource allocation changes.

• NOTIFY_DISABLED (1) – Do not notify on changes.

Charging-Correlation-Indicator (Optional), (Enumerated): Controls whether a charging identifier (e.g., GCID) should be reported to the PCRF:

• CHARGING_IDENTIFIER_REQUIRED (0) – Charging identifier is required.

IP-CAN-Type (Optional), (Enumerated): Identifies the IP-CAN access type used for data transfer:

• 3GPP-EPS (0)

• Non-3GPP-EPS (1)

Validation Rules:

• Either Charging-Rule-Definition, Charging-Rule-Name, or Charging-Rule-Base-Name must be specified.

• Bearer-Identifier should be provided if rules must be associated with specific bearers.

• If Rule-Activation-Time or Rule-Deactivation-Time is specified, it applies to all rules within the AVP.

• Monitoring-Flags values remain valid until explicitly updated.

Charging-Rule-Name

1005

OctetString

3GPP

Used to identify a PCC rule (Policy and Charging Control rule) by name. It can uniquely represent a PCC rule in two contexts:

• Dynamic Rules provided by the PCRF – It uniquely identifies a PCC rule within a specific IP CAN session.

• Predefined Rules stored in the PCEF – It uniquely identifies a predefined PCC rule within the PCEF itself.

This AVP allows referencing a specific rule for:

• Activation or deactivation during IP CAN session setup or modification.

• Modifications such as changing QoS, charging mechanisms, or flow rules.

Validation Rules:

• The Charging-Rule-Name must be unique within the IP CAN session or PCEF.

• If the rule name references a predefined rule, it must exist in the PCEF to avoid errors.

• Can be used independently or within Charging-Rule-Install AVP for grouping with other attributes like Monitoring Flags or QoS Information.

Charging-Rule-Report

1018

Grouped

3GPP

Used to report the status of PCC rules (Policy and Charging Control rules) at the PCEF (Policy and Charging Enforcement Function). It provides detailed feedback to the PCRF (Policy and Charging Rules Function) regarding the installation, modification, activation, deactivation, or failure of PCC rules.

The AVP structure is defined as follows:

Charging-Rule-Name (1005, OctetString): Identifies the specific PCC rule being reported.

Can refer to dynamic or predefined rules at the PCEF.

Charging-Rule-Base-Name (1004, UTF8String): References a group of predefined PCC rules at the PCEF for bulk reporting.

Bearer-Identifier (1020, OctetString): Indicates the bearer associated with the rule, particularly in GPRS scenarios.

PCC-Rule-Status (1019, Enumerated): Reports the status of the PCC rule:

• ACTIVE (0): Rule is active and enforced.

• INACTIVE (1): Rule is inactive or disabled.

• REMOVED (2): Rule has been removed from the session.

Rule-Failure-Code (1031, Enumerated): Indicates the failure reason for rule installation or enforcement:

• RESOURCE_ALLOCATION_FAILURE (1): Resource allocation failed.

• UNSUPPORTED_SERVICE (2): Requested service is not supported.

• QOS_NOT_AVAILABLE (3): QoS cannot be provided.

• INSUFFICIENT_BANDWIDTH (4): Bandwidth requirements cannot be satisfied.

Final-Unit-Indication (430, Grouped): Specifies the action to take for rules when credit runs out.

• TERMINATE (0): Disconnect service.

• REDIRECT (1): Redirect traffic to another address.

• RESTRICT_ACCESS (2): Limit access based on policy.

RAN-NAS-Release-Cause (1032, OctetString): Provides the cause for RAN or NAS layer session release.

Content-Version (1033, Unsigned32): Indicates the version number of the PCC rule definition for version tracking and updates.

Validation Rules:

• Supports multiple instances of the Charging-Rule-Report AVP to report different rules within a single Diameter message.

• Rule-Failure-Code must be included when rules fail.

• Must include Final-Unit-Indication when reporting out-of-credit situations.

• Includes Content-Version when supported by RuleVersioning features.

CoA-Information

1039

Grouped

3GPP

Used to carry information about a Care-of Address (CoA) along with its associated tunnel information. It is sent from the PCEF (Policy and Charging Enforcement Function) to the PCRF (Policy and Charging Rules Function) to facilitate policy decisions and enforcement for users in scenarios involving mobility and tunneling.

The AVP structure is defined as follows:

Tunnel-Information (1038, Grouped): Contains tunnel-specific details such as header length and filters required for processing tunnel packets.

Structure:

• Tunnel-Header-Length: Specifies the size of the tunnel header.

• Tunnel-Header-Filter: Defines filters for identifying traffic associated with the tunnel.

CoA-IP-Address (1037, Address): Contains the IP address assigned to the mobile node as its Care-of Address (CoA).

Validation Rules:

• Must include both CoA-IP-Address and Tunnel-Information.

• Supports multiple CoA-Information AVPs if different CoAs are active in parallel sessions.

• Checks for valid IPv4 or IPv6 addresses.

• Ensures that header length and filters match the transport protocol used in tunneling.

CoA-IP-Address

1035

Address

3GPP

Contains the Care-of Address (CoA) of a mobile node. It can hold either an IPv4 or IPv6 address. The CoA represents the temporary IP address assigned to the mobile node when it is connected to a foreign network during mobility scenarios. Allows multiple CoA-IP-Address AVPs if the mobile node uses multiple network interfaces or dual-stack configurations.

Conditional-APN-Aggregate-Max-Bitrate

2818

Grouped

3GPP

Defines the conditional APN policy information related to bandwidth limitations and conditions under which those limitations are enforced. It specifies maximum bandwidth values for uplink (UL) and downlink (DL) traffic over non-GBR QoS Class Identifiers (QCIs) within an APN (Access Point Name) context. The AVP structure is defined as follows:

APN-Aggregate-Max-Bitrate-UL (1041, Unsigned32): Specifies the maximum aggregate uplink bandwidth in bps for non-GBR traffic. Used when bandwidth values are ≤ 2^32-1.

APN-Aggregate-Max-Bitrate-DL (1040, Unsigned32): Specifies the maximum aggregate downlink bandwidth in bps for non-GBR traffic. Used when bandwidth values are ≤ 2^32-1.

Extended-APN-AMBR-UL (2821, Unsigned64): Specifies the maximum extended uplink bandwidth in kbps. Used when bandwidth exceeds 2^32-1 bps.

Extended-APN-AMBR-DL (2820, Unsigned64): Specifies the maximum extended downlink bandwidth in kbps. Used when bandwidth exceeds 2^32-1 bps.

IP-CAN-Type (1027, Enumerated): Specifies the IP Connectivity Access Network (IP-CAN) type. Please refer to the IP-CAN-Type AVP description for exact values.

RAT-Type (1032, Enumerated): Specifies the Radio Access Technology (RAT) type. Please refer to the RAT-Type AVP description for exact values.

Validation Rules:

• At least one pair of uplink/downlink AVPs is mandatory (either standard or extended).

• Extended AVPs are only used when bandwidth values exceed 2^32-1 bps.

• At least one condition must be specified using IP-CAN-Type or RAT-Type.

• Multiple conditions can be combined for fine-grained control over bandwidth allocation.

• If omitted, no specific limits apply, and traffic is handled based on default QoS policies.

Conditional-Policy-Information

2840

Grouped

3GPP

Defines policy parameters that the PCRF (Policy and Charging Rules Function) dynamically applies based on specific conditions for resource allocation. It supports bandwidth control, QoS definitions, and timing for policy enforcement.

The AVP structure is defined as follows: 

Execution-Time (451, Time): Specifies the time when the policy changes should take effect.

Default-EPS-Bearer-QoS (1016, Grouped): Defines the QoS settings for the default EPS bearer (Evolved Packet System). Includes parameters such as QCI (QoS Class Identifier)

Maximum and Guaranteed Bandwidth for uplink and downlink.

APN-Aggregate-Max-Bitrate-UL (1041, Unsigned32): Specifies the maximum uplink bandwidth for non-GBR traffic in bps. Used for bandwidth values ≤ 2^32-1.

APN-Aggregate-Max-Bitrate-DL (1040, Unsigned32): Specifies the maximum downlink bandwidth for non-GBR traffic in bps. Used for bandwidth values ≤ 2^32-1.

Extended-APN-AMBR-UL (2821, Unsigned64): Specifies uplink bandwidth in kbps for values > 2^32 bps. Supports extended bandwidth requirements (e.g., 5G).

Extended-APN-AMBR-DL (2820, Unsigned64): Specifies downlink bandwidth in kbps for values > 2^32 bps. Supports extended bandwidth requirements (e.g., 5G).

Conditional-APN-Aggregate-Max-Bitrate (2818, Grouped): Specifies conditional bandwidth limits based on IP-CAN and RAT types.

Validation Rules:

• Execution-Time is required for delayed enforcement.

• Standard AVPs apply for ≤ 2^32-1 bps.

• Extended AVPs apply for > 2^32 bps.

• At least one condition (e.g., IP-CAN or RAT-Type) must be specified in Conditional-APN-Aggregate-Max-Bitrate.

• If omitted, previous policies remain valid until explicitly replaced.

Credit-Management-Status

1037

Unsigned32 (Bitmask)

3GPP

Contains a bitmask representing different credit management conditions. It is used to communicate the status of credit control actions between the PCRF (Policy and Charging Rules Function) and the PCEF (Policy and Charging Enforcement Function). Each bit in the AVP corresponds to a specific condition or status related to the user's charging state, allowing systems to take appropriate actions based on the bit values.

Bit Definitions:

0 End User Service Denied: Service denied due to restrictions (e.g., insufficient balance).

1 Credit Control Not Applicable: Service granted without credit control (e.g., free service).

2 Authorization Rejected: Service denied explicitly by the charging system.

3 User Unknown: End user not found in the charging system.

4 Rating Failed: Rating error due to invalid AVPs or unsupported service requests.

5 No Gyn Session, Service Allowed: Gyn session failed, but service is allowed to continue. (Sd interface only)

6 No Gyn Session, Service Not Allowed: Gyn session failed, and service is denied. (Sd interface only)

Validation Rules:

• At least one bit must be set for the AVP to be valid.

• Conflicting bits cannot be set simultaneously (e.g., Bit 5 and Bit 6).

• For Sd interface-specific bits (5 and 6), ensure the interface compatibility before setting.

CSG-Information-Reporting

1071

Enumerated

3GPP

Used by the PCRF (Policy and Charging Rules Function) to instruct the PCEF (Policy and Charging Enforcement Function) to report changes in the Closed Subscriber Group (CSG) information of a user to the OFCS (Offline Charging System). This AVP defines specific events related to user movement between different CSG cells, including closed cells, subscribed hybrid cells, and unsubscribed hybrid cells.

Values:

0 CHANGE_CSG_CELL: Reports when the UE enters, leaves, or accesses a CSG cell.

1 CHANGE_CSG_SUBSCRIBED_HYBRID_CELL: Reports when the UE enters, leaves, or accesses a hybrid cell where the subscriber is a CSG member.

2 CHANGE_CSG_UNSUBSCRIBED_HYBRID_CELL: Reports when the UE enters, leaves, or accesses a hybrid cell where the subscriber is not a CSG member.

Validation Rules:

• Only one value can be set at a time since it is enumerated.

• Unsubscribed hybrid cell reporting (Value 2) may lead to high signaling loads, so use it sparingly and only for specific subscribers.

• Works with Event-Trigger AVPs to monitor changes in UE mobility events.

Default-Access

2829

Enumerated

3GPP

Used to indicate the default access network type selected or determined during a session. It facilitates the management and enforcement of default IP-CAN (IP Connectivity Access Network) types within the Policy and Charging Rules Function (PCRF) and Policy and Charging Enforcement Function (PCEF). This AVP uses the same values as the IP-CAN-Type AVP

Values:

0 3GPP-EPS: Access via 3GPP-Evolved Packet System (EPS).

1 Non-3GPP-EPS: Access via Non-3GPP networks like Wi-Fi.

2 3GPP-2: Access via CDMA/HRPD networks.

3 3GPP-WLAN: Access via 3GPP-WLAN interworking.

4 3GPP-HRPD: Access via HRPD within 3GPP2 networks.

5 3GPP-EHRPD: Access via Enhanced HRPD in 3GPP2.

6 3GPP-NBIFOM: Access through Non-Bundle IP Flow Mobility.

Validation Rules:

• Only values 0 (3GPP-EPS) and 1 (Non-3GPP-EPS) are valid in the current release.

• The default access value must be aligned with the session context of the UE.

• Changes to the default access type must be accompanied by QoS updates if required.

Default-Bearer-Indication

2844

Enumerated

3GPP

Specifies whether a Policy and Charging Control (PCC) rule should be bound to the default bearer or whether it should follow the QoS-based bearer binding procedures. It is primarily used by the Policy and Charging Rules Function (PCRF) when defining or modifying PCC rules to manage bearer binding. Values:

0 BIND_TO_DEF_BEARER: Binds the associated PCC rule to the default bearer.

1 BIND_TO_APPLICABLE_BEARER: The PCC rule follows bearer binding procedures defined by QoS-Information AVP (QCI/ARP). This is the default value if the AVP is not explicitly provided.

Validation Rules:

• When the AVP is included, it must contain a valid enumerated value.

• If this AVP is not present, the system assumes the BIND_TO_APPLICABLE_BEARER (1) behavior.

• If BIND_TO_APPLICABLE_BEARER (1) is selected, the QoS-Information AVP (containing QCI/ARP) must be provided.

Default-EPS-Bearer-QoS

1049

Grouped

3GPP

Defines the Quality of Service (QoS) information for the EPS (Evolved Packet System) default bearer. It establishes the parameters that control the QoS level for the default bearer, including the QoS Class Identifier (QCI) and Allocation-Retention Priority (ARP).

The AVP structure is defined as follows: 

QoS-Class-Identifier (QCI) (1028, Enumerated): Identifies a QoS Class that defines specific parameters such as delay, packet loss, and error rate, excluding bitrates.

Values:

1–4: Guaranteed Bit Rate (GBR) classes.

5–9: Non-GBR classes (only these are allowed in this AVP).

Allocation-Retention-Priority (ARP) (1034, Grouped): Specifies the priority level for resource allocation and retention during bearer setup or handovers.

Sub AVPs within ARP:

• Priority-Level (Unsigned32): Defines the priority rank (lower values indicate higher priority).

• Pre-emption-Capability (Enumerated): Indicates if this bearer can pre-empt lower-priority bearers.

• Pre-emption-Vulnerability (Enumerated): Indicates if this bearer can be pre-empted by higher-priority bearers.

Validation Rules:

• Either QoS-Class-Identifier or Allocation-Retention-Priority must be present.

• GBR values are not allowed. Only Non-GBR values for QCI are valid.

• QoS parameters must align with ARP settings for effective priority management.

Default-QoS-Information

2816

Grouped

3GPP

Defines the default Quality of Service (QoS) information for the IP-CAN session in Fixed Broadband Access (FBA). It provides either dynamically supplied QoS parameters or pre-configured QoS profiles for managing traffic flow within the network.

The AVP structure is defined as follows: 

QoS-Class-Identifier (QCI) (1028, Enumerated): Identifies a QoS Class that determines specific traffic handling priorities and performance characteristics.

Values:

1–4: Guaranteed Bit Rate (GBR) classes.

5–9: Non-GBR classes (suitable for signaling, video streaming, etc.).

Max-Requested-Bandwidth-UL (515, Unsigned32): Specifies the maximum uplink bitrate allowed for traffic, measured in bps (bits per second).

Max-Requested-Bandwidth-DL (516, Unsigned32): Specifies the maximum downlink bitrate allowed for traffic, measured in bps (bits per second).

Default-QoS-Name (2817, UTF8String): Defines a pre-configured QoS profile name stored in the PCEF. Used when dynamic QoS parameters are not provided.

Validation Rules:

• At least one AVP (QCI, UL, DL, or QoS-Name) must be specified.

• If Default-QoS-Name is provided, no dynamic QoS parameters (QCI, UL, DL) should be included.

• Values must not exceed 2^32-1 bps unless the Extended-BW-NR feature is supported.

• If omitted, the previous QoS parameters remain valid.

Default-QoS-Name

2817

UTF8String

3GPP

Specifies the name of a pre-configured default QoS profile stored in the PCEF (Policy and Charging Enforcement Function). It is part of the Default-QoS-Information AVP and is used to define a default QoS configuration when dynamic QoS parameters are not provided.

Validation Rules:

• Must contain a valid UTF8 string representing the name of a pre-configured QoS profile.

• Cannot be included alongside dynamic QoS AVPs like:

  • QoS-Class-Identifier (QCI)

  • Max-Requested-Bandwidth-UL/DL

• The specified profile name must exist in the PCEF configuration; otherwise, the request will fail.

• If omitted, the PCEF uses the previously defined QoS profile for the session.

Event-Report-Indication

1033

Grouped

3GPP

Used for event reporting between the PCRF (Policy and Charging Rules Function) and the PCEF (Policy and Charging Enforcement Function), containing event triggers and related information about network events. Reports events from the Access Network Gateway (BBERF) to the PCEF. Provides event trigger subscriptions required by the PCEF. The Event-Report-Indication AVP can include parameters like location changes, routing details, and network events.

The AVP structure is defined as follows: 

AN-Trusted (Enumerated): Indicates whether the Access Network is trusted (e.g., WLAN trusted or untrusted).

Event-Trigger (Enumerated (List)): Defines specific event triggers like RAT_CHANGE, USER_LOCATION_CHANGE, etc.

User-CSG-Information (Grouped): Provides Closed Subscriber Group (CSG) information, including cell membership.

IP-CAN-Type (Enumerated): Specifies the IP Connectivity Access Network (IP-CAN) type (e.g., 3GPP-EPS).

AN-GW-Address (Address (IPv4/IPv6, List)): Specifies the Access Network Gateway Address.

3GPP-SGSN-Address (OctetString): Provides the IPv4 address of the SGSN (Serving GPRS Support Node).

3GPP-SGSN-Ipv6-Address (OctetString): Provides the IPv6 address of the SGSN.

3GPP-SGSN-MCC-MNC (OctetString): Identifies the Mobile Country Code (MCC) and Mobile Network Code (MNC).

Framed-IP-Address (Address (IPv4)): Specifies the user's IP address allocated by the network.

RAT-Type (Enumerated): Identifies the Radio Access Technology (e.g., LTE, UMTS).

RAI (OctetString): Provides the Routing Area Identity (RAI) for user location.

3GPP-User-Location-Info (OctetString): Contains the user's location information based on 3GPP specifications.

Trace-Data (Grouped): Specifies trace parameters for troubleshooting user connections.

Trace-Reference (OctetString): References a trace session for network monitoring.

3GPP2-BSID (OctetString): Provides Base Station ID for 3GPP2 networks.

3GPP-MS-TimeZone (OctetString): Reports the UE's time zone information.

Routing-IP-Address (Address (IPv4/IPv6)): Specifies an IP address used for routing traffic.

UE-Local-IP-Address (Address (IPv4/IPv6)): Provides the local IP address of the UE (User Equipment).

HeNB-Local-IP-Address (Address (IPv4/IPv6)): Specifies the local IP address of the Home eNodeB.

UDP-Source-Port (Unsigned32): Defines the UDP source port used in communication.

Presence-Reporting-Area-Information (Grouped): Provides details about Presence Reporting Areas (PRAs) for location tracking.

Event-Trigger

1006

Enumerated

3GPP

Вefines events that require policy control actions between the PCRF (Policy and Charging Rules Function) and the PCEF (Policy and Charging Enforcement Function).

PCRF to PCEF: Specifies events that require re-requests for PCC rules when triggered.

PCEF to PCRF: Reports events that occurred at the gateway to notify PCRF for further actions.

Exceptions: NO_EVENT_TRIGGERS (14): Indicates that PCEF should not notify the PCRF about any events unless explicitly provisioned.

Reporting Behavior: If Event-Trigger is associated with additional parameters, these values must also be sent.

Unsubscribing from events requires sending Event-Trigger AVP with NO_EVENT_TRIGGERS.

Enumerated Values:

SGSN_CHANGE (0) - Triggered when serving SGSN changes.

QOS_CHANGE (1) - Triggered when QoS changes beyond defined limits.

RAT_CHANGE (2) - Triggered when the Radio Access Technology (RAT) changes.

TFT_CHANGE (3) - Triggered when Traffic Flow Templates (TFT) are modified.

PLMN_CHANGE (4) - Triggered when the Public Land Mobile Network (PLMN) changes.

LOSS_OF_BEARER (5) - Reports bearer loss in case of network issues.

RECOVERY_OF_BEARER (6) - Reports bearer recovery after temporary failure.

IP-CAN_CHANGE (7) - Triggered when the IP Connectivity Access Network (IP-CAN) changes.

QOS_CHANGE_EXCEEDING_AUTHORIZATION (11) - Reports QoS changes that exceed authorization limits.

RAI_CHANGE (12) - Triggered when the Routing Area Identity (RAI) changes.

USER_LOCATION_CHANGE (13) - Triggered when the user’s location changes (e.g., cell or TAI).

NO_EVENT_TRIGGERS (14) - Disables all event triggers except those always reported by default.

OUT_OF_CREDIT (15) - Reports PCC rules where credit is exhausted.

REALLOCATION_OF_CREDIT (16) - Reports credit reallocation for previously exhausted rules.

REVALIDATION_TIMEOUT (17) - Reports policy revalidation timeout events.

UE_IP_ADDRESS_ALLOCATE (18) - Triggered when a UE IP address is allocated.

UE_IP_ADDRESS_RELEASE (19) - Triggered when a UE IP address is released.

DEFAULT_EPS_BEARER_QOS_CHANGE (20) - Reports changes in default EPS bearer QoS.

AN_GW_CHANGE (21) - Triggered when the Access Node Gateway (AN-GW) changes.

SUCCESSFUL_RESOURCE_ALLOCATION (22) - Reports successful allocation of resources.

RESOURCE_MODIFICATION_REQUEST (23) - Triggered when resources are modified by the UE.

PGW_TRACE_CONTROL (24) - Reports trace activation or deactivation at the P-GW.

UE_TIME_ZONE_CHANGE (25) - Triggered when the UE’s time zone changes.

TAI_CHANGE (26) - Triggered when the Tracking Area Identity (TAI) changes.

ECGI_CHANGE (27) - Triggered when the E-UTRAN Cell Global Identifier (ECGI) changes.

CHARGING_CORRELATION_EXCHANGE (28) - Reports access network charging identifier updates.

APN-AMBR_MODIFICATION_FAILURE (29) - Reports failures in APN-AMBR modification requests.

USER_CSG_INFORMATION_CHANGE (30) - Reports when the UE enters/leaves a CSG cell.

USAGE_REPORT (33) - Provides usage monitoring reports to the PCRF.

DEFAULT_EPS_BEARER_QOS_MODIFICATION_FAILURE (34) - Reports failures in modifying default EPS bearer QoS.

USER_CSG_HYBRID_SUBSCRIBED_INFORMATION_CHANGE (35) - Reports user entering/leaving hybrid cells as a subscriber.

USER_CSG_HYBRID_UNSUBSCRIBED_INFORMATION_CHANGE (36) - Reports user entering/leaving hybrid cells as a non-subscriber.

ROUTING_RULE_CHANGE (37) - Reports changes in routing rules for IP flow mobility or NBIFOM.

APPLICATION_START (39) - Reports detection of application start traffic.

APPLICATION_STOP (40) - Reports detection of application stop traffic.

CS_TO_PS_HANDOVER (42) - Reports CS to PS handover events.

UE_LOCAL_IP_ADDRESS_CHANGE (43) - Reports UE Local IP Address changes.

H(E)NB_LOCAL_IP_ADDRESS_CHANGE (44) - Reports H(e)NB Local IP Address changes.

ACCESS_NETWORK_INFO_REPORT (45) - Requests access network information.

CREDIT_MANAGEMENT_SESSION_FAILURE (46) - Reports failures in credit management sessions.

DEFAULT_QOS_CHANGE (47) - Reports changes in Default QoS information.

CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA_REPORT (48) - Reports changes in user presence in specified areas.

ADDITION_OF_ACCESS (49) - Reports addition of access in NBIFOM scenarios.

REMOVAL_OF_ACCESS (50) - Reports removal of access in NBIFOM scenarios.

UNAVAILABLITY_OF_ACCESS (51) - Reports unavailability of access in NBIFOM scenarios.

AVAILABLITY_OF_ACCESS (52) - Reports availability of access in NBIFOM scenarios.

RESOURCE_RELEASE (53) - Reports outcomes of resource releases for specified rules.

ENODEB_CHANGE (54) - Reports changes in user location within eNB changes.

3GPP_PS_DATA_OFF_CHANGE (55) - Reports changes in 3GPP PS Data Off status.

UE_STATUS_RESUME (56) - Reports resumption of UE status from suspension.

SUCCESSFUL_QOS_UPDATE (57) - Reports successful QoS updates for MPS or DTS.

Execution-Time

2839

Time

3GPP

Specifies the exact NTP (Network Time Protocol) timestamp when the associated policy information should take effect. This AVP is primarily used in conjunction with the Conditional-Policy-Information AVP to define conditional enforcement of policies based on specific timing criteria. It ensures that policy rules or charging configurations are activated at a precise time, facilitating time-based policy enforcement in dynamic network scenarios.

Extended-APN-AMBR-DL

2848

Unsigned32

3GPP

Used to define the maximum aggregate bit rate for the downlink (DL) direction across all non-GBR (Non-Guaranteed Bit Rate) bearers associated with the same Access Point Name (APN). It serves as a mechanism for controlling and enforcing bandwidth allocation policies within the Policy and Charging Control (PCC) architecture, ensuring efficient resource utilization and traffic management.

Extended-APN-AMBR-UL

2849

Unsigned32

3GPP

Defines the maximum aggregate bit rate for the uplink (UL) direction across all non-GBR (Non-Guaranteed Bit Rate) bearers associated with the same Access Point Name (APN).

Extended-GBR-DL

2850

Unsigned32

3GPP

Used to specify the guaranteed bitrate for a downlink (DL) service data flow in kilobits per second (kbit/s). This AVP is designed to enforce Guaranteed Bit Rate (GBR) requirements for specific traffic flows that demand a minimum level of service quality, such as voice over IP (VoIP), video streaming, and other real-time applications. It accounts for overhead from the IP layer and all layers above, including UDP, RTP, and the RTP payload.

Extended-GBR-UL

2851

Unsigned32

3GPP

Used to define the guaranteed bitrate for an uplink (UL) service data flow, measured in kilobits per second (kbit/s). It ensures that specific uplink traffic flows, such as voice and video communication, meet the required Quality of Service (QoS) by reserving a minimum bitrate for transmission. This AVP accounts for all overhead from the IP layer and layers above, including UDP, RTP, and RTP payload.

Fixed-User-Location-Info

2825

Grouped

3GPP

The Fixed-User-Location-Info AVP is a Grouped Attribute-Value Pair (AVP) used to identify the User Equipment (UE) location within a Fixed Access Network. It provides information about the physical and logical access points through which the UE is connected, enabling precise identification and location tracking in fixed broadband networks. This AVP is particularly relevant in Fixed Broadband Access (FBA) scenarios where accurate location information is required for policy enforcement, charging, and network management. The AVP structure is defined as follows: 

SSID (Optional): Identifies the Service Set Identifier (SSID) for wireless or fixed connections. Typically used for Wi-Fi networks to define the connected wireless access point.

BSSID (Optional): Represents the Basic Service Set Identifier (BSSID), which is the MAC address of the access point in wireless networks. Useful for distinguishing specific access points in multi-SSID environments.

Logical-Access-ID (Optional): Specifies the logical identifier for the access point used by the UE. Helps distinguish virtual network elements or VLAN configurations within the network.

Physical-Access-ID (Optional): Provides the physical identifier for the access point used by the UE, such as port numbers, MAC addresses, or device identifiers.

Allows inclusion of other AVPs as needed to extend functionality or provide additional information.

Flow-Direction

1080

Enumerated

3GPP

Specifies the direction in which a filter rule applies to traffic flow. It defines whether the filter is valid for downlink, uplink, or bidirectional traffic. This AVP is crucial in defining service data flow detection rules and enforcing Quality of Service (QoS) policies in both UE-initiated and network-initiated procedures. 

Enumerated Values:

UNSPECIFIED (0): The filter applies downlink by default but does not specify a direction explicitly. For uplink traffic, the filter is treated as bidirectional. Allowed only in UE-initiated procedures when received from the PCEF in the CCR (Credit Control Request). PCRF should avoid using this value in network-initiated procedures.

DOWNLINK (1): The filter applies only to traffic sent to the UE (downlink).

Commonly used for enforcing policies on downloads, streaming, or server-to-client communications.

UPLINK (2): The filter applies only to traffic sent from the UE (uplink).

Suitable for managing uploads, VoIP calls, and other client-to-server communications.

BIDIRECTIONAL (3): The filter applies to traffic both to and from the UE (bidirectional).

Ideal for symmetric traffic patterns, such as VoIP and peer-to-peer communication.

Flow-Information

1058

Grouped

3GPP

Used to define and manage IP flow packet filters for Policy and Charging Control (PCC) rules within the Gx interface. It specifies the characteristics and conditions for filtering IP packets based on fields such as Flow-Description, Traffic Class, and Security Parameters. This AVP enables dynamic traffic management and Quality of Service (QoS) enforcement by matching specific packets to predefined rules and policies. It is commonly exchanged between the PCRF and the PCEF. The AVP structure is defined as follows:

Flow-Description (Optional): Describes the matching rules for filtering packets based on IP addresses, ports, and protocols. Example: "permit out ip from 192.168.1.1 to any 80".

Packet-Filter-Identifier (Optional): Unique identifier assigned to a packet filter. Required for UE-initiated requests to modify or delete filters.

Packet-Filter-Usage (Optional): Specifies the usage type of the packet filter (e.g., predefined or dynamic).

ToS-Traffic-Class (Optional): Represents Type of Service (ToS) or Traffic Class parameters for filtering based on traffic priority.

Security-Parameter-Index (Optional): Filters packets based on IPSec Security Parameter Index (SPI) for encrypted flows.

Flow-Label (Optional): Matches packets based on IPv6 Flow Label, providing additional filtering granularity.

Flow-Direction (Mandatory if filters are specified, Enumerated): Indicates whether the filter applies to uplink, downlink, or both directions. Values:

0 (UNSPECIFIED)

1 (DOWNLINK)

2 (UPLINK)

3 (BIDIRECTIONAL)

Routing-Rule-Identifier (Optional): Used in NBIFOM scenarios to associate routing rules for IP flow mobility.

Allows extension with other AVPs to enhance filter behavior.

Flow-Label

1057

OctetString

3GPP

Used to convey the IPv6 flow label header field. It is primarily utilized for traffic flow identification and packet filtering based on the Traffic Flow Template (TFT) in Policy and Charging Control (PCC) scenarios. The Flow-Label AVP enables network elements, such as the Policy and Charging Enforcement Function (PCEF), to efficiently match and prioritize traffic flows. This facilitates Quality of Service (QoS) enforcement and traffic classification for IPv6-based connections.

Value: Contains the IPv6 flow label extracted from the IPv6 header.

Format: Encoded as a 3-byte (24-bit) OctetString, padded if necessary to meet Diameter encoding requirements.

Example Value: 0x000123 (hexadecimal representation of the flow label).

Range: 0–0xFFFFF (20-bit flow label as defined in [RFC8200]).

Guaranteed-Bitrate-DL

1025

Unsigned32

3GPP

Used to define the guaranteed bitrate in bits per second (bps) for a downlink (DL) service data flow. It specifies the minimum bitrate that must be reserved and maintained for a given flow, ensuring Quality of Service (QoS) for latency-sensitive applications such as VoIP, video conferencing, and streaming media. This AVP includes overheads from the IP layer and above (e.g., UDP, RTP, and RTP payload).

When the required bitrate exceeds the maximum value supported by Unsigned32 (4,294,967,295 bps or approximately 4.3 Gbps), the Extended-GBR-DL AVP (AVP Code: 2850) should be used instead, as specified in 3GPP [TS29.212].

Guaranteed-Bitrate-UL

1026

Unsigned32

3GPP

Specifies the guaranteed bitrate in bits per second (bps) for an uplink (UL) service data flow. It ensures the minimum bandwidth required for traffic flows originating from the User Equipment (UE), supporting Quality of Service (QoS) for latency-sensitive and high-priority applications such as VoIP, video conferencing, and file uploads. This AVP accounts for overheads introduced by the IP layer and layers above, such as UDP, RTP, and RTP payloads. 

When the required bitrate exceeds the maximum supported value of 4,294,967,295 bps (approximately 4.3 Gbps), the Extended-GBR-UL AVP (AVP Code: 2851) should be used as specified in 3GPP [TS29.212] to accommodate higher bandwidth demands, especially in 5G networks.

HeNB-Local-IP-Address

2804

Address

3GPP

Used to specify the local IP address of a Home eNodeB (HeNB), also known as a femtocell, within 3GPP Evolved Packet System (EPS) networks. This AVP supports both IPv4 and IPv6 address formats and is defined to enable communication between the PCRF and the PCEF. The HeNB-Local-IP-Address AVP is particularly useful in scenarios where femtocells are deployed to provide enhanced indoor coverage, enabling accurate identification and management of the local IP address assigned to the HeNB.

IP-CAN-Session-Charging-Scope

2827

Enumerated

3GPP

Defines whether the Access-Network-Charging-Identifier-Gx AVP applies to the entire IP-CAN (IP Connectivity Access Network) session. This AVP is used within the Policy and Charging Control (PCC) framework to simplify charging and accounting processes by associating a charging identifier with the complete session instead of individual flows.

Enumerated Values:

IP-CAN_SESSION_SCOPE (0): Indicates that the Access-Network-Charging-Identifier-Gx AVP corresponds to the entire IP-CAN session rather than specific flows.

IP-CAN-Type

1027

Enumerated

3GPP

Specifies the type of Connectivity Access Network (IP-CAN) through which the user is connected. It is mandatory during the establishment of an IP-CAN session and is included in session modification messages if there is a change in the network type and the PCRF has requested notification of such changes. The IP-CAN-Type AVP supports a wide range of access technologies, making it suitable for both legacy and next-generation networks. It is commonly used in conjunction with the RAT-Type AVP to further detail the type of radio access technology.

Enumerated Values:

0 3GPP-GPRS: 3GPP GPRS access connected to the GGSN via Gn/Gp interfaces. RAT-Type AVP provides additional access details, excluding EUTRAN and LTE-M.

1 DOCSIS: DOCSIS-based access technology used in cable networks.

2 xDSL: Access through xDSL (Digital Subscriber Line) technologies.

3 WiMAX: WiMAX-based access according to IEEE 802.16 standards.

4 3GPP2: Access through 3GPP2 networks connected to the 3GPP2 packet core. RAT-Type AVP specifies the exact access technology.

5 3GPP-EPS: Access via 3GPP Evolved Packet System (EPS), such as LTE. Further details provided by the RAT-Type AVP.

6 Non-3GPP-EPS: Non-3GPP access connected to an EPC (Evolved Packet Core) network, including Wi-Fi and trusted/untrusted networks.

7 FBA (Fixed Broadband Access): Fixed broadband access technologies, such as fiber or xDSL, converged via the IP Edge.

8 3GPP-5GS: Access via 3GPP 5G System (5GS) networks, including details in the RAT-Type AVP, excluding NB-IoT and LTE-M.

9 Non-3GPP-5GS: Non-3GPP access connected to 5GS, such as Wi-Fi or other IP-based technologies.

Max-PLR-DL

2852

Unsigned32

3GPP

Used to specify the maximum acceptable packet loss ratio (PLR) for downlink voice service data flows. This AVP is applicable only to Policy and Charging Control (PCC) rules with QoS Class Identifier (QCI) = 1, which is associated with conversational voice services requiring low latency and high reliability. The value represents the ratio of lost packets to the total number of packets sent, expressed in tenths of a percent (0.1%).

Max-PLR-UL

2853

Unsigned32

3GPP

Specifies the maximum acceptable packet loss ratio (PLR) for uplink voice service data flows. It is applicable only to Policy and Charging Control (PCC) rules with QoS Class Identifier (QCI) = 1, which is designed for conversational voice services requiring low latency and high reliability. The value represents the ratio of lost packets to the total number of packets sent, expressed in tenths of a percent (0.1%).

Metering-Method

1007

Enumerated

3GPP

Specifies the parameters to be metered for offline and online charging in Policy and Charging Control (PCC) scenarios. It defines whether metering should be based on duration, volume, both duration and volume, or events related to a service data flow.

Enumerated Values:

0 DURATION: Meters the duration of the service data flow traffic.

1 VOLUME: Meters the volume of data exchanged within the service data flow.

2 DURATION_VOLUME: Meters both duration and volume of the service data flow traffic.

3 EVENT: Meters events associated with the service data flow, such as session initiation, termination, or specific actions.

Monitoring-Flags

2828

Unsigned32 (Bitmask)

3GPP

Defines specific monitoring actions for Policy and Charging Control (PCC) rules in IP-CAN sessions. It provides control over the inclusion or exclusion of service data flows from usage monitoring, enabling fine-grained traffic management for volume-based and time-based charging. Each bit position in the Monitoring-Flags AVP represents a specific flag that can be either enabled (1) or disabled (0) to modify the behavior of the PCEF.

Bitmask Definitions:

When set (1): Excludes the specified service data flows from volume/time monitoring at the IP-CAN session level.

When unset (0): Includes the specified service data flows in monitoring at the session level (default behavior).

Monitoring-Key

1066

OctetString

3GPP

Used as a unique identifier for a usage monitoring control instance in Policy and Charging Control (PCC) frameworks. It allows the  PCEF to distinguish and manage multiple usage monitoring sessions within a single IP-CAN session, enabling granular monitoring and policy enforcement based on specific flows or traffic categories.

Monitoring-Time

2810

Time

3GPP

Specifies the time at which the PCEF should reapply the threshold values provided by the PCRF for usage monitoring control. It enables time-bound enforcement of Policy and Charging Control (PCC) rules, allowing thresholds for volume, duration, or event-based monitoring to be reset or reapplied at a specific time.

Mute-Notification

2809

Enumerated

3GPP

Used to control notifications sent from the PCEF to the PCRF about the start or stop of an application's traffic flow as detected by specific Policy and Charging Control (PCC) rules. It is primarily utilized in solicited application reporting scenarios to mute (suppress) notifications related to application start/stop events, ensuring that PCRF is not notified unless explicitly required. Enumerated Values:

0 MUTE_REQUIRED: Indicates that the PCEF shall not inform the PCRF when the application's start/stop is detected for the specific PCC rule(s).

NBIFOM-Mode

2830

Enumerated

3GPP

Used to specify the Non-3GPP IP Flow Mobility (NBIFOM) mode for managing IP flow mobility between 3GPP and non-3GPP access networks. It indicates whether the IP flow mobility can be initiated by the User Equipment (UE) or the network.

This AVP is exchanged:

From PCEF to PCRF: Sent in the initial CCR (Credit Control Request) command to indicate the NBIFOM mode suggested by the UE.

From PCRF to PCEF: Sent in the CCA (Credit Control Answer) command to confirm the NBIFOM mode selected by the PCRF.

Enumerated Values:

0 UE_INITIATED: Indicates that IP flow mobility can be initiated by the UE based on user-defined policies.

1 NETWORK_INITIATED: Indicates that IP flow mobility can be initiated by the network based on operator-defined policies.

NBIFOM-Support

2831

Enumerated

3GPP

Used to indicate whether Non-3GPP IP Flow Mobility (NBIFOM) procedures are supported and authorized for a given IP-CAN session.

From PCEF to PCRF (Initial CCR): Indicates whether the UE and network support NBIFOM procedures.

From PCRF to PCEF (Initial CCA): Indicates whether the PCRF authorizes the application of NBIFOM for the session.

If this AVP is absent in the initial CCR, it implies that NBIFOM procedures are not supported by the UE or the network.

Enumerated Values:

0 NBIFOM_NOT_SUPPORTED: Indicates that the PCRF does not authorize applying NBIFOM to the session, or the UE/network does not support NBIFOM procedures.

1 NBIFOM_SUPPORTED: Indicates that the UE and network support NBIFOM (CCR) and the PCRF authorizes its application to the session (CCA).

NetLoc-Access-Support

2824

Enumerated

3GPP

Used to indicate whether the current access network supports Network Location (NetLoc) procedures for retrieving access network information. It provides information about the capabilities of the serving access network regarding NetLoc feature support.

Enumerated Values:

0 NETLOC_ACCESS_NOT_SUPPORTED: Indicates that the current access network does not support NetLoc procedures for retrieving access network data.

Network-Request-Support

1024

Enumerated

3GPP

Indicates whether the User Equipment (UE) and the access network support network-initiated bearer establishment procedures. It determines the ability of the network to establish bearers dynamically, allowing operators to provide advanced QoS and traffic management features. Enumerated Values:

0 NETWORK_REQUEST_NOT_SUPPORTED: Indicates that the UE and network do not support network-initiated bearer establishment requests.

1 NETWORK_REQUEST_SUPPORTED: Indicates that the UE and network support network-initiated bearer establishment requests.

Offline

1008

Enumerated

3GPP

Defines whether the offline charging interface for a specific Policy and Charging Control (PCC) rule or IP-CAN session should be enabled or disabled. It specifies whether the PCEF is required to generate offline charging records for billing purposes. Offline charging is commonly used for postpaid billing systems where usage records are collected and processed later rather than in real time. Enumerated Values:

0 DISABLE_OFFLINE: Indicates that the offline charging interface is disabled for the associated PCC rule or session.

1 ENABLE_OFFLINE: Indicates that the offline charging interface is enabled for the associated PCC rule or session.

Online

1009

Enumerated

3GPP

Used to define whether the online charging interface for a specific Policy and Charging Control (PCC) rule or IP-CAN session should be enabled or disabled. Online charging involves real-time credit control, typically used for prepaid billing systems, where usage is monitored and charged dynamically during the session.

Enumerated Values:

0 DISABLE_ONLINE: Indicates that the online charging interface is disabled for the associated PCC rule or session.

1 ENABLE_ONLINE: Indicates that the online charging interface is enabled for the associated PCC rule or session.

Packet-Filter-Content

1059

IPFilterRule

3GPP

Used to define the content of the packet filter for the creation of Policy and Charging Control (PCC) rules. It specifies the filtering criteria required by the PCRF to enforce traffic rules, based on UE-provided parameters. These rules determine whether packets are permitted or blocked based on IP addresses, protocols, and ports.

Packet-Filter-Identifier

1060

OctetString

3GPP

Used to specify the identity of a packet filter within a Policy and Charging Control (PCC) rule. It is primarily used for UE-initiated resource allocation to uniquely identify a packet filter assigned by the PCRF. The identifier remains unique per UE within the scope of the PCRF, enabling dynamic resource management and policy enforcement.

Packet-Filter-Information

1061

Grouped

3GPP

Contains detailed information about a single packet filter sent between the PCEF and the PCRF. This AVP supports packet filter management within Policy and Charging Control (PCC) rules, enabling the enforcement of QoS, traffic prioritization, and charging policies based on the properties of IP packets.

The AVP structure is defined as follows:

Packet-Filter-Identifier (OctetString): Unique identifier for the packet filter, assigned by the PCRF. Required for add, modify, and delete operations.

Precedence (Unsigned32): Specifies the evaluation priority for this filter relative to others. Lower values have higher precedence.

Packet-Filter-Content (IPFilterRule): Contains the filtering criteria, such as IP addresses, protocols, and ports, required for traffic classification and enforcement.

ToS-Traffic-Class (OctetString): Specifies the Type-of-Service (ToS) or Traffic Class values for matching traffic flows based on QoS requirements.

Security-Parameter-Index (SPI) (OctetString): Used for IPSec flow identification to ensure secure and encrypted communication.

Flow-Label (OctetString): Contains the IPv6 flow label header field for identifying and prioritizing traffic.

Flow-Direction (Enumerated): Defines the direction (uplink, downlink, or bidirectional) in which the filter applies, ensuring directional enforcement of policies.

Packet-Filter-Operation

1062

Enumerated

3GPP

Used to indicate a UE-initiated resource operation that requires Policy and Charging Control (PCC) rules to be added, modified, or deleted. This AVP enables the UE to dynamically manage its QoS requirements and traffic filters by signaling updates to the PCRF through the PCEF.

Enumerated Values:

0 DELETION: Indicates that the resources and PCC rules associated with the specified packet filter identifiers should be deleted.

1 ADDITION: Indicates a request for new resources and the creation of PCC rules for the provided packet filters.

2 MODIFICATION: Indicates that the QoS, precedence, or other parameters of an existing packet filter need to be modified.

Packet-Filter-Usage

1072

Enumerated

3GPP

Indicates whether the Policy and Charging Control (PCC) rule's traffic mapping information (packet filter) should be sent to the User Equipment (UE). It determines whether the UE should be provisioned with traffic filters that define how specific flows are managed, as per the IP Connectivity Access Network (IP-CAN) specifications. This AVP ensures consistency between network-enforced policies and UE behavior, especially in scenarios involving QoS enforcement, traffic classification, and bearer management.

Enumerated Values:

1 SEND_TO_UE: Indicates that the traffic mapping information (packet filter) should be sent to the UE, if applicable to the IP-CAN type.

Maximum Filter Limit: The number of filters that can be sent to the UE is limited based on the IP-CAN type (e.g., LTE, DSL).

PCC-Rule-Status

1019

Enumerated

3GPP

Used to describe the status of one or more Policy and Charging Control (PCC) rules. It enables the PCRF and the Policy and Charging Enforcement Function (PCEF) to manage and monitor the installation, activation, deactivation, and temporary suspension of PCC rules based on session and network conditions. Enumerated Values:

0 ACTIVE: Indicates that the PCC rule(s) are successfully installed (provisioned by PCRF) or activated (pre-configured at PCEF).

1 INACTIVE: Indicates that the PCC rule(s) are either removed (provisioned by PCRF) or inactive (pre-configured at PCEF).

2 TEMPORARILY INACTIVE: Indicates that the PCC rule(s) are temporarily disabled, for example, due to a bearer loss or network disruption.

Usage considerations:

• Rules marked as TEMPORARILY INACTIVE avoid complete removal and can be reactivated without requiring reinstallation.

• Rules marked INACTIVE are considered deleted and cannot be reactivated.

• Ensures synchronization between QoS enforcement and PCC rules for consistent traffic handling.

• Supports both pre-configured rules at the PCEF and dynamically provisioned rules from the PCRF.

P-CSCF-Restoration-Indication

2826

Enumerated

3GPP

The P-CSCF-Restoration-Indication AVP is an Enumerated Attribute-Value Pair (AVP) used to signal whether a Proxy-Call Session Control Function (P-CSCF) restoration is required.

This AVP is particularly relevant in scenarios involving IP Multimedia Subsystem (IMS) networks, where the P-CSCF serves as the entry point for the UE into the IMS core network. It ensures that restoration procedures are triggered to re-establish lost sessions or recover from failures affecting the P-CSCF.

Enumerated Values:

0 PCSCF_RESTORATION: Indicates that a P-CSCF restoration is requested, enabling recovery actions to restore sessions.

Usage considerations:

• Primarily applicable to IMS networks, where the P-CSCF is a core component.

• Restoration can be triggered by node failures, network updates, or manual resets.

• If restoration cannot be completed, the PCRF may send an error code indicating the cause of failure.

• If absent, no restoration is triggered, and session recovery relies on manual intervention.

PDN-Connection-ID

1065

OctetString

3GPP

Identifies a Packet Data Network (PDN) connection to which specific information refers. This AVP is primarily used in Policy and Charging Control (PCC) scenarios to associate QoS policies, charging rules, and bearer management operations with a specific PDN connection. It provides a unique identifier for managing multiple PDN connections associated with the same UE.

Usage considerations

• Enables the UE to handle multiple simultaneous PDN connections, each identified by a unique ID.

• Associates traffic flows and rules with the correct PDN connection, ensuring accurate enforcement.

• If not included, policies apply to the default PDN connection associated with the UE.

• Often used alongside QoS enforcement AVPs (e.g., QoS-Class-Identifier) and traffic filtering rules (e.g., Packet-Filter-Content AVP).

PRA-Install

2845

Grouped

3GPP

Used in 3GPP-EPS (Evolved Packet System) access types to provision new or updated Presence Reporting Areas (PRAs) for an IP-CAN session. Presence Reporting Areas are geographical zones or network-defined regions where the UE's presence is monitored for triggering policy actions based on location changes. This AVP facilitates dynamic configuration of PRAs, enabling location-aware services, charging, and QoS enforcement.

The AVP structure is defined as follows:

Presence-Reporting-Area-Information (Grouped): Contains detailed information about the Presence Reporting Area(s), including identifiers and boundary rules.

Allows inclusion of other AVPs relevant to the PRA configuration (e.g., Event-Trigger AVP).

Usage considerations:

• Supports dynamic updates without requiring session reinitialization.

• Allows provisioning of multiple areas in a single AVP instance.

• Often paired with the Event-Trigger AVP to define actions based on UE location changes.

• If absent, PRA configuration remains unchanged.

PRA-Remove

2846

Grouped

3GPP

Used in 3GPP-EPS (Evolved Packet System) access types to stop the reporting of one or more Presence Reporting Areas (PRAs) for a given IP-CAN session. This AVP facilitates dynamic removal of Presence Reporting Area monitoring by instructing the PCEF to terminate location-based monitoring associated with the specified Presence Reporting Area Identifiers. It is often used in scenarios where PRA monitoring is no longer required or when a user's session ends. 

Presence-Reporting-Area-Identifier (OctetString): Identifies the Presence Reporting Areas (PRAs) to be removed from monitoring.

Allows inclusion of other AVPs related to the PRA removal process, if required.

Usage considerations:

• Allows batch removal of multiple PRAs in a single AVP instance, optimizing signaling.

• If absent, previously provisioned PRA monitoring rules remain unchanged.

• Can be sent during active sessions for dynamic updates or at session termination to clean up rules.

Precedence

1010

Unsigned32

3GPP

Used to define the order of evaluation for Policy and Charging Control (PCC) rules and traffic flow filters within a session. It determines the priority in which service data flow templates (filters) are applied by the PCEF) during traffic detection, QoS enforcement, charging control, and usage monitoring. A lower Precedence value indicates higher priority, ensuring that rules or filters with more specific matching criteria are applied before less specific rules.

Usage considerations:

• Precedence values can be configured by the operator based on the IP-CAN type or policy requirements.

• PCRF-initiated modifications may require the PCEF to remap precedence values to maintain filter priority.

• In UE-initiated sessions, precedence values are not modified by the PCEF (per 3GPP [TS23.060]).

• Ensures consistent precedence assignments between PCC rules and traffic mapping filters.

Pre-emption-Capability

1047

Enumerated

3GPP

Used to define whether a service data flow or bearer can preempt resources that are already assigned to another service data flow or bearer with a lower priority level. It is utilized within the QoS-Information AVP or Default-EPS-Bearer-QoS AVP in Evolved Packet Systems (EPS) for resource allocation, ensuring efficient Quality of Service (QoS) handling in scenarios involving priority-based resource management.

Enumerated Values:

0 PRE-EMPTION_CAPABILITY_ENABLED: Allows the service data flow or bearer to preempt resources allocated to another flow or bearer with lower priority.

1 PRE-EMPTION_CAPABILITY_DISABLED: Disallows the service data flow or bearer from preempting resources assigned to another flow or bearer. (Default).

Details:

Enumerated values (0–1) indicating whether preemption is enabled or disabled.

If this AVP is absent, the default behavior is disabled (PRE-EMPTION_CAPABILITY_DISABLED).

Usage considerations:

• Typically used with the Pre-emption Vulnerability AVP (AVP Code: 1048) to define whether a flow or bearer can be preempted.

• If not included, the bearer or flow is treated as non-preemptive (disabled).

• Can be dynamically updated during session modifications to enable or disable preemption as required.

Pre-emption-Vulnerability

1048

Enumerated

3GPP

Used to specify whether the resources assigned to a service data flow or bearer can be preempted and reallocated to another higher-priority flow or bearer. It is included within the QoS-Information AVP or Default-EPS-Bearer-QoS AVP and supports priority-based QoS handling in Evolved Packet Systems (EPS), enabling resource management during congestion or network overload scenarios. Enumerated Values:

0 PRE-EMPTION_VULNERABILITY_ENABLED: Indicates that the service data flow or bearer can lose resources to accommodate higher-priority traffic. (Default)

1 PRE-EMPTION_VULNERABILITY_DISABLED: Indicates that the service data flow or bearer cannot be preempted, even by higher-priority traffic.

Details:

Value: Enumerated values (0–1) specifying whether preemption vulnerability is enabled or disabled.

If this AVP is absent, the default behavior is enabled (PRE-EMPTION_VULNERABILITY_ENABLED).

Usage considerations:

• Works in conjunction with the Pre-emption-Capability AVP (AVP Code: 1047) to define whether a flow or bearer is capable of preempting resources and whether it is vulnerable to preemption.

• Defaults to vulnerable (enabled) if this AVP is not explicitly specified.

• Allows dynamic updates during session modifications to enable or disable preemption vulnerability based on policy changes.

• Supports real-time adaptation to changes in network congestion or priority traffic requirements.

Presence-Reporting-Area-Elements-List

2820

OctetString

3GPP

Used in 3GPP-EPS (Evolved Packet System) access types to carry Presence Reporting Area (PRA) configuration data. It is encoded specifically starting from octet 9 of the Presence Reporting Area Action Information Element (IE) as specified in 3GPP [TS29.274].

Often used with PRA-Install (AVP Code: 2845) for adding PRAs and PRA-Remove (AVP Code: 2846) for removing PRAs.

Absence of this AVP implies that no PRA-specific updates are required.

Presence-Reporting-Area-Identifier

2821

OctetString

3GPP

Identifies a Presence Reporting Area (PRA) or a PRA set associated with user equipment (UE) presence changes. The AVP provides information about whether the UE is entering, leaving, or moving within a PRA or PRA set. This AVP is used by the MME/SGSN to notify the PCRF of UE presence changes in a network-defined PRA or PRA set.

Encoding Details [TS 29.274]:

• The PRA Identifier is located in octets 5 to 7 and contains the identifier of the PRA or PRA Set.

• The encoding is done using full hexadecimal representation (binary, not ASCII).

Additional flags and identifiers are defined for specific use cases, as outlined below.

Flags and Additional Information:

APRA (Additional PRA): Indicates a change in UE presence for more than one individual PRA within a PRA set. Requires inclusion of identifiers for each affected PRA.

IPRA (Inside PRA): Indicates the UE is inside or has entered the PRA identified by the PRA Identifier.

OPRA (Outside PRA): Indicates the UE is outside or has left the PRA identified by the PRA Identifier.

INAPRA (Inactive PRA): Indicates the PRA is inactive, and reporting of UE presence changes is deactivated.

Behavior: 

Only one of IPRA, OPRA, or INAPRA can be set to 1 for a given PRA Identifier.

If the APRA flag is set, subsequent octets must include additional PRA Identifiers with their respective presence statuses.

Presence-Reporting-Area-Information

2822

Grouped

3GPP

Describe a Presence Reporting Area (PRA). It combines multiple sub-AVPs to provide detailed information about the PRA configuration, status, and associated elements. This AVP facilitates location-aware services, policy enforcement, and monitoring based on user presence within specific network-defined zones.

The AVP structure is defined as follows:

Presence-Reporting-Area-Identifier (OctetString): Unique identifier for the PRA or PRA set, encoded in binary format (hexadecimal), defined in AVP 2821.

Presence-Reporting-Area-Status (Enumerated): Indicates the status of the PRA or UE status within the PRA (e.g., active or inactive).

Presence-Reporting-Area-Elements-List (OctetString): Contains PRA elements, describing the boundaries of the area (defined in AVP 2820).

Presence-Reporting-Area-Node (Optional, Grouped): Indicates nodes subscribed to UE status for the PRA (not applicable to the Gx interface).

Usage considerations:

• Dynamic Updates with PRA-Install and PRA-Remove: Typically used with PRA-Install (AVP 2845) to add PRAs and PRA-Remove (AVP 2846) to remove PRAs.

• Optional Node Tracking: The Presence-Reporting-Area-Node AVP is not applicable to the Gx interface but may apply to other interfaces.

Presence-Reporting-Area-Node

2855

Unsigned32 (Bitmask)

3GPP

Indicates which network entities (nodes) have subscribed to the User Equipment (UE) status updates within a Presence Reporting Area (PRA). It is primarily introduced for charging management purposes and specifies whether the Online Charging System (OCS) or Policy and Charging Rules Function (PCRF) subscribes to the UE status within a PRA. The AVP uses a bitmask representation, where each bit represents a subscription flag for a particular node.

Bitmask Values:

0 OCS: Indicates whether the Online Charging System (OCS) subscribes to the UE status updates within the PRA.

1 PCRF: Indicates whether the PCRF subscribes to UE status updates for policy enforcement and charging rules.

Usage considerations:

• Primarily introduced for charging management, not applicable to standard monitoring interfaces.

Presence-Reporting-Area-Status

2823

Enumerated

3GPP

Indicate the User Equipment (UE) status with respect to a Presence Reporting Area (PRA). It provides information on whether the UE is currently inside, outside, or if the PRA itself is inactive. This AVP supports mobility tracking, location-aware services, and dynamic policy enforcement based on UE movement within configured areas.

Enumerated Values:

0 In Area: UE is inside or has entered the PRA.

1 Out of Area: UE is outside or has left the PRA.

2 Inactive: The PRA is inactive in the serving node, implying no status updates are currently required.

Priority-Level

1046

Unsigned32

3GPP

Used to define the relative importance of a resource request for bearer establishment or modification in cases of resource limitations. It is primarily employed in admission control for Guaranteed Bit Rate (GBR) traffic and in scenarios requiring resource pre-emption to ensure Quality of Service (QoS). The Priority-Level AVP is closely linked to the QoS-Class-Identifier AVP and assists in determining packet marking at the transport level (e.g., Differentiated Services Code Point (DSCP) settings).

Value Range:

1 - 8: High Priority (Operator-Specific): Reserved for services authorized for prioritized treatment within the operator's network.

9 - 15: Lower Priority (Roaming or General Use): Assigned to roaming users or services authorized by the home network.

1 is the highest priority and should be used for critical services such as emergency calls.

15 is the lowest priority and can be used for non-critical applications.

PS-to-CS-Session-Continuity

1099

Enumerated

3GPP

Specifies whether a service data flow is eligible for Packet-Switched (PS) to Circuit-Switched (CS) session continuity, as defined in 3GPP [TS 23.216]. This AVP is typically employed in scenarios requiring seamless service continuity when transitioning between IP-based (PS) and legacy CS-based networks (e.g., during video calls).

Enumerated Values:

0 VIDEO_PS2CS_CONT_CANDIDATE: Indicates that the service data flow carries video and qualifies as a candidate for PS-to-CS session continuity.

QoS-Class-Identifier

1028

Enumerated

3GPP

Defines a set of Quality of Service (QoS) parameters applicable to IP-CAN (IP Connectivity Access Network) bearers or service data flows, as specified in 3GPP [TS 23.203]. This AVP provides standardized QoS characteristics that include parameters such as:

• Priority levels

• Packet delay budget

• Packet error rate

It does not specify bitrates or ARP (Allocation and Retention Priority), which must be provided separately.

Enumerated Values:

1 QCI_1: Conversational voice (low latency, high priority)

2 QCI_2: Conversational video (low latency, high priority)

3 QCI_3: Real-time gaming

4 QCI_4: Non-conversational video (buffered streaming)

5 QCI_5: Signaling (IMS control traffic)

6-9 QCI_6–9: Background and interactive traffic

65-85 QCI_65–85: Extended for 5G applications and IoT use cases

Supports custom values (128-254) for specialized services beyond standardized profiles.

QoS-Information

1016

Grouped

3GPP

Defines the Quality of Service (QoS) parameters for resources requested by the UE (User Equipment) or enforced by the PCEF (Policy and Charging Enforcement Function). It applies to IP-CAN bearers, PCC rules, QoS-Class-Identifiers (QCI), and APNs to ensure proper resource allocation, traffic prioritization, and bandwidth management.

The AVP structure is defined as follows:

QoS-Class-Identifier (Enumerated): Specifies the QCI for predefined QoS characteristics.

Max-Requested-Bandwidth-UL (Unsigned32): Maximum uplink bandwidth requested.

Max-Requested-Bandwidth-DL (Unsigned32): Maximum downlink bandwidth requested.

Extended-Max-Requested-BW-UL (Unsigned32): Extended uplink bandwidth for cases exceeding 2^32-1.

Extended-Max-Requested-BW-DL (Unsigned32): Extended downlink bandwidth for cases exceeding 2^32-1.

Guaranteed-Bitrate-UL (Unsigned32): Guaranteed uplink bitrate for GBR flows.

Guaranteed-Bitrate-DL (Unsigned32): Guaranteed downlink bitrate for GBR flows.

Extended-GBR-UL (Unsigned32): Extended guaranteed bitrate for uplink traffic when exceeding 2^32-1.

Extended-GBR-DL (Unsigned32): Extended guaranteed bitrate for downlink traffic when exceeding 2^32-1.

Bearer-Identifier (OctetString): Identifies the bearer if bound to an IP-CAN session initiated by the UE.

Allocation-Retention-Priority (Grouped): Defines priority level, pre-emption capability, and vulnerability for admission control.

APN-Aggregate-Max-Bitrate-UL (Unsigned32): Maximum aggregate uplink bandwidth across non-GBR bearers for the same APN.

APN-Aggregate-Max-Bitrate-DL (Unsigned32): Maximum aggregate downlink bandwidth across non-GBR bearers for the same APN.

Extended-APN-AMBR-UL (Unsigned32): Extended APN Aggregate Max Bitrate for uplink traffic.

Extended-APN-AMBR-DL (Unsigned32): Extended APN Aggregate Max Bitrate for downlink traffic.

Conditional-APN-Aggregate-Max-Bitrate (Grouped): Conditional max bitrates for non-GBR bearers under specified conditions.

Notes:

• Supports extended fields for 5G NR (New Radio) networks using Extended-GBR and Extended-AMBR.

• Allows for modifications during an active session using RESOURCE_MODIFICATION_REQUEST triggers.

• Enables enforcement at multiple levels—bearer, service data flow, and APN aggregation.

• If omitted, previous values remain valid unless explicitly updated.

QoS-Negotiation

1029

Enumerated

3GPP

Specifies whether the PCRF (Policy and Charging Rules Function) is permitted to negotiate the QoS parameters for a single PCC rule request during 3GPP-GPRS access. It controls whether the PCRF can authorize a QoS that differs from the one requested by the PCEF (Policy and Charging Enforcement Function) or UE (User Equipment).

Enumerated Values:

0 NO_QoS_NEGOTIATION: QoS negotiation is not allowed. The requested QoS parameters must be strictly enforced, and no deviations are permitted.

1 QoS_NEGOTIATION_SUPPORTED: QoS negotiation is allowed. The PCRF may authorize QoS values different from those requested. (Default Value)

QoS negotiation does not imply permanent changes—it affects only the current PCC rule and session context.

QoS-Upgrade

1030

Enumerated

3GPP

Used in the 3GPP-GPRS Access Type to specify whether the SGSN (Serving GPRS Support Node) supports QoS upgrades during the creation or modification of a PDP context. This AVP determines whether the PCRF (Policy and Charging Rules Function) is allowed to authorize bitrates—such as GBR (Guaranteed Bit Rate) or MBR (Maximum Bit Rate)—that exceed the initially requested bitrates for an IP-CAN bearer during session establishment or modification.

Enumerated Values:

0 QoS_UPGRADE_NOT_SUPPORTED: QoS upgrades are not supported. The PCRF must not provision bitrates higher than the requested values. (Default)

1 QoS_UPGRADE_SUPPORTED: QoS upgrades are supported. The PCRF can authorize higher bitrates based on network conditions and policy rules.

Behavior Rules:

• If the QoS-Upgrade AVP is omitted, the default value is QoS_UPGRADE_NOT_SUPPORTED (0).

• Once the AVP value is supplied, it remains applicable for the bearer until explicitly updated.

• If the SGSN does not support upgrades and the PCRF attempts to authorize higher bitrates, the request will fail unless explicitly negotiated.

RAN-NAS-Release-Cause

2819

OctetString

3GPP

Conveys information about the release cause code for a session termination or resource release initiated by the RAN (Radio Access Network) or NAS (Non-Access Stratum). For Non-3GPP-EPS access types, such as TWAN (Trusted Wireless Access Network) or untrusted WLAN, the AVP specifies the release cause code related to the disconnection event. 

Example Values:

0x0010: Normal Release

0x0011 : Authentication Failure

0x0012: Handover Failure

0x0013: Network Failure

0x0014: Protocol Error

0x0015: UE Lost Coverage

0x0016: Resource Optimization (e.g., Load Balancing)

Behavior Rules:

• If not present, it is assumed that the release cause is unknown or not applicable.

• The AVP values and encoding must strictly comply with the standards defined in 3GPP [TS 29.274] to ensure compatibility across network elements.

RAN-Rule-Support

2832

Enumerated

3GPP

Used to indicate whether the network supports RAN rule indications. It allows the PCRF (Policy and Charging Rules Function) to inform the PCEF (Policy and Charging Enforcement Function) about the capability of the network to handle RAN (Radio Access Network) rules.

Enumerated Values:

0 RAN rule indication support: The network supports the use of RAN rule indications.

Behavior Rules:

• The RAN-Rule-Support AVP is primarily used for policy control frameworks in LTE/5G networks.

• Must be included only when the network supports RAN rules, preventing non-compliance issues.

RAT-Type

1032

Enumerated

3GPP

Identifies the Radio Access Technology (RAT) being used to serve the User Equipment (UE). It specifies the type of access technology, such as 3G, LTE, 5G, WLAN, and others, enabling network elements to handle protocol-specific behaviors and optimizations.

Enumerated Values:

0 WLAN: Wireless LAN access network.

1 VIRTUAL: Unknown RAT (used when the RAT cannot be identified).

2 TRUSTED-N3GA: Trusted non-3GPP access excluding WLAN.

3 WIRELINE: Generic wireline access (e.g., DSL, fiber).

4 WIRELINE-CABLE: Cable-specific wireline access.

5 WIRELINE-BBF: Broadband Forum (BBF) wireline access.

1000 UTRAN: 3G Universal Terrestrial Radio Access Network.

1001 GERAN: 2G GSM/EDGE Radio Access Network.

1002 GAN: Generic Access Network (e.g., Unlicensed Mobile Access).

1003 HSPA_EVOLUTION: High-Speed Packet Access (HSPA) Evolution (3.5G).

1004 EUTRAN: LTE network (WB-EUTRAN).

1005 EUTRAN-NB-IoT: Narrowband IoT (NB-IoT) in LTE networks.

1006 NR: 5G New Radio (NR).

1007 LTE-M: LTE-Machine Type Communications (LTE-M).

1008 NR-U: 5G NR operating in unlicensed bands.

2000 CDMA2000_1X: CDMA2000 1X network (3GPP2 standard).

2001 HRPD: High Rate Packet Data network (3GPP2).

2002 UMB: Ultra Mobile Broadband (3GPP2, discontinued).

2003 EHRPD: Enhanced High Rate Packet Data (3GPP2).

Redirect-Information

1085

Grouped

3GPP

Provides redirection instructions for handling specific application traffic detected during Policy and Charging Control (PCC) processing. It informs the Policy and Charging Rules Function (PCRF) or Policy and Charging Enforcement Function (PCEF) about redirection requirements, including the address type and destination for redirection.

The AVP structure is defined as follows:

Redirect-Support (1086, Enumerated) Indicates whether redirection is supported and enabled/disabled for this session.

Enumerated Values:

0 DISABLED: Redirection is off.

1 ENABLED: Redirection is active.

Redirect-Address-Type (1087, Enumerated) Specifies the type of address used for redirection (e.g., IPv4, IPv6, FQDN).

Enumerated Values:

0 IPv4 Address

1 IPv6 Address

2 FQDN (Fully Qualified Domain Name)

Redirect-Server-Address (1088, UTF8String) Provides the redirect server's address (e.g., IP address or URL) for handling the redirection.

Absence of this AVP means no redirection applies, and default routing is used.

Redirect-Support

1086

Enumerated

3GPP

Defines whether redirection is enabled or disabled for a detected application's traffic in Policy and Charging Control (PCC). It works alongside the Redirect-Information AVP (1085) to indicate whether traffic should be redirected and to specify the necessary redirection details.

Enumerated Values:

0 REDIRECTION_DISABLED: Redirection is disabled for the application's traffic.

1 REDIRECTION_ENABLED: Redirection is enabled for the application's traffic. (Default if AVP is omitted)

Behavior Rules:

• If the Redirect-Support AVP is omitted, REDIRECTION_ENABLED (1) applies if Redirect-Information AVP is present.

Removal-Of-Access

2842

Enumerated

3GPP

Used in multi-access IP-CAN sessions to indicate that one specific access should be removed from the session. It allows the Policy and Charging Rules Function (PCRF) to instruct the Policy and Charging Enforcement Function (PCEF) or Bearer Binding and Event Reporting Function (BBERF) to terminate access for a particular connection, maintaining session control and resource management.

Enumerated Values:

0 REMOVAL_OF_ACCESS: Indicates that one access shall be removed from a multi-access IP-CAN session.

Usage considerations:

• Does not terminate the entire session—only removes one specific access.

• Supports advanced scenarios like Dual Connectivity and Multi-RAT (Radio Access Technology) support.

Reporting-Level

1011

Enumerated

3GPP

Specifies the granularity level at which the Policy and Charging Enforcement Function (PCEF) reports usage data for a given Policy and Charging Control (PCC) rule. It determines how detailed the reported usage metrics should be and is applicable for online and offline charging scenarios.

Enumerated Values:

0 SERVICE_IDENTIFIER_LEVEL: Usage reporting is based on a service ID and rating group combination level. It is applicable when both Service-Identifier and Rating-Group AVPs are included in the Charging-Rule-Definition AVP.

1 RATING_GROUP_LEVEL: Usage reporting is based solely on the rating group level. It is applicable when the Rating-Group AVP is provisioned within the Charging-Rule-Definition AVP.

2 SPONSORED_CONNECTIVITY_LEVEL: Usage reporting considers a sponsor identity, application service provider identity, and rating group combination. It applies primarily to offline charging scenarios.

Behavior Rules:

• If omitted, the previously supplied level remains valid. 

• If no level was previously supplied, the PCEF's default configuration applies.

Resource-Allocation-Notification

1063

Enumerated

3GPP

Specifies whether a confirmation notification should be sent for the resource allocation associated with a Policy and Charging Control (PCC) rule. It is used to ensure that resources required for specific charging rules are successfully allocated and confirmed.

Enumerated Values:

0 ENABLE_NOTIFICATION: Indicates that the resource allocation confirmation for the associated PCC rules must be provided.

Behavior Rules:

• If this AVP is omitted, no explicit confirmation is required from the PCEF.

• Used only when explicit feedback is necessary.

• This AVP must be included within or alongside the Charging-Rule-Install AVP, which defines the actual PCC rules being provisioned.

Resource-Release-Notification

2841

Enumerated

3GPP

Used to specify whether a notification should be sent upon the release of resources associated with specific Policy and Charging Control (PCC) rules. It ensures that any resource deallocation or removal process is explicitly confirmed.

Enumerated Values:

0 ENABLE_NOTIFICATION: Specifies that the PCEF must notify the PCRF about the release status for the related PCC rules.

Behavior Rules:

• If this AVP is omitted, no explicit confirmation is required from the PCEF regarding resource release.

• Explicit confirmation is used only when feedback about resource removal is critical.

• Must be included within or alongside the Charging-Rule-Remove AVP, which specifies the PCC rules being removed.

Revalidation-Time

1042

Time (NTP Timestamp)

3GPP

Used to specify a time limit by which the Policy and Charging Enforcement Function (PCEF) must revalidate Policy and Charging Control (PCC) rules by sending a re-request to the Policy and Charging Rules Function (PCRF).

Behavior Rules:

• Always provisioned with the REVALIDATION_TIMEOUT value in the Event-Trigger AVP.

• Uses Network Time Protocol (NTP) format to specify the exact time before which revalidation is required.

• Remains valid unless explicitly updated by the PCRF in subsequent Diameter messages.

Routing-Filter

1078

Grouped

3GPP

Used to define routing filter parameters for traffic management and routing policies. It is sent from the Policy and Charging Enforcement Function (PCEF) to the Policy and Charging Rules Function (PCRF) as part of traffic routing policies. This AVP specifies how traffic should be matched and classified using criteria such as flow descriptions, direction, traffic class, IPSec parameters, and flow labels. The AVP structure is defined as follows:

Flow-Description (Mandatory): Describes the traffic flow to match using source/destination IP, port numbers, and protocol types. Must specify "permit out ip from any to any" for wildcard filtering.

Flow-Direction (Mandatory): Specifies the direction of traffic flow. Must be set to BIDIRECTIONAL for this AVP.

ToS-Traffic-Class (Optional): Specifies the Type-of-Service (ToS) or Traffic Class to match traffic. Allows QoS tagging based on IP headers.

Security-Parameter-Index (Optional): Specifies the IPSec SPI for filtering encrypted traffic flows.

Flow-Label (Optional): Matches specific flow labels (used in IPv6 QoS) for routing.

Routing-IP-Address

1079

Address

3GPP

Contains either an IPv4 or IPv6 address associated with the mobile node's home address or care-of-address. It is primarily used in routing policies to identify the source or destination IP address for specific IP-CAN sessions and to facilitate traffic steering based on the user's network location. Key Fields:

IPv4 Address (Optional): Contains the IPv4 address associated with the device in dotted-decimal notation (e.g., 192.168.1.1).

IPv6 Address (Optional): Supports IPv6 addresses in colon-hexadecimal notation (e.g., 2001:0db8::1).

Routing-Rule-Definition

1076

Grouped

3GPP

Defines an IP flow mobility routing rule or NBIFOM routing rule sent between the Policy and Charging Enforcement Function (PCEF) and the Policy and Charging Rules Function (PCRF) within a single IP-CAN session. This AVP is used to establish routing rules for dynamic traffic steering based on IP flow mobility or network-based IP flow mobility (NBIFOM) procedures.

The AVP structure is defined as follows:

Routing-Rule-Identifier (Mandatory, OctetString): Uniquely identifies the routing rule for referencing within the IP-CAN session.

Routing-Filter (Optional, Repeated, Grouped): Specifies filter criteria (e.g., IP addresses, ports, protocols) to match traffic flows.

Precedence (Optional, Unsigned32): Specifies the priority of this rule relative to others—lower values indicate higher priority.

Routing-IP-Address (Optional, Address): Specifies the IP address (IPv4 or IPv6) for routing traffic.

IP-CAN-Type (Optional, Enumerated): Identifies the access type used for routing data flows. Values:

0: 3GPP-EPS

1: Non-3GPP-EPS

Routing-Rule-Failure-Code

2834

Unsigned32

3GPP

Used to specify the reason why a NBIFOM (Network-Based IP Flow Mobility) routing rule cannot be installed or modified. This AVP is included in the Routing-Rule-Report AVP and sent by the PCRF (Policy and Charging Rules Function) to the PCEF (Policy and Charging Enforcement Function) in response to routing rule management requests.

Enumerated Values:

0 Subscription Limitation: Rule blocked due to subscription constraints.

1 Operator Policy: Rule violates operator-defined policies.

2 Resource Limitation: Rule rejected due to insufficient network resources.

3 Routing Access Information Not Allowed: Rule denied by network policy.

4 Unspecified Error: Rule failed due to an unspecified error.

Routing-Rule-Identifier

1077

OctetString

3GPP

Unique identifier used to define IP flow mobility routing rules or NBIFOM (Network-Based IP Flow Mobility) routing rules within a single IP-CAN session.

It helps distinguish between different routing rules and facilitates communication between the PCEF (Policy and Charging Enforcement Function) and PCRF (Policy and Charging Rules Function) regarding rule management. Encoded as a UTF8String, it specifies the assigning node and the identifier sequence.

Routing-Rule-Install

1081

Grouped

3GPP

Used to install or modify IP flow mobility routing rules (defined in clause 4.3a) or NBIFOM (Network-Based IP Flow Mobility) routing rules (defined in clause 4.3c) as instructed by the PCEF (Policy and Charging Enforcement Function) to the PCRF (Policy and Charging Rules Function).

The AVP structure is defined as follows:

Routing-Rule-Definition: Specifies individual routing rules for IP flow mobility or NBIFOM. It is grouped for flexibility.

Allows adding custom AVPs or vendor-specific attributes, ensuring extensibility.

Routing-Rule-Remove

1075

Grouped

3GPP

The Routing-Rule-Remove AVP is used to remove IP flow mobility routing rules or NBIFOM (Network-Based IP Flow Mobility) routing rules for an IP-CAN session. It is sent by the PCEF (Policy and Charging Enforcement Function) to the PCRF (Policy and Charging Rules Function) to delete specific rules based on their identifiers. The AVP structure is defined as follows:

Routing-Rule-Identifier: Identifies the specific routing rule(s) to be removed. Multiple identifiers can be included.

Allows additional AVPs or vendor-specific attributes for extensibility and customization.

Routing-Rule-Report

2835

Grouped

3GPP

Used to report the status of NBIFOM (Network-Based IP Flow Mobility) routing rules. It informs the PCRF (Policy and Charging Rules Function) about the success or failure of rule installation or modification attempts and provides the reason for failures. The AVP structure is defined as follows:

Routing-Rule-Identifier: Identifies the routing rule(s) for which status is being reported. Multiple identifiers are supported.

PCC-Rule-Status: Describes whether the routing rules are ACTIVE, INACTIVE, or TEMPORARILY INACTIVE.

Routing-Rule-Failure-Code: Provides the reason for failure if rules cannot be installed or modified (e.g., policy conflict).

Multiple Routing-Rule-Report AVPs can be grouped for scenarios involving large rule sets.
Allows additional AVPs or vendor-specific extensions to be included if required.

Behavior rules:

Multiple Routing-Rule-Report AVPs can be included in the same message for batch reporting.
Status Codes:

• ACTIVE (0): Successfully installed or activated.

• INACTIVE (1): Failed to install or deactivate.

• TEMPORARILY INACTIVE (2): Temporarily disabled (e.g., loss of bearer).

Failure Codes:

• 0 Subscription Limitation: Rule cannot be applied due to user restrictions.

• 1 Operator Policy: Rule conflicts with network policy.

• 2 Resource Limitation: Lack of resources to enforce rule.

• 3 Routing Access Information Not Allowed: Network blocks routing information.

• 4 Unspecified Error: Generic failure reason.

Rule-Activation-Time

1043

Time

3GPP

Specifies the absolute time at which a PCC (Policy and Charging Control) rule should be enforced. It provides a precise NTP (Network Time Protocol) timestamp and ensures time-synchronized policy enforcement across network elements.

Behavior rules:

• Rules remain inactive until the specified activation time.

• If the Rule-Activation-Time AVP is omitted, rules are activated immediately.

• Requires synchronized clocks using NTP servers to avoid enforcement errors.

• Always specified in UTC to avoid time zone misalignment.

Rule-Deactivation-Time

1044

Time

3GPP

Specifies the absolute time at which a PCC (Policy and Charging Control) rule should stop being enforced. It provides a NTP (Network Time Protocol) timestamp, ensuring time-synchronized policy deactivation across network elements.

Behavior rules:

• Synchronized NTP clocks must be maintained to prevent timing mismatches.

• If Rule-Deactivation-Time AVP is not included, rules remain valid indefinitely until explicitly removed.

• Always specified in UTC for consistency across distributed systems.

Rule-Failure-Code

1031

Enumerated

3GPP

Identifies specific reasons why a PCC (Policy and Charging Control) rule could not be installed, activated, modified, or enforced. It is sent by the PCEF (Policy and Charging Enforcement Function) to the PCRF (Policy and Charging Rules Function) within a Charging-Rule-Report AVP.

Enumerated Values:

1 UNKNOWN_RULE_NAME: Rule name unknown to PCEF.

2 RATING_GROUP_ERROR: Invalid or unknown Rating-Group in the rule.

3 SERVICE_IDENTIFIER_ERROR: Invalid or unknown Service-Identifier.

4 GW/PCEF_MALFUNCTION: Failure due to malfunction of PCEF or gateway.

5 RESOURCES_LIMITATION: Insufficient resources to enforce rule.

6 MAX_NR_BEARERS_REACHED: Maximum number of bearers reached for the session.

7 UNKNOWN_BEARER_ID: Bearer-ID specified is invalid or unknown.

8 MISSING_BEARER_ID: Bearer-ID is missing when required.

9 MISSING_FLOW_INFORMATION: No flow information or application ID specified.

10 RESOURCE_ALLOCATION_FAILURE: Bearer establishment or modification failed.

11 UNSUCCESSFUL_QOS_VALIDATION: QoS validation failed (e.g., Guaranteed > Max-Requested Bandwidth).

12 INCORRECT_FLOW_INFORMATION: Invalid or unsupported flow information (IP version mismatch).

13 PS_TO_CS_HANDOVER: Rule disabled due to Packet-Switched (PS) to Circuit-Switched (CS) handover.

14 TDF_APPLICATION_IDENTIFIER_ERROR: Invalid or unknown TDF-Application-Identifier.

15 NO_BEARER_BOUND: No bearer available for binding the rule.

16 FILTER_RESTRICTIONS: Flow description violates filter restrictions.

17 AN_GW_FAILED: Access network gateway failure; further rules should not be sent until recovery.

18 MISSING_REDIRECT_SERVER_ADDRESS: No valid redirect server address provided or preconfigured at PCEF.

19 CM_END_USER_SERVICE_DENIED: Charging system denied the service request (e.g., insufficient balance).

20 CM_CREDIT_CONTROL_NOT_APPLICABLE: Service granted without further credit control needed (e.g., free service).

21 CM_AUTHORIZATION_REJECTED: Service authorization rejected.

22 CM_USER_UNKNOWN: End-user is unknown in the charging system.

23 CM_RATING_FAILED: Charging system unable to rate due to invalid AVP values or unsupported attributes.

24 ROUTING_RULE_REJECTION: Routing rule rejected by UE due to unspecified reasons.

25 UNKNOWN_ROUTING_ACCESS_INFORMATION: Routing rule rejected due to unknown access information.

26 NO_NBIFOM_SUPPORT: NBIFOM (Non-3GPP Interworking) not supported.

27 UE_STATE_SUSPEND: UE is in a suspend state.

28 TRAFFIC_STEERING_ERROR: Traffic steering to Gi-LAN failed due to invalid identifiers.

29 SAME_TIME_ERROR: Rule activation and deactivation times are identical, causing a configuration error.

Complementary AVPs:

• Charging-Rule-Report AVP: Contains the Rule-Failure-Code AVP as part of the error report.

• PCC-Rule-Status AVP: Describes the current status (e.g., active/inactive) of a rule.

• QoS-Information AVP: Provides additional context related to QoS errors during rule enforcement.

If Rule-Failure-Code AVP is omitted, it is assumed the rule enforcement was successful.

Security-Parameter-Index

1056

OctetString

3GPP

Specifies the Security Parameter Index (SPI) used in IPSec packets. It provides information about the security association that defines how data is encrypted or authenticated during transmission. This AVP is often utilized in Traffic Flow Template (TFT) packet filtering, as specified in 3GPP [TS 24.008].

Session-Release-Cause

1045

Enumerated

3GPP

Defines the reason for terminating an IP-CAN session. It is primarily sent by the PCRF (Policy and Charging Rules Function) when instructing the termination of a session due to specific conditions. This AVP enables PCEF (Policy and Charging Enforcement Function) or TDF (Traffic Detection Function) to take appropriate actions based on the release cause.

Enumerated Values:

0 UNSPECIFIED_REASON: Default value used when no specific cause is identified for session termination.

1 UE_SUBSCRIPTION_REASON: Indicates a change or removal in UE subscription, requiring session termination.

2 INSUFFICIENT_SERVER_RESOURCES: Specifies server overload or resource exhaustion, prompting session termination.

3 IP_CAN_SESSION_TERMINATION: Used in Sd interface for terminating TDF sessions as part of IP-CAN session termination.

4 UE_IP_ADDRESS_RELEASE: Indicates the release of an IPv4 address in a dual-stack IP-CAN session with active IPv4 flows.

TCP-Source-Port

2843

Unsigned32

3GPP

Indicates the TCP source port number used for the IKEv2 tunnel between the UE (User Equipment) and the ePDG (Evolved Packet Data Gateway). This AVP is particularly relevant in scenarios where a NAT (Network Address Translation) and firewall are detected, and IKEv2 messages are exchanged via a firewall traversal tunnel (FTT) as described in 3GPP [TS 24.302].

Usage Scenarios:

The TCP-Source-Port AVP is provided by the PCEF to the PCRF during IP-CAN session establishment over an untrusted WLAN as well as reporting of IP-CAN_CHANGE and RAT_CHANGE event triggers.

IKEv2 Firewall Traversal Tunnel Keep-Alive (FTT KAT) is used to maintain the tunnel:

• If the FTT_KAT configuration attribute is included in the IKE_AUTH response, the UE sets the FTT KAT to the provided value.

• If not included, the UE determines a random keep-alive time between 672 and 840 seconds by default.

TDF-Application-Identifier

1088

OctetString

3GPP

Specifies the application detection filter applied by the PCEF for application detection and control. Its value typically represents an application type, such as a list of URLs, domain names, or specific application patterns, and is used to:

• Apply policy and charging control rules related to application detection.

• Report application activity to the PCRF for monitoring or enforcement purposes.

TDF-Application-Instance-Identifier

2802

OctetString

3GPP

Dynamically identifies specific application instances detected and managed by the PCEF as part of Application Detection and Control (ADC) features. It allows correlation of Start and Stop events related to an application instance with its service data flow description when the flow description is deducible.

TDF-Destination-Host

1089

DiameterIdentity

3GPP

Specifies the Diameter Identity of the TDF (Traffic Detection Function) acting as the destination host for Diameter signaling messages.

TDF-Destination-Realm

1090

DiameterIdentity

3GPP

Specifies the Diameter Realm of the TDF (Traffic Detection Function), which acts as the destination realm for routing Diameter signaling messages. It is used to identify the administrative domain or routing realm to which the TDF belongs.

TDF-Information

1087

Grouped

3GPP

Provides details about the Traffic Detection Function (TDF) responsible for handling application detection and reporting within an IP-CAN session. It is primarily sent by the PCEF to the PCRF in a Credit Control Request (CCR) message when the CC-Request-Type is set to INITIAL-REQUEST. This AVP enables the PCRF to create a TDF session with the specified TDF instance to enforce application detection policies.

The AVP structure is defined as follows: 

TDF-Destination-Realm (1090): Specifies the realm of the TDF for routing purposes.

Example: "example.com"

TDF-Destination-Host (1089): Specifies the host name of the TDF.

Example: "tdf1.example.com"

TDF-IP-Address (1091): Specifies the IP address (IPv4 or IPv6) of the TDF.

Example: "192.168.1.10" or "2001:db8::1"

Usage considerations:

• If both pre-configured and dynamic values are present, the dynamic value (received in the request) takes precedence.

• Missing AVPs may lead to session rejection due to insufficient information for routing and enforcement.

TDF-IP-Address

1091

Address

3GPP

Identifies the IP address of the Traffic Detection Function (TDF) node responsible for application detection and reporting in an IP-CAN session. It supports both IPv4 and IPv6 addresses and can be used as an alternative or complement to TDF-Destination-Realm and TDF-Destination-Host AVPs.

TFT-Filter

1012

IPFilterRule

3GPP

Specifies a Traffic Flow Template (TFT) for packet filtering in 3GPP-GPRS access networks. It defines flow filters based on IP headers, protocols, and ports for controlling traffic flow direction and permissions. It is encoded using the IPFilterRule format, adhering to 3GPP [TS 24.008] specifications.

IPFilterRule Components:

Action: Permit or deny traffic. This AVP always permits traffic as defined by the TFT.

Direction: Out—Traffic flows from the UE to the network.

Protocol: Matches the Protocol Identifier (e.g., TCP, UDP). Defaults to IP if unspecified.

Source IP Address: Derived from the TFT filter's Remote Address and Subnet Mask. Defaults to any if unspecified.

Destination IP Address: Derived from the TFT filter's Local Address and Subnet Mask. Defaults to assigned if unspecified.

Port Numbers: Matches source or destination ports based on TFT filter definitions. Supports single values, lists, and ranges.

Does not support options or the invert modifier (!) for addresses.

TFT-Packet-Filter-Information

1013

Grouped

3GPP

Specifies Traffic Flow Template (TFT) details, including evaluation precedence, filter rules, traffic class, and flow direction. It is used in 3GPP-GPRS access networks for defining packet filters within a PDP context as part of PCC rules. The AVP structure is defined as follows:

Precedence (1011, Unsigned32): Specifies the evaluation precedence of this filter.

Lower values indicate higher priority.

TFT-Filter (1012, IPFilterRule): Defines the traffic flow template filter, including IP addresses, ports, and protocols. Example: permit out ip from any to assigned 5060.

ToS-Traffic-Class (1014, OctetString): Specifies Type of Service (ToS) or Traffic Class for marking packets based on DiffServ/DSCP.

Security-Parameter-Index (1056, OctetString): Contains security parameters for IPSec packets used in encryption and tunneling.

Flow-Label (1015, OctetString)

Identifies IPv6 flow labels to group packets for differentiated services or QoS treatment.

Flow-Direction (511, Enumerated): Defines the flow direction for the traffic filter:

IN (0): Incoming to the UE.

OUT (1): Outgoing from the UE.

BIDIRECTIONAL (2): Both directions.

3GPP-PS-Data-Off-Status

2847

Enumerated

3GPP

Indicates the data-off status for Packet-Switched (PS) services in 3GPP-EPS networks. It defines whether the User Equipment (UE) has activated or deactivated the data-off mode, which restricts data usage to comply with operator policies.

Enumerated Values:

0 ACTIVE: Indicates that the UE has activated data-off mode, disabling PS data services.

1 INACTIVE: Indicates that the UE has deactivated data-off mode, enabling PS data services (Default).

If the AVP is missing, it is treated as INACTIVE (1) to enable services by default.

ToS-Traffic-Class

1014

OctetString

3GPP

Used to convey Type-of-Service (ToS) or Traffic-Class (TC) information for IPv4 and IPv6 packets. It enables packet filtering and classification based on QoS parameters in the IP header. This AVP is encoded as two octets:

First Octet: Specifies the IPv4 ToS field or IPv6 Traffic-Class field.

Second Octet: Provides a mask to filter specific ToS/Traffic Class values.

Traffic-Steering-Policy-Identifier-DL

2836

OctetString

3GPP

Specifies a reference identifier for a pre-configured traffic steering policy applied at the PCEF in the downlink direction.

Traffic-Steering-Policy-Identifier-UL

2837

OctetString

3GPP

Specifies a reference identifier for a pre-configured traffic steering policy applied at the PCEF in the uplink direction.

If this AVP is not included, the PCEF applies default routing policies configured for uplink traffic.

Tunnel-Header-Filter

1036

IPFilterRule

3GPP

Defines the outer header filter information for a Mobile IP (MIP) tunnel. It specifies the filtering criteria to apply Quality of Service (QoS) rules to the payload within the tunnel. This AVP is particularly useful in scenarios where tunnel-based communications need to enforce traffic policies based on the outer IP header fields.

Mandatory Parameters:

Action: Must always be set to "permit".

Direction: Either "in" (uplink) or "out" (downlink).

Protocol: Specifies the IP protocol used (e.g., UDP or TCP).

Source IP Address: The source address in the tunnel header.

Source Port: Single port number for UDP tunneling.

Destination IP Address: The destination address in the tunnel header.

Destination Port: Single port number for UDP tunneling.

Restrictions:

Options: Shall not be used.

Invert Modifiers (!): Shall not be used for addresses.

Tunnel-Header-Length

1037

Unsigned32

3GPP

Defines the length of the tunnel header in octets. It specifies the size of the outer header used in tunnel encapsulation, enabling the PCEF (Policy and Charging Enforcement Function) to correctly process and enforce Quality of Service (QoS) rules for tunneled traffic.

Mandatory Parameter:

Tunnel Header Size: Specifies the length in octets of the tunnel header.

Behavior rules:

• If omitted, the default behavior depends on the protocol-specific header size pre-configured in the PCEF.

• The length value must be greater than zero to be valid.

Tunnel-Information

1038

Grouped

3GPP

Contains tunnel (outer) header information for a single IP flow. It is used in communication between the PCEF, PCRF, and Bearer Binding and Event Reporting Function (BBERF). This AVP is used for service data flow detection and QoS control within tunnels.

The AVP structure is defined as follows:

Tunnel-Header-Length (1037, Unsigned32): Specifies the length of the tunnel header in octets. It identifies the offset where the tunneled payload starts, enabling the BBERF to locate the inner IP header.

Tunnel-Header-Filter (1036, IPFilterRule): Defines the filter for tunnel header information. It includes the following fields:

Action: Must be set to "permit."

Direction: Specifies whether the filter applies to uplink (in) or downlink (out).

Protocol: Indicates the protocol used.

Source IP Address: Specifies the source IP address or range.

Source Port: Indicates the source port (single value) for UDP tunneling.

Destination IP Address: Specifies the destination IP address or range.

Destination Port: Indicates the destination port (single value) for UDP tunneling.

UDP-Source-Port

2806

Unsigned32

3GPP

Specifies the UDP source port number used in scenarios where Network Address and Port Translation (NAPT) is detected. It supports interworking with fixed broadband access networks and untrusted WLAN access over S2b interfaces as defined in [TS 29.212] Annex D.4 and Annex E.

Supports encapsulation of IKEv2 messages between the User Equipment (UE) and ePDG using UDP, following [RFC 3948] standards for NAT traversal.

UE-Local-IP-Address

2805

Address

3GPP

Specifies the local IP address assigned to the User Equipment (UE) in Non-3GPP-EPS access scenarios. It facilitates communication and session establishment by identifying the UE's local IP address used in various interworking and tunneling operations.

Used when the UE connects via non-3GPP access technologies, such as fixed broadband or untrusted WLAN, ensuring compatibility in hybrid network environments.

Supports broadband interworking scenarios as defined in [TS 29.212] Annex E.2.1.

UE-Status

2854

Enumerated

3GPP

Indicates the current status of the User Equipment (UE) in 3GPP-EPS access scenarios. It is used to manage policy enforcement based on the operational state of the UE, ensuring that the PCRF adapts its behavior accordingly.

Enumerated Values:

UE status suspend (1): Indicates that the UE is in a suspended state.

Policy enforcement cannot proceed because the UE is inactive or unreachable.

The PCEF informs the PCRF to halt policy decisions until the UE resumes operation.

This status is not applicable when the session modification procedure is initiated solely for PCC rule removal.

Usage-Monitoring-Information

1067

Grouped

3GPP

Provides usage monitoring control information. It defines thresholds and reporting mechanisms for monitoring user traffic volume and time usage in policy and charging control scenarios. This AVP supports both volume-based and time-based monitoring of user sessions.

The AVP structure is defined as follows:

Monitoring-Key (OctetString): Identifies the specific usage monitoring control instance.

Granted-Service-Unit (Grouped) (0–2 instances allowed): Provides details about the granted usage thresholds.

CC-Total-Octets: Sets the threshold for total volume usage.

CC-Input-Octets: Sets the threshold for uplink volume usage.

CC-Output-Octets: Sets the threshold for downlink volume usage.

CC-Time: Sets the threshold for time-based monitoring.