---
title: "e-Evidence, cross-border exchange, and ETSI TS 103 462 ILHI"
chapter: "27"
---

# e-Evidence, cross-border exchange, and ETSI TS 103 462 ILHI

Cross-border legal cooperation adds requesting and responding authorities, differing national formats, time limits, secure channels, and legal-assistance decisions. ETSI TS 103 462 defines an inter-LEMF handover interface (ILHI). ETSI TS 104 144 supports interfaces for the EU e-Evidence Regulation. Technical interoperability never overrides jurisdiction or legal review.

> **Safety boundary:** this chapter teaches lawful, governed system design from
> public standards. It does not provide operational targeting, activation,
> decryption, surveillance-evasion, or covert collection instructions.

## The mental model

| Concept | Plain meaning | Control that must travel with it |
|---|---|---|
| **Requesting/responding LEMF** | Authorities exchange approved material across an inter-LEMF path | Each side keeps its legal responsibility |
| **ILHI** | Standardized inter-LEMF transport and interworking | Bilateral agreement and secure trust are required |
| **Interworking function** | Maps local formats to agreed cross-border format | Preserve provenance and report transformation |
| **e-Evidence order** | Structured cross-border order to a service provider | Validate authority, service, deadlines, and remedies |
| **Conflict of law** | Duties in different jurisdictions may conflict | Stop and escalate; do not solve in code |
| **Delivery country** | Recipient and onward handling are jurisdiction-bound | Routing must match approved legal path |

## Apply it as a controlled workflow

1. Identify requesting, responding, provider, and receiving legal roles.
2. Validate the cooperation instrument and any grounds for refusal or escalation.
3. Pin ILHI/e-evidence versions and bilateral profiles.
4. Establish approved endpoints, trust anchors, and interworking mappings.
5. Test receipt, delay, partial availability, translation, and onward-custody evidence.
6. Close both sides with aligned status and retention outcomes.

## Evidence to demand

- Cross-border routing cannot be changed by ordinary network failover.
- Original and transformed representations remain linked and integrity-protected.
- Legal deadlines are visible separately from technical latency.
- Unknown national extensions stop safely.

## Failure to reason about

A disaster-recovery route would send cross-border handover through an unapproved country. Ordinary network resilience would violate legal routing. Use policy-aware route constraints and a controlled unavailable state.

## Feynman check

Cross-border exchange is like two courts using different forms. A trusted translator can align the forms, but only the law decides whether the package may cross the border.