Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

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

 

23  Lawful Interception for Non-IP Data Delivery (NIDD) using SCEF |R15|Word‑p. 262

23.1  Overview

This clause describes the LI functions for Non-IP Data Delivery using SCEF between the IoT UE and the SCS/AS. The IoT UE accesses the 3GPP network via E-UTRAN or GPRS access and the delivery of Non-IP Data to the SCS/AS is done using the SCEF.
The present document does not support the interception of Non-IP Data Delivery using a Point-to-Point (PtP) SGi tunnel and the interception of monitoring events requested using SCEF.
For NIDD using SCEF, the following NFs in the CSP network shall support the interception capabilities:
  • MME (when the access is E-UTRAN);
  • SGSN (when the access is GPRS);
  • HSS (for non-communication related events);
  • HLR (for non-communication related events);
  • SCEF (NIDD related events in non-roaming case, or in HPLMN);
  • IWK-SCEF (NIDD related events in VPLMN).
The intercept configuration for MME is shown in Figure 12.1.1 (clause 12.1). The intercept configuration for SGSN is shown in Figure 1b (clause 4). The intercept configuration for HSS is shown in Figure 12.1.2 (clause 12.1). The intercept configuration for HLR is shown in Figure 1c (clause 4). The intercept configuration for SCEF and IWK-SCF is shown in Figure 23.1.1 below.
[not reproduced yet]
Figure 23.1.1: Intercept Configuration for SCEF and IWK-SCEF for NIDD Delivery using SCEF
Up
The definition of the LI functional entities (ADMF, DF, MF, LEMF) and interfaces (X, HI) is the same as for 3G as given in clause 4.
If roaming interception is allowed, SCEF in the HPLMN shall report IRI and CC while the target is in the VPLMN. For warrants served in the VPLMN, the IWK-SCEF in the VPLMN shall report the IRI and CC.
The target identities for interception at the HSS, SCEF and IWK-SCEF are IMSI, MSISDN, External Identifier and ME (Mobile Equipment) Identity.
The target identities for interception at the MME and SGSN are IMSI, MSISDN, External Identifier.
For the delivery of the CC and IRI when performing non-IP data delivery using SCEF, the SCEF and IWK-SCEF provide correlation number and target identity to the DF2 and DF3. The correlation number shall be generated by using existing parameters related to the EPS bearer or NSAPI.
Up

23.2  Provision of Content of CommunicationsWord‑p. 263

23.2.1  X3-interface

The access method for the delivering of CC related to the NIDD using SCEF is based on duplication of packets without modification of the packets at the SCEF and/or IWK-SCEF. The duplicated packets with additional information in a header are sent to DF3 for further delivery to the LEA.
[not reproduced yet]
Figure 23.2.1: Configuration for CC interception of NIDD using SCEF
Up
In addition to the intercepted content of communication, the following information needs to be transferred from the SCEF and/or IWK-SCEF to the DF3:
  • target identity;
  • correlation number;
  • time stamp (optional);
  • direction (indicates whether T-PDU is MO or MT) - optional;
  • the target location (if available) or the IAs in case of location dependent interception.

23.3  Provision of Intercept Related Information

23.3.1  General

IRI events applicable for Lawful Interception of NIDD using SCEF include the events reported by MME, SGSN, HSS, SCEF and IWK-SCEF as described in the following clauses.

23.3.2  X2-interfaceWord‑p. 264
The following information needs to be transferred from the MME, SGSN, SCEF, IWK-SCEF or the HSS to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI, MSISDN, External Identifier, ME identity);
  • events and associated parameters as defined in clauses 12.A.3.3 and 12.A.3.4 may be provided;
  • the target location (if available) or the IAs in case of location dependent interception;
  • correlation number (only for SCEF and IWK-SCEF);
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

23.3.3  Structure of the events

There are several different events in which the information is sent to the DF2 if this is required. Details are described in the following clause. The events for interception are configurable (if they are sent to DF2) in the MME, SGSN, SCEF or the HSS and can be suppressed in the DF2. The network procedures for which the events are generated are defined in TS 23.060 and TS 23.401.
The following events are applicable to the MME:
  • IoT UE Attach for NIDD using SCEF;
  • IoT UE Detach for NIDD for using SCEF;
  • IoT UE Tracking Area Update for NIDD using SCEF;
  • IoT UE requested non-IP PDN connectivity;
  • IoT UE Requested non-IP PDN disconnection;
  • SCEF requested non-IP PDN disconnection
  • Start of interception with attached IoT UE with active non-IP PDN connection.
The following events are applicable to the SGSN:
  • IoT UE Attach for NIDD using SCEF;
  • IoT UE Detach for NIDD using SCEF;
  • IoT UE Routing Area Update for NIDD using SCEF;
  • IoT UE requested non-IP PDP context activation;
  • IoT UE Requested non-IP PDP context disconnection;
  • SCEF requested non-IP PDP context disconnection;
  • Start of interception with PDP context active.
The following events are applicable to the SCEF:
  • MME originated connection request;
  • MME/SGSN originated connection update;
  • SCEF originated connection update;
  • MME/SGSN originated disconnection request;
  • SCEF originated disconnection request;
  • Start of interception with connected UE;
  • Non-IP Packet Data Header Information.
The following events are applicable to the IWK-SCEF:
  • MME/SGSN originated connection request;
  • MME/SGSN originated connection update;
  • SCEF originated connection update;
  • MME/SGSN originated disconnection request;
  • SCEF originated disconnection request;
  • Start of interception with connected UE.
The following events are applicable to the HSS:
  • Serving Evolved Packet System for IoT UE;
  • HSS subscriber record change for IoT UE;
  • Cancel location for IoT UE.
The following events are applicable to the HLR:
  • Serving System for IoT UE;
  • Subscriber record change for IoT UE;
  • Cancel location for IoT UE.
A set of elements as shown below can be associated with the events. The events trigger the transmission of the information from the nodes to DF2. Available IEs from this set of elements as shown below can be extended in the nodes, if this is necessary as a national option. DF2 can extend available information if this is necessary as a national option.
Element
Comment

Observed MSISDN
MSISDN of the target.
Observed External Identifier
External Identifier of the target.
Observed IMSI
IMSI of the target.
Observed ME Id
ME Id of the target; when it coincides with the IMEI, it shall be checked for each activation over the radio interface.
Event type
Indicates which type of event is delivered: IoT UE Attach for NIDD using SCEF, IoT UE Detach for NIDD using SCEF, IoT UE Tracking Area Update for NIDD using SCEF, IoT UE Routing Area Update for NIDD using SCEF, IoT UE requested non-IP PDN connectivity, IoT UE Requested non-IP PDN disconnection, SCEF Requested non-IP PDN disconnection, IoT UE requested non-IP PDP Context activation, IoT UE Requested non-IP PDP Context disconnection, SCEF Requested non-IP PDP Context disconnection, Start of interception with attached IoE UE with non-IP PDN connection, Start of interception with non-IP PDP context active, MME/SGSN Originated Connection Request, MME/SGSN Originated Connection Update, SCEF Originated Connection Update, MME/SGSN Originated Disconnection Request, SCEF Originated Disconnection Request, Start of interception with Connected UE, Serving Evolved Packet System for IoT UE, Non-IP Packet Data Header Information, HSS subscriber record change for IoT UE, Cancel location for IoT UE, Serving System for IoT UE, Subscriber record change for IoT UE.
Event date
Date of the event generation in the ICE.
Event time
Time of the event generation in the ICE. Timestamp shall be generated relative to ICE internal clock.
Change Type
This indicates what has been changed (MSISDN, External Identifier or IMSI) in the Subscriber Change Record
Protocol Configuration Options
Are used to transfer parameters between the UE and the SCEF.
Attach type
Indicates the type of attach.
Location Information
Location Information is the Tracking Area Identity (TAI), TA List assigned to the UE, E-CGI and/or routing area identity. In case of Tracking Area Update or Routing Area Update event, the last visited TAI or RAI of the UE may be applicable. Country and network IDs can be considered as location information, by some national regulations.
APN
When provided by the MME, the parameter carries the Access Point Name provided by the UE. When provided by the S-GW/PDN-GW, it is the Access Point Name used for the connection.
SCEF-ID
When provided by the MME, the parameter identifies the SCEF to which the UE has connected.
RAT type
The Radio Access Type
Procedure Transaction Identifier
Identifies a set of messages belonging to the same procedure; the parameter is dynamically allocated by the UE.
Bearer identity
A bearer identity uniquely identifies the T6a or T6b Connection. The Bearer Identity is allocated by the MME/SGSN.
Initiator
The initiator of the procedure, either the network or the UE.
Switch off indicator
Indicates whether a detach procedure is due to a switch off situation or not.
Detach type
Parameter sent by the network to the UE to indicate the type of detach.
Serving MME/SGSN address
The address of the serving MME/SGSN.
Old Location Information
Location Information of the subscriber before Tracking Area Update or Routing Area Update.
Correlation Number
The correlation number is used to correlate CC and IRI.
Network Element Identifier
Unique identifier for the ICE reporting the event.
Logical Function Information
Used to distinguish between multiple logical functions operating in a single physical network element.
Failed attach reason
Reason for failed attach of the target.
IAs
The observed Interception Areas.
Request type
Indicates the type of request in an UE requested PDN connectivity, i.e. initial request or handover.
ULI Timestamp
Indicates the time when the User Location Information was acquired.
The parameter is specified in TS 29.274.
NSAPI
Network layer Service Access Point Identifier
The NSAPI information element contains an NSAPI identifying a PDP Context in a mobility management context specified by the Tunnel Endpoint Identifier Control Plane.
SCS/AS Identifier
Identity of the Service Capability Server/Application Server.
Reliable Data Service Source Port Number
Source Port Number for a Non-IP Data Packet using the Reliable Data Service
Reliable Data Service Destination Port Number
Destination Port Number for a Non-IP Data Packet using the Reliable Data Service
Packet Size
The size of the packet.

Up

23.3.4  NIDD using SCEF related eventsWord‑p. 267

23.3.4.1  MME related events

23.3.4.1.1  IoT UE Attach for NIDD using SCEF
When an attach activation is generated from the IoT UE this event is generated by the MME. This event is equivalent to the EPS Attach event defined in clause 12.2.3.1. The following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
Failed attach reason
IAs (if applicable)
APN
Protocol Configuration Options
Attach type
EPS Bearer identity

Up
23.3.4.1.2  IoT UE Detach for NIDD using SCEFWord‑p. 268
When the IoT UE detaches from the EPS, this event is generated. This event is equivalent to the EPS Detach event defined in clause 12.2.3.2. The following elements are delivered to the DF2 if available
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
Detach initiator
Switch off indicator
Detach type

Up
23.3.4.1.3  IoT UE Tracking Area Update for NIDD using SCEF
For each TA/EPS Location Update an update-event with the elements about the new location is generated. The event shall be sent in case of Tracking Area Update and UE triggered Control Plane Service Request, as specified in TS 23.401. In case of change of MME, the new MME shall send the event, and the old MME may optionally send the event as well. This event is equivalent to the EPS Tracking Area Update event defined in clause 12.2.3.7. The following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information (only for the new MME)
Old Location Information (only for the old MME)
IAs (if applicable)
Failure reason

Up
23.3.4.1.4  IoT UE requested PDN connectivity
When a PDN connectivity is requested from the IoT UE (TS 23.401), a UE requested PDN connectivity event is generated by the MME. This event is equivalent to the UE Requested PDN Connectivity event defined in clause 12.2.3.9. The following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
APN
SCEF-ID
Request type
PDN type
Failed reason
IAs (if applicable)
Protocol Configuration Options
EPS bearer identity

Up
23.3.4.1.5  IoT UE requested PDN disconnectionWord‑p. 269
When a PDN disconnection is requested from the UE to request for disconnection from the PDN (TS 23.401), a UE requested PDN disconnection event is generated by the MME. This event is equivalent to the UE Requested PDN disconnection event defined in clause 12.2.3.10. The following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
Linked EPS bearer identity

Up
23.3.4.1.6  SCEF requested PDN disconnection
When a PDN disconnection is requested from the SCEF to request for disconnection from the PDN (TS 23.401), a SCEF requested PDN disconnection event is generated by the MME. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
Linked EPS bearer identity

Up
23.3.4.1.7  Start of interception with attached IoT UE active NIDD connection.Word‑p. 270
This event will be generated if interception for a target is started and if the target is already attached with non-IP PDN connection.
This event is equivalent to the Start of interception with E-UTRAN attached UE event defined in clause 12.2.3.13. The following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
APN
SCEF-ID
IAs (if applicable)
EPS bearer identity

Up

23.3.4.2  SGSN related events

23.3.4.2.1  IoT UE Attach for NIDD using SCEF
When an attach activation is generated from an IoT UE this event is generated by the SGSN. This event is equivalent to the Attach event defined in clause 7.4.1 but for an Attach where a GPRS Non-IP Data Delivery Connection using SCEF is requested the following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
Failed attach reason
IAs (if applicable)
APN
Protocol Configuration Options
Attach type

Up
23.3.4.2.2  IoT UE Detach for NIDD using SCEFWord‑p. 271
For detach from an IoT UE this event is generated. This event is equivalent to the detach event defined in clause 7.4.2 but for a detach for a UE with a GPRS Non-IP Data Delivery Connection using SCEF the following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
Detach initiator
Switch off indicator
Detach type

Up
23.3.4.2.3  IoT UE Routing Area Update for NIDD using SCEF
For each Routing Area Update associated with an IoT UE using NIDD using SCEF this event is generated. The event shall be sent in case of Routing Area Update, UE triggered Service Request, as specified in TS 23.060. In case of change of SGSN, the new SGSN shall send the event, and the old SGSN may optionally send the event as well. This event is equivalent to the EPS Tracking Area Update event defined in clause 7.4.6 but for a Routing Area Update for a UE with a GRPS Non-IP Data Delivery Connection using SCEF the following elements are will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information (only for the new SGSN)
Old Location Information (only for the old SGSN)
IAs (if applicable)
Failure reason

Up
23.3.4.2.4  IoT UE requested PDP context activation for NIDD using SCEF
When a PDP context activation is generated for a Non-IP Data Connection this is generated. This event is equivalent to the Packet Data PDP context activation event defined in clause 7.4.3 but for a PDP context activation for a Non-IP Data Delivery Connection using SCEF the following elements are delivered to the DF2 if available:
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
APN
SCEF-ID
Request type
Failed reason
IAs (if applicable)
Protocol Configuration Options
NSAPI

Up
23.3.4.2.5  IoT UE requested PDP context deactivation for NIDD using SCEFWord‑p. 272
At PDP context deactivation for a Non-IP Data Connection this event is generated. This event is equivalent to the Packet Data PDP context deactivation event defined in clause 7.4.5 but for a PDP context deactivation for a Non-IP Data Delivery Connection using SCEF the following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
NSAPI

Up
23.3.4.2.6  SCEF requested PDP context deactivationWord‑p. 273
At SCEF requested PDP context deactivation a PDP context deactivation-event is generated. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
IAs (if applicable)
NSAPI

23.3.4.2.7  Start of interception with PDP context active
This event will be generated if interception for a target is started and if the target has at least one PDP context for a Non-IP Data Connection active. If more than one PDP context is open, for each of them an event record is generated. This event is equivalent to the Start of interception with PDP context active event defined in clause 7.4.4 but for a PDP context for a Non-IP Data Delivery Connection using SCEF the following elements are delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Location Information
APN
SCEF-ID
IAs (if applicable)
NSAPI

Up

23.3.4.3  SCEF related eventsWord‑p. 274
23.3.4.3.1  MME/SGSN originated connection request
When a Connectivity Request is received by the SCEF an MME/SGSN originated connection request event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Information Element
Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
RAT Type
APN
Request type
Failed reason
IAs (if applicable)
Protocol Configuration Options
Bearer identity

23.3.4.3.2  MME/SGSN originated connection update
When a Connectivity Update is received by the SCEF an MME/SGSN originated connection update event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
RAT Type
IAs (if applicable)
Protocol Configuration Options
Linked Bearer identity

23.3.4.3.3  SCEF originated connection update
When a Connectivity Update is sent by the SCEF an SCEF originated connection update event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
IAs (if applicable)
Protocol Configuration Options
Linked Bearer identity

23.3.4.3.4  MME/SGSN originated disconnection requestWord‑p. 275
When a Disconnection Request is received by the SCEF an MME/SGSN originated disconnection request event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
IAs (if applicable)
Linked Bearer identity

23.3.4.3.5  SCEF originated disconnection request
When a Disconnection Request is sent by the SCEF a SCEF originated disconnection request event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
IAs (if applicable)
Linked Bearer identity

23.3.4.3.6  Start of interception with connected UE
This event will be generated if interception for a target is started and if the target is already connected. If there are multiple PDN connections active for the target then for each of them an event report is generated.
These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
Location Information
APN
IAs (if applicable)
Bearer identity

Up
23.3.4.3.7  Non-IP Packet Data Header InformationWord‑p. 276

23.3.4.4  IWK-SCEF related eventsWord‑p. 277
23.3.4.4.1  MME/SGSN originated connection request
When a Connectivity Request is received by the IWK-SCEF an MME/SGSN originated connection request event is generated by the IWK-SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
RAT Type
APN
Request type
Failed reason
Ias (if applicable)
Protocol Configuration Options
Bearer identity

23.3.4.4.2  MME/SGSN originated connection updateWord‑p. 278
When a Connectivity Update is received by the IWK-SCEF from an MME/SGSN, an MME/SGSN originated connection update event is generated by the IWK-SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
RAT Type
Ias (if applicable)
Protocol Configuration Options
Linked Bearer identity

23.3.4.4.3  SCEF originated connection update
When a Connectivity Update is received by the IWK-SCEF from an SCEF, an SCEF originated connection update event is generated by the IWK-SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
Ias (if applicable)
Protocol Configuration Options
Linked Bearer identity

23.3.4.4.4  MME/SGSN originated disconnection requestWord‑p. 279
When a Disconnection Request is received by the IWK-SCEF from an MME/SGSN, an MME/SGSN originated disconnection request event is generated by the IWK-SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
Ias (if applicable)
Linked Bearer identity

23.3.4.4.5  SCEF originated disconnection request
When a Disconnection Request is received by the IWK-SCEF from an SCEF, an SCEF originated disconnection request event is generated by the SCEF. These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
Ias (if applicable)
Linked Bearer identity

23.3.4.4.6  Start of interception with connected UE
This event will be generated if interception for a target is started and if the target is already connected. If there are multiple PDN connections active for the target, then for each of them an event report is generated.
These elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME id
Event Type
Event Time
Event Date
Correlation Number
Network Element Identifier
Logical Function Information
APN
Ias (if applicable)
Bearer identity

23.3.4.5  HSS related eventsWord‑p. 280
23.3.4.5.1  Serving Evolved Packet System for IoT UE
The Serving Evolved Packet System for IoT UE event is generated at the HSS, when the HSS has detected that the target has roamed. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the Serving Evolved Packet System event defined in clause 12.2.3.8. The following elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed ME Id
Event Type
Event Time
Event Date
Network Element Identifier
Logical Function Information
Serving MME/SGSN Address

Up
23.3.4.5.2  HSS subscriber record change for IoT UE
This event will be used to report any change of association between IMSI or MSISDN or External Identifier of the target. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the Subscriber Record Change event defined in clause 12.2.3.15. The following elements will be delivered to the DF2 if available.
Information Element

New observed MSISDN
New observed External Identifier
New observed IMSI
Old observed MSISDN or A MSISDN
Old observed External Identifier
Old observed IMSI
Event Type
Event Time
Event Date
Change Type (MSISDN, or External Identifier or IMSI)
Network Element Identifier (HSS id...)
Other update: carrier specific

Up
23.3.4.5.3  Cancel location for IoT UE
This event "Cancel Location for IoT UE" will be used to report to DF2 when HSS sends to MME one cancel location or purge to serving system. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the Cancel Location event defined in clause 12.2.3.16 but for a target supporting Non-IP Data Delivery using SCEF the following elements are will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Event Type
Event Time
Event Date
Network Element Identifier (HSS Id…)
Previous visited MME/SGSN Identifier

Up

23.3.4.6  HLR related eventsWord‑p. 282
23.3.4.6.1  Serving System for IoT UE
The Serving System for IoT UE event is generated at the HLR, when the HLR has detected that the target has roamed. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the Serving System event defined in clause 7.4.9. The following elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Observed IMEI
Event Type
Event Time
Event Date
Network Element Identifier
Serving System Address

Up
23.3.4.6.2  Subscriber record change for IoT UE
This event will be used to report any change of association between IMSI or MSISDN or External Identifier of the target. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the HLR Subscriber Record Change event defined in clause 7.4.12. The following elements will be delivered to the DF2 if available.
Information Element

New observed MSISDN
Observed External Identifier
New observed IMSI
New observed IMEI
Observed MSISDN
Observed IMSI
Observed IMEI
Event Type
Event Time
Event Date
Network Element Identifier (HLR id...)
IMSI or MSISDN or IMEI change type
Other update: carrier specific

Up
23.3.4.6.3  Cancel location for IoT UE
This event "Cancel Location for IoT UE" will be used to report to DF2 when HLR sends to SGSN one cancel location or purge to serving system. This event can be reported for a target supporting Non-IP Data Delivery using SCEF. This event is equivalent to the Cancel Location event defined in clause 7.4.12. The following elements will be delivered to the DF2 if available.
Information Element

Observed MSISDN
Observed External Identifier
Observed IMSI
Event Type
Event Time
Event Date
Network Element Identifier (HLR Id...)
Previous serving system identifier (VPLMN id…)

Up


Up   Top   ToC