Understanding MVNO lawful interception responsibilities is essential before entering any market. One of the most common — and most consequential — questions in the MVNO business model is who bears the legal responsibility for lawful interception. The answer seems straightforward at first glance, but in practice it is layered with complexity. The legal obligation, the technical capability, the contractual arrangements, and the practical execution often involve both the MVNO and the host MNO, and the boundaries between their respective responsibilities can be unclear, contested, or simply unaddressed in the commercial agreements that govern their relationship.
This article provides a detailed examination of the legal, technical, and contractual dimensions of LI responsibility in the MVNO-MNO relationship, drawing on the regulatory frameworks of major European markets and the practical experience of operators navigating these issues.
MVNO Lawful Interception Responsibilities
Under the European Electronic Communications Code, Member States can make lawful interception a condition of the general authorisation, but national law decides who must do what. Many countries oblige every provider of a public service; others, such as Germany, put the technical obligation on whoever operates the network installation and give pure service providers lighter duties.
For MVNOs that hold their own regulatory registration — which is the case for most MVNOs operating in European markets — this means that the MVNO carries LI duties of its own, which may or may not include the full technical obligation. The fact that the MVNO uses the MNO’s network infrastructure does not make compliance the MNO’s problem alone, but it also does not automatically move every obligation to the MVNO.
National rules differ on this point. In Germany, § 170(1) TKG obliges whoever operates the telecommunications installation used to provide the service. A reseller or light MVNO that relies on its host’s installation must, under § 170(2) TKG, make sure the host can implement interception orders and tell the Bundesnetzagentur who implements them. A full MVNO that runs its own core is itself an operator under § 170(1). In the Netherlands, the Telecommunicatiewet places the obligation on the provider of the public electronic communications service. In France, the CPCE requires operators declared with ARCEP to maintain interception capabilities. The specific language differs, and so does the outcome: depending on the country and on how much of the network the MVNO operates, the obligation may sit with the MVNO, with the host MNO, or with both.
Many jurisdictions allow or recognise arrangements where the MNO performs interception on behalf of the MVNO. Where the MVNO is itself the obliged party and the MNO only acts on its behalf, the MVNO stays responsible for the result (in Germany, an obliged party may use a contractor but must remain able to implement orders under its own responsibility, § 5(3) TKÜV). The MVNO cannot simply point to the MNO and claim that compliance is the MNO’s problem.
The Technical Reality: Capability Resides with the MNO
Whatever the legal split, the technical capability to intercept communications often resides with the host MNO. This is because the MVNO’s subscribers communicate over the MNO’s radio access network, and their traffic traverses the MNO’s core network infrastructure. The interception points — the network elements where traffic can be captured and duplicated — are typically within the MNO’s domain.
This creates a tension: the entity that holds the subscriber relationship (the MVNO) often lacks the capability, while the host MNO that has the capability may itself be obliged for traffic on its network, as in Germany. Resolving this tension requires either the MVNO to acquire its own technical capability (by deploying its own core network elements and interception infrastructure), or the MNO to provide interception services to the MVNO as part of the wholesale arrangement.
The appropriate solution depends on the MVNO’s architecture. Full MVNOs that operate their own core network have direct control over the interception points and can deploy their own LI systems. Light MVNOs and resellers that rely entirely on the MNO’s infrastructure must depend on the MNO for interception capability, which requires formal agreements and technical arrangements.
The Contractual Dimension
The contract between the MVNO and the MNO is the primary mechanism for bridging the gap between obligation and capability. A well-drafted MVNO agreement will include specific provisions addressing lawful interception, covering the responsibilities of each party, the services that the MNO will provide, the response times and service levels, the technical interfaces and data formats, the cost allocation, and the liability for non-compliance.
In practice, many MVNO agreements are silent on lawful interception or address it only in general terms. This is a significant risk for the MVNO. If the agreement does not explicitly require the MNO to provide interception services, the MVNO may find itself unable to comply with its legal obligations and unable to compel the MNO to assist. Negotiating clear, comprehensive LI provisions should be a priority in any MVNO agreement negotiation.
Key provisions that should be included in the agreement are the scope of interception services provided by the MNO, activation timelines that meet regulatory requirements, data formats and delivery mechanisms for IRI and CC, processes for handling urgent and emergency interception requests, confidentiality obligations for all parties, audit rights enabling the MVNO to verify compliance, liability allocation for failures in the interception process, and procedures for regulatory changes requiring updates to the LI capability.
Models of LI Responsibility Allocation
Several models for allocating LI responsibility between the MVNO and MNO are used in practice. The first is the MNO-performed model, where the MNO performs interception on behalf of the MVNO. The MNO receives the interception order (either directly from law enforcement or via the MVNO), activates the intercept on its network, and delivers the intercepted data to law enforcement. The MVNO provides administrative support and coordinates with law enforcement. This model is common for light MVNOs and resellers and requires a comprehensive agreement with the MNO and validated technical arrangements.
The second model is the MVNO-performed model, where the MVNO deploys its own LI infrastructure — including a mediation function and handover interfaces — and performs interception independently. This model requires the MVNO to have sufficient network infrastructure (typically its own core network elements) to serve as interception points. It gives the MVNO full control over the interception process but requires significant technical investment.
The third model is a hybrid approach, where certain aspects of interception are handled by the MNO and others by the MVNO. For example, the MNO might capture the content (CC) in its network, while the MVNO’s own core elements (such as its IMS) produce the event data (IRI); both streams must then carry the same correlation number so the agency can match them, and the MVNO delivers them to law enforcement through its own mediation platform. This model requires close technical coordination between the MVNO and MNO but can provide a practical balance between capability and control.
Regulatory Expectations and Enforcement
Regulators across Europe have become increasingly attentive to the LI compliance of MVNOs. As the MVNO market has grown and diversified, regulators have recognised that MVNOs cannot be overlooked in the enforcement of interception obligations. Some legislators address this directly: Germany’s TKG, for example, sets specific duties for providers that use another operator’s network (§ 170(2) TKG), making clear that the MVNO’s dependency on the MNO does not remove the MVNO’s own responsibilities.
In enforcement actions, regulators and law enforcement agencies look at whoever holds the specific duty that was breached. In Germany, failing to maintain interception facilities is an administrative offence with fines of up to EUR 500,000 (§ 228 TKG). Contractual recourse against the MNO does not protect an MVNO from sanctions for its own duties.
This underscores the importance of ensuring that the MVNO-MNO arrangement for lawful interception is robust, tested, and documented. An arrangement that works on paper but has not been validated through testing and operational experience provides a false sense of security.
Practical Recommendations
For MVNOs, the practical recommendations are clear. Establish which LI duties are yours under national law and your network architecture, and accept that you can outsource the work but not the responsibility. Review your wholesale agreement and ensure that LI is comprehensively addressed, with clear responsibilities, service levels, and technical specifications. If you rely on the MNO for interception, verify its capability before you sign (in Germany this check is a legal duty under § 170(2) TKG) and test the end-to-end process, including how orders for your subscribers reach the MNO. Maintain your own documentation, audit trails, and operational procedures, even if the MNO performs the technical interception. And invest in understanding the LI landscape in your market, so that you can engage knowledgeably with regulators, law enforcement, and your MNO partner.
Conclusion
The question of MVNO versus MNO responsibility for lawful interception has no single answer: it depends on national law and on which network elements the MVNO operates, and it is rarely as simple as the commercial agreement suggests. Bridging the gap between legal obligation and technical capability requires careful contractual arrangements, validated technical solutions, and proactive engagement with regulators. MVNOs that approach this challenge systematically, with clear agreements and tested infrastructure, will be well positioned to meet their obligations. Those that leave it unaddressed will discover the consequences at the worst possible time — when a law enforcement agency presents an interception order and expects it to be executed.
For MNOs that host MVNOs, the recommendation is equally straightforward: check whether you are yourself obliged for the MVNO traffic on your installation (as in Germany), recognise that your MVNO partners have duties that depend on your technical cooperation, and build this cooperation into your wholesale offering. Providing clear, well-defined LI services to your MVNO partners protects both parties — the MVNO can meet its legal obligations, and the MNO avoids the reputational and practical complications that arise when an MVNO on its network fails to comply with an interception order. A collaborative approach to LI compliance serves the interests of the entire ecosystem — operators, regulators, and law enforcement alike.
The question of MVNO lawful interception responsibility is ultimately a legal one that varies by jurisdiction. Operators must obtain clear legal advice on their MVNO lawful interception obligations in each market.
Related Articles
For further reading on related topics, explore these articles:
- The MVNO LI Checklist: Everything You Need Before Going Live
- How to Handle LI When Your Core Network Is Outsourced or Hosted
- Roaming and Lawful Interception: What Happens When the Target Is Abroad?
External Resources
The following external resources provide additional context and official documentation:
