Name

AVP Code

Data Type

Vendor

Billing-Information

1115

UTF8String

3GPP

Used to carry transparent information that is intended to be forwarded to the billing system. It serves as a flexible container for billing-related data that may not require interpretation or processing by intermediate network nodes.

Delivery-Report

1111

Enumerated

3GPP

Specifies whether a delivery report is requested for a given transaction. It is primarily used in messaging services to indicate the need for a confirmation report about the delivery status of a message. If the Delivery-Report AVP is not present, the default behavior is "No Delivery Report Requested". Enumerated Values:
0 No_Delivery_Report_Requested: No delivery report is requested (default behavior if AVP is absent).

1 Delivery_Report_Requested: A delivery report is requested to confirm the delivery status of the message.

Initial-Recipient-Address

1105

Grouped

3GPP

Used to store recipient address information sent to the MSCF (Message Service Control Function). It supports multiple sub-AVPs to define a sequence number and the recipient address for the initial delivery of a message. The AVP structure is defined as follows:

Sequence-Number (Unsigned32): A unique sequence number for this recipient address.

Recipient-Address (UTF8String): The address of the recipient, e.g., a phone number or SIP URI.

Additional AVPs, if needed, for extended information.

Originating-Interface

1110

Enumerated

3GPP

Used to indicate the interface on which a multimedia message has been received. It provides contextual information about the message origin to support routing, charging, and service validation processes. Enumerated Values

0 MM1: Message received via MM1 interface, typically between an MS and MMSC.

1 MM3: Message received via MM3 interface, between MMSCs in different domains.

2 MM4: Message received via MM4 interface, between MMSCs in different networks.

3 MM7: Message received via MM7 interface, between MMSCs and VAS applications.

Read-Reply

1112

Enumerated

3GPP

Specifies whether a read reply notification is requested for a multimedia message. This AVP supports message tracking features by indicating the requirement for a read acknowledgment from the recipient. If the Read-Reply AVP is absent, the default value is "No Read Reply Requested" (0). Enumerated Values: 

0 No Read Reply Requested: No read reply is required.

1 Read Reply Requested: Read reply notification is requested.

Recipient-Address

1108

UTF8String

3GPP

Specifies the recipient address for a multimedia message. It follows the MMS addressing model defined in the 3GPP specifications, supporting multiple recipient types, including "To:", "Cc:", and "Bcc:". The recipient address is encoded using UTF8String format, allowing compatibility with email-like formats or MSISDN-based addressing. Format Specification: 

• Recipient-Address = {Recipient Type} {Recipient}

• Recipient Type = ("To:" / "Cc:" / "Bcc:")

• Recipient = Address ; Address follows MMS addressing model

Examples:

• To: user@example.com

• Cc: +1234567890

• Bcc: contact@domain.com

Result-Recipient-Address

1106

Grouped

3GPP

Used to store recipient address information returned by the MSCF (Multimedia Services Control Function). It includes details about the sequence number, recipient address, routeing address, and sender address, supporting MMS delivery tracking and routing operations. The AVP structure is defined as follows:

Sequence-Number (Unsigned32): Tracks the order of the recipient address in message processing.

Recipient-Address (UTF8String): Stores the recipient's address formatted as email, MSISDN, or URI.

Routeing-Address (UTF8String): Specifies the routing address used for MMS delivery.

Sender-Address (UTF8String): Provides the sender's address for tracking the origin of the multimedia message.

Routeing-Address

1109

UTF8String

3GPP

Used to store the recipient address required for routing multimedia messages (MMS). It allows the specification of recipient details, including address type and destination format, adhering to the MMS addressing model and SMTP encoding rules.

Routeing-Address-Resolution

1119

Enumerated

3GPP 

Used to indicate whether the Routeing-Address has been resolved. It is typically utilized within multimedia messaging (MMS) systems to ensure proper routing of messages.

Enumerated Values:

0 Unresolved: The Routeing-Address has not been resolved yet.

1 Resolved: The Routeing-Address has been successfully resolved.

Sender-Address

1104

UTF8String

3GPP 

Specifies the identification of the sender of a multimedia message (MMS). This AVP is used to provide the recipient with information about who sent the message.

Format Example: user@example.com (Email address), +1234567890 (Telephone number in international format)

Sender-Visibility

1113

Enumerated

3GPP 

Used to indicate whether the sender's identification in a multimedia message (MMS) is requested to be hidden or visible. 

Enumerated Values:

0 Not Hidden: Sender identification is requested not to be hidden. (Default Value)

1 Hidden: Sender identification is requested to be hidden.

Sequence-Number

1107

Unsigned32

3GPP 

Provides a unique identifier or counter for a recipient address group in multimedia messaging scenarios. It is commonly used to track and differentiate multiple recipient addresses within grouped AVPs.

Served-User-Identity

1100

Grouped

3GPP 

Identifies the served subscriber for whom a messaging process is requested. It provides details such as the MSISDN, VAS Provider ID, and VAS ID, enabling accurate identification and processing of the subscriber's messaging request. The AVP structure is defined as follows:

MSISDN (UTF8String): Subscriber's phone number in international format. Example: "+1234567890".

VASPID (UTF8String): Identifier of the Value-Added Service Provider managing the messaging service.

VASID (UTF8String): Identifier of the Value-Added Service utilized by the subscriber. Example: "Ringback Tones".

Service-Key

1114

UTF8String

3GPP 

Used to identify an application on the target MSCF (Multimedia Services Control Function). It acts as a logical identifier for specific service applications or routing purposes in multimedia messaging systems.

Status

1116

Grouped

3GPP 

Provides message status information to facilitate notifications for the served user. It allows systems to communicate the delivery status or processing status of a message, combining both status codes and status text descriptions.

The AVP structure is defined as follows:

Status-Code (Optional, UTF8String): Numeric or symbolic code representing the status.

Examples: "200" (Success), "404" (Not Found)

Status-Text (Optional, UTF8String): A human-readable explanation of the status or error. 

Examples: "Message Delivered Successfully", "Recipient Address Not Found"

Status-Code

1117

UTF8String

3GPP 

Provides a trigger event-specific response code to qualify the outcome of message processing.

Qualifies outcomes for submissions, retrievals, or processing triggers. Enables interoperability with protocols such as MM1, MM7, and MMS headers.

Behavior Based on Trigger Events:

MM1 Message Submission

Response-status-value: Numeric octet values based on M-send.conf X-Mms-Response-Status header.

Example: 200 (OK), 400 (Client Error), 500 (Server Error)

MM1 Message Delivery

Retrieve-status-value: Numeric octet values based on M-Retrieve.conf X-Mms-Retrieve-Status header.

Example: 200 (Retrieved Successfully), 404 (Not Found)

MM7 Message Submission

StatusCode: Numerical values defined in the MM7_submit.RES StatusCode element.

Example: 1000 (Accepted), 2000 (Error - General Failure)

Status-Text

1118

UTF8String

3GPP 

Provides a textual description qualifying the outcome of a message processing event. omplements the Status-Code AVP with a descriptive text. Allows for custom messages if predefined codes are insufficient.

Trigger-Event

1103

Enumerated

3GPP 

Specifies the type of event that initiated a Message-Process-Request. It identifies whether the triggering event was related to message submission, delivery, or other specific processing actions.

Enumerated Values

0: MM1 Message Submission, Profile based: Submission based on a user profile.

1: MM1 Message Submission, Address based: Submission based on a specific recipient address.

2: MM1 Message Delivery: Delivery process for an MM1 multimedia message.

3: MM7 Message Submission, Profile based: Submission via MM7 based on a user profile.

4: MM7 Message Submission, Address based: Submission via MM7 based on a specific recipient address.

VAS-ID

1102

UTF8String

3GPP 

Identifies the Value Added Service (VAS) associated with a specific multimedia message processing request. It allows network elements to reference and process VAS-specific configurations or rules during message handling.

VASP-ID

1101

UTF8String

3GPP 

Used to identify the Value Added Service Provider (VASP) associated with a particular multimedia messaging service. It allows network elements to manage and process VASP-specific configurations or service rules during message delivery and processing.