The MMS architecture is provided in Clause 5
of MMS Architecture . The two interfaces considered in developing the events and event information to be reported are the MMSM interface (between the MMS client and the MMS Proxy-Relay) and the MMSR interface (i.e., between two MMS Proxy-Relay nodes).
For separate delivery of MMS, the following events shall be reported by the ICE to the DF:
MMS Notification & Confirmation
MMS Retrieval Confirmation & Acknowledgement
MMS Store Requests
MMS Viewing Requests & Responses
MMS Deletion Requests (delete from MMBox and Proxy-Relay)
MMS Cancel Requests
MMS Delivery Reports
MMS Read Report.
The above events shall be reported from the ICE to the DF independent of any other services that may or may not be intercepted.
The following events shall be reported by the HSS:
Serving System (clause 7.4.9)
Serving Evolved Packet System (clauses 220.127.116.11, 18.104.22.168, 22.214.171.124).
A set of elements as shown below can be associated with the events. The events trigger the transmission of the information from the nodes to DF2. Available IEs from this set of elements as shown below can be extended in the nodes, if this is necessary as a national option. DF2 can extend available information if this is necessary as a national option. Where MMS CC is available during an event, in addition to the IRI event reported to DF2, an MMS CC event is reported to DF3.
MSISDN of the target.
IMSI of the target.
Observed MMS Address
An address in a format as specified in . This is where a SIP URI would be included.
Observed MMS Address for Non-Local ID
An address in a format as specified in  that will be intercepted as Non-Local ID target.
Observed IPv4/IPv6 Address
An IPv4 or IPv6 address of the target.
An address in a format as specified in .
Indicates which type of event is delivered: MMS Send, MMS Notification, MMS Notification Response, MMS Retrieval, MMS Retrieval Acknowledgement, MMS Forwarding, MMS Store, MMS Upload, MMS Delete from MMBox, MMS Delete from Proxy-Relay, MMS MMBox View, MMS Delivery, MMS Read Reply, MMS Cancel, MMS Cancel Confirm, MMS MMBox View Request, MMS MMBox View Confirm, Serving System, Serving Evolved System.
Time of the event generation in the ICE. Time stamp shall be generated relative to ICE internal clock.
Date of the event generation in the ICE.
Network Element Identifier
Unique identifier for the ICE (MMS Relay/Proxy) reporting the event.
To Recipient(s) address(es)
Address of a recipient; the "To" field may include addresses of multiple recipients. When address translation occurs, both the pre and post translated addresses (with appropriate correlation) are included.
CC Recipient(s) address(es)
Address of a recipient; the "CC" field may include addresses of multiple recipients. When address translation occurs, both the pre and post translated addresses (with appropriate correlation) are included.
BCC Recipient(s) address(es)
Address of a recipient; the "BCC" field may include addresses of multiple recipients. When address translation occurs, both the pre and post translated addresses (with appropriate correlation) are included.
Address of the sender of the MM or read reply. The sender may be the originator or a forwarding user. When address translation occurs (in the case of a token sent by the client and replaced with a proper address by the MMS Proxy/Relay), both the pre and post translated addresses (with appropriate correlation) are included.
The version of MMS used by the target.
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay.
An ID assigned by the MMS Proxy-Relay to uniquely identify an MMS message.
A reference, e.g., URI, for the MM which refers to the stored MM within the MMS Proxy-Relay or the MMBox.
Stored Message Reference
A reference, e.g., URI, for the MM which refers to the newly stored MM within the MMS Proxy-Relay or the MMBox.
Date and Time when the MM was last handled (either originated or forwarded). For origination, included by the sending MMS client or the originating MMS Proxy-Relay.
Subject of the MM.
Class of the MM. For example, a value of "auto" is automatically generated by the UE. If the field is not present, the class should be interpreted as "personal".
Length of time the MM will be stored in MMS Proxy- Relay or time to delete the MM. The field has two formats, either absolute or relative.
Desired Delivery Time
Date and Time of desired delivery. Indicates the earliest possible delivery of the MM to the recipient.
Priority of the MM assigned by the originator MMS UE.
An indication that the sender's address should not be delivered to the recipient.
Specifies whether the originator MMS UE requests a delivery report from each recipient.
Specifies whether the originator MMS UE requests a read report from each recipient.
Specifies whether the originator MMS UE wants the submitted MM to be saved in the user's MMBox, in addition to sending it.
Identification of the originating application of the original MM.
Identification of the destination application of the original MM.
Auxiliary application addressing information as indicated in the original MM.
Classifies the content of the MM to the smallest content class to which the message belongs.
Indicates if the MM contains any DRM-protected element.
Indicates if the originator wishes the MM to be adapted or not. This wish can be overridden by DRM protection rules or MMS service provider / network operator configuration.
The content type of the MM.
Previously Sent By
Address of the MMS Client that forwarded or originally sent the message and a sequence number. A higher sequence number indicates a forwarding event at a later point in time. This header field MAY appear multiple times.
Previously Sent by Date/Time
Date and time of a forwarding or original send transaction of the message and a sequence number.
The sequence number indicates the correspondence to the MMS Client's address in the "X-Mms-Previously- Sent-By" header field with the same sequence number. This header field MAY appear multiple times.
Identifies the value of the MM State associated with a to be stored or stored MM.
Identifies a keyword to add or remove from the list of keywords associated with a stored MM.
This field defines the location of the content to be retrieved.
MMS specific status.
Response Status Text
Text that qualifies the Response Status.
Indicates if the MM was successfully stored in the MMBox.
Store Status Text
Text that qualifies the Store Status.
Identifies the size of the MM.
Identifies whether the originator (e.g., a Value Added Service Provider) allows the MM to be further distributed. A "No" value indicates to the user that the originator requested the content of the MM is not supposed to be distributed further.
Contains the Content-Reference associated with the corresponding top level message content of the MM waiting for retrieval and MAY additionally contain the type/format of the message content.
Indicates whether manual retrieval mode is recommended for the MM.
Retrieval Mode Text
Explains why manual retrieval mode is recommended for the MM.
MMS specific status.
Retrieve Status Text
Text that qualifies the Retrieve Status.
This field indicates the reference (i.e. Message-ID) of the previous MM that is replaced by the current MM.
Provides a MMS status. A status of "retrieved" is only signalled by the retrieving UE after retrieval of the MM.
MMS Status Text
Text that qualifies the MMS Status.
Indication whether or not the sending of delivery report is allowed by the recipient MMS Client.
MMS Forward Req Date/Time
Date and Time that the MM was requested to be forwarded.
Status of the MM regarding whether it was read or not, e.g. Read, Deleted without being read.
Read Status text
Text explanation corresponding to the Read Status.
This field includes the Message ID identifying the message to be cancelled.
Provides the status of the cancel request.
A number, indicating the index of the first MM of those selected to have information returned in the response.
A number indicating the maximum number of selected MMs whose information are to be returned in the response.
If this is absent, information elements from all remaining MMs are to be returned. If this is zero then no MM-related information are to be returned.
A list of information elements that should appear in the view for each selected message.
Indicates a request for or the actual count of messages currently stored in the MMBox.
Indicates a request for or the actual quotas for the user's MMBox in messages or bytes.
MMS Message Count
Identifies the number of messages in the content part of the PDU.
Provides a mechanism to correlate IRI for MMS with CC for MMS based on a single MMS event.
The actual contents of the MM that is carried in the payload field of MMS messages.
Most of the parameters contained in Table 18.3.2-1 can be mapped to specific parameters defined in .
Editor's Note: Specific mapping for the parameters of Table 18.3.2-1 should be added in an update to the present document.
Clause 8 of  defines procedures for address translation for MMS and it is those procedures that are referenced whenever Clause 18.3
of the present document refers to address translation.