My ETSI TS 103 120 Notes
Find and download ETSI standards here
My notes on ETSI TS 103 120 document titled Lawful Interception (LI); Interface for warrant information.
103 120 Scope
ETSI TS 103 120 document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception. Typically this interface would be used between: on one side, a Communications Service Provider; and, on the other side, a Government or Law Enforcement Agency who is entitled to request a lawful action.
The ETSI reference model for LI (ETSI TS 102 232-1) defines three interfaces between law enforcement and CSPs, called HI-1, HI-2 and HI-3. The protocol defined in 103 120 document is designed to provide a large part of the functionality for HI-1. It is not designed to be used for HI-2 (delivery of intercept related information) or HI-3 (delivery of communications content). The protocol designed in 103 120 document may also be used for interfaces which require structured exchange of information relating to the establishment and management of Lawful Interception. The general view is that the HI-1 concept can also be used for other legal actions than LI. For that reason the present document could, besides LI, also be applied for retained data requests, seized data requests, data preservation orders and other similar legal requests
See specification for full details.
8.3 LDTaskObject
8.3.1 Overview
An Lawful Disclosure Task Object (LDTaskObject) represents the state of an LD Task - that is, the act of disclosing information. This corresponds to the WarrantTargetID and WarrantTechSpec elements defined in ETSI TR 103 690. In general, multiple tasks may be authorised by a single warrant.
The LDTaskObject consists of the following fields.
| Field | Format | Description | Reference |
|---|---|---|---|
| Reference | LDID (see ETSI TS 103 280) | LDID assigned to the product of task. | Clause 8.3.2 |
| Status | LDTaskStatus Dictionary Entry. | The current status of the task as determined by the Receiver. | Clause 8.3.3 |
| StatusReason | ActionUnsuccessful structure (see clause 6.4.9). | Optional information for the Receiver to indicate why the Object is in a certain state (such as Invalid or Rejected). Usage for national agreement. | Clause 6.4.9 |
| DesiredStatus | LDTaskDesiredStatus Dictionary Entry. | The current status of the task as specified by the Sender. | Clause 8.3.4 |
| RequestDetails | LDRequestDetails (see clause 8.3.5). | Details regarding the content of the disclosure request, such as identifiers and dates. | Clause 8.3.5 |
| DeliveryDetails | List of LDDeliveryDestination structures (see clause 8.3.6). | Destination(s) for the disclosure product. | Clause 8.3.6 |
| ApprovalDetails | ApprovalDetails (see annex E). | Details regarding the approval for this Task, including dates and signatures where appropriate. | Clause 8.2.9 |
| CSPID | EndpointID (see clause 6.2.4). | Describes the CSP required to implement the Task. | Clause 8.2.10 |
| HandlingProfile | LDHandlingProfile (see clause 8.2.11). | A dictionary entry which gives the name of a handling profile that represents a set of configuration information associated with this task. | Clause 8.2.11 |
| Flags | LDTaskFlags (see clause 8.3.7). | A set of flags associated with the Task Object. | Clause 8.3.7 |
| NationalLDTaskingParameters | See annex G. | See annex G. | Annex G |
8.3.2 Reference
The Reference field gives a reference identifier for the Task, for correlation with other processes. For LD, this shall be set to the LDID that will be assigned to the product of the disclosure. Format will be as per ETSI TS 103 280.
8.3.3 Status
The Status field gives the status of the LDTaskObject as determined by the Receiver. A Sender shall not attempt to set the Status as part of a CREATE or UPDATE Request, and a Receiver shall return an Action Unsuccessful Information Response if the Sender attempts to do so.
The Status field provides a key mechanism for mapping the content of the Object to the relevant nationally-defined processes. The rules for evaluating the correct value of the Status field shall be defined in the relevant national profile.
Given as a LDTaskStatus Dictionary Entry. The LDTaskStatus Dictionary is defined in table 8.16 (see annex F for more details on Dictionaries).
| Dictionary Owner | Dictionary Name |
|---|---|
| ETSI | LDTaskStatus. |
| Value | Meaning |
|---|---|
| AwaitingApproval | he Task is still waiting approval from one or more relevant authorities. |
| AwaitingDisclosure | The Task is approved, but is not yet processed by the LD system. |
| Disclosed | The Task has been processed and the product has been disclosed by the LD system. |
| DisclosureNotAvailable | The Task has been processed and the CSP has determined there is no product available to disclosure. |
| Rejected | The Task has been explicitly denied or rejected by one or more relevant authorities. |
| Cancelled | The Task has been permanently cancelled. |
| Error | The Task has not been processed due to a problem with the underlying LD system. |
| Invalid | The Task has not been processed to a problem with the current information populated in the Task Object. |