15 Interception of Messaging Services
33.1083G Security3GPPHandover interface for Lawful Interception (LI)Release 17TS
15.1 Overview
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 [18].
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. TS 33.107 [19] defines the SMS events to be reported. This clause will identify the set of event reports that are to be sent from the DF to the LEMF to achieve this separated delivery based on capabilities that already exist in the rest of this specification.
The network nodes, involved in providing the interception of messaging services, shall be determined based on the deployment configuration and the messaging scenario.
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.
15.2 SMS
15.2.1 Introduction
LI for SMS over a GPRS and UMTS access is specified in Clause 6. LI for SMS over IMS (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 7.
15.2.2 SMS over GPRS/UMTS
For separate delivery of SMS when SMS is used in conjunction with GPRS or UMTS access, the following records shall be sent by DF2 to the LEMF:
1) SMS MO and SMS MT Communication REPORT Records (Clause 6.5.1.1).
2) HLR Related REPORT Records:
a. Serving System REPORT Record (6.5.1.1);
b. Cancel location REPORT Record (6.5.1.1);
c. Register location REPORT Record (6.5.1.1);
d. Location information request REPORT Record (6.5.1.1).
The above REPORT Records shall be reported from DF2 to the LEMF independent of any other services that may or may not be intercepted.
15.2.3 SMS over IMS
For separate delivery of SMS when SMS over IMS (using IMS SIP signalling handled by the core network) is used, the following REPORT Records shall be reported by DF2 to the LEMF:
1) SMS over IP REPORT Record (see Table 15.2.3.1).
2) HSS related REPORT Records:
a. Serving System (6.5.1.1) or Serving Evolved Packet System (10.5.1.1) for use when roaming
b. Registration termination or Cancel Location (6.1.1.1 or 10.5.1.1);
c. Register location REPORT Record (6.5.1.1 or 10.5.1.1);
d. Location information request REPORT Record (6.5.1.1. or 10.5.1.1).
The above REPORT Records shall be able to be reported from DF2 to the LEMF independent of any other services that may or may not be intercepted.
Table 15.2.3.1: SMS over IMS REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed SIP-URI |
C |
SIP URI of the target (if available). |
|
observed TEL-URI |
C |
TEL URI of the target (if available). |
|
observed IMEI |
C |
IMEI of the target (if available). |
|
event type |
M |
Provide SMS over IP event type. |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
PANI header information |
C |
Elements of P-Access-Network-Info header information in SIP messages; described in TS 24.229 [76] §7.2A.4. Provided if available and applicable. |
|
SMS originating address |
M |
Shall be provided to identify the origination address for the SMS. |
|
SMS destination address |
M |
Shall be provided to identify the destination address for the SMS. |
|
SMS |
C |
Provided if the delivery of SMS Content is lawfully authorized |
|
service centre address |
M |
Shall be provided. |
|
SMS Initiator |
M |
Shall be provided to indicate whether the SMS is MO, MT, or Undefined. |
|
location information |
C |
Provide, when authorized, to identify location information for the target’s MS. |
|
Time of Location |
C |
Date/Time of UE Location (if target location provided). |
15.3 MMS
15.3.1 Introduction
LI for Separated Delivery of MMS (see Clause 18.3 of [19]), the events of Clause 18.3 need to be reported to the LEMF from DF2 and for CC from DF3, respectively. A Report record shall be utilized to report the IRI events while a CC shall be reported as described in this clause using a ULIC header.
The CC PDU contains the content of an MMS.
15.3.2 Identifiers
15.3.2.1 Overview
Specific identifiers are necessary to identify a target for interception uniquely and to correlate IRI and CC, which is conveyed over the different handover interfaces (HI2 and HI3). The identifiers are defined in the clauses below.
For the delivery of CC, the MMS Proxy-Relay provides correlation numbers and target identities to DF3. The MMS Proxy-Relay reports the IRI associated with the MMS services.
For the delivery of CC and IRI, the MMS Proxy-Relay provides correlation numbers and target identities to the DF2 and DF3. For a given target the correlation number for a given MMS is unique across all MMS involving the target.
15.3.2.2 Lawful Interception Identifier
For each target identity related to an interception measure, the authorized operator (CSP) shall assign a Lawful Interception Identifier (LIID), which has been agreed between the LEA and the operator (CSP). This shall be a LIID specific to MMS interception, per national regulation.
Using an indirect identification, pointing to a target identity makes it easier to keep the knowledge about a specific target limited within the authorized operator (CSP) and the handling agents at the LEA.
The LIID is a component of the CC delivery procedure and of the IRI records. It shall be used within any information exchanged at the handover interfaces HI2 and HI3 for identification and correlation purposes.
The LIID format shall consist of alphanumeric characters. It might for example, among other information, contain a lawful authorization reference number, and the date, when the lawful authorization was issued.
The authorized operator (CSP) shall either enter, based on an agreement with each LEA, a unique LIID for each target identity of the target or a single LIID for multiple target identities all pertaining to the same target.
If more than one LEA intercepts the same target identity, there shall be unique LIIDs assigned relating to each LEA.
15.3.2.3 Correlation Number
For a given target the Correlation Number is for a given MMS is unique across all MMS involving the target and used for the following purpose:
– correlate CC with IRI.
NOTE: The Correlation Number is at a minimum unique for each concurrent communication of a target within a lawful authorization.
15.3.6 IRI for MMS
15.3.6.1 General
The events defined in TS 33.107 [19] are used to generate records for the delivery via HI2.
There are multiple different event types received at DF2 level. According to each event, a Record is sent to the LEMF if this is required. The following table gives the mapping between event type received at DF2 level and record type sent to the LEMF.
Table 15.3.6.1.1: Mapping between MMS Events and HI2 records type
|
Event |
IRI Record Type |
|
MMS Send |
REPORT |
|
MMS Notification & Confirmation |
REPORT |
|
MMS Retrieval Confirmation |
REPORT |
|
MMS Retrieval Acknowledgement |
REPORT |
|
MMS Forwarding |
REPORT |
|
MMS Store Request |
REPORT |
|
MMS Viewing Request |
REPORT |
|
MMS Viewing Response |
REPORT |
|
MMS Deletion Request |
REPORT |
|
MMS Cancel Request |
REPORT |
|
MMS Read Report |
REPORT |
The Serving System and Serving Evolved Packet System events are reported as per Clause 6.5.1.1 and 10.5.1.1, respectively, of the present document.
A set of information is used to generate the records. The records used transmit the information from mediation function to LEMF. This set of information can be extended in the ICE or DF2 MF, if this is necessary in a specific country. The following table gives the mapping between information received per event and information sent in records.
Table 15.3.6.1.2: Mapping between Events information and IRI information
|
Parameter |
Description |
HI2 ASN.1 parameter |
|---|---|---|
|
Observed MSISDN |
MSISDN: the coding may be based on the global-phone-number, defined in Multimedia Messaging Service Encapsulation Protocol OMA-TS-MMS_ENC-V1_3-20110913-A {90]. |
partyInformation |
|
Observed IMSI |
IMSI of the target |
partyInformation |
|
Observed MMD Address |
An address in a format as specified in [90]. This is where a SIP URI would be included. |
partyInformation |
|
Observed MMS Address for Non-Local ID |
An address in a format as specified in [90]. National regulation requires Non-Local ID as target. In that case, It may be E164 number [29], or alphanumeric or numeric short code, or e-mail described in section 3.4 of IETF RFC 2822 [92], but excluding the obsolete definitions as indicated by the "obs-"prefix.(see clause 8 of Multimedia Messaging Service Encapsulation Protocol OMA-TS-MMS_ENC-V1_3-20110913-A {90]). |
partyInformation |
|
Observed shortcode |
Alphanumeric or numeric short code as defined in Multimedia Messaging Service Encapsulation Protocol OMA-TS-MMS_ENC-V1_3-20110913-A {90]. |
partyInformation |
|
Observed IPv4/IPv6 Address |
An IPv4 or IPv6 address of the target. |
partyInformation |
|
Event Type |
Description which type of event is delivered: Send, Notification, Notification Response, Retrieval, Retrieval Acknowledgement, Forwarding, Store, Upload, Delete, Delivery, Read Reply From Target, Read Reply To Target, Cancel, View Request, View Confirm. |
mMSEvent |
|
Event Date |
Date of the event generation in the MMS Proxy/Server. |
timestamp |
|
Event Time |
Time of the event generation in the MMS Proxy/Server. Timestamp shall be based on the MMS Proxy/Server internal clock. |
|
|
Correlation Number |
The correlation number is used to correlate CC and IRI. |
mMSCorrelationNumber |
|
Applic-ID |
Identification of the originating application of the original MM. |
applicID |
|
Aux Applic Info |
Auxiliary application addressing information as indicated in the original MM. |
auxApplicInfo |
|
BCC Recipients |
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. |
mMSParties/bCCAddresses |
|
Cancel id |
This field includes the Message ID identifying the message to be cancelled. |
cancelID |
|
Cancel Status |
Provides the status of the cancel request. |
cancelStatus |
|
CC Recipients |
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. |
mMSParties/CCAddresses |
|
Content Class |
Classifies the content of the MM to the smallest content class to which the message belongs. |
contentClass |
|
Content Location |
This field defines the location of the content to be retrieved. |
contentLocation |
|
Content Type |
The content type of the MM. |
contentType |
|
Delivery report |
Specifies whether the originator MMS UE requests a delivery report from each recipient. |
deliveryReport |
|
Desired Delivery Time |
Date and Time of desired delivery. Indicates the earliest possible delivery of the MM to the recipient. |
desiredDeliveryTime |
|
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. |
distributionIndicator |
|
DRM Content |
Indicates if the MM contains any DRM-protected element. |
dRMContent |
|
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. |
elementDescriptor |
|
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. |
expiry |
|
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. |
mMSParties/from |
|
Lawful interception identifier |
Unique number for each lawful authorization. |
lawfulInterceptionIdentifer |
|
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". |
messageClass |
|
Message ID |
An ID assigned by the MMS Proxy-Relay to uniquely identify an MMS message. |
messageID |
|
MM State |
Identifies the value of the MM State associated with a to be stored or stored MM. |
mMState |
|
MM State Flags |
Identifies a keyword to add or remove from the list of keywords associated with a stored MM. |
mMStateFlags |
|
MMS Attributes |
A list of information elements that should appear in the view for each selected message. |
mMSAttributes |
|
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. |
mMSDateTime |
|
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. |
mMSLimit |
|
MMS Message Count |
Identifies the number of messages in the content part of the PDU. |
mMSMessageCount |
|
MMS Quotas |
Indicates a request for or the actual quotas for the user’s MMBox in messages or bytes. |
mMSQuotas |
|
MMS Start |
A number, indicating the index of the first MM of those selected to have information returned in the response. |
mMSStart |
|
MMS Status |
Provides a MMS status. A status of "retrieved" is only signalled by the retrieving UE after retrieval of the MM. |
mMSStatus |
|
MMS Status Text |
Text that qualifies the MMS Status. |
mMSStatusText |
|
MMS Totals |
Indicates a request for or the actual count of messages currently stored in the MMBox. |
|
|
MMS Version |
The version of MMS used by the target. |
|
|
Network Identifier |
Operator ID plus unique identifier for the MMS Server. |
networkIdentifer |
|
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. |
previouslySentBy |
|
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. |
reviouslySentByDateTime |
|
Priority |
Priority of the MM assigned by the originator MMS Client. |
priority |
|
Read report |
Specifies whether the originator MMS UE requests a read report from each recipient. |
readReport |
|
Read Status |
Text explanation corresponding to the Read Status. |
readStatus |
|
Replace ID |
This field indicates the reference (i.e. Message-ID) of the previous MM that is replaced by the current MM. |
replaceID |
|
Reply Applic ID |
Identification of an application to which replies, delivery reports, and read reports are addressed. |
replyApplicID |
|
Report Allowed |
Indication whether or not the sending of delivery report is allowed by the recipient MMS Client. |
reportAllowed |
|
Response Status |
MMS specific status. |
responseStatus |
|
Response Status Text |
Text that qualifies the Response Status. |
responseStatusText |
|
Retrieval Mode |
Indicates whether manual retrieval mode is recommended for the MM. |
retrievalMode |
|
Retrieval Mode Text |
Explains why manual retrieval mode is recommended for the MM. |
retrievalModeText |
|
Retrieve Status |
MMS specific status. |
retrieveStatus |
|
Retrieve Status Text |
Text that qualifies the Retrieve Status. |
retrieveStatusText |
|
Sender visibility |
An indication that the sender’s address should not be delivered to the recipient. |
senderVisibility |
|
Store |
Specifies whether the originator MMS UE wants the submitted MM to be saved in the user’s MMBox, in addition to sending it. |
store |
|
Store Status |
Indicates if the MM was successfully stored in the MMBox. |
storeStatus |
|
Store Status Text |
Text that qualifies the Store Status. |
storeStatusText |
|
To Recipients |
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. |
mMSParties/toAddresses |
|
Transaction ID |
An ID used to correlate an MMS request and response between the target and the MMS Proxy-Relay. |
transactionID |
NOTE: LIID parameter has to be present in each record sent to the LEMF.
15.3.6.2 Events and Event Information
15.3.6.2.1 Overview
This clause describes the information sent from the Delivery Function (DF) to the Law Enforcement Monitoring Facility (LEMF) to support Lawful Interception (LI). The information is described as records and information carried by a record. This focus is on describing the information being transferred to the LEMF.
The IRI events and data are encoded into records as defined in the Table 15.3.6.1.1 Mapping between MMS Events and HI2 records type and Annex B.15 Intercept related information (HI2). IRI is described in terms of a ‘causing event’ and information associated with that event. Within each IRI record there is a set of events and associated information elements to support the particular service.
The communication events described in Table 15.3.6.1.1: Mapping between MMS Events and HI2 record type and Table 15.3.6.1.2: Mapping between Events information and IRI information convey the basic information for reporting the disposition of a communication. This clause describes those events and supporting information.
Each record described in this clause consists of a set of parameters. Each parameter is either:
– mandatory (M) required for the record,
– conditional (C) required in situations where a condition is met (the condition is given in the Description), or
– optional (O) provided at the discretion of the implementation.
The information to be carried by each parameter is identified. Both optional and conditional parameters are considered to be OPTIONAL syntactically in ASN.1 Stage 3 descriptions. The Stage 2 inclusion takes precedence over Stage 3 syntax.
15.3.6.2.2 REPORT record information
The REPORT record is used to convey the events of MMS service interception.
The REPORT record shall be triggered when:
– the target sends a MMS;
– the target receives a notification of an incoming MMS;
– the target responds to the notification of an incoming MMS;
– an MMS is retrieved by the target;
– the target acknowledges to the retrieved MMS;
– the target forwards an MMS;
– the target stores an MMS in the Mmbox;
– the target uploads an MMS to the Mmbox;
– the target deletes a MMS stored in the Mmbox;
– the target receives a MMS Delivery report;
– the target sends a MMS Read Reply;
– the target receives a MMS Read Reply;
– the target receives a MMS cancel request;
– the target sends a MMbox view request;
– the target receives a confirmation of a sent MMbox View request.
Table 15.3.6.2.2.1: MMS Send REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
Observed IMPU/IMPI |
||
|
Observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Send). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
correlation number |
C |
Provide to allow correlation of CC and IRI when CC is authorized. |
|
To Recipients |
M |
Shall be provided and shall include untranslated and translated addresses. |
|
CC Recipients |
C |
Provide if available to identify CC recipients. When included, shall provide untranslated and translated addresses. |
|
BCC Recipients |
C |
Provide if available to identify BCC recipients. When included, shall provide untranslated and translated addresses. |
|
From address |
M |
Shall be provided (includes both target provided address and if translation occurs, network substituted post-translation address). |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
MMS Date/Time |
M |
Shall be provided. |
|
Message Class |
C |
Provide if available to identify the message class. |
|
Expiry |
M |
Shall be provided (either the signalled expiry or the default, whichever applies). |
|
Desired Delivery Time |
C |
Provide when sent by the target to indicate the desired MMS delivery time. |
|
Priority |
C |
Provide when sent by the target to indicate the desired MMS priority. |
|
Sender visibility |
C |
Provide when 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. |
|
Delivery report |
C |
Provide when sent by the target to indicate the desired delivery report. |
|
Read report |
C |
Provide when sent by the target to indicate the desired read report. |
|
Store |
C |
Provide when sent by the target to indicate the MMS is to be stored. |
|
Applic ID |
C |
Provide when sent by the target to identify the destination application. |
|
Reply Applic ID |
C |
Provide when sent by the target to identify the application to which replies, delivery reports, and read reports are addressed. |
|
Content Class |
C |
Provide when sent by the target to identify the class of the content. |
|
DRM Content |
C |
Provide when sent by the target to indicate if the MM contains any DRM-protected element. |
|
Adaptation Allowed |
C |
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. |
|
Content Type |
M |
Shall be provided. |
|
Content Location |
C |
Provide if signalled to the target in response to the target sending an MMS. |
|
Response Status |
C |
Provide if signalled to the target in response to the target sending an MMS. |
|
Response Status Text |
C |
Provide if signalled to the target in response to the target sending an MMS. |
|
Store Status |
C |
Provide if signalled to the target in response to the target sending an MMS. |
|
Store Status Text |
C |
Provide if signalled to the target in response to the target sending an MMS. |
Table 15.3.6.2.2.2: MMS Notification REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Notification). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
correlation number |
C |
Provide to allow correlation of CC and IRI when delivery of CC is authorized. |
|
To Recipients |
M |
Shall be provided and shall include untranslated and translated addresses. |
|
CC Recipients |
C |
Provide if available to identify CC recipients. When included, shall provide untranslated and translated addresses. |
|
BCC Recipients |
C |
Provide if available to identify BCC recipients. When included, shall provide untranslated and translated addresses. |
|
From address |
M |
Shall be provided regardless of anonymity (includes both target provided address and if translation occurs, network substituted post-translation address). |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
MMS Date/Time |
M |
Shall be provided. |
|
Message Class |
M |
Shall be provided. |
|
Expiry |
M |
Shall be provided |
|
Distribution indicator |
C |
If sent to the target, shall be included. |
|
Element descriptor |
C |
If sent to the target, shall be included. |
|
Retrieval Mode |
C |
If sent to the target, shall be included. |
|
Retrieval Mode Text |
C |
If sent to the target, shall be included. |
|
Sender visibility |
C |
If the originator indicated a desire to withhold their address from the MM recipient, then this parameter shall be included. |
|
Delivery report |
C |
If sent to the target, shall be included. |
|
Read report |
C |
Provide when sent by the target to indicate the desired read report. |
|
Applic ID |
C |
If sent to the target, shall be included. |
|
Reply Applic ID |
C |
If sent to the target, shall be included. |
|
Aux Applic Info |
C |
If sent to the target, shall be included. |
|
Content Class |
C |
If sent to the target, shall be included. |
|
DRM Content |
C |
If sent to the target, shall be included. |
|
Replace ID |
C |
If sent to the target, shall be included. |
|
Content Location |
C |
If sent to the target, shall be included. |
Table 15.3.6.2.2.3: MMS Notification Response REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Notification Response). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
MMS Status |
M |
Shall be provided. |
|
Report Allowed |
C |
If sent by the target, shall be included. |
Table 15.3.6.2.2.4: MMS Retrieval REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Retrieval). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
correlation number |
C |
Provide to allow correlation of CC and IRI when delivery of CC is authorized. |
|
To Recipients |
M |
Shall be provided and shall include untranslated and translated addresses. |
|
CC Recipients |
C |
Provide if available to identify CC recipients. When included, shall provide untranslated and translated addresses. |
|
BCC Recipients |
C |
Provide if available to identify BCC recipients. When included, shall provide untranslated and translated addresses. |
|
From address |
M |
Shall be provided regardless of anonymity (includes both target provided address and if translation occurs, network substituted post-translation address). |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
MMS Date/Time |
M |
Shall be provided. |
|
Previously sent by |
C |
If available, shall be provided. |
|
Previously sent by Date/Time |
C |
If available, shall be provided. |
|
MM State |
C |
Provide if sent to the target. |
|
Message Class |
C |
Provide if available to identify the message class. |
|
Priority |
M |
Shall be provided (either the signalled priority or the default, whichever applies). |
|
Delivery report |
C |
Provide when sent by the target to indicate the desired delivery report. |
|
Read report |
C |
Provide when sent by the target to indicate the desired read report. |
|
Sender visibility |
C |
If the originator indicated a desire to withhold their address from the MM recipient, then this parameter shall be included. |
|
Retrieve Status |
C |
If sent to the target, shall be included. |
|
Retrieve Status Text |
C |
If sent to the target, shall be included. |
|
Distribution indicator |
C |
If sent to the target, shall be included. |
|
Applic ID |
C |
If sent to the target, shall be included. |
|
Reply Applic ID |
C |
If sent to the target, shall be included. |
|
Aux Applic Info |
C |
If sent to the target, shall be included. |
|
Content Class |
C |
If sent to the target, shall be included. |
|
DRM Content |
C |
If sent to the target, shall be included. |
|
Replace ID |
C |
If sent to the target, shall be included. |
|
Content Type |
C |
If sent to the target, shall be included. |
Table 15.3.6.2.2.5: MMS Retrieval Acknowledgement REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMboxID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Retrieval Acknowledgement). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
Report Allowed |
C |
If sent to the target, shall be included. |
Table 15.3.6.2.2.6: MMS Forwarding REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Forwarding). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
correlation number |
C |
Provide to allow correlation of CC and IRI when delivery of CC is authorized. |
|
To Recipients |
M |
Shall be provided and shall include untranslated and translated addresses. |
|
CC Recipients |
C |
Provide if available to identify CC recipients. When included, shall provide untranslated and translated addresses. |
|
BCC Recipients |
C |
Provide if available to identify BCC recipients. When included, shall provide untranslated and translated addresses. |
|
From address |
M |
Shall be provided (includes both target provided address and if translation occurs, network substituted post-translation address). |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Message ID |
M |
Shall be provided. |
|
MMS Forward Req Date/Time |
M |
Shall be provided. |
|
Message Class |
C |
Provide if available to identify the message class. |
|
Expiry |
M |
Shall be provided (either the signalled expiry or the default, whichever applies). |
|
Desired Delivery Time |
C |
Provide when sent by the target to indicate the desired MMS delivery time. |
|
Priority |
C |
Provide when sent by the target to indicate the desired MMS priority. |
|
Sender visibility |
C |
Provide when 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. |
|
Delivery report allowed |
M |
Shall be provided to report the target requested reporting to the original sender or the default, whichever applies. |
|
Delivery report |
C |
Provide when sent by the target to indicate the desired delivery report. |
|
Read report |
C |
Provide when sent by the target to indicate the desired read report. |
|
Store |
C |
Provide when sent by the target to have the forwarded MM stored. |
|
MM State |
C |
Provide when sent by the target to set the state for the forwarded MM when it is stored. |
|
Content Location |
M |
Shall be provided. |
|
Response Status |
M |
Shall be provided. |
|
Response Status Text |
C |
If provided to the target, shall be included. |
|
Store Status |
C |
If sent to the target, shall be included. |
|
Store Status Text |
C |
If sent to the target, shall be included. |
Table 15.3.6.2.2.7: MMS Store REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Forwarding). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
MM State |
C |
If provided by the target, shall be included. |
|
MM Flags |
C |
If provided by the target, shall be included. |
|
Content Location |
M |
Shall be provided. |
|
Store Status |
M |
Shall be provided. |
|
Store Status Text |
C |
If sent to the target, shall be provided. |
Table 15.3.6.2.2.8: MMS Upload REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Upload). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
MM State |
C |
If sent by the target, shall be included. |
|
MM Flags |
C |
If sent by the target, shall be included. |
|
Content Type |
M |
Shall be provided. |
|
Content Location |
C |
If available, shall be included. |
|
Store Status |
M |
Shall be provided. |
|
Store Status Text |
C |
If sent to the target, shall be included. |
|
MMBox Description pdu |
M |
Shall be provided. The MMBox description PDU (as described in Table 15.3.6.2.2.16) corresponds to the particular MM being uploaded. |
Table 15.3.6.2.2.9: MMS Delete REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Delete). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction ID |
M |
Shall be provided. |
|
Content Location |
M |
Shall be provided. |
|
Response Status |
M |
Shall be provided. |
|
Response Status Text |
C |
If available, shall be provided. |
Table 15.3.6.2.2.10: MMS Delivery REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Delivery). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
To Recipients |
M |
Shall be provided. |
|
MMS date/time |
M |
Shall be provided. |
|
Message id |
M |
Shall be provided. |
|
MMS Status |
M |
Shall be provided. |
|
MMS Status Text |
C |
If available, shall be included. |
|
Applic-ID |
C |
If available, shall be provided. |
|
Reply-Applic-id |
C |
If available, shall be provided. |
|
Aux-Applic-Info |
C |
If available, shall be provided. |
Table 15.3.6.2.2.11: MMS Read Reply From Target REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Read Reply From Target). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
To Recipients |
M |
Shall be provided. Identifies the recipient of the read report. |
|
From address |
M |
Shall be provided and include target’s MMS address. |
|
Message id |
M |
Shall be provided. |
|
Read Status |
M |
Shall be provided. |
|
MMS date time |
M |
Shall be provided. |
|
Applic-ID |
C |
If available, shall be provided. |
|
Reply-Applic-id |
C |
If available, shall be provided. |
|
Aux-Applic-Info |
C |
If available, shall be provided. |
Table 15.3.6.2.2.12: MMS Read Reply To Target REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Read Reply To Target). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
To Recipients |
M |
Shall be provided and include the address of the read recipient (i.e., the target). |
|
From address |
M |
Shall be provided and include the address of read reply source. |
|
Message id |
M |
Shall be provided. |
|
Read Status |
M |
Shall be provided. |
|
MMS date time |
C |
If available, shall be provided. |
|
Applic-ID |
C |
If available, shall be provided. |
|
Reply-Applic-id |
C |
If available, shall be provided. |
|
Aux-Applic-Info |
C |
If available, shall be provided. |
Table 15.3.6.2.2.13: MMS Cancel REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS Cancel). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Cancel id |
M |
Shall be provided. |
|
Cancel Status |
C |
If available, shall be provided. |
Table 15.3.6.2.2.14: MMS View Request REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 number |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS View Request). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction id |
M |
Shall be provided. |
|
MM State |
C |
If provided by the target, shall be included. |
|
MM Flags |
C |
If provided by the target, shall be included. |
|
Content Location |
C |
If provided by the target, shall be included. |
|
MMS Start |
C |
If provided by the target, shall be included. |
|
MMS Limit |
C |
If provided by the target, shall be included. |
|
MMS Attributes |
C |
If provided by the target, shall be included. |
|
MMS Totals |
C |
If provided by the target, shall be included. |
|
MMS Quotas |
C |
If provided by the target, shall be included. |
Table 15.3.6.2.2.15: MMS View Confirm REPORT Record
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
observed IMEI |
||
|
observed IMSI |
C |
Provide at least one and others when available. |
|
observed MSISDN |
||
|
observed IMPU/IMPI |
||
|
observed E.164 |
||
|
observed MMS Address/MMbox ID |
||
|
observed IPv4/IPv6 Address |
||
|
event type |
M |
Provide MMS event type (i.e., MMS View Confirm). |
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
MMS Version |
M |
Shall be provided. |
|
Transaction id |
M |
Shall be provided. |
|
MM State |
C |
Provide if sent to the target. |
|
MM Flags |
C |
Provide if sent to the target. |
|
Content Location |
C |
Provide if sent to the target. |
|
MMS Start |
C |
Provide if sent to the target. |
|
MMS Limit |
C |
Provide if sent to the target. |
|
MMS Attributes |
C |
Provide if sent to the target. |
|
MMS Totals |
C |
Provide if sent to the target. |
|
MMS Quotas |
C |
Provide if sent to the target. |
|
Response Status |
M |
Shall be provided. |
|
Response Status Text |
C |
Provide if sent to the target. |
|
MMS Message Count |
C |
Provide if sent to the target. |
|
Content type |
M |
Shall be provided. |
|
MMBox Description pdu |
M |
Shall provide one or more MMBox description PDUs where each MMBox description PDU (as described in Table 15.3.6.2.2.16) corresponds to a particular MM. |
Table 15.3.6.2.2.16: MMS Description PDU
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
correlation number |
C |
Provide to allow correlation of CC and IRI when delivery of CC is authorized. |
|
To Recipients |
M |
Shall be included. |
|
CC Recipients |
C |
Provide if available. |
|
BCC Recipients |
C |
Provide if available. |
|
From address |
M |
Shall be provided regardless of anonymity |
|
Message ID |
C |
Shall be provided unconditionally for the MMS View Confirm report record and shall be included for the MMS Upload report record 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. |
|
MMS Date Time |
C |
If available for the MM, shall be provided. |
|
Previously Sent by |
C |
If available for the MM, shall be provided. |
|
Previously Sent by Date Time |
C |
If available for the MM, shall be provided. |
|
MM State |
C |
Shall be included for the MMS View Confirm report record and shall be included in the MMS Upload report record if provided by the target. |
|
MM Flags |
C |
If at least one keyword is associated with the MM, then this parameter shall be included. This parameter may convey all the keywords associated with the MM. If no keywords are associated with the MM, then this parameter may be excluded. |
|
Message Class |
C |
If available, shall be included. |
|
Priority |
C |
If available, shall be provided. |
|
Delivery Time |
C |
If available, shall be provided. |
|
Expiry |
C |
If available, shall be provided. |
|
Delivery report |
C |
If available, shall be provided. |
|
Read report |
C |
If available, shall be provided. |
|
Message size |
C |
If available, shall be provided. |
|
Content Location |
C |
Shall only be used in conjunction with the MMS View Confirm report record |
|
Content type |
M |
Shall be provided. |
15.3.7 CC for MMS
15.3.7.1 General
The CC for an MMS shall be provided by the ICE to DF3 which will then handle delivery over HI3 to the LEMF.
Correlation information shall be included in the CC to allow for correlation of the CC to the IRI to which it pertains. Table 15.3.7.1 shows the contents of the MMS CC PDU to be sent to the LEMF when CC is reported.
Table 15.3.7.1: MMS CC PDU
|
Parameter |
MOC |
Description/Conditions |
|---|---|---|
|
event date |
M |
Provide the date and time the event is detected. |
|
event time |
||
|
network identifier |
M |
Shall be provided including the network element identifier. |
|
lawful intercept identifier |
M |
Shall be provided. |
|
correlation number |
M |
Provide to allow correlation of CC and IRI |
|
MMS Version |
M |
Shall be provided, if available. |
|
Transaction id |
M |
Shall be provided, if available. |
|
MMS Content |
M |
Shall be provided. |