If the UE registered to non-3GPP access, following information can be regarded as UE location information:

  If the UE registered to 3GPP access and non-3GPP access simultaneously, following information can be regarded as UE location information:

• All location information when the UE only registered to non-3GPP access,
• All location information when the UE only registered to 3GPP access, more details can refer to TS 36.305.

The positioning of a UE can be performed via either 3GPP access network or non-3GPP access network. For a MT-LR Location Service request, in order to select the positioning access type, the GMLC uses information retrieved from the UDM and optionally serving AMFs, e.g. access type, its serving AMF identity(ies), and UE connectivity state of this access, if available, and locally configured operator policy as follows:

• If only one AMF identity is provided by the UDM, the GMLC selects this AMF for UE positioning.
• When the UE is concurrently served by multiple PLMNs respectively for 3GPP access and non-3GPP access, multiple AMF identities with corresponding access types may be provided by the UDM, and the GMLC selects one access type and its associated AMF, which may be based on access type and its AMF, UE connectivity state per access type information, if this is retrieved from UDM or AMFs, PLMN identity, and/or locally configured operator policy. If the location estimation result provided by this AMF cannot fulfil the QoS requirements, the GMLC may reselect another access type and its associated AMF from the candidate list provided by the UDM to perform positioning.

When AMF receives a MT-LR Location Service request, the AMF shall provide to the LMF UE connectivity state per access type as well as the QoS requirement that are received from the GMLC. When AMF receives the event report from the UE for a periodic or triggered MT-LR Location Service, the AMF may select a LMF or use the LMF indicated by the UE as described in clause 6.4 and clause 6.3.1 and may provide the UE connectivity state per access type to the LMF. The LMF determines the positioning access type and positioning method based on the QoS requirement, UE/network positioning capability, and UE connectivity state per access type received from the AMF and the locally configured operator policy.

An LCS client or AF may or may not be authorised to retrieve the UE location, e.g. for commercial use. UE LCS privacy is a feature which allows a UE and/or AF to control which LCS clients and AFs are and are not allowed access to UE location information. UE LCS privacy can be supported via subscription and via UE LCS privacy profile handling. With subscription, privacy preferences for a UE are stored in a UE LCS privacy profile as part of UE subscription data in the UDM and queried from the UDM by another NF such as GMLC or NEF. The UDM may also store the UE privacy profile in the UDR. In this release of the specification, subscription of privacy preferences is restricted to the Call/Session unrelated Class as defined in clause 5.4.2.2.3 and the PLMN Operator Class as defined in clause 5.4.2.2.4. With UE LCS privacy profile handling, the UE and/or AF can provide and update part of the UE privacy profile and provide it to the network as an update to the UDR. In this release of the specification, UE LCS privacy profile handling is restricted to the Location Privacy Indication as defined in clause 5.4.2.3. The UE LCS privacy profile is used to indicate whether LCS requests from LCS clients and AFs are allowed or disallowed, together with the POI as defined in clause 5.4.4.

A generation or change to the LPI in UE LCS privacy profile is determined by the UE and provided to the network using N1 NAS message. It may be updated by UE any time. An authorized AF is allowed to provision the LPI in UE LCS privacy profile for specific UE(s) via NEF. The LPI in UE LCS privacy profile may be provided or updated by the target UE during the 5GC-MT-LR and Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events. The updated profile is stored into the UDR by the UDM after the interaction with the AMF. The LPI in UE LCS privacy profile shall include an indication if location is allowed or disallowed and may include a valid time period for LPI as described in clause 5.4.2.3. In addition, a notification is sent by the UDM in order to notify the subscribed consumer i.e. GMLC and NEF about the change of UE LCS privacy profile:

• Target UE identity (one or both of GPSI and SUPI);
• Updated UE LCS privacy profile.

The POI is used to determine whether the UE LCS privacy profile of the subscriber to be positioned shall be overridden by the request for location services. The POI is applicable only to regulatory services. The assignment of a POI value with an "override" or "not override" value in the LCS client profile (see clause 7.2.1) is done during the LCS client provisioning (out of scope of this specification). The type of LCS client requesting location information (i.e. emergency, law-enforcement etc.) shall determine the value of the POI assigned to the LCS client profile.

UDM provides the UE LCS privacy profile to NEF and GMLC, if the information is available. For a 5GC_MT_LR request for immediate location, the GMLC in the HPLMN, or the HGMLC when the UE is roaming, determines whether the LCS client or NF is authorized to retrieve UE location, based on the UE privacy profile. Authorization is determined by first verifying whether the location request is allowed according to the Location Privacy Indication (LPI) defined in clause 5.4.2.3. If the location request is not allowed, an error response is returned to the LCS client, AF, or NF. If the location request is allowed according to the LPI, authorization is next verified according to the Call/Session unrelated Class for an LCS Client or AF or according to the PLMN Operator Class for an NF. For the Call/Session unrelated Class client types where POI does not apply, the HGMLC determines one of the following indications to be included in the location request forwarded to the serving AMF, or VGMLC in the case of roaming:

• Location allowed without notification;
• Location allowed with notification;
• Location with notification and privacy verification; location allowed if no response;
• Location with notification and privacy verification; location restricted if no response.

For PLMN Operator Class client types that are permitted to receive UE location information or where POI applies, a "location allowed without notification" is included. For a Call/Session unrelated Class client type, which a geographic area restriction was included in the UE LCS privacy profile, the (H)GMLC performs an initial location by including a "location allowed without notification" indication in the location request sent to the VGMLC or AMF. The (H)GMLC then determines, based on the obtained location, whether location of the UE is allowed. If location of the UE is allowed subject to notification or verification, the (H)GMLC initiates a second location request to the VGMLC or serving AMF for the purpose of notification and/or verification only and includes one of the following indications in the second location request forwarded to the serving AMF, or VGMLC in the case of roaming:

• Notification only
• Notification and privacy verification only

When "Notification and privacy verification only" is included, the serving AMF shall report the result of privacy verification back to the (H)GMLC (i.e. location allowed, location not allowed or timeout on a response) and the (H)GMLC shall determine whether or not to return the location received for the first request back to the LCS client based or AF on this result. For a direct NEF query to a serving AMF, or for an NEF query via the UDM, if GMLC is not involved, the NEF determines whether the AF is authorized to retrieve UE location, based on the UE LCS privacy profile.

Support of UE LCS privacy for a deferred UE location is the same as that described in clause 5.4.5 for an immediate UE location with the differences and qualifications described in this clause. An (H)GMLC or NEF shall subscribe to notification of a change in the UE LCS privacy profile from the UDM at the start of a deferred 5GC-MT-LR procedure and shall verify UE privacy both at the start of the deferred 5GC-MT-LR procedure and for each location result returned to an LCS client or AF based on the most recent UE LCS privacy profile received from the UDM. If the UE LCS privacy profile indicates notification or verification of a location request is required for a particular value added LCS client, the (H)GMLC indicates this in the initial location request sent to the serving AMF and the serving AMF notifies the UE or verifies the location request with the UE, as for an immediate location request, when the UE first becomes reachable. The serving AMF also indicates the type of deferred location request in the NAS Location Notification Invoke Request sent to the UE. However, the location notification or verification is not repeated for each UE location in the case of a periodic or triggered 5GC-MT-LR. For a value added LCS client, AF, value added LCS client group or LCS service type, for which a geographic area restriction was included, the (H)GMLC includes any request for notification or verification of the location request in the initial location request sent to the serving AMF. The (H)GMLC then determines whether a location result can be returned to the LCS client or AF based on whether the location result is or is not restricted by the geographic area restriction. If the location result is allowed by the geographic area restriction, the (H)GMLC does not perform a second location request to the serving AMF for the purpose of notification and/or verification only. If the location result is not allowed by the geographic area restriction, the (H)GMLC discards the location result without notifying the LCS client or AF.