Telecommunications info - Revision history

Paul: updated 103 120 scope

2026-04-16T13:55:13Z

updated 103 120 scope

← Older revision		Revision as of 08:55, 16 April 2026
Line 266:		Line 266:
	\| ETSI TS 103 707 \|\| Lawful Interception (LI); Handover for messaging services over HTTP/XML \|\| Document specifies the handover details to deliver messaging services for LI over HTTP/XML		\| ETSI TS 103 707 \|\| Lawful Interception (LI); Handover for messaging services over HTTP/XML \|\| Document specifies the handover details to deliver messaging services for LI over HTTP/XML
	\|-		\|-
	\| ETSI TS 103 120 \|\| Lawful Interception (LI); Interface for warrant information \|\| Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.		\| ETSI TS 103 120 \|\| Lawful Interception (LI); Interface for warrant information \|\| Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception. Typically this interface would be used between on one side, a Communications Service Provider and on the other side, a Government or Law Enforcement Agency who is entitled to request a lawful action.

			The present document is a specific and detailed example of one particular Warrantry interface for eWarrants.

			The ETSI reference model for LI (ETSI TS 102 232-1) defines three interfaces between law enforcement and
			CSPs, called HI-1, HI-2 and HI-3. The protocol defined in the present document is designed to provide a large part of
			the functionality for HI-1. It is not designed to be used for HI-2 (delivery of intercept related information) or HI-3
			(delivery of communications content). The protocol designed in the present document may also be used for interfaces
			which require structured exchange of information relating to the establishment and management of Lawful Interception.
			The general view is that the HI-1 concept can also be used for other legal actions than LI. For that reason, the present document could, besides LI, also be applied for retained data requests, seized data requests, data preservation orders and other similar legal requests.
	\|-		\|-
	\| ETSI TS 104 144 \|\| Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers \|\| Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.		\| ETSI TS 104 144 \|\| Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers \|\| Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.

Paul: updated 102 656 and 102 657 scopes

2026-04-16T13:51:16Z

updated 102 656 and 102 657 scopes

@@ Line 242: / Line 242: @@
 | style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
 |-
-| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data ||
+| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data || Document gives guidance for the delivery and associated issues of retained data of telecommunications and subscribers. It provides a set of requirements relating to handover interfaces for the retained traffic data and subscriber data by law enforcement and other authorized requesting authorities.
 |-
-| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data  ||
+| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data  || Document is based on requirements from ETSI TS 102 656.
 |-
 | ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.

Paul: added 104 144

2026-02-03T17:43:42Z

added 104 144

← Older revision		Revision as of 12:43, 3 February 2026
Line 251:		Line 251:
	\|-		\|-
	\| ETSI TS 103 120 \|\| Lawful Interception (LI); Interface for warrant information \|\| Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.		\| ETSI TS 103 120 \|\| Lawful Interception (LI); Interface for warrant information \|\| Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
			\|-
			\| ETSI TS 104 144 \|\| Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers \|\| Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.
	\|-		\|-
	\| ETSI TS 103 280 \|\| Lawful Interception (LI); Dictionary for common parameters \|\| Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]		\| ETSI TS 103 280 \|\| Lawful Interception (LI); Dictionary for common parameters \|\| Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]

Paul: /* Case Examples */

2025-11-28T17:20:23Z

Case Examples

← Older revision		Revision as of 12:20, 28 November 2025
Line 342:		Line 342:
	== Case Examples ==		== Case Examples ==

	[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later. ~~Why?~~		[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later.

Paul: added case examples

2025-11-28T16:21:31Z

added case examples

← Older revision		Revision as of 11:21, 28 November 2025
Line 339:		Line 339:

	[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]		[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

			== Case Examples ==

			[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later. Why?

Paul: /* National Requirements Resources */

2025-08-06T19:17:45Z

National Requirements Resources

← Older revision		Revision as of 14:17, 6 August 2025
Line 338:		Line 338:
	== National Requirements Resources ==		== National Requirements Resources ==

	[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications~~/Companies~~/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]		[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

Paul: Added link to My 3GPP 23.401 notes

2025-05-14T20:58:08Z

Added link to My 3GPP 23.401 notes

← Older revision		Revision as of 15:58, 14 May 2025
Line 67:		Line 67:
	\|\| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).		\|\| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
	The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.		The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

			[[My 3GPP 23.401 Notes]]
	\|-		\|-
	\| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] \|\| 3rd Generation Partnership Project;		\| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] \|\| 3rd Generation Partnership Project;
Line 72:		Line 74:
	System architecture for the 5G System (5GS);		System architecture for the 5G System (5GS);
	Stage 2		Stage 2
	\|\| 5G core network [[My 3GPP 23.501 Notes]]		\|\| 5G core network

			[[My 3GPP 23.501 Notes]]
	\|-		\|-
	\| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] \|\| 3rd Generation Partnership Project;		\| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] \|\| 3rd Generation Partnership Project;

Paul: /* Lawful Interception or Related Standards */

2025-03-12T21:31:32Z

Lawful Interception or Related Standards

← Older revision		Revision as of 16:31, 12 March 2025
Line 230:		Line 230:
	\| ETSI TS 103 643 \|\| Techniques for assurance of digital material used in legal proceedings \|\|		\| ETSI TS 103 643 \|\| Techniques for assurance of digital material used in legal proceedings \|\|
	\|-		\|-
	\| ETSI TS 101 671 & ETSI ES 201 671 \|\| Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic \|\| Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service. Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331. Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.		\| ETSI TS 101 671 & ETSI ES 201 671 \|\| Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic \|\| Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
			* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
			* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
	\|-		\|-
	\| ETSI TS 103 462 \|\| Lawful Interception (LI); Inter LEMF Handover Interface \|\|		\| ETSI TS 103 462 \|\| Lawful Interception (LI); Inter LEMF Handover Interface \|\|

Paul: /* Lawful Interception or Related Standards */

2025-03-12T21:29:40Z

Lawful Interception or Related Standards

← Older revision		Revision as of 16:29, 12 March 2025
Line 230:		Line 230:
	\| ETSI TS 103 643 \|\| Techniques for assurance of digital material used in legal proceedings \|\|		\| ETSI TS 103 643 \|\| Techniques for assurance of digital material used in legal proceedings \|\|
	\|-		\|-
	\| ETSI TS 101 671 \|\| Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic \|\| Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service. Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331. Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.		\| ETSI TS 101 671 & ETSI ES 201 671 \|\| Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic \|\| Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service. Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331. Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
	\|-		\|-
	\| ETSI TS 103 462 \|\| Lawful Interception (LI); Inter LEMF Handover Interface \|\|		\| ETSI TS 103 462 \|\| Lawful Interception (LI); Inter LEMF Handover Interface \|\|

Paul: /* Lawful Interception or Related Standards */

2024-03-25T17:58:54Z

Lawful Interception or Related Standards

← Older revision		Revision as of 12:58, 25 March 2024
Line 196:		Line 196:
	* specifies protocols for the transfer of IRI and CC across the handover interfaces;		* specifies protocols for the transfer of IRI and CC across the handover interfaces;
	* specifies protocol profiles for the handover interface.		* specifies protocol profiles for the handover interface.

			[[My 102 232-1 notes]]
	\|-		\|-
	\| ETSI TS 102 232-2 \|\| Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services \|\| This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.		\| ETSI TS 102 232-2 \|\| Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services \|\| This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.