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…

...

A (Normative) ASN.1 Schema for the Internal and External Interfaces p. 382

The ASN.1 module describing the structures used for LI_X2, LI_X3, LI_HI2 and LI_HI3 ("TS33128Payloads") is given in the file TS33128Payloads.asn which accompanies the present document.

B (Normative) LI Notification p. 382

Based on clause 5.6 of the present document, this annex defines a system of management notification of LI system with the LI_HI4 interface.

The LI_HI4 interface shall be used to transport specific LI service O&M information (referred to as LI Notification) from the CSP to the LEMF. The individual parameters of the LI Notification message shall be coded using ASN.1 and the basic encoding rules (BER). The delivery of LI Notification shall be performed directly using the same mechanism as used for delivery of IRI messages over LI_HI2 and CC over LI_HI3.

The LI Notification shall be used to send electronic notification to the LEMF in the following cases:

after the activation of lawful interception;
after the deactivation of lawful interception;
after the modification of an active lawful interception.

Table B.1-1: LINotification message

Field Name	Description	M/C/O
notificationType	Information on the type of notification: activation, deactivation or modification	M
deliveryInformation	Delivery Information which has been decided by the LEA in terms of delivery numbers, IP addresses for LI_HI2 and LI_HI3	O
appliedTargetID	Target Identifier applied in the ADMF for the warrant	O
appliedStartTime	Start time applied to the ADMF for the warrant	C
appliedEndTime	End time applied to the ADMF for the warrant	C
appliedTargetIsLocal	Set to TRUE if the type of target is known to be local, absent otherwise (i.e. unknown)	C
appliedTargetIsNonLocal	Set to TRUE if the type of target is known to be non-local, absent otherwise (i.e. unknown)	C

Conditional parameters shall be set as follows:

LI Activation Notification
Field Name	Description	M/C/O
notificationType	Activation	M
appliedStartTime	Always present and represents: The Start Date/Time in the warrant or, The Date/Time of the CSP activation in the ADMF or, The scheduled future Start Date/Time.	C
appliedEndTime	Absence means the interception has been activated with no predefined End Date/Time. Presence means the End time is scheduled to be applied at that (future) time.	C

LI Modification Notification
Field Name	Description	M/C/O
notificationType	Modification	M
appliedStartTime	Present and provides the new Start Date/Time if modified by the LI Modification command	C
appliedEndTime	Present and provides the new End Date/Time if modified by the LI Modification command	C

LI Deactivation Notification
Field Name	Description	M/C/O
notificationType	Deactivation	M
appliedStartTime	Absent	C
appliedEndTime	Present and provides the actual End Date/Time, e.g. timed stop as per initial warrant or as per new warrant, or as pre-emptive audited stop from the LEA, or major LI failure.	C

The individual notifications parameters shall be sent to the LEMF as soon as possible with the lowest latency at least once (if available).

The MDF2/MDF3 will deliver the LINotification message to LEMF.

C (Normative) XSD Schema for LI_X1 extensions p. 383

The XSD schema describing the extensions used for LI_X1 is given in the file urn_3GPP_ns_li_3GPPX1Extensions.xsd which accompanies the present document.