Editing My 33.127 Notes (section)

=== 5.7.1	General ===
3GPP networks use temporary identifiers in place of permanent identifiers to ensure that identities which are visible on exposed interfaces (e.g. RAN) cannot be used to track or degrade the privacy of a subscriber. For LI purposes, CSPs are required to be able to provide real-time association between temporary and permanent identifiers where the use of such identifier associations impact the ability of the LEA to uniquely identify the UE, subscriber or true permanent identifiers associated with a service.

33.127 defines two sets of capabilities which allow CSPs to report such association to LEAs:
* Real-time reporting of associations as observed by POIs as part of network access, target communications and service usage.
* Dedicated real-time query, lookup and reporting of identifier associations.

For real-time reporting based on POI observation, associations are reported through a combination of dedicated event records sent from the POI to the MDF over LI_X2 and through inclusion of specific parameters in other communications service records reported over LI_X2.

For dedicated query, lookup and reporting, the following figure shows the high-level architecture used to support identifier association query and response requirements. '''The Identifier Event Function (IEF) provides the Identifier Caching Function (ICF) with the events necessary to answer the identifier association queries from the IQF.''' LEAs are able to issue real-time queries to the Identifier Query Function (IQF), which in turn queries the ICF.

<center>[[File:High-level ID-Retrieval-via-Query-Response.png|High-level ID-Retrieval-via-Query-Response diagram]]</center>

The IQF and ICF shall support the following query types:
* Single query and response.
* Single query and response followed by triggered real-time reporting of any subsequent changes reported to the ICF (see NOTE 2).

Within 33.127 V18.0.0 document, '''only a single ICF for all IEFs is supported.'''

Within 33.127 V18.0.0 document, interfaces and generic functionality for dedicated identifier query and response are defined in this clause, while specific instances of the IEFs are defined within clause 6 and the ICF in clause 7.
For each request over LI_HIQR, the LEA shall provide a legal warrant/authorisation unique identifier. In addition, depending on the scenario, the LEA needs to provide, the observed identity (temporary or permanent), along with the serving cell identity, tracking area identifier, and time of observation by LEA.

The IQF shall obtain in real-time the identifier associations which match the LEA query from the ICF and provide a response to the LEA over LI_HIQR.
In some cases, it may not be possible to establish a single unique identifier association given the information provided by the LEA. IQF handling in such a scenario is subject to the authorisation in the warrant and is outside the scope of the present document.

:NOTE 1: If the LEA is unable to provide the tracking area associated with an observed temporary identifier this may prevent the CSP from uniquely associating the identifier to the correct UE.
:NOTE 2: Single query and response followed by triggered real-time reporting of any subsequent changes detected by the IEF is only applicable to queries based on a permanent identifier where the changes reported are new temporary identifiers to which that permanent identifier has been associated.
:NOTE 3: The terms identifier and identity are used interchangeably in clause 5.7. This also applies to the naming of functions like IQF.