Content for  TS 33.128  Word version:  18.7.0

If the warrant is for IRI and CC, then the LI functions in the SGW/PGW shall be provisioned in accordance with clause 6.3.3.1.2 for non-CUPS architecture and clause 6.3.3.1.3 for CUPS architecture, the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4, and the MDF3 shall be provisioned in accordance with clause 6.3.3.1.5. If the warrant is for IRI only, the IRI-POI in the SGW/PGW shall be provisioned in accordance with clause 6.3.3.1.2 for non-CUPS architecture and clause 6.3.3.1.3 for CUPS architecture and the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4. If approach 1 described in clause 6.2.3.9 is used for packet header information reporting:

• For non-CUPS architecture, the IRI-POI in the SGW/PGW shall be provisioned in accordance with clause 6.3.3.1.2 and the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4.
• For CUPS architecture, the IRI-TF in the SGW-C/PGW-c shall be provisioned in accordance with clause 6.3.3.1.3 and the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4.

If approach 2 described in clause 6.2.3.9 is used for packet header information reporting:

• For non-CUPS architecture, the CC-POI in the SGW/PGW shall be provisioned in accordance with clause 6.3.3.1.2, the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4, and the MDF3 shall be provisioned in accordance with clause 6.3.3.1.5.
• For CUPS architecture, the CC-TF in the SGW-C/PGW-C shall be provisioned in accordance with clause 6.3.3.1.3, the MDF2 shall be provisioned in accordance with clause 6.3.3.1.4, and the MDF3 shall be provisioned in accordance with clause 6.3.3.1.5.

The LI functions in the SGW/PGW and ePDG, the MDF2 and 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):

• IMSI.
• MSISDN (using the E164Number target identifier format from ETSI TS 103 221-1 [7]).
• IMEI.

In the case of EPC-5GC interworking via combined SMF+PGW-C and UPF+PGW-U, the LI functions in the SMF+PGW-C, MDF2 and MDF3 shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivatlent if ETSI TS 103 221-1 [7] is not used):

• SUPINAI.
• SUPIIMSI.
• IMSI.
• GPSINAI.
• GPSIMSISDN.
• MSISDN (using the E164Number target identifier format from ETSI TS 103 221-1 [7]).
• PEIIMEISV.
• PEIIMEI.
• IMEI.

When the target identifier is an IMSI, the LI functions in the SMF+PGW-C shall also trigger when events associated to a SUPI in the form of an IMSI with a value matching the provisioned IMSI target identifier value are detected. Likewise, when the target identifier is a SUPIIMSI, the LI functions in the SMF+PGW-C shall also trigger when events associated to an IMSI with a value matching the provisioned SUPIIMSI target identifier value are detected. When the target identifier is an MSISDN, the LI functions in the SMF+PGW-C shall also trigger when events associated to a GPSI in the form of an MSISDN with a value matching the provisioned MSISDN target identifier value are detected. Likewise, then the target identifier is a GPSIMSISDN, the LI functions in the SMF+PGW-C shall also trigger when events associated to an MSISDN with a value matching the provisioned GPSIMSISDN target identifier value are detected. When the target identifier is an IMEI, the LI functions in the SMF+PGW-C shall also trigger when events associated to a PEI in the form of an IMEI with a value matching the provisioned IMEI target identifier value are detected. Likewise, then the target identifier is a PEIIMEI, the LI functions in the SMF+PGW-C shall also trigger when events associated to an IMEI with a value matching the provisioned PEIIMEI target identifier value are detected.

When the EPS is implemented using non-CUPS architecture, the IRI-POI and CC-POI present in the SGW/PGW and ePDG are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. A single task may be used. Table 6.3.3.1-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI and the CC-POI in the SGW/PGW.

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.

When the EPS is implemented using CUPS architecture, the IRI-POI, IRI-TF and CC-TF present in the SGW-C/PGW-C and the IRI-POI and CC-POI present in the ePDG are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. When the EPS is implemented using CUPS architecture, the IRI-POI, IRI-TF and CC-TF present in the SGW-C/PGW-C and the IRI-POI and CC-POI present in the ePDG are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.3.3.1-2 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI, CC-TF and IRI-TF in the SGW-C/PGW-C. If the ePDG is used, the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI and the CC-POI in the ePDG are detailed in Table 6.3.3.1-1.

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 CP entity of the SGW/PGW or ePDG shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.3.3.1-3 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.

The MDF3 listed as the delivery endpoint for the xCC generated by the CC-POI in the UP entity of the SGW/PGW or ePDG shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.3.3.1-5 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF3. If packet header reporting is authorised and approach 2 described in clause 6.2.3.9 is used, the endpoint for the MDF3 shall be the MDF2 over LI_MDF.