My 33.127 Notes - Revision history

Paul: /* 7.3.4 Cell database information reporting */

2024-04-27T18:50:33Z

7.3.4 Cell database information reporting

← Older revision		Revision as of 13:50, 27 April 2024
Line 159:		Line 159:
	=== 7.3.4 Cell database information reporting ===		=== 7.3.4 Cell database information reporting ===

	When a cell identity is provided for the target's location in IRI, the Communication Service Provider (CSP) may also provide Cell ~~Site~~ Information (CSI) for the reported cell identity. The MDF2 may retrieve CSI by access to a CSP maintained database (referred to as CSP Cell Database) as shown in figure 7.3.4-1. When using CSI ~~supplemental~~ reporting and the CSP cannot deliver via IRI messages generated from the xIRI, the MDF2 shall generate a Cell Site Report (CSR) for location information specific to the cell identity reported.		When a cell identity is provided for the target's location in IRI, the Communication Service Provider (CSP) may also provide Cell Supplemental Information (CSI) for the reported cell identity. The MDF2 may retrieve CSI by access to a CSP maintained database (referred to as CSP Cell Database) as shown in figure 7.3.4-1. When using CSI reporting and the CSP cannot deliver via IRI messages generated from the xIRI, the MDF2 shall generate a Cell Site Report (CSR) for location information specific to the cell identity reported.

	The following information shall be delivered when CSI is provided in IRI or a MDF2 generated CSR:		The following information shall be delivered when CSI is provided in IRI or a MDF2 generated CSR:

Paul: /* 7.7 Identity Caching Function */

2023-01-24T17:06:40Z

7.7 Identity Caching Function

← Older revision		Revision as of 12:06, 24 January 2023
Line 152:		Line 152:

	The ICF shall support immediate deletion of identifier associations received in events for one or more IEF(s) when requested to do so by the LICF (proxied by the LIPF) over LI_XEM1.		The ICF shall support immediate deletion of identifier associations received in events for one or more IEF(s) when requested to do so by the LICF (proxied by the LIPF) over LI_XEM1.

			== 7.3 Location of 7 Service layer based interception ==

			From 3GPP TS 33.127 V16.0.0 (2019-06)

			=== 7.3.4 Cell database information reporting ===

			When a cell identity is provided for the target's location in IRI, the Communication Service Provider (CSP) may also provide Cell Site Information (CSI) for the reported cell identity. The MDF2 may retrieve CSI by access to a CSP maintained database (referred to as CSP Cell Database) as shown in figure 7.3.4-1. When using CSI supplemental reporting and the CSP cannot deliver via IRI messages generated from the xIRI, the MDF2 shall generate a Cell Site Report (CSR) for location information specific to the cell identity reported.

			The following information shall be delivered when CSI is provided in IRI or a MDF2 generated CSR:
			* LIID.
			* Cell identity.
			* Date/time(s) established by MDF2.
			* Cell supplemental information.

			If CSI for a cell identity has been previously reported to the LEMF for the current interception, and if allowed by CSP-LEA mutual agreement, the CSP may not need to resend this specific CSI, unless it has changed.

			If the CSP does not support CSR or CSI, the database can be provided by non-real-time means.

	== 7.7 Identity Caching Function ==		== 7.7 Identity Caching Function ==

Paul: /* 5.7 Identifier association and reporting */

2023-01-24T17:00:29Z

5.7 Identifier association and reporting

← Older revision		Revision as of 12:00, 24 January 2023
Line 76:		Line 76:

	== 5.7 Identifier association and reporting ==		== 5.7 Identifier association and reporting ==

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	=== 5.7.1 General ===		=== 5.7.1 General ===

Paul: /* 5.4.17 Lawful Interception Internal Event Management 1 (LI_XEM1) Interface */

2023-01-24T16:59:39Z

5.4.17 Lawful Interception Internal Event Management 1 (LI_XEM1) Interface

← Older revision		Revision as of 11:59, 24 January 2023
Line 68:		Line 68:

	=== 5.4.17 Lawful Interception Internal Event Management 1 (LI_XEM1) Interface ===		=== 5.4.17 Lawful Interception Internal Event Management 1 (LI_XEM1) Interface ===

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	The LI_XEM1 interface is used by the LICF (proxied by the LIPF) to manage and control the activation state of the IEF(s) and ICF.		The LI_XEM1 interface is used by the LICF (proxied by the LIPF) to manage and control the activation state of the IEF(s) and ICF.

Paul: /* 5.4.16 Lawful Interception Internal Event Record (LI_XER) Interface */

2023-01-24T16:59:24Z

5.4.16 Lawful Interception Internal Event Record (LI_XER) Interface

← Older revision		Revision as of 11:59, 24 January 2023
Line 56:		Line 56:

	=== 5.4.16 Lawful Interception Internal Event Record (LI_XER) Interface ===		=== 5.4.16 Lawful Interception Internal Event Record (LI_XER) Interface ===

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	The Lawful Interception Internal Event Record (LI_XER) interface is used by the IEF to send identifier association events to the ICF.		The Lawful Interception Internal Event Record (LI_XER) interface is used by the IEF to send identifier association events to the ICF.

Paul: /* 5.4.15 Lawful Interception Handover Interface Query Response (LI_HIQR) Interface */

2023-01-24T16:59:09Z

5.4.15 Lawful Interception Handover Interface Query Response (LI_HIQR) Interface

← Older revision		Revision as of 11:59, 24 January 2023
Line 33:		Line 33:

	=== 5.4.15 Lawful Interception Handover Interface Query Response (LI_HIQR) Interface ===		=== 5.4.15 Lawful Interception Handover Interface Query Response (LI_HIQR) Interface ===

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	The Lawful Interception Handover Interface Query Response (LI_HIQR) interface is used by the Law Enforcement Agency (LEA) to send identifier association queries to the IQF and from the IQF to return identities associations to the LEA in response.		The Lawful Interception Handover Interface Query Response (LI_HIQR) interface is used by the Law Enforcement Agency (LEA) to send identifier association queries to the IQF and from the IQF to return identities associations to the LEA in response.

Paul: /* 5.4.14 Lawful Interception Internal Query Response (LI_XQR) */

2023-01-24T16:58:55Z

5.4.14 Lawful Interception Internal Query Response (LI_XQR)

← Older revision		Revision as of 11:58, 24 January 2023
Line 10:		Line 10:

	=== 5.4.14 Lawful Interception Internal Query Response (LI_XQR) ===		=== 5.4.14 Lawful Interception Internal Query Response (LI_XQR) ===

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	The LI_XQR interface is used by the IQF to send identifier association queries to the ICF and from the ICF to return identities associations to the IQF in response.		The LI_XQR interface is used by the IQF to send identifier association queries to the ICF and from the ICF to return identities associations to the IQF in response.

Paul: /* 5.4.13 Lawful Interception Identity Query Function (LI_IQF) Interface */

2023-01-24T16:58:36Z

5.4.13 Lawful Interception Identity Query Function (LI_IQF) Interface

← Older revision		Revision as of 11:58, 24 January 2023
Line 2:		Line 2:

	=== 5.4.13 Lawful Interception Identity Query Function (LI_IQF) Interface ===		=== 5.4.13 Lawful Interception Identity Query Function (LI_IQF) Interface ===

			Added in 3GPP TS 33.127 V16.6.0 (2020-12)

	LI_IQF is an interface between Lawful Interception Control Function (LICF) and Identity Query Function (IQF) and is used by the LICF to send management information related to Identity Event Functions (IEFs) and Identity Caching Function (ICF), to the IQF.		LI_IQF is an interface between Lawful Interception Control Function (LICF) and Identity Query Function (IQF) and is used by the LICF to send management information related to Identity Event Functions (IEFs) and Identity Caching Function (ICF), to the IQF.

Paul: /* 5.7.2.1 Identity Query Function (IQF) */

2022-11-16T18:34:58Z

5.7.2.1 Identity Query Function (IQF)

← Older revision		Revision as of 13:34, 16 November 2022
Line 98:		Line 98:
	==== 5.7.2.1 Identity Query Function (IQF) ====		==== 5.7.2.1 Identity Query Function (IQF) ====
	The IQF is the function responsible for receiving and responding to dedicated LEA real-time queries for identifier associations. The IQF is a sub-function of the ADMF.		The IQF is the function responsible for receiving and responding to dedicated LEA real-time queries for identifier associations. The IQF is a sub-function of the ADMF.
	On receiving a valid query, the IQF shall query the ICF in order to obtain the required mapped identities. The IQF shall be able to support both association from permanent identifiers to temporary identifiers and from temporary identifiers to permanent identifiers.		On receiving a valid query, the IQF shall query the ICF in order to obtain the required mapped identities. <span style="color:red">The IQF shall be able to support both association from permanent identifiers to temporary identifiers and from temporary identifiers to permanent identifiers.</span>

	:NOTE 1: Only queries based on applicable subscription permanent identifiers or associated temporary identifiers are supported by the present document. Queries based on ME hardware identifiers or communications services identifiers (e.g. E.164 numbers) are not supported by the IQF.		:NOTE 1: Only queries based on applicable subscription permanent identifiers or associated temporary identifiers are supported by the present document. Queries based on ME hardware identifiers or communications services identifiers (e.g. E.164 numbers) are not supported by the IQF.

Paul: /* 7.7.2 ICF Query Identities */

2022-09-30T18:58:58Z

7.7.2 ICF Query Identities

← Older revision		Revision as of 13:58, 30 September 2022
Line 155:		Line 155:
	:NOTE: Targeting based on GPSI, PEI, IMS identifiers or other legacy identifiers (e.g. MSISDN) is not supported by the present document.		:NOTE: Targeting based on GPSI, PEI, IMS identifiers or other legacy identifiers (e.g. MSISDN) is not supported by the present document.

	The list of event parameters is specified in TS 33.128 ~~[15]~~. Each event shall include at the minimum the following information:		The list of event parameters is specified in TS 33.128. Each event shall include at the minimum the following information:
	* Query target identifier.		* Query target identifier.
	* Time of target identifier observation.		* Time of target identifier observation.