{"id":2175,"date":"2026-09-02T08:00:00","date_gmt":"2026-09-02T07:00:00","guid":{"rendered":"https:\/\/ic-services.io\/?p=2175"},"modified":"2026-10-21T14:10:16","modified_gmt":"2026-10-21T13:10:16","slug":"mvno-vs-mno-rechtmasige-uberwachung","status":"publish","type":"post","link":"https:\/\/ic-services.io\/de\/resources\/blog\/mvno-vs-mno-lawful-interception\/","title":{"rendered":"MVNO vs. MNO: Wer ist rechtlich verantwortlich f\u00fcr Telekommunikations\u00fcberwachung (TK\u00dc)?"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Vor dem Eintritt in einen Markt ist es unerl\u00e4sslich, die Verantwortlichkeiten von MVNOs im Zusammenhang mit der Telekommunikations\u00fcberwachung zu verstehen. Eine der h\u00e4ufigsten \u2013 und folgenreichsten \u2013 Fragen im MVNO-Gesch\u00e4ftsmodell ist, wer die rechtliche Verantwortung f\u00fcr die Telekommunikations\u00fcberwachung tr\u00e4gt. Die Antwort scheint auf den ersten Blick einfach zu sein, ist in der Praxis jedoch sehr komplex. Die rechtliche Verpflichtung, die technische Leistungsf\u00e4higkeit, die vertraglichen Vereinbarungen und die praktische Umsetzung betreffen h\u00e4ufig sowohl den MVNO als auch den Host-MNO, und die Grenzen zwischen ihren jeweiligen Zust\u00e4ndigkeiten k\u00f6nnen unklar, umstritten oder in den ihre Beziehung regelnden Gesch\u00e4ftsvereinbarungen schlichtweg nicht geregelt sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dieser Artikel bietet eine detaillierte Untersuchung der rechtlichen, technischen und vertraglichen Aspekte der LI-Verantwortung in der Beziehung zwischen MVNO und MNO und st\u00fctzt sich dabei auf die regulatorischen Rahmenbedingungen der wichtigsten europ\u00e4ischen M\u00e4rkte sowie auf die praktischen Erfahrungen von Betreibern, die sich mit diesen Themen auseinandersetzen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verpflichtungen von MVNOs im Zusammenhang mit der Telekommunikations\u00fcberwachung<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For MVNOs that hold their own regulatory registration \u2014 which is the case for most MVNOs operating in European markets \u2014 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&#8217;s network infrastructure does not make compliance the MNO&#8217;s problem alone, but it also does not automatically move every obligation to the MVNO.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">National rules differ on this point. In Germany, \u00a7 170(1) TKG obliges whoever operates the telecommunications installation used to provide the service. A reseller or light MVNO that relies on its host&#8217;s installation must, under \u00a7 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 \u00a7 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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, \u00a7 5(3) TK\u00dcV). The MVNO cannot simply point to the MNO and claim that compliance is the MNO&#8217;s problem.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Die technische Realit\u00e4t: Die Kompetenz liegt beim Mobilfunknetzbetreiber<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Whatever the legal split, the technical capability to intercept communications often resides with the host MNO. This is because the MVNO&#8217;s subscribers communicate over the MNO&#8217;s radio access network, and their traffic traverses the MNO&#8217;s core network infrastructure. The interception points \u2014 the network elements where traffic can be captured and duplicated \u2014 are typically within the MNO&#8217;s domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die geeignete L\u00f6sung h\u00e4ngt von der Architektur des MVNO ab. Vollst\u00e4ndige MVNOs, die ein eigenes Kernnetz betreiben, haben direkte Kontrolle \u00fcber die Ausleitungspunkte und k\u00f6nnen ihre eigenen LI-Systeme einsetzen. Light-MVNOs und Wiederverk\u00e4ufer, die vollst\u00e4ndig auf die Infrastruktur des MNO angewiesen sind, m\u00fcssen sich in dieser Hinsicht auf den MNO verlassen. <a href=\"https:\/\/ic-services.io\/de\/losungen\/lawful-interception\/\">\u00dcberwachungsf\u00e4higkeit<\/a>, wof\u00fcr formelle Vereinbarungen und technische Vorkehrungen erforderlich sind.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Die vertragliche Dimension<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Der Vertrag zwischen dem MVNO und dem MNO ist das wichtigste Instrument, um die L\u00fccke zwischen Verpflichtung und Leistungsf\u00e4higkeit zu schlie\u00dfen. Eine gut ausgearbeitete MVNO-Vereinbarung enth\u00e4lt konkrete Bestimmungen zur Telekommunikations\u00fcberwachung, in denen die Verantwortlichkeiten der einzelnen Parteien, die vom MNO zu erbringenden Dienstleistungen, die Reaktionszeiten und Servicelevels, die technischen Schnittstellen und Datenformate, die Kostenverteilung sowie die Haftung bei Nichteinhaltung geregelt sind.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In der Praxis enthalten viele MVNO-Vertr\u00e4ge keine Bestimmungen zur Telekommunikations\u00fcberwachung oder behandeln dieses Thema nur in allgemeiner Form. Dies stellt ein erhebliches Risiko f\u00fcr den MVNO dar. Wenn der Vertrag den MNO nicht ausdr\u00fccklich zur Bereitstellung von \u00dcberwachungsdiensten verpflichtet, kann es sein, dass der MVNO seinen gesetzlichen Verpflichtungen nicht nachkommen kann und den MNO nicht zur Unterst\u00fctzung verpflichten kann. Die Aushandlung klarer, umfassender Bestimmungen zur Telekommunikations\u00fcberwachung sollte bei jeder Verhandlung eines MVNO-Vertrags Priorit\u00e4t haben.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zu den wichtigsten Bestimmungen, die in der Vereinbarung enthalten sein sollten, geh\u00f6ren der Umfang der vom Mobilfunknetzbetreiber erbrachten \u00dcberwachungsdienste, Aktivierungsfristen, die den beh\u00f6rdlichen Anforderungen entsprechen, Datenformate und \u00dcbermittlungsmechanismen f\u00fcr IRI und CC, Verfahren zur Bearbeitung dringender und notfallbezogener TK\u00dc-Anfragen, Vertraulichkeitsverpflichtungen f\u00fcr alle Parteien, Pr\u00fcfungsrechte, die es dem MVNO erm\u00f6glichen, die Einhaltung der Vorschriften zu \u00fcberpr\u00fcfen, die Haftungszuweisung bei Fehlern im TK\u00dc-Prozess sowie Verfahren f\u00fcr regulatorische \u00c4nderungen, die Aktualisierungen der LI-F\u00e4higkeit erfordern.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Modelle zur Zuweisung der Verantwortung im Bereich LI<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In der Praxis kommen verschiedene Modelle zur Aufteilung der Verantwortung f\u00fcr die \u00dcberwachung zwischen dem MVNO und dem MNO zum Einsatz. Das erste ist das vom MNO durchgef\u00fchrte Modell, bei dem der MNO die \u00dcberwachung im Auftrag des MVNO durchf\u00fchrt. Der MNO erh\u00e4lt den \u00dcberwachungsbefehl (entweder direkt von den Strafverfolgungsbeh\u00f6rden oder \u00fcber den MVNO), aktiviert die \u00dcberwachung in seinem Netz und \u00fcbermittelt die \u00fcberwachten Daten an die Strafverfolgungsbeh\u00f6rden. Der MVNO leistet administrative Unterst\u00fctzung und koordiniert die Ma\u00dfnahmen mit den Strafverfolgungsbeh\u00f6rden. Dieses Modell ist bei \u201eLight\u201c-MVNOs und Wiederverk\u00e4ufern \u00fcblich und erfordert eine umfassende Vereinbarung mit dem MNO sowie validierte technische Vorkehrungen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das zweite Modell ist das vom MVNO durchgef\u00fchrte Modell, bei dem der MVNO seine eigene LI-Infrastruktur \u2013 einschlie\u00dflich einer Vermittlungsfunktion und \u00dcbergabeschnittstellen \u2013 einrichtet und die \u00dcberwachung eigenst\u00e4ndig durchf\u00fchrt. Dieses Modell setzt voraus, dass der MVNO \u00fcber eine ausreichende Netzinfrastruktur (in der Regel eigene Kernnetzelemente) verf\u00fcgt, die als Ausleitungspunkte dienen k\u00f6nnen. Es gew\u00e4hrt dem MVNO die volle Kontrolle \u00fcber den TK\u00dc-Prozess, erfordert jedoch erhebliche technische Investitionen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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&#8217;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 <a href=\"https:\/\/ic-services.io\/de\/produkte\/softwarelosungen\/li-vermittlungsplattform\/\">Mediationsplattform<\/a>. Dieses Modell erfordert eine enge technische Abstimmung zwischen dem MVNO und dem MNO, kann jedoch ein ausgewogenes Verh\u00e4ltnis zwischen Leistungsf\u00e4higkeit und Kontrolle gew\u00e4hrleisten.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Regulatorische Erwartungen und Durchsetzung<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Die Aufsichtsbeh\u00f6rden in ganz Europa widmen dem Thema zunehmend Aufmerksamkeit. <a href=\"https:\/\/ic-services.io\/de\/dienstleistungen\/managed-li-operations\/\">Einhaltung der LI-Vorschriften<\/a> 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&#8217;s TKG, for example, sets specific duties for providers that use another operator&#8217;s network (\u00a7 170(2) TKG), making clear that the MVNO&#8217;s dependency on the MNO does not remove the MVNO&#8217;s own responsibilities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei Durchsetzungsma\u00dfnahmen gehen die Aufsichtsbeh\u00f6rden und <a href=\"https:\/\/ic-services.io\/de\/losungen\/uberwachung-durch-die-strafverfolgungsbehorden\/\">Strafverfolgungsbeh\u00f6rden<\/a> 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 (\u00a7 228 TKG). Contractual recourse against the MNO does not protect an MVNO from sanctions for its own duties.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dies unterstreicht, wie wichtig es ist, sicherzustellen, dass die Vereinbarung zwischen MVNO und MNO zur Telekommunikations\u00fcberwachung robust, erprobt und dokumentiert ist. Eine Vereinbarung, die auf dem Papier funktioniert, aber nicht durch Tests und praktische Erfahrungen validiert wurde, vermittelt ein falsches Gef\u00fchl der Sicherheit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Praktische Empfehlungen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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 \u00a7 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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Schlussfolgerung<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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 \u2014 when a law enforcement agency presents an interception order and expects it to be executed.<\/p>\n\n\n<p class=\"wp-block-paragraph\">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 \u2014 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 \u2014 operators, regulators, and law enforcement alike.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die Frage nach der Verantwortung von MVNOs im Hinblick auf die Telekommunikations\u00fcberwachung ist letztlich eine rechtliche Frage, die je nach Rechtsordnung unterschiedlich geregelt ist. Die Betreiber m\u00fcssen sich in jedem Markt eindeutig rechtlich beraten lassen, welche Verpflichtungen ihnen als MVNOs im Zusammenhang mit der Telekommunikations\u00fcberwachung obliegen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verwandte Artikel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Weitere Informationen zu verwandten Themen finden Sie in diesen Artikeln:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/ic-services.io\/de\/?p=2173\">Die MVNO LI-Checkliste: Alles, was Sie vor dem Going Live brauchen<\/a><\/li>\n<li><a href=\"https:\/\/ic-services.io\/de\/?p=2177\">So gehen Sie mit LI um, wenn Ihr Kernnetzwerk ausgelagert oder gehostet wird<\/a><\/li>\n<li><a href=\"https:\/\/ic-services.io\/de\/?p=2181\">Roaming und Telekommunikations\u00fcberwachung: Was passiert, wenn sich die Zielperson im Ausland befindet?<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Externe Ressourcen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Die folgenden externen Quellen bieten zus\u00e4tzlichen Kontext und offizielle Dokumentation:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32018L1972\" target=\"_blank\" rel=\"noopener noreferrer\">Europ\u00e4ischer Kodex f\u00fcr elektronische Kommunikation (EECC)<\/a><\/li>\n<li><a href=\"https:\/\/www.etsi.org\/technologies\/lawful-interception\" target=\"_blank\" rel=\"noopener noreferrer\">ETSI-Normen f\u00fcr Telekommunikations\u00fcberwachung (TK\u00dc)<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Understanding MVNO lawful interception responsibilities is essential before entering any market. One of the most common \u2014 and most consequential [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":2543,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[8],"tags":[],"class_list":["post-2175","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry-use-cases"],"uagb_featured_image_src":{"full":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception.jpg",1600,1067,false],"thumbnail":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-150x150.jpg",150,150,true],"medium":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-300x200.jpg",300,200,true],"medium_large":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-768x512.jpg",768,512,true],"large":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-1024x683.jpg",1024,683,true],"1536x1536":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-1536x1024.jpg",1536,1024,true],"2048x2048":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception.jpg",1600,1067,false],"trp-custom-language-flag":["https:\/\/ic-services.io\/wp-content\/uploads\/2026\/09\/mvno-vs-mno-lawful-interception-18x12.jpg",18,12,true]},"uagb_author_info":{"display_name":"David Son","author_link":"https:\/\/ic-services.io\/de\/author\/david\/"},"uagb_comment_info":0,"uagb_excerpt":"Understanding MVNO lawful interception responsibilities is essential before entering any market. One of the most common \u2014 and most consequential [&hellip;]","_links":{"self":[{"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/posts\/2175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/comments?post=2175"}],"version-history":[{"count":7,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/posts\/2175\/revisions"}],"predecessor-version":[{"id":2687,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/posts\/2175\/revisions\/2687"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/media\/2543"}],"wp:attachment":[{"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/media?parent=2175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/categories?post=2175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ic-services.io\/de\/wp-json\/wp\/v2\/tags?post=2175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}