Name

AVP Code

Data Type

Vendor

Absent-User-Diagnostic-SM

3322

Unsigned32

3GPP

Indicates the diagnostic explaining the absence of the subscriber. The values are defined in 3GPP [TS 23.040] clause 3.3.2.

Additional-Serving-Node

2406

Grouped

3GPP

Provides detailed information about an additional network node serving the targeted user. 

The AVP structure is defined as follows:

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

SGSN-Realm (Optional): The realm associated with the SGSN.

SGSN-Numbe (Optional)r: The number identifying the SGSN.

MME-Name (Optional): The name of the Mobility Management Entity.

MME-Realm (Optional): The realm associated with the MME.

MME-Number-for-MT-SMS (Optional): The MME number used specifically for mobile-terminated SMS.

MSC-Number (Optional): The number identifying the Mobile Switching Center.

The allowed combinations include:

a) SGSN-Number only.

b) SGSN-Name, SGSN-Realm, and SGSN-Number when the HSS supports the "Gdd in SGSN" feature, as indicated over S6a or Gr interfaces.

c) MME-Name, MME-Realm, and MME-Number-for-MT-SMS.

d) MSC-Number only.

e) MSC-Number combined with MME-Name and MME-Realm.

IP-SM-GW-SBI-Support-Indicator

3348

Enumerated

3GPP

Indicates whether the IP Short Message Gateway (IP-SM-GW) supports the Service-Based Interface (SBI). 

Defined Enumerated Values:

0: NOT_SUPPORT_SBI: The IP-SM-GW does not support the Service-Based Interface (SBI).

1: SUPPORT_SBI: The IP-SM-GW supports SBI and can be engaged using service-based protocols.

IP-SM-GW-SM-Delivery-Outcome

3320

Grouped

3GPP

Indicate the result of Short Message (SM) delivery via an IP Short Message Gateway (IP-SM-GW). This AVP is specifically used for the purpose of setting or updating message waiting data in the Home Subscriber Server (HSS), depending on whether the SM delivery attempt was successful or not. The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): Indicates the cause or result of the SM delivery attempt. This may signify success, failure, temporary errors, or permanent errors based on standardized cause values.

Absent-User-Diagnostic-SM (Optional): Provides additional information if the SM delivery failed due to the user being absent.

Maximum-UE-Availability-Time

3329

Time

3GPP

Specifies the UTC timestamp until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for Short Message (SM) Delivery.

MME-Absent-User-Diagnostic-SM

3313

Unsigned32

3GPP

Provides a diagnostic value reported by the Mobility Management Entity (MME) explaining why the user is absent and unreachable for Short Message (SM) delivery. The values are defined in 3GPP TS 23.040 clause 3.3.2.

MME-SM-Delivery-Outcome

3317

Grouped

3GPP

Indicate the result of a Short Message (SM) delivery attempt by the Mobility Management Entity (MME). It is primarily used to update the Message Waiting Data stored in the Home Subscriber Server (HSS) when the SM is delivered via an MME.

The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): Indicates the result of the SM delivery attempt (e.g., success, congestion, memory capacity exceeded, or other error causes). 

Absent-User-Diagnostic-SM (Optional): Provides a specific diagnostic code, as reported by the MME, explaining the user's absence. 

MSC-Absent-User-Diagnostic-SM

3314

Unsigned32

3GPP

Conveys a diagnostic value provided by the Mobile Switching Center (MSC) to explain the absence of a user during an attempted Short Message (SM) delivery. 

The values are defined in 3GPP TS 23.040 clause 3.3.2.

MSC-SM-Delivery-Outcome

3318

Grouped

3GPP

Indicates the result of a Short Message (SM) delivery attempt via the Mobile Switching Center (MSC). It is primarily used to update the Message Waiting Data in the Home Subscriber Server (HSS) when SM delivery is performed over circuit-switched (CS) domains.

The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): Specifies the result of the SM delivery attempt. 

Absent-User-Diagnostic-SM (Optional): Contains a diagnostic code provided by the MSC to explain why the user was unavailable for SM delivery.

MWD-Status

3312

Unsigned32 (Bitmask)

3GPP

Represents a bitmask used to convey message waiting status flags stored in the Home Subscriber Server (HSS) or Unified Data Management (UDM) node. 

Bitmask Definition:

Bit 0: SC-Address Not Included: When set, this bit indicates that the Service Center (SC) Address has not been added to the Message Waiting Data in the HSS.

Bit 1: MNRF-Set: Indicates that the Message Notification Request Flag (MNRF) is set in the HSS. This flag is used to manage message waiting notifications for the subscriber.

Bit 2: MCEF-Set: Indicates that the Message Completion Event Flag (MCEF) is set in the HSS. It signals that the message delivery has reached a certain completion stage.

Bit 3: MNRG-Set: Indicates that the Message Notification Registration GPRS (MNRG) flag is set in the HSS. It relates to notifications expected after registration events in 3G networks.

Bit 4: MNR5G-Set: Indicates that the HSS or UDM is awaiting a reachability notification or registration from 5G serving nodes. This is essential for message delivery when the subscriber's device is attached via a 5G access network.

Note: Bits not defined in the specification must be set to zero by the sender and ignored by the receiver, ensuring forward compatibility and adherence to protocol robustness.

RDR-Flags

3323

Unsigned32 (Bitmask)

3GPP

Represents a bitmask used to control short message delivery behavior, specifically within the context of the S6c interface.

Bitmask Definition:

Bit 0: Single-Attempt-Delivery: When this bit is set, it indicates that only one delivery attempt shall be performed for the specific Short Message. 

Note: All bits not explicitly defined in the specification must be set to zero by the sender and disregarded by the receiver.

Serving-Node

2401

Grouped

3GPP

Conveys information about the network node currently serving the subscriber targeted for SMS delivery. It is originally defined in 3GPP TS 29.173.

The AVP structure is defined as follows:

SGSN-Name (Optional): The Diameter identity of the SGSN serving the user, used when the "Gdd in SGSN" feature is supported.

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

SGSN-Number (Optional): The ISDN address of the SGSN. Can appear alone or with SGSN-Name and SGSN-Realm when additional routing information is required.

MME-Name (Optional): The Diameter identity of the MME serving the user.

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

MME-Number-for-MT-SMS (Optional): An identifier used by the HSS for routing MT SMS messages via the MME.

MSC-Number (Optional): The ISDN address of the MSC currently serving the user.

IP-SM-GW-Number (Optional): The ISDN address of the IP Short Message Gateway (IP-SM-GW), used in IP-SM-GW-based delivery scenarios.

IP-SM-GW-Name (Optional): The Diameter identity of the IP-SM-GW.

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

IP-SM-GW-SBI-Support-Indicator (Optional): Indicates whether the IP-SM-GW supports the SBI interface, providing information about interface capability.

Allowed Combinations:

The specification permits the following combinations of sub-AVPs in a Serving-Node instance:

a) SGSN-Number

b) SGSN-Name + SGSN-Realm + SGSN-Number

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

d) MSC-Number

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

f) IP-SM-GW-Number

g) IP-SM-GW-Number + IP-SM-GW-Name

h) IP-SM-GW-Number + IP-SM-GW-SBI-Support-Indicator

i) IP-SM-GW-Number + IP-SM-GW-Name + IP-SM-GW-SBI-Support-Indicator

SGSN-Absent-Subscriber-Diagnostic-SM

3315

Unsigned32

3GPP

Indicates the diagnostic reason for the subscriber's absence as reported by the Serving GPRS Support Node (SGSN). This AVP is relevant when an MT (Mobile Terminated) Short Message delivery attempt fails and the SGSN returns an absence-related error. The values are defined in 3GPP [TS 23.040] clause 3.3.2.

SGSN-SM-Delivery-Outcome

3316

Grouped

3GPP

Reports the outcome of Short Message (SM) delivery attempts made via the Serving GPRS Support Node (SGSN). 

The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): An enumerated AVP that indicates the delivery outcome for the Short Message. 

Absent-User-Diagnostic-SM (Optional): An Unsigned32 value that provides a more granular diagnostic when the delivery failed due to the subscriber being absent.

SM-Delivery-Cause

3321

Enumerated

3GPP

Indicate the outcome of a Short Message (SM) delivery attempt when reporting to the HSS/UDM over the S6c interface. 

Enumerated Values:

0: UE_MEMORY_CAPACITY_EXCEEDED: Indicates that the SM delivery failed because the user's equipment (UE) had insufficient memory to store the message.

1: ABSENT_USER: Indicates that the message could not be delivered because the user was not reachable at the time of the attempt (e.g., not attached to the network).

2: SUCCESSFUL_TRANSFER: Indicates that the message was successfully delivered to the user's device.

SM-Delivery-Not-Intended

3311

Enumerated

3GPP

Indicates that the delivery of a Short Message (SM) is not intended as part of the current Diameter procedure. Instead, the requestor is seeking only subscriber identity-related information from the HSS/UDM, such as IMSI or MCC+MNC.

Enumerated Values:

0: ONLY_IMSI_REQUESTED: Indicates that the requester is only interested in retrieving the IMSI (International Mobile Subscriber Identity) of the subscriber. No SM delivery is intended.

1: ONLY_MCC_MNC_REQUESTED: Indicates that the requester requires only the Mobile Country Code (MCC) and Mobile Network Code (MNC) information. No SM delivery is intended.

SM-Delivery-Outcome

3316

Grouped

3GPP

Reports the outcome of a Short Message (SM) delivery attempt to the HSS/UDM. 

The AVP structure is defined as follows:

MME-SM-Delivery-Outcome (Optional): Contains the delivery result reported by the MME (Mobility Management Entity) when SM delivery was attempted over EPS (Evolved Packet System).

MSC-SM-Delivery-Outcome (Optional): Represents the outcome reported by the MSC (Mobile Switching Center) when SM delivery was attempted via the CS (Circuit Switched) domain.

SGSN-SM-Delivery-Outcome (Optional): Reports the outcome from the SGSN (Serving GPRS Support Node) in GPRS/UMTS networks when used for SM delivery.

IP-SM-GW-SM-Delivery-Outcome (Optional): Conveys the result from the IP-SM-GW (IP Short Message Gateway), used in IMS or IP-based SM delivery architectures.

SMSF-3GPP-SM-Delivery-Outcome (Optional): Reflects the result of SM delivery via the SMS Function (SMSF) over 3GPP access in 5G architectures.

SMSF-Non-3GPP-SM-Delivery-Outcome (Optional): Reports the SM delivery result when performed by the SMSF over non-3GPP access networks (e.g., Wi-Fi or untrusted access).

SM-RP-MTI

3308

Enumerated

3GPP

Represents the RP-Message Type Indicator (MTI) used in Short Message (SM) delivery procedures. 

Enumerated Values:

0: SM_DELIVER: Indicates that the Short Message is an SM-Deliver message (i.e., a mobile-terminated message sent to the user).

1: SM_STATUS_REPORT: Indicates that the message is a status report generated in response to a previously sent SM, typically reporting delivery status to the originating party.

SM-RP-SMEA

3309

OctetString

3GPP

Contains the RP-Originating SME Address, which identifies the Short Message Entity (SME) that originated the Short Message (SM). It shall be formatted according to the formatting rules of the address fields described in 3GPP [TS 23.040].

SMSF-3GPP-Absent-User-Diagnostic-SM

3334

Unsigned32

3GPP

Indicate the diagnostic reason for the user's absence as reported by the SMS Function (SMSF) registered for 3GPP access (e.g., LTE or 5G NR). The values are defined in 3GPP [TS 23.040] clause 3.3.2.

SMSF-3GPP-Address

3344

Grouped

3GPP

Identifies the Short Message Service Function (SMSF) currently serving the targeted subscriber for 3GPP access (e.g., LTE or 5G NR). The SMSF is a 5G Core network entity responsible for routing and managing Short Message (SM) traffic.

The AVP structure is defined as follows: 

SMSF-3GPP-Number (Optional): The ISDN address of the SMSF serving the subscriber for SM delivery over 3GPP access.

SMSF-3GPP-Name (Optional): The Diameter identity (FQDN) of the SMSF.

SMSF-3GPP-Realm (Optional): The Diameter realm of the SMSF, used for routing Diameter messages.

SMSF-3GPP-SBI-Support-Indicator (Optional): An enumerated AVP indicating whether the SMSF supports communication over SBI (e.g., using HTTP/2 and RESTful APIs as per 5G SBA specifications).

SMSF-3GPP-Name

3340

DiameterIdentity

3GPP

Used to carry the Diameter identity (FQDN) of the Short Message Service Function (SMSF) currently serving the user over 3GPP access (e.g., LTE or 5G NR).

For further details on the encoding of this AVP, see IETF [RFC 6733].

SMSF-3GPP-Number

3338

OctetString

3GPP

Contains the ISDN number of the Short Message Service Function (SMSF) registered for 3GPP access. For further details on the definition of this AVP, see 3GPP [TS 23.003]. This AVP contains an SMSF-3GPP-Number 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.

SMSF-3GPP-Realm

3342

DiameterIdentity

3GPP

Contains the Diameter Realm Identity of the Short Message Service Function (SMSF) currently registered to serve the user over 3GPP access (e.g., LTE or 5G NR). 

For further details on the encoding of this AVP, see IETF [RFC 6733].

SMSF-3GPP-SBI-Support-Indicator

3346

Enumerated

3GPP

Indicates whether the Short Message Service Function (SMSF) registered for 3GPP access supports the Service-Based Interface (SBI) architecture as specified in the 5G core network model.

Enumerated Values:

0: NOT_SUPPORT_SBI: Indicates that the SMSF does not support Service-Based Interface communication.

1: SUPPORT_SBI: Indicates that the SMSF does support Service-Based Interface communication, as expected in modern 5G Service-Based Architecture (SBA).

SMSF-3GPP-SM-Delivery-Outcome

3336

Grouped

3GPP

Reports the result of Short Message (SM) delivery performed by the Short Message Service Function (SMSF) registered for 3GPP access (e.g., LTE or 5G NR). 

The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): An enumerated AVP that indicates the overall outcome of the SM delivery attempt. 

Absent-User-Diagnostic-SM (Optional): An Unsigned32 AVP that provides a more detailed diagnostic code if the delivery failed due to user absence. 

SMSF-Non-3GPP-Absent-User-Diagnostic-SM

3335

Unsigned32

3GPP

Provides a diagnostic reason for a failed Short Message (SM) delivery attempt, as reported by the Short Message Service Function (SMSF) registered for non-3GPP access (e.g., Wi-Fi or untrusted access networks). The values are defined in 3GPP [TS 23.040] clause 3.3.2.

SMSF-Non-3GPP-Address

3345

Grouped

3GPP

Provides addressing and identity information for the Short Message Service Function (SMSF) that serves the targeted user via non-3GPP access networks (e.g., Wi-Fi or untrusted access).

The AVP structure is defined as follows:

SMSF-Non-3GPP-Number (Optional): The ISDN number of the SMSF for non-3GPP access.

SMSF-Non-3GPP-Name (Optional): The Diameter identity (FQDN) of the SMSF serving the user over non-3GPP access. 

SMSF-Non-3GPP-Realm (Optional): The Diameter realm to which the SMSF belongs. 

SMSF-Non-3GPP-SBI-Support-Indicator (Optional): An Enumerated AVP that indicates whether the SMSF supports Service-Based Interface (SBI) communication in accordance with 5G Service-Based Architecture (SBA).

SMSF-Non-3GPP-Name

3341

DiameterIdentity

3GPP

Contains the Diameter identity (FQDN) of the Short Message Service Function (SMSF) registered to serve the user over non-3GPP access (e.g., Wi-Fi, untrusted access networks). For further details on the encoding of this AVP, see IETF [RFC 6733].

SMSF-Non-3GPP-Number

3339

OctetString

3GPP

Contains the ISDN number of the SMSF registered for Non-3GPP access. For further details on the definition of this AVP, see 3GPP [TS 23.003]. This AVP contains an SMSF-Non-3GPP-Number 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.

SMSF-Non-3GPP-Realm

3343

DiameterIdentity

3GPP

Contains the Diameter Realm Identity of the Short Message Service Function (SMSF) registered for non-3GPP access (e.g., Wi-Fi or untrusted networks). 

For further details on the encoding of this AVP, see IETF [RFC 6733].

SMSF-Non-3GPP-SBI-Support-Indicator

3347

Enumerated

3GPP

Indicates whether the Short Message Service Function (SMSF) registered for non-3GPP access supports the Service-Based Interface (SBI) communication model, as defined in 5G System architecture.

Enumerated Values:

0: NOT_SUPPORT_SBI: Indicates that the SMSF does not support Service-Based Interface communication.

1: SUPPORT_SBI: Indicates that the SMSF does support Service-Based Interface communication.

SMSF-Non-3GPP-SM-Delivery-Outcome

3337

Grouped

3GPP

Reports the outcome of a Short Message (SM) delivery attempt made via the Short Message Service Function (SMSF) registered for non-3GPP access (e.g., Wi-Fi or untrusted networks).

The AVP structure is defined as follows:

SM-Delivery-Cause (Optional): An Enumerated AVP that indicates the delivery outcome of the SM. Possible values include:

Absent-User-Diagnostic-SM (Optional): An Unsigned32 AVP that provides a more granular diagnostic code when the delivery failed due to user absence. Diagnostic values are specified in 3GPP [TS 23.040] clause 3.3.2, and cover scenarios such as IMSI detached, MS purged, or network failure.

SMS-GMSC-Alert-Event

3333

Unsigned32 (Bitmask)

3GPP

Signals alerting events to the SMS Gateway Mobile Switching Center (SMS-GMSC). 

Bitmask Definition:

Bit 0: UE-Available-For-MT-SMS: When this bit is set, it indicates that the User Equipment (UE) has become available for receiving MT SMS messages. 

Bit 1: UE-Under-New-Serving-Node: When set, this bit indicates that the UE is now under the control of a new serving node, such as a different MME or SGSN. 

Note: All bits not defined in the current specification must be set to zero by the sender and discarded by the receiver to ensure forward compatibility and robustness.

SRR-Flags

3310

Unsigned32 (Bitmask)

3GPP

Used over the S6c interface within the Send Routing Info for SM (SRR) procedure to signal specific behaviors and preferences that affect Short Message (SM) delivery logic.

Bitmask Definition:

Bit 0: GPRS-Indicator: Indicates that the SMS-GMSC supports receiving two serving node addresses (e.g., both MME and SGSN) from the HSS. This is important in dual-mode (GPRS + LTE) environments where fallback routing may be required.

Bit 1: SM-RP-PRI: Signals that the Short Message delivery should be attempted even if a Service Centre (SC) address is already present in the Message Waiting Data file. This allows for high-priority or override delivery attempts in scenarios where MWD exists.

Bit 2: Single-Attempt-Delivery: Specifies that only one delivery attempt should be performed for this SM. Useful in time-sensitive delivery or retry-limiting scenarios.

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