Name

AVP Code

Data Type

Vendor

Active-Time

4324

Unsigned32

3GPP

Specifies the amount of active time granted to the User Equipment (UE) in seconds.

APN-Rate-Control-Status

4326

Grouped

3GPP

Contain APN Rate Control Status Information as specified in figure 8.38-10 of 3GPP [TS 29.274].

APN-Rate-Control-Status-Validity-Time

4330

Unsigned64

3GPP

Contains information of octets k+13 to k+20 as specified in figure 8.38-10 of 3GPP [TS 29.274].

BSSGP-Cause

4309

Unsigned32

Contains the non-transparent copy of the cause value of the BSSGP "Cause" as specified in figure 8.38-10 of 3GPP [TS 29.274].

Cause-Type

4301

Enumerated

3GPP

Used to identify the type of S1AP (S1 Application Protocol) Cause in signaling between eNodeB and the Mobility Management Entity (MME). 

Enumerated Values:

0: RADIO_NETWORK_LAYER: Indicates that the cause of the failure or event is related to the Radio Network Layer. Example: handover failures, radio link failures, or congestion in the radio interface.

1: TRANSPORT_LAYER: Indicates that the failure or event is related to the Transport Layer.

Example: issues with SCTP (Stream Control Transmission Protocol) connections, IP transport problems, or signaling path failures.

2: NAS: Indicates that the failure or event is caused by Non-Access Stratum (NAS) signaling.

Example: authentication failures, NAS message integrity failures, or NAS protocol errors.

3: PROTOCOL: Indicates that the issue is related to a protocol error in the S1AP signaling layer.

Example: unexpected messages, incorrect information elements, or unsupported protocol versions.

4: MISCELLANEOUS: Used for other types of causes that do not fall into the specific categories above. Example: generic system failures, undefined errors, or internal network issues.

CMR-Flags

4317

Unsigned32 (Bitmask)

3GPP

Provides information about the reachability status of the User Equipment (UE). 

Bitmask Definition:

Bit 0: UE-Reachable-Indicator: When set (1), it indicates that the UE has become reachable or is about to become reachable.

Communication-Failure-Information

4300

Grouped

3GPP

Provides detailed information about the cause of a communication failure in mobile networks. It is used in the T6a interface, as defined in 3GPP specifications, to specify why communication between network elements or with the User Equipment (UE) has failed.

The AVP structure is defined as follows:

Cause-Type (Mandatory): Specifies the type of failure that occurred. The possible values are defined in the Cause-Type AVP, categorizing failures into radio network, transport, NAS, protocol, or miscellaneous issues.

S1AP-Cause (Optional): Indicates the cause of failure in the S1AP protocol (S1 Application Protocol) used between eNodeB and the MME. 

RANAP-Cause (Optional): Specifies the cause of failure in the RANAP protocol (Radio Access Network Application Part) used in 3G networks between RNC (Radio Network Controller) and the core network. 

BSSGP-Cause (Optional): Indicates the cause of failure in the BSSGP (Base Station System GPRS Protocol) layer, which is used in 2G GPRS networks.

GMM-Cause (Optional): Provides the cause of failure in the GMM (GPRS Mobility Management) protocol, which handles mobility and session management for GPRS users.

SM-Cause (Optional): Specifies the cause of failure in the Session Management (SM) protocol, which handles PDP context activation and data session establishment.

Connection-Action

4314

Enumerated

3GPP

Used in the T6a/b interfaces to specify the action to be performed on a T6a/b connection. 

Enumerated Values:

0: CONNECTION_ESTABLISHMENT: Indicates that the T6a/b Connection-Management-Request applies to establishing a new connection.

1: CONNECTION_RELEASE: Indicates that the T6a/b Connection-Management-Request applies to releasing an existing connection.

2: CONNECTION_UPDATE: Indicates that the T6a/b Connection-Management-Request applies to updating an existing connection’s properties.

Counter-Value

4319

Unsigned32

3GPP

Contains the number of occurrences of reception of RRC cause "MO Exception data".

Downlink-Number-Of-Packets-Allowed

4329

Unsigned32

3GPP

Contain information of octets k+9 to k+12 as specified in figure 8.38-10 of 3GPP [TS 29.274].

Downlink-Rate-Limit

4312

Unsigned32

3GPP

Contain the maximum number of NAS Data PDUs per deci hour (6 minutes) for this UE for downlink.

Extended-PCO

4313

OctetString

3GPP

Contains the value part of the ePCO IE, starting from octet 4, as specified in clause 9.9.4.26 of 3GPP [TS 24.301].

GMM-Cause

4304

Unsigned32

3GPP

Contains the GMM cause code as specified in clause 10.5.5.14 of 3GPP [TS 24.008].

Idle-Status-Indication

4322

Grouped

3GPP

Used in the T6a interface to provide information about a UE’s transition into idle mode.

The AVP structure is defined as follows:

Idle-Status-Timestamp (Optional): A timestamp indicating when the UE entered idle mode.

Active-Time (Optional): The duration (in seconds) for which the UE is expected to remain reachable before transitioning to deep sleep.

Subscribed-Periodic-RAU-TAU-Timer (Optional): Defines the periodic Tracking Area Update (TAU) or Routing Area Update (RAU) timer assigned to the UE.

eDRX-Cycle-Length (Optional): Specifies the eDRX cycle length granted to the UE by the MME/SGSN.

DL-Buffering-Suggested-Packet-Count (Optional): The suggested number of downlink packets that should be buffered for the UE.

The Subscribed-Periodic-RAU-TAU-Timer AVP shall contain the periodic TAU/RAU time granted to the UE by the MME/SGSN. The eDRX-Cycle-Length AVP shall contain the eDRX cycle length granted to the UE by the MME/SGSN. The DL-Buffering-Suggested-Packet-Count AVP shall contain the suggested number of downlink packets sent to the S-GW by the MME/SGSN.

Idle-Status-Timestamp

4323

Time

3GPP

Contain a timestamp (the time at which the UE transitioned into idle mode).

Monitoring-Event-Configuration

3122

Grouped

3GPP

Сarries monitoring event configuration data for the T6a/T6b interface. It is defined in 3GPP TS 29.336 and is used to configure monitoring events related to UE activity, location, and reachability status.

The AVP structure is defined as follows:

SCEF-Reference-ID (Optional): A unique identifier assigned by the SCEF (Service Capability Exposure Function) to track monitoring sessions.

SCEF-Reference-ID-Ext (Optional): An extended version of the SCEF-Reference-ID, used when the Extended Reference IDs feature is supported by both SCEF and MME/SGSN.

SCEF-ID (Mandatory): The Diameter Identity of the SCEF, uniquely identifying the entity responsible for the monitoring event configuration.

Monitoring-Type (Mandatory): Defines the type of monitoring event being configured (e.g., reachability, location, or mobility tracking).

SCEF-Reference-ID-for-Deletion (Optional, Multiple): A list of SCEF reference IDs that should be deleted from the monitoring session.

SCEF-Reference-ID-for-Deletion-Ext (Optional, Multiple): Extended version of SCEF-Reference-ID-for-Deletion, used when Extended Reference IDs feature is supported.

Maximum-Number-of-Reports (Optional): Specifies the maximum number of reports that should be generated for this monitoring session.

Monitoring-Duration (Optional): The validity period for the monitoring configuration, indicating how long the monitoring event should be active.

Charged-Party (Optional): Identifies the entity responsible for charging related to the monitoring session.

UE-Reachability-Configuration (Optional): Contains reachability monitoring parameters, specifying when and how the UE’s reachability status should be tracked.

Location-Information-Configuration (Optional): Defines the parameters for location-based monitoring, allowing precise tracking of UE movements.

Number-Of-UE-Per-Location-Configuration (Optional, Multiple): Specifies the number of UEs that should be monitored per configured location parameter.

When the "Extended Reference IDs" feature is supported by the SCEF and MME/SGSN, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used insted of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively.

Monitoring-Event-Report

3123

Grouped

3GPP

Contains monitoring event report data for the T6a/T6b interface, originally defined in 3GPP [TS 29.336]. It provides event-based updates related to UE reachability, connectivity status, and location.

The AVP structure is defined as follows:

SCEF-Reference-ID (Mandatory): A unique identifier assigned by the SCEF to track the monitoring event.

SCEF-Reference-ID-Ext (Optional): An extended version of the SCEF-Reference-ID, used when the Extended Reference IDs feature is supported by both SCEF and MME/SGSN.

SCEF-ID (Optional): The Diameter Identity of the SCEF, uniquely identifying the entity responsible for the monitoring event report.

Monitoring-Type (Optional): Defines the type of monitoring event being reported (e.g., reachability, location, or mobility tracking).

Reachability-Information (Optional): Provides the reachability status of the UE, indicating whether the UE is available for communication.

EPS-Location-Information (Optional): Carries location information of the UE in EPS networks, including cell ID, tracking area, and serving network details.

Communication-Failure-Information (Optional): Includes failure reasons for communication issues, such as radio network failures or protocol-related errors.

Number-Of-UE-Per-Location-Report (Optional, Multiple): Specifies the number of UEs being monitored per location report.

Loss-Of-Connectivity-Reason (Optional): Indicates the reason for loss of connectivity, such as radio signal degradation or network detach events.

Visited-PLMN-Id (Optional): Contains the identifier of the visited PLMN (Public Land Mobile Network) where the UE is currently located.

Idle-Status-Indication (Optional): Provides details about the UE transitioning into idle mode, including the timestamp of transition.

Reporting-Time-Stamp (Optional): The timestamp indicating when the monitoring event was reported.

Maximum-UE-Availability-Time (Optional): Specifies the maximum duration for which the UE is expected to remain available for communication.

PDN-Connectivity-Status-Report (Optional, Multiple): Contains information about the PDN connectivity status, including active data sessions and network attachment status.

Reachability-Cause (Optional): Indicates the reason for the current reachability status of the UE (e.g., device powered off, out of coverage, or roaming restrictions).

The AVPs applicable for each Monitoring-Type reported by the MME/SGSN are specified under 3GPP [TS 29.128] clause 5.2.2. When the "Extended Reference IDs" feature is supported by the SCEF and MME/SGSN, the SCEF-Reference-ID-Ext AVP shall be used instead of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver.

Non-IP-Data

4315

OctetString

3GPP

Contains the Non-IP data conveyed between the MME or SGSN and the SCEF.

Number-Of-Additional-Exception-Reports

4328

Unsigned32

3GPP

Contain information of octets k+5 to k+8 as specified in figure 8.38-10 of 3GPP [TS 29.274].

Number-Of-UE-Per-Location-Configuration

4306

Grouped

3GPP

Contains the location information for which the number of UEs needs to be reported by the MME/SGSN.

The AVP structure is defined as follows:

EPS-Location-Information (Mandatory): Contains detailed location information about the EPS (Evolved Packet System). Essential for determining which geographic/serving area the UE count applies to.

IMSI-Group-Id (Optional): Identifies a group of IMSIs (International Mobile Subscriber Identities).

Number-Of-UE-Per-Location-Report

4307

Grouped

3GPP

Contain the location information along with the number of UEs found at that location by the MME/SGSN.

The AVP structure is defined as follows:

EPS-Location-Information (Mandatory): Contains details of the EPS location where the UE count is being reported.

UE-Count (Mandatory): Specifies the number of UEs detected in the given EPS location.

Used to monitor network capacity utilization and traffic density.

IMSI-Group-Id (Optional): Identifies a group of IMSIs (International Mobile Subscriber Identities).

RANAP-Cause

4303

Unsigned32

3GPP

Contains the non-transparent copy of the cause value of the RANAP cause code as specified in clause 9.2.1.4 of 3GPP [TS 25.413].

Reachability-Cause

4325

Enumerated

3GPP

Indicates the reason for a UE (User Equipment) reachability event. 

Enumerated Values:

0: CHANGE_TO_CONNECTED_MODE: The UE has transitioned from an idle state to an active (connected) state.

1: REACHABLE_FOR_PAGING: The UE is now reachable for paging, indicating that it can receive paging messages.

RRC-Cause-Counter

4318

Grouped

3GPP

Tracks occurrences of the "MO Exception Data" cause in the network. It stores:

• The number of times the "MO Exception Data" cause has been received.

• The timestamp when this cause was received for the first time.

The AVP structure is defined as follows:

Counter-Value (Optional): The number of times the "MO Exception Data" cause was received.

RRC-Counter-Timestamp (Optional): The timestamp of the first occurrence of "MO Exception Data".

RRC-Counter-Timestamp

4320

Time

3GPP

Represents the timestamp when the first instance of the "MO Exception Data" cause was received.

S1AP-Cause

4302

Unsigned32

3GPP

Contains a non-transparent copy of the S1AP cause code as specified clause 9.2.1.3 of 3GPP [TS 36.413]. The RAN cause sub-category of the S1AP-Cause as specified in 3GPP [TS 36.413] shall be encoded in the Cause-Type AVP as specified in clause 6.4.5 3GPP [TS 29.128].

SCEF-Wait-Time

4316

Time

3GPP

Contains the timestamp (in UTC) until which the SCEF expects a response.

Serving-Node

2401

Grouped

3GPP

Contains the name, number, and realm of the serving node responsible for T4-triggering in Short Message Service (SMS) delivery scenarios. It is used in the T4 interface, as defined in 3GPP [TS 29.173], to provide details about the serving node currently handling the subscriber.

The AVP structure is defined as follows:

SMSF-3GPP-Name (Optional): The name of the 3GPP Short Message Service Function (SMSF) serving the subscriber.

SMSF-3GPP-Realm (Optional): The Diameter realm of the 3GPP SMSF.

SMSF-3GPP-Number (Optional): The number of the 3GPP SMSF responsible for handling SMS traffic.

SMSF-Non-3GPP-Name (Optional): The name of the Non-3GPP SMSF responsible for SMS routing.

SMSF-Non-3GPP-Realm (Optional): The Diameter realm of the Non-3GPP SMSF.

SMSF-Non-3GPP-Number (Optional): The number of the Non-3GPP SMSF responsible for SMS delivery.

SGSN-Name (Optional): The name of the Serving GPRS Support Node (SGSN).

SGSN-Realm (Optional): The Diameter realm of the SGSN.

SGSN-Number (Optional): The number of the SGSN used for SMS delivery.

MME-Name (Optional): The name of the Mobility Management Entity (MME) responsible for MT-SMS processing.

MME-Realm (Optional): The Diameter realm of the MME.

MME-Number-for-MT-SMS (Optional): The number of the MME used for Mobile-Terminated SMS.

MSC-Number (Optional): The Mobile Switching Center (MSC) number used for SMS routing.

IP-SM-GW-Number (Optional): The IP Short Message Gateway (IP-SM-GW) number, used for routing SMS messages over IP-based networks.

IP-SM-GW-Name (Optional): The name of the IP-SM-GW responsible for SMS delivery.

IP-SM-GW-Realm (Optional): The Diameter realm of the IP-SM-GW.

The following combinations are allowed:

a) SGSN-Number

b) SGSN-Name & SGSN-Realm & SGSN-Number

c) MME-Name & MME-Realm & MME-Number-for-MT-SMS

d) MSC-Number

e) MSC-Number & MME-Name & MME-Realm

f) IP-SM-GW-Number

g) IP-SM-GW-Number & IP-SM-GW-Name & IP-SM-GW-Realm

h) SMSF-3GPP-Number

i) SMSF-3GPP-Name & SMSF-3GPP-Realm & SMSF-3GPP-Number

j) SMSF-Non-3GPP-Number

k) SMSF-Non-3GPP-Name & SMSF-Non-3GPP-Realm & SMSF-Non-3GPP-Number

Serving-PLMN-Rate-Control

4310

Grouped

3GPP

Used to control the rate of uplink and downlink messages within a Serving PLMN (Public Land Mobile Network). It defines the maximum allowed rate limits for message transmission, ensuring network stability and fair resource allocation.

The rate limits are managed by the MME (Mobility Management Entity) and are specified in 3GPP [TS 23.401].

The AVP structure is defined as follows:

Uplink-Rate-Limit (Optional): Defines the maximum uplink rate (UE to network).

Downlink-Rate-Limit (Optional): Defines the maximum downlink rate (network to UE).

SM-Cause

4305

Unsigned32

3GPP

Contain the SM cause code as specified in clause 10.5.6.6 and 10.5.6.6A of 3GPP [TS 24.008].

TDA-Flags

4321

Unsigned32 (Bitmask)

3GPP

Convey status flags related to T6a/T6b-based signaling between the MME (Mobility Management Entity), SGSN (Serving GPRS Support Node), and eNodeB. It primarily reports whether downlink Non-IP Data Delivery (NIDD) was acknowledged by the eNodeB.

This AVP follows the specifications from 3GPP [TS 29.338], section 6.4.31.

Bitmask Definition:

0: Acknowledged Delivery: This bit, when set, indicates that the eNodeB has acknowledged the successful delivery of a downlink Non-IP Data Delivery (NIDD) message.

Note: Bits not defined in this table shall be cleared by the sending entity and discarded by the receiving entity.

Terminal-Information

1401

Grouped

3GPP

Used to store terminal-specific details about the user's device. This AVP originates from 3GPP [TS 29.272] and is referenced in 3GPP [TS 29.338] for T6a/T6b interfaces.

The AVP structure is defined as follows:

IMEI (Optional): The International Mobile Equipment Identity (IMEI) of the user's device.

Software-Version (Optional): The software version identifier of the terminal (corresponds to the Type Allocation Code - TAC).

UE-Count

4308

Unsigned32

3GPP

Contain the number of UEs counted against a given criteria (say location information).

Uplink-Number-Of-Packets-Allowed

4327

Unsigned32

3GPP

Contains information of octets k+1 to k+4 as specified in figure 8.38-10 of 3GPP [TS 29.274].

Uplink-Rate-Limit

4311

Unsigned32

3GPP

Contain the maximum number of NAS Data PDUs per deci hour (6 minutes) for this UE for uplink.