Name

AVP Code

Data Type

Vendor

Access-Restriction-Data

1426

Bitmask (Unsigned32)

3GPP

Defines network access restrictions for a subscriber's access to different types of radio and non-radio networks.

Indicates network access restrictions at the HSS level.

Each bit in the bitmask represents a restriction on a specific type of access.

Used by MME/SGSN to determine whether a subscriber is allowed or restricted from accessing specific RAT (Radio Access Technology) types.

Takes precedence over certain APN-level restrictions, such as WLAN offloadability.

Bitmask Definition

0: UTRAN Not Allowed: Subscriber cannot access UTRAN (3G)

1: GERAN Not Allowed: Subscriber cannot access GERAN (2G)

2: GAN Not Allowed: Subscriber cannot access GAN (Generic Access Network, UMA)

3: I-HSPA-Evolution Not Allowed: Subscriber cannot use I-HSPA Evolution

4: WB-E-UTRAN Not Allowed: Subscriber cannot access LTE (Wideband E-UTRAN)

5: HO-To-Non-3GPP-Access Not Allowed: Subscriber cannot perform handover to non-3GPP networks

6: NB-IoT Not Allowed: Subscriber cannot access NB-IoT networks

7: Enhanced Coverage Not Allowed: Subscriber cannot access Enhanced Coverage LTE (EC-LTE)

8: NR as Secondary RAT in E-UTRAN Not Allowed: Subscriber cannot use NR as a secondary RAT in LTE

9: Unlicensed Spectrum as Secondary RAT Not Allowed: Subscriber cannot use unlicensed spectrum as a secondary RAT

10: NR in 5GS Not Allowed: Subscriber cannot access 5G NR networks

11: LTE-M Not Allowed: Subscriber cannot access LTE-M (Cat-M1)

12: WB-E-UTRAN Except LTE-M Not Allowed: Subscriber cannot access Wideband E-UTRAN except LTE-M

13: WB-E-UTRAN(LEO) Not Allowed: Subscriber cannot access WB-E-UTRAN via Low-Earth-Orbit satellites

14: WB-E-UTRAN(MEO) Not Allowed: Subscriber cannot access WB-E-UTRAN via Medium-Earth-Orbit satellites

15: WB-E-UTRAN(GEO) Not Allowed: Subscriber cannot access WB-E-UTRAN via Geostationary satellites

16: WB-E-UTRAN(OTHERSAT) Not Allowed: Subscriber cannot access WB-E-UTRAN via other satellite types

17: NB-IoT(LEO) Not Allowed: Subscriber cannot access NB-IoT via Low-Earth-Orbit satellites

18: NB-IoT(MEO) Not Allowed: Subscriber cannot access NB-IoT via Medium-Earth-Orbit satellites

19: NB-IoT(GEO) Not Allowed: Subscriber cannot access NB-IoT via Geostationary satellites

20: NB-IoT(OTHERSAT) Not Allowed: Subscriber cannot access NB-IoT via other satellite types

21: LTE-M(LEO) Not Allowed: Subscriber cannot access LTE-M via Low-Earth-Orbit satellites

22: LTE-M(MEO) Not Allowed: Subscriber cannot access LTE-M via Medium-Earth-Orbit satellites

23: LTE-M(GEO) Not Allowed: Subscriber cannot access LTE-M via Geostationary satellites

24: LTE-M(OTHERSAT) Not Allowed: Subscriber cannot access LTE-M via other satellite types

Active-APN

1612

Grouped

3GPP

Provides details about dynamically established APNs on a serving node. This AVP allows the HSS (Home Subscriber Server) to restore active APNs if they are lost due to a node restart or failure.

Tracks active APNs dynamically assigned to a subscriber.

Ensures restoration of APNs if lost due to an MME/SGSN reboot.

Includes information about APN context, network selection, and mobility management.

The AVP structure is defined as follows:

Context-Identifier (Mandatory, Unsigned32): Identifies the APN context for multi-access PDU sessions.

Service-Selection (Optional, UTF8String): Indicates the APN name (e.g., internet, ims).

MIP6-Agent-Info (Optional, Grouped): Provides Mobile IP v6 agent details, as per RFC 5447.

Visited-Network-Identifier (Optional, OctetString): Identifies the visited network (e.g., PLMN ID).

Specific-APN-Info (Optional, Grouped, Multiple): Contains APN-specific settings, such as QoS profiles.

Optional compliant AVPs for extensibility.

Additional-Context-Identifier

1683

Unsigned32

3GPP

Identifies an alternative default APN when a user’s subscription profile includes multiple PDN (Packet Data Network) types.

Helps differentiate between IP-based PDNs, non-IP PDNs, and Ethernet PDNs.

Adjacent-Access-Restriction-Data

1673

Grouped

3GPP

Contains a Public Land Mobile Network (PLMN) ID and the associated Access-Restriction-Data for that PLMN.

The AVP structure is defined as follows:

Visited-PLMN-Id (Mandatory, OctetString): Contains the PLMN Identifier for the adjacent network.

Access-Restriction-Data (Mandatory, Unsigned32 (Bitmask): Contains a bitmask representing access restrictions in this PLMN.

Adjacent-PLMNs

1672

Grouped

3GPP

Contains a list of Public Land Mobile Network (PLMN) IDs where a User Equipment (UE) served by an MME/SGSN is likely to perform a handover from the current PLMN.

The AVP structure is defined as follows:

Visited-PLMN-Id (Mandatory, OctetString): Contains one or more PLMN Identifiers representing neighboring networks.

Aerial-UE-Subscription-Information

1699

Enumerated

3GPP

Indicates whether an aerial (unmanned) UE is allowed or not allowed to access the network.

Enumerated Values

0: AERIAL_UE_ALLOWED: The UE is permitted to use aerial communication services.

1: AERIAL_UE_NOT_ALLOWED: The UE is restricted from using aerial communication services.

Age-Of-Location-Information

1611

Unsigned32

3GPP

Indicates the time elapsed (in minutes) since the last network contact of a UE.

AIR-Flags

1679

Unsigned32 (Bitmask)

3GPP

Containing a bitmask that indicates specific requests from an MME or SGSN to an HSS during an Authentication-Information-Request (AIR) procedure.

Defined Bitmask Values

0: Send UE Usage Type: When set (1), the MME or SGSN requests the HSS to send the "UE Usage Type" subscription parameter.

Note: All undefined bits must be set to 0 by the sender (MME/SGSN) and ignored by the receiver (HSS).

Alert-Reason

1434

Enumerated

3GPP

Specifies the reason for an alert notification from the HSS to an MME or SGSN.

Enumeration Values

0: UE_PRESENT: The UE is present in the network.

1: UE_MEMORY_AVAILABLE: The UE has available memory, enabling it to receive new messages.

Note: The HSS selects the appropriate reason based on network conditions and UE status.

All-APN-Configurations-Included-Indicator

1428

Enumerated

3GPP

Indicates whether all APN configurations are included in the message or only the modified/added configurations.

Defined Enumeration Values

0: ALL_APN_CONFIGURATIONS_INCLUDED: The message contains all APN configurations for the subscriber.

1: MODIFIED_ADDED_APN_CONFIGURATIONS_INCLUDED: The message only contains modified or newly added APN configurations.

Note: Value 0 means the entire APN list is included, requiring a full refresh of stored APN data.

Value 1 means only changes (additions/modifications) are included, allowing incremental updates without replacing the full APN configuration.

AMBR

1435

Grouped

3GPP

AMBR (Aggregate Maximum Bit Rate) AVP defines the maximum bit rate for uplink and downlink traffic in a subscriber's profile. It is crucial for controlling the total bandwidth available to a user, ensuring fair resource distribution in LTE and 5G networks.

The AVP structure is defined as follows:

Max-Requested-Bandwidth-UL (Mandatory, Unsigned32): Specifies the maximum uplink bandwidth in bits per second (bps).

Max-Requested-Bandwidth-DL (Mandatory, Unsigned32): Specifies the maximum downlink bandwidth in bits per second (bps).

Extended-Max-Requested-BW-UL (Optional, Unsigned32): Specifies the maximum uplink bandwidth in kilobits per second (kbps) if it exceeds 4294967295 bps.

Extended-Max-Requested-BW-DL (Optional, Unsigned32): Specifies the maximum downlink bandwidth in kilobits per second (kbps) if it exceeds 4294967295 bps.

Note: AMBR AVP cannot indicate the requested bandwidth between 4294967296 and 4294967999 bits per second, and any larger value that cannot be represented in the granularity of kilobits per second.

A-MSISDN

1643

OctetString

3GPP

A-MSISDN AVP (Additional MSISDN) is an OctetString AVP that contains an alternate MSISDN associated with a subscriber.

It is encoded using TBCD (Telephony Binary Coded Decimal) format, as specified in 3GPP [TS 29.002].

This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address. 

This AVP may be present in the Subscription-Data AVP when sent within ULA. It may also be present in the Subscription-Data AVP, sent within an IDR, if the current value in the MME or SGSN needs to be changed.

APN-Configuration

1430

Grouped

3GPP

Contains information related to the user’s subscribed Access Point Name (APN) configurations. Each APN configuration is uniquely identified by the Context-Identifier.

The AVP structure is defined as follows:

Context-Identifier (Mandatory, Unsigned32): Unique ID for this APN Configuration (range 1-50 for MAP interworking).

Served-Party-IP-Address (Optional (0-2), IP Address (IPv4 / IPv6): Static IP assigned to the UE (lower 64 bits of IPv6 should be 0).

PDN-Type (Mandatory, Enumerated): Identifies PDN type (IPv4, IPv6, IPv4v6, Non-IP, Ethernet).

Service-Selection (Mandatory, UTF8String): APN name for this APN configuration.

EPS-Subscribed-QoS-Profile (Optional, Grouped): Defines subscribed QoS profile for EPS.

VPLMN-Dynamic-Address-Allowed (Optional, Enumerated): Specifies if VPLMN dynamic address allocation is allowed.

MIP6-Agent-Info (Optional, Grouped): Includes Mobile IPv6 information if applicable.

Visited-Network-Identifier (Optional, OctetString): PLMN ID where PGW was dynamically allocated.

PDN-GW-Allocation-Type (Optional, Enumerated): Defines PGW allocation (static/dynamic).

3GPP-Charging-Characteristics (Optional, OctetString): Defines charging parameters.

AMBR (Optional, Grouped): Defines APN-specific AMBR (Aggregated Maximum Bit Rate).

Specific-APN-Info (Optional (0-*), Grouped): Contains specific APN information (if required).

APN-OI-Replacement (Optional, UTF8String): Operator Identifier replacement for this APN.

SIPTO-Permission (Optional, Enumerated): Indicates if Selected IP Traffic Offload (SIPTO) is allowed.

LIPA-Permission (Optional, Enumerated): Indicates if Local IP Access (LIPA) is allowed.

Restoration-Priority (Optional, Unsigned32): Defines restoration priority for the APN.

SIPTO-Local-Network-Permission (Optional, Enumerated): Controls SIPTO offload at the local network level.

WLAN-Offloadability (Optional, Enumerated): Specifies if WLAN offload is allowed.

Non-IP-PDN-Type-Indicator (Optional, Enumerated): Specifies if Non-IP PDN Type is used.

Non-IP-Data-Delivery-Mechanism (Optional, Enumerated): Specifies the data delivery mechanism for Non-IP traffic.

SCEF-ID (Optional, UTF8String): Service Capability Exposure Function (SCEF) ID for Non-IP traffic.

SCEF-Realm (Optional, UTF8String): SCEF domain for Non-IP traffic.

Preferred-Data-Mode (Optional, Unsigned32): Preferred data mode for this APN.

PDN-Connection-Continuity (Optional, Enumerated): Defines PDN connection continuity behavior.

RDS-Indicator (Optional, Enumerated): Indicates Roaming Data Service (RDS) settings.

Interworking-5GS-Indicator (Optional, Enumerated): Defines if 5G interworking is enabled.

Ethernet-PDN-Type-Indicator (Optional, Enumerated): Indicates if Ethernet PDN Type is used.

The AMBR included in APN-Configuration shall include the AMBR associated to this specific APN configuration (APN-AMBR).

The Served-Party-IP-Address AVP may be present 0, 1 or 2 times. These AVPs shall be present if static IP address allocation is used for the UE, and they shall contain either of:

• an IPv4 address, or

• an IPv6 address/prefix, or

• both, an IPv4 address and an IPv6 address/prefix.

For the IPv6 prefix, the lower 64 bits of the address shall be set to zero.

The PDN-GW-Allocation-Type AVP applies to the MIP6-Agent-Info AVP. Therefore, it shall not be present if MIP6-Agent-Info is not present.

The APN-OI-Replacement included in this grouped AVP shall include the APN-OI-Replacement associated with this APN configuration. This APN-OI-Replacement has higher priority than UE level APN-OI-Replacement.

The Visited-Network-Identifier AVP indicates the PLMN where the PGW was allocated, in case of dynamic PGW assignment.

NOTE: If interworking with MAP is needed, the Context-Identifier will be in the range of 1 and 50.

The Non-IP-Data-Delivery-Mechanism shall only be present when Non-IP-PDN-Type-Indicator is set to TRUE (1).

The SCEF-ID AVP and the SCEF-Realm AVP shall only be present when Non-IP-PDN-Type-Indicator is set to TRUE (1), and Non-IP-Data-Delivery-Mechanism is set to SCEF-BASED-DATA-DELIVERY (1).

The RDS-Indicator may be present when Non-IP-PDN-Type-Indicator is set to TRUE (1), and Non-IP-Data-Delivery-Mechanism is set to SCEF-BASED-DATA-DELIVERY (1).

Absence of PDN-Connection-Continuity AVP indicates that the handling is left to local VPLMN policy.

APN-Configuration-Profile

1429

Grouped

3GPP

Defines a subscriber's APN configurations for Evolved Packet System (EPS). It contains multiple APN-Configuration AVPs, which individually define parameters for each subscribed Access Point Name (APN).

The AVP structure is defined as follows:

Context-Identifier (Mandatory, Unsigned32): Identifies the default APN configuration for this subscriber.

Additional-Context-Identifier (Optional, Unsigned32): Identifies an additional default APN (only for subscriptions with multiple PDN types).

Third-Context-Identifier (Optional, Unsigned32): Identifies a third default APN (for subscriptions with three PDN types: IP, Non-IP, Ethernet).

All-APN-Configurations-Included-Indicator (Mandatory, Enumerated): Indicates whether all APN configurations are included or only modified/added APNs.

APN-Configuration (Mandatory (1-*), Grouped): Defines individual APN settings (at least one required).

The Subscription-Data AVP associated with an IMSI contains one APN-Configuration-Profile AVP.

Each APN-Configuration-Profile AVP contains one or more APN-Configuration AVPs.

Each APN-Configuration AVP describes the configuration for a single APN.

Therefore, the cardinality of the relationship between IMSI and APN is one-to-many.

The Context-Identifier AVP shall identify the per subscriber's default APN configuration.

If present, the Additional-Context-Identifier AVP shall identify another default APN configuration, only for those subscriptions containing more than one types of APNs i.e. among APNs with an IP-based PDN type, APNs with a Non-IP PDN type, and APNs with an Ethernet PDN type; in this case, each of those two default APN configurations shall have a different PDN type category (e.g. one default APN with an IP-based PDN type, and another default APN with a Non-IP PDN type).

If present, the Third-Context-Identifier AVP shall identify another default APN configuration, only for those subscriptions containing more than two types of APNs i.e. among APNs with an IP-based PDN type, APNs with a Non-IP PDN type, and APNs with an Ethernet PDN type; in this case, each of those three default APN configurations shall have a different PDN type category (i.e. one default APN with an IP-based PDN type, and another default APN with a Non-IP PDN type and one default APN with an Ethernet PDN type).

APN-OI-Replacement

1431

UTF8String

3GPP

Specifies the domain name used to replace the APN Operator Identifier (APN-OI) when constructing the Access Point Name (APN). It is primarily used in non-roaming scenarios and home-routed roaming cases to ensure proper DNS resolution of APN-FQDN (Fully Qualified Domain Name).

Area-Scope

1624

Grouped

Defines a list of location identifiers that specify the geographical area relevant to a certain Diameter transaction. It includes cell identities, location areas, tracking areas, and routing areas.

The AVP structure is defined as follows:

Cell-Global-Identity (Optional, OctetString): Identifies a cell in GSM/UMTS networks.

E-UTRAN-Cell-Global-Identity (Optional, OctetString): Identifies a cell in LTE/NR networks.

Routing-Area-Identity (Optional, OctetString): Identifies a routing area in GPRS networks.

Location-Area-Identity (Optional, OctetString): Identifies a location area in GSM/UMTS.

Tracking-Area-Identity (Optional, OctetString): Identifies a tracking area in LTE/NR.

All parameters are optional but at least one must be present.

Authentication-Info

1413

Grouped

3GPP

Contains authentication vectors for E-UTRAN, UTRAN, and GERAN access networks. These vectors are used for authentication and security key derivation in LTE, 3G, and 2G networks.

The AVP structure is defined as follows:

E-UTRAN-Vector (Optional, Multiple): Contains authentication vectors for E-UTRAN (LTE) authentication. Includes RAND, XRES, AUTN, CK, IK for LTE security.

UTRAN-Vector (Optional, Multiple): Contains authentication vectors for UTRAN (3G) authentication. Includes RAND, XRES, AUTN, CK, IK for 3G security.

GERAN-Vector (Optional, Multiple): Contains authentication vectors for GERAN (2G) authentication. Includes RAND, SRES, Kc for 2G security.

AUTN

1446

OctetString

3GPP

Used in the Authentication and Key Agreement (AKA) procedure within LTE and 5G networks. It contains the authentication token generated by the Home Subscriber Server (HSS) or Authentication Center (AuC) and sent to the User Equipment (UE) during the authentication process. The AUTN AVP is used in combination with the RAND (Random Challenge) AVP to verify the authenticity of the network and to generate encryption and integrity protection keys.

Broadcast-Location-Assistance-Data-Types

1700

Bitmask (Unsigned64)

3GPP

Indicates the broadcast location assistance data types a User Equipment (UE) is subscribed to receive. These data types define ciphering keys used to decipher broadcast assistance data for positioning and location services.

Bitmask Values

0: Positioning SIB Type 1-1: UE subscribed to receive ciphering keys for SIB Type 1-1.

1: Positioning SIB Type 1-2: UE subscribed to receive ciphering keys for SIB Type 1-2.

2: Positioning SIB Type 1-3: UE subscribed to receive ciphering keys for SIB Type 1-3.

3: Positioning SIB Type 1-4: UE subscribed to receive ciphering keys for SIB Type 1-4.

4: Positioning SIB Type 1-5: UE subscribed to receive ciphering keys for SIB Type 1-5.

5: Positioning SIB Type 1-6: UE subscribed to receive ciphering keys for SIB Type 1-6.

6: Positioning SIB Type 1-7: UE subscribed to receive ciphering keys for SIB Type 1-7.

7: Positioning SIB Type 2-1: UE subscribed to receive ciphering keys for SIB Type 2-1.

8: Positioning SIB Type 2-2: UE subscribed to receive ciphering keys for SIB Type 2-2.

9: Positioning SIB Type 2-3: UE subscribed to receive ciphering keys for SIB Type 2-3.

10: Positioning SIB Type 2-4: UE subscribed to receive ciphering keys for SIB Type 2-4.

11: Positioning SIB Type 2-5: UE subscribed to receive ciphering keys for SIB Type 2-5.

12: Positioning SIB Type 2-6: UE subscribed to receive ciphering keys for SIB Type 2-6.

13: Positioning SIB Type 2-7: UE subscribed to receive ciphering keys for SIB Type 2-7.

14: Positioning SIB Type 2-8: UE subscribed to receive ciphering keys for SIB Type 2-8.

15: Positioning SIB Type 2-9: UE subscribed to receive ciphering keys for SIB Type 2-9.

16: Positioning SIB Type 2-10: UE subscribed to receive ciphering keys for SIB Type 2-10.

17: Positioning SIB Type 2-11: UE subscribed to receive ciphering keys for SIB Type 2-11.

18: Positioning SIB Type 2-12: UE subscribed to receive ciphering keys for SIB Type 2-12.

19: Positioning SIB Type 2-13: UE subscribed to receive ciphering keys for SIB Type 2-13.

20: Positioning SIB Type 2-14: UE subscribed to receive ciphering keys for SIB Type 2-14.

21: Positioning SIB Type 2-15: UE subscribed to receive ciphering keys for SIB Type 2-15.

22: Positioning SIB Type 2-16: UE subscribed to receive ciphering keys for SIB Type 2-16.

23: Positioning SIB Type 2-17: UE subscribed to receive ciphering keys for SIB Type 2-17.

24: Positioning SIB Type 2-18: UE subscribed to receive ciphering keys for SIB Type 2-18.

25: Positioning SIB Type 2-19: UE subscribed to receive ciphering keys for SIB Type 2-19.

26: Positioning SIB Type 3-1: UE subscribed to receive ciphering keys for SIB Type 3-1.

27: Positioning SIB Type 1-8: UE subscribed to receive ciphering keys for SIB Type 1-8.

28: Positioning SIB Type 2-20: UE subscribed to receive ciphering keys for SIB Type 2-20.

29: Positioning SIB Type 2-21: UE subscribed to receive ciphering keys for SIB Type 2-21.

30: Positioning SIB Type 2-22: UE subscribed to receive ciphering keys for SIB Type 2-22.

31: Positioning SIB Type 2-23: UE subscribed to receive ciphering keys for SIB Type 2-23.

32: Positioning SIB Type 2-24: UE subscribed to receive ciphering keys for SIB Type 2-24.

33: Positioning SIB Type 2-25: UE subscribed to receive ciphering keys for SIB Type 2-25.

34: Positioning SIB Type 4-1: UE subscribed to receive ciphering keys for SIB Type 4-1.

35: Positioning SIB Type 5-1: UE subscribed to receive ciphering keys for SIB Type 5-1.

Note: Bits not defined in this table must be cleared by the HSS and ignored by MME/SGSN.

Call-Barring-Info

1488

Grouped

3GPP

Used to indicate service codes for call barring services related to SMS (Short Message Service). This AVP allows an operator to configure restrictions on sending or receiving SMS messages for a subscriber.

The AVP structure is defined as follows:

SS-Code (Mandatory, OctetString): Identifies the Supplementary Service (SS) that the barring applies to.

SS-Status (Mandatory, OctetString): Specifies whether the call barring service is active or inactive.

Cancellation-Type

1420

Enumerated

3GPP

Specifies the reason for a cancellation request in the network. It is used in Cancel-Location-Request (CLR) messages sent from the HSS (Home Subscriber Server) to MME/SGSN, instructing them to remove subscriber information from their databases.

Enumerated Values

0: MME_UPDATE_PROCEDURE: Sent when Cancel Location Request (CLR) is triggered due to Update Location Request (ULR) from a new MME or UE context request from AMF.

1: SGSN_UPDATE_PROCEDURE: Sent when CLR is triggered due to ULR from a new SGSN, UE context request from AMF, or UE deregistration request from UDM.

2: SUBSCRIPTION_WITHDRAWAL: Sent when HSS removes a user's subscription, requiring MME/SGSN to clear the subscriber's data.

3: UPDATE_PROCEDURE_IWF: Used by an IWF (Interworking Function) when communicating with a pre-Release 8 HSS for interworking purposes.

4: INITIAL_ATTACH_PROCEDURE: Sent when CLR is triggered due to an Update Location Request from SGSN/MME during an initial attach procedure.

Carrier-Frequency

1696

Unsigned32

3GPP

Specifies the carrier frequency used by the UE (User Equipment). This frequency is essential for network operations, mobility management, and spectrum allocation. It is used in Diameter messages for EPS (Evolved Packet System) to communicate radio frequency information. Value should be in the range of 0..262143, see 3GPP [TS 36.331].

Cell-Global-Identity

1604

OctetString

3GPP

Uniquely identifies the radio cell where the User Equipment (UE) is currently registered. It is a key identifier used in location management, handover, and tracking in cellular networks.

The CGI value follows the 3GPP [TS 23.003] specification and is encoded as an OctetString following the format:

Mobile Country Code (MCC): 3 digits (2 Octets): Identifies the country of the network operator.

Mobile Network Code (MNC): 2 or 3 digits (1-2 Octets): Identifies the mobile operator.

Location Area Code (LAC): 2 Octets: Identifies the Location Area in which the cell is located.

Cell Identity (CI): 2 Octets: Identifies a specific cell within the location area.

Client-Identity

1480

OctetString

3GPP

Holds the ISDN number of an external client in an international E.164 number format. The number is TBCD-encoded following ITU-T Rec E.164 and 3GPP [TS 29.002].

Each digit of the phone number is represented in semi-octet format (2 digits per byte).

If the number has an odd length, the last digit is padded with F (1111 in binary).

Country Code (CC): 1-3 digits: Identifies the country (e.g., +1 for the USA).

National Destination Code (NDC): Variable: Identifies the network operator.

Subscriber Number: Variable: Identifies the individual client.

CLR-Flags

1638

Bitmask

3GPP

Used in the Cancellation-Location-Request (CLR) message on the S6a/S6d interfaces.

It provides control indicators for HSS-to-MME or HSS-to-SGSN interactions, particularly for subscriber management and reattachment procedures.

Bitmask Definitions

0: S6a/S6d-Indicator: 

• 1 CLR is sent on S6a (to MME)

• 0: CLR is sent on S6d (to SGSN).

1: Reattach-Required: 

• 1 UE must immediately reattach to the network.

• 0: No immediate reattachment required.

Notes: The S6a/S6d-Indicator flag shall be used during initial attach procedure for a combined MME/SGSN. The S6a/S6d-Indicator flag may also be sent to a standalone node.

Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

For the purpose of withdrawing "Aerial UE Subscription", HSS may send CLR with CLR-Flag set to Reattach-Required.

Collection-Period-RRM-LTE

1657

Enumerated

3GPP

Defines the time interval for collecting measurement samples related to Radio Resource Management (RRM) measurements in LTE networks.

This parameter is mandatory if the job type is set to Immediate MDT or Immediate MDT and Trace and any of the bits 2 (M2) or 3 (M3) of the list of measurements parameter (defined in Section 5.10.3 [TS 32.422]) in LTE is set to 1. The parameter is used only in case of RAN side measurements whose configuration is determined by RRM.

This measurement parameter defines the collection period that should be used to collect available measurement samples in case of RRM configured measurements. The same collection period should be used for all such measurements that are requested in the same MDT or combined Trace and MDT job.

Enumerated Values

0: 1024 ms

1: 1280 ms

2: 2048 ms

3: 2560 ms

4: 5120 ms

5: 10240 ms

6: 1 minute

Collection-Period-RRM-UMTS

1658

Enumerated

3GPP

Defines the time interval for collecting measurement samples related to Radio Resource Management (RRM) measurements in UMTS networks.

This parameter is mandatory if the job type is set to Immediate MDT or Immediate MDT and Trace and any of the bits 3 (M3), 4 (M4), 5 (M5) of the list of measurements parameter (defined in Section 5.10.3 [TS 32.422]) in UMTS is set to 1. The parameter is used only in case of RAN side measurements whose configuration is determined by RRM. This measurement parameter defines the collection period that should be used to collect available measurement samples in case of RRM configured measurements. The same collection period should be used for all such measurements that are requested in the same MDT or combined Trace and MDT job.

Enumerated Values

0: 250 ms

1: 500 ms

2: 1000 ms

3: 2000 ms

4: 3000 ms

5: 4000 ms

6: 6000 ms

7: 8000 ms

8: 12000 ms

9: 16000 ms

10: 20000 ms

11: 24000 ms

12: 28000 ms

13: 32000 ms

14: 64000 ms

Some values may not be always available e.g., due to the large amount of logging they would generate in a highly loaded network. The selection of a specific subset of supported values at the RNC is vendor-specific.

Complete-Data-List-Included-Indicator

1468

Enumerated

3GPP

Indicates whether the full list of PDP contexts is included in a message or only the modified/added PDP contexts.

Enumerated Values:

0: All_PDP_CONTEXTS_INCLUDED: The full list of PDP contexts is included.

1: MODIFIED_ADDED_PDP_CONTEXTS_INCLUDED: Only modified or newly added PDP contexts are included.

Context-Identifier

1423

Unsigned32

3GPP

Used to uniquely identify a specific APN configuration within a subscriber's profile.

Core-Network-Restrictions

1704

Unsigned32 (Bitmask)

3GPP

Contains a bitmask indicating whether access to certain core network types is restricted for a user.

Bitmask Definitions

0: Reserved: Deprecated. This bit is ignored by the MME.

1: 5GC Not Allowed: If set to 1, access to the 5G Core (5GC) is not allowed for the user.

Note: Bits not defined in this table shall be cleared by the HSS and discarded by the MME.

Coupled-Node-Diameter-ID

1666

DiameterIdentity

3GPP

Contains the Diameter identity of the coupled node in S6a or S6d interfaces as specified in 3GPP [TS 23.003] clause 19.4.2.4 and 19.4.2.6.

CSG-Id

1437

Unsigned32

3GPP

Represents a Closed Subscriber Group (CSG) Identifier. It is used to identify CSG cells where only authorized subscribers can connect. Values are coded according to 3GPP [TS 23.003]. Unused bits (least significant) shall be padded with zeros.

CSG-Subscription-Data

1436

Grouped

3GPP

Contains information about a subscriber's Closed Subscriber Group (CSG) subscription. It specifies which CSGs the subscriber is allowed to access, along with additional information such as expiration date, visited PLMN, and allowed services. This AVP is essential for managing access control to femtocell or small cell networks, where CSG IDs define restricted access areas within the mobile network.

The AVP structure is defined as follows:

CSG-Id (Mandatory): Identifies the Closed Subscriber Group (CSG) to which the subscriber belongs. Used by the MME and SGSN to enforce access restrictions for the subscriber.

Expiration-Date (Optional): Defines the validity period of the CSG subscription. If set, access to the CSG is granted only until this date.

Service-Selection (Optional, Multiple): Specifies the list of services the subscriber is permitted to use while connected to this CSG.

Visited-PLMN-Id (Optional): Identifies the Visited Public Land Mobile Network (PLMN) in which the CSG is being accessed. If not present, the CSG-Subscription-Data applies to the subscriber’s home PLMN.

Current-Location-Retrieved

1610

Enumerated

3GPP

Indicates whether the most recent location information of a User Equipment (UE) has been successfully retrieved.

Enumerated Values:

0: ACTIVE-LOCATION-RETRIEVAL: Location was obtained after successful paging (idle mode) or direct retrieval from the eNB (connected mode).

This value is used when location information was obtained after a successful paging procedure for Active Location Retrieval when the UE is in idle mode or after retrieving the most up-to-date location information from the eNB when the UE is in connected mode.

Daylight-Saving-Time

1650

Enumerated

3GPP

Indicates the Daylight Saving Time (DST) (in steps of 1 hour) used to adjust for summertime the time zone of the location where the UE is attached in the visited network.

Enumerated Values:

0: NO_ADJUSTMENT: No daylight saving adjustment is applied.

1: PLUS_ONE_HOUR_ADJUSTMENT: Time zone is adjusted by +1 hour.

2: PLUS_TWO_HOURS_ADJUSTMENT: Time zone is adjusted by +2 hours.

DL-Buffering-Suggested-Packet-Count

1674

Integer32

3GPP

Used to indicate whether extended buffering of downlink packets at the Serving Gateway (SGW) should be requested or not for a High Latency Communication user.

Additionally, it may suggest the number of packets to be buffered.

Defined Values

0: Extended DL Data Buffering NOT REQUESTED: The SGW should NOT buffer additional downlink packets for this UE.

-1: Extended DL Data Buffering REQUESTED, without a suggested number of packets: The SGW should buffer packets but with no specific limit.

> 0: Extended DL Data Buffering REQUESTED, with a suggested number of packets: The SGW should buffer up to the specified number of packets.

DSA-Flags

1422

Unsigned32 (Bitmask)

3GPP

Indicates network node area restrictions due to regional subscription policies.

Defined Bit Flags:

0: Network Node Area Restricted: If set, the complete Network Node area (SGSN area) is restricted due to regional subscription rules.

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

DSR-Flags

1421

Unsigned32 (Bitmask)

3GPP

Specifies various withdrawal actions for subscriber data in the MME or SGSN.

Defined Bit Flags:

0: Regional Subscription Withdrawal: Deletes the regional subscription from subscriber data.

1: Complete APN Configuration Profile Withdrawal: Deletes all EPS APN configuration data (only applies to S6d interface).

2: Subscribed Charging Characteristics Withdrawal: Deletes charging characteristics from the subscription data.

3: PDN Subscription Contexts Withdrawal: Deletes specific PDN subscription contexts identified by the Context-Identifier AVP.

4: STN-SR: Deletes the Session Transfer Number for SRVCC from the subscriber data.

5: Complete PDP Context List Withdrawal: Deletes all PDP contexts for the subscriber.

6: PDP Contexts Withdrawal: Deletes specific PDP contexts identified by the Context-Identifier AVP.

7: Roaming Restricted Due to Unsupported Feature: Removes roaming restriction from the subscriber data.

8: Trace Data Withdrawal: Deletes Trace Data from subscriber data.

9: CSG Deleted: Deletes CSG-Subscription-Data in MME/SGSN (applies to both S6a/S6d and S7a/S7d interfaces).

10: APN-OI-Replacement: Deletes the UE-level APN-OI-Replacement from subscriber data.

11: GMLC List Withdrawal: Deletes the LCS GMLC List from MME/SGSN.

12: LCS Withdrawal: Deletes the LCS service identified by the SS-Code AVP from MME/SGSN.

13: SMS Withdrawal: Deletes the SMS service identified by the SS-Code AVP or TS-Code AVP.

14: Subscribed Periodic RAU-TAU Timer Withdrawal: Deletes the RAU/TAU timer from the subscriber data.

15: Subscribed VSRVCC Withdrawal: Deletes the Subscribed VSRVCC from subscriber data.

16: A-MSISDN Withdrawal: Deletes the Additional MSISDN (A-MSISDN) from subscriber data.

17: ProSe Withdrawal: Deletes the ProSe subscription data from MME/SGSN.

18: Reset-IDs: Deletes the set of Reset-IDs from MME/SGSN.

19: DL-Buffering-Suggested-Packet-Count Withdrawal: Deletes the DL Buffering Suggested Packet Count from MME/SGSN.

20: Subscribed IMSI-Group-Id Withdrawal: Deletes all IMSI-Group-Id(s) from MME/SGSN.

21: Delete Monitoring Events: Deletes all monitoring events associated with the provided SCEF-ID.

22: User Plane Integrity Protection Withdrawal: Indicates User Plane Integrity Protection may no longer be required (only applies to SGSN).

23: MSISDN Withdrawal: Deletes the MSISDN from subscriber data (also removes monitoring events tied to MSISDN).

24: UE Usage Type Withdrawal: Deletes the UE Usage Type from subscription data.

25: V2X Withdrawal: Deletes the V2X subscription data from MME/SGSN.

26: External-Identifier-Withdrawal: Deletes External Identifier from subscriber data.

27: Aerial-UE-Subscription Withdrawal: Deletes the Aerial UE subscription from subscriber data.

28: Paging Time Window Subscription Withdrawal: Deletes the Paging Time Window subscription from subscriber data.

29: Active-Time-Withdrawal: Deletes the Active Time used for PSM from subscriber data.

30: eDRX-Cycle-Length Withdrawal: Deletes the eDRX-Cycle-Length from subscriber data.

31: Service-Gap-Time Withdrawal: Deletes the Service Gap Time from subscriber data.

Notes: If the Complete APN Configuration Profile Withdrawal bit is set, this bit should not be set. 

If the Complete PDP context list Withdrawal bit is set, this bit should not be set.

Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

Bits 3 and 6 are excluding alternatives and shall not both be set.

When this AVP is transferred over the S7a/S7d interface, only the bit 9 (CSG Deleted) is meaningful, other bits shall be cleared.

eDRX-Cycle-Length

1691

Grouped

3GPP

Specifies an Extended Discontinuous Reception (eDRX) cycle length for a specific RAT type (e.g., E-UTRAN, NB-IoT). It helps optimize power saving for IoT devices by reducing the frequency of paging and network communication.

The AVP structure is defined as follows:

RAT-Type (Mandatory, Enumerated): Defines the RAT (Radio Access Technology) Type for which the eDRX cycle applies (e.g., LTE, NB-IoT).

eDRX-Cycle-Length-Value (Mandatory, OctetString): Encodes the eDRX cycle length based on 3GPP [TS 29.274].

eDRX-Cycle-Length-Value

1692

OctetString

3GPP

Specifies the Extended Discontinuous Reception (eDRX) cycle value for a specific RAT type. It is used for power-saving mode in IoT and LTE/5G networks.

The contents of eDRX-Cycle-Length-Value shall consist of 1 octet.

The encoding shall be as defined in 3GPP [TS 24.008], clause 10.5.5.32, and it shall only contain the value of the field "eDRX value" for a given RAT type, i.e., the 4 least significant bits of the octet in this AVP shall contain bits 1-4 of octet 3 in the "Extended DRX parameter" IE, and the 4 most significant bits of the octet in this AVP shall be set to 0.

eDRX-Related-RAT

1705

Grouped

3GPP

Specifies the Radio Access Technology (RAT) type to which the Extended Discontinuous Reception (eDRX) Cycle Length applies.

The AVP structure is defined as follows:

RAT-Type (Required, Multiple): Identifies the Radio Access Technology (RAT) types associated with eDRX. Possible values include:

1: UTRAN: (Universal Terrestrial Radio Access Network)

2: GERAN: (GSM EDGE Radio Access Network)

3: WLAN: (Wireless Local Area Network)

4: GAN: (Generic Access Network)

5: HSPA-Evolution

6: E-UTRAN (LTE)

7: NB-IoT (Narrowband IoT)

8: NR (New Radio, 5G)

Emergency-Info

1687

Grouped

3GPP

Contains information about the Packet Data Network Gateway (PDN-GW) used for establishing emergency PDN connections. It ensures that emergency services can be provided with a dedicated PDN-GW when required. 

The AVP structure is defined as follows:

MIP6-Agent-Info (Optional): Contains information about the PDN Gateway (PGW) used for emergency PDN connections.

EPS-Location-Information

1496

Grouped

3GPP

Provides location-related information for a subscriber in the Evolved Packet System (EPS). This AVP helps in tracking the user's network location, either via the MME (Mobility Management Entity) or the SGSN (Serving GPRS Support Node), enabling efficient network operations and seamless mobility management.

The AVP structure is defined as follows:

MME-Location-Information (Optional): Contains the location information related to the MME in the EPS network. Includes Tracking Area Identity (TAI), Cell Identity (ECGI), and additional mobility data.

SGSN-Location-Information (Optional): Contains the location information related to the SGSN when the UE is in 3G (UTRAN/GERAN) mode. Includes Routing Area Identity (RAI), Cell Global Identity (CGI), and additional SGSN-specific data.

EPS-Subscribed-QoS-Profile

1431

Grouped

3GPP

Contains the bearer-level Quality of Service (QoS) parameters associated with the default bearer for an Access Point Name (APN) in Evolved Packet System (EPS). It ensures that a user’s subscription includes the appropriate QoS Class Identifier (QCI) and Allocation Retention Priority (ARP) for efficient traffic handling in LTE networks.

The AVP structure is defined as follows:

QoS-Class-Identifier (Mandatory): Defines the QoS Class Identifier (QCI) for the subscribed default bearer. This AVP defined in 3GPP [TS 29.212] as an Enumerated. Specifies the QoS characteristics such as priority, packet delay budget, and packet loss rate. The values permitted for this AVP over the S6a/S6d interface are restricted to non-GBR (Guaranteed Bit Rate) bearers only, as defined in 3GPP [TS 23.008]. Values QCI_1, QCI_2, QCI_3 and QCI_4, which are associated to GBR bearers, cannot be sent over S6a/S6d.

Allocation-Retention-Priority (Mandatory): Determines the priority level for resource allocation and retention in case of network congestion. Consists of:

• Priority Level (PL): Defines the importance of retaining or allocating the bearer.

• Pre-emption Capability: Whether the bearer can take resources from another lower-priority bearer.

• Pre-emption Vulnerability: Whether this bearer can have its resources taken by a higher-priority bearer.

EPS-User-State

1495

Grouped

3GPP

Contains the user state information in the Mobility Management Entity (MME) and/or Serving GPRS Support Node (SGSN) within an Evolved Packet System (EPS) network. This AVP allows network elements to determine whether a user is currently attached, connected, or unreachable, aiding in mobility management and session handling.

The AVP structure is defined as follows:

MME-User-State (Optional): Indicates the user’s state in the MME, defining whether the UE (User Equipment) is in an attached, detached, or connected state in the LTE network.

SGSN-User-State (Optional): Represents the user's state in the SGSN, primarily used when the UE is operating in GERAN/UTRAN (2G/3G) networks.

Equipment-Status

1445

Enumerated

3GPP

Defines the current status of a User Equipment (UE) in the network. It is primarily used for IMEI-based device authorization and helps the network determine whether the device is allowed or restricted from accessing services.

Enumerated Values

0: PERMITTEDLISTED: The device is whitelisted and can access the network.

1: PROHIBITEDLISTED: The device is blacklisted and cannot access the network.

Equivalent-PLMN-List

1637

Grouped

3GPP

Contains a list of equivalent Public Land Mobile Network (PLMN) IDs associated with the registered PLMN (visited PLMN) of the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN). This AVP provides information on networks that are considered equivalent for roaming and service continuity.

The AVP structure is defined as follows:

Visited-PLMN-Id (Mandatory, Repeating): A list of PLMN IDs (encoded as OctetString) that are equivalent to the visited PLMN.

Error-Diagnostic

1614

Enumerated

3GPP

Provides additional information about an error condition in response to a Diameter request. It helps diagnose subscription-related or roaming-related failures when a Diameter Experimental-Error AVP is present.

Enumerated Values

0: GPRS_DATA_SUBSCRIBED: Used when the Experimental-Error is DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION, but the user has a GPRS subscription.

1: NO_GPRS_DATA_SUBSCRIBED: Used when the Experimental-Error is DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION, and the user does not have GPRS subscription data.

2: ODB_ALL_APN: Used when the Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED, and the Operator Determined Barring (ODB) restricts all packet-oriented services.

3: ODB_HPLMN_APN: Used when the Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED, and the ODB restricts access to home PLMN APNs (HPLMN-AP barred).

4: ODB_VPLMN_APN: Used when the Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED, and the ODB restricts access to visited PLMN APNs (VPLMN-AP barred).

Ethernet-PDN-Type-Indicator

1707

Enumerated

3GPP

Specifies whether the APN (Access Point Name) is configured as an Ethernet PDN (Packet Data Network) type.

Enumerated Values:

0: FALSE: The APN does not have an Ethernet PDN type. This is the default behavior when the AVP is absent.

1: TRUE: The APN has an Ethernet PDN type, and the PDN-Type AVP inside APN-Configuration AVP must be ignored.

E-UTRAN-Cell-Global-Identity

1602

OctetString

3GPP

Contains the E-UTRAN Cell Global Identification (ECGI) of the user, which uniquely identifies the LTE/5GNR cell where the User Equipment (UE) is registered as specified in 3GPP [TS 23.003]. Octets are coded as described in 3GPP [TS 29.002]. The first 3 octets contain the PLMN ID (MCC+MNC). The remaining 4 octets store the ECI in big-endian format.

E-UTRAN-Vector

1414

Grouped

3GPP

Contains authentication and key agreement parameters for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) authentication procedures.

The AVP structure is defined as follows:

Item-Number (Optional, Unsigned32): Identifies the sequence number of the vector.

Used to keep track of authentication vector ordering.

RAND (Mandatory, OctetString): A random challenge value used in the authentication process. Generated by the Home Subscriber Server (HSS).

XRES (Mandatory, OctetString): The expected response (XRES) computed from RAND and shared with the serving network. Compared with the UE’s computed response to authenticate the subscriber.

AUTN (Mandatory, OctetString): The authentication token generated by the HSS. Sent to the UE to allow it to verify network authenticity.

KASME (Mandatory, OctetString): The Access Security Management Entity (KASME) key, derived from RAND and other security parameters. 

Event-Threshold-Event-1F

1661

Integer32

3GPP

Defines the event threshold for Event 1F measurements used in Minimization of Drive Tests (MDT) and radio resource management (RRM) in LTE/5G networks, see 3GPP [TS 32.422].

This AVP is used when Immediate MDT (Minimization of Drive Tests) or Combined Trace and Immediate MDT is activated. It specifies the signal strength threshold that must be reached before an event-based report is triggered.

The allowed value range depends on the specific measurement type.

CPICH RSCP (Received Signal Code Power): -120 to 25 dBm

CPICH Ec/No (Energy per chip to total noise ratio): -24 to 0 dB

Pathloss: 30 to 165 dB

Event-Threshold-Event-1I

1662

Integer32

3GPP

Defines the threshold for reporting UMTS M2 measurements when an Event 1I reporting trigger is configured.

It specifies the Timeslot ISCP (Interference Signal Code Power) threshold that must be exceeded before a measurement report is triggered. 

The allowed value range (3GPP [TS 32.422]) for this AVP is between -120 and -25.

Detailed definition of the parameter is in 3GPP [TS 25.331] section 14.1.3.3.

Event-Threshold-RSRP

1629

Unsigned32

3GPP

Defines the threshold for reporting Reference Signal Received Power (RSRP) measurements in LTE and NR (5G) networks. Mandatory if the report trigger parameter is configured for A2 event reporting or A2 event-triggered periodic reporting. The job type must be set to Immediate MDT or combined Immediate MDT and Trace.

Used in Minimization of Drive Tests (MDT) and subscriber location tracking.

Allowed Values (3GPP [TS 32.422]):

LTE (4G): 0 – 97: 3GPP [TS 36.331]

NR (5G): 0 – 127: 3GPP [TS 38.331]

These values represent RSRP threshold levels for triggering event-based reporting.

Event-Threshold-RSRQ

1630

Unsigned32

3GPP

Defines the threshold for reporting Reference Signal Received Quality (RSRQ) measurements in LTE and NR (5G) networks. Mandatory if the report trigger parameter is configured for A2 event reporting or A2 event-triggered periodic reporting. The job type must be set to Immediate MDT or combined Immediate MDT and Trace.

Used in Minimization of Drive Tests (MDT) and network performance monitoring.

Allowed Values (3GPP [TS 32.422]):

LTE (4G): 0 – 34: 3GPP [TS 36.331]

NR (5G): 0 – 127: 3GPP [TS 38.331]

These values represent RSRQ threshold levels for triggering event-based reporting.

Expiration-Date

1439

Time

3GPP

Used in Closed Subscriber Group (CSG) subscription management. It specifies the exact timestamp when a user's subscription to a CSG-ID (Closed Subscriber Group Identifier) expires.

External-Client

1479

Grouped

3GPP

Contains the identities of external clients authorized to locate a target UE (User Equipment) for a Mobile Terminated Location Request (MT-LR). This AVP is used in location-based services (LBS) to regulate which external entities can request the position of a specific UE. It ensures that only authorized clients have access to location data, enforcing network policies on location privacy and notification requirements.

The AVP structure is defined as follows:

Client-Identity (Mandatory): This field identifies the external client requesting the location of the target UE. It is typically represented as a string containing an identity value that uniquely distinguishes the client.

GMLC-Restriction (Optional): Specifies restrictions applied by the Gateway Mobile Location Center (GMLC) when processing location requests. This AVP enforces limitations based on network policies, regulating whether the external client can access location data under specific conditions.

Notification-To-UE-User (Optional): Indicates whether the target UE user should be notified about the location request. This ensures compliance with privacy regulations by allowing the UE user to be informed of external location queries.

Other AVPs may be included for extensibility, allowing additional parameters to be specified depending on network implementation and regulatory requirements.

Ext-PDP-Address

1621

Address

3GPP

Represents an additional data protocol address. It is used when the PDP (Packet Data Protocol) supports dual-stack (IPv4v6).

Ext-PDP-Type

1620

OctetString

3GPP

Specifies the type of Packet Data Protocol (PDP) context. It is primarily used when a dual-stack (IPv4v6) PDP context is assigned to a subscriber. Octets are coded according to 3GPP [TS 29.002] and 3GPP [TS 29.060] and shall contain the value of IPv4v6.

5QI

1713

Integer32

3GPP

Specifies the QoS characteristics of a PDU session in 5G networks. It shall contain the 5QI. See 3GPP [TS 23.501] for allowed values. If the 5QI is used in PC5 QoS parameter, it shall contain PQI, PQI is a special 5QI (see clause 5.4.2.1 of 3GPP [TS 23.287]).

Geodetic-Information

1609

OctetString

3GPP

Contains the geodetic location of a user, providing latitude, longitude, and altitude coordinates. The encoding format of Geodetic Location follows the specifications in 3GPP [TS 29.002], ensuring compatibility with various location-based services (LBS).

Geographical-Information

1608

OctetString

3GPP

Contains the geographical Information of the user. For details and octet encoding, see 3GPP [TS 29.002].

GERAN-Vector

1416

Grouped

3GPP

Holds authentication vector information for GERAN (GSM EDGE Radio Access Network). It is used in authentication and key agreement (AKA) procedures for GSM and EDGE networks.

The AVP structure is defined as follows:

RAND (Mandatory, OctetString): Random challenge value for AKA authentication.

SRES (Mandatory, OctetString): Signed response used for authentication verification.

Kc (Mandatory, OctetString): Cipher key for encrypting GSM traffic.

GMLC-Number

1474

OctetString

3GPP

Contains the ISDN number of the GMLC in international number format as described in [ITU-T Rec E.164] and shall be encoded as a TBCD-string. See 3GPP [TS 29.002] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

GMLC-Restriction

1481

Enumerated

3GPP

Specifies the level of restriction applied to location-based services (LBS) using the Global Mobile Location Center (GMLC). It determines whether location retrieval requests are restricted to a specific GMLC list or are limited to requests from within the home country.

Enumerated Values

0: GMLC_LIST: Only GMLCs from a predefined list can request location information.

1: HOME_COUNTRY: Only GMLCs from the subscriber's home country can request location information.

GPRS-Subscription-Data

1467

Grouped

3GPP

Contains user profile information relevant to GPRS (General Packet Radio Service). It is used in the Diameter S6a/S6d interfaces within the Evolved Packet System (EPS) to store subscription data related to packet-switched services. This AVP is primarily exchanged between the Home Subscriber Server (HSS) and the Mobility Management Entity (MME) during subscriber authentication and profile management procedures.

The AVP structure is defined as follows:

Complete-Data-List-Included-Indicator (Mandatory): Indicates whether the full list of PDP-Context AVPs is included in the message. 

PDP-Context (Mandatory, Multiple: 1–50 instances): Represents individual Packet Data Protocol (PDP) contexts, which define specific packet-switched data sessions for the subscriber. Each PDP-Context AVP contains information about an active or provisioned PDP session, including attributes like the APN (Access Point Name), QoS (Quality of Service) profile, and IP address allocation method.

The number of PDP-Context AVPs is limited by the maxNumOfPDP-Contexts value as specified in 3GPP [TS 29.002].

Other AVPs may be included for extensibility, allowing operators to define additional attributes related to GPRS subscription policies.

Group-PLMN-Id

1677

OctetString

3GPP

Contain the concatenation of MCC and MNC as of 3GPP [TS 23.003]. 

The content of this AVP shall be encoded as an octet string according to [Table 7.3.191-1]:

Bit Position     Octet 1             Octet 2           Octet 3

Bits 8-5           MCC Digit 2     MNC Digit 3     MNC Digit 2

Bits 4-1           MCC Digit 1     MCC Digit 3     MNC Digit 1

See 3GPP [TS 24.008], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111".

Group-Service-Id

1676

Unsigned32

3GPP

Used to identify a specific service for which an IMSI-Group-Id is utilized.

Defined Values

1: Group-specific NAS-level congestion control

2: Group-specific monitoring of UE count in a geographical area

Values greater than 1000 are reserved for home operator specific use. IMSI-Group-IDs with a Group-Service-Id in this range shall not be sent outside the HPLMN unless roaming agreements allow so.

Guaranteed-Flow-Bitrates

1715

Integer32

3GPP

Indicates the guaranteed bits delivered for the PC5 QoS flow by UE over the PC5 interface within a period of time. The unit of Guaranteed-Flow-Bitrates is bits/s.

Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions

1498

Enumerated

3GPP

Indicates whether IMS Voice over Packet-Switched (PS) Sessions is uniformly supported across all Tracking Areas (TAs) or Routing Areas (RAs) associated with the serving node for a given subscriber. This AVP is relevant for determining whether a subscriber can utilize IMS-based voice services consistently across the network, including when roaming.

Enumerated Values:

0: NOT_SUPPORTED: indicates that "IMS Voice over PS Sessions" is not supported, homogeneously, in any of the TAs or RAs associated to the serving node for the served subscribers including consideration on roaming relationship for IMS Voice over PS.

1: SUPPORTED: indicates that "IMS Voice over PS Sessions" is supported, homogeneously, in all of the TAs or RAs associated to the serving node for the served subscriber including consideration on roaming relationship for IMS Voice over PS.

If this AVP is not present in the command, it indicates that there is no homogeneous support of IMS Voice Over PS Sessions on all the TA/RAs of the serving node, or that the homogeneity of this support is unknown to the serving node.

NOTE: In order to ensure the T-ADS by HPLMN, MME or SGSN is expected to either set Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP to "NOT_SUPPORTED (0)", or not to set this AVP for inbound roaming subscribers if there is no IMS Voice over PS roaming relationship with the HPLMN.

HPLMN-ODB

1418

Unsigned32 (Bitmask)

3GPP

Used to indicate operator-imposed restrictions on a subscriber for specific services within the Home Public Land Mobile Network (HPLMN).

Bitmask Definitions

0: HPLMN-specific barring type 1

1: HPLMN-specific barring type 2

2: HPLMN-specific barring type 3

3: HPLMN-specific barring type 4

HPLMN-ODB may apply to mobile originated short messages; See 3GPP [TS 23.015].

IAB-Operation-Permission

1709

Enumerated

3GPP

Used to indicate whether a User Equipment (UE) is allowed to operate as an Integrated Access and Backhaul (IAB) node in the network. Defines whether the UE is authorized to participate in IAB-based communication. Used in MME (Mobility Management Entity) or SGSN (Serving GPRS Support Node) to apply network policies.

Defined in 3GPP [TS 23.401].

Enumerated Values

0: IAB_OPERATION_ALLOWED: UE is allowed for IAB operation.

1: IAB_OPERATION_NOTALLOWED: UE is not allowed for IAB operation.

ICS-Indicator

1491

Enumerated

3GPP

Indicates whether the IMS Centralized Services (ICS) architecture is applied to a subscriber’s IMS (IP Multimedia Subsystem) session. The meaning of the values is defined in 3GPP [TS 23.292] and 3GPP [TS 23.216].

Enumerated Values

0: FALSE: ICS is not applied to the IMS session.

1: TRUE: ICS is applied, and IMS must handle calls accordingly.

IDA-Flags

1441

Unsigned32 (Bitmask)

3GPP

Used in Insert Subscriber Data Answer (IDA) messages. It provides network restriction information, particularly about regional subscription limitations.

Bitmask Table

0: Network Node Area Restricted: If set (1), indicates that the entire SGSN area is restricted due to regional subscription policies.

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

IDR-Flags

1490

Unsigned32 (Bitmask)

3GPP

Used in Insert Subscriber Data Request (IDR) messages. It provides various status and request indicators related to subscriber data, UE reachability, location, and IMS Voice over PS Sessions.

Bitmask Table:

0: UE Reachability Request: If set (1), MME/SGSN must notify HSS when UE becomes reachable.

1: T-ADS Data Request: If set (1), HSS requests the IMS Voice over PS Sessions support status, RAT Type, and timestamp of the last radio contact.

2: EPS User State Request: If set (1), HSS requests current user state from MME/SGSN.

3: EPS Location Information Request: If set (1), HSS requests EPS location information from MME/SGSN.

4: Current Location Request: If set (1), MME/SGSN must page the UE to provide real-time location information (only used with bit 3).

5: Local Time Zone Request: If set (1), HSS requests current local time zone of the UE’s visited network.

6: Remove SMS Registration: If set (1), MME must unregister for SMS services.

7: RAT-Type Requested: If set (1), MME/SGSN must provide RAT Type corresponding to EPS location info (only used with bit 3).

8: P-CSCF Restoration Request: If set (1), MME/SGSN must perform HSS-based P-CSCF restoration procedures as per 3GPP [TS 23.380] clause 5.4.

IMEI

1402

UTF8String

3GPP

Used to store the International Mobile Equipment Identity (IMEI) as specified in 3GPP [TS 23.003]. It should consist of 14 digits, including the 8-digit Type Allocation Code (TAC) and the 6-digit Serial Number (SNR). It may also include a 15th digit (Check Digit (CD) / Spare Digit (SD)).

Immediate-Response-Preferred

1412

Unsigned32

3GPP

Indicates whether an immediate response is preferred when requesting authentication vectors. The presence of this AVP implies a preference for an immediate response, whereas its absence indicates that an immediate response is not preferred. If this AVP is present, its actual value is not significant.

When EUTRAN-AVs and UTRAN-AVs or GERAN-AVs are requested, presence of this AVP within the Requested-EUTRAN-Authentication-Info AVP shall indicate that EUTRAN-AVs are requested for immediate use in the MME/SGSN; presence of this AVP within the Requested-UTRAN-GERAN-Authentication-Info AVP shall indicate that UTRAN-AVs or GERAN-AVs are requested for immediate use in the MME/SGSN. It may be used by the HSS to determine the number of vectors to be obtained from the AuC and the number of vectors downloaded to the MME or SGSN.

IMSI-Group-Id

1675

Grouped

3GPP

Contains information about the IMSI-Group-Id, which is used to categorize users based on their IMSI within a specific service or operator-defined grouping.

The AVP structure is defined as follows:

Group-Service-Id (Mandatory, Unsigned32): Identifies the specific service for the IMSI-Group-Id.

Group-PLMN-Id (Mandatory, OctetString): Concatenation of MCC and MNC in octet format.

Local-Group-Id (Mandatory, OctetString): Local identifier for IMSI grouping within an operator.

For details see 3GPP [TS 23.003], clause 19.9).

IMS-Voice-Over-PS-Sessions-Supported

1492

Enumerated

3GPP

Indicates whether IMS Voice over Packet-Switched (PS) Sessions is supported by the UE’s most recently used Tracking Area (TA) or Routing Area (RA) in the serving node.

Enumerated Values:

0: NOT_SUPPORTED: IMS Voice over PS Sessions is not supported by the UE’s last used TA/RA.

1: SUPPORTED: IMS Voice over PS Sessions is supported by the UE’s last used TA/RA.

Interworking-5GS-Indicator

1706

Enumerated

3GPP

Signals whether the interworking between 5G System (5GS) and Evolved Packet System (EPS) is subscribed or not subscribed for a given APN.

Enumerated Values:

0: NOT-SUBSCRIBED: The UE does not have an interworking subscription between EPS and 5GS for this APN.

1: SUBSCRIBED: The UE is subscribed for EPS-5GS interworking for this APN.

The default value when this AVP is not present is NOT-SUBSCRIBED (0).

Item-Number

1419

Unsigned32

3GPP

Used to order authentication vectors (AVs) received within one request.

Job-Type

1623

Enumerated

3GPP

Specifies the type of data collection job to be activated in the mobile network, particularly in Minimization of Drive Tests (MDT) and radio network tracing.

Enumerated Values

0: Immediate MDT only: Immediate MDT collection, capturing real-time measurements.

1: Logged MDT only: Logged MDT collection for later retrieval.

2: Trace only: Traditional trace job without MDT.

3: Immediate MDT and Trace: Simultaneous execution of Immediate MDT and Trace.

4: RLF reports only: Collection of Radio Link Failure reports.

5: RCEF reports only: Collection of reports for Radio Coverage Enhancement Function.

6: Logged MBSFN MDT: Logged MDT for Multicast Broadcast Single Frequency Networks (MBSFN).

Notes: The Job type "RLF reports only" and "RCEF reports only" are applicable only in management based trace activation in E-UTRAN and NG-RAN.

Logged MBSFN MDT is applicable only for activation in E-UTRAN. 

KASME

1450

OctetString

3GPP

Contains the K_ASME key, which is used in EPS security architecture for secure communication between User Equipment (UE), the eNodeB, and the Mobility Management Entity (MME). See 3GPP [TS 33.401].

Kc

1453

OctetString

3GPP

Contains the Ciphering Key (Kc) used in GSM and GERAN security mechanisms to encrypt user data and signaling messages over the air interface.

Last-UE-Activity-Time

1494

Time

3GPP

Contains the timestamp of the last radio activity between the UE (User Equipment) and the serving node (MME/SGSN).

LCS-Info

1473

Grouped

3GPP

Contains Location Services (LCS)-related information for a subscriber. It defines parameters that regulate location-based services (LBS) and specify which entities are permitted to request the location of the subscriber’s User Equipment (UE). This AVP is exchanged over the S6a and S6d interfaces between the Home Subscriber Server (HSS) and the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN).

The AVP structure is defined as follows:

GMLC-Number (Optional, Multiple): A list of Gateway Mobile Location Centers (GMLCs) in the Home PLMN (HPLMN) that are permitted to issue Mobile Terminated Location Requests (MT-LR) for this subscriber. Each GMLC-Number represents a telephone number or identifier that corresponds to an authorized GMLC entity that can request the subscriber’s location.

LCS-PrivacyException (Optional, Multiple): Defines privacy exceptions that apply only when using the S6d interface. These rules regulate location privacy policies, defining exceptions to default privacy settings based on specific conditions or entities.

MO-LR (Optional, Multiple): A list of Mobile-Originated Location Requests (MO-LR) permitted for the subscriber. MO-LR refers to location requests initiated by the UE itself, either for personal location-based applications or for network-based services that require UE-originated location data.

Other AVPs may be included to support extensibility and allow for additional LCS policy configurations.

LCS-Privacy-Exception

1475

Grouped

3GPP

Specifies exceptions to the default Location Services (LCS) privacy settings. It defines which classes of LCS clients are permitted to locate any target UE (User Equipment) under specific conditions. This AVP is crucial in managing privacy policies while ensuring that authorized entities, such as emergency services or network operators, can access location data when required.

The AVP structure is defined as follows:

SS-Code (Mandatory): Identifies the Supplementary Service (SS) Code, defining a specific service related to location services. 

SS-Status (Mandatory): Represents the status of the Supplementary Service (e.g., whether the privacy exception is enabled or disabled).

Notification-To-UE-User (Optional): Specifies whether the UE user should be notified when their location is accessed under a privacy exception. 

External-Client (Optional, Multiple): A list of external clients that are permitted to request the UE’s location under privacy exception conditions. Each External-Client AVP contains details about an external entity, such as a corporate service provider or law enforcement agency, that may request location data.

PLMN-Client (Optional, Multiple): A list of Public Land Mobile Network (PLMN) clients authorized to request location information. Includes mobile network operators and service providers who may need access to subscriber location data for network-related services.

Service-Type (Optional, Multiple): Specifies the types of services that may override privacy restrictions to request the UE’s location. 

Other AVPs may be included to extend the privacy exception policy with additional parameters.

LIPA-Permission

1618

Enumerated

3GPP

Specifies whether a particular APN can be accessed via Local IP Access (LIPA). LIPA enables UEs to directly access local networks without routing through the mobile operator’s core network, improving performance for localized services.

Enumerated Values

0: LIPA_PROHIBITED: The APN cannot be accessed via Local IP Access (LIPA).

1: LIPA_ONLY: The APN can only be accessed via LIPA (i.e., no core network access).

2: LIPA_CONDITIONAL: The APN can be accessed via both LIPA and non-LIPA methods.

If the LIPA-Permission AVP is not present, the APN is assumed to be LIPA_PROHIBITED.

List-Of-Measurements

1625

Bitmask (Unsigned32)

3GPP

Specifies which measurements should be collected during Minimization of Drive Test (MDT) procedures or Trace activation. The meaning of the bits is defined in 3GPP TS 32.422. The most significant bit is bit 8 of the first octet.

This parameter is mandatory if the Job Type is configured for Immediate MDT or combined Immediate MDT and Trace. This parameter defines the measurements that shall be collected. For further details see also TS 37.320. The parameter is 4 octet long bitmap.

Bitmask Definition

1: CPICH RSCP (M1): UE measures CPICH Received Signal Code Power (RSCP) for UMTS.

2: P-CCPCH RSCP (M2): For TDD: Primary Common Control Physical Channel (P-CCPCH) RSCP.

3: SIR and SIR Error (M3): Signal-to-Interference Ratio (SIR) and Error collected by NodeB.

4: UE Power Headroom (M4): UE reports Power Headroom (UPH) for E-DCH transport channels.

5: Received Total Wideband Power (RTWP) (M5): NodeB measures total received power in UMTS cells.

6: Data Volume (M6): RNC measures Data Volume separately for DL and UL.

7: Throughput (M7): RNC measures Throughput per RAB and per UE (DL & UL).

Local-Group-Id

1678

OctetString

3GPP

Used to represent an operator-defined group. This AVP allows operators to categorize subscribers or network entities into logical groups for administrative, policy, or operational purposes.

Local-Time-Zone

1649

Grouped

3GPP

Provides the time zone information of the location where the User Equipment (UE) is attached in the visited network. It includes both the Time Zone offset and the Daylight Saving Time (DST) adjustment, ensuring that network elements are aware of the correct local time configuration for the subscriber.

The AVP structure is defined as follows:

Time-Zone (Mandatory): Represents the local time zone offset from Coordinated Universal Time (UTC) at the UE’s location.

Daylight-Saving-Time (Mandatory): Specifies the Daylight Saving Time (DST) adjustment applicable in the visited network.

Other AVPs may be included for extensibility, allowing further customization based on specific network implementations.

Location-Area-Identity

1606

OctetString

3GPP

Contains the Location Area Identification of the user which identifies the Location area where the user is located, as specified in 3GPP TS 23.003. Octets are coded as described in 3GPP [TS 29.002].

Logging-Duration

1639

Enumerated

3GPP

Specifies the duration for which Minimization of Drive Tests (MDT) logging is valid when the UE (User Equipment) is in IDLE mode. This parameter is applicable when the job type parameter is configured for Logged MDT or Logged MBSFN MDT (Multicast-Broadcast Single Frequency Network MDT).

The parameter is mandatory if the job type parameter is configured for Logged MDT or Logged MBSFN MDT. The parameter determines the validity of MDT logged configuration for IDLE. The timer starts at time of receiving configuration by the UE, and continues independent of UE state transitions and RAT or RPLMN changes. Detailed definition of the parameter is in [TS 37.320], [TS 25.331], [TS 36.331] and [TS 38.331].
Enumerated Values:

For UMTS and LTE Networks:

0: 600 seconds (10 minutes)

1: 1200 seconds (20 minutes)

2: 2400 seconds (40 minutes)

3: 3600 seconds (1 hour)

4: 5400 seconds (1.5 hours)

5: 7200 seconds (2 hours)

For NR (5G) Networks:

6: 600 seconds (10 minutes)

7: 1200 seconds (20 minutes)

8: 2400 seconds (40 minutes)

9: 3600 seconds (1 hour)

10: 5400 seconds (1.5 hours)

11: 7200 seconds (2 hours)

Logging-Interval

1638

Enumerated

3GPP

Defines the time interval at which the User Equipment (UE) logs measurement reports for Minimization of Drive Tests (MDT) in IDLE mode. The logging interval determines how frequently the UE records network conditions while in Logged MDT mode, ensuring effective network performance monitoring and optimization.

The possible values are those defined in 3GPP [TS 32.422] for Logging Interval. The parameter is an enumerated type with the following values in UMTS, and LTE as per defined in [TS 25.331] and [TS 36.331].

Enumerated Values:

For UMTS and LTE Networks:

0: 1280 ms (1.28 sec)

1: 2560 ms (2.56 sec)

2: 5120 ms (5.12 sec)

3: 10240 ms (10.24 sec)

4: 20480 ms (20.48 sec)

5: 30720 ms (30.72 sec)

6: 40960 ms (40.96 sec)

7: 61440 ms (61.44 sec)

For NR (5G) Networks:

0: 1280 ms (1.28 sec)

1: 2560 ms (2.56 sec)

2: 5120 ms (5.12 sec)

3: 10240 ms (10.24 sec)

4: 20480 ms (20.48 sec)

5: 30720 ms (30.72 sec)

6: 40960 ms (40.96 sec)

7: 61440 ms (61.44 sec)

8: 320 ms (0.32 sec)

9: 640 ms (0.64 sec)

10: Infinity (No logging interval limit)

Maximum-Flow-Bitrates

1716

Integer32

3GPP

Specifies the maximum bit rate for the PC5 QoS flow over the PC5 interface. It defines the upper limit for data transmission in bits per second.

MBSFN-Area

1694

Grouped

3GPP

Defines a Multicast-Broadcast Single Frequency Network (MBSFN) area in which a UE is located. It includes the MBSFN Area ID and the Carrier Frequency, which are essential for Multimedia Broadcast Multicast Service (MBMS) operations over LTE and NR networks.

The AVP structure is defined as follows:

MBSFN-Area-ID (Optional): Identifies a specific MBSFN area within a carrier frequency.

If this field is present along with Carrier-Frequency, it refers to a specific MBSFN area within that frequency. If absent while Carrier-Frequency is present, it means all MBSFN areas on the specified frequency are indicated.

Carrier-Frequency (Optional): Specifies the carrier frequency in which the MBSFN area is located. If this field is present while MBSFN-Area-ID is absent, it refers to all MBSFN areas on that frequency. 

If both MBSFN-Area-ID and Carrier-Frequency are absent, it indicates any MBSFN area.

Other AVPs may be included for extensibility, allowing additional parameters to be specified depending on network requirements.

MBSFN-Area-ID

1695

Unsigned32

3GPP

Identifies a specific Multicast-Broadcast Single Frequency Network (MBSFN) Area. This identifier is used to distinguish MBSFN areas within a carrier frequency for Multimedia Broadcast Multicast Service (MBMS) operations over LTE and NR networks. The MBSFN-Area-ID is defined in 3GPP [TS 36.331], with a valid range of 0 to 255.

MDT-Allowed-PLMN-Id

1660

OctetString

3GPP

Specifies the Public Land Mobile Network (PLMN) where Minimization of Drive Tests (MDT) data collection is allowed for a given subscriber. This AVP contains the Mobile Country Code (MCC) and Mobile Network Code (MNC) concatenated together and encoded in an octet string format as per 3GPP [TS 23.003].

Encoding Format (per 3GPP [TS 24.008], clause 10.5.1.13):

Octet   Bits 8-5            Bits 4-1

1          MCC digit 2     MCC digit 1

2          MNC digit 3     MCC digit 3

3          MNC digit 2     MNC digit 1

If the MNC is 2 digits long, bits 5-8 of octet 2 are coded as “1111”.

MDT-Configuration

1622

Grouped

3GPP

Contains configuration parameters for Minimization of Drive Tests (MDT) as specified in 3GPP [TS 32.422]. MDT is used to collect network performance data from User Equipment (UE) in IDLE and CONNECTED modes, allowing operators to optimize network coverage, performance, and quality without requiring traditional drive tests.

The AVP structure is defined as follows:

Job-Type (Mandatory): Specifies the type of MDT job, which defines whether Logged MDT (data collected in IDLE mode) or Immediate MDT (real-time data collection in CONNECTED mode) is used.

Area-Scope (Optional): Defines the geographical area where MDT data collection applies.

It may specify Tracking Areas (TAs), Cells, or MBSFN Areas in which data collection is authorized.

List-Of-Measurements (Optional): Defines which network parameters should be measured during MDT data collection (e.g., signal strength, interference, etc.).

Reporting-Trigger (Optional): Specifies the event or condition that triggers MDT data reporting (e.g., threshold-based reporting, periodic reporting).

Report-Interval (Optional): Defines the time interval between consecutive MDT measurement reports.

Report-Amount (Optional): Specifies the maximum number of MDT reports to be sent before stopping data collection.

Event-Threshold-RSRP (Optional): Defines the Reference Signal Received Power (RSRP) threshold that triggers event-based MDT reporting.

Event-Threshold-RSRQ (Optional): Defines the Reference Signal Received Quality (RSRQ) threshold that triggers event-based MDT reporting.

Logging-Interval (Optional): Specifies the interval at which measurements should be logged during Logged MDT.

Logging-Duration (Optional): Defines the total duration for which Logged MDT data collection is active.

Measurement-Period-LTE (Optional): Defines the measurement period for LTE networks.

Measurement-Period-UMTS (Optional): Defines the measurement period for UMTS networks.

Collection-Period-RRM-LTE (Optional): Specifies the data collection period for LTE Radio Resource Management (RRM) measurements.

Collection-Period-RRM-UMTS (Optional): Specifies the data collection period for UMTS Radio Resource Management (RRM) measurements.

Positioning-Method (Optional): Specifies the positioning method used for location-based MDT measurements (e.g., A-GPS, cell-ID).

Measurement-Quantity (Optional): Defines which measurement quantities should be reported (e.g., signal strength, path loss).

Event-Threshold-Event-1F (Optional): Defines the threshold for Event 1F, which is used in mobility reporting.

Event-Threshold-Event-1I (Optional): Defines the threshold for Event 1I, which is used in handover optimization.

MDT-Allowed-PLMN-Id (Optional, Multiple): A list of PLMNs (Public Land Mobile Networks) where MDT data collection is permitted.

MBSFN-Area (Optional, Multiple): Specifies MBSFN areas where MDT measurements apply, used for broadcast/multicast MDT scenarios.

Other AVPs may be included for extensibility, allowing further customization of MDT policies.

MDT-User-Consent

1634

Enumerated

3GPP

Indicates whether the user has given their explicit consent for Minimization of Drive Tests (MDT) activation 3GPP [TS 32.422].

Enumerated Values

0: CONSENT_NOT_GIVEN: User has not given consent for MDT activation.

1: CONSENT_GIVEN: User has given consent for MDT activation.

The default value when this AVP is not present in ULA is CONSENT_NOT_GIVEN (0). Absence of this AVP in IDR shall be interpreted as the MDT-User-Consent has not been modified. The presence of this subscription parameter in ULA or IDR shall be independent of the support of the Trace Function by the MME/SGSN (see [TS 29.272] clause 7.3.10). 

Measurement-Period-LTE

1650

Enumerated

3GPP

Defines the measurement period for data volume and scheduled IP throughput measurements in Long-Term Evolution (LTE) networks. It is used in Minimization of Drive Tests (MDT) data collection and is required when Immediate MDT or Immediate MDT with Trace is configured, and specific measurement bits in List-Of-Measurements (M4 or M5 for UL/DL) are set to 1.

The measurement period dictates the time duration over which the eNodeB collects and aggregates MDT measurement data, ensuring consistent and reliable throughput evaluation. The same measurement period is used for both Uplink (UL) and Downlink (DL) measurements.

Enumerated Values:

0: 1024 ms (1.024 sec)

1: 1280 ms (1.28 sec)

2: 2048 ms (2.048 sec)

3: 2560 ms (2.56 sec)

4: 5120 ms (5.12 sec)

5: 10240 ms (10.24 sec)

6: 1 minute

Some values may not be always available e.g., due to the large amount of logging they would generate in a highly loaded network. The selection of a specific subset of supported values at the eNB is vendor-specific.

Measurement-Period-UMTS

1651

Enumerated

3GPP

Specifies the measurement period for Data Volume and Throughput measurements in UMTS networks. It is required when Immediate MDT or Immediate MDT with Trace is configured, and specific measurement bits in List-Of-Measurements (M6 or M7 for UL/DL) are set to 1.

This parameter defines the time duration over which the Radio Network Controller (RNC) collects and aggregates MDT measurement data, ensuring uniform and reliable throughput evaluation. The same measurement period is applied to both Uplink (UL) and Downlink (DL) measurements.

Enumerated Values:

0: 250 ms (Not valid for this parameter)

1: 500 ms (Not valid for this parameter)

2: 1000 ms (1 sec)

3: 2000 ms (2 sec)

4: 3000 ms (3 sec)

5: 4000 ms (4 sec)

6: 6000 ms (6 sec)

7: 8000 ms (8 sec)

8: 12000 ms (12 sec)

9: 16000 ms (16 sec)

10: 20000 ms (20 sec)

11: 24000 ms (24 sec)

12: 28000 ms (28 sec)

13: 32000 ms (32 sec)

14: 64000 ms (64 sec)

Some values may not be always available e.g., due to the large amount of logging they would generate in a highly loaded network. The selection of a specific subset of supported values at the RNC is vendor-specific.

Measurement-Quantity

1655

Unsigned32

3GPP

Defines the specific M1 measurement parameters applicable for Event Threshold 1F reporting in Minimization of Drive Tests (MDT). It is used to specify which radio measurements are relevant for event-based MDT data collection when the Reporting Trigger parameter is configured for 1F reporting and the Job-Type parameter is set to Immediate MDT or combined Trace and Immediate MDT.

Bitmask Definition (3GPP [TS 32.422], Section 5.10.15):

Bit 8: Reserved: Not used

Bit 7: Reserved: Not used

Bit 6: Reserved: Not used

Bit 5: Reserved: Not used

Bit 4: Reserved: Not used

Bit 3: Pathloss: Measures pathloss experienced by the UE

Bit 2: CPICH RSCP: Measures the Received Signal Code Power (RSCP) of the Common Pilot Channel (CPICH) in UMTS

Bit 1: CPICH Ec/N0: Measures the ratio of received energy per chip to noise density (Ec/N0) for CPICH in UMTS

Only one bit should be set at a time.

MME-Location-Information

1600

Grouped

3GPP

Contains location-related data for a subscriber as known by the Mobility Management Entity (MME). This information is primarily used for user location tracking, monitoring event reporting, and lawful interception. It helps network components determine the last known position of a subscriber, allowing for location-based services, mobility management, and emergency services.

The AVP structure is defined as follows:

E-UTRAN-Cell-Global-Identity (Optional): Identifies the E-UTRAN cell where the subscriber is currently located. Encodes the Mobile Country Code (MCC), Mobile Network Code (MNC), and E-UTRAN Cell Identity (ECI).

Tracking-Area-Identity (Optional): Contains the Tracking Area Identifier (TAI), which uniquely identifies a Tracking Area (TA) in LTE. Includes MCC, MNC, and Tracking Area Code (TAC).

Geographical-Information (Optional): Provides latitude, longitude, and altitude information for the subscriber's location. Encoded as per 3GPP [TS 23.032].

Geodetic-Information (Optional): Specifies the geodetic coordinates (longitude, latitude, altitude, and accuracy) for the subscriber’s position. 

Current-Location-Retrieved (Optional): Indicates whether the location information was actively retrieved (e.g., via network paging).

Age-Of-Location-Information (Optional): Specifies the time elapsed (in seconds) since the location information was last updated. 

User-CSG-Information (Optional): Contains Closed Subscriber Group (CSG) information, indicating whether the subscriber is camped on a CSG cell.

eNodeB-ID (Optional): Identifies the eNodeB (LTE base station) serving the subscriber.

Used for monitoring event reporting and network optimizations.

Extended-eNodeB-ID (Optional): Provides an extended identifier for the eNodeB, used in networks where additional granularity is required.

Other AVPs may be included to provide further location-related attributes.

MME-Number-for-MT-SMS

1641

OctetString

3GPP

Contains the ISDN number corresponding to the Mobility Management Entity (MME) for Mobile Terminated Short Message Service (MT-SMS). It is used to route MT-SMS traffic to the appropriate MME, ensuring the correct delivery of SMS messages to subscribers in LTE networks.

This AVP follows the international numbering format as defined in ITU-T Rec E.164 and is encoded as a TBCD-string (Telephony Binary Coded Decimal) as specified in 3GPP [TS 29.002].

This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

MME-User-State

1497

Grouped

3GPP

Provides information about the user’s state in the Mobility Management Entity (MME). It is used to indicate whether a subscriber is active, idle, or in another defined state within the LTE network. This AVP allows network components to determine the current activity level of a subscriber and manage mobility, paging, and resource allocation accordingly.

The AVP structure is defined as follows:

User-State (Optional): Indicates the current state of the subscriber in the MME.

Possible values include:

0: DETACHED (User is not registered with the network)

1: ATTACHED (User is registered and reachable)

2: CONNECTED (User has an active connection)

3: IDLE (User is registered but does not have an active connection)

Other AVPs may be included for extensibility, allowing additional user state parameters to be conveyed.

MO-LR

1485

Grouped

3GPP

Defines the types of location requests a User Equipment (UE) is subscribed to for mobile-originated location services. It is used in location-based services (LBS) to specify whether a subscriber is permitted to request their own location using MO-LR procedures.

The AVP structure is defined as follows:

SS-Code (Mandatory): Identifies the Supplementary Service (SS) Code that defines the MO-LR service type. Encoded as per 3GPP [TS 23.003].

SS-Status (Mandatory): Indicates the status of the Supplementary Service (SS) Code, showing whether MO-LR is enabled or disabled. Encoded as per 3GPP [TS 23.011].

Other AVPs may be included to provide further location service configurations.

MPS-Priority

1610

Unsigned32 (Bitmask)

3GPP

Used to indicate subscription to specific priority services for a User Equipment (UE). This AVP informs network entities such as MME or SGSN about priority subscriptions applicable either in the Circuit-Switched (CS) domain (Enhanced Multi-Level Precedence and Preemption—eMLPP or 1x RTT priority service) or in the Evolved Packet System (EPS) domain (Multimedia Priority Service—MPS).

Bitmask Definition:

Bit 0: MPS-CS-Priority: When this bit is set (1), it signifies that the UE has an active subscription to eMLPP or 1x RTT priority services within the Circuit-Switched domain. The Home Subscriber Server (HSS) obtains this subscription data from the eMLPP subscription information according to 3GPP [TS 29.002] or from the 1x RTT priority service, which is beyond the scope of 3GPP standards.

Bit 1: MPS-EPS-Priority: When set (1), this bit indicates that the UE is subscribed to Multimedia Priority Service (MPS) in the EPS domain.

Notes: Any bits beyond those explicitly defined in the table (bit 0 and bit 1) must be cleared (set to 0) by the sending HSS. The receiving Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) shall discard (ignore) these undefined bits if received.

Network-Access-Mode

1417

Enumerated

3GPP

Specifies the type of network access mode available for a subscriber. It is used to determine whether the subscriber can access both packet-switched (PS) and circuit-switched (CS) services or only packet-switched services.

Enumerated Values:

0: PACKET_AND_CIRCUIT: The subscriber has access to both packet-switched (PS) and circuit-switched (CS) services.

1: Reserved: This value is reserved and should not be used.

2: ONLY_PACKET: The subscriber is restricted to packet-switched (PS) services only, without circuit-switched (CS) access.

Non-IP-Data-Delivery-Mechanism

1686

Enumerated

3GPP

Specifies the mechanism used for delivering Non-IP data for a given Access Point Name (APN). This AVP is used in the S6a interface between the Home Subscriber Server (HSS) and Mobility Management Entity (MME) to configure Non-IP data transport options for devices that do not rely on traditional IP-based communication. If this AVP is absent, the default delivery mechanism is SGi-BASED-DATA-DELIVERY (0).

Enumerated Values:

0: SGi-BASED-DATA-DELIVERY: Non-IP data is delivered via Point-to-Point tunneling over the SGi interface (e.g., via a direct connection to an application server).

1: SCEF-BASED-DATA-DELIVERY: Non-IP data is delivered via the Service Capability Exposure Function (SCEF), providing additional capabilities such as security and network exposure.

Non-IP-PDN-Type-Indicator

1685

Enumerated

3GPP

Used to specify whether an Access Point Name (APN) is configured as a Non-IP PDN type. This AVP is primarily utilized in S6a interface exchanges between the Home Subscriber Server (HSS) and Mobility Management Entity (MME) to signal whether the PDN type is non-IP based.

If this AVP is absent, the default value is FALSE (0), meaning that the APN is considered to have a standard IP-based PDN type.

Enumerated Values:

0: FALSE: The APN does not have a Non-IP PDN type. The PDN type follows the configuration specified in the PDN-Type AVP inside the APN-Configuration AVP.

1: TRUE: The APN has a Non-IP PDN type. In this case, any value in the PDN-Type AVP within the APN-Configuration AVP should be ignored.

NOR-Flags

1416

Unsigned32 (Bitmask)

3GPP

Used in the Notify Request (NOR) message exchanged over the S6a and S6d interfaces between the Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and Home Subscriber Server (HSS). It provides additional signaling control, indicating specific states and requirements related to subscriber mobility, SMS delivery, and network registration.

Bitmask Definition:

0:Single-Registration-Indication: If set, instructs the HSS to send a Cancel Location request to the SGSN. The SGSN must not set this flag when sending NOR.

1: SGSN Area Restricted: If set, indicates that the entire SGSN service area is restricted due to regional subscription limitations.

2: Ready for SM from SGSN: If set, indicates that the UE is available or has memory capacity to receive one or more short messages via SGSN.

3: UE Reachable from MME: If set, indicates that the UE has become reachable again from the MME.

4: Reserved: This bit is deprecated and must be ignored by the receiving HSS.

5: UE Reachable from SGSN: If set, indicates that the UE has become reachable again from the SGSN.

6: Ready for SM from MME: If set, indicates that the UE is available or has memory capacity to receive one or more short messages via MME.

7: Homogeneous Support of IMS Voice Over PS Sessions: If set, signals that IMS Voice over Packet-Switched (PS) Sessions support is updated.

8: S6a/S6d-Indicator: If set, the NOR message originates from an MME (S6a interface). If cleared, the message is from an SGSN (S6d interface).

9: Removal of MME Registration for SMS: If set, signals that the MME requests to remove its registration for SMS services.

Notes: The S6a/S6d-Indicator flag shall be used together with Homogeneous Support of IMS Voice Over PS Sessions flag, i.e. if the Homogeneous Support of IMS Voice Over PS Sessions bit is set, the S6a/S6d-Indicator bit shall be set if the message is sent from the MME or the MME part on the combined MME/SGSN, and shall be cleared if the message is sent from the SGSN or the SGSN part on the combined MME/SGSN. This S6a/S6d-Indicator bit shall be discarded by the receiving HSS if the Homogeneous Support of IMS Voice Over PS Sessions bit is not set.

Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS.

Notification-To-UE-User

1471

Enumerated

3GPP

Used in location-based services (LCS) to specify the notification and verification policy when obtaining location information of a User Equipment (UE). It determines whether the user should be notified and/or their permission required before sharing location data.

Enumerated Values:

0: NOTIFY_LOCATION_ALLOWED: The user is notified, and location information is provided.

1: NOTIFYANDVERIFY_LOCATION_ALLOWED_IF_NO_RESPONSE: The user is notified and verification is required; if no response is received, location information is provided.

2: NOTIFYANDVERIFY_LOCATION_NOT_ALLOWED_IF_NO_RESPONSE: The user is notified and verification is required; if no response is received, location information is not provided.

3: LOCATION_NOT_ALLOWED: The location request is denied, and the user is not notified.

Number-Of-Requested-Vectors

1412

Unsigned32

3GPP

Indicates the number of Authentication Vectors (AVs) that the requesting entity (MME or SGSN) is prepared to receive from the HSS.

OMC-Id

1492

OctetString

3GPP

Used to identify the Operations and Maintenance Center (OMC) associated with a subscriber or network entity. The OMC-Id is coded according to 3GPP [TS 29.002], which specifies the encoding format used for various network identifiers in the Mobile Application Part (MAP) protocol.

Operation-Mode

1695

Enumerated

3GPP

Specifies the operation mode applicable to the Paging-Time-Window-Length. It defines how paging procedures are handled for different network configurations. This AVP is primarily used in paging-related signaling between the Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) over the S6a and S6d interfaces. The values for this AVP are defined in 3GPP [TS 24.008], clause 10.5.5.32.

The allowed values of Operation-Mode shall be in the range of 0 to 255.

Enumerated Values:

0: Spare: Reserved for future use.

1: Iu mode: Indicates that the Iu interface is used (applicable for UMTS networks).

2: WB-S1 mode: Indicates Wideband S1 mode, used for LTE and 5G networks.

3: NB-S1 mode: Indicates Narrowband S1 mode, applicable to NB-IoT (Narrowband IoT).

4-255: Spare: Reserved for future use.

Operator-Determined-Barring

1422

Unsigned32 (Bitmask)

3GPP

Defines operator-enforced restrictions on a subscriber's services. It specifies which services are barred, allowing the Home Subscriber Server (HSS) to enforce access control policies over the S6a and S6d interfaces when interacting with MME (Mobility Management Entity) and SGSN (Serving GPRS Support Node).

The AVP consists of a bitmask, where each bit corresponds to a specific barring rule.

Bitmask Definition:

0: All Packet-Oriented Services Barred

1: Roamer Access to HPLMN-AP (Home Public Land Mobile Network - Access Point) Barred

2: Roamer Access to VPLMN-AP (Visited Public Land Mobile Network - Access Point) Barred

3: Barring of All Outgoing Calls

4: Barring of All Outgoing International Calls

5: Barring of All Outgoing International Calls Except Those Directed to the Home PLMN Country

6: Barring of All Outgoing Inter-Zonal Calls

7: Barring of All Outgoing Inter-Zonal Calls Except Those Directed to the Home PLMN Country

8: Barring of All Outgoing International Calls Except Those Directed to the Home PLMN Country and Barring of All Outgoing Inter-Zonal Calls

Paging-Time-Window

1701

Grouped

3GPP

Used to specify the length of the Paging Time Window along with the applicable Operation Mode. It is utilized in paging procedures for managing network efficiency and battery life of User Equipment (UE) by defining how long a paging cycle should last in different operational scenarios.

The AVP structure is defined as follows:

Operation-Mode (Mandatory): Specifies the network operation mode (Iu, WB-S1, NB-S1) for which the Paging-Time-Window applies. Defined in AVP 1695 (see Operation-Mode AVP).

Paging-Time-Window-Length (Mandatory): Defines the duration of the paging time window, encoded as a Byte Buffer. The specific length is determined based on network settings.

Paging-Time-Window-Length

1702

OctetString

3GPP

Contains the Paging time window length subscribed for this user for a given operation mode. The contents of Paging-Time-Window-Length shall consist of 1 octet. The encoding shall be as defined in 3GPP [TS 24.008], clause 10.5.5.32, and it shall only contain the value of the field "Paging Time Window length" for a given RAT type, i.e., the 4 most significant bits of the octet in this AVP shall contain bits 5-8 of octet 3 in the "Extended DRX parameter" IE (see Figure 10.5.5.32 of 3GPP [TS 24.008]), and the 4 least significant bits of the octet in this AVP shall be set to 0.

PC5-Flow-Bitrates

1714

Grouped

3GPP

Specifies the bit rate parameters for PC5 (Proximity Services - ProSe) flows. It is used for Guaranteed Bit Rate (GBR) QoS flows in V2X (Vehicle-to-Everything) and ProSe communication over the PC5 interface.

The AVP structure is defined as follows:

Guaranteed-Flow-Bitrates (Optional): Specifies the minimum bit rate that must be provided for the PC5 flow. This ensures QoS assurance for critical communication.

Maximum-Flow-Bitrates (Optional): Specifies the maximum bit rate allowed for the PC5 flow, preventing excessive bandwidth consumption and ensuring network efficiency.

PC5-Link-AMBR

1718

Integer32

3GPP

Specifies the Aggregated Maximum Bit Rate (AMBR) for all Non-GBR (Non-Guaranteed Bit Rate) QoS flows over the PC5 interface. The value represents the total allowable bit rate in bits per second (bps) for non-GBR traffic, ensuring that the link does not exceed a defined threshold.

PC5-QoS-Flow

1712

Grouped

3GPP

Contains Quality of Service (QoS) parameters for a PC5 flow, which is used in ProSe (Proximity Services) and V2X (Vehicle-to-Everything) communication over the PC5 interface. It ensures that QoS constraints are properly applied to PC5-based direct communication, particularly for applications requiring guaranteed service levels, such as vehicular safety messaging and public safety communication.

The AVP structure is defined as follows:

5QI (Mandatory): 5G QoS Identifier (5QI), an integer that specifies the QoS characteristics of the PC5 flow. This maps to standardized QoS settings for latency, packet loss, and priority (as per 3GPP [TS 23.501]).

PC5-Flow-Bitrates (Optional): Defines Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) for the flow. If present, it enforces bandwidth constraints for the PC5 communication session.

PC5-Range (Optional): Defines the valid geographical range within which the PC5 flow applies. This is useful in V2X and ProSe scenarios where location-based QoS policies need to be enforced.

PC5-Range

1717

Integer32

3GPP

Defines the applicable range (in meters) for PC5 communication in Vehicle-to-Everything (V2X) services. It specifies the distance within which PC5 QoS parameters apply for groupcast mode communication over the PC5 reference point. For definition of the Range see clause 5.4.2.4 of 3GPP [TS 23.287]. When receiving UEs are beyond this range, the communication defaults to best effort instead of following PC5 QoS guarantees. The PHY/MAC layers may use the PC5-Range to adjust packet handling techniques such as Hybrid Automatic Repeat Request (HARQ) to maintain QoS requirements as defined in 3GPP [TS 38.300].

PDN-Connection-Continuity

1661

Enumerated

3GPP

Defines how to handle the Packet Data Network (PDN) connection when a User Equipment (UE) moves between different Radio Access Technologies (RATs). It specifies whether the PDN connection should be maintained or disconnected during inter-RAT mobility between broadband (WB-E-UTRAN, UTRAN) and narrowband (NB-IoT, GPRS, EC-GSM-IoT) networks. This AVP corresponds to the "PDN continuity at inter-RAT mobility" field as defined in 3GPP [TS 23.401], Table 5.7.1-1.

Enumerated Values:

0: MAINTAIN-PDN-CONNECTION: The PDN connection is maintained when the UE moves between broadband and narrowband RATs.

1: DISCONNECT-PDN-CONNECTION-WITH-REACTIVATION-REQUEST: The PDN connection is disconnected, but the UE is expected to request reactivation in the new RAT.

2: DISCONNECT-PDN-CONNECTION-WITHOUT-REACTIVATION-REQUEST: The PDN connection is disconnected, and the UE is not expected to request reactivation in the new RAT.

PDN-GW-Allocation-Type

1437

Enumerated

3GPP

Specifies whether the PDN Gateway (PDN-GW) address included in the MIP6-Agent-Info AVP has been statically allocated by the operator or dynamically assigned by other network entities. 

Enumerated Values:

0: STATIC: The PDN-GW address is statically provisioned in the HSS by the operator. The subscriber must always use the predefined gateway.

1: DYNAMIC: The PDN-GW is dynamically selected by the network, based on availability and policy.

PDN-Type

1456

Enumerated

3GPP

Indicates the type of Packet Data Network (PDN) address when the PDN is IP-based. It is used in S6a and S6d interfaces between the Home Subscriber Server (HSS) and Mobility Management Entity (MME)/Serving GPRS Support Node (SGSN) to define whether a PDN connection supports IPv4, IPv6, or dual-stack IPv4v6.

Enumerated Values:

0: IPv4: The PDN can be accessed only in IPv4 mode.

1: IPv6: The PDN can be accessed only in IPv6 mode.

2: IPv4v6: The PDN supports both IPv4 and IPv6 simultaneously (dual-stack).

3: IPv4_OR_IPv6: The PDN can be accessed in either IPv4 or IPv6 mode, but not in dual-stack mode.

PDP-Context

1469

Grouped

3GPP

Defines a PDP context for a subscriber. This AVP includes all necessary parameters related to the PDP context configuration, such as address types, QoS parameters, service selection, APN settings, and charging characteristics. It is used for multiple PDP context configurations for a single user, ensuring the correct handling of data session management when the UE (User Equipment) moves between different radio access technologies (RATs).

The AVP structure is defined as follows:

Context-Identifier (Mandatory): A unique identifier for the PDP context.

PDP-Type (Mandatory): Specifies the type of PDP, such as IP-based or Non-IP (HEX 02).

PDP-Address (Optional): The IP address associated with the PDP context.

QoS-Subscribed (Mandatory): The Quality of Service (QoS) parameters for the PDP context.

VPLMN-Dynamic-Address-Allowed (Optional): Indicates whether dynamic IP addressing is allowed for the VPLMN (Visited Public Land Mobile Network).

Service-Selection (Mandatory): Defines the service selected by the user.

3GPP-Charging-Characteristics (Optional): Defines charging characteristics related to the PDP context.

Ext-PDP-Type (Optional): Specifies an extended PDP type, if applicable.

Ext-PDP-Address (Optional): Specifies an extended PDP address, if applicable.

AMBR (Optional): Defines the Aggregated Maximum Bit Rate (AMBR) for the APN associated with this PDP context.

APN-OI-Replacement (Optional): A replacement APN operator identifier for this PDP context.

SIPTO-Permission (Optional): Indicates whether SIPTO (Session Initiation Protocol offload) is allowed.

LIPA-Permission (Optional): Indicates whether LIPA (Local IP Access) is allowed.

Restoration-Priority (Optional): A priority for restoring the PDP context after a failure.

SIPTO-Local-Network-Permission (Optional): Indicates whether SIPTO is allowed for local networks.

Non-IP-Data-Delivery-Mechanism (Optional): Defines the mechanism used for Non-IP data delivery when the PDP type is Non-IP.

SCEF-ID (Optional): Specifies the Service Capability Exposure Function (SCEF) identifier for Non-IP data delivery.

PDP-Type

1475

OctetString

3GPP

Used to specify the type of Packet Data Protocol (PDP) being used in a PDP context. It indicates whether the PDP is IPv4, IPv6, or Non-IP. This AVP is used to determine how the network will handle the data session and what type of addressing (IPv4, IPv6, or Non-IP) is applied.

This AVP is defined in 3GPP [TS 29.002] and is used in GPRS, LTE, and 5G networks to manage data session types and the corresponding network resources for devices.

Allowed Values:

IPv4 (HEX 21): Indicates that the PDP context will use IPv4 addressing.

IPv6 (HEX 57): Indicates that the PDP context will use IPv6 addressing.

Non-IP (HEX 02): Indicates that the PDP context does not use IP-based addressing, and a non-IP delivery mechanism is used instead (e.g., for IoT devices or machine-to-machine communications).

PLMN-Client

1493

Enumerated

3GPP

Used to specify the client type of the Public Land Mobile Network (PLMN) in a specific operation. This AVP helps the network identify the context or type of service being provided to the User Equipment (UE), influencing how the PLMN manages the service request. It is primarily used in location-based services and network management contexts in mobile communication systems.

Enumerated Values:

0: BROADCAST_SERVICE: Indicates that the service is a broadcast service, where location or network information is broadcasted for users to access.

1: O_AND_M_HPLMN: Represents Operation and Maintenance services for the Home Public Land Mobile Network (HPLMN). Typically used for network management and maintenance purposes.

2: O_AND_M_VPLMN: Represents Operation and Maintenance services for the Visited Public Land Mobile Network (VPLMN), applicable when a user is roaming.

3: ANONYMOUS_LOCATION: Indicates a location-based service that provides anonymous location information, possibly for emergency services or general location broadcasting without revealing the identity of the UE.

4: TARGET_UE_SUBSCRIBED_SERVICE: Specifies a service targeted for a specific UE that is subscribed to a particular service, often used for targeted services such as value-added services or location-based offerings.

Positioning-Method

1654

Unsigned32 (Bitmask)

3GPP

Defines the positioning method to be used for Minimization of Drive Tests (MDT) when Immediate MDT or Immediate MDT with Trace is configured. This AVP determines which location determination techniques should be used in Long-Term Evolution (LTE) and New Radio (NR) networks for MDT-based measurements.

It is encoded as a bitmask, where each bit represents a specific positioning method. If this AVP is not present, the best-effort positioning method is used, which may default to Cell ID-based positioning in the worst-case scenario.

Bitmask Definition (3GPP [TS 32.422], Section 5.10.19)

Bit 8: Spare (Reserved): Reserved for future use

Bit 7: Spare (Reserved): Reserved for future use

Bit 6: Spare (Reserved): Reserved for future use

Bit 5: Spare (Reserved): Reserved for future use

Bit 4: Spare (Reserved): Reserved for future use

Bit 3: E-Cell ID: Enhanced Cell ID-based positioning

Bit 2: GNSS: Global Navigation Satellite System (GPS, Galileo, etc.)

Preferred-Data-Mode

1665

Unsigned32 (Bitmask)

3GPP

Specifies the preferred data transmission mode for an Access Point Name (APN). It contains a bitmask that indicates whether the User Plane or Control Plane should be preferred for transmitting the associated traffic. The bitmask provides flexibility in network operations, allowing the Home Subscriber Server (HSS) to instruct the Mobility Management Entity (MME) on how to prioritize the transmission method based on the type of service or application.

Bitmask Definition:

0: Data over User Plane Preferred: If set, indicates that the User Plane (data plane) is preferred for transmitting the traffic associated with the APN. If not set, the User Plane is not preferred.

1: Data over Control Plane Preferred: If set, indicates that the Control Plane (signaling plane) is preferred for transmitting the traffic associated with the APN. If not set, the Control Plane is not preferred.

Notes: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME.

At least one of the bits 0 and 1 shall be set to 1. Both bits 0 and 1 may be set to 1 to indicate that both User Plane and Control Plane are preferred for transmitting the traffic associated with the APN.

This parameter only applies to E-UTRAN and SGi PDN connections. Data over User Plane refers to PDN data transported  over S1-U and Data Radio Bearer. Data over Control Plane refers to PDN data transported over NAS and Signalling Radio Bearer.

PUA-Flags

1411

Unsigned32 (Bitmask)

3GPP

Used to instruct the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) to take specific actions regarding the Temporary Mobile Subscriber Identity (TMSI) values used for a subscriber. The AVP controls the freezing of the M-TMSI (Mobile TMSI) or P-TMSI (Packet TMSI), preventing them from being immediately reused. This is relevant during network procedures to ensure the integrity of subscriber identification and prevent potential conflicts in TMSI reuse.

Bitmask Definition:

0: Freeze M-TMSI: If set, indicates that the M-TMSI (Mobile TMSI) should be frozen and not immediately reused. This prevents re-use of the M-TMSI for a certain period, helping to ensure that the subscriber's identity remains unique and avoiding conflicts.

1: Freeze P-TMSI: If set, indicates that the P-TMSI (Packet TMSI) should be frozen and not immediately reused. This prevents re-use of the P-TMSI in the SGSN for the specified period, ensuring there is no conflict with other subscribers or sessions.

PUR-Flags

1577

Unsigned32 (Bitmask)

3GPP

Used to indicate the purging status of the User Equipment (UE) in the MME (Mobility Management Entity) or SGSN (Serving GPRS Support Node) parts of a combined MME/SGSN node. The flags help the Home Subscriber Server (HSS) understand the status of the UE when purging or deactivating sessions, particularly during mobility management procedures.

Bitmask Definition:

0: UE Purged in MME: If set, indicates that the MME part of the combined MME/SGSN node has purged the UE. This bit is not set by a standalone SGSN.

1: UE Purged in SGSN: If set, indicates that the SGSN part of the combined MME/SGSN node has purged the UE. This bit is not set by a standalone MME.

QoS-Subscribed

1477

OctetString

3GPP

Represents the Quality of Service (QoS) parameters subscribed to by the User Equipment (UE). This AVP contains a concatenated string of octets, which are encoded according to 3GPP [TS 29.002]. The AVP includes the QoS information relevant to the UE's data session, and it may include extensions for additional QoS parameters (e.g., Ext-QoS-Subscribed, Ext2-QoS-Subscribed, etc.).

RAND

1478

OctetString

3GPP

Used to represent the random number (RAND) generated as part of the authentication process in mobile networks. This AVP is used in various authentication and security procedures to ensure that the identity of the user is verified securely. The RAND value is a randomly generated 128-bit number that is defined in 3GPP [TS 33.401], which is used in conjunction with other parameters like the K (encryption key) to authenticate a subscriber and establish secure communication.

RAT-Frequency-Selection-Priority-ID

1454

Unsigned32

3GPP

Specifies the subscribed value for RAT (Radio Access Technology)/Frequency Priority in the Subscriber Profile as per 3GPP [TS 23.401] and 3GPP [TS 23.060]. This AVP helps the network determine the priority of RAT and frequency selection for a subscriber, ensuring that the UE (User Equipment) connects to the most appropriate network based on operator configurations and subscriber preferences.

This AVP follows the coding defined in 3GPP [TS 36.413], and the values are defined within the range of 1 to 256.

RDS-Indicator

1710

Enumerated

3GPP

Used to specify whether the Reliable Data Service (RDS) is enabled or disabled for a particular Access Point Name (APN). The RDS feature is defined in 3GPP [TS 23.682] and is used to enhance data transfer reliability over mobile networks, particularly in scenarios where data integrity is critical.

Enumerated Values:

0: DISABLED: Indicates that the Reliable Data Service (RDS) is disabled for the APN. This means that standard data transmission methods are used without additional reliability mechanisms.

1: ENABLED: Indicates that the Reliable Data Service (RDS) is enabled for the APN. This ensures reliable delivery of data, including mechanisms for error correction and retransmission.

Regional-Subscription-Zone-Code

1487

OctetString

3GPP

Contains a Zone Code (ZC) as defined in 3GPP [TS 23.003], clause 4.4. This AVP is used to specify the Regional Subscription Zone for a subscriber's VPLMN (Visited Public Land Mobile Network), which defines the tracking areas or routing areas where the user is allowed or disallowed to roam. The Zone Code is a part of the user's subscription data, with the VPLMN defining up to 10 zone codes per user.

Notes: Each zone code represents a collection of tracking area or routing areas (defined by the operator of the VPLMN) where the user is allowed, or disallowed, to roam. The determination of which areas are actually allowed, and which ones are not allowed, is done by the serving node (MME/SGSN) in an implementation-dependent manner.

The description of RSZI in 3GPP [TS 23.003] is applicable, in the context of this specification, not only to location areas, but also to routing and tracking areas.

Relay-Node-Indicator

1578

Enumerated

3GPP

Used to indicate whether the subscription data belongs to a Relay Node. This AVP helps network elements identify the type of node handling the subscription data, which is important for certain network operations such as relay services. The presence or absence of this AVP informs the network whether it should treat the subscription data differently based on the node type.

Enumerated Values:

0: NOT_RELAY_NODE: Indicates that the subscription data does not belong to a Relay Node.

1: RELAY_NODE: Indicates that the subscription data belongs to a Relay Node.

Report-Amount

1579

Enumerated

3GPP

Specifies the number of measurement reports to be taken by the User Equipment (UE) for periodical reporting during connected mode. 

Detailed definition of the parameter is in 3GPP [TS 38.331], [TS 36.331] and [TS 25.331].

This AVP is particularly relevant in scenarios where UE-side measurements are triggered periodically (e.g., M1 measurement in LTE/NR or M1/M2 measurements in UMTS). The parameter defines the amount of measurement reports to be collected based on the configured reporting trigger and job type for Immediate MDT (Minimized Data Transfer) or a combined Immediate MDT and Trace.

The possible values are those defined in 3GPP [TS 32.422] for Report Amount.

Enumerated Values:

0: 1: Report 1 measurement value.

1: 2: Report 2 measurement values.

2: 4: Report 4 measurement values.

3: 8: Report 8 measurement values.

4: 16: Report 16 measurement values.

5: 32: Report 32 measurement values.

6: 64: Report 64 measurement values.

7: infinity: Report an infinite number of measurement values.

Reporting-Trigger

1580

Unsigned32 (Bitmask)

3GPP

Indicates the type of measurement reporting trigger configured for UE-side measurements. It specifies when measurement reports should be triggered based on periodical, event-based, or event-based periodic conditions, as defined in 3GPP [TS 32.422] and 3GPP [TS 37.320]. This AVP is mandatory when the reporting trigger is configured for Immediate MDT or combined Immediate MDT and Trace, particularly for M1 measurements in LTE, NR, and UMTS networks.

Bitmask Definition:

0: Periodical: If set, indicates periodical reporting trigger for UE-side measurements.

1: Event A2 for LTE and NR: If set, indicates Event A2 trigger for LTE and NR.

2: Event 1f for UMTS: If set, indicates Event 1f trigger for UMTS.

3: Event 1i for UMTS 1.28 MCPS TDD: If set, indicates Event 1i trigger for UMTS 1.28 MCPS TDD.

4: A2 event triggered periodic for LTE and NR: If set, indicates A2 event triggered periodic for LTE and NR.

5: All configured RRM event triggers for LTE and NR: If set, indicates all configured RRM event triggers for M1 measurements in LTE and NR.

6: All configured RRM event triggers for UMTS: If set, indicates all configured RRM event triggers for M1/M2 measurements in UMTS.

7: Reserved: Reserved for future use, should be cleared.

The parameter shall not have the combination of periodical, event based and event based periodic reporting at the same time, i.e. :

For LTE and NR, only one of the bits 1, 2, and 5 can be set. 

For UMTS, bit 1 cannot be set at the same time with either bit 3 or bit 4.

Report-Interval

1581

Enumerated

3GPP

Specifies the interval between periodic measurements taken by the User Equipment (UE) when the UE is in connected mode. This AVP is mandatory when the Reporting Trigger is configured for periodic UE-side measurements (such as M1 measurements in LTE or NR, and M1/M2 measurements in UMTS), and the job type is configured for Immediate MDT or combined Immediate MDT and Trace.

The AVP defines the interval between each measurement report to be sent by the UE, which can be configured based on different time intervals in milliseconds for UMTS, LTE, and NR.

Enumerated Values:

UMTS (3GPP [TS 25.331]):

0: 250 ms: 250 milliseconds

1: 500 ms: 500 milliseconds

2: 1000 ms: 1 second

3: 2000 ms: 2 seconds

4: 3000 ms: 3 seconds

5: 4000 ms: 4 seconds

6: 6000 ms: 6 seconds

7: 8000 ms: 8 seconds

8: 12000 ms: 12 seconds

9: 16000 ms: 16 seconds

10: 20000 ms: 20 seconds

11: 24000 ms: 24 seconds

12: 28000 ms: 28 seconds

13: 32000 ms: 32 seconds

14: 64000 ms: 64 seconds

LTE (3GPP [TS 36.331]):

15: 120 ms: 120 milliseconds

16: 240 ms: 240 milliseconds

17: 480 ms: 480 milliseconds

18: 640 ms: 640 milliseconds

19: 1024 ms: 1.024 seconds

20: 2048 ms: 2.048 seconds

21: 5120 ms: 5.12 seconds

22: 10240 ms: 10.24 seconds

23: 1 min: 1 minute (60 seconds)

24: 6 min: 6 minutes (360 seconds)

25: 12 min: 12 minutes (720 seconds)

26: 30 min: 30 minutes (1800 seconds)

27: 60 min: 60 minutes (3600 seconds)

NR (3GPP TS 38.331):

28: 120 ms: 120 milliseconds

29: 240 ms: 240 milliseconds

30: 480 ms: 480 milliseconds

31: 640 ms: 640 milliseconds

32: 1024 ms: 1.024 seconds

33: 2048 ms: 2.048 seconds

34: 5120 ms: 5.12 seconds

35: 10240 ms: 10.24 seconds

36: 20480 ms: 20.48 seconds

37: 40960 ms: 40.96 seconds

3838: 1 min: 1 minute (60 seconds)

3939: 6 min: 6 minutes (360 seconds)

4040: 12 min: 12 minutes (720 seconds)

4141: 30 min: 30 minutes (1800 seconds)

4242: 60 min: 60 minutes (3600 seconds)

Requested-EUTRAN-Authentication-Info

1408

Grouped

3GPP

Used to convey information related to the authentication request for Evolved Universal Terrestrial Radio Access Network (E-UTRAN). It contains essential details needed during the authentication process of the UE (User Equipment), including the number of requested vectors, preference for immediate response, and any necessary re-synchronization information.

The AVP structure is defined as follows:

Number-Of-Requested-Vectors (Optional): This parameter indicates the number of authentication vectors that are requested by the network for the authentication procedure. It helps control the scope of the authentication process by specifying how many vectors (combinations of RAND and AUTN parameters) should be generated for the UE during authentication.

Immediate-Response-Preferred (Optional): This parameter indicates whether the network prefers to receive an immediate response for the authentication request. It is typically used when the network needs to speed up the authentication process for certain scenarios, such as real-time applications or time-sensitive operations.

Re-synchronization-Info (Optional): This parameter provides any necessary information for re-synchronization of the authentication process. It can be used to recover from a state where the UE and the network are out of sync, such as when there are discrepancies in the authentication data or counters.

Requested-UTRAN-GERAN-Authentication-Info

1409

Grouped

3GPP

Contains essential information related to authentication requests for UTRAN (Universal Terrestrial Radio Access Network) and GERAN (GSM EDGE Radio Access Network). It defines the parameters needed during the authentication process for these networks, including the number of requested vectors, preference for immediate response, and re-synchronization information.

The AVP structure is defined as follows:

Number-Of-Requested-Vectors (Optional): This parameter indicates the number of authentication vectors required for the authentication procedure. It defines how many sets of authentication data (such as RAND and AUTN) should be generated for the UE during the authentication process.

Immediate-Response-Preferred (Optional): This parameter indicates whether the network prefers an immediate response for the authentication request. It is useful in situations where real-time performance is required, or the UE needs to be authenticated quickly, such as for urgent services.

Re-synchronization-Info (Optional): This parameter provides information needed for re-synchronizing the authentication procedure between the UE and the network. It is essential when the UE and network are out of sync, such as due to discrepancies in authentication counters or other synchronization issues.

Reset-ID

1676

OctetString

3GPP

Used to uniquely identify a resource in the HSS (Home Subscriber Server) that may have experienced a failure or a restart. This identifier is essential in the Reset procedure, particularly when modifying, adding, or deleting subscription data shared by multiple subscribers. The Reset-ID is used to track and manage the set of affected subscribers in cases where such changes or failures occur within the HSS's realm.

Restoration-Priority

1754

Unsigned32

3GPP

Used to specify the relative priority of a user's PDN connection among other PDN connections to the same APN when restoring connections affected by a SGW (Serving Gateway) or PGW (Packet Gateway) failure or restart (see 3GPP [TS 23.007]). This AVP is crucial for prioritizing recovery in cases where multiple PDN connections to the same APN are affected, ensuring that the most critical or high-priority connections are restored first.

Values:

1 to 16 are defined, with 1 representing the highest priority and 16 representing the lowest priority.

The value indicates the relative importance of the PDN connection, guiding the network in restoring the most critical connections first during a failure or restart of network elements.

Re-Synchronization-Info

1415

OctetString

3GPP

Used to carry the concatenated values of RAND (random number) and AUTS (authentication synchronization token). This AVP is used in situations where there is a need to re-synchronize the authentication procedure between the User Equipment (UE) and the network, particularly in cases of authentication failures, out-of-sync counters, or re-authentication scenarios.

Roaming-Restricted-Due-To-Unsupported-Feature

1681

Enumerated

3GPP

Used to indicate that roaming is restricted for a subscriber due to the lack of support for a specific feature in the visited network. This AVP informs the Home Subscriber Server (HSS) or network entities that the subscriber's roaming services cannot be provided because the required feature is not supported by the visited network.

Enumerated Values:

0: Roaming-Restricted-Due-To-Unsupported-Feature: Roaming is restricted for the subscriber due to an unsupported feature in the visited network.

Routing-Area-Identity

1696

OctetString

3GPP

Contains the Routing Area Identity of the user. This identity specifies the routing area where the user equipment (UE) is located, as defined in 3GPP [TS 23.003]. The Routing Area Identity helps identify the specific location area within a network, which is essential for efficient routing of the user’s traffic. Octets are coded as described in 3GPP [TS 29.002].

SCEF-Realm

1791

DiameterIdentity

3GPP

Contains the Diameter realm of the Service Capability Exposure Function (SCEF). The SCEF-Realm identifies the domain or realm to which the SCEF belongs. This AVP is essential for routing Diameter messages between the SCEF and other network elements, ensuring that network operations are correctly handled according to the SCEF's domain.

Service-Area-Identity

1697

OctetString

3GPP

Contains the Service Area Identifier (SAI) of the user. This identifier specifies the service area where the user is currently located, as defined in 3GPP [TS 23.003]. The Service-Area-Identity helps the network identify the specific service area within which the user equipment (UE) is operating, enabling accurate service delivery and network management. Octets are coded as described in 3GPP [TS 29.002].

Service-Gap-Time

1792

Unsigned32

3GPP

Specifies the minimum time duration (in seconds) the User Equipment (UE) must remain in ECM-IDLE mode after leaving ECM-CONNECTED mode, before it is allowed to send a subsequent connection request to re-enter ECM-CONNECTED mode. This AVP is part of the Service Gap Control feature defined in 3GPP [TS 23.401]. The Service-Gap-Time helps manage resource utilization and ensures the efficient management of signaling resources between the UE and the network.

Service-Type

1483

Grouped

3GPP

Contains the identities of the service types that are allowed to locate a target UE (User Equipment) for a Mobile Terminated Location Request (MT-LR). The Service-Type is crucial in managing which services can interact with the UE's location information when handling location requests within the network.

The AVP structure is defined as follows:

Service-Type-Identity (Mandatory): This parameter contains the identity of the service type that is allowed to request the location of the target UE for MT-LR. The identity ensures that only specific services, as defined by their identifiers, can access the location information of the UE.

GMLC-Restriction (Optional): This parameter specifies any restrictions related to the Gateway Mobile Location Centre (GMLC) that applies when handling location requests. It defines how the GMLC interacts with the location information, ensuring it abides by specific rules or constraints set by the network.

Notification-To-UE-User (Optional): This parameter indicates how the UE should be notified of the location request, defining how the user equipment will react to MT-LR requests. The Notification-To-UE-User helps in determining whether the UE will be alerted, and if so, how.

Service-Type-Identity

1484

Unsigned32

3GPP

Used to specify the identity of the service type that is allowed to interact with the Mobile Terminated Location Request (MT-LR). The ServiceTypeIdentity uniquely identifies the service type in question, as defined in 3GPP [TS 29.002]. This AVP ensures that only authorized services, as identified by their service type identity, are granted access to the location information of the UE (User Equipment).

SGs-MME-Identity

1807

UTF8String

3GPP

Contains the MME identity used over the SGs interface, as specified in 3GPP [TS 23.003] (Clause 19.4.2.4). This AVP is used to uniquely identify the MME (Mobility Management Entity) within the SGs interface, which is responsible for handling signaling between the SGSN (Serving GPRS Support Node) and the MME.

SGSN-Location-Information

1601

Grouped

3GPP

Contains the location-related information of a User Equipment (UE) that is relevant for the Serving GPRS Support Node (SGSN). This AVP includes several sub-AVPs that define the location and service area of the UE, and is essential for managing location-based services, mobility management, and paging operations in mobile networks.

The AVP structure is defined as follows:

Cell-Global-Identity (Optional): This parameter identifies the cell in which the UE is currently located. It is used to track the location of the UE at the cellular level.

Location-Area-Identity (Optional): This parameter identifies the location area in which the UE resides. It provides further granularity in determining the UE’s location within the network.

Service-Area-Identity (Optional): This identifies the service area of the UE, indicating the region or area where the user equipment is located.

Routing-Area-Identity (Optional): This parameter identifies the routing area within which the UE is currently located. It is used for the routing of data to the UE.

Geographical-Information (Optional): This provides additional geographical data related to the UE’s location.

Geodetic-Information (Optional): This contains geodetic data, such as latitude and longitude, that describe the UE's physical location.

Current-Location-Retrieved (Optional): This parameter indicates whether the current location of the UE has been successfully retrieved.

Age-Of-Location-Information (Optional): This parameter represents the age of the location information in seconds, providing a timestamp of when the location data was last updated.

User-CSG-Information (Optional): This parameter includes User CSG (Closed Subscriber Group) information, which is relevant to users on private or restricted networks.

SGSN-Number

1602

OctetString

3GPP

Contains the ISDN number of the Serving GPRS Support Node (SGSN). The number is encoded as a TBCD (Teletex Binary Coded Decimal) string, in line with the international number format defined by [ITU-T Rec E.164]. See 3GPP [TS 29.002] for encoding of TBCD-strings.

This AVP helps identify the SGSN by providing its telephone number in a standardized format for communication across the network.

SGSN-User-State

1498

Grouped

3GPP

Contains information about the user's state in the Serving GPRS Support Node (SGSN). It provides the SGSN with the relevant state of a user, which is important for managing the user's mobility, location, and session states within the network. The user state defines whether the user is in an active or inactive state, and helps in decision-making for processes such as paging, location updates, and service handling.

The AVP structure is defined as follows:

User-State (Mandatory): This parameter contains the state of the user within the SGSN.

SIPTO-Local-Network-Permission

1707

Unsigned32

3GPP

Indicates whether the traffic associated with a particular Access Point Name (APN) is allowed or not for SIPTO (Selected IP Traffic Offload) at the local network. 

Defined Values:

SIPTO at Local Network ALLOWED (0): This value indicates that SIPTO is allowed for the specified APN within the local network. This means that the traffic related to this APN can be offloaded to the local network, optimizing the use of the network's resources.

SIPTO at Local Network NOTALLOWED (1): This value indicates that SIPTO is not allowed for the specified APN within the local network. This means that the traffic cannot be offloaded, and the network may handle the traffic in a more traditional manner, potentially routing it through more extensive network paths.

SIPTO-Permission

1706

Enumerated

3GPP

Indicates whether the traffic associated with a particular Access Point Name (APN) is allowed or not for SIPTO (Selected IP Traffic Offload) above the Radio Access Network (RAN). This AVP helps determine if data traffic can be offloaded from the core network to local network or trusted networks higher up the stack, beyond just the RAN level.

Enumerated Values:

SIPTO_above_RAN_ALLOWED (0): This value indicates that SIPTO is allowed above the RAN, meaning that the traffic associated with the APN can be offloaded to more efficient paths that bypass the core network, improving overall data transfer efficiency.

SIPTO_above_RAN_NOTALLOWED (1): This value indicates that SIPTO is not allowed above the RAN, meaning that the traffic associated with the APN will not be offloaded and will instead follow traditional network paths, such as through the core network, possibly leading to higher latency and congestion.

SMS-Register-Request

1715

Enumerated

3GPP

Indicates whether the MME (Mobility Management Entity) or SGSN (Serving GPRS Support Node) requires registration for SMS (Short Message Service). This AVP defines the SMS registration preference of the MME or SGSN and determines whether the node should be registered for SMS or if it prefers not to be registered. The values defined by this AVP help manage SMS routing and interoperability in networks with varying SMS handling capabilities.

Enumerated Values:

SMS_REGISTRATION_REQUIRED (0): This value indicates that the MME or SGSN requires SMS registration, which means the node needs to be registered for SMS. This is typically the case when the SGs interface is supported and SMS is essential for the operation of the network.

SMS_REGISTRATION_NOT_PREFERRED (1): This value indicates that the MME or SGSN does not prefer to be registered for SMS but can still handle SMS traffic if necessary. This can be used in cases where SMS is not a primary service for the node.

NO_PREFERENCE (2): This value indicates that the MME or SGSN has no preference regarding SMS registration. The node does not require or prevent SMS registration, and the decision can be made based on network requirements.