Avamprogetto 2a

Technical requirements for the handover interfaces for the execution of telecommunications surveillance

4.3.3.1.5.8 Elements of the HI-1 and LITask objects for rejection or error response

In case of error response due to invalid request error use the elements shown in the table below (UPDATERsponse):

UPDATEResponse

Element or attribute Description Example

HI-1 Object

ObjectIdentifier UUID according to 8a1a0c46-2495-46d5-82c3-

IETF RFC 4122 canonical 1900dcecaaa6

form

Generation Positive integer2

LastChanged QualifiedDateTime (see ETSI 2016-07-12T13:30:00+02:00

TS 103 280 V1.2.1)

LITask

Reference LIID (see ETSI TS 103 280). 2016092187654321

Status/ common:Owner

TaskStatus PTSS PTSS

proprietary dictionary entry

and ShortString (see ETSI

TS 103 280 V1.2.1)

Status/ common:Name

TaskStatus PTSS TaskStatus

proprietary dictionary entry

and ShortString (see ETSI

TS 103 280 V1.2.1)

Status/ common:Value

TaskStatus PTSS Invalid

proprietary dictionary entry

and ShortString (see ETSI

TS 103 280 V1.2.1)

Table 4-32: Elements of the HI-1 and LITask objects for invalid response

4.3.3.2 Message flow for secure email order processing for retained data

Retained data orders encompass the retroactive interception data (see section 7) and the information requests (see section 8).

The secure email transport method allows the exchange of retained data orders and data in both HI-A and HI-B domains described in ETSI TS 102 657 V1.17.1.

4.3.3.2.1 Message flow for successful email order processing for retained data

The following figure shows the message flow of the secure email interception orders for retained data exchange between the PTSS and CSP in case of successful processing.