The ETSI TS 101 331 and 3GPP TS 33.127 standards have established a technically coherent framework for lawful intercept in IP and 5G networks. Network functions expose X1/X2/X3 interfaces, mediation devices aggregate and deliver, and the warrant management workflow is reasonably well defined. What the standards do not address is the jurisdictional question: when a user served by Network A roams onto Network B while subject to a warrant issued in Country C, which operator is obligated to intercept, what they must deliver, and to whom.
The roaming intercept jurisdiction problem
For inbound roamers, the visited network (VPLMN) carries the traffic. Under most national frameworks, the intercept obligation falls on the operator that carries the traffic — which in a roaming scenario is the visited operator, who has no awareness of warrants issued by the home jurisdiction. The home operator (HPLMN) may be notified that the target is roaming but cannot compel the visited operator to intercept.
The practical resolution in most bilateral roaming scenarios is that the HPLMN signals interception to the visited network through the roaming intercept trigger mechanisms defined in 3GPP specifications. But this requires that the visited network has implemented the roaming intercept capability — a capability that 3GPP specifies but that is not universally deployed — and that the bilateral roaming agreement addresses intercept obligations, which most do not explicitly.
What operators actually need to do
Operators serving international traffic — including as the visited network for inbound roamers — should have a documented answer to two questions: which national frameworks create intercept obligations for traffic carried on their network, and does their LI infrastructure have the technical capability to satisfy those obligations for roaming traffic specifically.
The second question is where most compliance gaps exist. An operator may have a fully certified LI system for domestic traffic and have no tested capability for roaming intercept scenarios. The warrant processing workflow, the delivery interface, and the target identification method are all different for a roaming intercept, and these paths are rarely tested as rigorously as the domestic case.
Bilateral agreement gaps
Most roaming agreements are silent on intercept obligations. This creates ambiguity about whether the VPLMN is required to support roaming intercept triggers from the HPLMN, what the VPLMN's liability is if it cannot satisfy a request, and who is responsible for delivery to the requesting lawful authority.
Operators should review their standard roaming agreement templates to ensure that intercept obligations are addressed explicitly — not to increase liability but to clarify which party is responsible for which aspect of the intercept chain when the technical capability exists and is invoked. Ambiguity in this area creates risk for both parties in a roaming relationship.
