Content for TS 33.128 Word version: 18.6.0

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…

6.3.3 LI at SGW/PGW and ePDG 6.3.3.0 General 6.3.3.1 Provisioning over LI_X1 6.3.3.1.1 General 6.3.3.1.2 Non-CUPS Architecture 6.3.3.1.3 CUPS Architecture 6.3.3.1.4 Provisioning of the MDF2 6.3.3.1.5 Provisioning of the MDF3
...

6.3.3 LI at SGW/PGW and ePDG p. 134

6.3.3.0 General p. 134

Unless otherwise specified, the following clauses apply to both CUPS and non-CUPS EPS architectures. When CUPS architecture is used, unless otherwise specified, the term SGW/PGW refers to both the SGW-U/PGW-U and the SGW-C/PGW-C.

Unless otherwise specified, the following clauses apply in the case of EPC-5GC interworking via combined SMF+PGW-C and UPF+PGW-U.

6.3.3.1 Provisioning over LI_X1 p. 134

6.3.3.1.1 General p. 134

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.

6.3.3.1.2 Non-CUPS Architecture p. 136

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.

Table 6.3.3.1-1: ActivateTask message for the IRI-POI and CC-POI in the SGW/PGW and ePDG in non-CUPS architecture

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF.	M
TargetIdentifiers	One of the target identifiers listed in the clause above.	M
DeliveryType	Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant.	M
ListOfDIDs	Delivery endpoints of LI_X2 or LI_X3. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.	M
TaskDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.	C

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.

6.3.3.1.3 CUPS Architecture p. 136

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.

Table 6.3.3.1-2: ActivateTask message for the IRI-POI, CC-TF and IRI-TF in the SGW-C/PGW-C in CUPS architecture

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF. If the CC-TF or IRI-TF is also being tasked for the same interception, the same XID shall be used.	M
TargetIdentifiers	One or more of the target identifiers listed in clause 6.3.3.1.1.	M
DeliveryType	Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant. NOTE: "X2Only" for IRI-POI, IRI-TF and "X3Only" for CC-TF can also be also be used.	M
TaskDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.	C
ListOfDIDs	Delivery endpoints of LI_X2 or LI_X3. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.	M

6.3.3.1.4 Provisioning of the MDF2 p. 137

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.

Table 6.3.3.1-3: ActivateTask message for MDF2

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF.	M
TargetIdentifiers	One or more of the target identifiers listed in the paragraph above.	M
DeliveryType	Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant. (Ignored by the MDF2).	M
TaskDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.	C
ListOfDIDs	Delivery endpoints of LI_HI2. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.	M
ListOfMediationDetails	Sequence of Mediation Details, See Table 6.3.3.1-4.	M

Table 6.3.3.1-4: Mediation Details for MDF2

ETSI TS 103 221-1 [7] field name	Description	M/C/O
LIID	Lawful Intercept ID associated with the task.	M
DeliveryType	Set to "HI2Only".	M
ListOfDIDs	Details of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.	C
ServiceScoping	Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7], Annex C, Table C.2.	C
MediationDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the MediationDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. This field shall be included if deviation from the taskDetails HeaderReporting TaskDetailsExtensions is required. If included, the details shall be used instead of the HeaderReporting instructions specified in the HeaderReporting field in the TaskDetails structure.	C

6.3.3.1.5 Provisioning of the MDF3 p. 137

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.

Table 6.3.3.1-5: ActivateTask message for MDF3

ETSI TS 103 221-1 [7] field name	Description	M/C/O
XID	XID assigned by LIPF.	M
TargetIdentifiers	One or more of the target identifiers listed in the paragraph above.	M
DeliveryType	Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant.	M
TaskDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.	C
ListOfDIDs	Delivery endpoints of LI_HI3 or LI_MDF. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.	M
ListOfMediationDetails	Sequence of Mediation Details, See Table 6.3.3.1-6.	M

Table 6.3.3.1-6: Mediation Details for MDF3

ETSI TS 103 221-1 [7] field name	Description	M/C/O
LIID	Lawful Intercept ID associated with the task.	M
DeliveryType	Set to "HI3Only".	M
ListOfDIDs	Details of where to send the CC for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.	C
ServiceScoping	Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7], Annex C, Table C.2.	C
MediationDetailsExtensions/ HeaderReporting	Header reporting-specific tag to be carried in the MediationDetailsExtensions field of ETSI TS 103 221-1 [7]. See Table 6.2.3.9.2-1. This field shall be included if deviation from the taskDetails HeaderReporting TaskDetailsExtensions is required. If included, the details shall be used instead of the HeaderReporting instructions specified in the HeaderReporting field in the TaskDetails structure.	C