7.4 Messaging
33.1283GPPProtocol and procedures for Lawful Interception (LI)Release 18SecurityStage 3TS
7.4.1 Introduction
Stage 3 intercept capabilities for SMS at an SMSF are defined in clause 6.2.5. Stage 3 for MMS interception follows in clause 7.4.3.
7.4.2 LI at the MMS Proxy-Relay
7.4.2.1 Provisioning over LI_X1
The IRI-POI present in the MMS Proxy-Relay is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the MMS Proxy-Relay shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages:
– E164Number.
– EmailAddress.
– GPSIMSISDN.
– IMPI.
– IMPU.
– IMSI.
– SUPIIMSI.
– NAI.
– SUPINAI.
7.4.2.2 Generation of xIRI over LI_X2
The IRI-POI present in the MMS Proxy-Relay shall send xIRI over LI_X2 for the events listed in TS 33.127 [5] clause 7.5.2.3, which is further expanded in the present document in clause 7.4.2.4 below.
7.4.2.3 Generation of xCC over LI_X3
The CC-POI present in the MMS Proxy-Relay shall send xCC over LI_X3 for any MMS event where CC is available and authorized for reporting for the events listed in clause TS 33.127 [5] 7.5.2.3.
The xCC payload shall consist of the MMS contents given as a MIME encoded document (RFC 2045) according to OMA-TS-MMS_ENC [39]. The payload format shall be set to "MIME document" (value 15).
7.4.2.4 MMS Record Generation Cases
The triggers for MMS record generation are detailed in each of clauses 7.4.3.1 through 7.4.3.20. All triggers are defined by the detection of messages at the local MMS Proxy-Relay. They belong to one of two following high-level categories:
– at the local MMS Proxy-Relay, the sending or arrival of a message, either to or from the local target UE, using OMA-TS-MMS_ENC [39] definitions, or
– at the local MMS Proxy-Relay, the sending or arrival of a message to or from a non-local MMS Proxy-Relay, pertaining to messages either to or from a non-local target UE served by that non-local MMS Proxy-Relay, using the inter-proxy MM4 reference point, TS 23.140 [40] clause 8.4 definitions.
The present document assumes that the intercepted MMS complies with version 1.3 of OMA-TS-MMS_ENC [39]. If the intercepted messages do not comply fully, or the version is other than 1.3, parameters are required to be provided only if available.
In the following tables, the acronym Multimedia Message (MM) refers to a message in particular, while Multimedia Message Service (MMS) refers to the service in general.
7.4.3 MMS Records
7.4.3.1 MMSSend
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSSend record when the MMS Proxy-Relay sends m-send-conf (as defined in OMA-TS-MMS_ENC [39] clause 6.1.1) to local target UE.
Table 7.4.3-1 contains parameters generated by the IRI-POI, along with parameters derived from the m-send-req message (from the local target UE to the MMS Proxy-Relay), and the m-send-conf message (from MMS Proxy-Relay to the local target UE).
Table 7.4.3-1: Payload for MMSSend
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
dateTime |
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. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. This parameter is included if the corresponding MM includes a “TO” field. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
cCRecipients |
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. This parameter is included if the corresponding MM includes a "CC" field. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
bCCRecipients |
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. This parameter is included if the corresponding MM includes a “BCC” field. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
direction |
Indicates the direction of the MM. This shall be encoded as “from target.” |
M |
subject |
The subject of the MM. Include if sent to the MMS Proxy-Relay. |
C |
messageClass |
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." Include if sent to the MMS Proxy-Relay. |
C |
expiry |
Length of time in seconds the MM will be stored in MMS Proxy-Relay or time to delete the MM. The field has two formats, either absolute or relative. |
M |
desiredDeliveryTime |
Date and Time of desired delivery. Indicates the earliest possible delivery of the MM to the recipient. Include if sent to the MMS Proxy-Relay. |
C |
priority |
Priority of the MM assigned by the originator MMS Client. Include if sent to the MMS Proxy-Relay. |
C |
senderVisibility |
An indication that the sender’s address should not be delivered to the recipient. Sent by the target to indicate the target’s visibility to the other party or if not signalled by the target and the default is to not make target visible to the other party. The values given in OMA-TS-MMS_ENC [39] clause 7.3.52 shall be encoded as follows: “Show” = True, “Hide” = False. Include if sent to the MMS Proxy-Relay. |
C |
deliveryReport |
Specifies whether the originator MM UE requests a delivery report from each recipient. Sent by the target to indicate the desired delivery report. The values given in OMA-TS-MMS_ENC [39] clause 7.3.13. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
readReport |
Specifies whether the originator MM UE requests a read report from each recipient. Sent by the target to indicate the desired read report. The values given in OMA-TS-MMS_ENC [39] clause 7.3.37 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
store |
Specifies whether the originator MM UE wants the submitted MM to be saved in the user’s MMBox, in addition to sending it. Sent by the target to indicate the MM is to be stored. The values given in OMA-TS-MMS_ENC [39] clause 7.3.56 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
state |
Identifies the value of the MM State associated with a to be stored or stored MM. See OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent to the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent to the MMS Proxy-Relay. |
C |
replyCharging |
If this field is present its value is set to “accepted” or “accepted text only” and the MMS-version-value of the M-Notification.ind PDU is higher than 1.0, this header field will indicate that a reply to this particular MM is free of charge for the recipient. If the Reply-Charging service is offered and the request for reply-charging has been accepted by the MMS service provider the value of this header field SHALL be set to “accepted” or “accepted text only”. See OMA-TS-MMS_ENC [39] clause 7.3.43. Include if sent to the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Sent by the target to identify the destination application as defined in OMA-TS-MMS_ENC [39] clause 7.3.2. Include if sent to the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Sent by the target to identify the application to which replies, delivery reports, and read reports are addressed as defined in OMA-TS-MMS_ENC [39] clause 7.3.42. Include if sent to the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent to the MMS Proxy-Relay. |
C |
contentClass |
Classifies the content of the MM to the smallest content class to which the message belongs. Sent by the target to identify the class of the content. See OMA-TS-MMS_ENC [39] clause 7.3.9. Include if sent to the MMS Proxy-Relay. |
C |
dRMContent |
Indicates if the MM contains any DRM-protected element. Provide when sent by the target to indicate if the MM contains any DRM-protected element. The values given in OMA-TS-MMS_ENC [39] clause 7.3.16 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
adaptationAllowed |
Provide when sent by the target to identify whether the target wishes the MM to be adapted or not. If overridden, an indication shall be included in the parameter. Include if sent to the MMS Proxy-Relay. |
C |
contentType |
The content type of the MM. See OMA-TS-MMS_ENC [39] clause 7.3.11 |
M |
responseStatus |
MMS specific status. See OMA-TS-MMS_ENC [39] clause 7.3.48. |
M |
responseStatusText |
Text that qualifies the Response Status. Include if sent to the target. As defined in OMA-TS-MMS_ENC [39] clause 7.3.49. Include if sent by the MMS Proxy-Relay. |
C |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. |
M |
7.4.3.2 MMSSendByNonLocalTarget
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSSendByNonLocalTarget record when the MMS Proxy-Relay receives MM4_forward.REQ (as defined in TS 23.140 [40] clause 8.4.1) from the non-local MMS Proxy-Relay, that contains a non-local target ID.
Table 7.4.3-2 contains parameters generated by the IRI-POI, along with parameters derived from the MM4_forward.REQ message (from the non-local MMS Proxy-Relay to the local MMS Proxy-Relay).
Table 7.4.3-2: Payload for MMSSendByNonLocalTarget
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
transactionID |
An ID used to correlate an MMS request and response between the proxies. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “from target.” |
M |
contentType |
The content type of the MM. See OMA-TS-MMS_ENC [39] clause 7.3.11 |
M |
messageClass |
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." Include if sent to the MMS Proxy-Relay. |
C |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). |
M |
expiry |
Length of time in seconds the MM will be stored in MMS Proxy-Relay or time to delete the MM. The field has two formats, either absolute or relative. Include if sent to the MMS Proxy-Relay. |
C |
deliveryReport |
Specifies whether the originator MM UE requests a delivery report from each recipient. Indicates the desired delivery report. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Included if it exists in the MMS Proxy-Relay message. Include if sent to the MMS Proxy-Relay. |
C |
priority |
Priority of the MM assigned by the originator MMS Client. Reported if sent by the target. Include if sent to the MMS Proxy-Relay. |
C |
senderVisibility |
An indication that the sender’s address should not be delivered to the recipient. Indicates the target’s visibility to the other party or if not signalled by the target and the default is to not make target visible to the other party. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Show” = True, “Hide” = False. Include if sent to the MMS Proxy-Relay. |
C |
readReport |
Specifies whether the originator MM UE requests a read report from each recipient. Provide when sent by the target to indicate the desired read report. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
subject |
The subject of the MM. Include if sent by the target. |
C |
forwardCount |
The number of times the MM was forwarded |
C |
previouslySentBy |
History of UEs that have forwarded (including originally submitted) the MM. Include if sent to the MMS Proxy-Relay. |
C |
previouslySentByDateTime |
The timestamp associated with the previous forward events. Include if sent to the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Provide when sent by the target to identify the destination application as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Provide when sent by the target to identify the application to which replies, delivery reports, and read reports are addressed as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent to the MMS Proxy-Relay. |
C |
contentClass |
Classifies the content of the MM to the smallest content class to which the message belongs. Identifies the class of the content. Include if sent to the MMS Proxy-Relay. Include if sent to the MMS Proxy-Relay. |
C |
dRMContent |
Indicates if the MM contains any DRM-protected element. Indicates if the MM contains any DRM-protected element. The values given as defined in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
adaptationAllowed |
Identifies whether the target wishes the MM to be adapted or not. If overridden, an indication shall be included in the parameter. Include if sent to the MMS Proxy-Relay. |
C |
7.4.3.3 MMSNotification
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSNotification record when the MMS Proxy-Relay sends a m-notification-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.2) to the MMS client in the local target UE.
Table 7.4.3-3 contains parameters generated by the IRI-POI, along with parameters derived from the m-notification-ind message (from the local MMS Proxy-Relay to the local target).
Table 7.4.3-3: Payload for MMSNotification
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC[ AA] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. If the originating MMS client requested address hiding, but the MMS Proxy-Relay has access to the "From" field, this shall be reported, regardless of the fact that it may be hidden from the recepient. |
C |
direction |
Indicates the direction of the MM. This shall be encoded as “to target." |
M |
subject |
The subject of the MM. Include if sent by the MMS Proxy-Relay. |
C |
deliveryReportRequested |
Specifies whether the originator MMS UE requests a delivery report from each recipient. The values given in OMA-TS-MMS_ENC [39] clause 7.3.13 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
stored |
Specifies whether the MM was stored in the target’s MMBox, and that the content-location-value field is a reference to it. "Stored" is coded as True, and "not Stored" is coded as False. As defined in OMA-TS-MMS_ENC [39] clause 7.3.57. Include if sent by the MMS Proxy-Relay. |
C |
messageClass |
Class of the MM. For example, a value of "auto" is automatically generated by the UE. |
M |
priority |
Priority of the MM assigned by the originator MMS Client. Include if sent by the MMS Proxy-Relay. |
C |
messageSize |
Specifies the size of the MM that was viewed or uploaded. Specified in bytes. |
M |
expiry |
Length of time in seconds the MM will be stored in MMS Proxy-Relay or time to delete the MM. The field has two formats, either absolute or relative. |
M |
replyCharging |
If this field is present its value is set to “accepted” or “accepted text only” and the MMS-version-value of the M-Notification.ind PDU is higher than 1.0, this header field will indicate that a reply to this particular MM is free of charge for the recipient. If the Reply-Charging service is offered and the request for reply-charging has been accepted by the MMS service provider the value of this header field SHALL be set to “accepted” or “accepted text only”. See OMA-TS-MMS_ENC [39] clause 7.3.43. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.4 MMSSendToNonLocalTarget
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSSendToNonLocalTarget record when the local MMS Proxy-Relay sends a MM4_forward.REQ (as defined in TS 23.140 [40] clause 8.4.1) to the non-local MMS Proxy-Relay, that contains a non-local target ID.
Table 7.4.3-4 contains parameters generated by the IRI-POI, along with parameters derived from the MM4_forward.REQ message (from the non-local MMS Proxy-Relay to the local MMS Proxy-Relay).
Table 7.4.3-4: Payload for MMSSendToNonLocalTarget
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
transactionID |
An ID used to correlate an MMS request and response between the proxies. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target.” |
M |
contentType |
The content type of the MM. See OMA-TS-MMS_ENC [39] clause 7.3.11 |
M |
messageClass |
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." Include if sent by the MMS Proxy-Relay message. |
C |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). |
M |
expiry |
Length of time in seconds the MM will be stored in MMS Proxy-Relay or time to delete the MM. The field has two formats, either absolute or relative. Include if sent by the MMS Proxy-Relay message. |
C |
deliveryReportRequested |
Specifies whether the originator MMS UE requests a delivery report from each recipient. Indicates the desired delivery report. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay message. |
C |
priority |
Priority of the MM assigned by the originator MMS Client. Reported if sent by the target. Include if sent by the MMS Proxy-Relay message. |
C |
senderVisibility |
Indicates whether the sender’s address should not be delivered to the recipient. Indicates the target’s visibility to the other party or if not signalled by the target and the default is to not make target visible to the other party. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Show” = True, “Hide” = False. Include if sent by the MMS Proxy-Relay message. |
C |
readReport |
Specifies whether the originator MMS UE requests a read report from each recipient. Indicates the desired read report. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay message. |
C |
subject |
The subject of the MM. Include if sent to the target. |
C |
forwardCount |
The number of times the MM was forwarded |
C |
previouslySentBy |
History of UEs that have forwarded (including originally submitted) the MM. Include if sent by the MMS Proxy-Relay message. |
C |
previouslySentByDateTime |
The timestamp associated with the previous forward events. Include if sent by the MMS Proxy-Relay message. |
C |
applicID |
Identification of the originating application of the original MM. Provide when sent by the target to identify the destination application as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent by the MMS Proxy-Relay message. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Identifies the application to which replies, delivery reports, and read reports are addressed as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent by the MMS Proxy-Relay message. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent by the MMS Proxy-Relay message. |
C |
contentClass |
Classifies the content of the MM to the smallest content class to which the message belongs. Identifies the class of the content. Include if sent by the MMS Proxy-Relay message. |
C |
dRMContent |
Indicates if the MM contains any DRM-protected element. Indicates if the MM contains any DRM-protected element. The values given as defined in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay message. |
C |
adaptationAllowed |
identifies whether the target wishes the MM to be adapted or not. If overridden, an indication shall be included in the parameter. Include if sent by the MMS Proxy-Relay message. |
C |
store |
Specifies whether the originator MMS UE wants the submitted MM to be saved in the user’s MMBox, in addition to sending it. Indicates whether the MMS is to be stored. The values given in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay message. |
C |
applicID |
Identification of the originating application of the original MM. Identifies the destination application as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent by the MMS Proxy-Relay message. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Identifies the application to which replies, delivery reports, and read reports are addressed as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent by the MMS Proxy-Relay message. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent by the MMS Proxy-Relay message. |
C |
contentClass |
Classifies the content of the MM to the smallest content class to which the message belongs. Identifies the class of the content. Include if sent by the MMS Proxy-Relay message. |
C |
dRMContent |
Indicates if the MM contains any DRM-protected element. Indicates whether the MM contains any DRM-protected element. The values given as defined in TS 23.140 [40] clause 8.4.1.4 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay message. |
C |
7.4.3.5 MMSNotificationResponse
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSNotificationResponse record when the MMS Proxy-Relay receives a m-notifyresp-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.2, table 4) from the MMS client in the target UE for the deferred retrieval case only. The immediate retrieval trigger on m-notifyresp-ind is in clause 7.4.3.7.
Table 7.4.3-5 contains parameters generated by the IRI-POI, along with parameters derived from the m-notifyresp-ind message (from the local target UE to the MMS Proxy-Relay).
Table 7.4.3-5: Payload for MMSNotificationResponse
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target” |
M |
status |
Provides a MM status. A status of "retrieved" is only signalled by the retrieving UE after retrieval of the MM. |
M |
reportAllowed |
Indication whether or not the sending of delivery report is allowed by the recipient MMS Client. The values given in OMA-TS-MMS_ENC [39] clause 7.3.47 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
7.4.3.6 MMSRetrieval
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSRetrieval record when the MMS Proxy-Relay sends a m-retrieve-conf (as defined in OMA-TS-MMS_ENC [39] clause 6.3) to the MMS client in the target UE.
Table 7.4.3-6 contains parameters generated by the IRI-POI, along with parameters derived from the m-retrieve-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-6: Payload for MMSRetrieval
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. |
M |
dateTime |
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. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. Include if sent by the MMS Proxy-Relay. |
C |
previouslySentBy |
History of UEs that have forwarded (including originally submitted) the MM. Include if sent by the MMS Proxy-Relay. |
C |
previouslySentByDateTime |
The timestamp associated with the previous forward events. Include if sent by the MMS Proxy-Relay. |
C |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. Include if sent by the MMS Proxy-Relay. At least one of the terminatingMMSParty or cCRecipients must be included. |
C |
cCRecipients |
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. Include if sent by the MMS Proxy-Relay. At least one of the terminatingMMSParty or cCRecipients must be included. |
C |
direction |
Indicates the direction of the MM. This shall be encoded as “to target,” or "fromTarget," as appropriate. |
M |
subject |
The subject of the MM. Include if sent by the MMS Proxy-Relay. |
C |
state |
Identifies the value of the MM State associated with a to be stored or stored MM. See OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent by the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. Include if sent. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent by the MMS Proxy-Relay. |
C |
messageClass |
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." Include if sent by the MMS Proxy-Relay. |
C |
priority |
Priority of the MM assigned by the originator MMS Client. Include if sent by the MMS Proxy-Relay. |
C |
deliveryReport |
Specifies whether the originator MM UE requests a delivery report from each recipient. Indicates whether a delivery report is desired. The values given in OMA-TS-MMS_ENC [39] clause 7.3.13. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
readReport |
Specifies whether the originator MM UE requests a read report from each recipient. Indicates whether a read report is desired. The values given in OMA-TS-MMS_ENC [39] clause 7.3.37 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
replyCharging |
If this field is present its value is set to “accepted” or “accepted text only” and the MMS-version-value of the PDU is higher than 1.0, this header field will indicate that a reply to this particular MM is free of charge for the recipient. If the Reply-Charging service is offered and the request for reply-charging has been accepted by the MMS service provider the value of this header field SHALL be set to “accepted” or “accepted text only”. See OMA-TS-MMS_ENC [39] clause 7.3.43. Include if sent by the MMS Proxy-Relay. |
C |
retrieveStatus |
MMS specific status. It is used by the recipient MMS Proxy-Relay to inform the recipient MMS Client about errors, if any that occurred during the preceding retrieval operation. Include if sent by the MMS Proxy-Relay. |
C |
retrieveStatusText |
Text that qualifies the Retrieve Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.55. Include if sent by the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Sent by the target to identify the destination application as defined in OMA-TS-MMS_ENC [39] clause 7.3.2. Include if sent by the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Sent by the target to identify the application to which replies, delivery reports, and read reports are addressed as defined in OMA-TS-MMS_ENC [39] clause 7.3.42. Include if sent by the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent by the MMS Proxy-Relay. |
C |
contentClass |
Classifies the content of the MM to the smallest content class to which the message belongs. Sent by the target to identify the class of the content. See OMA-TS-MMS_ENC [39] clause 7.3.9. Include if sent by the MMS Proxy-Relay. |
C |
dRMContent |
Indicates if the MM contains any DRM-protected element. Provide when sent by the target to indicate if the MM contains any DRM-protected element. The values given in OMA-TS-MMS_ENC [39] clause 7.3.16 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
replaceID |
Indicates the message ID of the message this one is intended to replace. Include if sent by the MMS Proxy-Relay. |
C |
contentType |
The content type of the MM. See OMA-TS-MMS_ENC [39] clause 7.3.11. |
M |
7.4.3.7 MMSDeliveryAck
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSDeliveryAck record when:
– the MMS Proxy-Relay receives an m-acknowledge-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.4) from the MMS client in the target UE (for deferred retrieval), or
– the MMS Proxy-Relay receives an m-notifyresp-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.4) from the MMS client in the target UE (for immediate retrieval).
Table 7.4.3-7 contains parameters generated by the IRI-POI, along with parameters derived from the m-acknowledge-ind message (from the local target UE to the MMS Proxy-Relay), and the m-notifyresp-ind message (from the local target UE to the MMS Proxy-Relay).
Table 7.4.3-7: Payload for MMSDeliveryAck
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
reportAllowed |
Indicates whether the target allows sending of a delivery report. Encoded as "Yes" = True, "No" = False. Include if received by the MMS Proxy-Relay. |
C |
status |
Provides a MM status. A status of "retrieved" is only signalled by the retrieving UE after retrieval of the MM. Include if received by the MMS Proxy-Relay and if generated from a m-notifyresp-ind. |
C |
direction |
Indicates the direction of the MM. This shall be encoded as “to target.” |
M |
7.4.3.8 MMSForward
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSForward record when the MMS Proxy-Relay sends an m-forward-conf (as defined in OMA-TS-MMS_ENC [39] clause 6.5.2) to the MMS client in the target UE.
Table 7.4.3-8 contains parameters generated by the IRI-POI, along with parameters derived from the m-forward-req message (from the local target UE to the MMS Proxy-Relay), and the m-forward-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-8: Payload for MMSForward
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
dateTime |
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. Include if sent to the MMS Proxy-Relay. |
C |
originatingMMSParty |
ID(s) of the originating (forwarding) party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as the case of a token sent by the client and replaced with a proper address to the MMS Proxy-Relay), both the pre and post translated addresses (with appropriate correlation) are included. |
M |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. Include if sent to the MMS Proxy-Relay. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
cCRecipients |
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. This parameter is included if the corresponding MM includes a "CC" field. Include if sent to the MMS Proxy-Relay. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
bCCRecipients |
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. This parameter is included if the corresponding MM includes a “BCC” field. Include if sent to the MMS Proxy-Relay. At least one of the terminatingMMSParty, cCRecipients, or bCCRecipients must be included. |
C |
direction |
Indicates the direction of the MM. This shall be encoded as “from target.” |
M |
expiry |
Length of time in seconds the MM will be stored in MMS Proxy-Relay or time to delete the MM. The field has two formats, either absolute or relative. Include either the signalled expiry or the default, whichever applies. Include if sent to the MMS Proxy-Relay. |
C |
desiredDeliveryTime |
Date and Time of desired delivery. Indicates the earliest possible delivery of the MM to the recipient. Include if sent to the MMS Proxy-Relay. |
C |
deliveryReportAllowed |
An indication that the target requested reporting to the original sender or the default, whichever applies. The values given in OMA-TS-MMS_ENC [39] clause 7.3.47 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
deliveryReport |
Specifies whether the originator MMS UE requests a delivery report from each recipient. The values given in OMA-TS-MMS_ENC [39] clause 7.3.13. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
store |
Specifies whether the originator MMS UE wants the submitted MM to be saved in the user’s MMBox, in addition to sending it. Sent by the target to have the forwarded MM stored. The values given in OMA-TS-MMS_ENC [39] clause 7.3.56 shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
state |
Identifies the value of the MM State associated with a MM to be stored or stored MM. Sets the state for the forwarded MM when it is stored. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent to the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. Include if sent to the MMS Proxy-relay. See OMA-TS-MMS_ENC [39] clause 7.3.32. |
C |
contentLocationReq |
The content-location-value field defines the URL for the MMS server location of the content to be retrieved as it appears in the m-forward-req. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. |
M |
replyCharging |
If this field is present its value is set to “accepted" or “accepted text only” and the MMS-version-value is higher than 1.0, this header field will indicate that a reply to this particular MM is free of charge for the recipient. If the Reply-Charging service is offered and the request for reply-charging has been accepted by the MMS service provider the value of this header field SHALL be set to “accepted" or “accepted text only”. See OMA-TS-MMS_ENC [39] clause 7.3.43. Include if sent to the MMS Proxy-Relay. |
C |
responseStatus |
MMS specific status. See OMA-TS-MMS_ENC [39] clause 7.3.48. |
M |
responseStatusText |
Text that qualifies the Response Status. Include if sent to the target. As defined in OMA-TS-MMS_ENC [39] clause 7.3.49. Include if sent by the MMS Proxy-Relay. |
C |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. Include if sent by the MMS Proxy-Relay. |
C |
contentLocationConf |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-forward-conf. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
storeStatus |
Indicates if the MM was successfully stored in the MMBox. Include if sent by the MMS Proxy-Relay. |
C |
storeStatusText |
Text that qualifies the Store Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.59. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.9 MMSDeleteFromRelay
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSDeleteFromRelay record when the MMS Proxy-Relay sends a m-delete-conf (defined in OMA-TS-MMS_ENC [39]) to the MMS client in the target UE.
Table 7.4.3-9 contains parameters generated by the IRI-POI, along with parameters derived from the m-delete-req message (from the local target UE to the MMS Proxy-Relay), and the m-delete-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-9: Payload for MMSDeleteFromRelay
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. |
M |
version |
The version of MM, to include major and minor version. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target,” or "fromTarget," as appropriate. |
M |
contentLocationReq |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-delete-conf, as defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent to the MMS Proxy-Relay. |
M |
contentLocationConf |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-delete-conf, as defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
deleteResponseStatus |
The delete response, as defined in OMA-TS-MMS_ENC [39] clause 7.3.48. |
M |
deleteResponseText |
The delete response, as defined in OMA-TS-MMS_ENC [39] clause 7.3.49. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.10 MMSMBoxStore
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSMBoxStore record when the MMS Proxy-Relay sends a m-mbox-store-conf (defined in OMA-TS-MMS_ENC [39] clause 6.8) to the MMS client in the target UE.
Table 7.4.3-10 contains parameters generated by the IRI-POI, along with parameters derived from the m-mbox-store-req message (from the local target UE to the MMS Proxy-Relay), and from the m-mbox-store-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-10: Payload for MMSMBoxStore
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target.” |
M |
contentLocationReq |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-mbox-store-req. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
M |
state |
Identifies the value of the MM State associated with a MM to be stored or stored MM. Sets the state for the forwarded MM when it is stored. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent by the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent by the MMS Proxy-Relay. |
C |
contentLocationConf |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-mbox-store-conf. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
storeStatus |
Indicates if the MM was successfully stored in the MMBox. |
M |
storeStatusText |
Text that qualifies the Store Status. Include if sent to the target. As defined in OMA-TS-MMS_ENC [39] clause 7.3.59. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.11 MMSMBoxUpload
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSMBoxUpload record when the MMS Proxy-Relay sends a m-mbox-upload-conf (defined in OMA-TS-MMS_ENC [39] clause 6.10) to the MMS client in the target UE.
Table 7.4.3-11 contains parameters generated by the IRI-POI, along with parameters derived from the m-mbox-upload-req message (from the local target UE to the MMS Proxy-Relay), and from the m-mbox-upload-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-11: Payload for MMSMBoxUpload
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target,” or "fromTarget," as appropriate. |
M |
state |
Identifies the value of the MM State associated with a MM to be stored or stored MM. Sets the state for the forwarded MM when it is stored. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent by the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent by the MMS Proxy-Relay. |
C |
contentType |
The content type of the MM. See OMA-TS-MMS_ENC [39] clause 7.3.11 |
M |
contentLocation |
The content-location-value field defines the URL for the MMS server location of the MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
storeStatus |
Indicates if the MM was successfully stored in the MMBox. |
M |
storeStatusText |
Text that qualifies the Store Status. Include if sent to the target. As defined in OMA-TS-MMS_ENC [39] clause 7.3.59. Include if sent by the MMS Proxy-Relay. |
C |
mMBoxDescription |
The MMBox description PDU as defined in 7.4.3.20 corresponds to the particular MM. include if sent by the MMS Proxy-Relay. |
C |
7.4.3.12 MMSMBoxDelete
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSMBoxDelete record when the MMS Proxy-Relay sends a m-mbox-delete.conf (defined in OMA-TS-MMS_ENC [39]) to the MMS client in the target UE.
Table 7.4.3-12 contains parameters generated by the IRI-POI, along with parameters derived from the m-mbox-delete-req message (from the local target UE to the MMS Proxy-Relay), and from the m-mbox-delete-conf message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-12: Payload for MMSMBoxDelete
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as “to target,” or "fromTarget," as appropriate. |
M |
contentLocationReq |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-mbox-delete-req. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. |
M |
contentLocationConf |
The content-location-value field defines the URL for the MMS server location of the MM as it appears in the m-mbox-delete-conf. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
responseStatus |
MMS specific status. |
M |
responseStatusText |
Text that qualifies the Response Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.49. |
C |
7.4.3.13 MMSDeliveryReport
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSDeliveryReport record when the MMS Proxy-Relay sends an m-delivery-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.11) to the MMS client in the target UE.
Table 7.4.3-13 contains parameters generated by the IRI-POI, along with parameters derived from the m-delivery-ind message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-13: Payload for MMSDeliveryReport
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. Include if sent by the MMS Proxy-Relay. |
M |
terminatingMMSParty |
ID(s) of the terminating party of the original message this Delivery Report refers to, in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). Include if sent by the MMS Proxy-Relay. |
M |
responseStatus |
MMS specific status. |
M |
responseStatusText |
Text that qualifies the Response Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.49. Include if sent by the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Sent by the target to identify the destination application as defined in OMA-TS-MMS_ENC [39] clause 7.3.2. Include if sent by the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Sent by the target to identify the application to which replies, delivery reports, and read reports are addressed as defined in OMA-TS-MMS_ENC [39] clause 7.3.42. Include if sent by the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.14 MMSDeliveryReportNonLocalTarget
The IRI-POI in the MMS Proxy-Relay shall generate an xIRI containing an MMSDeliveryReportNonLocalTarget record when the MMS Proxy-Relay:
– sends MM4_delivery_report.REQ (as defined in TS 23.140 [40] clause 8.4.2), that contains a non-local target ID, to the non-local MMS Proxy-Relay, or
– receives MM4_delivery_report.REQ, that contains a non-local target ID, from the non-local MMS Proxy-Relay.
Table 7.4.3-14 contains parameters generated by the IRI-POI, along with parameters derived from the MM4_delivery_report.REQ message (from the local MMS Proxy-Relay to the non-local MMS Proxy-Relay, or inversely).
Table 7.4.3-14: Payload for MMSDeliveryReportNonLocalTarget
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
transactionID |
An ID used to correlate an MMS request and response between the proxies. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
terminatingMMSParty |
ID(s) of the terminating party of the original message this Delivery Report refers to, in one or more of the formats described in 7.4.2.1. |
M |
originatingMMSParty |
ID(s) of the originating party of the original message this Delivery Report refers to, in one or more of the formats described in 7.4.2.1. |
M |
direction |
Indicates the direction of the MM. This shall be encoded as "toTarget," or “from target,” as appropriate. |
M |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). |
M |
forwardToOriginator |
Indicates whether the MMS Proxy-Relay is allowed to forward the delivery report to the originating UE. "Yes" is coded as True, and "No" is coded as False. Include if sent to/by the MMS Proxy-Relay. |
C |
mMStatus |
Provides a MM status. A status of "retrieved" is only signalled by the retrieving UE after retrieval of the MM. |
M |
mMStatusExtension |
Extension of the MMStatus, that provides more granularity. Include if sent to/by the MMS Proxy-Relay. |
C |
mMStatusText |
Text that qualifies the MM Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.55. Include if sent to/by the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Identifies the destination application as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to/by the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Identifies the application to which replies, delivery reports, and read reports are addressed as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to/by the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent to/by the MMS Proxy-Relay. |
C |
7.4.3.15 MMSReadReport
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSReadReport record when the MMS Proxy-Relay:
– sends a m-read-orig-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.7.2) to the MMS client in the target UE, or
– receives a m-read-rec-ind (as defined in OMA-TS-MMS_ENC [39] clause 6.7.2) from the MMS client in the target UE.
Table 7.4.3-15 contains parameters generated by the IRI-POI, along with parameters derived from the m-read-orig-ind message (from the MMS Proxy-Relay to the local target UE), and from the m-read-rec-ind message (from the local target UE to the MMS Proxy-Relay).
Table 7.4.3-15: Payload for MMSReadReport
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. |
M |
terminatingMMSParty |
ID(s) of the terminating party (i.e. the intended recipient of the read report or the originator of the initial MM message to which the read report applies) in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
originatingMMSParty |
ID(s) of the originating party (i.e. the originator of the read report or the recipient the initial MM message to which the read report applies) in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
direction |
Indicates the direction of the original MM (not of this message). This shall be encoded either as "from target," or “to target,” as appropriate. |
M |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). Include if sent to/by the MMS Proxy-Relay. |
C |
readStatus |
Status of the MMS (e.g.read or deleted without reading.) |
M |
applicID |
Identification of the originating application of the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.2. Include if sent to/by the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. As defined in OMA-TS-MMS_ENC [39] clause 7.3.42. Include if sent to/by the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent to/by the MMS Proxy-Relay. |
C |
7.4.3.16 MMSReadReportNonLocalTarget
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSReadReportNonLocalTarget record when the MMS Proxy-Relay:
– sends a MM4_read_reply_report.REQ (as defined in TS 23.140 [40] clause 8.4.3), that contains a non-local target ID, to the non-local MMS Proxy-Relay, or
– receives a MM4_read_reply_report.REQ (as defined in TS 23.140 [40] clause 8.4.3), that contains a non-local target ID, from the non-local MMS Proxy-Relay.
Table 7.4.3-16 contains parameters generated by the IRI-POI, along with parameters derived from the MM4_read_reply_report.REQ message (from the local MMS Proxy-Relay to the non-local MMS Proxy-Relay, or inversely).
Table 7.4.3-16: Payload for MMSReadReportNonLocalTarget
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
transactionID |
An ID used to correlate an MMS request and response between the proxies. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. |
M |
direction |
Indicates the direction of the original MM (not of this message). This shall be encoded either as "from target" = True, or “to target” = False. |
M |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. As defined in TS 23.140 [40] clause 8.4.1.4. |
M |
dateTime |
Date and Time when the MM was last handled (either originated or forwarded). |
M |
readStatus |
Status of the MMS (e.g.read or deleted without reading.) |
M |
readStatusText |
Text explanation corresponding to the Read Status. Include if sent to/by the MMS Proxy-Relay. |
C |
applicID |
Identification of the originating application of the original MM. Identifies the destination application as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to/by the MMS Proxy-Relay. |
C |
replyApplicID |
Identification of an application to which replies, delivery reports, and read reports are addressed. Identifies the application to which replies, delivery reports, and read reports are addressed, as defined in TS 23.140 [40] clause 8.4.1.4. Include if sent to/by the MMS Proxy-Relay. |
C |
auxApplicInfo |
Auxiliary application addressing information as indicated in the original MM. As defined in OMA-TS-MMS_ENC [39] clause 7.3.4. Include if sent to/by the MMS Proxy-Relay. |
C |
7.4.3.17 MMSCancel
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSCancel record when the MMS Proxy-Relay sends a m-cancel-req (as defined in OMA-TS-MMS_ENC [39] clause 6.13) to the MMS client in the target UE.
Table 7.4.3-17 contains parameters generated by the IRI-POI, along with parameters derived from the m-cancel-req message (from the MMS Proxy-Relay to the local target UE).
Table 7.4.3-17: Payload for MMSCancel
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
cancelID |
This field includes the Message ID identifying the message to be cancelled. As defined in OMA-TS-MMS_ENC [39] clause 7.3.6. |
M |
direction |
Indicates the direction of the original MM. This shall be encoded as “to target." |
M |
7.4.3.18 MMSMBoxViewRequest
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSViewRequest record when the MMS Proxy-Relay receives a m-mbox-view-req (as defined in OMA-TS-MMS_ENC [39] clause 6.9) from the MMS client in the target UE.
Table 7.4.3-18 contains parameters generated by the IRI-POI, along with parameters derived from the m-mbox-vew-req message (from the local target UE to the MMS Proxy-Relay).
Table 7.4.3-18: Payload for MMSMBoxViewRequest
Field name |
Description |
M/C/O |
transactionID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. As defined in OMA-TS-MMS_ENC [39] clause 7.3.63. |
M |
version |
The version of MM, to include major and minor version. |
M |
contentLocation |
The content-location-value field defines the URL for the MMS Proxy-Relay location of the content to be retrieved. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent to the MMS Proxy-Relay. |
C |
state |
Specifies a MM State value to use in selecting the messages to return. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent to the MMS Proxy-Relay. |
C |
flags |
Specifies a MM Flags keyword to use in selecting the messages to return in the response. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent to the MMS Proxy-Relay. |
C |
start |
A number, indicating the index of the first MM of those selected to have information returned in the response. Include if sent to the MMS Proxy-Relay. |
C |
limit |
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. Include if sent to the MMS Proxy-Relay. |
C |
mMSAttributes |
A list of information elements that should appear in the view for each selected message. Include if sent to the MMS Proxy-Relay. |
C |
mMSTotals |
Indicates a request for or the actual count of messages currently stored in the MMBox. The values given in OMA-TS-MMS_ENC [39] clause 7.3.62. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
mMSQuotas |
Indicates a request for or the actual quotas for the user’s MMBox in messages or bytes. The values given in OMA-TS-MMS_ENC [39] clause 7.3.36. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent to the MMS Proxy-Relay. |
C |
7.4.3.19 MMSMBoxViewResponse
The IRI-POI present in the MMS Proxy-Relay shall generate an xIRI containing an MMSViewConfirm record when the MMS Proxy-Relay sends a m-mbox-view.conf (as defined in OMA-TS-MMS_ENC [39] clause 6.9) to the MMS client in the target UE.
Table 7.4.3-19 contains parameters generated by the IRI-POI, along with parameters derived from the m-mbox-vew-conf message (from the local target UE to the MMS Proxy-Relay).
Table 7.4.3-19: Payload for MMSMBoxViewResponse
Field name |
Description |
M/C/O |
version |
The version of MM, to include major and minor version. |
M |
responseStatus |
MMS specific status. |
M |
responseStatusText |
Text that qualifies the Response Status. As defined in OMA-TS-MMS_ENC [39] clause 7.3.49. |
C |
contentLocation |
The content-location-value field defines the URL for the MMS server location of the content to be retrieved. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
state |
Specifies a MM State value to use in selecting the messages to return. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent by the MMS Proxy-Relay. |
C |
flags |
Specifies a MM Flags keyword to use in selecting the messages to return in the response. See OMA-TS-MMS_ENC [39] clause 7.3.32. Include if sent by the MMS Proxy-Relay. |
C |
start |
A number, indicating the index of the first MM of those selected to have information returned in the response. Include if sent by the MMS Proxy-Relay. |
C |
limit |
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. Include if sent by the MMS Proxy-Relay. |
C |
mMSAttributes |
A list of information elements that should appear in the view for each selected message. Include if sent by the MMS Proxy-Relay. |
C |
mMSTotals |
Indicates a request for or the actual count of messages currently stored in the MMBox. The values given in OMA-TS-MMS_ENC [39] clause 7.3.62. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
mMSQuotas |
Indicates a request for or the actual quotas for the user’s MMBox in messages or bytes. The values given in OMA-TS-MMS_ENC [39] clause 7.3.36. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
mMBoxDescription |
The MMBox description PDU as defined in 7.4.3.20 corresponds to the particular MM. |
M |
7.4.3.20 MMBoxDescription
The MMBoxDescription used in MMSMBoxViewResponse and MMSMBoxUpload records is defined in table 7.4.3-20.
Table 7.4.3-20: Payload for MMBoxDescription
Field name |
Description |
M/C/O |
contentLocation |
The content-location-value field defines the URL for the MMS Proxy-relay location of the content to be retrieved. As defined in OMA-TS-MMS_ENC [39] clause 7.3.10. Include if sent by the MMS Proxy-Relay. |
C |
messageID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MM. Included unconditionally for the MMS View Confirm report and is included for the MMS Upload report if a Message ID was previously assigned to the MM. In this latter case, if a Message ID was not previously assigned, this parameter is excluded. As defined in OMA-TS-MMS_ENC [39] clause 7.3.29. Include if sent by the MMS Proxy-Relay. |
C |
state |
Identifies the value of the MM State associated with a MM to be stored or stored MM. Include for the MMS View Confirm. Include for the MMS View Request if provided by the target. As defined in OMA-TS-MMS_ENC [39] clause 7.3.33. Include if sent by the MMS Proxy-Relay. |
C |
flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. This parameter may convey all the keywords associated with the MM. Include if at least one keyword is associated with the MM. If no keywords are associated with the MM, then this parameter may be excluded. Include if sent by the MMS Proxy-Relay. |
C |
dateTime |
Date and Time when the MM request was detected. Include if sent by the MMS Proxy-Relay. |
C |
originatingMMSParty |
ID(s) of the originating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. Include if sent by the MMS Proxy-Relay. |
C |
terminatingMMSParty |
ID(s) of the terminating party in one or more of the formats described in 7.4.2.1 When address translation occurs (such as 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. I Include if sent by the MMS Proxy-Relay. |
C |
cCRecipients |
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. This parameter is included if the corresponding MM includes a “CC” field. Include if sent by the MMS Proxy-Relay. |
C |
bCCRecipients |
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. This parameter is included if the corresponding MM includes a “BCC” field. Include if sent by the MMS Proxy-Relay. |
C |
messageClass |
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". Include if sent by the MMS Proxy-Relay. |
C |
subject |
The subject of the MM. Include if sent by the MMS Proxy-Relay. |
C |
priority |
Priority of the MM assigned by the originator MMS Client. Reported if sent by the target. Include if sent by the MMS Proxy-Relay. |
C |
deliveryTime |
Date and Time of delivery. Include if sent by the MMS Proxy-Relay. |
C |
readReport |
Specifies whether the originator MMS UE requests a read report from each recipient. The values given in OMA-TS-MMS_ENC [39] clause 7.3.37. shall be encoded as follows: “Yes” = True, “No” = False. Include if sent by the MMS Proxy-Relay. |
C |
messageSize |
Specifies the size of the MM that was viewed or uploaded. Specified in bytes. Include if sent by the MMS Proxy-Relay. |
C |
replyCharging |
If this field is present its value is set to “accepted” or “accepted text only” and the MMS-version-value of the M-Notification.ind PDU is higher than 1.0, this header field will indicate that a reply to this particular MM is free of charge for the recipient. If the Reply-Charging service is offered and the request for reply-charging has been accepted by the MMS service provider the value of this header field SHALL be set to “accepted” or “accepted text only”. See OMA-TS-MMS_ENC [39] clause 7.3.43. Include if sent by the MMS Proxy-Relay. |
C |
previouslySentBy |
Address of the MMS Client that forwarded or previously sent the message. along with a sequence number and timestamp. A higher sequence number indicates a forwarding event at a later point in time. 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. Include if sent by the MMS Proxy-Relay. |
C |
previouslySentByDateTime |
Date/Time MM was previously sent.This header field MAY appear multiple times. Include if sent by the MMS Proxy-Relay. |
C |
contentType |
The content type of the MM. Include if sent by the MMS Proxy-Relay. |
C |
7.4.3.21 MMS Content
If content delivery is authorized, the CC-POI in the MMS Proxy-Relay shall generate an xCC as per clause 7.4.2.3 when any of the events in clauses 7.4.3.1 through 7.4.3.19 are detected.
7.4.4 IRI and CC Generation
7.4.4.1 Generation of IRI over LI_HI2
When an IRI-POI in the MMS Proxy-Relay generated xIRI is received over LI_X2, the MDF2 shall send an xIRI over LI_HI2 without undue delay. The xIRI shall contain a copy of the record received over LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The threeGPP33128DefinedCC field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.
The timestamp field of the PSHeader structure shall be set to the time that the MMS event was observed (i.e. the timestamp field of the xIRI). The LIID and CID fields shall correctly reflect the target identity and communication session to which the IRI belongs.
7.4.4.2 Generation of CC over LI_HI3
When a CC-POI in the MMS Proxy-Relay generated xCC message is received over LI_X3, the MDF3 shall send a CC message over LI_HI3 without undue delay. The CC message shall contain a copy of the MMS received over LI_X3. The record may be enriched with other information available at the MDF.