Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 33.128  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M… 
7.8 LI at SCEF  7.8.1 Provisioning over LI_X1  7.8.1.1 General  7.8.1.2 Provisioning of the IRI-POI and CC-POI in SCEF  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  7.8.2.1.2 SCEF PDN connection establishment  7.8.2.1.3 PDN connection update  7.8.2.1.4 PDN connection release  7.8.2.1.5 Unsuccessful procedure  7.8.2.1.6 Start of interception with established PDN connection  7.8.2.2 Generation of xCC at CC-POI in SCEF over LI_X3  7.8.2.3 Generation of IRI over LI_HI2  7.8.2.4 Generation of CC over LI_HI3  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  7.8.3.1.2 Device trigger  7.8.3.1.3 Device trigger replacement  7.8.3.1.4 Device trigger cancellation  7.8.3.1.5 Device trigger report notification  7.8.3.2 Generation of IRI over LI_HI2 
...

 

7.8  LI at SCEF  p. 260

7.8.1  Provisioning over LI_X1  p. 260

7.8.1.1  General  p. 260

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.
Up

7.8.1.2  Provisioning of the IRI-POI and CC-POI in SCEF  p. 261

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.
Up

7.8.2  LI for NIDD using SCEF  p. 261

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

7.8.2.1.1  General  p. 261
The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.8.2.3 of TS 33.127, 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  p. 261
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 clause 5.8 of TS 29.128):
  • 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.
Field name Value M/C/O
iMSIIMSI 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
mSISDNMSISDN associated with the PDN Connection if available.C
externalIdentifierExternal Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.C
iMEIIMEI associated to the device if available.C
ePSBearerIDIdentity of the EPS bearer that MME allocated to the Non-IP PDN connection.M
sCEFIDSCEF identity handling the EPS Bearer.M
aPNAccess Point Name used to establish the PDN Connection. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
rDSSupportTrue if Reliable Data Service is supported in the PDN Connection,. otherwise FalseM
sCSASIDString Identifying the SCS/AS the traffic will be delivered to.M
Up
7.8.2.1.3  PDN connection update  p. 262
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 clause 5.7 of TS 29.128.
  • 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 clause 5.8 of TS 29.128.
  • 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 clause 5.7 of TS 29.128.
  • 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 clause 5.8 of TS 29.128.
  • 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 clause 5.4.2.6.2 of TS 24.250).
  • 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 clause 5.4.2.6.2 of TS 24.250).
  • 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 clause 5.4.2.6.3 of TS 24.250).
  • 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 clause 5.4.2.6.3 of TS 24.250).
Field name Value M/C/O
iMSIIMSI 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
mSISDNMSISDN associated with the PDN Connection if available.C
externalIdentifierExternal Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.C
initiatorInitiator of the modification of the PDN Connection, UE, MME or SCEF.M
rDSSourcePortNumberRDS source port number.C
rDSDestinationPortNumberRDS destination port number.C
applicationIDApplication identifier on the UE or on the SCS/AS if RDS is used.C
sCSASIDIdentifier of the SCS/AS if RDS is used.C
rDSAction Action if RDS is used. Possible values: "ReservePort", "ReleasePort". C
serializationFormatData format exchanged between UE and SCS/AS if RDS is used.C
ePSBearerIDIdentity of the EPS bearer that MME allocated to the Non-IP PDN connection (see NOTE below).M
NOTE:
For the backward compatibility purposes the parameter is coded as OPTIONAL in the ASN.1 schema (Annex A).
Up
7.8.2.1.4  PDN connection release  p. 263
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 clause 5.8 of TS 29.128).
  • 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 clause 5.7 of TS 29.128).
  • 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 clause 5.8 of TS 29.128).
  • 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 clause 5.7 of TS 29.128).
Field name Value M/C/O
iMSIIMSI 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
mSISDNMSISDN associated with the PDN Connection if available.C
externalIdentifierExternal Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.C
ePSBearerIDIdentity of the EPS bearer that MME allocates to the Non-IP PDN Connection.M
timeOfFirstPacketTime of first packet for the PDN Connection.C
timeOfLastPacketTime of last packet for the PDN Connection.C
uplinkVolumeNumber of uplink octets for the PDN Connection.C
downlinkVolumeNumber of downlink octets for the PDN Connection.C
releaseCauseReason for PDN Connection release.M
Up
7.8.2.1.5  Unsuccessful procedure  p. 264
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 clause 6.3.3 of TS 29.128 and clause 5.4.2.6 of TS 24.250):
  • 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".
Field name Value M/C/O
failureCauseCause of unsuccessful procedure.M
iMSIIMSI 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
mSISDNMSISDN associated with the PDN Connection if available.C
iMEIIMEI associated to the device if available.C
externalIdentifierExternal Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.C
ePSBearerIDIdentity of the EPS bearer that MME allocated to the Non-IP PDN connection.M
aPNAccess Point Name associated with the target traffic. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003. (see NOTE)M
rDSDestionationPortNumberRDS destination port number.C
applicationIDApplication identifier associated with the RDS port number.C
sCSASID SCS/AS Identifier. If the SCS/AS Idenitifer is not available, the placeholder value "Unknown" shall be used. C
NOTE:
If the APN is not available, the placeholder value ".unknown." shall be used.
Up
7.8.2.1.6  Start of interception with established PDN connection  p. 265
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.
Field name Value M/C/O
iMSIIMSI 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
mSISDNMSISDN associated with the PDN Connection if available.C
externalIdentifierExternal Identifier associated with the PDN Connection if available, defined as NAI in ASN.1.C
iMEIIMEI associated to the device if available.C
ePSBearerIDIdentity of the EPS bearer that MME allocated to the Non-IP PDN connection.M
sCEFIDSCEF identity handling the EPS Bearer.M
aPNAccess Point Name associated with the target traffic. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
rDSSupportTrue if Reliable Data Service is supported in the PDN Connection, otherwise False.M
sCSASIDString 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).
Up

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

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  p. 265

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.
IRI message Record type
SCEFPDNConnectionEstablishmentBEGIN
SCEFPDNConnectionReleaseEND
SCEFPDNConnectionUpdateCONTINUE
SCEFStartOfInterceptionWithEstablishedPDNConnectionBEGIN
SCEFUnsuccessfulProcedureREPORT
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.
Up

7.8.2.4  Generation of CC over LI_HI3  p. 266

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.
Up

7.8.3  LI for device triggering  p. 266

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

7.8.3.1.1  General  p. 266
The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.11.3.4 of TS 33.127, the details of which are described in the following clauses.
7.8.3.1.2  Device trigger  p. 266
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 clause 5.7 of TS 29.122).
  • SCEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to TRIGGER and User-Identifier AVP matching the IMSI of the target UE as specified in clause 5.2.1 of TS 29.337.
Field name Value M/C/O
iMSIIMSI associated with the UEC
mSISDNMSISDN used with the UEC
externalIdentifierExternal Identifier used with the UEC
triggerIdIdentity of the Device trigger that should be provided in the deviceTriggeringDeliveryReportNotification IRI, Device trigger replacement IRI and Device trigger cancellation IRIM
sCSASIDThe SCS/AS sending the Device triggerM
triggerPayloadThe Device triggering payloadC
validityPeriodThe validity time in seconds for the specific action requestedC
priorityDTThe priority of the Device triggerC
sourcePortIdApplication identity on the SCS/AS which delivers the Device triggerC
destinationPortIdUsed to uniquely identify the triggering application addressed in the deviceC
Up
7.8.3.1.3  Device trigger replacement  p. 267
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 clause 5.7 of TS 29.122).
  • SCEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to REPLACE and User-Identifier AVP matching the IMSI of the target UE as specified in clause 5.2.1 of TS 29.337.
Field name Value M/C/O
iMSIIMSI associated with the target UEC
mSISDNMSISDN used with the taget UEC
externalIdentifierExternal Identifier used with the taget UEC
triggerIdIdentity of the corresponding Device trigger to be replacedM
sCSASIDIdentity 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 triggerM
triggerPayloadThe device triggering payloadC
validityPeriodThe validity time in seconds for the specific action requestedC
priorityDTThe priority of the device triggerC
sourcePortIdPort on the SCSAS which delivers the device triggerC
destinationPortIdPort on the device which is the recipient of the device triggerC
Up
7.8.3.1.4  Device trigger cancellation  p. 267
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 clause 5.7 of TS 29.122).
  • SCEF sends a T4 Device-Trigger-Request (DTR) to SM-SC with Trigger-Action AVP set to RECALL and User-Identifier AVP matching the IMSI of the target UE as specified in clause 5.2.1 of TS 29.337.
Field name Value M/C/O
iMSIIMSI associated with the target UEC
mSISDNMSISDN used with the taget UEC
externalIdentifierExternal Identifier used with the target UEC
triggerIdIdentity of the corresponding device trigger to be cancelledM
Up
7.8.3.1.5  Device trigger report notification  p. 268
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 clause 5.7 of TS 29.122).
  • SM-SC sends a T4 Delivery-Report-Request (DRR) to the SCEF with User-Identifier matching the IMSI of the target UE as specified in clause 5.2.2 of TS 29.337.
Field name Value M/C/O
iMSIIMSI associated with the target UEM
mSISDNMSISDN used with the target UEC
externalIdentifierExternal Identifier used with the target UEC
triggerIdIdentity of the corresponding Device triggerM
deviceTriggerDeliveryResultDelivery 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
Up

7.8.3.2  Generation of IRI over LI_HI2  p. 268

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.
IRI message Record type
SCEFDeviceTriggerREPORT
SCEFDeviceTriggerReplaceREPORT
SCEFDeviceTriggerCancellationREPORT
SCEFDeviceTriggerReportNotifyREPORT
Up

Up   Top   ToC