{"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":"interceptacion-legal-mvno-frente-a-mno","status":"publish","type":"post","link":"https:\/\/ic-services.io\/es\/resources\/blog\/mvno-vs-mno-lawful-interception\/","title":{"rendered":"OMV vs. OMR: \u00bfQui\u00e9n es legalmente responsable de la interceptaci\u00f3n legal?"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Es fundamental comprender las responsabilidades de los MVNO en materia de interceptaci\u00f3n legal antes de entrar en cualquier mercado. Una de las cuestiones m\u00e1s habituales \u2014y con mayores consecuencias\u2014 en el modelo de negocio de los MVNO es qui\u00e9n asume la responsabilidad legal de la interceptaci\u00f3n legal. La respuesta parece sencilla a primera vista, pero en la pr\u00e1ctica presenta numerosas complejidades. La obligaci\u00f3n legal, la capacidad t\u00e9cnica, los acuerdos contractuales y la ejecuci\u00f3n pr\u00e1ctica suelen implicar tanto al MVNO como al MNO anfitri\u00f3n, y los l\u00edmites entre sus respectivas responsabilidades pueden ser poco claros, objeto de controversia o, simplemente, no estar contemplados en los acuerdos comerciales que rigen su relaci\u00f3n.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Este art\u00edculo ofrece un an\u00e1lisis detallado de los aspectos jur\u00eddicos, t\u00e9cnicos y contractuales de la responsabilidad de LI en la relaci\u00f3n entre los operadores m\u00f3viles virtuales (OMV) y los operadores de red m\u00f3vil (ORM), bas\u00e1ndose en los marcos normativos de los principales mercados europeos y en la experiencia pr\u00e1ctica de los operadores que se enfrentan a estas cuestiones.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Responsabilidades de los operadores m\u00f3viles virtuales (MVNO) en materia de interceptaci\u00f3n legal<\/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\">La realidad t\u00e9cnica: la capacidad recae en el operador de telefon\u00eda m\u00f3vil<\/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\">La soluci\u00f3n adecuada depende de la arquitectura del MVNO. Los MVNO completos, que gestionan su propia red central, tienen control directo sobre los puntos de interceptaci\u00f3n y pueden implementar sus propios sistemas de LI. Los MVNO ligeros y los revendedores, que dependen por completo de la infraestructura del MNO, deben recurrir al MNO para <a href=\"https:\/\/ic-services.io\/es\/soluciones\/interceptacion-legal\/\">capacidad de interceptaci\u00f3n<\/a>, lo que requiere acuerdos formales y disposiciones t\u00e9cnicas.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">La dimensi\u00f3n contractual<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">El contrato entre el operador m\u00f3vil virtual (MVNO) y el operador de red m\u00f3vil (MNO) es el mecanismo principal para salvar la brecha entre las obligaciones y las capacidades. Un acuerdo de operador m\u00f3vil virtual (OMV) bien redactado incluir\u00e1 disposiciones espec\u00edficas relativas a la interceptaci\u00f3n legal, en las que se recojan las responsabilidades de cada parte, los servicios que prestar\u00e1 el operador de red m\u00f3vil (OMN), los tiempos de respuesta y los niveles de servicio, las interfaces t\u00e9cnicas y los formatos de datos, la distribuci\u00f3n de costes y la responsabilidad en caso de incumplimiento.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">En la pr\u00e1ctica, muchos acuerdos de operador m\u00f3vil virtual (OMV) no hacen referencia alguna a la interceptaci\u00f3n legal o la abordan \u00fanicamente en t\u00e9rminos generales. Esto supone un riesgo significativo para el OMV. Si el acuerdo no exige expl\u00edcitamente al operador de red m\u00f3vil (ORM) que preste servicios de interceptaci\u00f3n, el OMV podr\u00eda verse incapaz de cumplir con sus obligaciones legales y de obligar al ORM a prestarle asistencia. La negociaci\u00f3n de cl\u00e1usulas claras y exhaustivas sobre la interceptaci\u00f3n legal debe ser una prioridad en cualquier negociaci\u00f3n de un acuerdo de operador m\u00f3vil virtual (MVNO).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Las disposiciones clave que deben incluirse en el acuerdo son: el alcance de los servicios de interceptaci\u00f3n prestados por el operador de red m\u00f3vil (MNO), los plazos de activaci\u00f3n que cumplan los requisitos normativos, los formatos de datos y los mecanismos de entrega de la IRI y el CC, los procesos para gestionar las solicitudes de interceptaci\u00f3n urgentes y de emergencia, las obligaciones de confidencialidad de todas las partes, los derechos de auditor\u00eda que permitan al operador m\u00f3vil virtual (MVNO) verificar el cumplimiento, la atribuci\u00f3n de responsabilidad por fallos en el proceso de interceptaci\u00f3n y los procedimientos para los cambios normativos que requieran actualizaciones de la capacidad de interceptaci\u00f3n (LI).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Modelos de asignaci\u00f3n de responsabilidades en el LI<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">En la pr\u00e1ctica se utilizan varios modelos para distribuir la responsabilidad de la interceptaci\u00f3n entre el MVNO y el MNO. El primero es el modelo en el que act\u00faa el MNO, en el que este lleva a cabo la interceptaci\u00f3n en nombre del MVNO. El MNO recibe la orden de interceptaci\u00f3n (ya sea directamente de las fuerzas del orden o a trav\u00e9s del MVNO), activa la interceptaci\u00f3n en su red y entrega los datos interceptados a las fuerzas del orden. El operador m\u00f3vil virtual (OMV) proporciona apoyo administrativo y coordina la actuaci\u00f3n con las fuerzas del orden. Este modelo es habitual entre los OMV de bajo perfil y los revendedores, y requiere un acuerdo exhaustivo con el operador de red m\u00f3vil (OMN) y disposiciones t\u00e9cnicas validadas.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">El segundo modelo es el modelo gestionado por el MVNO, en el que el MVNO despliega su propia infraestructura de LI \u2014incluida una funci\u00f3n de mediaci\u00f3n e interfaces de traspaso\u2014 y lleva a cabo la interceptaci\u00f3n de forma independiente. Este modelo requiere que el MVNO cuente con una infraestructura de red suficiente (normalmente sus propios elementos de red central) para que estos act\u00faen como puntos de interceptaci\u00f3n. Otorga al MVNO un control total sobre el proceso de interceptaci\u00f3n, pero exige una importante inversi\u00f3n t\u00e9cnica.<\/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\/es\/productos\/soluciones-de-software\/li-plataforma-de-mediacion\/\">plataforma de mediaci\u00f3n<\/a>. Este modelo requiere una estrecha coordinaci\u00f3n t\u00e9cnica entre el operador m\u00f3vil virtual (MVNO) y el operador de red m\u00f3vil (MNO), pero puede ofrecer un equilibrio pr\u00e1ctico entre capacidad y control.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Expectativas normativas y aplicaci\u00f3n de la normativa<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Las autoridades reguladoras de toda Europa prestan cada vez m\u00e1s atenci\u00f3n a la <a href=\"https:\/\/ic-services.io\/es\/servicios\/operaciones-li-gestionadas\/\">Cumplimiento de la normativa LI<\/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\">En las medidas coercitivas, las autoridades reguladoras y <a href=\"https:\/\/ic-services.io\/es\/soluciones\/supervision-de-las-fuerzas-del-orden\/\">fuerzas del orden<\/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\">Esto pone de relieve la importancia de garantizar que el acuerdo entre el operador m\u00f3vil virtual (OMV) y el operador de red m\u00f3vil (ORM) para la interceptaci\u00f3n legal sea s\u00f3lido, haya sido probado y est\u00e9 documentado. Un acuerdo que funcione sobre el papel, pero que no haya sido validado mediante pruebas y experiencia operativa, ofrece una falsa sensaci\u00f3n de seguridad.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Recomendaciones pr\u00e1cticas<\/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\">Conclusi\u00f3n<\/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\">La cuesti\u00f3n de la responsabilidad de los MVNO en materia de interceptaci\u00f3n legal es, en \u00faltima instancia, una cuesti\u00f3n jur\u00eddica que var\u00eda seg\u00fan la jurisdicci\u00f3n. Los operadores deben obtener un asesoramiento jur\u00eddico claro sobre sus obligaciones en materia de interceptaci\u00f3n legal como MVNO en cada mercado.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Art\u00edculos relacionados<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Si desea leer m\u00e1s sobre temas relacionados, consulte estos art\u00edculos:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/ic-services.io\/es\/?p=2173\">La lista de control del OMV LI: Todo lo que necesita antes de lanzarse<\/a><\/li>\n<li><a href=\"https:\/\/ic-services.io\/es\/?p=2177\">C\u00f3mo gestionar LI cuando la red central est\u00e1 externalizada o alojada en un servidor externo<\/a><\/li>\n<li><a href=\"https:\/\/ic-services.io\/es\/?p=2181\">Itinerancia e interceptaci\u00f3n legal: \u00bfqu\u00e9 ocurre cuando el objetivo se encuentra en el extranjero?<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Recursos externos<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Los siguientes recursos externos proporcionan contexto adicional y documentaci\u00f3n oficial:<\/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\">C\u00f3digo Europeo de Comunicaciones Electr\u00f3nicas (EECC)<\/a><\/li>\n<li><a href=\"https:\/\/www.etsi.org\/technologies\/lawful-interception\" target=\"_blank\" rel=\"noopener noreferrer\">Normas de interceptaci\u00f3n legal del ETSI<\/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\/es\/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\/es\/wp-json\/wp\/v2\/posts\/2175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/comments?post=2175"}],"version-history":[{"count":7,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/posts\/2175\/revisions"}],"predecessor-version":[{"id":2687,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/posts\/2175\/revisions\/2687"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/media\/2543"}],"wp:attachment":[{"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/media?parent=2175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/categories?post=2175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ic-services.io\/es\/wp-json\/wp\/v2\/tags?post=2175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}