7.8 LI at SCEF

33.1283GPPProtocol and procedures for Lawful Interception (LI)Release 18SecurityStage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.8.1 Provisioning over LI_X1

7.8.1.1 General

For NIDD using SCEF:

– If delivery type for the warrant is "IRI and CC", then the IRI-POI and the CC-POI in the SCEF, the MDF2 and MDF3 shall be provisioned.

– If delivery type for the warrant is "IRI", then the IRI-POI in the SCEF and the MDF2 shall be provisioned.

– Delivery type "CC" is not applicable to the warrant.

For device triggering, MSISDN-less MO SMS and Parameter Provisioning:

– the delivery type for the warrant is "IRI"; the IRI-POI in the SCEF and the MDF2 shall be provisioned.

7.8.1.2 Provisioning of the IRI-POI and CC-POI in SCEF

The IRI-POI and CC-POI present in the SCEF are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.

The POI in the SCEF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):

– IMSI.

– MSISDN.

– External Identifier.

NOTE: For Parameter Provisioning, only MSISDN and External Identifier are applicable.

7.8.2 LI for NIDD using SCEF

7.8.2.1 Generation of xIRI at IRI-POI in SCEF over LI_X2

7.8.2.1.1 General

The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in TS 33.127 [5] clause 7.8.2.3, the details of which are described in the following clauses. Each event will be based on PDN Connection between SCEF and target UE, except in case of Unsucessful Procedure.

7.8.2.1.2 SCEF PDN connection establishment

The IRI-POI in the SCEF/IWK-SCEF shall generate an xIRI containing an SCEFPDNConnectionEstablishment record when the IRI-POI present in the SCEF/IWK-SCEF detects that a Non-IP PDN Connection using SCEF has been established by the target UE. The IRI-POI present in the SCEF/IWK-SCEF shall generate the xIRI for the following events (see TS 29.128 [62], clause 5.8):

– the SCEF/IWK-SCEF sends a T6a/T6ai Connection Management Answer to MME as a response to a T6a/T6ai Connection Management Request received with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and Connection-Action AVP set to CONNECTION_ESTABLISHMENT to confirm the establishment of a Non-IP PDN connection.

– in roaming situation SCEF sends a T7 Connection Management Answer to IWK-SCEF as a confirmation to the T7 Connection Management Request received with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Connection-Action AVP set to CONNECTION_ESTABLISHMENT.

Table 7.8.2-1: SCEFPDNConnectionEstablishment record

Field name	Value	M/C/O
iMSI	IMSI associated with the Non-IP PDN Connection of the target UE (e.g. as provided by the MME in the associated Connection Management Request).	C
mSISDN	MSISDN associated with the PDN Connection if available.	C
externalIdentifier	External Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.	C
iMEI	IMEI associated to the device if available.	C
ePSBearerID	Identity of the EPS bearer that MME allocated to the Non-IP PDN connection.	M
sCEFID	SCEF identity handling the EPS Bearer.	M
aPN	Access Point Name used to establish the PDN Connection. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.	M
rDSSupport	True if Reliable Data Service is supported in the PDN Connection,. otherwise False	M
sCSASID	String Identifying the AF the traffic will be delivered to.	M

7.8.2.1.3 PDN connection update

The IRI-POI in the SCEF/IWK-SCEF shall generate an xIRI containing an SCEFPDNConnectionUpdate record when the IRI-POI present in the SCEF/IWK-SCF detects that a Non-IP PDN Connection has been updated for the target UE. The IRI-POI present in the SCEF/IWK-SCEF shall generate the xIRI for the following events:

– SCEF/IWK-SCEF sends a T6a/T6ai Connection Management Answer to confirm the T6a/T6ai Connection Management Request received with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Connection-Action AVP set to CONNECTION_UPDATE as described in TS 29.128 [62] clause 5.7.

– SCEF/IWK-SCEF receives a T6a/T6ai Connection Management Answer from MME which confirms the T6a/T6ai Connection Management Request sent by SCEF/IWK-SCEF with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Connection-Action AVP set to CONNECTION_UPDATE as described in TS 29.128 [62] clause 5.8.

– in roaming situation SCEF sends a T7 Connection Management Answer to IWK-SCEF to confirm the T7 Connection Management Request received with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Connection-Action AVP set to CONNECTION_UPDATE as described in TS 29.128 [62] clause 5.7.

– in roaming situation SCEF receives a T7 Connection Management Answer from IWK-SCEF which confirms the T7 Connection Management Request with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Connection-Action AVP set to CONNECTION_UPDATE as described in TS 29.128 [62] clause 5.8.

– SCEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Reserve port" to confirm the reservation of a combination of source and destination port numbers for use for a traffic to be sent by the UE to a specific application on an SCS/AS (see TS 24.250 [61] clause 5.4.2.6.2).

– SCEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by the SCEF with an "Action" field set to "Reserve port" to confirm the reservation of a combination of source and destination port numbers for use for a traffic to be sent by an SCS/AS to a specific application on the UE (see TS 24.250 [61] clause 5.4.2.6.2).

– SCEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Release port" to confirm the release of a combination of source and destination port numbers for an application on an SCS/AS (see TS 24.250 [61] clause 5.4.2.6.3).

– SCEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Success" in response to a RDS MANAGE PORT command sent by the SCEF with an "Action" field set to "Release port" to confirm the release of a combination of source and destination port numbers for an application on the UE (see TS 24.250 [61] clause 5.4.2.6.3).

Table 7.8.2-2: SCEFPDNConnectionUpdate record

Field name	Value	M/C/O
iMSI	IMSI associated with the Non-IP PDN Connection of the target UE (e.g. as provided by the MME in the associated Connection Management Request).	C
mSISDN	MSISDN associated with the PDN Connection if available.	C
externalIdentifier	External Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.	C
initiator	Initiator of the modification of the PDN Connection, UE, MME or SCEF.	M
rDSSourcePortNumber	RDS source port number.	C
rDSDestinationPortNumber	RDS destination port number.	C
applicationID	Application identifier on the UE or on the SCS/AS if RDS is used.	C
sCSASID	Identifier of the SCS/AS if RDS is used.	C
rDSAction	Action if RDS is used. Possible values: “ReservePort”, “ReleasePort”.	C
serializationFormat	Data format exchanged between UE and SCS/AS if RDS is used.	C

7.8.2.1.4 PDN connection release

The IRI-POI in the SCEF/IWK-SCEF shall generate an xIRI containing an SCEFPDNConnectionRelease record when the IRI-POI present in the SCEF/IWK-SCEF detects that a Non-IP PDN Connection needs to be released for the target UE. The IRI-POI present in the SCEF/IWK-SCEF shall generate the xIRI for the following events:

– SCEF/IWK-SCEF informs MME that the Non-IP PDN Connection for NIDD is no longer valid using T6a Connection Management Request with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and Connection-Action AVP set to CONNECTION_RELEASE. SCEF initiates the release of the Non-IP PDN connection when it is notified by the HSS about the end of NIDD authorization for the target UE (see TS 29.128 [62] clause 5.8).

– SCEF sends a T6a Connection Management Answer to MME to confirm the T6a Connection Management Request received with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Action-Action AVP set to CONNECTION_RELEASE (see TS 29.128 [62] clause 5.7).

– SCEF informs IWK-SCEF that the Non-IP PDN Connection for NIDD is no longer valid using T6a Connection Management Request with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and Connection-Action AVP set to CONNECTION_RELEASE (see TS 29.128 [62] clause 5.8).

– SCEF sends a T7 Connection Management Answer to IWK-SCEF to confirm the T7 Connection Management Request with User-Identifier AVP including the set of identities of the UE, i.e. IMSI/MSISDN/External Identifier matching the target Identifier and with Action AVP set to CONNECTION_RELEASE (see TS 29.128 [62] clause 5.7).

Table 7.8.2-3: SCEFPDNConnectionRelease record

Field name	Value	M/C/O
iMSI	IMSI associated with the Non-IP PDN Connection of the target UE (e.g. as provided by the MME in the associated Connection Management Request).	C
mSISDN	MSISDN associated with the PDN Connection if available.	C
externalIdentifier	External Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.	C
ePSBearerID	Identity of the EPS bearer that MME allocates to the Non-IP PDN Connection.	M
timeOfFirstPacket	Time of first packet for the PDN Connection.	C
timeOfLastPacket	Time of last packet for the PDN Connection.	C
uplinkVolume	Number of uplink octets for the PDN Connection.	C
downlinkVolume	Number of downlink octets for the PDN Connection.	C
releaseCause	Reason for PDN Connection release.	M

7.8.2.1.5 Unsuccessful procedure

The IRI-POI in the SCEF/IWK-SCEF shall generate an xIRI containing an SCEFUnsuccessfulProcedure record when the IRI-POI present in the SCEF/IWK-SCEF detects an unsuccessful procedure or error condition for a target UE matching one of the target identifiers provided via LI_X1.

Accordingly, the IRI-POI in the SCEF/IWK-SCEF generates the xIRI when any of the following events is detected (see TS 29.128 [62] clause 6.3.3 and TS 24.250 [61] clause 5.4.2.6):

– SCEF sends a T6a Connection Management Answer with Experimental-Result AVP set to DIAMETER_ERROR_USER_UNKNOWN.

– SCEF sends a T6a Connection Management Answer with Experimental-Result AVP set to DIAMETER_ERROR_OPERATION_NOT_ALLOWED when Action AVP of the T6a Connection Management Request received by the SCEF is not set to CONNECTION_ESTABLISHMENT, CONNECTION_UPDATE or CONNECTION_ RELEASE.

– SCEF sends a T6a Connection Management Answer with Experimental-Result AVP set to DIAMETER_ERROR_NIDD_CONFIGURATION_NOT_AVAILABLE when Action AVP of the T6a Connection Management Request received by the SCEF is set to CONNECTION_ESTABLISHMENT and the NIDD configuration for the target UE does not exist or fails at SCEF.

– SCEF sends a T6a Connection Management Answer with Experimental-Result AVP set to DIAMETER_ERROR_INVALID_EPS_BEARER when Action AVP of the T6a Connection Management Request received by the SCEF is set to CONNECTION_UPDATE or CONNECTION_RELEASE and the EPS Bearer Identity does not exist.

– SCEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Port not free" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Reserve port".

– SCEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Port not free" in response to a RDS MANAGE PORT command sent by SCEF with an "Action" field set to "Reserve port".

– SCEF returns a RDS MANAGE PORT Response to a UE with a "Status" field set to "Port not associated with specified application" in response to a RDS MANAGE PORT command sent by UE with an "Action" field set to "Release port".

– SCEF receives a RDS MANAGE PORT Response from a UE with a "Status" field set to "Port not associated with specified application" in response to a RDS MANAGE PORT command sent by SCEF with an "Action" field set to "Release port".

Table 7.8.2-4: SCEFUnsuccessfulProcedure record

Field name	Value	M/C/O
failureCause	Cause of unsuccessful procedure.	M
iMSI	IMSI associated with the Non-IP PDN Connection of the target UE (e.g. as provided by the MME in the associated Connection Management Request).	C
mSISDN	MSISDN associated with the PDN Connection if available.	C
iMEI	IMEI associated to the device if available.	C
externalIdentifier	External Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.	C
ePSBearerID	Identity of the EPS bearer that MME allocated to the Non-IP PDN connection.	M
aPN	Access Point Name associated with the target traffic. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.	M
rDSDestionationPortNumber	RDS destination port number.	C
applicationID	Application identifier associated with the RDS port number.	C
sCSASID	SCS/AS Identifier.	C

7.8.2.1.6 Start of interception with established PDN connection

The IRI-POI in the SCEF/IWK-SCEF shall generate an xIRI containing an SCEFStartOfInterceptionWithEstablishedPDNConnection record when the IRI-POI present in the SCEF detects that a Non-IP PDN Connection using SCEF has already been established for the target UE when interception starts.

In a non-roaming scenario, the IRI-POI in the SCEF (or in a roaming scenario, the IRI-POI in the IWK-SCEF in the VPLMN) shall generate the xIRI containing the SCEFStartOfInterceptionWithEstablishedPDNConnection record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case:

– A PDN connection to the SCEF for the target UE exists, uniquely identified by an EPS Bearer Identity, APN, and UE Identity.

The IRI-POI in the SCEF/IWK-SCEF shall generate the xIRI containing the SCEFStartOfInterceptionWithEstablishedPDNConnection record for each of the PDN Connections for NIDD using SCEF associated with the target UE.

Table 7.8.2-5: SCEFStartOfInterceptionWithEstablishedPDNConnection record

Field name	Value	M/C/O
iMSI	IMSI associated with the Non-IP PDN Connection of the target UE (e.g. as provided by the MME in the associated Connection Management Request).	C
mSISDN	MSISDN associated with the PDN Connection if available.	C
externalIdentifier	External Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.	C
iMEI	IMEI associated to the device if available.	C
ePSBearerID	Identity of the EPS bearer that MME allocated to the Non-IP PDN connection.	M
sCEFID	SCEF identity handling the EPS Bearer.	M
aPN	Access Point Name associated with the target traffic. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.	M
rDSSupport	True if Reliable Data Service is supported in the PDN Connection, otherwise False.	M
sCSASID	String Identifying the SCS/AS the traffic will be delivered to.	M

The IRI-POI present in the SMF generating an xIRI containing a SCEFStartOfInterceptionWithEstablishedPDUSession record shall set the Payload Direction field in the PDU header to not applicable (see ETSI TS 103 221-2 [8] clause 5.2.6).

7.8.2.2 Generation of xCC at CC-POI in SCEF over LI_X3

The CC-POI present in the SCEF shall send xCC over LI_X3 for each NIDD packet.

Each X3 PDU shall contain the contents of the user plane packet (i.e. NIDD) using an unstructured payload.

The CC-POI present in the SCEF shall set the payload format to indicate the appropriate payload type (i.e. unstructured payload) as described in ETSI TS 103 221-2 [8] clause 5.4.

7.8.2.3 Generation of IRI over LI_HI2

When an xIRI is received over LI_X2 from the IRI-POI in the SCEF/IWK-SCEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).

The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).

The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to table 7.8.2-6.

Table 7.8.2-6: IRI type for IRI messages

Record type	IRI Type
SCEFPDNConnectionEstablishment	BEGIN
SCEFPDNConnectionRelease	END
SCEFPDNConnectionUpdate	CONTINUE
SCEFStartOfInterceptionWithEstablishedPDNConnection	BEGIN
SCEFUnsuccessfulProcedure	REPORT

IRI messages associated with the same PDU Session shall be assigned the same CIN (see ETSI TS 102 232-1 [9] clause 5.2.4).

The threeGPP33128DefinedIRI field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.

7.8.2.4 Generation of CC over LI_HI3

When xCC is received over LI_X3 from the CC-POI in the SCEF, the MDF3 shall populate the threeGPP33128DefinedCC field with a CCPayload structure containing NIDDCCPDU and send it over LI_HI3 interface to LEMF without undue delay.

The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time that the SCEF observed the data (i.e. the timestamp field of the xCC). The LIID and CID fields shall correctly reflect the target identity and communication session to which the CC belongs.

7.8.3 LI for device triggering

7.8.3.1 Generation of xIRI LI_X2 at IRI-POI in SCEF over LI_X2

7.8.3.1.1 General

The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in TS 33.127 [5] clause 7.11.3.4, the details of which are described in the following clauses.

7.8.3.1.2 Device trigger

The IRI-POI in the SCEF shall generate an xIRI containing a SCEFDeviceTrigger record when the IRI-POI present in the SCEF detects that an SCS/AS has sent a Device triggering request to a target UE matching one of the target identifiers.

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:

– SCEF sends a Device triggering response to the SCS/AS to acknowledge the reception of a Device triggering request with MSISDN or External Identifier matching the target identifier (See TS 29.122 [63] clause 5.7).

– SCEF sends a T4 Device-Trigger-Request (DTR) to SMS-SC with Trigger-Action AVP set to TRIGGER and User-Identifier AVP matching the IMSI of the target UE as specified in TS 29.337 [60] clause 5.2.1.

Table 7.8.3-1: SCEFDeviceTrigger record

Field name	Value	M/C/O
iMSI	IMSI associated with the UE	C
mSISDN	MSISDN used with the UE	C
externalIdentifier	External Identifier used with the UE	C
triggerId	Identity of the Device trigger that should be provided in the deviceTriggeringDeliveryReportNotification IRI, Device trigger replacement IRI and Device trigger cancellation IRI	M
sCSASID	The SCS/AS sending the Device trigger	M
triggerPayload	The Device triggering payload	C
validityPeriod	The validity time in seconds for the specific action requested	C
priorityDT	The priority of the Device trigger	C
sourcePortId	Application identity on the SCS/AS which delivers the Device trigger	C
destinationPortId	Used to uniquely identify the triggering application addressed in the device	C

7.8.3.1.3 Device trigger replacement

The IRI-POI in the SCEF shall generate an xIRI containing a SCEFDeviceTriggerReplace record when the IRI-POI present in the SCEF detects that an SCS/AS has sent a Device triggering replacement for a previously sent Device triggering request to a UE matching one of the target identifiers provided via LI_X1 to the IRI POI in the SCEF. It replaces a previously submitted Device triggering request which has not yet been delivered to the UE.

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:

– SCEF receives a Device triggering request (for a Device trigger replacement) from an SCS/AS with MSISDN or External Identifier matching the target identifier (See TS 29.122 [63] clause 5.7).

– SCEF sends a T4 Device-Trigger-Request (DTR) to SMS-SC with Trigger-Action AVP set to REPLACE and User-Identifier AVP matching the IMSI of the target UE as specified in TS 29.337 [60] clause 5.2.1.

Table7.8.3-2: SCEFDeviceTriggerReplace record

Field name	Value	M/C/O
iMSI	IMSI associated with the target UE	C
mSISDN	MSISDN used with the taget UE	C
externalIdentifier	External Identifier used with the taget UE	C
triggerId	Identity of the corresponding Device trigger to be replaced	M
sCSASID	Identity of the SCS/AS replacing an existing Device trigger which has not been delivered yet to the device (e.g. because the device is unreachable) by a new Device trigger	M
triggerPayload	The device triggering payload	C
validityPeriod	The validity time in seconds for the specific action requested	C
priorityDT	The priority of the device trigger	C
sourcePortId	Port on the SCSAS which delivers the device trigger	C
destinationPortId	Port on the device which is the recipient of the device trigger	C

7.8.3.1.4 Device trigger cancellation

The IRI-POI in the SCEF shall generate an xIRI containing a SCEFDeviceTriggerCancellation record when the IRI-POI present in the SCEF detects that an SCS/AS has sent a Device triggering cancellation for a previously sent Device triggering request to a UE matching one of the target identifiers provided via LI_X1 to the IRI-POI in the SCEF. It cancels previously submitted Device triggering request which has not yet been delivered to the target UE.

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:

– SCEF receives a Device triggering request (for a device trigger cancellation) from SCS/AS related to a previously received Device triggering request with MSISDN or External Identifier matching the target identifier (See TS 29.122 [63] clause 5.7).

– SCEF sends a T4 Device-Trigger-Request (DTR) to SMS-SC with Trigger-Action AVP set to RECALL and User-Identifier AVP matching the IMSI of the target UE as specified in TS 29.337 [60] clause 5.2.1.

Table 7.8.3-3: SCEFDeviceTriggerCancellation record

Field name	Value	M/C/O
iMSI	IMSI associated with the target UE	C
mSISDN	MSISDN used with the taget UE	C
externalIdentifier	External Identifier used with the target UE	C
triggerId	Identity of the corresponding device trigger to be cancelled	M

7.8.3.1.5 Device trigger report notification

The IRI-POI in the SCEF shall generate an xIRI containing a SCEFDeviceTriggerReportNotify record when the IRI-POI present in the SCEF detects that the SCEF has returned a Device triggering delivery report notification to the SCS/AS with a cause value indicating the trigger delivery outcome (e.g. succeeded, unknown or failed).

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:

– SCEF sends a Device triggering delivery report notification to inform the SCS/AS on the delivery outcome of the device trigger (see TS 29.122 [63] clause 5.7).

– SMS-SC sends a T4 Delivery-Report-Request (DRR) to the SCEF with User-Identifier matching the IMSI of the target UE as specified in TS 29.337 [60] clause 5.2.2.

Table 7.8.3-4: SCEFDeviceTriggerReportNotify record

Field name	Value	M/C/O
iMSI	IMSI associated with the target UE	M
mSISDN	MSISDN used with the target UE	C
externalIdentifier	External Identifier used with the target UE	C
triggerId	Identity of the corresponding Device trigger	M
deviceTriggerDeliveryResult	Delivery result represents the result of the delivery of a device triggering request: – SUCCESS: The value indicates that the device action request was successfully completed. – UNKNOWN: The value indicates any unspecified errors. – FAILURE: The value indicates that this trigger encountered a delivery error and is deemed permanently undeliverable. – TRIGGERED: The value indicates that Device triggering request is accepted by the SCEF. – EXPIRED: The value indicates that the validity period expired before the trigger could be delivered. – UNCONFIRMED: The value indicates that the delivery of the device action request is not confirmed. – REPLACED: The value indicates that the device triggering replacement request is accepted by the SCEF. – TERMINATE: The SCEF includes this value in the response for a successful device triggering cancellation request. The value indicates that the delivery of the device action request is terminated by the SCS/AS.	M

7.8.3.2 Generation of IRI over LI_HI2

When an xIRI is received over LI_X2 from the IRI-POI in the SCEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).

The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).

Table 7.8.3-5 shows the IRI type (see ETSI TS 102 232-1 [9] clause 5.2.10) to be used for each record type.

Table 7.8.3-5: IRI type for messages

Record type	IRI Type
SCEFDeviceTrigger	REPORT
SCEFDeviceTriggerReplace	REPORT
SCEFDeviceTriggerCancellation	REPORT
SCEFDeviceTriggerReportNotify	REPORT

7.8.4 LI for MSISDN-less MO SMS

7.8.4.1 Generation of xIRI LI_X2 at IRI-POI in SCEF over LI_X2

7.8.4.1.1 General

The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in TS 33.127 [5] clause 7.11.4.4, the details of which are described in the following clauses.

7.8.4.1.2 MSISDN-less MO SMS

The IRI-POI in the SCEF shall generate an xIRI containing a SCEFMSISDNLessMOSMS record when the IRI-POI present in the SCEF detects that a target UE has sent a MSISDN-less MO SMS to an SCS/AS.

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:

– SCEF receives a SGd MO-Forward-Short-Message-Request (OFR) from an SMS-SC with IMSI matching the target identifier (see TS 29.338 [59] clause 6.2.1).

– SCEF sends a MsisdnLessMoSmsNotification to the SCS/AS with the External Identifier of the UE sending the MSISDN-less SMS (see TS 29.122 [63] clause 5.15).

Table 7.8.4-1: SCEFMSISDNLessMOSMS record

Field name	Value	M/C/O
iMSI	IMSI associated with the target UE	C
externalIdentifier	External Identifier in the form of username@realm and corresponding to the identity of the originating SMS party	C
terminatingSMSParty	Identity of the SCS/AS receiving the SMS	M
sMS	SMS TPDU	C
sourcePort	port identifying the application of the target UE sending the MSISN-less MO SMS	C
destinationPort	port identifying the application of the SCS/AS which is the recipient of the MSISN-less MO SMS	C

7.8.4.2 Generation of IRI over LI_HI2

The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).

The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to table 7.8.4-2.

Table 7.8.4-2: IRI type for IRI messages

Record type	IRI Type
SCEFMSISDNLessMOSMS	REPORT

7.8.5 LI for parameter provisioning

7.8.5.1 Generation of xIRI LI_X2 at IRI-POI in SCEF over LI_X2

7.8.5.1.1 General

The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in corresponding in TS 33.127 [5] clause 7.11.5.4, the details of which are described in the following clauses.

7.8.5.1.2 Communication pattern update

The IRI-POI in the SCEF shall generate an xIRI containing an SCEFCommunicationPatternUpdate record when the IRI-POI present in the SCEF detects that an SCS/AS has updated the Communication pattern data.

Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected (See TS 29.122 [63] clause 5.10):

– SCEF receives a request to provision the communication pattern parameters from an SCS/AS related to the target UE (PUT).

– SCEF receives a request to delete the existing communication patterns parameters from an SCS/AS related to the target UE (DELETE).

– SCEF returns a response (200 OK) containing the communication pattern parameters of the target UE to the querying SCS/AS (GET).

Table 7.8.5-1: SCEFCommunicationPatternUpdate record

Field name	Value	M/C/O
mSISDN	MSISDN of the target UE the communication pattern applies to	C
externalIdentifier	External Identifier of the target UE the communication pattern applies to	C
periodicCommunicationIndicator	Identifies whether UE communicates periodically or on demand	O
communicationDurationTime	Indicates for how long the UE will normally stay in CM-Connected for data transmission expressed in seconds	O
periodicTime	Interval Time of periodic communication in seconds	O
scheduledCommunication Time	Time and day of the week when the UE is available for communication, as defined in TS 29.571	O
scheduledCommunicationType	Indicates that the Scheduled Communication Type is Downlink only or Uplink only or Bi-directional	O
stationaryIndication	Identifies whether the UE is stationary or mobile	O
batteryIndication	Identifies power consumption criticality for the UE: if the UE is battery powered but the battery is not rechargeable/not replaceable, battery powered with rechargeable/replaceable battery, or not battery powered.	O
trafficProfile	Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission	O
expectedUEMovingTrajectory	Identifies the UE’s expected geographical movement	O
expectedTimeAndDayOfWeekInTrajectory	Identifies the time and day of week when the UE is expected to be at each location included in the Expected UE Moving Trajectory	O
sCSASID	SCS/AS identity requesting communication pattern update	M
validityTime	Identifies when the expected UE behavior parameter set expires and shall be deleted. If absent, it indicates that there is no expiration time for this parameter set	O

7.8.5.2 Generation of IRI over LI_HI2

The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).

The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to table 7.8.5-2.

Table 7.8.5-2: IRI type for IRI messages

Record type	IRI Type
SCEFCommunicationPatternUpdate	REPORT