Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4   5…   5A…   6…   7…   7A…   8…   9…   10…   11…   12…   12.2…   12.3…   12.4…   12.5…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…   B…   C…   D…   E…   F…   G…   H…   I…   J…   L…

 

18  Invocation of Lawful Interception for messaging services |R13|

18.1  Overview of messaging services interception

The capabilities defined in this clause apply when the interception of messaging services shall be separated from the interception of all other services. This clause applies to the messaging services identified in clause 5.13 of TS 33.106.
For messaging services, separated delivery when SMS events are detected, the CSP shall be able to use existing intercept capabilities defined in this specification, but isolatable to only deliver messaging services when specified by a lawful authorisation.
The network nodes, involved in providing the interception of messaging services, shall be determined based on the deployment configuration and the messaging scenario. For SMS over NAS, the MME shall be an ICE.
When lawfully authorized, Law Enforcement requires access to CC and IRI for the events pertaining to the target's authorization, access to, and use of message services, independent of the deployed service architecture. This includes where the communications between the target and associates are sent and received over separate channels, or may be accessed at different ICEs at different geographical locations in the service provider's network.
For MMS, implementation options considered in this standard are: interception at the MMS level or normal packet session CC interception at an PS/IMS/EPS ICE and transferred to the DF2/DF3 which then subsequently isolates and delivers the MMS IRI and/or CC associated with the messaging service separate from all other services. Details of IRI and CC reporting for MMS events are for further study.
National regulations on a per interception basis may limit delivery of communications (CC and IRI) of an outbound international roaming target by the messaging service as described in clause 5.1.4 of TS 33.106.
If roaming interception is not allowed and it is determined that the target is outside the country, reporting by the HPLMN for messaging services shall be as follows:
  • All related messsaging service events defined in this clause are subject to this mechanism with the exception that messaging service events in the HPLMN involving communications to the target that are not transmitted to the target are not subject to this mechanism.
Non-communications-associated IRI (e.g. those identified by the HSS) are not affected by this requirement.
Up

18.2  SMSWord‑p. 205

18.2.1  Introduction

LI for SMS over a GPRS and UMTS access is specified in clause 7. LI for SMS over IP (using IMS SIP signalling handled by the core network) which can be used in conjunction with LTE access as well as other non-3GPP IP based access is defined in clause 7A.6.

18.2.2  SMS over GPRS/UMTS

For separate delivery of SMS when SMS is used in conjunction with GPRS or UMTS access, the following events shall be reported by the ICE to the DF:
  1. SMS (clause 7.4.7)
  2. HLR Related events
    1. Serving System (clause 7.4.9)
    2. HLR subscriber record change (clause 7.4.12)
    3. Cancel location (clause 7.4.13);
    4. Register location (clause 7.4.14);
    5. Location information request (clause 7.4.15).
The above events shall be reported from the ICE to the DF independent of any other services that may or may not be intercepted.
Up

18.2.3  SMS over IP

For separate delivery of SMS when SMS over IP (using IMS SIP signalling handled by the core network) is used, the following events shall be reported by the ICE to the DF:
  1. Intercepted SIP event as described in clause 7A.3.0
  2. HSS related events
    1. Serving System (clause 7A.2.3.1) for use when roaming
    2. IMPU or IMPI changed in a HSS subscriber record change (clause 7A.2.3.2);
    3. Registration termination (clause 7A.2.3.3);
    4. Location information request (clause 7A.2.3.4).
The above events shall be able to be reported from the ICE to the DF independent of and to the exclusion of any other services that may or may not be intercepted.
Up

18.2.4  SMS over NAS |R14|Word‑p. 206

18.2.4.0  Introduction

SMS over NAS reporting uses the architecture and interfaces defined in Clause 12 Lawful Interception for Evolved Packet System.

18.2.4.1  Structure of the events

SMS over NAS uses the MME as an ICE.
The following events are applicable to the MME:

18.2.4.2  SMS over NAS Events

For separate delivery of SMS when the NAS infrastructure is used, the following events shall be reported from the MME to the DF:
  1. SMS over NAS (clause 18.2.4.3)
    In addition, the following HSS events shall be reported:
  2. HSS Related events
    1. Serving Evolved Packet System (clauses 12.2.3.8, 12.4.3.10, 12.5.3.5)
    2. HSS subscriber record change (clauses 12.2.3.15, 12.3.4.18, 12.5.3.15)
    3. Cancel location (clause 12.2.3.16)
    4. Register Termination (clauses 12.3.3.16, 12.3.4.19)
    5. Register location (clauses 12.2.3.17, 12.4.3.20)
    6. Location information request (clauses 12.2.3.18, 12.4.3.20, 12.5.3.17).
The above events shall be reported from the ICE to the DF independent of any other services that may or may not be intercepted.
Information Element
Description

Observed MSISDN
MSISDN of the target.
Observed IMSI
IMSI of the target.
Observed IMEI
IMEI of the target; when it coincides with the IMEI, it shall be checked for each activation over the radio interface.
Observed Non-Local ID
Target Identifier with the E. 164 number of Non-Local ID target.
Event type indicating SMS over NAS.
Event date
Date of the event generation in the ICE.
Event time
Time of the event generation in the ICE. Timestamp shall be generated relative to ICE internal clock.
Location Information (if available).
If the information in the MME received over S1 (TS 36.413) includes one or more cell IDs, then all cell IDs shall be reported to the LEMF whenever location reporting is triggered at the MME.
Time of Location
Date/Time of location. The time when location was obtained by the location source node.
Network Element Identifier
Unique identifier for the ICE reporting the event.
SMS
The SMS content with SMS header which is sent with the SMS-service. The header also includes the SMS-Centre address.
SMS Initiator
SMS indicator whether the SMS is MO or MT or undefined.
IAs
The observed Interception Areas.

Up

18.2.4.3  SMS over NASWord‑p. 207
For SMS-MO, the event is generated in the MME. Dependent on national requirements, event generation shall occur in the following cases:
  • when the MME receives the SMS from the target MS, or when the MME detects that an SMS is to the Non-Local ID target.
  • when the SMS that was originated from the target MS, or sent to the Non-Local ID target.
For SMS-MT, the event is generated in the MME. Dependent on national requirements, event generation shall occur in the following cases:
  • when the MME receives the SMS originated from a Non-Local ID target, or one that will have to be sent to a target MS.
  • when the MME receives notification that recipient MS has received the SMS successfully. The recipient MS is the target MS when the SMS is sent to the target. The recipient MS may not be the target when the SMS was originating from a Non-Local ID target.
Data over NAS for Internet of Things is for further study.
These elements will be delivered to the DF2 if available:
  • Observed MSISDN
  • Observed IMSI
  • Observed IMEI
  • Observed Non-Local ID
  • Event Type
  • Event Time
  • Event Date
  • Network Element Identifier
  • Location Information
  • Time of Location
  • SMS
  • SMS Initiator
  • IAs (if applicable)
Up

18.3  MMS |R14|Word‑p. 208

18.3.1  Background

Clause 7.6 defines an interception solution for MMS over GPRS/UMTS whereby the packet IP stream is sent to the DF and onto to the LEMF for LE to extract the MMS information. However, that solution does not allow for the separate delivery of MMS from other services. In fact, that approach necessitates the interception and delivery of a packet data session which may not be authorized for interception. This clause defines an approach to intercept and deliver only MMS related events and deliver those separate from any other services that may or may not be intercepted.
It is a national option for the CSP and LEA to agree on the maximum size of and MMS to be delivered to the LEMF. If the MMS is bigger than the agreed size it is a national option for what to do (e.g. don't deliver it to the LEMF).
MMS service is defined in TS 22.140, OMA's MMS Architecture OMA-AD-MMS-V1_3-20110913-A [72], and OMA's Multimedia Messaging Service Encapsulation Protocol OMA-TS-MMS_ENC-V1_3-20110913-A [73].
The key network elements involved in the support of MMS is the MMS Proxy-Relay. The MMS Proxy-Relay is responsible for:
  1. receiving a MMS from a served UE and forwarding that to the MMS Proxy-Relay of the destination UE,
  2. receiving a MMS from an originating MMS Proxy-Relay and forwarding this MMS or a notification of it to its served UE,
  3. receiving a request for retrieval of an MMS from a served UE and delivering that MMS to the served UE,
  4. providing the served UE with delivery status and read reports of served UE originated MMS
  5. providing a MMS/Relay of another UE with delivery status and read reports of MMS received for the served UE.
When a Non-Local Id is used as target identity, the interception shall be performed at the MMS Proxy Relay. For MMS messages originated from a target wth Non-Local ID, the target is identified from FROM field. For MMS messages to the target with Non-Local ID, the target are identified from TO, CC and BCC fields. The interception may be triggered on the value address defined in the clause 8 of MMS addressing model of OMA's Multimedia Messaging Service Encapsulation Protocol OMA-TS-MMS_ENC-V1_3-20110913-A [73].
LI for MMS requires IRI and CC related to the MMS to be detected by the MMS Proxy-Relay and forwarded to the DF.
[not reproduced yet]
Figure 18.1: MMS Proxy-Relay Intercept configuration
Up

18.3.2  MMS Architecture IRI/CC EventsWord‑p. 209
The MMS architecture is provided in Clause 5 of MMS Architecture [72]. 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:
  1. MMS Send
  2. MMS Notification & Confirmation
  3. MMS Retrieval Confirmation & Acknowledgement
  4. MMS Forwarding
  5. MMS Store Requests
  6. MMS Viewing Requests & Responses
  7. MMS Deletion Requests (delete from MMBox and Proxy-Relay)
  8. MMS Cancel Requests
  9. MMS Delivery Reports
  10. 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:
  1. Serving System (clause 7.4.9)
  2. Serving Evolved Packet System (clauses 12.2.3.8, 12.4.3.10, 12.5.3.5).
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.
Information Element
Description

Observed MSISDN
MSISDN of the target.
Observed IMSI
IMSI of the target.
Observed MMS Address
An address in a format as specified in [73]. This is where a SIP URI would be included.
Observed MMS Address for Non-Local ID
An address in a format as specified in [73] that will be intercepted as Non-Local ID target.
Observed IPv4/IPv6 Address
An IPv4 or IPv6 address of the target.
Observed shortcode
An address in a format as specified in [73].
Event type
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.
Event time
Time of the event generation in the ICE. Time stamp shall be generated relative to ICE internal clock.
Event date
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.
From address
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.
MMS Version
The version of MMS used by the target.
Transaction ID
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay.
Message ID
An ID assigned by the MMS Proxy-Relay to uniquely identify an MMS message.
Message Reference
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.
MMS Date/Time
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
Subject of the MM.
Message Class
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".
Expiry
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
Priority of the MM assigned by the originator MMS UE.
Sender Visibility
An indication that the sender's address should not be delivered to the recipient.
Delivery Report
Specifies whether the originator MMS UE requests a delivery report from each recipient.
Read Report
Specifies whether the originator MMS UE requests a read report from each recipient.
Store
Specifies whether the originator MMS UE wants the submitted MM to be saved in the user's MMBox, in addition to sending it.
Applic-ID
Identification of the originating application of the original MM.
Reply-Applic-ID
Identification of the destination application of the original MM.
Aux-Applic-Info
Auxiliary application addressing information as indicated in the original MM.
Content Class
Classifies the content of the MM to the smallest content class to which the message belongs.
DRM Content
Indicates if the MM contains any DRM-protected element.
Adaptation Allowed
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.
Content Type
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.
MM State
Identifies the value of the MM State associated with a to be stored or stored MM.
MM Flags
Identifies a keyword to add or remove from the list of keywords associated with a stored MM.
Content Location
This field defines the location of the content to be retrieved.
Response Status
MMS specific status.
Response Status Text
Text that qualifies the Response Status.
Store Status
Indicates if the MM was successfully stored in the MMBox.
Store Status Text
Text that qualifies the Store Status.
Message Size
Identifies the size of the MM.
Distribution Indicator
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.
Element Descriptor
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.
Retrieval Mode
Indicates whether manual retrieval mode is recommended for the MM.
Retrieval Mode Text
Explains why manual retrieval mode is recommended for the MM.
Retrieve Status
MMS specific status.
Retrieve Status Text
Text that qualifies the Retrieve Status.
Replace ID
This field indicates the reference (i.e. Message-ID) of the previous MM that is replaced by the current MM.
MMS Status
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.
Report Allowed
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.
Read Status
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.
Cancel ID
This field includes the Message ID identifying the message to be cancelled.
Cancel Status
Provides the status of the cancel request.
MMS Start
A number, indicating the index of the first MM of those selected to have information returned in the response.
MMS 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.
MMS Attributes
A list of information elements that should appear in the view for each selected message.
MMS Totals
Indicates a request for or the actual count of messages currently stored in the MMBox.
MMS Quotas
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.
Correlation ID
Provides a mechanism to correlate IRI for MMS with CC for MMS based on a single MMS event.
MMS Content
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 [73].
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 [73] 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.
Up

18.3.3  MMS EventsWord‑p. 212

18.3.3.1  MMS Send

The MMS Send event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a M-Send.conf (as defined in [73]) to the target. According to [73], the Proxy-Relay sends a M-Send.conf to the target in response to a M-Send.req (as defined in [73]) received from the target for sending an MM to one or more destination party(ies).
The elements of Table 18.3.3.1 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To Recipient(s) address(es) (untranslated and translated)
CC Recipient(s) address(es) (untranslated and translated)
BCC Recipient(s) address(es) (untranslated and translated)
From address (includes both target provided address and if translation occurs, network substituted post-translation address.
MMS Version
Transaction ID
Message ID
MMS Date/Time
Message Class
Expiry
Desired Delivery Time
Priority
Sender Visibility
Delivery Report
Read Report
Store
Applic ID
Reply Applic ID
Content Class
DRM Content
Adaptation Allowed
Content Type
Content Location (from M-Send.conf)
Response Status (from M-Send.conf)
Response Status Text (from M-Send.conf)
Store Status (from M-Send.conf)
Store Status Text (from M-Send.conf)
Correlation (only if MMS CC is also intercepted)

When the MMS Send event is generated and interception of CC is required, the MMS Send CC event is also generated. In this case, the elements of Table 18.3.3.2 will be delivered to the DF3, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Correlation ID
Subject
MMS Content

Up

18.3.3.2  MMS Notification & ResponseWord‑p. 213
The MMS Notification report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a MMS Notification (M-Notification.ind as defined in [73]) to the target indicating the arrival of an MMS for the target.
The elements of Table 18.3.3.3 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To Recipient(s) addresses
CC Recipient(s) addresses
BCC Recipient(s) addresses
From address (included regardless of anonymity)
MMS Version
Transaction ID
Message ID
MMS Date/Time (Timestamp when this MMS was last handled [either originated or forwarded])
Previously Sent By
Previously Sent By Date/Time (May appear multiple times)
MM State
Message Class
Priority
Message Size
Expiry
Distribution Indicator
Element Descriptor
Retrieval Mode
Retrieval Mode Text
Sender Visibility
Delivery Report
Applic ID
Reply Applic ID
Aux Applic Info
DRM Content
Replace ID
Content Location
Correlation ID (only if MMS CC is to be delivered)

The MMS Notification Response report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay receives a MMS Notification Response (M-NotifyResp.ind as defined in [73]) from the target acknowledging the MMS Notification.
The elements of Table 18.3.3.4 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Transaction ID
Message ID
MMS Status
Report Allowed

Up

18.3.3.3  MMS Retrieval & AcknowledgementWord‑p. 215
The MMS Retrieval report event is generated at the MMS Proxy-Relay when the MMS Proxy-Relay sends a Retrieve.conf PDU (as defined in [73]) to the target. According to [73], the MMS Proxy-Relay sends a Retrieve.conf PDU to the target in response to a MMS retrieval request from the target.
The elements of Table 18.3.3.5 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To Recipient(s) addresses
CC Recipient(s) addresses
BCC Recipient(s) addresses
From address (included regardless of anonymity)
MMS Version
Transaction ID
Message ID
MMS Date/Time (Timestamp when this MMS was last handled [either originated or forwarded])
Previously Sent By
Previously Sent By Date/Time (May appear multiple times)
MM State
Message Class
Priority
Sender Visibility
Delivery Report
Read Report
Retrieve Status
Retrieve Status Text
Distribution Indicator
Applic ID
Reply Applic ID
Aux Applic Info
Content Class
DRM Content
Replace ID
Correlation ID (only if MMS CC is also intercepted)

When the MMS Retrieval event is generated and CC interception is required, the MMS Retrieval CC event shall also be generated. In this case, the elements of Table 18.3.3.6 will be delivered to the DF3, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Subject
Correlation ID
MMS Content

The MMS Retrieval Acknowledgement report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay receives a MMS Retrieval Acknowledgement (M-Acknowledge.ind as defined in [73]) from the target acknowledging the transaction to the MMS Proxy-Relay.
The elements of Table 18.3.3.7 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Transaction ID
Message ID
Report Allowed

Up

18.3.3.4  MMS ForwardingWord‑p. 217
The MMS Forwarding report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a M-Forward.conf (as defined in [73]) to the target. According to [73], the MMS Proxy-Relay sends a M-Forward.conf (as defined in [73]) to the target is response to a received a MMS Forwarding Request (M-Forward.ind as defined in [73]) from the target.
The elements of Table 18.3.3.8 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To Recipient(s) address(es) (untranslated and translated)
CC Recipient(s) address(es) (untranslated and translated)
BCC Recipient(s) address(es) (untranslated and translated)
From address (includes both target provided address and if translation occurs, network substituted post-translation target address.
MMS Version
Transaction ID
Message ID
MMS Forward Req Date/Time
Message Class
Expiry
Desired Delivery Time
Priority
Sender Visibility
Delivery Report Allowed
Delivery Report
Read Report
Store
MM State
Content Location
Response Status (from M-Forward.conf)
Response Status Text (from M-Forward.conf)
Store Status (from M-Forward.conf)
Store Status Text (from M-Forward.conf)

Up

18.3.3.5  MMS StoreWord‑p. 218
The MMS Store report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a M-Mmbox-Store.conf (defined in [73]) to the target. According to [73], the Proxy-Relay sends a M-Mmbox-Store.conf) to the target in response to a received MMS Store Request (M-Mmbox-Store.req as defined in [73]) from the target for a MM that has not been retrieved yet.
The elements of Table 18.3.3.9 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
Transaction ID
MMS Version
Content Location
MM State
MM Flags
Store Status
Store Status Text

Up

18.3.3.6  MMS Upload

The MMS Upload report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a M-Mmbox-Upload.conf (defined in [73]) to the target. According to [73], the MSM Proxy-Relay sends a M-Mmbox-Upload.conf to the target in response to a received MMS Upload Request (M-Mmbox-Upload.req as (defined in [73]) from the target.
The elements of Table 18.3.3.10 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
Transaction ID
MMS Version
MM State
MM Flags
Content Type
MM Description PDU (see Table 18.3.3.19)
Content Location (from M-Mmbox-Upload.conf)
Store Status (from M-Mmbox-Upload.conf)
Store Status Text (from M-Mmbox-Upload.conf)
Correlation ID (only if MMS CC is also intercepted)

When the MMS Upload event is generated and CC interception is also required, an MMS Upload CC event is also generated at the MMS Proxy-Relay. In this case, the elements of Table 18.3.3.11 will be delivered to the DF3, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Correlation ID
MMS Content

Up

18.3.3.7  MMS Delete (Stored in MMBox or in Proxy-Relay)Word‑p. 219
The MMS Delete event is generated at the MMS Proxy-Relay when the MMS Proxy-Relay sends a M-Mmbox-Delete.conf (defined in [73]) to the target. According to [73], the MMS Proxy-Relay sends a M-Mmbox-Delete.conf to the target in response to a received a MMS Delete Request (M-Mmbox-Delete.req as defined in [73]) from the target to delete an MM from the target's MMBox.
The elements of Table 18.3.3.12 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
Transaction ID
MMS Version
Content Location
Response Status
Response Status Text

Up

18.3.3.8  MMS Delivery

The MMS Delivery report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a MMS Delivery Notification (M-Delivery.ind as defined in [73]) to the target.
The elements of Table 18.3.3.13 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To Recipient address
Handled Date/Time
Message ID
MMS Status
MMS Status text
Applic-ID
Reply-Applic-ID
Aux-Applic-Info

Up

18.3.3.9  MMS Read ReplyWord‑p. 220
The MMS Read Reply-From-Target report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay receives a MMS Read Reply Notification (M-Read-Rec.ind as defined in [73]) from the target. The elements of Table 18.3.3.14 will be delivered to the DF2, if available.
The MMS Read Reply-To-Target report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a MMS Read Reply Notification (M-Read-Orig.ind as defined in [73]) to the target. The elements of Table 18.3.3.15 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To (MMS sender's address)
From address (includes both target provided address and if translation occurs, network substituted post-translation target address).
Message ID
Read Status
Applic-ID
Reply-Applic-ID
Aux-Applic-Info
Table 18.3.3.15: Information Elements for MMS Read Reply to Target Event
Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
To (target's address)
From address (address of read reply source).
Message ID
Read Status
Read Status text
Applic-ID
Reply-Applic-ID
Aux-Applic-Info

Up

18.3.3.10  MMS CancelWord‑p. 221
The MMS Cancel report event is generated at the MMS Proxy-Relay, when the MMS Proxy-Relay sends a MMS Cancel Request (M-Cancel.req as defined in [73]) to the target.
The elements of Table 18.3.3.16 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Cancel ID (includes the Message ID identifying the message to be cancelled)
Cancel Status

18.3.3.12  MMS MMBox Viewing

The MMS MMBox View Request event is generated at the MMS Proxy-Relay when the MMS Proxy-Relay receives a MMS MMBox Viewing Request (M-Mbox-View.req as defined in [73]) from the target. In this case, the elements of Table 18.3.3.17 will be delivered to the DF2, if available.
The MMS MMBox View Confirm event is generated at the MMS Proxy-Relay when the MMS Proxy-Relay sends a M-Mbox-View.conf (defined in [73]). In this case, the elements of Table 18.3.3.18 will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Transaction ID
MM State
MM Flags
Content Location
MMS Start
MMS Limit
MMS Attributes
MMS Totals
MMS Quotas

 
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Transaction ID
MM State
MM Flags
Content Location
MMS Start
MMS Limit
MMS Attributes
MMS Totals
MMS Quotas
Response Status
Response Status Text
MMS Message Count
Content Type
Correlation ID (only if MMS CC is also intercepted)
MMBox Description PDU (see Table 18.3.3.19)

 
Information Element

Correlation ID
To Recipient(s) addresses
CC Recipient(s) addresses
BCC Recipient(s) addresses
From address (included regardless of anonymity)
Message ID
MMS Date/Time
Previously Sent By (May appear multiple times)
Previously Sent By Date/Time (May appear multiple times)
MM State
MM Flags
Message Class
Priority
Delivery Time
Expiry
Sender Visibility
Delivery Report
Read Report
Message Size
Content Location
Content Type

When the MMS MMBox View Confirm event is generated at the MMS Proxy-Relay and CC interception is also required, the MMS Proxy-Relay also generates a MMS MMBox View Confirm CC event. In this case, the elements of Table 18.3.3.20 will be delivered to the DF3, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed MMS Address
Observed IPv4/IPv6 Address
Event Type
Event Time
Event Date
Network Element Identifier
MMS Version
Correlation ID
MMS Content

Up


Up   Top   ToC