Content for  TS 33.128  Word version:  18.6.0

If the warrant is for IRI and CC, then the IRI-POI and the CC-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2, the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3, and the MDF3 shall be provisioned in accordance with clause 6.2.3.1.4. If the warrant is for IRI only, the IRI-POI in the SMF shall be provisioned in accordance with clause 6.2.3.1.2 and the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3. If approach 1 described in clause 6.2.3.9 is used for packet header information reporting, the IRI-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2 and the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3. If approach 2 described in clause 6.2.3.9 is used for packet header information reporting, the CC-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2, the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3, and the MDF3 shall be provisioned in accordance with clause 6.2.3.1.4. If the SMF is part of a combined SMF+PGW-C, the requirements in clause 6.3.3 shall apply.

The IRI-POI, IRI-TF and CC-TF present in the SMF are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. The POI/TF in the SMF 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):

• SUPIIMSI.
• SUPINAI.
• PEIIMEI.
• PEIIMEISV.
• GPSIMSISDN.
• GPSINAI.

Table 6.2.3-0A shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI, in the SMF.

To enable packet header information reporting, parameters specified in Table 6.2.3.9.2-1: PDHRReportingExtensions parameters shall be provided as the TaskDetailsExtensions/HeaderReporting field of the LI_X1 provisioning message.

The MDF2 listed as the delivery endpoint for xIRI generated by the IRI-POI in the SMF or the IRI-POI in the UPF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.2.3-0B shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2. The MDF2 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):

• SUPIIMSI.
• SUPINAI.
• PEIIMEI.
• PEIIMEISV.
• GPSIMSISDN.
• GPSINAI.

The MDF3 listed as the delivery endpoint for the xCC generated by the CC-POI in the UPF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.2.3-0D shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF3. If packet header information reporting is authorised and approach 2 described in clause 6.2.3.9.1 is used, the endpoint for the MDF3 shall be the MDF2 over LI_MDF. The MDF3 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):

• SUPIIMSI.
• SUPINAI.
• PEIIMEI.
• PEIIMEISV.
• GPSIMSISDN.
• GPSINAI.

The IRI-POI present in the SMF shall send the xIRIs over LI_X2 for each of the events listed in clause 6.2.3.3 of TS 33.127, the details of which are described in the following clauses. In the case where the SMF is part of a combined SMF+PGW-C, the details of the events are specified in clause 6.3.3.2. The IRI-POI present in the SMF shall also send a SeparatedLocationReporting xIRI (as described in clause 7.3.4.1) when the IRI-POI provisioned in the H-SMF detects that the V-SMF has sent location data via the HsmfUpdateData service operation to the H-SMF that does not otherwise trigger an existing SMF record type. As specified in clause 5.6.1 of TS 23.501, a PDU session may support either a single-access PDU Connectivity Service (referred to as a single-access PDU Session) or a multi-access PDU Connectivity Service (referred to as a Multi-Access PDU (MA PDU) session). The details of the messages for single-access PDU sessions are provided below in clauses 6.2.3.2.2, 6.2.3.2.3, 6.2.3.2.4, 6.2.3.2.5 and 6.2.3.2.6. The details of the messages for multi-access PDU sessions are provided below in clauses 6.2.3.2.7 and 6.2.3.2.8.

The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionEstablishment record when the IRI-POI present in the SMF detects that a single-access PDU session has been established for the target UE. The IRI-POI present in the SMF shall generate the xIRI for the following events:

• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the N1 NAS message (via AMF) PDU SESSION ESTABLISHMENT ACCEPT to the UE and the 5G Session Management (5GSM) state within the SMF is changed to PDU SESSION ACTIVE (see clauses 6.1.3.3 and 6.4.1 of TS 24.501).
• For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Create Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see clauses 5.2.1, 5.2.2.7, 5.2.3, 6.1.2.4, and 6.1.6.4 of TS 29.502).

If the Npcf_SMPolicyControl_Create response received from the PCF for the target UE in response to Npcf_SMPolicyControl_Create request includes PCC rules in which the traffic control policy data contains either a routeToLocs IE or trafficSteeringPolIdDl IE and/or trafficSteeringPolIdUl IE, then the SMF shall include those PCC rules in the xIRI. These PCC rules correspond to policies that influence the target UE's traffic flows (see clause 5.5.3 of TS 29.513).

Each PCC rule for traffic influence has the payload defined in Table 6.2.3-1E.

The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionModification record when the IRI-POI present in the SMF detects that a single-access PDU session has been modified for the target UE. The IRI-POI present in the SMF shall generate the xIRI for the following events:

• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) PDU SESSION MODIFICATION COMPLETE from the UE and the 5GSM state within the SMF is returned to PDU SESSION ACTIVE (see clauses 6.1.3.3, 6.3.2 and 6.4.2 of TS 24.501). This applies to the following two cases:
  • UE initiated PDU session modification (see clause 4.3.3.2 of TS 23.502).
  • Network initiated PDU session modification (see clause 4.3.3.2 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the N1 NAS message (via AMF) PDU SESSION ESTABLISHMENT ACCEPT to the UE and the 5GSM state within the SMF remains in the PDU SESSION ACTIVE (see clauses 6.1.3.3 and 6.4.1 of TS 24.501). This applies to the following case:
  • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP); see clauses 4.9.2.1 and 4.9.2.2 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the Nsmf_PDUSession_UpdateSMContext response to the AMF when the PDU session modified or SM context is changed. In this case, the Nsmf_PDUSession_UpdateSMContext response may not have an embedded NAS message. This applies to the following case:
  • Handover scenarios (5G to 5G, see clauses 4.9.1.2 and 4.9.1.3 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Establishment Response when a PFCP session is established on a new UPF (or V-UPF in a roaming case) within the existing SM Context without a following Nsmf_PDUSession_Update_Context message being sent to the AMF. This applies to the following case:
  • Handover scenarios (5G to 5G, see clauses 4.9.1.2 and 4.9.1.3 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Modification Response when a new tunnel Identifier (local or remote) is added to the PDU session or removed from the PDU session without a following Nsmf_PDUSession_Update_Context message being sent to the AMF. This applies to the following case:
  • Handover scenarios (5G to 5G, see clauses 4.9.1.2 and 4.9.1.3 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Deletion Response when a PFCP session is deleted from an SM Context that remains active. This applies to the following case:
  • Handover scenarios (5G to 5G, see clauses 4.9.1.2 and 4.9.1.3 of TS 23.502).
• For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) receives the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoFromUe IE containing the PDU SESSION MODIFICATION COMPLETE (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502). This applies to the following three cases:
  • UE initiated PDU session modification (see clause 4.3.3.3 of TS 23.502).
  • Network (VPLMN) initiated PDU session modification (see clause 4.3.3.3 of TS 23.502).
  • Network (HPLMN) initiated PDU session modification (see clause 4.3.3.3 of TS 23.502).
• For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Create Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502) while it had received a N16 Nsmf_PDU_Session_Create Request message with an existing PDU Session Id with access type being changed. This applies to the following case:
  • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP); see clauses 4.9.2.3 and 4.9.2.4 of TS 23.502) where the V-SMF is used for the PDU session on the new access type only.
• For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see TS 29.502) while it had received a N16 Nsmf_PDU_Session_Update Request message with an existing PDU Session Id with access type being changed. This applies to the following case:
  • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP) where the same V-SMF is used for the PDU session on both access types.
• For a non-roaming scenario, SMF sends a Nsmf_EventExposure_Notify request to the NEF or AF for the target UE for the event "UP Path Change" related to a corresponding subscription from AF (see clause 4.2.2 of TS 29.508).
• For a non-roaming scenario, SMF sends a Nsmf_EventExposure_AppRelocationInfo response to the NEF or AF for the target UE in response to Nsmf_EventExposure_AppRelocationInfo request sent by NEF or AF to SMF (see clause 4.2.5 of TS 29.508).
• For a non-roaming scenario, SMF receives a Nnef_PFDManagement_Fetch response from the NEF for the target UE in response to Nnef_PFDManagement_Fetch request sent by SMF to NEF (see clause 4.2.2 of TS 29.551).

If the Npcf_SMPolicyControlUpdateNotify response sent to the PCF for the target UE in response to an Npcf_SMPolicyControlUpdateNotify request includes PCC rules in which the traffic control policy data contains either a routeToLocs IE or trafficSteeringPolIdDl IE and/or trafficSteeringPolIdUl IE, then the SMF shall include those PCC rules in the xIRI. These PCC rules correspond to policies that influence the target UE's traffic flows (see clause 5.5.3 of TS 29.513).

The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionRelease record when the IRI-POI present in the SMF detects that a single-access PDU session has been released. The IRI-POI present in the SMF shall generate the xIRI for the following events:

• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) PDU SESSION RELEASE COMPLETE from the UE and the 5GSM state within the SMF is changed to PDU SESSION INACTIVE (see clauses 6.1.3.3 and 6.4.3 of TS 24.501). This applies to the following two cases:
  • UE initiated PDU session release (see clause 4.3.4.2 of TS 23.502).
  • Network initiated PDU session release (see clause 4.3.4.2 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) STATUS from the UE with the cause values listed in clause 6.5.3 of TS 24.501 and the 5GSM state within the SMF is changed to PDU SESSION INACTIVE. One of the cases where this applies is of UE finding that the PDU session ID received in a PDU SESSION MODIFICATION COMMAND is invalid.
• For a non-roaming scenario, the SMF (or for a roaming scenario, the V-SMF in the VPLMN) sends the Nsmf_PDUSession_ReleaseSMContext Response to the AMF (see clause 5.2.2.4 of TS 29.502). This applies to the case where the PDU session is released without any N1 or N2 messages (e.g. AMF initiates the PDU session release when it finds that the PDU session is no longer associated with the UE, see clause 4.2.2.4 of TS 23.502).
• For a non-roaming scenario, the SMF (or for a roaming scenarios, V-SMF in the VPLMN) sends Nsmf_PDUSession_SMContextStatusNotify (see clause 6.1.6.2.8 of TS 29.502) with RELEASED in the ResourceStatus IE (see clause 6.1.6.3.1 of TS 29.502) to the AMF. This applies to the case where PDU session release is neither initiated by a NAS message nor by Nsmf_PDUSessionReleaseSMContext Request message (see clause 5.2.2.5 of TS 29.502).
• For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) receives the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoFromUe IE containing the PDU SESSION RELEASE COMPLETE (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502) from the V-SMF. This applies to the following three cases:
  • UE initiated PDU session release (see clause 4.3.4.3 of TS 23.502).
  • Network (VPLMN) initiated PDU session release (see clause 4.3.4.3 of TS 23.502).
  • Network (HPLMN) initiated PDU session release (see clause 4.3.4.3 of TS 23.502).
• For a roaming scenario, H-SMF in the HPLMN sends the Nsmf_PDUSession_Release Response to the V-SMF (see clause 5.2.2.9 of TS 29.502). This applies to the case where the PDU session is released without any N1 or N2 messages (e.g. AMF in the VPLMN initiates the PDU session release when it finds that the PDU session is no longer associated with the UE, see clause 4.3.4.3 of TS 23.502).
• For a roaming scenario, H-SMF in the HPLMN sends a Nsmf_PDUSession_StatusNotify (see clause 6.1.6.2.17 of TS 29.502) with RELEASED in the ResourceStatus IE (see clause 6.1.6.3.1 of TS 29.502) to the V-SMF. This applies to the case where PDU session release is neither initiated by a NAS message nor by Nsmf_PDUSessionRelease Request message (see clause 5.2.2.9 of TS 29.502).

The IRI-POI in the SMF shall generate an xIRI containing an SMFStartOf­Interception­WithEstablished­PDUSession record when the IRI-POI present in the SMF detects that a single-access PDU session has already been established for the target UE when interception starts. In a non-roaming scenario, the IRI-POI in the SMF (or in a roaming scenario, the IRI-POI in the V-SMF in the VPLMN) shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case:

• The 5GSM state within the SMF for that UE is 5GSM: PDU SESSION ACTIVE or PDU SESSION MODIFICATION PENDING.

In a home-routed roaming scenario, the IRI-POI in the H-SMF shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case:

• The H-SMF had not sent a Nsmf_PDU_Session_Update Request (n1SmInfoToUe: PDU SESSION RELEASE COMMAND) to the V-SMF for a PDU session and H-SMF had previously sent a Nsmf_PDU_Session_Create Response (n1SmInfoToUE: PDU SESSION ESTABLISHMENT ACCEPT) to the V-SMF for that PDU session.

The IRI-POI in the SMF shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record for each of the PDU sessions (that meets the above criteria) associated with the newly identified target UEs.

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

The IRI-POI in the SMF shall generate an xIRI containing an SMFUnsuccessfulProcedure record when the IRI-POI present in the SMF detects an unsuccessful procedure or error condition for a UE matching one of the target identifiers provided via LI_X1. Accordingly, the IRI-POI in the SMF generates the xIRI when one of the following events are detected:

• SMF sends a PDU SESSION ESTABLISHMENT REJECT message to the target UE.
• SMF sends a PDU SESSION MODIFICATION REJECT message to the target UE.
• SMF sends a PDU SESSION RELEASE REJECT message to the target UE.
• SMF receives a PDU SESSION MODIFICATION COMMAND REJECT message from the target UE.
• An ongoing SM procedure is aborted at the SMF, due to e.g. a 5GSM STATUS message sent from or received by the SMF.