Content for  TS 33.127  Word version:  18.8.0

In the 5GC network, the AMF handles the access and mobility functions as well as provides or facilitates UE location information delivery to other NFs in the course of location-related service operations, such as LCS or Location Reporting. The AMF shall have LI capabilities to generate the target UE's network access, registration, connection management, and location update related xIRI. Extending the generic LI architecture presented in clause 5, Figure 6.2-3 below gives a reference point representation of the LI architecture with AMF as a CP NF providing the IRI-POI functions.

The LICF present in the ADMF receives the warrant from an LEA, derives the intercept information from the warrant and provides the same to the LIPF. The LIPF present in the ADMF provisions the IRI-POI (over LI_X1) present in the AMF and the MDF2. The LIPF may interact with the SIRF (over LI_SI) present in the NRF to discover the AMFs in the network. The IRI-POI present in the AMF detects the target UE's access and mobility related functions (network access, registration and connection management), generates and delivers the xIRI to the MDF2 over LI_X2. The MDF2 delivers the IRI messages as part of the Interception Product to the LEMF over LI_HI2.

The LIPF present in the ADMF provisions the intercept information associated with the following target identities to the IRI-POI present in the AMF:

• SUPI.
• PEI.
• GPSI.

The interception performed on the above three identities are mutually independent, even though, an xIRI may contain the information about the other identities when available.

TS 33.501 defines the ability to prevent the SUPI being exposed over the 5G RAN through the use of SUCI. Where SUPI privacy is implemented by both the UDM and UE, the SUPI is not sent in the clear over the RAN. Therefore, AMF has to rely on the UDM to provide the SUPI as part of the registration procedure as defined in TS 33.501. If the AMF receives a SUCI from the UE then the AMF shall ensure for every registration (including re-registration) that SUPI has been provided by the UDM to the AMF and that the SUCI to SUPI mapping has been verified as defined in TS 33.501. This shall be performed regardless of whether the SUPI is a target of interception. The AMF IRI-POI shall provide both the SUPI and the current SUCI in all applicable events defined in clause 6.2.2.4.

The IRI-POI present in the AMF shall generate xIRI, when it detects the following specific events or information:

• Registration.
• Deregistration.
• Location update.
• Identifier association.
• Start of interception with already registered UE.
• Unsuccessful procedure.
• Positioning info transfer.
• Handover.
• Trace.
• UE policy transfer.
• Service accept.

The registration xIRI is generated when the IRI-POI present in an AMF detects that a target UE has successfully registered to the 5GS via 3GPP NG-RAN or non-3GPP access. The registration xIRI describes the type of registration performed (e.g. initial registration, periodic registration, registration mobility update) and the access type (e.g. 3GPP, non-3GPP). Unsuccessful registration shall be reported only if the target UE has been successfully authenticated. The deregistration xIRI is generated when the IRI-POI present in an AMF detects that a target UE has deregistered from the 5GS. The deregistration xIRI shall indicate whether it was a UE-initiated or a network-initiated deregistration. The location update xIRI is generated each time the IRI-POI present in an AMF detects that the target's UE location is updated due to target UE mobility (e.g. in case of Xn based inter NG-RAN handover) or when the AMF observes target UE location information during some service operation (e.g., LCS, Location Reporting, or emergency services). The generation of such xIRI may be omitted if the updated UE location information is already included in other xIRIs (e.g. mobility registration) provided by the IRI-POI present in the same AMF. If the information in the AMF received over N2 (TS 38.413) includes one or more cell IDs, then all cell IDs shall be reported to the LEMF whenever location reporting is triggered at the AMF. The identifier association xIRI is generated each time the IRI-POI in the AMF detects a SUCI or 5G-GUTI allocation change for a SUPI associated with the target UE. The start of interception with already registered UE xIRI is generated when the IRI-POI present in an AMF detects that interception is activated on the target UE that has already been registered in the 5GS. When additional warrants are activated on a target UE, MDF2 shall be able to generate and deliver the start of interception with already registered UE related IRI messages to the LEMF associated with the warrants without receiving the corresponding start of interception with already registered UE xIRI. The unsuccessful procedure xIRI is generated when the IRI-POI present in an AMF detects that a target initiated procedure (e.g. session establishment, SMS) is rejected, is not accepted by the AMF, or fails before the proper NF handling the communication attempt itself is involved. The unsuccessful procedure xIRI is also generated when the IRI-POI present in the AMF detects that a PDU session modification request to convert a single access PDU session to a Multi-Access PDU (MA PDU) session is not accepted by the AMF and therefore not forwarded to the SMF. The IRI-POI in the AMF shall support per target selective activation or deactivation of reporting of identifier association xIRI independently of activation of LI for all other events. When identifier association xIRI only reporting is activated, the IRI-POI in the AMF shall also generate location update xIRI. The positioning info transfer xIRI is generated when the IRI-POI present in the AMF detects one the following events:

• network-based or network-assisted positioning requests, responses or reports related to a target UE are being exchanged between LMF and NG-RAN via the AMF.
• UE-based or UE-assisted positioning requests, responses or reports related to a target UE are being exchanged between LMF and the target UE via the AMF.

The handover xIRI is generated when the IRI-POI in the AMF detects that a target UE is the subject of a handover between radio access nodes in 5GS to EPS, Intra 5GS, 5GS to UTRA, or EPS to 5GS scenarios. The trace xIRI is generated when the IRI-POI in the AMF detects that a trace session has been initiated for a target. The UE policy transfer xIRI is generated when the IRI-POI present in the AMF detects that UE policies related to a target UE are being sent by the PCF to the target UE via the AMF and confirmed by the target UE. The service accept xIRI is generated when the IRI-POI in the AMF detects that the target UE service request has been accepted, changing the service state of the target.

The list of xIRI parameters is specified in TS 33.128. All xIRI shall include the following:

• Target identity.
• Time stamp.
• Correlation information.

The list of parameters in each xIRI is defined in TS 33.128. The following give a summary. The registration xIRI shall include the following:

• Registration type information.
• Access type information.
• Requested slice information.

The deregistration xIRI shall include the following:

• UE initiated de-registration.
• Access type information.
• Network initiated de-registration.

The location update xIRI shall include the following:

• Location of the target UE (see clause 7.3).

The identifier association xIRI shall include the following:

• Subscription permanent identifier.
• Temporary identifier association (i.e. SUCI or 5G-GUTI).
• Association change type indication.

The start of interception with already registered UE xIRI shall include the following:

• Access type information.
• Requested slice information.

The unsuccessful communication attempt xIRI shall include the following:

• Rejected type of communication attempt.
• Access type information.
• Failure reason.

The handover xIRI shall include the following:

• Handover type and reason.
• Radio related information.
• UE capability information.

When the access type is non-3GPP, the IP address used by the UE to reach the N3A Entity shall be reported. The port shall also be reported if available. The trace xIRI shall include the following:

• Trace related information.

The UE policy transfer xIRI shall include the following:

• UE policies.

The service accept xIRI shall include the following:

• Service request related information.
• Service accept related information.

The AMF shall provide the IRI-POI functions in the following network topology cases:

• Non-roaming case.
• Roaming case, in VPLMN.
• Roaming case, in HPLMN for non-3GPP access.

In a roaming case, it is possible that the target UE may use non-3GPP access with the N3A Entity present in the HPLMN.

The AMF shall provide IEF capabilities. The IEF present in the AMF shall support LI_XEM1 interface and upon activation shall provide IEF events to the ICF over LI_XER interface. The IEF shall not generate events prior to UEs being successfully registered by the AMF onto the network.

The IEF present in the AMF shall generate report records, when it detects the following specific events or information for any UE:

• Association of a 5G-GUTI to a SUPI (this may also include SUCI to SUPI association).
• De-association of a 5G-GUTI from a SUPI.

The association event shall be generated by the IEF in the AMF whenever the AMF initiates any action or procedure for which a new allocated 5G-GUTI is sent to the UE regardless of whether the action or procedure is completed successfully.

The list of event parameters is specified in TS 33.128. Each event shall include at the minimum the following information:

• Subscription permanent identifier.
• Observed temporary identifier(s).
• Cell identity (see clause 7.3).
• Time stamp of event.
• AMF identifier (including Region and Set Identifiers).
• Tracking area identifier.
• Registration area (including tracking area identifier list).

The following additional information shall be included if it is available in the AMF when the event is reported to the ICF:

• Permanent equipment identifier.

Since the IEF generates events independently of network topology for individual service usage UEs, no specific network topology handling is provided by the IEF. The IQF shall be responsible for handling any network topology requirements that may be applied by the LEA in an individual warrant.