Datasets:

OrganizedProgrammers
/

3GPPSpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 466k rows

hash stringlengths 32 32	doc_id stringlengths 5 12	section stringlengths 4 595	content stringlengths 0 6.67M
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.1 General	The UE LCS privacy profile shall include information related to classes of LCS client, referred to as "privacy classes", which are permitted, or conditionally permitted, to obtain location information for the UE. Privacy classes are defined in clause 9.5.3 of TS 23.271 [4], but not all classes defined in TS 23.271 [4] are supported in this specification. Privacy classes are supported as described below. The differences between the Privacy classes for 5GS and those for EPS are described in Annex A. The UE LCS privacy profile also includes the Location Privacy Indication, as defined in clause 5.4.2.3, which can be provided and updated by the UE and/or AFs.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.2 Privacy Classes
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.2.1 Universal Class	The universal class defined in clause 9.5.3.1 of TS 23.271 [4] is not supported in this specification.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.2.2 Call/Session related Class	The call/session related class defined in clause 9.5.3.2 of TS 23.271 [4] is not supported in this specification.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.2.3 Call/Session unrelated Class	The call/session unrelated class defined in clause 9.5.3.3 of TS 23.271 [4] is supported for a 5GC-MT-LR. The subscription options for the Call/Session unrelated Class may be assigned to an identified value added LCS Client, AF, value added LCS Client group or service type as described in clause 7.1 and comprise one of the following alternatives: - positioning allowed without notifying the UE user (default case); - positioning allowed with notification to the UE user; - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. NOTE: LCS service types are defined in TS 22.071 [2] and numeric values for LCS service types are listed in clause 17.7.8 of TS 29.002 [29]. A default subscription as described in clause 9.5.3.3 of TS 23.271 [4] is included in the UE LCS privacy profile for any value added LCS client or AF not otherwise identified for the Call/Session unrelated Class and defines one of the following alternatives: - positioning not allowed (default case); - positioning allowed with notification to the UE user; - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. The subscription options for the Call/Session unrelated Class may further indicate additional information for each identified value added LCS client, for each identified service type and for the unidentified value added LCS clients as follows: - A valid time period for positioning; - A valid geographic area for positioning. The UE LCS privacy profile may also indicate that any unidentified value added LCS client or an LCS Client associated with an identified service type shall provide a codeword in order to locate the UE, where the codeword is verified by either a GMLC or the UE. When verification by a GMLC is indicated, a list of one or more codewords is included as part of the UE LCS privacy profile.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.2.4 PLMN Operator Class	The PLMN operator class defined in clause 9.5.3.4 of TS 23.271 [4] is supported. NOTE: The PLMN Operator Class (except O&M LCS client in the VPLMN) can be applied to SNPN. Besides the types of client specified in clause 9.5.3.4 of TS 23.271 [4], the PLMN Operator Class also supports positioning by the following types of client: - NWDAF in the HPLMN (when the UE is currently being served by the HPLMN); - NWDAF in the VPLMN.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.2.3 Location Privacy Indication (LPI)	The Location Privacy Indication is not defined in TS 23.271 [4]. The Location Privacy Indication defines whether LCS requests for UE from any LCS clients are allowed or disallowed. The LPI at least includes one of the following global settings (for all LCS clients and AFs): - Location for UE is disallowed (location for UE not allowed to any LCS client except where POI applies). - Location for UE is allowed (default setting, and LCS requests for UE from LCS clients are authorized based on their associated privacy classes as defined in clause 5.4.2.2). NOTE: Additional LPI values may be supported for additional differentiation of location request types. The LPI also allows the following optional settings: - Valid time period for LPI, including start time and end time. The LPI takes precedence on the subscribed privacy classes as defined in clause 5.4.2.2. The LPI allows a UE to override the location preference of the subscribed privacy classes. The usage of LPI is described in clause 6.1.2.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.3 Provision of UE LCS privacy profile	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. NOTE: The AF allowed to provision the UE LCS privacy profile is different from the AF sending location requests. 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.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.4 Privacy Override Indicator (POI)	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.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.5 LCS service authorization for an Immediate UE Location	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. NOTE 1: The UE LCS privacy profiles are not sent to the VGMLC. 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. NOTE 2: Notification and verification are not supported for a direct NEF query to a serving AMF, or for an NEF query via the UDM. Consequently, when notification or verification are required, or may be required based on a geographic area restriction, an NEF shall forward a location request to a GMLC or return an error indication to the requesting AF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.4.6 LCS service authorization for a Deferred UE Location	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.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.5 Location service exposure	Location service can be exposed to the authorized control plane NF or the LCS client to obtain the UE location to enable their application and services using the MT-LR procedure. For the location service exposed to the AF which is not allowed to directly interact with the GMLC or AMF, CAPIF API may be used between NEF and the AF as described in clause 6.2.5.1 of TS 23.501 [18]. For location service exposure, there are two types of location service requests as defined in clause 4.1a.4 and clause 4.1a.5: - Location Immediate Request (LIR); and - Location Deferred Request (LDR). The following attributes may be included in the location service requests: - Target UE identity; - LCS Client identity or AF ID; - Service identity, if needed; - Codeword, if needed; - Type of Event definition, i.e. UE available, change of area, motion or periodic location, applicable to deferred location requests only; - Indication of requiring reliable UE location information; - Definitions for change of area type deferred location requests. Following parameters may be defined, if needed: a) Indication for event trigger, i.e. UE enters, leaves or is within requested target area; b) Indication of either a single event report or multiple event reports; c) Minimum time interval between area event reports, if multiple event reports are requested; d) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the change of area event report; e) Duration of event reporting; f) Maximum time interval between reports; g) Maximum sampling time for event detection; h) Indication to have an additional check whether UE is located within the requested target area, and when this additional check is requested, the location estimate is mandatory; - Definitions for motion type deferred location requests. Following parameters may be defined, if needed: a) Linear distance threshold; b) Indication of either a single event report or multiple event reports; c) Minimum time interval between motion event reports, if multiple event reports are requested; d) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the motion event report; e) Duration of event reporting; e) Maximum time interval between reports; f) Maximum sampling time for event detection; - Definitions for periodic location type deferred location requests. Following parameters may be defined, if needed: a) Time interval between successive location reports; b) Total number of reports; - Start time, stop time (i.e. specifying the validity time of LCS request), if needed for LCS Client e.g. using the OMA MLP protocol; - Interval, applicable to periodical requests only; - Requested LCS Quality of Service information, if needed, i.e. accuracy, response time and LCS QoS Class; - Requested type of location, i.e. "current location", "current or last known location" or "initial location" applicable to LIR only (current location is only available for LDR); - Supported GAD shapes, if needed; - Velocity of the UE, if needed; - Priority, if needed; - Service coverage (i.e. E.164 country codes for geographic areas, ITU-T Recommendation E.164 [23]), if needed; - Requested maximum age of location, if needed; - Local coordinate reference system, if needed for LCS Client e.g. using the OMA MLP protocol; - Target area, i.e. geographical area expressed as one of the following format, if needed: a) a shape defined in TS 23.032 [8]; b) local coordinate system for LCS Client e.g. using the OMA MLP protocol; c) E.164 country code for a geographic area [23] for LCS Client e.g. using the OMA MLP protocol; d) PLMN identity for LCS Client e.g. using the OMA MLP protocol; e) geopolitical name of the area (e.g. London) for LCS Client e.g. using the OMA MLP protocol; - Response Method, if needed for LCS Client e.g. using the OMA MLP protocol; - Scheduled Location Time. - Definitions for periodic or triggered location reporting from a UE to an LCS Client or AF over user plane. Following parameters may be defined, if needed: a) Request for user plane reporting; b) User plane address of the LCS Client or AF; c) Security information to enable a secure connection. The following attributes may be included in the location service response: - Location indication of UE in geographical coordinates and/or local coordinates expressed as a shape as defined in TS 23.032 [8] or for LCS Client e.g. using the OMA MLP protocol, local coordinate reference system; - Velocity of the UE as defined in TS 23.032 [8], if requested and if available; - The information about the positioning method used to obtain the location estimate of the UE, if it is available at the LCS server and if needed; - Time stamp of location estimate; - Indication when UE enters, is within or leaves the Geographical area, if needed; - Acknowledgement for a deferred location request, if needed. - Request id, if needed. - Indication that the requested QoS was not met, if needed, only applicable if the request was for best effort class - Indication of a periodic event. - Indication of a motion event. - Indication that a deferred location request has been activated in a UE. - Indication of expiration of the maximum reporting interval for the area event or motion event for LCS Client e.g. using the OMA MLP protocol. - Indication of a cumulative event for user plane location reporting from a UE to an LCS Client or AF. In addition, the information attributes of the location service request may be used also in the location service response. For a LCS client in the core network, the LCS service request is sent to GMLC using Le interface. For an AF not allowed to directly interact with the GMLC or AMF, the LCS service request is sent to NEF using the service based interface. For an internal control plane NF, the LCS service request is sent to AMF or GMLC using the service based interface. NOTE: For regulatory services, any control plane NF can be LCS client. To support location service exposure through NEF, when NEF receives a LCS service request, it determines based on the location accuracy of the QoS requirement, e.g. lower or higher than cell-ID level, on whether to invoke the GMLC service or the AMF service for the LCS service request.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.6 LCS Charging	Charging Information for LCS service is collected at GMLC and AMF. For roaming case, the Charging Information shall be collected in both home PLMN and visited PLMN for inter-operator charging purpose. Charging mechanism for LCS service and the Charging Information collected at GMLC and at AMF are defined in TS 32.271 [30] and TS 32.298 [31].
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7 Support of Concurrent Location Requests
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.1 General	Concurrent Location Requests occur when any entity (e.g. UE, AMF, LMF, GMLC, NEF): - Case A: receives/initiates multiple LCS requests (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the location estimate of the same target UE within a time period; or - Case B: receives/initiates one or more new LCS request(s) (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the location estimate of the same target UE during the location session to support the old LCS request(s). In either case, if allowed by the QoS requirements and privacy settings, the entity may combine the concurrent location requests by fully executing one of the requests and using the ensuing location estimate result(s) to satisfy the other request(s) without fully executing the latter. When concurrent location requests are supported, each entity needs to ensure it correlates each location/position response with the associated request and different concurrent location requests shall be treated separately without any dependency on one another by any entity. NOTE 1: Combining of location requests is not allowed for a deferred 5GC-MT-LR for periodic or triggered location for privacy reasons (e.g. a target UE would not be aware that location event reports were being sent to multiple AFs and/or external LCS clients). NOTE 2: An entity (e.g. AMF, GMLC, NEF) may cache location information obtained for one location request and use this information to support later location requests for "current or last known location". This is not considered to be a case of concurrent location requests. If the entity, either itself or in association with another entity, cannot support concurrent location requests or it can only support up to a certain number of concurrent location requests, it can reject or defer a new concurrent request or cancel one or more existing requests. For Case B, it can also allow the new location request to proceed concurrently with and separately from the previous requests. LCS Client/AF priority and any other relevant priority information (e.g. UE subscription preferences) should be considered when rejecting or deferring a concurrent request or when cancelling one or more existing requests. In particular, location requests associated with emergency services or lawful interception clients should be given priority over other location requests.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.2 Combining location requests by an H-GMLC or NEF	An H-GMLC or NEF may combine concurrent location requests (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the same target UE by executing only one request and using the ensuing location estimate result(s) to satisfy the other request(s). The conditions for this are as follows: - the H-GMLC must be able to fully resolve privacy requirements for the other location request(s) without requiring notification or verification by the UE (though notification only as in steps 17-23 of clause 6.1.2 could still be used in the case of location dependent privacy); and - the QoS for the other request(s) should be less strict than the QoS for the executed location request. An H-GMLC may also combine concurrent location requests in the case of a bulk location request for a group of UEs as described in clause 6.8. In this case, location information for any UE in the group may be obtained from location information obtained from another concurrent location request for the same UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.3 Combining location requests by a V-GMLC	A V GMLC may combine concurrent 5GC-MT LR and 5GC-MO-LR related location requests for the same target UE provided it is clear and unambiguous for any 5GC-MT LR that will not be fully executed (e.g. from the contents of any location request received from the H GMLC) that no outstanding privacy related actions are required for the UE (e.g. no privacy notification and/or privacy verification interaction with the UE). QoS requirements must also be satisfied for the non-executed location requests.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.4 Combining location requests by an AMF	An AMF may combine concurrent 5GC-MT LR, 5GC-MO LR and 5GC-NI LR location requests once any needed privacy related actions (e.g. UE notification and verification) have been performed for each 5GC-MT LR. (i.e. AMF may decide to not execute multiple positioning procedures for the concurrent location requests) QoS requirements must also be satisfied for the non-executed location requests.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.5 Combining location requests by an LMF	An LMF may combine concurrent location requests for the same target UE provided QoS requirements can be satisfied for the non-executed location requests.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.7.6 Combining location requests by a UE	A UE may combine concurrent location requests provided QoS requirements can be satisfied and provided any positioning procedures with an LMF remain supported according to the positioning protocol.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.8 Interworking with the IMS	When the location service request is initiated by the LCS Client / AF for the location estimation of a target UE in an IMS session, a SIP-URI or a TEL-URL maybe included in the request to identify the target UE. In that case, the H-GMLC of the UE shall be able to convert the SIP-URI/TEL-URL into SUPI of the target UE. NOTE 1: The H-GMLC may query IMS-HSS or UDM to retrieve the SUPI of the target UE based on its SIP-URI/TEL-URL. NOTE 2: If multiple SUPIs are resolved for the SIP-URI/TEL-URL, the H-GMLC behaviour is out of scope of this specification.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.9 Location Service involving Mobile Base Station Relay
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.9.1 General	A MBSR (i.e. mobile IAB-node) may have location service capability as specified in TS 38.305 [9] and participate in the location service of a UE. As the MBSR may be moving, the location service procedures need to be enhanced as following for an accurate estimation of the UE positioning: - The UE reports the cell IDs of all the cells the UE performed DL positioning measurements on. - The MBSR which performed the location service procedures for the UE includes it's cell ID in the reported UL positioning measurement. - The AMF serving the UE provides the cell ID of serving cell of the UE and indicates, if possible, that the cell-ID belongs to a MBSR to the LMF in the location request. The AMF serving the UE also provides LMF with the additional ULI Information received from NG-RAN, so that the LMF can initiate the positioning procedure to obtain the location information of the MBSR. - Additionally, the LMF uses the reported cell IDs to derive whether the cell ID(s) corresponds to a MBSR. There can be multiple MBSR cells in the measurement report. - The LMF may also decide whether the cell ID(s) corresponds to MBSR(s) based on information received in a TRP information exchange i.e. that the cell-ID belongs to a MBSR and the UE-ID (GPSI) associated with MBSR. - To aid the LMF to improve the accuracy of the UE location estimation, the MBSR velocity information and time of obtaining its location measurement data should be obtained by the LMF when available. The LMF uses the received location and velocity of the MBSR(s) when estimating the location of the Target UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.9.2 Obtaining location information for the MBSR	There are multiple options for an LMF to obtain the location information and velocity of the MBSR(s): - The LMF can derive the location and velocity of the MBSR by triggering the gNB serving the MBSR using NRPPa or by requesting the GMLC to derive the location of the MBSR (UE) using the UE-ID of the MBSR. The GMLC triggers MT-LR procedure as specified in clause 6.11.1 or 6.11.2. - As the timing of the location estimations for the Target UE and MBSR(s) is important for the quality of the location estimation of the Target UE, the LMF needs to reduce the timing offset of the positioning measurements, i.e. the positioning of the Target UE and MBSR can be scheduled with using the same scheduled location time and compensate for the potential time difference of the positioning measurements, e.g. taking velocity of MBSR into account.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.9.3 Privacy check for MBSR	If the positioning of the MBSR is performed for the location estimation of a Target UE (UE different from the MBSR), the privacy check in clause 5.4 is skipped for the MBSR. When the LMF requests the GMLC to derive the location of the MBSR (UE), the LMF includes a MBSR indication indicating the location of MBSR is requested to determine the location of a Target UE in the location request. The GMLC obtains the subscription information of the MBSR (UE) from the UDM. Based on the indication, and/or MBSR's subscription information, the GMLC skips the privacy check. If the positioning of the MBSR is performed for the location estimation of the MBSR itself when it acts as a normal UE which is not authorized to operate as MBSR based on the subscription information, the UE privacy check procedure in clause 5.4 is performed.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.10 Support of Positioning over user plane connection between UE and LMF for non-regulatory service	LMF and UE may utilize a user plane connection to transfer supplementary services messages and LPP messages. User Plane protocol (LCS-UPP) to support supplementary services messages and LPP messages transport between the UE and the LMF is defined in TS 24.572 [48]. If LMF decides to use user plane the LMF should indicate the UE to use user plane for positioning with the information to establish a secure connection, and via this secure connection, position messages can be transferred between UE and the LMF. The URSP defined in TS 23.503 [41] is used by UE to determine how to route the position messages. The operator may provide LMF(s) address information and connection capability for LCS use in traffic descriptors and LCS user plane positioning dedicated PDU session parameters (e.g., DNN and S-NSSAI) in Route Selection Descriptors to the UE as part of the URSP rule. The position messages can be routed to an established PDU Session or can trigger the establishment of a new PDU Session. The LMF and UE may maintain the established user plane connection and the established user plane connection may be reused for subsequent user plane position messages transmission trigged by UE or LMF. If the LMF detects the user plane connection is not used for an implementation specific time, the LMF terminates the user plane connection. The supplementary services messages transferred over user plane only support event report messages, periodic triggered invoke messages and MS cancel deferred location messages. NOTE 1: In this Release, the user plane connection between UE and LMF can not be used for regulatory positioning service. NOTE 2: For one positioning procedure, the LMF selects either control plane or user plane to transfer the associated supplementary services messages and LPP messages. During the positioning procedure, the LMF and UE should avoid switching between control plane and user plane to transfer the messages above.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.11 Collection of GNSS assistance data	LMF may collect GNSS assistance data by reusing Data Collection from AF as described in clause 5.20a of TS 23.501 [18] and Naf_EventExposure service described in clause 5.2.19.2 of TS 23.502 [19]. The collection may be performed on a periodic basis. LMF generates a mapping table of GNSS assistant data and applicable area (e.g. TA lists). LMF may generate multiple sets of GNSS assistance data for the same location area, and each of them corresponds to a certain location accuracy. The accuracy of GNSS assistance data may vary for different areas. NOTE 1: The multiple accuracy level of GNSS assistance data can be the reason the collection method, and /or calculation method. After the collection, LMF may send the collected GNSS assistance data to UEs via the procedures described in clause 6.14.1 (Broadcast of Assistance Data by an LMF) or clause 6.11.1 (UE Assisted and UE Based Positioning Procedure) during a positioning session. In the case of using Broadcast of Assistance Data by an LMF, the LMF may provision one or more of GNSS assistance data to RAN. LMF may also provision one or more cyphered key(s) to UE from the AMF, and each cyphered key corresponds to a certain GNSS assistance data.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.12 UE Unaware Positioning	UE Unaware Positioning applies to the regulatory location service. When UE Unaware Positioning is required by LCS Client/AF, if the UE is in CM_IDLE or RRC_INACTIVE state, the UE cannot be paged during the positioning procedure. In this case, the 5GC provides the latest stored UE location information to the LCS Client/AF if the requested LCS QoS can be achieved. If the UE is in CM_CONNECTED state, the LMF selects Uplink Positioning method to obtain UE location.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.13 Support of location service in PNI-NPN with signalling optimisation	Support of location service in PNI-NPN is based on the PNI-NPN description defined in clause 5.30.3 of TS 23.501 [18]. PNI-NPN architecture described in Annex C are supported. Under the PNI-NPN architecture described in Annex C, the relevant Network Functions in local network are defined as follows: - Local AMF, an AMF type function deployed in the local network, it supports: - Functionalities related to AMF service operation "NonUeN2MessageTransfer" within Namf_Communication service, defined in TS 29.518 [16]. - Handling "UL and DL NON UE ASSOCIATED NRPPA TRANSPORT", defined in TS 38.413 [38]. NOTE 1: Local AMF can support other functionalities defined in TS 23.501 [18]. NOTE 2: It is assumed only one local AMF is deployed in the local network. - LMF, deployed in the local network, it supports: - Pre-configured with local AMF FQDN or communication address. - For DL UE associated NRPPa signalling, sends the signaling message to the serving AMF. - For DL NON UE associated NRPPa signalling, sends the signaling message to the local AMF. - NG-RAN, deployed in the local network, it supports: - Pre-configured with local AMF FQDN or communication address. - Establishes TNL association with local AMF. - For UL UE associated NRPPa signalling, sends the signalling message to the serving AMF - For UL NON UE associated NRPPa signalling, sends the signalling message to the local AMF - GMLC, deployed in the local network. - UDM, deployed in public network, it supports: - Pre-configured with UE's allowed local network list. - For GMLC request from a different network domain, verify GMLC request by checking whether the local network of GMLC is on the pre-configured UE's allowed local network list. For Nudm_SDM_Get request or Nudm_UECM_Get request from local network, sends the UE data (i.e. privacy setting of UE, current serving AMF address, SUPI) after successful verification. When UE access the NG-RAN in the local network, during the registration procedure or service request procedure, NG-RAN selects the serving AMF in the public network. With appropriate configuration, local AMF cannot be selected as the serving AMF for the UE. During the positioning procedure, if LMF determines network assisted positioning method, the positioning procedure defined in clause 6.11.2 is used and the AMF is the serving AMF. If the LMF determines to obtain Non-UE Associated Network Assistance Data, the positioning procedure defined in clause 6.11.3 is used and the AMF is the local AMF. For MO-LR, immediate MT-LR and deferred MT-LR, the AMF provides the GMLC contact address and a reference number to LMF. When LMF determines UE location, LMF provides the UE location to GMLC directly, as defined in clause 6.3.1. NOTE 3: LMF should not determine to use E-CID positioning method for location service in PNI-NPN.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.14 Event Report Allowed Area	During the deferred 5GC-MT-LR procedure, when the UE detects the triggered or periodic event happens, if it is inside the event report allowed area, the UE is allowed to generate and send the event report to network to reduce UE power consumption. The event report allowed area is a list of cell(s) or TA(s) determined by GMLC based on the event report expected area provided by UE which is a geographical area and is sent to the UE during the deferred 5GC-MT-LR procedure. The event report allowed area applies to the Area, Periodic Location and Motion event types. When the UE decides to send an event report (i.e. the event is detected or the maximum reporting time is expired), if the UE is inside the event report allowed area, the UE sends the event report. If the event report is not received from the UE for an implementation dependent time period, the AF or LCS Client or GMLC cancels the deferred 5GC-MT-LR procedure for periodic, or triggered location events. NOTE: The UE can only send event report when the UE is inside of event report allowed area. The event report allowed area can also be used differently if an area usage indication is provided together with the event report expected area by the UE. A reporting indication that is determined by GMLC based on the area usage indication means when the UE detects the triggered or periodic event happens, if it is outside the event report allowed area, the UE is allowed to generate and send the event report to network to reduce UE power consumption.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.15 Support of Low Power and High Accuracy Positioning	Service requirements for low power and high accuracy positioning (LPHAP) is defined in TS 22.261 [3] and TS 22.104 [39]. Support of low power and high accuracy positioning is optional in this release of specification. Low power and high accuracy positioning is supported via subscription and in the LCS related subscriber data in the UDM, an LPHAP indication may be included. During the positioning procedure, AMF provides the LPHAP indication to the LMF. The LPHAP indication is either obtained from the GMLC, or stored in the UE LCS context received during UE registration procedure. If LMF receives from AMF of the LPHAP indication in the location request, LMF determines appropriate positioning method, e.g. network-based positioning method, or may determine to trigger the low power periodic and triggered 5GC-MT-LR procedures in clause 6.7 by taking into account the LPHAP indication. In addition, LMF may also send LPHAP Assistance Information defined in TS 38.455 [15] to RAN in the positioning procedure, as defined in clause 6.11.2.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.16 Location services assisted by NWDAF	LMF and AMF may utilize analytics from NWDAF to assist with location services as described in clause 6.21. NWDAF may provide Location Accuracy analytics as specified in clause 6.17 of TS 23.288 [37] to LMF. When LMF receives analytics for Location Accuracy from the NWDAF, it may use the analytics to determine indoor or outdoor for a location estimate, to select or adjust appropriate positioning methods for the requested location accuracy. NWDAF may provide UE related mobility analytics as specified in clause 6.7 of TS 23.288 [37] to AMF. The UE location information received in analytics can be used by AMF to perform the UE location verification for NR satellite access. NWDAF may provide to the LMF trained ML model(s) which directly estimates UE location. 5.16A Network data analytics assisted by LCS NWDAF may interact with the LCS system to request location information for a target UE or a group of UEs via Ngmlc services or NL9. NWDAF may request an aggregated report for a single UE from GMLC to include multiple UE location estimates for a period of time. NWDAF may also provide a reporting time to indicate the latest time for reporting. NOTE: The value of the reporting time is left for NWDAF implementation. The reporting time should be earlier than the parameter 'time when analytics information is needed' (if applicable) defined in TS 23.288 [37]. 5.16B LCS Continuity During UE Mobility LCS session continuity during UE mobility applies to: - deferred triggered/periodic MT-LR, immediate MT-LR and MO-LR procedures. - uplink, downlink or uplink and downlink positioning methods. 5.16B.1 Mobility Between 5GS and EPS LCS continuity of UE in RRC-CONNECTED state enables transfer of a location session between 5GS and EPS. The LCS QoS may then be mapped from the source RAT to the target RAT. The Lr' interface between the EPC-GMLC and 5GC-GMLC is implementation specific - or the EPC-GMLC and 5GC-GMLC may be co-located.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.17 Support of Ranging and Sidelink Positioning	Ranging and Sidelink Positioning as defined in TS 23.586 [40] is supported. The following procedures have been specified to support the Network Assisted Sidelink Positioning: - SL-MO-LR involving LMF as defined in clause 6.20.1; - SL-MT-LR involving LMF as defined in clause 6.20.3; - 5GC-MO-LR Procedure using SL positioning as defined in clause 6.20.2; - 5GC-MT-LR Procedure using SL positioning as defined in clause 6.20.5; - SL-MT-LR for periodic, triggered Location Events as defined in clause 6.20.4.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.18 Support for UE positioning based on a ML Model at the LMF
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.18.0 General	The LMF may calculate the UE location and estimate the achieved accuracy by using LMF-based AI/ML Positioning. When receiving the request from AMF for determining a UE location, the LMF selects an appropriate positioning method as described in clause 5.2 to determine the result of the positioning. The result of the positioning may be calculated by using LMF-based AI/ML Positioning ML model supported by LMF. The LMF collects input data from UE or NG-RAN for the LMF-based AI/ML Positioning to perform location calculation and provide the location to the consumer. NOTE 1: Whether to select LMF-based AI/ML Positioning for location result calculation is determined by LMF. NOTE 2: The specific measurement data collected by LMF from UE and NG-RAN for LMF-based AI/ML Positioning are in the scope of RAN specifications and not in the scope of this specification. Editor's note: What input data collected from UE and NG-RAN to LMF for LMF-based AI/ML Positioning will be determined by RAN WG1. How to collect the input data for LMF-based AI/ML Positioning calculation need coordination with RAN WGs. The ML model that is used for LMF-based AI/ML Positioning may be trained by LMF. The trigger for data collection required for model training in LMF is up to implementation. LMF collects input data from UE for ML model training as described in clause 6.22.2. The LMF collects input data from NG-RAN for ML model training as described in clause 6.22.3. The LMF may also request a trained ML model for LMF-based AI/ML Positioning from NWDAF containing MTLF as described in clause 6.22.5. The LMF discovers a suitable NWDAF containing MTLF via NRF as described in clause 5.2 of TS 23.288 [37] with the following considerations: - The LMF may provide the positioning case information(e.g. UE assisted/LMF-based AI/ML Positioning case, NG RAN node assisted LMF-based AI/ML Positioning case, or both). - The LMF provides an Area of Interest, and may include the ML Model Interoperability indicator to discover an NWDAF that can provide an AI/ML Model. - The LMF may request a NWDAF with ML Model accuracy checking capability to report when the model is degraded (i.e. for ML model performance monitoring). NOTE 3: Other NWDAF discovery parameters listed in clause 5.2 of TS 23.288 [37] such as Analytics ID, FL capability type and related time period, S-NSSAI or any roaming capabilities are not included by LMF. Editor's note: The types of LMF-based AI/ML positioning model (e.g., per positioning case) is FFS, which needs to be coordinated with RAN WGs. The LMF requests the NWDAF containing MTLF to provide an ML Model for LMF-based AI/ML Positioning as described in clause 6.2A of TS 23.288 [37] with the following considerations: - The LMF provides the following input parameters in the Nnwdaf_MLModelProvision_Subscribe or Nnwdaf_MLModelInfo_Request: - LMF-based AI/ML positioning indication. - Optionally, Vendor ID, ML Model Filter Information (e.g. Area of Interest), Positioning case information, Target of ML Model Reporting, ML Model Target Period, Time when model is needed, Inference Input Data information and ML Model Monitoring Information. - If vendor specific information is required , then the ML Model Interoperability Information is included. - If the LMF supports multiple AI/ML Models, indication of support for multiple ML Models, optionally with Number of ML Models and Accuracy level(s) of Interest. The NWDAF containing MTLF collects input data to perform the ML model training as described in clause 6.22.4, and the NWDAF containing MTLF performs ML model provision to LMF as described in clause 6.2A of TS 23.288 [37] with the following considerations: - The NWDAF containing MTLF provides the ML Model identifier and ML Model Information for the ML Model for UE Positioning, and optionally, the following parameters: - ML Model Filter Information and/or Target of ML Model Reporting, if the ML Model provisioning request includes multiple ML Model Filter Information and/or Target of ML Model Reporting; - Indication of whether the ML Model identifier is updated (e.g. retrained ML model). - Validity period, Spatial validity, Training Input Data Information, ML Model accuracy Information. Editor's note: The collected input data for LMF-based AI/ML Positioning model training will be determined by RAN1. How to collect the input data for LMF-based AI/ML Positioning model training need coordination with RAN WGs. Once the ML model for LMF-based AI/ML Positioning is trained and available in the LMF, the LMF may use it to perform UE Positioning after receiving a location determination request from AMF. Editor's note: Whether user consent for UE positioning calculation is needed apart from the existing GMLC check of the LCS privacy profile is FFS. For ML model training, performance monitoring and UE positioning calculation using LMF-based AI/ML Positioning, the LMF checks with UDM the user consent status before collecting UE related data, see clause 6.22.3 and clause 6.22.4. Either LMF or NWDAF containing MTLF may perform performance monitoring for LMF-based AI/ML Positioning. When the ML model that is used for LMF-based AI/ML Positioning is trained by LMF the LMF monitors the performance of the ML model. When the ML model that is used for LMF-based AI/ML Positioning in LMF is trained by NWDAF containing MTLF, then the NWDAF containing MTLF monitors the performance of the ML model. LMF may determine whether to use the LMF-based AI/ML Positioning to perform location calculation based on the model performance monitoring result. LMF or the NWDAF containing MTLF may also trigger the ML model retraining based on the model performance monitoring result.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.18.1 Void
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.18.2 AI/ML model performance monitoring for LMF-based AI/ML Positioning	When the AI/ML model that is used for LMF-based AI/ML Positioning is trained by LMF, the LMF may perform performance monitoring for AI/ML model by collecting the measurements data and ground truth data of PRU(s)/UE(s) by using the procedures of data collection for LMF-based AI/ML Positioning as specified in clause 6.22.2 or clause 6.22.3. Before collecting the data from UE(s), LMF needs to check the user consent in UDM, however LMF does not need to check user consent for data collected from PRU. LMF calculates the location information based on the collected measurement data by using AI/ML model. Based on the calculated location information and ground truth data, LMF evaluates the AI/ML model performance to generate the performance monitoring result. The result may trigger LMF to change the positioning method, e.g. from LMF-based AI/ML Positioning to the legacy positioning or retrain the AI/ML model in LMF. When the AI/ML model that is used for LMF-based AI/ML Positioning in LMF is trained by NWDAF containing MTLF, then the NWDAF containing MTLF may monitor the performance of the AI/ML model as specified in clause 6.2E.4 of TS 23.288 [37] based on the data collection via the LMF as specified in clause 6.22.4. If the data collection is not granted, the LMF does not perform any data collection procedure for the ML model performance monitoring for this UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.19 Location Service involving Mobile Wireless Access Backhaul
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.19.1 General	A MWAB may have location service capability as specified in TS 38.305 [9] and participate in the location service of a UE. As the MWAB may be moving, the location service procedures need to be enhanced as following for an accurate estimation of the UE position: - The UE reports the cell IDs of all the cells the UE performed DL positioning measurements on. - The MWAB which performed the location service procedures for the UE includes its cell ID in the reported UL positioning measurement. - The AMF serving the UE provides the cell ID of serving cell of the UE and indicates, if possible, that the cell-ID belongs to a MWAB to the LMF in the location request. The AMF serving the UE may also provide LMF with the additional ULI Information received from MWAB. - Additionally, the LMF uses the reported cell IDs to derive whether the cell ID(s) corresponds to a MWAB. There can be multiple MWAB cells in the measurement report. - The LMF may also decide whether the cell ID(s) corresponds to MWAB(s) based on information received in a TRP information exchange i.e., that the cell-ID belongs to a MWAB and the UE-ID (GPSI) associated with MWAB. - To aid the LMF to improve the accuracy of the UE location estimation, the MWAB velocity information and time of obtaining its location measurement data should be obtained by the LMF when available. The LMF uses the received location and velocity of the MWAB(s) when estimating the location of the Target UE. The reference architectures for MWAB involved location services in different scenarios are specified in Annex S of TS 23.501 [18].
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.19.2 Obtaining location information for the MWAB	There are multiple options for an LMF to obtain the location information and velocity of the MWAB(s): - The LMF can derive the location and velocity of the MWAB by using NRPPa or by requesting the GMLC in MWAB Broadcasted PLMN to derive the location of the MWAB-UE using the UE-ID of the MWAB-UE. The GMLC in MWAB Broadcasted PLMN requests the location of the MWAB-UE by requesting the GMLC in MWAB-UE HPLMN which is responsible to trigger MT-LR procedure as specified in clause 6.1.1 or clause 6.1.2 or requests the location of the MWAB-UE by requesting the NEF in the MWAB-UE HPLMN which is responsible to trigger the MT-LR procedure as specified in clause 6.1.2. - As the timing of the location estimations for the Target UE and MWAB(s) is important for the quality of the location estimation of the Target UE, the LMF needs to reduce the timing offset of the positioning measurements, i.e. the positioning of the Target UE and MWAB can be scheduled with using the same scheduled location time and compensate for the potential time difference of the positioning measurements, e.g. taking velocity of MWAB into account.
f07a33accd7fdb2aa929bcb3619e29df	23.273	5.19.3 Privacy check for MWAB	If the positioning of the MWAB is performed for the location estimation of a Target UE different from a MWAB-UE), the privacy check in clause 5.4 is skipped for the MWAB-UE. When the LMF requests the GMLC in MWAB Broadcasted PLMN to derive the location of the MWAB-UE, the LMF includes in the request to the GMLC or the NEF of the HPLMN a MWAB indication indicating the location of MWAB is requested to determine the location of a Target UE in the location request. The GMLC in the MWAB-UE HPLMN receives the MWAB indication from the GMLC of the Broadcasted PLMN or the NEF of the MWAB-UE HPLMN if the location of the MWAB-UE is requested via the NEF. Based on the MWAB indication, the GMLC in MWAB-UE HPLMN skips the privacy check. If the positioning of the MWAB-UE is performed for the location estimation of the MWAB-UE itself the UE privacy check procedure in clause 5.4 is performed.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6 Location Service Procedures
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1 5GC-MT-LR Procedure
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1.1 5GC-MT-LR procedure for the regulatory location service	Figure 6.1.1-1 illustrates the general network positioning for the LCS clients external to the PLMN for the regulatory location service for non-roaming scenario. In this scenario, it is assumed that the target UE is identified using an SUPI or GPSI. This procedure is applicable to a request from an LCS client for a current location of the target UE, and it is assumed that the LCS client is authorised to use the location service and no privacy verification is required. Figure 6.1.1-1: 5GC-MT-LR procedure for the regulatory location service 1. The external location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. The request may include the required QoS, UE unaware indication and Supported GAD shapes. If location is required for more than one UE, the steps following below may be repeated and in that case the GMLC shall verify whether the number of Target UEs in the LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If Maximum Target UE Number is exceeded, the GMLC shall reject the LCS request, the step 2-10 are skipped, and then GMLC respond to the client with proper error cause in the step 11. 2. The GMLC invokes a Nudm_UECM_Get service operation towards the home UDM of the target UE to be located with the GPSI or SUPI of this UE. 3. The UDM returns the network addresses of the current serving AMF. NOTE: For backward compatibility, the GMLC can use a Nudm_SDM_Get service operation to retrieve the SUPI of the target UE from a Rel-15 UDM as defined in clause 5.2.3.3.2 of TS 23.502 [19]. 4. The GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, and client type and may include the required QoS, UE unaware indication and Supported GAD shapes. 5. If the UE is in CM IDLE state and UE unaware indication is not included, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. If UE unaware indication is received by AMF, and the UE is in CM_IDLE state or in RRC_INACTIVE state (if known by AMF by requesting the NG-RAN to report RRC state information), the steps 6 - 9 are skipped. 6. The AMF selects an LMF based on the available information as defined in clause 5.1 or based on AMF local configuration. The LMF selection takes the 5G-AN currently serving the UE into account. The selection may use a NRF query. 7. The AMF invokes the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the serving cell identity of the Primary Cell in the Master RAN node and the Primary Cell in the Secondary RAN node when available based on Dual Connectivity scenarios, and the client type and may include an indication if UE supports LPP, the required QoS, UE Positioning Capability if available, UE unaware indication and Supported GAD shapes. If any of the procedures in clause 6.11.1 or clause 6.11.2 are used the service operation includes the AMF identity. 8. The LMF performs one or more of the positioning procedures described in clauses 6.11.1, 6.11.2 and 6.11.3. During this step the LMF may use the Namf_Communication_N1N2MessageTransfer service operation to request the transfer of a Positioning related N1 message to the UE or the transfer of a Network Positioning message to the serving NG-RAN node (gNB or NG-eNB) for the UE. The LMF shall determine a geographical location and optionally a location in local coordinates. If UE unaware indication is received from AMF in step 7, the LMF selects Uplink Positioning method to obtain UE location and performs the positioning procedure described in clause 6.11.2. 9. The LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the UE and UE Positioning Capability if the UE Positioning Capability is received in step 8 including an indication that the capabilities are non-variable and not received from AMF in step 7. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. If UE unaware indication is received from AMF in step 7 and the NG-RAN rejects the Network Positioning message as described in clause 6.11.2 with appropriate rejection cause (e.g. UE cannot be paged) in step 8, the LMF rejects the Nlmf_Location_DetermineLocation Request with appropriate rejection cause (e.g. UE cannot be paged). 10. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the GMLC/LRF to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. The AMF stores the UE Positioning Capability in UE context when received from LMF. If the AMF decides to skip steps 5 - 9 in step 5 based on the UE unaware indication and the UE state or the LMF rejects the Nlmf_Location_DetermineLocation Request with appropriate rejection cause (e.g. UE cannot be paged), the AMF may convert any last known location in the form of a cell ID or TAI into geographical information based on TS 23.032 [8] and as defined in clause 6.2.6.2.5 of TS 29.518 [16] and clauses 5.4.4.7, 5.4.4.8 and 5.4.4.9 of TS 29.571 [33] and answer to the GMLC with the geographical information together with the age of this location. 11. The GMLC sends the location service response to the external location services client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1.2 5GC-MT-LR Procedure for the commercial location service	Figure 6.1.2-1 illustrates the general network positioning requested by the LCS clients, the AF or the NF (e.g. NWDAF). In this scenario, it is assumed that the target UE may be identified using an SUPI or GPSI. This procedure is applicable to a request from an LCS client, an NF or an AF for a current location of the target UE, and it is assumed that - Privacy verification may be required for the location service request; - The LCS client, or the AF or NF needs to be authorised to use the location service. Figure 6.1.2-1: 5GC-MT-LR Procedure for the commercial location services 1. The LCS Client, the NF or the AF (via NEF) sends a request to the (H)GMLC for a location and optionally a velocity for the target UE which may be identified by an GPSI or an SUPI. The request may include the required QoS, supported GAD shapes and other attributes. (H)GMLC (for 1a, 1c) or NEF (for 1b) authorizes the LCS Client, the NF or the AF for the usage of the LCS service. If the authorization fails, step 2-23 are skipped and (H)GMLC (for 1a, 1c) or NEF (for 1b) responds to the LCS Client, the NF or the AF the failure of the service authorization in step 24. In some cases, the (H)GMLC derives the GPSI or SUPI of the target UE and possibly the QoS from either subscription data or other data supplied by the LCS Client, the NF or the AF. The LCS request may carry also the Service Identity (see TS 22.071 [2]) and the Codeword and the service coverage information. The (H)GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client or AF. If the service identity does not match one of the service identities for the LCS client or AF, the (H)GMLC shall reject the LCS request. Otherwise, the (H)GMLC can map the received service identity in a corresponding service type. The LCS service request may include a scheduled location time if a current location of the UE is required at a specific time in the future. The LCS service request may include integrity requirements including Time-to-Alert (TTA), Target Integrity Risk (TIR) and Alert Limit(AL). Definitions of these parameters are specified in TS 38.305 [9]. NOTE 1: In this release of specification, integrity requirements are for GNSS integrity and RAT-dependent integrity. The applicable positioning methods for RAT-dependent integrity are specified in TS 38.305 [9]. If the LCS service request contains the pseudonym of the target UE and the (H)GMLC cannot resolve the PMD address from the pseudonym, the (H)GMLC itself determines the verinym (GPSI or SUPI) of the target UE. If the (H)GMLC can resolve the address of PMD from the pseudonym, the HGMLC requests the verinym from its associated PMD. If (H)GMLC is not able to obtain the verinym of the target UE, the (H)GMLC shall cancel the location request. If a scheduled location time is not included and the requested type of location is "current or last known location" and the requested maximum age of location information is available, the (H)GMLC verifies whether it stores the previously obtained location estimate of the target UE. If the HGMLC stores the location estimate and timestamp of the location estimate (if available) and the location estimate satisfies the requested accuracy and the requested maximum age of location, the (H)GMLC checks the result of the privacy check at step 2. If the result of the privacy check for call/session unrelated class is "Location allowed without notification" then steps 3-23 may be skipped. 1b-1 AF sends the Nnef_EventExposure_Subscribe to the NEF. 1b-2 The NEF identifies based on the QoS attribute received from the location request that higher than cell-ID level location accuracy is required and invokes the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC, which contains the attributes received from the AF request. The NEF may also invoke the Ngmlc_Location_ProvideLocation_Request service operation to the (H)GMLC for lower than cell-ID location accuracy as an implementation option or if a scheduled location time is included. 1c. The NF (e.g. NWDAF) invokes the Ngmlc_Location_ProvideLocation service operation to the (H)GMLC. If location is required for more than one UE, the steps following below may be repeated and in that case the NEF or HGMLC receiving location request, shall verify whether the number of Target UEs in the Nnef_EventExposure_Subscribe, Ngmlc_Location_ProvideLocation or LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If Maximum Target UE Number is exceeded, the NEF or HGMLC shall reject the Nnef_EventExposure_Subscribe, Ngmlc_Location_ProviceLocation or LCS request, the steps 2-23 are skipped, and then GMLC respond to the client with proper error cause in the step 24. NOTE 2: If cell-ID level or lower than cell-ID level location accuracy is required in the location request, the NEF may invoke an Namf_EventExposure_Subscribe service operation to subscribe location event reporting from the AMF for the target UE as further described in clause 6.5. 2. The (H)GMLC invokes a Nudm_SDM_Get service operation towards the UDM of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the target UE Privacy setting of the UE. The (H)GMLC checks the UE LCS privacy profile. If the target UE is not allowed to be located, steps 3-23 are skipped. The UDM may also reply (H)GMLC with an LPHAP indication, if stored in the UE LCS subscriber data. 3. The (H)GMLC invokes a Nudm_UECM_Get service operation towards the UDM of the target UE with GPSI or SUPI of this UE. The UDM returns the network addresses of the current serving AMF and additionally the address of a VGMLC (for roaming case). If the location request is an immediate location request, the (H)GMLC checks the country codes of the serving node addresses. If the (H)GMLC finds the current AMF is out of the service coverage of the (H)GMLC, the (H)GMLC returns an appropriate error message to the LCS client, the NF or the AF (via NEF). GMLC may determine the LMF ID based on the LCS data for an LCS Client/AF. In case a group ID is provided or derived from the location request, GMLC determines the LMF ID based on the provisioned Group ID. GMLC may be configured with an LMF ID, irrelevant to any LCS client/AF. When the GMLC receives a MT location request from LCS client/AF, GMLC determines the LMF ID for all LCS client/AF. NOTE 3: The UDM is aware of the serving AMF address at UE registration on an AMF as defined in clause 4.2.2.2.2 of TS 23.502 [19]. The UDM is aware of a serving VGMLC address at UE registration on an AMF as defined in clause 4.2.2.2.2 of TS 23.502 [19]. NOTE 4: The HGMLC can also query the HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271 [4]. The EPC-MT-LR procedure described in clause 9.1.15 of TS 23.271 [4], excluding the UE availability event, may then be performed instead of steps 4-23, e.g. if the HSS returns an MME address but the UDM does not return an AMF address. 4. For a non-roaming case, this step is skipped. In the case of roaming, the HGMLC may receive an address of a VGMLC (together with the network address of the current serving AMF) from the UDM in step 3, otherwise, the HGMLC may use the NRF service in the HPLMN to select an available VGMLC in the VPLMN, based on the VPLMN identification contained in the AMF address received in step 3. The HGMLC then sends the location request to the VGMLC by invoking the Ngmlc_Location_ProvideLocation service operation towards the VGMLC. In the cases when the HGMLC did not receive the address of the VGMLC, or when the VGMLC address is the same as the HGMLC address, or when both PLMN operators agree, the HGMLC sends the location service request message to the serving AMF. In this case, step 4 is skipped. If the result of privacy check indicates that the verification based on current location is needed, the HGMLC shall send a location request to the VGMLC (in the case of roaming) or to the AMF (in the case of non-roaming) indicating "positioning allowed without notification" and VGMLC shall invoke an Namf_Location_ProvidePositioningInfo Request service operation towards the AMF at step 5. H-GMLC also provides the LCS client type of AF, if received in step 41b‑2, or LCS client type of LCS client and other attributes to be sent to AMF in step 5. 5. In the case of roaming, the VGMLC first authorizes that the location request is allowed from this HGMLC, PLMN or from this country. If not, an error response is returned. The (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI, the client type and may include the required LCS QoS, supported GAD shapes, scheduled location time, service type and other attributes as received or determined in step 1. If received in step 2, the (H)GMLC or VGMLC provides the LPHAP indication to the AMF. To support location service in PNI-NPN with signalling optimisation, the H-GMLC also includes a contact address (Notification Target Address, e.g. a URI) and a Notification Correlation ID, which is used by LMF to provide location determination to H-GMLC directly. NOTE 5: The location request forwarded at step 4 and step 5 may also carry the result of the privacy check in step 2 which may include a codeword provided by the LCS Client or AF and an indication of a privacy related action as described in clause 5.4. 6. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. If signalling connection establishment fails, step 7-13 are skipped and the AMF answers to the GMLC in step 14 with the last known location of the UE (i.e. Cell ID) together with the age of this location. 7. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification and if the UE supports LCS notification (according to the UE capability information), a notification invoke message is sent to the target UE, indicating the identity of the LCS client and the , service type (if that is both supported and available) and whether privacy verification is required. 8. The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the AMF indicating, if privacy verification was requested, whether permission is granted or denied for the current LCS request. If the UE user does not respond after a predetermined time period, the AMF shall infer a "no response" condition. The AMF shall return an error response in step 14 and if roaming VGMLC in step 15 to the HGMLC if privacy verification was requested and either the UE user denies permission or there is no response with the indication received from the (H)GMLC indicating barring of the location request and steps 10~13 are skipped. The notification result may also indicate the Location Privacy Indication setting for subsequent LCS requests; i.e whether subsequent LCS requests, if generated, will be allowed or disallowed by the UE. The Location Privacy Indication may also indicate a time for disallowing the subsequent LCS requests. 9. The AMF invokes the Nudm_ParameterProvision_Update (LCS privacy) service operation to store in the UDM the Location Privacy Indication information received from the UE. The UDM may then store the updated UE privacy setting information into the UDR as the "LCS privacy" Data Subset of the Subscription Data. 10-13. Step 10-13 are the same as steps 6-9 defined in clause 6.1.1 with the addition that LMF can also perform 6.11.4 as positioning procedure and service type may be indicated towards the LMF and the exception that the LMF may determine the UE location in local coordinates or geographical co-ordinates or both. If the supported GAD shapes is not received in step 11 or Local Co-ordinates is not included in the supported GAD shapes, the LMF shall determine a geographical location. If a scheduled location time is provided at step 5, steps 11 and 12 include the following additional differences. 11. The AMF includes the scheduled location time in the Nlmf_Location_DetermineLocation service operation sent towards the LMF. If received in step 5, the AMF provides the LPHAP indication to the LMF. If H-GMLC contact address is received in step 5, AMF also includes the H-GMLC contact address and the Notification Correlation ID in the Nlmf_Location_DetermineLocation service operation and sends towards the LMF. Based on UE user plane positioning capabilities, if the target UE supports the UE user plane positioning capability for LCS-UPP, the AMF shall provide the SUPI and/or GPSI of the target UE (see TS 29.572 [12]) as UE identity in the Nlmf_Location_DetermineLocation Request. NOTE 6: In this case, the AMF ensures that a consistent UE identity is used for a particular LMF by implementation. 12. If received in step 11 of the LPHAP indication, the LMF may determine an appropriate positioning method by taking into account the LPHAP indication. When sending a location request to the UE, the LMF may include the scheduled location time. NOTE 7: If integrity requirements are received in step 11, LMF may determine to use GNSS positioning method and RAT-dependent positioning method. The applicable positioning methods for RAT-dependent integrity are specified in TS 38.305 [9]. NOTE 8: LMF does not deliver the scheduled location time to NG-RAN as part of step 12. NOTE 9: The LMF may send a location request to the UE at step 12 containing the scheduled location time sometime before the scheduled location time to allow the UE to enter CM Connected state shortly before the scheduled location time. If H-GMLC contact address and the Notification Correlation ID is received in step 11, the LMF responds to AMF in the Nlmf_location_determineLocation Response to indicate that the location determination will be sent directly to GMLC. In this case, the LMF determines to use local AMF for obtaining Non-UE Associated Network Assistance Data, as described in clause 6.11.3. When LMF determines the UE location, it executes the step 28 as described in clause 6.3.1. 14. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. If indicated in step 13 that the location determination will be sent directly to GMLC, AMF responds to GMLC with Namf_location_providePositioningInfo Response to indicate that GMLC will receive the location from LMF directly. 15. In the case of roaming, the VGMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method received at step 14 to the HGMLC. For non-roaming scenario, this step is skipped. 16. If the privacy check in step 2 indicates that further privacy checks are needed, the (H)GMLC shall perform an additional privacy check in order to decide whether the (H)GMLC can forward the location information to the LCS client or AF or send a notification if the result of the privacy check requires the notification and verification based on current location. One example when this additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations. When an additional privacy check is not needed, the (H)GMLC skips steps 17-23. 17. If the result of privacy checks in step 16 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the (H)GMLC shall send a location request to the VGMLC with location type indicating "notification only". 18. The (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request notification (and verification) based on current location. 19. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. 20. If the indicator of privacy check related action indicates that the UE must either be notified or notified with privacy verification and if the UE supports LCS notification, the AMF sends a notification invoke message to the target UE, indicating the identity of the LCS client and the service type (if that is both supported and available) and whether privacy verification is required. 21. Step 21 is the same as step 8. 22. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the (V)GMLC (or HGMLC for roaming when the NL3 reference point is not supported) with an indication of the result of notification and verification procedure performed in steps 20-21. 23. In the case of roaming, the VGMLC forwards an indication of the result of notification and verification procedure to the HGMLC. For non-roaming scenario, this step is skipped. 24. The (H)GMLC sends the location service response to the LCS Client, the NF or the AF (via the NEF) if the target UE is allowed to be located by the LCS Client, the NF or the AF. Accordingly, NEF invokes Nnef_EventExposure_Notify or sends Nnef_EventExposure_Subscribe Response to the AF. If the location request from the LCS Client contained the pseudonym and the (H)GMLC resolved the verinym from the pseudonym in step 1, the (H)GMLC shall use the pseudonym of the target UE in the location response to the external LCS client. If the external LCS client or AF requires it, the (H)GMLC may first transform the universal location co-ordinates provided by the AMF into some local geographic reference system. The (H)GMLC may record charging information both for the LCS Client or AF and inter-network revenue charges from the AMF's network. The location service response from the (H)GMLC to the LCS Client, the NF or the AF may contain the information about the positioning method used and the indication whether the obtained location estimate satisfies the requested accuracy or not. If in step 2, step 15, step 16 or step 23 the (H)GMLC identifies that the target UE is not allowed to be located by the LCS Client, the NF or the AF, it rejects the LCS service request, and optionally indicate in the response the reason of the rejection, i.e. the target UE is not allowed to be located. If the LCS QoS Class is Assured and (H)GMLC detects that requested accuracy is not achieved, the (H)GMLC sends error response including failure cause.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1.3 5GC-MT-LR multiple location procedure for the regulatory location service	Figure 6.1.3-1 illustrates an extension procedure of 5GC-MT-LR procedure for the regulatory location service defined in clause 6.1.1. This procedure is applicable for providing multiple location estimates of the target UE to LCS client. Figure 6.1.3-1: 5GC-MT-LR multiple location procedure for the regulatory location service 1. Steps 1-7 for 5GC-MT-LR procedure for the regulatory location service clause 6.1.1 are performed with the following differences: - At step 1 in clause 6.1.1 the request from external location services client may include acceptance of INTERMEDIATE response and maximum response time. - At step 4 in clause 6.1.1 Namf_Location_ProvidePositioningInfo service operation invoked by GMLC may include the acceptance of INTERMEDIATE response and maximum response time, GMLC contact address and LIR reference number. The LIR reference number is allocated by GMLC based on predefined rule. - At step 7 in clause 6.1.1 Nlmf_Location_DetermineLocation service operation invoked by AMF may include additionally include acceptance of INTERMEDIATE response and maximum response time, GMLC contact address, LIR reference number for the INTERMEDIATE response. AMF can overwrite maximum response time to avoid timeout. 2. LMF performs positioning procedures and determines multiple location estimates during the session. 2.1. This step is executed if the INTERMEDIATE result is available. The LMF invokes an Nlmf_Location_EventNotify service operation towards GMLC and provides the INTERMEDIATE location of the UE during the session and timestamp of the location estimate, and LIR reference number, and INTERMEDIATE event type. 2.2. This step is executed if step 2.1 was executed. The GMLC sends the INTERMEDIATE location of the UE and timestamp of the location estimate to external location services client. 3. Based on step 9 in clause 6.1.1 the LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the FINAL location of the UE. LMF ensures that FINAL location will be transferred towards AMF within the maximum response time. 4. Steps 10-11 for 5GC-MT-LR procedure for the regulatory location service clause 6.1.1 are performed with the following differences: - At step 11 the FINAL location is sent from GMLC to LCS client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1.4 5GC-MT-LR procedure involving Mobile Base Station Relay	Figure 6.1.4-1 illustrates the network positioning for the LCS clients when Mobile Base Station Relay(s) is involved. In this scenario, it is assumed that the target UE may be identified using an SUPI or GPSI. The procedure follows the functionality in clause 5.9 and the 5G-MT-LR procedures in clauses 6.1.1 and 6.1.2. It is further assumed that: - The NG-RAN in figure 6.1.4-1 is a donor-CU to the MBSR. - When the MBSR is integrated or fully migrated to a new gNB, the OAM triggers the LMF to perform TRP Information Exchange procedure. The LMF learns that a new integrated TRP at a gNB is mobile and its MBSR IAB UE ID (GPSI) via a TRP information exchange towards the gNB with the Cell ID of the TRP. The LMF may also performs NRPPa TRP information exchange procedure before the positioning procedure for a target UE, e.g. to determine the position capability of NG-RAN. - The LMF that performs the location estimation of the MBSR can be different than the LMF that performs the location estimation of the target UE (not shown in figure 6.1.4-1). Figure 6.1.4-1: 5GC-MT-LR procedure involving Mobile Base Station Relay 1. [Optional] The location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or an SUPI. The UE may or may not be served by a MBSR. 2. The GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF serving the target UE to request the current location of the target UE. The location procedure may be also triggered at the AMF for a 5GC-NI-LR as at step 1 in clause 6.10.1, or an event report sent by the UE for a deferred 5GC-MT-LR for periodic or triggered location as at step 25 in clause 6.3.1. 3. The 5GC-MT-LR procedure as specified in clause 6.1.1 step 5-8 or clause 6.1.2 step 6-12 are performed with the difference that the LMF selection also consider LMF capability supporting MBSR involvement. If the AMF is aware that the target UE is served by a MBSR, it would select the LMF that can support the MBSR handling. NOTE 1: The step 4 to 11 may happen as part of step 3. 4. LMF derives if any MBSR(s) is involved in the positioning of the target UE based on the cell-ID used for positioning measurements in the step 3. The AMF serving the target UE may indicate that the serving cell is an MBSR (if applicable). When the MBSR was integrated as a TRP (IAB-DU) with a gNB, the LMF may determine from in a TRP information exchange procedure that the cell-ID belongs to the MBSR and/or the UE-ID (GPSI) associated with MBSR. The LMF, when the OAM provides a new Cell Id to the LMF, performs a TRP information exchange as specified in TS 38.455 [15] for the new Cell ID. When the MBSR is integrated or fully migrated in the NG-RAN, the Cell ID(s) of the MBSR is (are)provided to the LMF and, in the case of full migration, any stale Cell ID of fully migrated MBSR is removed from LMF by OAM. If the LMF selects any cell for UE positioning measurements, and the LMF determines it needs to perform a TRP information exchange with the cell, it shall perform TRP Information Exchange procedure as specified in TS 38.455 [15].As the MBSR can be mobile the LMF may need to determine an updated location of the MBSR by either performing step 5-7 (option 1) or performing step 8-10 (option 2) if option 1 is not feasible. If several MBSRs were derived, then step 5-7 or step 8-10 are be performed for each MBSR. NOTE 2: It is assumed that for the case of MBSR's inter CU mobility, the OAM can timely update the Cell Id of the MBSR to the LMF so as to enable it to perform a proper TRP information exchange. Until the Cell Id of the MBSR is provided to LMF by OAM, the Cell of the MBSR is not used for location procedures. 5. [Conditional] The LMF initiates a NRPPa TRP Information Exchange procedure to request the updated location information of the TRP(s) associated with MBSR(s) by directing the TRP information exchange messages to the gNB associated with the Cell ID(s), for example, by setting the NRPPa TRP Information Type Item IE to "mobile TRP location info". Donor-CU further send a F1 TRP INFORMATION REQUEST message to any MBSR IAB-DU. 6. [Conditional] The MBSR IAB-UE initiates a 5GC-MO-LR procedure (as defined in clause 6.2) to get its location information. The MBSR IAB-UE's location info is used by the co-located MBSR IAB-DU to determine the updated location for its TRP. 7. [Conditional] The MBSR IAB-DU report its updated TRP location, e.g. TRP's geo-coordinate, velocity and the time for obtaining them, to the Donor-CU, which is further forwarded to LMF. 8. [Conditional] The LMF invokes the Ngmlc_Location_ProvideLocation_Request service operation to the GMLC by providing the identifier of MBSR IAB-UE and a scheduled location time. The LMF determines the identifier of MBSR IAB-UE based on the Cell ID of MBSR and the received the GPSI of the MBSR in a TRP information exchange when the MBSR was integrated as a TRP. LMF may receive the scheduled location time in step 3. Otherwise, LMF may generate the scheduled location time, e.g. based on response time. 9. [Conditional] The GMLC determines the AMF serving the MBSR and step 4-10 in clause 6.1.1 or steps 4-23 in clause 6.1.2 is performed. The privacy check in clause 5.4 is skipped for the MBSR based on the subscription data of the MBSR (IAB-UE). The scheduled location time received in step 8 is also provided to the MBSR IAB-UE when sending a location request to the MBSR. 10. [Conditional] The GMLC sends the location service response including the MBSR IAB-UE's location to the LMF. 11. [Conditional] The LMF performs one of the positioning procedures with the target UE described in clauses 6.11.1 and 6.11.2. To reduce the timing offset of the positioning measurements, the UE positioning may be scheduled with the same scheduled location time as the MBSR positioning in step 9. LMF sends the same time with the scheduled location time in step 8 to the target UE in clause 6.11.1. If Network Assisted procedure is used, the NG-RAN may provide the MBSR updated location and velocity information and the time obtained them to the LMF via NRPPa message as defined in TS 38.455 [15]. 12. The LMF uses the received location and velocity of the MBSR(s) when estimating the location of the target UE together with the measurements reports in step 3 or optionally the updated measurement reports in step 11. 13. The LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the target UE. 14. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the GMLC to return the current location of the target UE. 15. The GMLC sends the location service response to the location services client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.1.5 5GC-MT-LR procedure involving MWAB	Figure 6.1.5-1 illustrates the network positioning requested by the LCS clients when MWAB(s) is involved. In this scenario, it is assumed that the target UE may be identified using an SUPI or GPSI. The procedure follows the functionality in clause 5.19 and the 5G-MT-LR procedures in clauses 6.1.1 and 6.1.2. It is further assumed that: - The NG-RAN in figure 6.1.5-1 is a MWAB-gNB. - When the MWAB-gNB is integrated to the 5GS, the OAM triggers the LMF to perform TRP Information Exchange procedure. The LMF learns that a new integrated TRP at a MWAB-gNB is mobile and its UE ID (GPSI) of the MWAB-UE via a TRP information exchange towards the MWAB-gNB with the Cell ID of the TRP. The LMF may also performs NRPPa TRP information exchange procedure before the positioning procedure for a target UE, e.g. to determine the position capability of NG-RAN. - The LMF that performs the location estimation of the MWAB (MWAB-UE) can be different (e.g. even in different PLMN) than the LMF that performs the location estimation of the target UE (not shown in figure 6.1.5-1). Figure 6.1.5-1: 5GC-MT-LR procedure involving MWAB NOTE 1: In this procedure one MWAB is assumed, however multiple MWABs could be involved (in which case the steps of location of MWAB are repeated for each involved MWAB). 1. The location services client sends a request to the (H)GMLC for a location for the target UE identified by an GPSI or an SUPI. The UE may or may not be served by a MWAB. 2. If the UE was roaming in the Broadcasted PLMN, the (H)GMLC of the target UE requests the Broadcasted PLMN GMLC to provide the UE location by a Ngmlc_Location_ProvideLocation_Request. Otherwise the GMLC of the Broadcasted PLMN and the (H)GMLC of the target UE are the same. 3. The GMLC in MWAB Broadcasted PLMN invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF serving the target UE to request the current location of the target UE. The location procedure may be also triggered at the AMF for a 5GC-NI-LR as at step 1 in clause 6.10.1, or an event report sent by the UE for a deferred 5GC-MT-LR for periodic or triggered location as at step 25 in clause 6.3.1. 4. The 5GC-MT-LR procedure as specified in clause 6.1.1 step 5-8 or clause 6.1.2 step 6-12 are performed with the difference that the LMF selection also consider LMF capability supporting MWAB involvement. If the AMF is aware that the target UE is served by a MWAB, it would select the LMF that can support the MWAB handling. NOTE 1: The steps 5 to 12 may happen as part of step 4. 5. LMF derives if any MWAB(s) is involved in the positioning of the target UE based on the cell-ID used for positioning measurements in the step 4. The AMF serving the target UE may indicate that the serving cell is an MWAB (if applicable). When the MWAB-gNB was integrated as a TRP, the LMF may determine from in a TRP information exchange procedure that the cell-ID belongs to the MWAB and/or the UE-ID (GPSI) associated with MWAB-UE. The LMF, when the OAM provides a new Cell Id to the LMF, performs a TRP information exchange as specified in TS 38.455 [15] for the new Cell ID. When the MWAB-gNB is integrated in the 5GS, the Cell ID(s) of the MWAB is (are)provided to the LMF. If the LMF selects any cell for UE positioning measurements, and the LMF determines it needs to perform a TRP information exchange with the cell, it shall perform TRP Information Exchange procedure as specified in TS 38.455 [15].As the MWAB can be mobile the LMF may need to determine an updated location of the MWAB by either performing steps 6-8 (option 1) or performing steps 9-11 (option 2) if option 1 is not feasible. NOTE 2: It is assumed that for the case of MWAB mobility, the OAM can timely update the Cell Id of the MWAB to the LMF so as to enable it to perform a proper TRP information exchange. Until the Cell Id of the MWAB is provided to LMF by OAM, the Cell of the MWAB is not used for location procedures. 6. [Conditional] The LMF initiates a NRPPa TRP Information Exchange procedure to request the updated location information of the TRP(s) associated with MWAB(s) by directing the TRP information exchange messages to the MWAB-gNB associated with the Cell ID(s), for example, by setting the NRPPa TRP Information Type Item IE to "mobile TRP location info". 7. [Conditional] The MWAB-UE may initiate a 5GC-MO-LR procedure (as defined in clause 6.2) to get its location information if requested by MWAB-gNB based on implementation. The MWAB-UE's location info is used by the co-located MWAB-gNB to determine the updated location for its TRP. 8. [Conditional] The MWAB-gNB report its updated TRP location, e.g. TRP's geo-coordinate, velocity and the time for obtaining them, to the LMF. 9. [Conditional] If the LMF invokes the Ngmlc_Location_ProvideLocation_Request service operation to the GMLC in MWAB Broadcasted PLMN by providing the identifier of MWAB-UE, a MWAB Indication indicating the location request is for a MWAB-UE and a scheduled location time. The LMF determines the identifier of MWAB-UE based on the Cell ID of MWAB-gNB and the received the GPSI of the MWAB-UE in a TRP information exchange when the MWAB-gNB was integrated as a TRP. LMF may receive the scheduled location time in step 4. Otherwise, LMF may generate the scheduled location time, e.g. based on response time. 10. [Conditional] The GMLC in BH PLMN determines the AMF serving the MWAB-UE and steps 5-11 in clause 6.1.1 or steps 4-23 in clause 6.1.2 is performed. The privacy check in clause 5.4 is skipped for the MWAB based on the MWAB Indication received at step 9. The scheduled location time received in step 9 via the LMF is also provided to the MWAB-UE when sending a location request to the MWAB-UE. When the MWAB-UE is roaming, the GMLC of the UE may further retrieve the location information of the MWAB-UE via the GMLC (or, not shown in this message flow, the NEF) in MWAB-UE Broadcasted PLMN which is responsible to retrieve the location information of the MWAB-UE via the GMLC in BH PLMN, based on the information retrieved from UDM of the MWAB-UE (i.e. the serving AMF address and the GMLC address serving the MWAB-UE in BH PLMN). 11. [Conditional] The GMLC in MWAB Broadcasted PLMN sends the location service response including the MWAB-UE's location to the LMF of the broadcasted PLMN. When the MWAB-UE is roaming, the GMLC in MWAB Broadcasted PLMN receives the location response from the GMLC or NEF in MWAB-UE HPLMN. 12. [Conditional] The LMF performs one of the positioning procedures with the target UE described in clauses 6.11.1 and 6.11.2. To reduce the timing offset of the positioning measurements, the UE positioning may be scheduled with the same scheduled location time as the MWAB-UE positioning in step 10. LMF sends the same time with the scheduled location time in step 9 to the target UE in clause 6.11.1. If Network Assisted procedure is used, the MWAB-gNB may provide the MWAB-UE updated location and velocity information and the time obtained them to the LMF via NRPPa message as defined in TS 38.455 [15]. 13. The LMF uses the received location and velocity of the MWAB when estimating the location of the target UE together with the measurements reports in step 4 or optionally the updated measurement reports in step 12. 14. The LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the target UE. 15. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the GMLC to return the current location of the target UE. 16. If the target UE was roaming in the Broadcasted PLMN, the GMLC of the Broadcasted PLMN responds to the (H)GMLC of the UE to provide the target UE location in a Ngmlc_Location_ProvideLocation_Response. Otherwise the GMLC of the Broadcasted PLMN and the (H)GMLC of the UE are the same. 17. The (H)GMLC of the target UE sends the location service response to the location services client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.2 5GC-MO-LR Procedure	Figure 6.2-1 illustrates the general network positioning requested by the UE to the serving PLMN for obtaining the location related information of itself or just assistance data. Figure 6.2-1: 5GC-MO-LR Procedure 1) If the UE is in CM-IDLE state, UE instigates the UE triggered Service Request as defined in clause 4.2.3.2 of TS 23.502 [19] in order to establish a signalling connection with the AMF. 2) The UE sends an MO-LR Request message included in a UL NAS TRANSPORT message. The MO-LR Request may optionally include up to three LPP positioning message(s). Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an LCS client or AF, or location assistance data. If the UE is requesting its own location or that its own location be sent to an LCS client or AF, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location, the requested type of location (e.g. "current location", "current or last known location") and, optionally for a current location, a scheduled location time. If the UE is requesting that its location be sent to an LCS client, the message shall include the identity of the LCS client or the AF, and may include the address of the GMLC through which the LCS client or AF (via NEF) should be accessed. In addition, a Service Type indicates which MO-LR service of the LCS Client is requested by the UE may be included. The message also may include a pseudonym indicator to indicate a pseudonym should be assigned by the network and transferred to the LCS Client as the UE's identity. The message may also include integrity requirements including Time-to-Alert (TTA), Target Integrity Risk (TIR) and Alert Limit(AL). Definitions of these parameters are specified in TS 38.305 [9]. NOTE 1: In this release of specification, integrity requirements are for GNSS integrity and RAT-dependent integrity. The applicable positioning methods for RAT-dependent integrity are specified in TS 38.305 [9]. If the UE is instead requesting location assistance data, the embedded LPP message specifies the type of assistance data and the positioning method for which the assistance data applies. For an LCS 5GC-MO-LR requesting location transfer to an LCS Client or AF, the AMF shall assign a GMLC address, i.e. VGMLC address, which is stored in the AMF. If a VGMLC address is not available, the AMF may reject the location request. The AMF verifies the subscription profile of the UE and decides if the requested service is allowed or not by checking the Mobile Originated data retrieved from UDM during the UE Registration Procedure, as defined in clause 4.2.2.2.2 of TS 23.502 [19]. If the requested type of location is "current or last known location" and the requested maximum age of location information is available, the AMF verifies whether it stores the previously obtained location estimate and related timestamp (if available) of the target UE. If the AMF stores the location estimate and the related timestamp (if available) and the location estimate satisfies the requested accuracy and the requested maximum age of the location, the AMF skips steps 3 - 6. 3) The AMF selects an LMF as described in clause 5.1. AMF may be configured locally a mapping table of UE identity e.g. MSISDN and LMF address. When receiving a MO-LR, AMF determines LMF based on local configuration or by retrieving from UDM in the UE LCS subscriber data. If the AMF is aware that the UE is served by a MBSR or MWAB, it would select the LMF that can support the MBSR or MWAB handling. 4) The AMF invokes the Nlmf_Location_DetermineLocation service operation towards the LMF. The service operation includes an LCS Correlation identifier, the serving cell identity, the client type, an indication whether a location estimate, or location assistance data is requested, UE Positioning Capability if available, a list of MO-LR subscribed assistance data and any embedded LPP message(s) in the MO-LR Request. If the UE's location is requested, the service request may include an indication if UE supports LPP, the requested QoS, Supported GAD shapes and any scheduled location time. If location assistance data is requested, the embedded LPP message(s) will convey the requested types of location assistance data. If any of the procedures in clause 6.11.1 or 6.11.2 are used the service operation includes the AMF identity. Once an AMF has selected an LMF it must continue to use that LMF for the duration of the session. To support location service in PNI-NPN with signalling optimisation, the AMF also includes a contact address (Notification Target Address, e.g. a URI) and a Notification Correlation ID, which is used by LMF to provide location determination to H-GMLC directly. If the AMF is aware that the UE is served by a MBSR or MWAB, it provides the indication to the LMF. Based on UE user plane positioning capabilities, if the target UE supports the UE user plane positioning capability for LCS-UPP, the AMF shall provide the SUPI and/or GPSI of the target UE (see TS 29.572 [12]) as UE identity in the Nlmf_Location_DetermineLocation Request. NOTE 2: In this case, the AMF ensures that a consistent UE identity is used for a particular LMF by implementation. NOTE 3: If the UE is requesting its own location, AMF does not indicate support of a GAD shape for local co-ordinates, see TS 23.032 [8]. 5) If the UE is requesting its own location, the actions described in clause 6.11 are performed together with the actions described for step 12 in clause 6.1.2 if a scheduled location time is present. If the UE is instead requesting location assistance data, the LMF transfers this data to the UE as described in clause 6.11.1. The LMF determines the exact location assistance data to transfer according to the type of data specified by the UE, the UE location capabilities, the MO-LR subscribed assistance data and the current cell. If the LMF is informed that the UE is served by a MBSR, the LMF may perform the operation of clause 6.1.4 step 5 to step 7, or step 8 to step 10, to obtain the MBSR location information. The LMF will take the MBSR location into account when determining the UEs location. If the LMF determines that the UE is served by a MWAB, the LMF may perform the operation of clause 6.1.5 step 5 to step 7, or step 8 to step 10, to obtain the MWAB location information. The LMF will take the MWAB location into account when determining the UE's location. If H-GMLC contact address and the Notification Correlation ID is received in step 11, and the LMF determines to use local AMF for obtaining Non-UE Associated Network Assistance Data, as described in clause 6.11.3, the LMF responds to AMF in the Nlmf_location_determineLocation Response to indicate that the location determination will be sent directly to GMLC. When LMF determines the UE location, it executes the step 28 as described in clause 6.3.1. NOTE 4: If integrity requirements are received in step 4, LMF may determine to use GNSS positioning method and RAT-dependent positioning method. The applicable positioning methods for RAT-dependent integrity are specified in TS 38.305 [9]. 6) When a location estimate best satisfying the requested QoS has been obtained or when the requested location assistance data has been transferred to the UE, the LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF. The service operation includes the LCS Correlation identifier, the location estimate, if this was obtained, its age and accuracy and may include information about the positioning method. If a location estimate was not successfully obtained, or if the requested location assistance data could not be transferred successfully to the UE, a failure cause is included in the service operation. The service operation may also include the UE Positioning Capability if the UE Positioning Capability is received in step 5 including an indication that the capabilities are non-variable and not received from AMF in step 4. If the UE is requesting location assistance data, steps 7 to 12 are skipped. 7) If the location estimate was successfully obtained, the AMF invokes the Ngmlc_Location_LocationUpdate service operation towards to the VGMLC assigned in the step 2. The service operation carries the identity of the UE, the event causing the location estimate (5GC-MO-LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target UE. In addition, the service operation may include the pseudonym indicator, the identity of the LCS Client, AF ID, the GMLC address, the timestamp of the location estimate and the Service Type specified by the UE, if available. 8) If the UE did not request transfer of its location to an LCS Client or AF in step 2, steps 8 to 11 are skipped. If the VGMLC is same NF instance as HGMLC this step is skipped. Otherwise VGMLC invokes the Ngmlc_Location_LocationUpdate service operation towards to the HGMLC (the VGMLC may query the NRF to obtain the address of the HGMLC) including the information received from the AMF. 9a) If the pseudonym indicator is included in the MO-LR Location Information, the HGMLC assigns a pseudonym to the UE. If the identified LCS Client is not accessible by the HGMLC, step 9a and step 10a are skipped. Otherwise the GMLC transfers the location information to the LCS client, carrying the identity or the pseudonym of the UE, the event causing the location estimate (5GC-MO‑LR), the Service Identity, if available, and the location estimate, the timestamp of the location estimate (if available) and its age, in accordance with the LCS QoS Class requested by the target UE. If the UE requested LCS QoS class was Assured, GMLC sends the result to the LCS client only if the result has been indicated to fulfil the requested accuracy. If the UE requested LCS QoS class was Best Effort, GMLC sends whatever result it received to the LCS client with an appropriate indication if the requested accuracy was not met. NOTE 5: The HGMLC maps any Service Type Identity received in step 8 into a Service Identity. 9b-1) If the AF ID is included in step 1, the HGMLC assigns the NEF address based on local configuration or via NRF and invokes Ngmlc_Location_LocationUpdateNotify service request towards the NEF, carrying the AF ID. The location information parameters sent within this service operation are same as the step 9a except that no pseudonym is included. 9b-2) If the identified AF is not accessible by the NEF, step 9b-2 and step 10b-1 are skipped. Otherwise, the NEF transfer the location information to the identified AF by invoking the Nnef_Location_LocationUpdateNotify service. 10a) If the LCS Client does not support MO-LR (for temporary or permanent reasons) or cannot handle the location estimate of the UE, e.g. the LCS Client does not know the Service Identity, or the UE does not register to the LCS Client, the LCS Client has no corresponding data of the UE, the LCS Client shall return the Location Information ack message to the HGMLC with a suitable error cause. Otherwise, the LCS Client handles the location estimate according to the Service Identity, sends the GMLC or the HGMLC the Location Information ack message signalling that the location estimate of the UE has been handled successfully. 10b-1) If the AF cannot handle the location estimate of the UE, e.g. the UE does not register to the AF, the AF has no corresponding data of the UE, the AF shall respond to the Nnef_Location_LocationUpdateNotify service request with a suitable error cause. Otherwise, the AF handles the location estimate according to the Service Identity and respond to the Nnef_Location_LocationUpdateNotify service request indicating that the location estimate of the UE has been handled successfully. 10b-2) The NEF sends a Ngmlc_Location_LocationUpdateNotify service response towards the HGMLC with the outcome of the operation. 11) If the VGMLC is same NF instance as HGMLC this step is skipped. If the identified LCS Client or AF is not accessible, the HGMLC sends a Ngmlc_Location_LocationUpdate service response to VGMLC with an appropriate error cause. Otherwise, the response shall include an acknowledgement. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client or AF, and if not, the corresponding error cause obtained in step 10. In addition, the HGMLC may record charging information both for the UE and inter-working revenues charges. 12) If the VGMLC receives the MO-LR Location Information Acknowledgement from the HGMLC, if the identified LCS Client or AF is not accessible, the VGMLC sends a Ngmlc_Location_LocationUpdate service response to AMF with an appropriate error cause. Otherwise, the response shall include an acknowledgement. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client or AF, and if not, the corresponding error cause obtained in step 9 or 10. In addition, the VGMLC may record charging information both for the UE and inter-working revenue charges. If the VGMLC receives Ngmlc_Location_LocationUpdate Request from the AMF and it is not required to send to any LCS Client or AF, the VGMLC may record charging information for the UE and response the Ngmlc_Location_LocationUpdate Request to the AMF. 13) The AMF sends an MO-LR Response message included in a DL NAS TRANSPORT message. If the UE is requesting its own location, the response carries any location estimate requested by the UE and the timestamp of the location estimate (if available) including the indication received from LMF whether the obtained location estimate satisfies the requested accuracy or not, or an indicator whether a location estimate was successfully transferred to the identified LCS client or AF. If the location estimate was successfully transferred to the identified LCS Client or AF, the MO-LR Response message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client or AF, and if not, the corresponding error cause obtained in step 13. In addition, AMF may record charging information.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3 Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.1 Initiation and Reporting of Location Events	Figure 6.3.1-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic, Triggered and UE Available Location Events. The procedure supports mobility of a UE within a VPLMN 5GCN and from a 5GCN to an EPC. Figure 6.3.1-1: Deferred 5GC-MT-LR for periodic, triggered and UE available location events 1. The external location services client, the NF or the AF (via NEF) sends a request to the (H)GMLC for location reporting for periodic, triggered or UE available location events. The request is sent as described for step 1 in clause 6.1.2 with the differences described here. The LCS Service Request provides the type of periodic or triggered location reporting being requested and associated parameters. For periodic location, the LCS Service Request includes the time interval between successive location reports, the total number of reports and may include location QoS. For periodic location reporting, the LCS Service Request may include a scheduled location time for the first periodic location report. For area event reporting, the LCS Service Request includes details of the target geographical area, an indication to have an additional check whether UE is located within the requested target area, whether the event to be reported is the UE being inside, entering into or leaving the target area, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS), and whether only one location report is required or more than one. If the target area is expressed by a local coordinate system or a geopolitical name, the (H)GMLC shall convert the target area to a geographical area expressed by a shape as defined in TS 23.032 [8]. For motion event reporting, the LCS Service Request includes the threshold linear distance, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS), and whether only one location report is required or more than one. 1b-1 AF invokes the Nnef_EventExposure_Subscribe service operation to the NEF. 1b-2 The NEF forwards the request to the (H)GMLC. The NEF assigns a LDR refence number locally and sends it to (H-)GMLC, 1c. The NF (e.g. NWDAF) invokes the Ngmlc_Location_ProvideLocation service operation to the (H)GMLC. NOTE 1: If the LCS Client/AF requests an additional check about whether the UE is located within the provisioned target area, the LCS Client/AF shall also request that location estimates shall be included in event reports. 2. The (H)GMLC may verify UE privacy requirements as for step 2 in clause 6.1.2. The (H)GMLC may also subscribe to and receive notification of UE privacy profile updates according to steps 0 and 4 of clause 6.12.1. The (H)GMLC may also receive the event report expected area and optionally an area usage indication from UDM. For area event reporting, if there is no overlap between the event report expected area and the area provided by the AF or LCS Client, the (H)GMLC rejects the location request with a failure cause. 3. The (H)GMLC queries the UDM for the AMF address and, in the case of roaming, a VGMLC address as for step 3 in clause 6.1.2. GMLC may determine the LMF ID based on the LCS data for an LCS Client/AF. In case a group ID is provided or derived from the location request, GMLC determines the LMF ID based on the provisioned Group ID. GMLC may be configured with an LMF ID, irrelevant to any LCS client/AF. When the GMLC receives a MT location request from LCS client/AF, GMLC determines the LMF ID for all LCS client/AF. NOTE 2: The HGMLC may also query the HSS of the target UE for a serving MME address as described in clause 9.1.1 of TS 23.271 [4]. The deferred EPC-MT-LR procedure for Periodic and Triggered Location described in clause 9.1.19 of TS 23.271 [4] or the EPC-MT-LR procedure for the UE availability event described in clause 9.1.15 of TS 23.271 [4] may then be performed instead of steps 4-31 - e.g. if the HSS returns an MME address but the UDM does not return an AMF address. 4. This step is skipped for a non-roaming UE. For a roaming UE, the HGMLC obtains a VGMLC address if not received at step 3 and invokes the Ngmlc_Location_Provide Location Request service operation to forward the location request to the VGMLC as described for step 4 of in clause 6.1.2. The (H)GMLC also includes a contact address for the (H)GMLC (Notification Target Address, e.g. a URI) and an LDR reference number (Notification correlation ID) to be used for event reporting at steps 20 and 29. The LDR reference number is either allocated by (H)GMLC based on predefined rule, e.g. operator's policy if the location request is received in step 1a, or allocated by NEF, if the location request is received in step 1b. If the event report expected area is received in step 2, the (H)GMLC is responsible to determine the event report allowed area which includes a cell/TA list based on the event report expected area. In the case of an area event, if there is overlap(s) between the event report expected area and the area provided by the AF or LCS client, the (H)GMLC will separately derive the TA/cell lists and take the overlapped TA/cell lists as the event report allowed area. If the area usage indication is also received in step 2, the (H)GMLC is responsible to determine the reporting indication regarding how the UE will report when the UE is inside or outside the event report allowed area. The (H)GMLC may include the event report allowed area and optionally a reporting indication. 5. The (H)GMLC or VGMLC invokes the Namf_Location_ProvidePositioningInfo Request service operation to forward the location request to the serving AMF as described for step 5 in clause 6.1.2 and includes the (H)GMLC contact address and LDR reference number. The LDR reference number is either allocated by (H-)GMLC based on predefined rule, e.g. operator's policy if the location request is received in step 1a, or allocated by NEF, if the location request is received in step 1b. For area event reporting, the target geographical area is converted into a corresponding list of cell and/or tracking area identities. The service operation includes the event report allowed area, the reporting indication if they are determined by GMLC in step 4. 6-8. If the AMF supports a deferred location request, the AMF returns an acknowledgment to the external LCS client, the NF, or the AF, via the (H)GMLC and, in the case of roaming, the VGMLC, indicating that the request for deferred location was accepted. The VGMLC, when used, may optionally release resources for the deferred location request at this point. 9. If the UE is not currently reachable (e.g. is using eDRX or PSM), the AMF waits for the UE to become reachable. NOTE 3: In the event of mobility of the UE to another AMF or to EPC when the UE becomes reachable, the old AMF can return an event indication to the (H)GMLC as at steps 19 and 20 and may include the address of the new serving AMF or MME if known. If a new serving AMF or MME is not known, the (H)GMLC can repeat step 3 to query the UDM and HSS for the new AMF or MME address. If a new AMF address is received, the (H)GMLC can restart the procedure from step 4. 10. Once the UE is reachable, if the UE is then in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. NOTE 4: The AMF may decide to cancel the location request before the UE becomes reachable (e.g. due to lack of resources or due to a timeout on the UE becoming reachable) or when the UE becomes reachable (e.g. if the AMF executes NAS level congestion control on the UE, or for other reasons). The AMF then skips steps 10-18 and proceeds to step 19 to return an indication of location cancelation to the VGMLC or (H)GMLC. 11-12. The AMF performs steps 7-8 in clause 6.1.2 to notify the UE of the location request and verify privacy requirements if required by the location request received at step 5 and supported by the UE. The AMF includes in the notification to the UE the type of deferred location request in the case of periodic or triggered location. 13. The AMF selects an LMF as described for step 6 in clause 6.1.1. The selection may take into account the type of deferred location request (e.g. whether periodic or triggered) and any parameters for the deferred location request (e.g. the number of event reports required and/or the duration). 14. The AMF invokes the Nlmf_Location_DetermineLocation Request service operation towards the LMF to initiate a request for deferred UE location. For a request for periodic or triggered location, the service operation includes all the information received in step 4 or step 5 including the (H)GMLC contact address, LDR reference number, UE Positioning Capability if available and any scheduled location time and may include a list of allowed access types for event reporting at step 22. For a request for the UE available location event, the (H)GMLC contact address and LDR reference number are not included, except for the case to support location service in PNI-NPN with signalling optimisation described in clause 5.13. In all cases, the service operation includes an LCS Correlation identifier, the AMF identifier, the serving cell identity, the client type and may include an indication if UE supports LPP, the required QoS and Supported GAD shapes. The service operation includes the event report allowed area, the reporting indication if received by AMF in step 5. The AMF may include the UE ID (i.e. SUPI) in the service operation. 15. The LMF performs one or more of the positioning procedures described in clause 6.11.1, 6.11.2 and 6.11.3 and as described for step 8 in clause 6.1.1. During this step, the LMF may request and obtain the UE positioning capabilities (e.g. which may indicate the type(s) of periodic and triggered location supported by the UE and the access types supported by the UE for event reporting). The LMF may also obtain the UE location - e.g. for a request for the UE available location event or when an initial location is requested for periodic or triggered UE location. For a request for the UE available location event, the LMF skips steps 16 and 17. 16. If periodic or triggered location was requested, the LMF sends a supplementary services LCS Periodic-Triggered Invoke Request to the UE via the serving AMF by invoking the Namf_Communication_N1N2MessageTransfer service operation. The LCS Periodic-Triggered Location Invoke carries the location request information received from the AMF at step 14, including the (H)GMLC contact address, LDR reference number and any scheduled location time. The LCS Periodic-Triggered Location Invoke also includes a deferred routing identifier, which can be the identification of the LMF when the LMF will act as a serving LMF or a default LMF identification otherwise. The LCS Periodic-Triggered Location Invoke may indicate the allowed access types for event reporting at step 25 (e.g. one or more of NR, E-UTRA connected to 5GC, non-3GPP access connected to 5GC, any of the RAT Types specified for NR satellite access) and may include embedded positioning message(s) which indicates certain allowed or required location measurements (or a location estimate and the timestamp of the location estimate if available) at step 24 for each location event reported (e.g. based on the positioning capabilities of the UE obtained in step 14 and the allowed access types). As part of NAS transport of the LCS Periodic-Triggered Location Invoke from the serving AMF to the UE, the serving AMF includes an immediate routing identifier in the NAS transport message containing an LCS Correlation identifier - e.g. according to clause 6.11.1. The service operation includes the event report allowed area, the reporting indication received by LMF in step 14. NOTE 5: The deferred routing identifier may be global (e.g. an IP address, UUID or URI) or may be local. The deferred routing identifier is used for routing in step 25. However, the immediate routing identifier included by the AMF in step 15 is used for routing in step 17. 17. If the request in step 16 can be supported, the UE returns a supplementary services acknowledgment to the LMF, which is transferred via the serving AMF using the immediate routing identifier and delivered to the LMF using an Namf_Communication_N1MessageNotify service operation. 18. The LMF invokes the Nlmf_Location_DetermineLocation Response service operation towards the AMF to respond to the request at step 14. For a request for the UE available location event, the response includes any UE location obtained at step 15 and the LMF then releases all resources and if (H)GMLC contact address and the Notification Correlation ID is received in step 14 for PNI-NPN signalling optimization, the LMF responds to AMF to indicate that the location determination will be sent directly to GMLC and step 19 is skipped and similarly with step 28, the LMF sends Nlmf_Location_EventNotify to (H)GMLC directly. For a periodic or triggered location request, the response includes any location obtained at step 15, a confirmation of whether periodic or triggered location was successfully activated in the UE according to steps 16 and 17 and the identification of the LMF in the case of successful activation with a serving LMF; the LMF also retains state information and resources for later steps if the LMF acts a serving LMF. If the multiple QoS class was used in the location request, the LMF provides the achieved Location QoS Accuracy in step 15. If the UE cannot support the periodic and triggered location request, the service operation returned to the AMF shall include a suitable error cause. The service operation also includes the UE Positioning Capability if the UE Positioning Capability is received in step 15 including an indication that the capabilities are non-variable and not received from AMF in step 14. 19. The AMF invokes the Namf_Location_EventNotify service operation towards the VGMLC for roaming, or (H)GMLC for non-roaming, and includes any location received at step 18 and, for periodic or triggered location, a confirmation of whether or not periodic or triggered location was successfully activated in the target UE. The VGMLC, if used, may be the same VGMLC used in steps 5 and 6 or may be a different VGMLC. In the case of a different VGMLC, the AMF includes the HGMLC contact address and LDR reference number. The AMF also includes the LMF identification and the achieved Location QoS Accuracy if received at step 18. The AMF may then release all resources for the location request and cease support for the procedure. 20. This step is skipped for a non-roaming UE. For a roaming UE, The VGMLC forwards the response received at step 19 to the HGMLC using the HGMLC contact address received at step 19 (for a different VGMLC) or received and stored at step 4 (for the same VGMLC) and includes the LDR reference number and any LMF identification that was received. The VGMLC may then release all resources for the location request and cease support for the procedure. NOTE 6: As an optional optimization for a roaming UE, instead of performing steps 19 and 20, the AMF may invoke the Namf_Location_EventNotify service operation directly towards the HGMLC (e.g. if a VGMLC is not used or if the VGMLC ceases support after step 8). 21. The (H)GMLC forwards the response to the external LCS client, the NF or the AF (via the NEF). If the location request at step 1 was for the UE available location event, the procedure terminates here and further steps 22-31 are not performed. 22. For a periodic or triggered location request where steps 16 and 17 were successfully performed, the UE monitors for occurrence of the trigger or periodic event requested in step 16. For the area event or motion event, the UE monitors the requested event at intervals equal to or less than the maximum event sampling interval. An event trigger is detected by the UE when any of the following occur: (i) a requested area event or motion event has been detected and the minimum reporting time interval has elapsed since the last report (if this is not the first event report); (ii) a requested periodic location event has occurred; or (iii) the maximum reporting time for an area event or motion event has expired. When a trigger or periodic event is detected and if the UE is camped on or connected to (or can otherwise access) an access type allowed by the LMF at step 16, the UE proceeds to step 23. If the UE cannot access an allowed access type, the UE may skip reporting the trigger event or may report the trigger event at a later time when an allowed access type becomes available, according to requirements received from the LMF at step 16. When a scheduled location time is provided for periodic location request at step 16, a UE should perform steps 23-25 some time in advance of the scheduled location time for the first periodic event report or some time in advance of the periodic interval expiration for each succeeding periodic event report in order to enable location measurements at step 23 or step 27 to occur near to each of these times, respectively. If the event report allowed area with no reporting indication is received in step 16, when UE detects the event happens, it further checks whether it is inside the event report allowed area. If yes, the steps 23 to 30c are performed. Otherwise, the steps 23 to 30c are skipped. If the event report allowed area with a reporting indication is received in step 16, when UE detects the event happens, it further checks whether it is outside the event report allowed area. If yes, the steps 23 to 30c are performed. Otherwise, the steps 23 to 30c are skipped. 23. The UE obtains any location measurements or a location estimate that were requested or allowed at step 16. NOTE 7: Obtaining a location estimate when requested also applies to the trigger event corresponding to expiration of the maximum reporting interval for an area event or motion event. 24. The UE performs a UE triggered service request as defined in clause 4.2.3.2 of TS 23.502 [19] if in CM-IDLE state in order to establish a signalling connection with the AMF. 25. The UE sends a supplementary services event report message to the LMF which is transferred via the serving AMF (which may be different to the original serving AMF for steps 14-16) and is delivered to the LMF using an Namf_Communication_N1MessageNotify service operation. The event report may indicate the type of event being reported (e.g. whether a normal event or expiration of the maximum reporting interval) and may include embedded positioning message(s) which includes any location measurements or location estimate and the timestamp of the location estimate if available obtained at step 23. The UE also includes the deferred routing identifier received in step 16 in the NAS Transport message used to transfer the event report from the UE to the AMF. The AMF then forwards the event report to either the serving LMF or any suitable LMF based on whether the deferred routing identifier indicates a particular LMF or default (any) LMF. If a different LMF than the serving LMF is used, procedure in clause 6.4 is used. The UE also includes the (H)GMLC contact address, the LDR reference number, whether location estimates are to be reported and if so the location QoS in the event report and any scheduled location time indicated at step 16 for periodic reporting. If the default (any) LMF is used, the AMF shall provide the UE ID (i.e. SUPI) in the Namf_Communication_N1MessageNotify service operation. NOTE 8: When forwarding the event report message to the LMF in step 25, the AMF includes the deferred routing identifier received in step 25 as the LCS Correlation Identifier. The deferred routing identifier can assist a serving LMF in identifying the periodic or triggered location session if the same serving LMF had assigned the deferred routing identifier at step 16 or can indicate to the LMF that it is acting as a default LMF. NOTE 9: The scheduled location time included at step 25 equals T + (N-1)*P, where T is the initial Scheduled Location Time, N is the Report Number (N≥1) and P is the time interval between successive periodic events. 26. When the LMF receives the event report and if it can handle this event report, the LMF updates the status of event reporting(e.g. the number of event reports so far received from the UE and/or the duration of event reporting so far) and returns a supplementary services acknowledgment for the event report to the UE. The acknowledgment may optionally include a new deferred routing identifier indicating a new serving LMF or a default (any) LMF. When the LMF delivers the acknowledgement for the event report to the AMF by invoking an Namf_Communication_N1N2MessageTransfer service operation, the LMF shall provide the UE ID (i.e. SUPI). If the UE does not receive any response from the LMF after a predefined time, i.e. the current LMF does not support the deferred location request (for temporary or permanent reasons) or due to some radio access failures, the UE may re-send the report one or more times. If the UE sends the repeated event report more than the predefined maximum resending time and the UE still does not receive any response from AMF, the UE shall stop resending the report and reserve the event report, then record a corresponding flag to indicate that a report has been sent unsuccessfully. When the UE performs location update and detects the PLMN is changed, if the flag has been set, the UE shall send the report to the corresponding AMF, and the flag will be cleared upon a success of the sending. NOTE 10: Inclusion of a new deferred routing identifier in the event report acknowledgment at step 26 may be used to change the serving LMF (e.g. if a UE moves into an area or to an access type that is better supported by a different LMF or if the serving LMF is overloaded) or to enable a default LMF to become a serving LMF. 27. If a location estimate is needed for event reporting, the LMF may perform one or more of the positioning procedures described in clauses 6.11.1, 6.11.2, 6.11.3 and 6.11.4 and as described for step 8 in clause 6.1.1 and step 12 in clause 6.1.2. The LMF then determines the UE location using the location measurements and/or location estimate(s) obtained at this step and/or received at step 25. The LMF may also determine the timestamp of the location estimate. If the positioning procedures described in clause 6.11.1 and clause 6.11.2 are used, when the LMF delivers the Namf_Communication_N1N2MessageTransfer to AMF, the LMF shall provide the UE ID (i.e. SUPI). NOTE 11: A precondition for the procedure in clause 6.11.1 is that an LCS Correlation identifier assigned by the serving AMF has been previously passed to the LMF. The LCS Correlation identifier is used in steps 1, 3, 6 and 7 in clause 6.11.1 to ensure that during a positioning session between the LMF and UE, positioning response messages from the UE are returned by the AMF to the correct LMF and carrying an indication (the LCS Correlation identifier) which can be recognized by the LMF. To retain this capability in step 27, the LMF shall assign a Correlation identifier indicating the LMF (and optionally a positioning session) for use at step 1 in clause 6.11.1. To enable an AMF to distinguish a Correlation identifier assigned by an LMF (used in this procedure) from a Correlation identifier assigned by the AMF (used otherwise for clause 6.11.1), the two types of Correlation identifier could be selected from different ranges, with or without a flag. 28. In the case of roaming, the LMF selects a VGMLC (which may be different to the VGMLC for steps 3-8 and steps 19-21), The LMF then invokes an Nlmf_Location_EventNotify service operation towards the selected VGMLC or (H)GMLC with an indication of the type of event being reported, the (H)GMLC contact address and LDR reference number, the identification of the LMF if this is a serving LMF, and any location estimate and the timestamp of the location estimate (if available) obtained at step 27. If multiple QoS class was used in the initial location request, the LMF provides the achieved Location QoS Accuracy in step 27. NOTE 12: In the case of roaming, the LMF may select the VGMLC for step 28 using the NRF service or using configuration information in the LMF or may use the same VGMLC as for steps 3-8 (e.g. if the LMF acts as a serving LMF and received the VGMLC address from the AMF as part of step 14). 29. This step is skipped for a non-roaming UE. For a roaming UE, the VGMLC invokes an Ngmlc_Location_EventNotify service operation to forward the information received in step 28 (e.g. including the type of event being reported, the LDR reference number and possibly the LMF identification) to the HGMLC which identifies the periodic and triggered location request from the LDR reference number. NOTE 13: As an optional optimization for a roaming UE, instead of performing steps 28 and 29, the LMF may invoke the Nlmf_Location_EventNotify service operation directly towards the HGMLC. NOTE 14: In the event of mobility of the UE to an access network for which event reporting at step 22 is not allowed (e.g. an access network in EPS) or if the UE is otherwise unable to send event reports (e.g. due to being powered off), the (H)GMLC may not receive event reports at step 28 or step 29 at fixed intervals for periodic location or at intervals equal to or less than the maximum reporting interval for triggered location. In such a case, the (H)GMLC may cancel the periodic or triggered location reporting using the procedures defined in clause 6.3.3. The UE may also cancel the periodic or triggered location reporting either locally or using the procedure defined in clause 6.3.2 once the UE can access an access network that is allowed for event reporting. 30. The (H)GMLC uses the LDR reference number received in step 28 or step 29 to identify the periodic and triggered location request received in step 1 and then sends the type of event being reported and any location estimate and the timestamp of the location estimate (if available) and used positioning methods to the external LCS client, the NF or the AF (via the NEF), and sends the LDR reference number to LCS client. The (H)GMLC may also verify UE privacy requirements before reporting the event and any location to the external LCS client, the NF or the AF. If multiple QoS class was used in the initial location request, the LMF provides the achieved Location QoS Accuracy in step 27. If an indication to have an additional check is received at step 1, the (H)GMLC will verify the UE location estimate is within the target area, and send the event report to the LCS client, the NF or the AF. 31. The UE continues to monitor for further periodic or trigger events as in step 22 and instigates steps 23-30 each time a trigger event is detected. NOTE 15: Service continuity for reporting of periodic or trigger events when a UE moves between 5GS and EPS is not supported in this release of the specification.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.2 Cancellation of Reporting of Location Events by a UE	Figure 6.3.2-1 summarizes a procedure to enable a UE to cancel a deferred 5GC-MT-LR procedure for periodic, or triggered location events (e.g. if the UE is powered off or if the UE cancels the location request based on user's input). It is assumed that a deferred 5GC-MT-LR for periodic or triggered location events has already been initiated in the UE according to steps 1-17 for the procedure in clause 6.3.1. If a network entity (e.g. (H)GMLC, AMF or LMF) cancels a deferred 5GC-MT-LR procedure for periodic or triggered location events, part of the procedure in clause 6.3.3 for cancellation by an AF, an NF or external LCS Client would be used to cancel towards the UE and part of the procedure in this clause would be used to cancel towards the AF, the NF or external LCS Client. Figure 6.3.2-1: UE Cancellation of a Deferred 5GC-MT-LR for periodic or triggered location events 1. The UE performs a UE triggered service request as defined in clause 4.2.3.2 of TS 23.502 [19] if in CM-IDLE state in order to establish a signalling connection with the AMF. 2. The UE sends a Cancel Location request message to the LMF which is transferred via the serving AMF and is delivered to the LMF using an Namf_Communication_N1MessageNotify service operation. The UE includes the deferred routing identifier originally received in step 16 of the procedure in clause 6.3.1 (or as updated by step 26 in clause 6.3.1 or by the procedure in clause 6.4) in the NAS Transport message used to transfer the cancel location request from the UE to the AMF. The AMF then forwards the cancel location request to either the serving LMF or any suitable LMF based on whether the deferred routing identifier indicates a particular LMF or any (default) LMF. The UE also includes the (H)GMLC contact address and the LDR reference number. 3. In the case of roaming, the LMF selects a VGMLC. The LMF then invokes an Nlmf_Location_EventNotify service operation towards the selected VGMLC or (H)GMLC with an indication of the cancelation of location event reporting, the (H)GMLC contact address and LDR reference number. NOTE 1: In the case of roaming, the LMF may select the VGMLC for step 3 using the NRF service or using configuration information in the LMF or may use the same VGMLC as for steps 3-8 of clause 6.3.1 (e.g. if the LMF acts as a serving LMF and received the VGMLC address from the AMF as part of step 14 of clause 6.3.1). 4. This step is skipped for a non-roaming UE. For a roaming UE, the VGMLC invokes an Ngmlc_Location_EventNotify service operation to forward the cancel location request (including the LDR reference number) to the HGMLC which identifies the periodic and triggered location request from the LDR reference number. NOTE 2: As an optional optimization for a roaming UE, instead of performing steps 3 and 4, the LMF may invoke the Nlmf_Location_EventNotify service operation directly towards the HGMLC. 5. The (H)GMLC uses the LDR reference number received in step 3 or step 4 to identify the periodic and triggered location request received in step 1 of clause 6.3.1 and then forwards the cancel location to the external LCS client, the NF or the AF (via the NEF). 6. The LMF returns an acknowledgment to the UE via the serving AMF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.3 Cancellation of Reporting of Location Events by an AF, an NF or External LCS Client or GMLC	Figure 6.3.3-1 summarizes a procedure to enable an AF, an NF or External LCS Client or GMLC to cancel a deferred 5GC-MT-LR procedure for periodic, or triggered location. It is assumed that a deferred 5GC-MT-LR for periodic or triggered location events has already been requested according to the procedure in clause 6.3.1 up until at least step 20. Figure 6.3.3-1: Cancellation of a Deferred 5GC-MT-LR for periodic or triggered location events by an AF, an NF or External LCS Client 1. The external LCS client, the NF or the AF (via an NEF) send a request to cancel the periodic or triggered location to the (H)GMLC, the external LCS client, the NF or the AF shall include the identity of the deferred request. The HGMLC may itself initiate the cancellation procedure, e.g. when it is notified that the UE LCS privacy profile stored in the UDM was changed. For every outstanding Deferred Location Request against that UE, the HGMLC shall perform a new privacy check based on the updated UE LCS privacy profile stored in the UDM. If the privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request shall be continued. Otherwise, if the privacy check does not pass, i.e. the Location estimate of the target UE is not allowed to be provided to the LCS Client, the HGMLC shall initiate a cancellation procedure NOTE: GMLC may perform privacy check for more than one location request as a bulk operation. 2. The (H)GMLC queries the UDM to determine the serving AMF address as in step 3 of clause 6.3.1. 3. For a roaming UE, the HGMLC obtains a VGMLC address if not received at step 2 and invokes an Ngmlc_Location_CancelLocation service operation to forward the cancellation request to the VGMLC. The (H)GMLC also includes the contact address for the (H)GMLC and the LDR reference number in the request and the latest LMF identification received in step 20 or step 29 in clause 6.3.1 if either step has occurred and included an LMF identification. 4. The (H)GMLC or VGMLC invokes the Namf_Location_CancelLocation service operation to forward the cancellation request to the serving AMF and includes the (H)GMLC contact address, LDR reference number and LMF identification if available. 5. If an LMF identification was included in step 4, the AMF forwards the cancelation request to the indicated LMF by invoking an Nlmf_Location_CancelLocation service operation and includes the (H)GMLC contact address and LDR reference number. The LMF then releases all resources for the location request. 6. If the UE is not currently reachable (e.g. is using eDRX or PSM), the AMF waits for the UE to become reachable. 7. Once the UE is reachable, if the UE is then in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. 8. The AMF sends the cancelation request to the target UE and includes the (H)GMLC contact address and the LDR reference number. The UE then releases all resources for the location request. 9. The UE returns an acknowledgment to the AMF. 10. The AMF responds to Namf_Location_CancelLocation, then V-GMLC or (H)GMLC releases all resources for the location request. AMF releases all resources for the location request. 11. For a roaming UE, the VGMLC responds to Ngmlc_Location_CancelLocation, then HGMLC releases all resources for the location request. 12. [Conditional] If the cancellation procedure is requested by HGMLC (i.e. the procedure is triggered in step 1c) and the cancelled location event is reported to external client, the NF or the AF (via NEF).
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.4 Cancellation of Reporting of data collection by a UE	The procedure described in Figure 6.3.4-1 enables a UE to cancel a data collection by LMF to train the LMF-based AI/ML Positioning model as described in clause 6.22.2, for example if the UE is powered off or if the UE cancels the data collection based on user's input (e.g. UE is not willing to report input data). Figure 6.3.4-1: UE Cancellation of a data collection 1. The LMF performs a data collection procedure as defined in clause 6.22.2. 2. Same as step 2 in clause 6.3.2. 3. same as step 6 in clause 6.3.2.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.5 Deferred 5GC-MT-LR Procedure for Periodic Location Events based on NRPPa Periodic Measurement
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.5.1 Initiation and Reporting of Periodic Events based on NRPPa Periodic Measurement	Figure 6.3.5.1-1: Deferred 5GC-MT-LR for Periodic Events based on NRPPa Periodic Measurement 1. Deferred 5GC-MT-LR steps 1-14 are executed as described in clause 6.3.1. AF, LCS clients or NF triggers periodic location event. 2. LMF performs one or more of the positioning procedures as it is described in step 15 in clause 6.3.1. LMF based on UE capability information received in this step and based on configuration decides to perform NRPPa Periodic Measurements. Once LMF determines to use NRPPa periodic measurement, it may perform Positioning Information Exchange based on an NRPPa protocol in TS 38.455 [15] between the LMF and NG-RAN (e.g. as described in clause 8.2.6.2 of TS 38.455) 3. Deferred 5GC-MT-LR steps 18-21 are executed as described in clause 6.3.1 with the following changes: - The NRPPa periodic indication is added to steps 18-20 to indicate Periodic Location Estimates are generated based on NRPPa Periodic Measurement. (H)GMLC stores NRPPa periodic indication. 4a-b. LMF performs NRPPa Periodic E-CID Measurement Initiation Request (clause 8.2.1.2 of TS 38.455 [15]) or LMF performs NRPPa Periodic Measurement Request (clause 8.5.1.2 of TS 38.455 [15]). LMF uses the time interval between successive location reports and the total number of reports received in step 1 to setup NRPPa periodical report procedure. 5. The AMF forwards the message to NG-RAN. 6-7a. NG-RAN returns with E-CID Measurement Initiation Response (clause 8.2.1.2 of TS 38.455 [15]). 6-7b. NG-RAN returns with Measurement Response (clause 8.5.1.2 of TS 38.455 [15]). 8-9a. LMF is receiving E-CID Measurement Report from NG-RAN periodically (clause 8.2.3.2 of TS 38.455 [15]). LMF uses Measurement Information to calculate Location Result. 8-9b. LMF is receiving Measurement Report from NG-RAN periodically (clause 8.5.2.2 of TS 38.455 [15]). LMF uses Measurement Information to calculate Location Result. 10. LMF invokes Nlmf_Location_EventNotify service operation as described in step 28 in clause 6.3.1 in order to transfer location information to VGMLC or (H)GMLC. 11. Deferred 5GC-MT-LR step 29 is executed as described in clause 6.3.1. 12a. Deferred 5GC-MT-LR step 30a is executed as described in clause 6.3.1. 12b-1. Deferred 5GC-MT-LR step 30b-1 is executed as described in clause 6.3.1. 12b-2. Deferred 5GC-MT-LR step 30b-2 is executed as described in clause 6.3.1. 12c. Deferred 5GC-MT-LR step 30c is executed as described in clause 6.3.1. Steps between 8 and 12c are executed periodically. LMF before step 4 invokes Namf_EventExposure_Subscribe to receive events from serving AMF about NG-RAN change using "RAN_Node" as LocationFilter. When LMF receives from NG-RAN error causes (e.g. due to UE mobility to another NG-RAN node or UE is released to CM-IDLE mode) that NG-RAN node is unable to provide the measurement results then LMF considers that the NRPPa periodic reporting is terminated by NG-RAN. The LMF may re-trigger a request for NRPPa periodical reporting, considering the event notification from AMF which is subscribed by the LMF as described above. The LMF change is defined in the clause 6.4.1.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.3.5.2 Cancellation of Reporting of Periodic Events by an AF, an NF or External LCS Client or GMLC	Cancellation of Reporting of Periodic Events by an AF, an NF or External LCS Client or GMLC based on NRPPa Periodic Measurement executed as described in clause 6.3.3 with the following changes: - Steps from 6 to 9 are not executed based on NRPPa periodic indication provided by VGMLC in step 4. (i.e. UE's related procedures are not executed). - When in step 5 LMF receives Namf_Location_CancelLocation, LMF stops NRRPa periodic measurement report by requesting E-CID Measurement Termination (clause 8.2.4.2 of TS 38.455 [15]) or Measurement Abort (clause 8.5.4.2 of TS 38.455 [15]) or Positioning Deactivation (clause 8.2.10 of TS 38.455 [15]) and unsubscribe for AMF event.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.4 LMF Change Procedure
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.4.0 General	The LMF Change procedure supports change of a serving LMF during a deferred 5GC-MT-LR procedure for periodic, or triggered location events as defined in clause 6.3.1. When a serving LMF is used for the procedure in clause 6.3.1, mobility of the target UE may lead to a change of serving AMF for which the original serving LMF is not suitable. For example, the serving LMF may be very remote from the new serving AMF leading to higher resource utilisation for AMF to LMF signalling or the LMF may not be configured with information (e.g. a cell database) for the current access network for the UE to enable location. In such a case, the serving LMF may need to change. Figure 6.4-1 shows a procedure to enable change of the serving LMF when a UE sends an event report as at step 25 in clause 6.3.1. Figure 6.4-1: Change of serving LMF for periodic and triggered UE location events Precondition: Steps 1-23 in clause 6.3.1 have already been performed and steps 22-30 may have been performed or repeated. A serving LMF is used and the current serving LMF is LMF1. 1. The UE performs a service request if needed as for step 24 in clause 6.3.1. 2. The UE sends a NAS Transport message containing a supplementary services event report message to the serving AMF. The NAS Transport message includes a deferred routing identifier indicating LMF1. Step 2 corresponds to part of step 25 for clause 6.3.1. 3. Based on operator configuration and policy, the AMF may evaluate and determine that LMF1 is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF. AMF may already have LMF2 information e.g. from previous NRF discovery or locally configured, otherwise AMF queries NRF and in response may get a set of LMF profiles. AMF selects new LMF (i.e. LMF2 in this case) for the current UE location based on LMF service area (consisting of one or more TA(s)) and also other information as listed in clause 5.1. 4. The AMF invokes the Namf_Communication_N1MessageNotify service operation towards LMF1. The service operation includes the event report received in step 2. If the AMF determined in step 3 that a new LMF2 should be used, it indicates that to the LMF1 as well. 5. If the AMF did not indicate a new LMF in step 4, based on the operator configuration and policy, LMF1 may evaluate and determine that it is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF. LMF1 may already have LMF2 information e.g. from previous NRF discovery or locally configured, otherwise LMF1 queries NRF and in response may get a set of LMF profiles. LMF1 selects new LMF (i.e. LMF2 in this case) for the current UE location based on LMF service area (consisting of one or more TA(s)) and other information as listed in clause 5.1. 6. LMF1 invokes an Nlmf_Location_LocationContextTransfer Request service operation towards LMF2 to provide the current location context of the UE and includes the event report message received in step 4. The service operation includes the AMF identity and all the information originally received by LMF1 for the periodic or triggered location request either from the AMF according to the procedure in clause 6.3.1 or from an earlier serving LMF according to this procedure. The service operation may also include the current status of event reporting (e.g. the number of event reports so far received from the UE and/or the duration of event reporting so far) and may include location related information for the UE such a previous location estimate and the timestamp of the location estimate (if available) or location measurements. 7. LMF2 informs LMF1 of the location context transfer operation results. LMF1 then releases all resources for the procedure. 8. LMF2 invokes the Namf_Communication_N1N2MessageTransfer service operation towards the AMF to request the transfer of a supplementary services Event Report Acknowledgment message to the UE. The Event Report Acknowledgment indicates a change of LMF and includes a deferred routing identifier indicating LMF2. 9. The AMF forwards the Event Report Acknowledgment to the UE in a NAS Transport message. The AMF also informs the LMF2 of the result of the delivery of the Event Report Acknowledgement. 10. If a location estimate is needed for event reporting, LMF2 may perform positioning of the UE and determines the UE location as at step 27 in clause 6.3.1. The rest of the procedure in clause 6.3.1 then continues from step 28 with LMF2 retaining state information to enable support of subsequent event reports from the UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.4.1 LMF Change Procedure for NRPPa Periodic Measurement	The LMF Change procedure supports change of a serving LMF during a deferred 5GC-MT-LR procedure for Periodic Location Events based on NRPPa Periodic Measurement as defined in the clause 6.3.5.1. LMF change may be initiated due to new NG-RAN or new serving AMF. Figure 6.4.1-1: Change of serving LMF for Periodic Events based on NRPPa Periodic Measurement 1. NG-RAN or AMF change happens, e.g. due to UE mobility in CM-CONNECTED state. The (new) AMF may trigger the event notification towards LMF (e.g. based on the event subscription as described in clause 6.3.5.1). When there is a change of AMF, the new AMF receives all event subscriptions from old AMF. The new AMF informs LMF about the new AMF address if the LMF has subscribed for the NG-RAN change event as described in clause 6.3.5.1 and the LMF reinitiates NRPPa Periodic Measurement Initiation towards new serving AMF with the remaining number of reports. 2. [Conditional] LMF1 may evaluate and determine that it is unsuitable or unable to support location for the current UE NG-RAN and determines LMF2 as being a more suitable LMF. LMF1 may already have LMF2 information e.g. from previous NRF discovery or locally configured, otherwise LMF1 queries. LMF1 selects new LMF based on NG-RAN location based and other information as listed in clause 5.1. 3. [Conditional] LMF1 invokes an Nlmf_Location_LocationContextTransfer Request service operation towards LMF2 to provide the current location context of the UE. The service operation includes the AMF identity and all the information originally received by LMF1 for the periodic location request either from the AMF or from an earlier serving LMF according to this procedure. LMF2 invokes Namf_EventExposure_Subscribe to receive events from serving AMF about NG-RAN change. 4. [Conditional] LMF2 informs LMF1 of the location context transfer operation results. LMF2 performs NRPPa Periodic Measurement Initiation. 5. [Conditional] LMF1 releases all resources for the procedure and unsubscribe from AMF event.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.5 Unified Location Service Exposure Procedure
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.5.1 Unified Location Service Exposure Procedure without routing by a UDM	Figure 6.5.1-1 shows a unified location service exposure procedure provided by an NEF in an HPLMN for a target UE to an NF in the HPLMN or to an external AF outside the HPLMN. The procedure enables a request for an immediate location or for a deferred location for a target UE. Figure 6.5.1-1: Unified Location Service Exposure Procedure without routing by a UDM 1a. An external AF invokes an Nnef_EventExposure_Subscribe service operation towards an NEF in the HPLMN for a target UE and includes an identification of the UE (e.g. SUPI or GPSI) and details of the location request such as whether a current or last know immediate location or a deferred location is requested, the location accuracy and response time, maximum age of location, LDR request information and other information applicable to the type of request. 1b. As an alternative to step 1a, a consumer NF in the HPLMN for a target UE invokes an Nnef_EventExposure_Subscribe service operation towards an NEF in the HPLMN and includes a global identification of the UE (e.g. SUPI or GPSI) and details of the location request as in step 1a. 2. Based on the service requirements in step 1a or step 1b (e.g. location QoS and whether an immediate or deferred location is requested) and on the availability of GMLC versus AMF based location service, the NEF determines whether the location request in step 1a or step 1b can be mapped to a GMLC based location service or to an AMF location event exposure service. The NEF determines to use whichever mapping is supported or, when both mappings are supported, may employ implementation or operator dependent procedures to make a choice. When a GMLC based location service is determined, steps 3-6 are performed and steps 7-15 are omitted. When an AMF location event exposure service is determined, steps 7-15 are performed and steps 3-6 are omitted. If NEF determines the location request is handled by AMF, it allocates an LDR reference number. NOTE 1: The NEF may take the potential load to the system, e.g. AMF/UDM load, or GMLC load, into consideration when deciding which location service to use, or whether to reject the request from NF or AF. The NEF may also take into account QoS. For example, when QoS accuracy exceeds cell ID, the GMLC location service shall be used if available. 3. When a GMLC based location service is determined in step 2, the NEF invokes an Ngmlc_Location_ProvideLocation Request service operation towards an HGMLC in the HPLMN. The service operation may include all of the information received from the AF or NF in step 1a or 1b. 4. For a request for an immediate location, the HGMLC performs steps 2-10 of the 5GC-MT-LR procedure in clause 6.1.1 in the case of regulatory location or steps 2-23 of the 5GC-MT-LR procedure in clause 6.1.2 in the case of commercial location. For a request for deferred location, the HGMLC performs steps 2-29 of the deferred 5GC-MT-LR procedure for periodic, triggered or UE available location events in clause 6.3.1. 5. The HGMLC invokes the Ngmlc_Location_ProvideLocation Response service operation towards the NEF to confirm the request in step 3 for a request for deferred location or to return the UE location for a request for an immediate location. 6. If deferred location was requested in step 1, the HGMLC invokes one or more Ngmlc_Location_EventNotify service operations towards the NEF, to convey a single UE location in the case of deferred location for the UE available event or to convey an indication of location activation in the UE followed by one or more location event reports in the case of deferred location for periodic or triggered location events. 7. When an AMF location event exposure service is determined in step 2, if the NEF needs to verify the target UE privacy requirements, the NEF invokes a Nudm_SDM_Get service operation towards the UDM of the target UE to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the target UE Privacy setting and the SUPI of the UE. The NEF checks the privacy settings. If the target UE is not allowed to be located, steps 8-14 are skipped. NOTE 2: The AMF location event exposure service does not support a real time query to the UE to verify UE privacy requirement by the user. If the NEF finds this is needed, the NEF either selects a GMLC location service or returns an error to the external AF or NF. 8. The NEF invokes a Nudm_UECM_Get service operation towards the UDM of the target UE with SUPI of this UE. The UDM returns the network addresses of the current serving AMF. If the location request is an immediate location request, the NEF checks the country codes of the serving node addresses. If the NEF finds out the current AMF locates out of the service coverage, the NEF returns an appropriate error message to the AF or NF. When the UE is concurrently served by multiple PLMNs respectively for 3GPP access and non-3GPP access, multiple AMF IDs with corresponding access type are provided by the UDM, the NEF selects one access type and its associated AMF based on principle defined in clause 5.3.2. 9. The NEF invokes an Namf_EventExposure Subscribe service operation towards the serving AMF for the target UE and indicates whether a one-time UE location is requested or multiple UE locations for some triggering event, if current or last known is requested, maximum age of location and includes information on location accuracy (e.g. cell ID or TA granularity). If the NEF has no direct access to AMF or is configured to use UDM for the AMF event exposure, procedure in clause 6.5.2 is used instead. 10. The AMF responds to the service operation in step 9. 11. If the UE is currently reachable and in CM-IDLE state and if current location is requested in step 9 with a cell ID accuracy and maximum age of location cannot be fulfilled based on AMF knowledge of the current or last known serving cell, the AMF perform a network triggered service request as described in TS 23.502 [19] to place the UE in CM-CONNECTED state. 12. If an immediate location is requested in step 9 which the AMF can support based on AMF knowledge of the current or last known serving cell or serving TA for the UE, the AMF uses this information. Otherwise, the AMF invokes the NG-RAN location reporting procedure defined in clause 4.10 of TS 23.502 [19] to obtain a single location or multiple UE locations according to the request in step 9. The AMF may convert any location that was obtained in the form of a cell ID or TAI into geographical information based on TS 23.032 [8] and as defined in clause 6.2.6.2.5 of TS 29.518 [16] and clauses 5.4.4.7, 5.4.4.8 and 5.4.4.9 of TS 29.571 [33] before proceeding to step 13. 13. The AMF invokes the Namf_EventExposure Notify service operation towards the NEF to provide the current or last known UE location as obtained at step 12. When the NEF obtains more than one serving AMF and corresponding access type from UDM at step 8, if the location information provided by AMF can not meet the required LCS QoS, the NEF may forward the location request to another AMF, i.e. Steps 9-15 is performed in another PLMN served by this AMF. In this case, if the access type associated with another AMF is non-3GPP access, procedure defined in clause 6.9.2 applies. 14. If the AMF invokes the NG-RAN location reporting procedure in step 12 to obtain multiple UE locations and receives multiple location reports from NG-RAN as part of step 12, the AMF invokes one or more additional Namf_EventExposure Notify service operations towards the NEF to provide each additional UE location provided by NG-RAN. The AMF may convert each additional UE location in the form of a cell ID or TAI into geographical information as in step 12. NOTE 4: AMF conversion of a UE location in the form of a cell ID or TAI into geographical information in step 12 and step 14 can be PLMN operator dependent. However, it is expected that AMF conversion will normally be needed for a roaming UE to avoid VPLMN cell ID and TAI configuration in the HPLMN NEF. 15. In the case of LDR, the NEF may itself initiate the Namf_EventExposure Unsubscribe service operation, e.g. if when the UE's privacy setting stored in the UDM was changed. For every outstanding Deferred Location Request against that UE, the NEF shall perform a new privacy check based on the updated privacy setting stored in the UDM. If the privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request should be continued. Otherwise, if the privacy check does not pass, i.e. the Location estimate of the target UE is not allowed to be provided to the LCS Client, the NEF shall initiate a cancellation. Then AMF then releases all resources for the LDR request, and NEF shall send a notification of cancellation of LDR request to consumer AF or NF in the step 17a, 17b. 16a, 16b. The NEF returns the first UE location received at step 5 or step 13 or a confirmation of a request for deferred location received at step 5 in the case of a GMLC location service to the external AF (step 15a) or NF (step 15b). 17a, 17b. If one or more additional location reports are received at step 6 or step 14, the NEF returns one or more additional locations to the external AF (step 16a) or NF (step 16b). If step 15 occurs, a notification of cancellation of LDR request shall be sent to the consumer AF (step 17a) or consumer NF (step 17b). NOTE 5: As part of step 16 and step 17, the NEF converts any UE location received in the form of a cell ID or TAI into geographical information prior to sending the location to a consumer AF or NF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.5.2 Unified Location Service Exposure Procedure with routing via a UDM	Figure 6.5.2-1 shows the procedure used by an NEF to access the serving AMF for the UE when the NEF does not have direct access to the serving AMF or is configured to use UDM for AMF location event exposure service. When this procedure is used, steps 1-8 in Figure 6.5.2-1 replace steps 8-14 in Figure 6.5.1-1. Figure 6.5.2-1: Unified Location Service Exposure Procedure with routing by a UDM 1. The NEF invokes an Nudm_EventExposure Subscribe service operation towards the UDM for the target UE for location reporting and indicates whether a one-time UE location is requested or multiple UE locations for some triggering event and includes the UE identity (SUPI or GPSI) and information on location accuracy (e.g. cell ID or TA granularity). A correlation ID is also included. 2. The UDM invokes an Namf_EventExposure Subscribe service operation towards the serving AMF for the target UE for location reporting and includes the information received in the service operation for step 1 including the correlation ID and a URI for the NEF. 3. The AMF responds to the service operation in step 2. 4. The UDM responds to acknowledges the service operation in step 1. 5. The AMF performs a Network Triggered Service Request if needed as for step 11 of clause 6.5.1. 6. The AMF obtains a location of the UE or invokes a location reporting procedure with NG-RAN to obtain a UE location or multiple UE locations as for step 12 of clause 6.5.1. 7. The AMF invokes the Namf_EventExposure Notify service operation towards the NEF indicated by the URI received in step 2 and includes the first UE location obtained at step 6 and the correlation ID received at step 2. 8. If the AMF invokes a location reporting procedure with NG-RAN to obtain multiple UE locations at step 6, the AMF invokes one or more Namf_EventExposure Notify service operations towards the NEF to provide each additional UE location as in step 14 for clause 6.5.1.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.6 NG-RAN Location Service Exposure Procedure	The NG-RAN Location Service Exposure procedure is not supported in this Release of the specification.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7 Low Power Periodic and Triggered 5GC-MT-LR Procedures	The low power periodic and triggered 5GC-MT-LR procedures may be used to support a request from an external LCS client or AF for deferred location for periodic or triggered location events. The procedures may be used as alternatives to the procedures in clause 6.3.1 and clause 6.4. If the procedures are used, cancellation of the reporting of location events is still supported using the procedures in clause 6.3.2 and clause 6.3.3.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7.1 Event Reporting with no change of LMF	Figure 6.7.1-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic or Triggered Location Events using low power event reporting. This procedure is only applicable to a UE with E-UTRA access to 5GC. Figure 6.7.1-1: Low Power Periodic and Triggered 5GC-MT-LR Procedure with no change of LMF 1. Steps 1-23 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 are performed with the following exceptions. - At step 14, the AMF includes an indication in the Nlmf_Location_DetermineLocation Request service operation that the UE supports and is allowed to use Control Plane CIoT 5GS Optimisation as described in clause 5.31.4 of TS 23.501 [18]. - At step 16, if the AMF indicates the UE supports and is allowed to use Control Plane CIoT 5GS Optimisation at step 14 and if the LMF decides to allow Control Plane CIoT 5GS Optimisation, the LMF includes an indication in the LCS Periodic-Triggered Invoke Request that the UE is allowed to use Control Plane CIoT 5GS Optimisation to send Event Reports. The LMF may also include criteria indicating when Control Plane CIoT 5GS Optimisation may be used to send Event Reports. The criteria may include a maximum duration for sending Event Reports using Control Plane CIoT 5GS Optimisation, a maximum number of consecutive Event Reports to be sent using Control Plane CIoT 5GS Optimisation or both. NOTE 1: As part of negotiating 5G network behaviour during registration, a UE indicates in a Registration Request whether Control Plane CIoT 5GS Optimisation is supported for location event reporting. This indication may be passed to the LMF by the AMF at step 14 for clause 6.3.1. 2. The UE determines whether to report the event detected at step 22 in clause 6.3.1 using Control Plane CIoT 5GS Optimisation or using a NAS signalling connection. If the UE is currently in CM CONNECTED state or is not accessing E-UTRA connected to 5GC, the UE shall use a NAS signalling connection. Otherwise, the determination shall be based on criteria received from the LMF at step 14 in clause 6.3.1 when criteria are received. When the criteria include a maximum duration for sending event reports using Control Plane CIoT 5GS Optimisation, the UE shall report the event using a NAS signalling connection if the UE has not used a NAS signalling connection to report events during an immediately preceding time interval equal to the maximum duration. When the criteria include a maximum number of consecutive Event Reports to be sent using Control Plane CIoT 5GS Optimisation, the UE shall report the event using a NAS signalling connection if the UE has used Control Plane CIoT 5GS Optimisation to report each of the N previous events, where N equals the maximum number of consecutive Event Reports. In other cases, Control Plane CIoT 5GS Optimisation may be used to report the event if supported by the 3GPP access type. If use of a NAS signalling connection is determined, steps 24-31 for the procedure in clause 6.3.1 are performed and steps 3-11 below are skipped. If use of Control Plane CIoT 5GS Optimisation is determined, steps 3-11 below are performed. 3. If the UE and ng-eNB node both support EDT, the UE sends an RRCEarlyDataRequest message to the ng-eNB node and includes a NAS control plane service request. Otherwise, the UE established an RRC connection with the ng-eNB node and sends the NAS control plane service request. The NAS control plane service request includes an event report message which includes the information described in step 25 in clause 6.3.1 (e.g. the type of event being reported and any location measurements or location estimate obtained at step 23 in clause 6.3.1). The control plane service request also includes the deferred routing identifier received in step 16 in clause 6.3.1. The UE also includes a NAS Release Assistance Indication (NAS RAI) in the NAS message. The NAS RAI indicates a single response is expected. NOTE 2: Event reporting using Control Plane CIoT 5GS Optimisation requires a single Event report acknowledgment from the LMF. 4. The ng-eNB node forwards the NAS message to the AMF in an N2 Initial UE message and includes an "EDT Session" indication if EDT was used at step 3. 5. The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to either the serving LMF or any suitable LMF as described for step 25 for clause 6.3.1. The AMF includes an indication of Control Plane CIoT 5GS Optimisation in the service operation and the serving cell ID. 6. The AMF returns a NAS Service Accept to the ng-eNB node which is encapsulated in an N2 Downlink NAS Transport message. 7. If EDT was used at step 3, the ng-eNB node establishes an RRC connection to the UE. 8. The ng-eNB node sends an RRC DL Information Transfer message to the UE and includes the NAS Service Accept message received in step 6. 9. The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 for clause 6.3.1. 10. The AMF forwards the acknowledgment to the ng-eNB node in a NAS DL NAS Transport message which is encapsulated in an N2 Downlink NAS Transport message. The AMF also includes an "end indication" in the N2 message. NOTE 3: If the AMF determines more data or signalling may be pending for the UE, the AMF does not include the "end indication" at step 10 and step 12 below is not performed. 11. The ng-eNB node sends an RRC DL Information Transfer message to the UE and includes the NAS message received in step 10. 12. If the "end indication" was received in step 10, the ng-eNB node releases the RRC connection. 13. If a location estimate is needed for event reporting, the LMF determines the UE location using the location measurements and/or location estimate received in the event report at step 5 and/or the serving cell ID provided by the AMF at step 5. NOTE 4: The LMF does not attempt to obtain additional location measurements from the UE or from the NG-RAN. 14. Steps 28-31 for clause 6.3.1 are performed to send the event report to the external client or AF and to continue event detection at the UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7.2 Event Reporting with change of LMF	Figure 6.7.2-1 shows a procedure to enable change of the serving LMF when a UE sends an event report as at steps 3 and 4 in clause 6.7.1. Figure 6.7.2-1: Event Reporting with change of LMF Precondition: Step 1 in clause 6.7.1 has already been performed and steps 2-11 in clause 6.7.1 may have been performed or repeated. A serving LMF is used and the current serving LMF is LMF1. 1. Steps 2-4 for Event Reporting for no change of LMF in clause 6.7.1 are performed with the following exceptions. - At step 3, the NAS control plane service request includes a deferred routing identifier indicating LMF1. 2. Steps 3-8 for the LMF Change procedure in clause 6.4 are performed with the following exceptions. - At step 4, the Namf_Communication_N1MessageNotify service operation includes an indication of Control Plane CIoT 5GS Optimisation. - At step 6, the Nlmf_Location_LocationContextTransfer Request service operation includes an indication of Control Plane CIoT 5GS Optimisation and the serving cell ID. 3. Steps 7-10 for Event Reporting for no change of LMF in clause 6.7.1 are performed with LMF2 replacing the LMF in clause 6.7.1. The rest of the procedure in clause 6.7.1 then continues in step 11 with LMF2 retaining state information to enable support of subsequent event reports from the UE.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7.3 Event Reporting in RRC INACTIVE state for DL Positioning, RAT Independent Positioning or No Positioning	Figure 6.7.3-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic or Triggered Location Events when a UE is in RRC INACTIVE state and when DL positioning, RAT independent positioning or no positioning is used for event reporting. This procedure is only applicable to a UE with NR access to 5GC. Figure 6.7.3-1: Low Power Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state with DL Positioning, RAT Independent Positioning or No Positioning 1. Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 are performed with the following differences. - At step 16 in clause 6.3.1, the LMF indicates to the UE that DL positioning, RAT Independent positioning or no positioning will be used for subsequent location reporting events when the UE is in RRC INACTIVE state. If DL positioning or RAT independent positioning will be used, the LMF includes an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16, where the LPP positioning message requests DL location measurements, RAT independent location measurements or a location estimate based on these location measurements. If no location of the UE is needed for event reporting or if a location based on a Cell ID will suffice for the location QoS, the LMF does not include an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16. NOTE 1: A deferred routing identifier indicating a default LMF cannot be included in the LCS Periodic-Triggered Location Invoke sent at step 16 in clause 6.3.1 because for event reporting at steps 5-11 below. the LMF needs to know which type of positioning was indicated at step 1 in order to correctly support these subsequent steps. However, a default LMF would not know which type of positioning had been indicated at step 1. 2. The UE enters RRC INACTIVE state some time before an event is detected at step 22 or step 31 in clause 6.3.1. If the UE is not in RRC INACTIVE state when an event is detected at step 22 or step 31 in clause 6.3.1, then the UE follows the procedure described for steps 22-31 in clause 6.3.1 to report the event to the LMF and to the LCS Client or AF. NOTE 2: The LMF is not aware of whether the UE is in RRC INACTIVE state. This allows the LMF to follow the procedure described here or the procedure described in clause 6.3.1 for event reporting. With the procedure described here, a UE that was initially in RRC INACTIVE state can remain in RRC INACTIVE state after the procedure is complete. With the procedure in clause 6.3.1, a UE that was initially in RRC INACTIVE state could be moved into RRC CONNECTED state during the procedure in clause 6.3.1. 3. The UE monitors for and detects a trigger event as described for step 22 in clause 6.3.1. 4. If DL positioning or RAT independent positioning was indicated at step 1, the UE obtains the location measurements or location estimate requested in the LPP message received in step 1. If DL positioning or RAT independent positioning was not indicated at step 1, this step is skipped. 5. The UE sends an RRC Resume Request with small data transmission (SDT) to a receiving gNB node in the NG-RAN. The RRC Resume Request includes an RRC UL Information Transfer message containing an UL NAS TRANSPORT message that includes a supplementary services event report message. If DL positioning or RAT independent positioning was indicated at step 1, the UE includes an LPP positioning message in the supplementary services event report message that includes the location measurements or location estimate obtained at step 4. If DL positioning or RAT independent positioning was not indicated at step 1, the UE does not include an LPP positioning message in the supplementary services event report message. The event report message also includes other information described in step 25 in clause 6.3.1 (e.g. the type of event being reported). The UL NAS TRANSPORT message also include the deferred routing identifier received in step 16 in clause 6.3.1. 6. The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message. NOTE 3: If the receiving gNB node is not the anchor gNB node for the UE, the UL NAS TRANSPORT message may be forwarded to the serving AMF via the anchor gNB node. 7. The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to the serving LMF as described for step 25 in clause 6.3.1. 8. The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 in clause 6.3.1. NOTE 4: If there is a change of LMF according to clause 6.4, the acknowledgment includes a deferred routing identifier for the new LMF as described in clause 6.4. 9. The AMF forwards the acknowledgment to the receiving gNB node in a DL NAS TRANSPORT message which is encapsulated in an N2 Downlink NAS Transport message. NOTE 5: If the receiving gNB node is not the anchor gNB node for the UE, the DL NAS TRANSPORT message may be forwarded to the receiving gNB node via the anchor gNB node. 10. The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 10. 11. The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state. 12. Following step 11, the UE remains in RRC INACTIVE state. 13. If a location estimate is needed for event reporting, the LMF determines the UE location using the location measurements or location estimate received at step 7 or a Cell ID provided by the AMF at step 7. NOTE 6: The LMF does not attempt to obtain additional location measurements from the UE or from the NG-RAN. 14. Steps 28-31 for clause 6.3.1 are performed to send the event report to the LCS client or AF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7.4 Event Reporting in RRC INACTIVE state for UL Positioning	Figure 6.7.4-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic or Triggered Location Events when a UE is in RRC INACTIVE state and when UL positioning is used for event reporting. This procedure is only applicable to a UE with NR access to 5GC. Figure 6.7.4-1: Low Power Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state with UL Positioning 1. Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 are performed with the following differences. - At step 16 in clause 6.3.1, the LMF indicates to the UE that UL positioning may be used for subsequent location reporting events when the UE is in RRC INACTIVE state by not including an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16. NOTE 1: A deferred routing identifier indicating a default LMF cannot be included in the LCS Periodic-Triggered Location Invoke sent at step 16 in clause 6.3.1 because for event reporting at steps 4-11 below. the LMF needs to know which type of positioning was indicated at step 1 in order to correctly support these subsequent steps. However, a default LMF would not know which type of positioning had been indicated at step 1. 2. The UE enters RRC INACTIVE state some time before an event is detected at step 22 or step 31 in clause 6.3.1. If the UE is not in RRC INACTIVE state when an event is detected at step 22 or step 31 in clause 6.3.1, then the UE follows the procedure described for steps 22-31 in clause 6.3.1 to report the event to the LMF and to the LCS Client or AF. NOTE 2: The LMF is not aware of whether the UE is in RRC INACTIVE state. This allows the LMF to follow the procedure described here or the procedure described in clause 6.3.1 for event reporting. With the procedure described here, a UE that was initially in RRC INACTIVE state can remain in RRC INACTIVE state after the procedure is complete. With the procedure in clause 6.3.1, a UE that was initially in RRC INACTIVE state could be moved into RRC CONNECTED state during the procedure in clause 6.3.1. 3. The UE monitors for and detects a trigger event as described for step 22 in clause 6.3.1. 4. The UE sends an RRC Resume Request with small data transmission (SDT) to a receiving gNB node in the NG-RAN. The RRC Resume Request includes an RRC UL Information Transfer message containing an UL NAS TRANSPORT message that includes a supplementary services event report message. The UE does not include an LPP positioning message in the supplementary services event report message. The event report message includes other information described in step 25 in clause 6.3.1 (e.g. the type of event being reported). The UL NAS TRANSPORT message also includes the deferred routing identifier received in step 16 in clause 6.3.1. 5. The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message. NOTE 3: If the receiving gNB node is not the anchor gNB node for the UE, the UL NAS TRANSPORT message may be forwarded to the serving AMF via the anchor gNB node. 6. The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to the serving LMF as described for step 25 in clause 6.3.1. 7. The LMF uses the Network Assisted Positioning Procedure in clause 6.11.2 to request the receiving gNB node to provide an UL configuration to the UE at step 11. The receiving gNB node then determines an UL Configuration to be used later at step 11 and indicates this to the LMF. The LMF also uses the Non-UE Associated Network Assistance Data procedure in clause 6.11.3 to request UL location measurements of the UE by NG-RAN gNB nodes. NOTE 4: Because the UE is in RRC INACTIVE state and thus in CM CONNECTED state, step 2 of the Network Assisted Positioning Procedure in clause 6.11.2 whereby the AMF performs a Network Triggered Service Request will not be performed. This avoids a transition of the UE into RRC CONNECTED state. 8. The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 in clause 6.3.1. NOTE 5: If there is a change of LMF according to clause 6.4, the acknowledgment includes a deferred routing identifier for the new LMF as described in clause 6.4. 9. The AMF forwards the acknowledgment to the receiving gNB node in a DL NAS TRANSPORT message which is encapsulated in an N2 Downlink NAS Transport message. NOTE 6: If the receiving gNB node is not the anchor gNB node for the UE, the DL NAS TRANSPORT message may be forwarded to the receiving gNB node via the anchor gNB node. 10. The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 10. 11. The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state and includes the UL Configuration determined at step 7. 12. The UE transmits UL positioning signals according to the UL Configuration received at step 11. The NG-RAN gNB nodes that were requested to obtain UL location measurements at step 7 obtain the UL location measurements of the UL positioning signals transmitted by the UE. 13. The NG-RAN gNB nodes transfer the UL location measurements obtained at step 12 to the LMF according to the Non-UE Associated Network Assistance Data Procedure in clause 6.11.3. 14. Following step 13, the UE remains in RRC INACTIVE state. 15. The LMF determines the UE location using the UL location measurements received at step 13. NOTE 7: The LMF does not attempt to obtain additional location measurements from the UE or from the NG-RAN. 16. Steps 28-31 in clause 6.3.1 are performed to send the event report to the LCS client or AF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.7.5 Event Reporting in RRC INACTIVE state for UL+DL Positioning	Figure 6.7.5-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic or Triggered Location Events when a UE is in RRC INACTIVE state and when UL-DL positioning is used for event reporting. This procedure is only applicable to a UE with NR access to 5GC. Figure 6.7.5-1: Low Power Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state with UL+DL Positioning 1. Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 are performed with the following differences. - At step 16 in clause 6.3.1, the LMF indicates to the UE that UL+DL positioning will be used for subsequent location reporting events when the UE is in RRC INACTIVE state by including an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16, where the LPP positioning message identifies an UL-DL positioning method and requests DL location measurements for this positioning method. The LMF also includes a deferred routing identifier in the LCS Periodic-Triggered Location Invoke which is an identification of the LMF. NOTE 1: A deferred routing identifier indicating a default LMF cannot be included in the LCS Periodic-Triggered Location Invoke sent at step 16 in clause 6.3.1 because for event reporting at steps 4-20 below. the LMF needs to know which type of positioning was indicated at step 1 in order to correctly support these subsequent steps. However, a default LMF would not know which type of positioning had been indicated at step 1. 2. The UE enters RRC INACTIVE state some time before an event is detected at step 22 or step 31 in clause 6.3.1. If the UE is not in RRC INACTIVE state when an event is detected at step 22 or step 31 in clause 6.3.1, then the UE follows the procedure described for steps 22-31 in clause 6.3.1 to report the event to the LMF and to the LCS Client or AF. NOTE 2: The LMF is not aware of whether the UE is in RRC INACTIVE state. This allows the LMF to follow the procedure described here or the procedure described in clause 6.3.1 for event reporting. With the procedure described here, a UE that was initially in RRC INACTIVE state can remain in RRC INACTIVE state after the procedure is complete. With the procedure in clause 6.3.1, a UE that was initially in RRC INACTIVE state could be moved into RRC CONNECTED state during the procedure in clause 6.3.1. 3. The UE monitors for and detects a trigger event as described for step 22 in clause 6.3.1. 4. The UE sends an RRC Resume Request with small data transmission (SDT) to a receiving gNB node in the NG-RAN. The RRC Resume Request includes an RRC UL Information Transfer message containing an UL NAS TRANSPORT message that includes a supplementary services event report message. The UE includes an LPP positioning message in the supplementary services event report message that includes a request for an UL Configuration to support the UL+DL positioning method indicated to the UE at step 1. The event report message also includes other information described in step 25 in clause 6.3.1 (e.g. the type of event being reported). The UL NAS TRANSPORT message also includes the deferred routing identifier received in step 16 in clause 6.3.1. 5. The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message. NOTE 3: If the receiving gNB node is not the anchor gNB node for the UE, the UL NAS TRANSPORT message may be forwarded to the serving AMF via the anchor gNB node. 6. The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to the serving LMF as described for step 25 in clause 6.3.1. 7. The LMF uses the Network Assisted Positioning Procedure in clause 6.11.2 to request the receiving gNB node to provide an UL configuration to the UE at step 11. The receiving gNB node then determines an UL Configuration to be used later at step 11 and indicates this to the LMF. The LMF also uses the Non-UE Associated Network Assistance Data procedure in clause 6.11.3 to request UL location measurements of the UE by NG-RAN gNB nodes. NOTE 4: Because the UE is in RRC INACTIVE state and thus in CM CONNECTED state, step 2 of the Network Assisted Positioning Procedure in clause 6.11.2 whereby the AMF performs a Network Triggered Service Request will not be performed. This avoids a transition of the UE into RRC CONNECTED state. 8. The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 in clause 6.3.1. NOTE 5: If there is a change of LMF according to clause 6.4, the acknowledgment includes a deferred routing identifier for the new LMF as described in clause 6.4. 9. The AMF forwards the acknowledgment to the receiving gNB node in a DL NAS TRANSPORT message which is encapsulated in an N2 Downlink NAS Transport message. NOTE 6: If the receiving gNB node is not the anchor gNB node for the UE, the DL NAS TRANSPORT message may be forwarded to the receiving gNB node via the anchor gNB node. 10. The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 9. 11. The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state and includes the UL Configuration determined at step 7. 12. The UE transmits UL positioning signals according to the UL Configuration received at step 11. The UE also obtains DL location measurements as requested at step 1. The NG-RAN gNB nodes that were requested to obtain UL location measurements at step 7 obtain the UL location measurements of the UL positioning signals transmitted by the UE. 13. The NG-RAN gNB nodes transfer the UL location measurements obtained at step 12 to the LMF according to the Non-UE Associated Network Assistance Data Procedure in clause 6.11.3. 14. The UE sends an RRC Resume Request with small data transmission to the receiving gNB node. The RRC Resume Request includes an RRC UL Information Transfer message containing an UL NAS TRANSPORT message that includes a supplementary services event report message. The event report message indicates that this is a second event report associated with the first event report sent at step 4 and includes an LPP positioning message that includes the DL location measurements obtained at step 12. The UL NAS TRANSPORT message also includes the deferred routing identifier received in either step 16 in clause 6.3.1 or step 10 in this procedure if there was a change of LMF. NOTE 7: The LMF can be aware that UL+DL positioning is used from receipt at step 6 of the LPP positioning message in the supplementary services event report message that includes a request for an UL Configuration to support the UL+DL positioning method indicated to the UE at step 1. The LMF can thus expect to receive the second event report at step 14. 15. The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message. NOTE 8: If the receiving gNB node is not the anchor gNB node for the UE, the UL NAS TRANSPORT message may be forwarded to the serving AMF via the anchor gNB node. 16. The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to the serving LMF as described for step 25 in clause 6.3.1. 17. The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 in clause 6.3.1. 18. The AMF forwards the acknowledgment to the receiving gNB node in a DL NAS TRANSPORT message which is encapsulated in an N2 Downlink NAS Transport message. NOTE 9: If the receiving gNB node is not the anchor gNB node for the UE, the DL NAS TRANSPORT message may be forwarded to the receiving gNB node via the anchor gNB node. 19. The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 18. 20. The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state. 21. Following step 20, the UE remains in RRC INACTIVE state. 22. The LMF determines the UE location using the UL location measurements received at step 13 and the DL location measurements received at step 16. NOTE 10: The LMF does not attempt to obtain additional location measurements from the UE or from the NG-RAN. 23. Steps 28-31 in clause 6.3.1 are performed to send the event report to the LCS client or AF.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.8 Bulk Operation of LCS Service Request Targeting to Multiple UEs	The procedure described in this clause applies to 5GC_MT_LR and Deferred 5GC-MT-LR request targeting to a group of UE identified by an external/internal group ID, if available. Figure 6.8-1: Bulk operation of LCS service request targeting to multiple UEs 1. This step is the same as step 1 of clause 6.1.2 and step 1 of clause 6.3.1, with the difference that the LCS request is targeting a group of UE identified by a group ID. The GMLC may map the external/internal group ID to the list of UE ID (i.e. SUPI) using Nudm_SDM_Get (Group Identifier Translation, External Group Identifier) service operation. NOTE: Step 1b-1 assumes the LCS QoS provided by AF indicate "high-accuracy", and NEF determines the location request is handled by GMLC. 1b-2. The NEF shall send a Ngmlc_Location_ProvideLocation Request to the GMLC with the group of UE identified by a group ID to indicate a bulk operation procedure. If deferred location is requested the NEF shall include an Event type to indicate that deferred location is requested and provides an LDR reference number (Notification Correlation ID) to be used for event reporting at steps 6b-1 and 11b-1. If immediate location is requested the NEF shall not provide an Event type to indicate that immediate location is requested and provides a Notification Correlation ID to be used for reporting at steps 6b-1. 1c. he NF (e.g. NWDAF) shall send a Ngmlc_Location_ProvideLocation Request to the GMLC with the group of UE identified by a group ID to indicate a bulk operation procedure. 2a. If deferred location is requested from the LCS Client, the GMLC responds with an acknowledgment. 2b-1. The GMLC responds with a Ngmlc_Location_ProvideLocation Response. GMLC may decide whether completely or partially (i.e. accept part of the UE(s) within the group identified by the group ID in step 1) reject the location request. If GMLC decides to partially reject the location request, GMLC will respond to the LCS client /AF with a proper error cause. 2b-2. The NEF acknowledges the execution of the Nnef_EventExposure_Subscribe. 2c. If deferred location is requested from the NF, the GMLC responds with an acknowledgment. Steps 3 to 5 are carried out once per UE. 3. The GMLC invokes a Nudm_SDM_Get (LCS privacy, SUPI) service operation towards the UDM to get the UE LCS privacy profile of the target UE. The GMLC checks the privacy settings. For the UE whose privacy setting does not allow it to be located, steps 4 and 5 are skipped. The GMLC may also subscribe to and receive notification of UE privacy profile updates according to steps 0 and 4 of clause 6.12.1. 4. The GMLC invokes a Nudm_UECM_Get service operation towards the UDM of the target UE with SUPI of this UE. The UDM returns the current serving AMF ID to the GMLC. 5a. If no AMF ID is returned at step 4: - if it is a deferred location request and the GMLC supports the storage of the LCS service request for a group of UE, the GMLC subscribes the UE reachability status to the UDM using Nudm_EventExposure_Subscribe service operation with the data key "SUPI"; - otherwise, this step is skipped and the GMLC returns an appropriate error cause to the LCS client or NEF at step 6. 5b. If the UDM returns the current serving AMF ID to the GMLC at step 4: - the GMLC initiates 5GC_MT_LR procedure (from step 4 onwards) as described in clause 6.1.2, with the difference that Step 24 is skipped (as it is replaced by step 6 below); The GMLC shall not include the Notification Correlation ID received from NEF in step 1b-2. - or the GMLC initiates Deferred 5GC-MT-LR Procedure (from step 4 onwards) as described in clause 6.3.1 with the difference that steps 8,21 and 30 are skipped (as it is replaced by steps 2, 6 and 11 below) and that GMLC assign LDR reference numbers (separate number for each UE) to be used for event reporting at steps 20 and 29. 6a. The GMLC receives response messages as defined in clause 6.1.2 step 22 or 23 or GMLC receives notification messages as defined in clause 6.3.1 step 28 or 29. The GMLC sends one or more LCS Service Responses to the LCS Client to convey UE locations or event reports. 6b-1. The GMLC receives response messages as defined in clause 6.1.2 step 22 or 23 or GMLC receives notification messages as defined in clause 6.3.1 step 28 or 29. The GMLC maps the messages to the Request received in step 1b-2 and invokes one or more Ngmlc_Location_EventNotify service operations towards the NEF to convey UE locations or event reports. GMLC may aggregate one or more UE location estimates / event reports in each message sent to NEF. 6b-2. The NEF invokes one or more Nnef_EventExposure_Notify service operations towards the AF, to convey UE locations or event reports , received from GMLC in step 6b-1. 6c. The GMLC receives response messages as defined in clause 6.1.2 step 22 or 23 or GMLC receives notification messages as defined in clause 6.3.1 steps 28 or 29. The GMLC sends one or more Ngmlc_Location_EventNotify to the NF to convey UE locations or event reports. 7. For the deferred location request, if any UE in the group didn't get its serving AMF ID at step 4, the GMLC may store the LCS service request locally if the GMLC supports the storage of the LCS service request for a group of UE; otherwise, this step is skipped. Further steps apply to the UEs of the group who was not registered to the network when the LCS service request is received at GMLC. 8. UE performs the registration as described in clause 4.2.2 of TS 23.502, during which an AMF is selected to serve the UE, and the AMF ID is stored into UDM. 9. UDM notifies the GMLC who had subscribed the UE registration at step 5a using Nudm_EventExposure_Notify service operation, which includes "SUPI" and UE registration status. 10. GMLC initiates Deferred 5GC-MT-LR Procedure as described in step 5b. 11a. The GMLC receives notification messages as defined in clause 6.3.1 step 28 or 29. The GMLC sends one or more LCS Service Responses to the LCS Client to convey UE locations or event reports. 11b-1. The GMLC receives notification messages as defined in clause 6.3.1 step 28 or 29. The GMLC maps the messages to the Request received in step 1b-2 and invokes one or more Ngmlc_Location_EventNotify service operations towards the NEF to convey UE locations or event reports. GMLC may aggregate one or more UE location estimates / event reports in each message sent to NEF. 11b-2. The NEF invokes one or more Nnef_EventExposure_Notify service operations towards the AF, to convey event reports received from GMLC in step 11b-1. 11c. The GMLC receives notification messages as defined in clause 6.3.1 steps 28 or 29. The GMLC sends one or more Ngmlc_Location_EventNotify to the NF to convey UE locations or event reports.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.9 Procedures to Support Non-3GPP Access
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.9.1 Common Positioning Procedures when a UE is served by only one PLMN	Figure 6.9.1-1 shows the common positioning procedures to support location services with non-3GPP access when UE is served by only one PLMN, which provides either non-3GPP access only or both 3GPP access and non-3GPP access. The common positioning procedures can be triggered by: - 5GC-NI-LR procedure (described in clause 6.10.1), which assumes that the serving AMF is aware of the emergency session initiation - e.g. due to supporting an Emergency Registration procedure or assisting in establishing an emergency PDU Session. If such emergency session procedure is initiated via non-3GPP access, the AMF provides access type to LMF in step 2 in clause 6.10.1,the LMF shall use the access type provided by AMF in step 2 in clause 6.9.1; or - 5GC-MT-LR procedure (described in clause 6.1.1 and 6.1.2 and 6.10.2), which is applicable to a request from an LCS client for a current location. - 5GC-MO-LR procedure (described in clause 6.2), for this case, the access type is selected by the UE using the UE Local Configuration to initiate MO-LR procedure which is the same as the 5GC-MO-LR Procedure in clause 6.2 with following differences: - The AMF shall in step 4 of clause 6.2 include UE connectivity state per access type. - In step 5 of clause 6.2 the modification in this clause shall be applied, the LMF shall also determine positioning methods and the positioning access type, which can be different with the access type selected by the UE. - Deferred 5GC-MT-LR procedure for periodic, triggered and UE available location events (described in clause 6.3.1), which is applicable to report of location event for a deferred 5GC-MT-LR procedure. - Unified Location Service Exposure Procedure (described in clause 6.5), which allows an NEF to provide location service exposure to an NF in HPLMN or to an external AF outside the HPLMN when requested by the NF or the AF. Figure 6.9.1-1: Common positioning procedures when UE is served by the one PLMN 1. The AMF invokes the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the UE, which includes the QoS requirement and UE connectivity state per access type. 2. The LMF determines the positioning access type and the positioning method based on the UE/network positioning capability, the QoS requirement and UE connectivity state per access type received from the AMF and the locally configured operator policy. The LMF may also determine the access type for transmission of an LPP message to the UE (e.g. in order to ensure the UE will be in a connected state for the selected positioning access type). When the LPP protocol in TS 37.355 [20] is determined to be used to obtain location information from the UE and the UE has both 3GPP and non-3GPP access, the AMF shall decide which access type should be used to transmit the location information if the LMF did not select an access type. For example, if the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in Non-3GPP access, AMF may prefer to select the N3IWF/TNGF/W-AGF to relay positioning signalling to UE, rather than performing paging procedures via the 3GPP access. When the NRPPa protocol in TS 38.455 [15] is determined to be used to obtain location information from the NG-RAN or N3IWF/TNGF/W-AGF: - In the case that 3GPP Access is determined to be used to transmit the location information, the Network Assisted Positioning procedure in step 3b and/or the obtaining Non-UE Associated Network Assistance Data procedure in step 3c shall be performed. - In the case that non-3GPP Access is determined to be used to obtain the location information, the Network Assisted Positioning procedure in step 3e shall be performed. When the LPP protocol in TS 37.355 [20] is determined to be used to obtain location information from the UE: - In the case that 3GPP Access is determined to be used to relay the location information, the UE Assisted and UE Based Positioning procedure in step 3a shall be performed. - In the case that non-3GPP Access is determined to be used to relay the location information, the UE Assisted and UE Based Positioning procedure in step 3d shall be performed. 3a. This step is same as the UE Assisted and UE Based Positioning procedure in clause 6.11.1. 3b. This step is same as the Network Assisted Positioning procedure in clause 6.11.2 with the difference that step 1 of clause 6.11.2 includes the selected Access Type (i.e. 3GPP access). The AMF forwards the Network Positioning message to the NG-RAN in step 3 of clause 6.11.2 based on the received Access Type. 3c. This step is same as the Obtaining Non-UE Associated Network Assistance Data procedure in clause 6.11.3. 3d. This step is same as the UE Assisted and UE Based Positioning procedure in clause 6.11.1 with the following difference: - The NG-RAN in clause 6.11.1 is replaced by the N3IWF/TNGF/W-AGF in Figure 6.9.1-1; - Steps 2 and 5 in clause 6.11.1 are omitted; - The location information returned by the UE can include information specified in clause 5.3.1. 3e. This step is same as the Network Assisted Positioning procedure in clause 6.11.2 with the following difference: - The NG-RAN in clause 6.11.2 is replaced by the N3IWF/TNGF/W-AGF in Figure 6.9.1-1; - Steps 2 and 4 in clause 6.11.2 are omitted; - The Access Type, i.e. non-3GPP access type, which is selected to provide the location information is included in step 1 of clause 6.11.2. The AMF forwards the Network Positioning message to the N3IWF/TNGF/W-AGF based on the received Access Type in step 1 of clause 6.11.2. - The location information returned in step 5 of clause 6.11.2 is specified in clause 5.3.1. The UE is replaced by 5G-RG in the case of wireline access type.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.9.2 MT-LR Procedures when a UE is served by Different PLMNs for 3GPP Access and Non-3GPP Access	Figure 6.9.2-1 and Figure 6.9.2-2 show the enhanced MT-LR positioning procedures to support location service with non-3GPP access when the UE is served by different PLMNs for 3GPP access and non-3GPP access. The procedures can be triggered by the 5GC-MT-LR Procedures described in clause 6.1.1, clause 6.1.2 and clause 6.3, which are applicable to a request from an LCS client for an immediate current location or a deferred location. Figure 6.9.2-1: MT-LR positioning procedures when UE is served by the two VPLMNs 1. The step is same as step 1 in clause 6.1.1 or clause 6.3.1. 2. The step is same as step 2 in clause 6.1.1 or clause 6.3.1. 3. The step is same as step 3 in clause 6.1.1 or clause 6.3.1 with the difference that when the UE is served by more than one AMF the UDM provides to the HGMLC for each access type, - serving AMF identity with the corresponding PLMN Id, - possibly a VGMLC address. 4. When the HGMLC identifies that the UE is served by different PLMNs according to the returned information from the UDM in step 3 it may retrieve the CM state(s) per Access Type from the candidate AMFs by using Namf_EventExposure service, or from the UDM using Nudm_EventExposure service. The HGMLC selects one access type and its associated AMF based on the UDM returned information in step 3, QoS requirement, CM state(s) per Access type of the UE, PLMN identity and/or the locally configured operator policy. NOTE: The locally configured operator policy in the HGMLC can include access type and CM state and PLMN priority for positioning. For example, the local policy can be 3GPP access first and/or connected state first and/or V-PLMN and/or H-PLMN first. 5. The HGMLC forwards the location request to the VGMLC-1 and may include the V-AMF-1 identity received in step 3 and the target UE identity (e.g. SUPI). 6. The VGMLC-1 invokes the Namf_Location_ProvideLocation_Request service operation to forward the location request to the V-AMF-1. Then the V-LMF-1 receives the location request from the V-AMF-1. 7. This step is same as step 2-3 of the Common Positioning Procedures in clause 6.9.1. 8-9. The VGMLC-1 receive the location service response from the V-LMF-1 and for a request for an immediate location, returns positioning results to the HGMLC. For an immediate location, the location service response contains positioning information, the information about the positioning method used and the indication of whether the obtained location estimate satisfies the requested LCS QoS (e.g. accuracy) or not (described in clause 9.1.1 of TS 23.271 [4]). For a request for a deferred location, the location service response indicates whether the location request was accepted. 10. For a request for an immediate location, if the HGMLC identifies that the location service response from the chosen PLMN meets required LCS QoS, it returns the results to the LCS Client directly. Otherwise, the HGMLC may forward the location request to another AMF (in another PLMN) so as to obtain the positioning result which can meet required LCS QoS shown as step 11. For a request for a deferred location, if the HGMLC identifies that location service was accepted (by the chosen PLMN), it returns this indication to the LCS Client directly. Otherwise, the HGMLC may forward the location request to another AMF (in another PLMN). 11. This step obtains the immediate positioning information or requests a deferred location from another PLMN, the details are the same as steps 5-9. 12-13. The HGMLC returns a location service response to the LCS client. For a request for immediate location, if the positioning result from the other PLMN meets the QoS requirement, the HGMLC returns it to the LCS client. Otherwise, the HGMLC returns final location service response without including any positioning result. For a request for deferred location, if the result from the other PLMN indicates acceptance of the location request, the HGMLC returns this to the LCS client. Otherwise, the HGMLC returns a final location service response indicating failure of the deferred location request. Figure 6.9.2-2: MT-LR positioning procedures when UE is served by HPLMN and VPLMN Figure 6.9.2-2 shows the MT-LR positioning procedures when the UE is served by the H-PLMN and a V-PLMN. The difference with procedures shown in Figure 6.9.2-1 is that the HGMLC interacts with AMF directly shown in step 11 of Figure 6.9.2-2 without involving VGMLC shown in step 11 of Figure 6.9.2-1. In scenarios where the HGMLC prioritizes location by the H-PLMN rather than V-PLMN at step 4, steps 5-9 may be replaced by step 11 and step 11 (when step 11 occurs) is then replaced by steps 5-9.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.9.3 MO-LR Procedures when UE is served by the Different PLMNs via 3GPP Access and Non-3GPP Access	When UE is served by the different PLMNs via 3GPP access and Non-3GPP access, UE uses the UE Local Configuration to select the access to initiate MO-LR procedure which is the same as the 5GC-MO-LR Procedure in clause 6.2. If Non-3GPP access is selected, the following difference exists: - The NG-RAN in 5GC-MO-LR Procedure in clause 6.2 is corresponding to the N3IWF/TNGF; - Step 5 in 5GC-MO-LR Procedure in clause 6.2 is the same as step 3d or 3e in Common Positioning Procedure when UE is served by the same PLMN in clause 6.9.1.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.9.4 NI-LR Procedures when a UE is served by Different PLMNs for 3GPP access and non-3GPP access	When UE is served by the different PLMNs via 3GPP access and non-3GPP access, the UE selects one access to register to the 5GC for emergency services as defined in TS 23.167 [10], or request the establishment of a PDU Session related to an emergency session. The NI-LR procedures are the same as the 5GC-NI-LR Procedure (described in clause 6.10.1) with the difference that: - if the procedures are performed for non-3GPP access, NG-RAN in Figure 6.10.1 is replaced by an N3IWF/TNGF/W-AGF and the UE Positioning in step 3 in Figure 6.10.1 is performed according to steps 3d and 3e in Figure 6.9.1-1. - In step 2 in 5GC-NI-LR Procedure in clause 6.10.1, AMF also provides access type to LMF. LMF shall use the access type provided by AMF for positioning. The UE is replaced by 5G-RG in the case of wireline access type.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10 Procedures dedicated to Support Regulatory services
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10.1 5GC-NI-LR Procedure	Figure 6.10.1-1 shows a Network Induced Location Request (NI-LR) procedure for a UE in the case where the UE initiates an emergency session or other session using NG-RAN. The procedure assumes that the serving AMF is aware of the regulatory service associated with the session (e.g. emergency session initiation - e.g. due to supporting an Emergency Registration procedure or assisting in establishing an emergency PDU Session). The procedure can also be used to verify UE location for NR satellite access. Figure 6.10.1-1: 5GC Network Induced Location Request (5GC-NI-LR) for a UE 1. A trigger for AMF to initiate the 5GC-NI-LR procedure happens, e.g. the UE registers to the 5GC for emergency services or requests the establishment of a PDU Session related to an applicable regulatory service (e.g. emergency session initiation) or the AMF decides to verify UE location via LCS procedure for a UE registered for NR satellite access. 2. For verifying UE location via LCS service for NR satellite access this step is mandatory, for other triggers this step is optional. The AMF selects an LMF based on NRF query or configuration in AMF and invokes the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the serving cell identity of the Primary Cell in the Master RAN node and the Primary Cell in the Secondary RAN node when available based on Dual Connectivity scenarios, and an indication of a location request from a regulatory services client (e.g. emergency services) and may include an indication if UE supports LPP, the required QoS and Supported GAD shapes, the UE Positioning Capability if available. When AMF needs to know the geographical area of the UE to check whether the PLMN is allowed to operate in the area, an indication of this is included. When AMF needs to verify the location of the UE when a UE registers via NR satellite access, the AMF includes in indication in the request to the LMF that the request is for UE location verification. If any of the procedures in clause 6.11.1 or 6.11.2 are used the service operation includes the AMF identity. Optionally, the AMF may also request UE related analytics containing UE location information (e.g., UE mobility analytics) from NWDAF to assist with UE location verification for NR satellite access as described in clause 6.21.2. 3. [Conditional] If step 2 occurs, the LMF performs one or more of the positioning procedures described in clause 6.11.1, 6.11.2 and 6.11.3. If the AMF included an indication at step 2, the LMF maps the UE location to a geographical area where a PLMN is or is not allowed to operate. 4. [Conditional] If step 3 occurs, the LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the UE. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. The service operation also includes the UE Positioning Capability if the UE Positioning Capability is received in step 3 including an indication that the capabilities are non-variable and not received from AMF in step 2. When UE geographical area determination for location verification is indicated at step 2, the service operation also returns the geographical area where a PLMN is or is not allowed to operate determined at step 3. NOTE 1: Any remaining procedures for regulatory services other than emergency services are not addressed in this flow. The remaining steps are applicable for emergency services. 5. [Conditional] For emergency services, the AMF selects an GMLC based on NRF query or configuration in AMF. The information regarding the endpoint in the GMLC to deliver the event notification, is obtained from the NRF as specified in clause 7.1.2 of TS 23.501 [18] or from local configuration in the AMF. AMF invokes the Namf_Location_EventNotify service operation towards the selected GMLC to notify the GMLC of an emergency session initiation. The service operation includes the SUPI or the PEI, and the GPSI if available, the identity of the AMF, an indication of an emergency session and any location obtained in step 3. 6. [Conditional] For emergency services, the GMLC forwards the location to an external emergency services client or may wait for a request for the location from the external emergency services client (not shown in Figure 6.10.1-1) before forwarding the location. 7. [Conditional] For emergency services, the emergency services session and emergency PDU Session are released. 8. [Conditional] For emergency services, the AMF invokes the Namf_Location_EventNotify service operation towards the GMLC to notify the GMLC that the emergency session was released to enable the GMLC and LRF to release any resources associated with the emergency session.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10.2 5GC-MT-LR Procedure without UDM Query	Figure 6.10.2-1 illustrates a location request for an emergency services session, where an emergency services client (e.g. a Public Safety Answering Point) identifies the target UE and the serving LRF using correlation information that was previously provided to it by the IMS Core. The signalling used to provide the correlation information to the PSAP is defined in TS 23.167 [10]. The correlation information may be used by the LRF to retrieve other information previously provided to it by the IMS Core and/or AMF as described for Figure 6.10.1-1. This allows the GMLC associated with the LRF to request a location from the AMF without needing to query the UDM of the target UE for the serving AMF address. This scenario therefore supports location of emergency sessions from roamers and USIM-less and other non-registered UEs, and requires that identifying information for the UE and AMF have been provided to the GMLC/LRF as described in clauses 6.10.1 and 6.10.3. Figure 6.10.2-1: 5GC-MT-LR Procedure without UDM Query 1. The external emergency services client (e.g. a PSAP) sends a request to the LRF for a location for the target UE and includes correlation information identifying the target UE. The request may include the required QoS and Supported GAD shapes. The LRF address and the correlation information would have been previously provided to the external client when the emergency session from the UE was established. 2. The LRF/GMLC determines the AMF by associating the correlation information received from the external client with other information received previously from the AMF as described in step 5 of clause 6.10.1 and step 7 of clause 6.10.3. The GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI or the PEI or GPSI and an indication of a location request from an emergency services client and may include the required QoS and Supported GAD shapes. The AMF identifies the target UE using the SUPI or in the case of a USIM-less emergency session, or non-registered USIM emergency session, the PEI. 3. The AMF selects an LMF based on NRF query or configuration in AMF and invokes the Nlmf_Location_DetermineLocation service operation towards the LMF to request the current location of the UE. The service operation includes a LCS Correlation identifier, the serving cell identity and an indication of a location request from an emergency services client and may include an indication if UE supports LPP, the required QoS and Supported GAD shapes, UE Positioning Capability if available. If any of the procedures in clause 6.11.1 or clause 6.11.2 are used the service operation includes the AMF identity. 4. The LMF performs one or more of the positioning procedures described in clauses 6.11.1, 6.11.2 and 6.11.3. 5. The LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the current location of the UE. The service operation includes the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. The service operation also includes the UE Positioning Capability if the UE Positioning Capability is received in step 4 including an indication that the capabilities are non-variable and not received from AMF in step 3. 6. The AMF returns the Namf_Location_ProvidePositioningInfo Response towards the GMLC/LRF to return the current location of the UE. The service operation includes the LCS Correlation identifier, the location estimate, its age and accuracy and may include information about the positioning method and the timestamp of the location estimate. 7. The LRF sends the location service response to the external emergency services client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10.3 Location continuity for Handover of an Emergency session from NG-RAN	Figure 6.10.3-1 shows support for location continuity for handover of an emergency session from NG-RAN on the source side to either NG-RAN or another 3GPP RAN on the target side. The procedure applies when control plane location according to Figures 6.10.1-1 and 6.10.2-1 is used for location of the UE on the source side. The procedure is based on the procedures for location continuity currently defined in clause 9.4.5.4 of TS 23.271 [4]. NOTE: If User Plane (SUPL) Location Protocol [49] is used on the source (NG-RAN) side, then the current procedure for location continuity in TS 23.271 [4] can be used. Figure 6.10.3-1: Location Continuity for Handover of an Emergency session from NG-RAN 1. Following the request for an emergency session, the UE establishes a PDU Session for emergency services and an IMS emergency session for NG-RAN access, during which an LRF is assigned in the serving network IMS and a source GMLC may be chosen. The 5GC-NI-LR procedure of Figure 6.10.1-1 is also performed which provides the source AMF identity to the GMLC and LRF and optionally an initial location for the UE. 2. At some later time, the LRF may need the UE location and requests the source GMLC to invoke the Namf_Location_ProvidePositioningInfo service operation towards the AMF to request the current location of the UE. The service operation includes the SUPI or the PEI, the required QoS and an indication of a location request from an emergency services client. 3. If step 2 occurs or if support for an NI-LR is required, the source AMF starts a location session to obtain the location of the UE as described in clause 6.10.2 or clause 6.10.1. 4. The source AMF receives a request to handover the UE to a cell associated with a different target node which may be another AMF for intra-RAN handover or a different type of node (e.g. an MME) for inter-RAN handover (e.g. to E-UTRAN connected to EPC). 5. The handover procedure is executed as specified in clause 4.9.1.3 of TS 23.502 [19]. 6. Any location session started in step 3 may terminate normally before step 6. If not, the source AMF shall abort the location session once step 5 is complete. 7a. If steps 2 and 3 has occurred, the source AMF returns the Namf_Location_ProvidePositioningInfo Response towards the GMLC to return any location estimate and the timestamp of the location estimate (if available) obtained for the UE. The service operation includes the target node identity. 7b. If steps 2 and 7a do not occur, the source AMF may invoke the Namf_Location_EventNotify service operation towards the source GMLC (i.e. the GMLC used in step 1) to indicate the handover. The service operation includes the SUPI or the PEI and the GPSI if available, an event type indicating handover and the identity of the target node. 8a. For inter-RAN handover (e.g. to E-UTRAN connected to EPC) and if control plane location will be used on the target side, the target node (e.g. MME) may send a Subscriber Location Report to a GMLC on the target side after completion of the handover in step 6. The Subscriber Location Report carries the UE identity (IMSI, MSISDN and/or IMEI), an event type indicating handover and the identity of the target node. The target node may determine the target GMLC from configuration information. 8b. For intra-RAN handover and if control plane location will be used on the target side, the target AMF may invoke the Namf_Location_EventNotify service operation towards the GMLC to indicate the handover. The service operation includes the SUPI or the PEI and the GPSI if available, an event type indicating handover and the identity of the target node. 9. Reconfiguration of the LRF and the source and target GMLCs may occur in a manner outside the scope of 3GPP. 10. If the LRF needs a location estimate for the UE after handover has occurred and if control plane location is used on the target side, the LRF may instigate an MT-LR request via the target Node.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10.4 5GC-MT-LR multiple location procedure without UDM Query	Figure 6.10.4-1 illustrates an extension procedure of 5GC-MT-LR procedure without UDM Query for the regulatory location service defined in clause 6.10.2. This procedure is applicable for providing multiple location estimates of the target UE to emergency services client. Figure 6.10.4-1: 5GC-MT-LR Multiple Location Procedure without UDM Query 1. Steps 1-3 for 5GC-MT-LR procedure without UDM Query in clause 6.10.2 are performed with the following differences: - At step 1 in clause 6.10.2 the request from external emergency client (e.g. a PSAP) location services client may include the acceptance of INTERMEDIATE response and maximum response time. - At step 2 in clause 6.10.2 Namf_Location_ProvidePositioningInfo service operation invoked by GMLC may include the acceptance of INTERMEDIATE response and maximum response time, GMLC contact address and LIR reference number. The LIR reference number is allocated by GMLC based on predefined rule. - At step 3 in clause 6.10.2 Nlmf_Location_DetermineLocation service operation invoked by AMF may include the acceptance of INTERMEDIATE response and maximum response time, GMLC contact address, and LIR reference number. AMF can overwrite maximum response time to avoid timeout. 2. LMF performs positioning procedures and determines multiple location estimates during the session. 2.1 This step is executed if INTERMEDIATE response is available. The LMF invokes an Nlmf_Location_EventNotify service operation towards GMLC and provides the INTERMEDIATE location of the UE and timestamp of the location estimate, and LIR reference number, and INTERMEDIATE event type. 2.2 This step is executed if step 2.1 was executed. The GMLC sends the INTERMEDIATE location of the UE and timestamp of the location estimate to external location services client. 3. Based on step 5 in clause 6.10.2 the LMF returns the Nlmf_Location_DetermineLocation Response towards the AMF to return the FINAL location of the UE. LMF ensures that FINAL location will be transferred towards AMF within the maximum response time. 4. Steps 6-7 for 5GC-MT-LR procedure without UDM Query in clause 6.10.2 are performed with the following differences: - At step 7 the FINAL location is sent from GMLC to the external services client.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.10.5 Multiple location procedure for multiple emergency LCS clients	The multiple location procedure for multiple emergency LCS clients (e.g. routing entities including routing proxy or a redirect server defined in TS 23.167 [10]) in the same emergency session is an extension procedure of 5GC-MT-LR multiple location procedure without UDM Query defined in clause 6.10.4, with following differences: 1. There is one or a sequence of location request(s) from one or a series of emergency LCS clients' (e.g. LCS requests for routing defined in clauses 4.3.4 and 6.10). GMLC identifies by the LCS Clients' requests (e.g. by LCS client profile as emergency routing entity, or the request being HELD [52], etc.) that it is an emergency call routing procedure and carries out the multiple location procedure defined in clause 6.10.4. The INTERMEDIATE tagging in the request defined in 6.10.4 and the response time in the request are not mandatory in this case. 2. At step 2.2 in clause 6.10.4, GMLC starts responding to one or a series of the request(s) from different external emergency clients based on the available cached INTERMEDIATE/FINAL result(s) from LMF. When GMLC receives and responds to the requests from multiple emergency LCS clients, GMLC may process the request as per configurations of multiple LCS clients' profiles and/or request parameters (e.g. maximum response time, maximum age of location, etc.). NOTE: It depends on operator's policy and/or regulatory requirement(s) how GMLC responds with the result from the available cached INTERMEDIATE/FINAL result(s), e.g. the most recent one or the most accurate one.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11 Common Sub-Procedures
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11.0 General	The procedures defined in clause 6.11 are applicable to both a UE and PRU. Wherever, a UE is referenced in these procedures, a PRU may be used instead.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11.1 UE Assisted and UE Based Positioning Procedure	Figure 6.11.1-1 shows a positioning procedure used by an LMF to support UE based positioning, UE assisted positioning and delivery of assistance data. The procedure is based on use of the LPP protocol defined in TS 37.355 [20] between the LMF and UE. Figure 6.11.1-1: UE Assisted and UE Based Positioning Procedure Precondition: A LCS Correlation identifier and the AMF identity has been passed to the LMF by the serving AMF. 1. The LMF invokes the Namf_Communication_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Downlink (DL) Positioning message to the UE. The service operation includes the DL Positioning message. The Session ID parameter of the Namf_Communication_N1N2MessageTransfer service operation is set to the LCS Correlation identifier. The Downlink Positioning message may request location information from the UE, provide assistance data to the UE or query for the UE capabilities if the UE Positioning Capability is not received from AMF. 2. If the UE is in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19] to establish a signalling connection with the UE. 3. The AMF forwards the Downlink Positioning message to the UE in a DL NAS TRANSPORT message. The AMF includes a Routing identifier, in the DL NAS TRANSPORT message, which is set to the LCS Correlation identifier. The Downlink Positioning message may request the UE to response to the network, e.g. may request the UE to acknowledge the Downlink Positioning message, to return location information or to return capabilities, as defined in TS 37.355 [20]. 4. The UE stores any assistance data provided in the Downlink Positioning message and performs any positioning measurements and/or location computation requested by the Downlink Positioning message. 5. If the UE has entered CM-IDLE state during step 4 and needs to responses to the request received in step 3, the UE instigates the UE triggered Service Request as defined in clause 4.2.3.2 of TS 23.502 [19] in order to establish a signalling connection with the AMF. 6. [Conditional] The UE sends to the AMF the Uplink Positioning message included in a NAS TRANSPORT message, e.g. to acknowledge the Downlink Positioning message, to return any location information obtained in step 4 or returns any capabilities, as requested in step 3. When the UE sends Uplink Positioning message in a NAS TRANSPORT message, the UE shall also include in the UL NAS TRANSPORT message the Routing identifier received in step 3. 7. [Conditional] The AMF invokes the Namf_Communication_N1MessageNotify service operation towards the LMF indicated by the routing identifier received in step 6. The service operation includes the Uplink Positioning message received in step 6 and the LCS Correlation identifier. Steps 6 and 7 may be repeated if the UE needs to send multiple Uplink Positioning messages to respond to the request received in Step 3. Steps 1 to 7 may be repeated to send new assistance data, and to request further location information and further UE capabilities.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11.2 Network Assisted Positioning Procedure	Figure 6.11.2-1 shows a procedure that may be used by an LMF to support network assisted and network based positioning. The procedure may be based on UE associated NRPPa signalling in TS 38.455 [15] between the LMF and NG-RAN. Figure 6.11.2-1: Network Assisted Positioning Procedure Precondition: A LCS Correlation identifier and the AMF identity have been passed to the LMF by the serving AMF. In the case of PRU, LCS Correlation identifier is generated by LMF and provided to AMF during PRU Registration Accept message. 1. The LMF invokes the Namf_Communication_N1N2MessageTransfer service operation towards the AMF to request the transfer of a Network Positioning message to the serving NG-RAN node (gNB or ng-eNB) for the UE. The service operation includes the Network Positioning message and may indicate if the positioning is initiated towards a PRU and the LCS Correlation identifier. The Network Positioning message may request location information for the UE from the NG-RAN and may include UE unaware indication if it is received by LMF from AMF. LMF may provide an LPHAP Assistance Information to RAN in an NRPPa message, if LPHAP indication is received in step 11 clause 6.1.2. 2. If the UE is in CM IDLE state and there is no UE unaware indication for the UE in the UE's location context, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 [19], to establish a signalling connection with the UE. If positioning towards a PRU is indicated in step 1, the AMF verifies the UE is a valid PRU before initiating the procedure. If the UE is in CM-IDLE state and there is UE unaware indication for the UE in the UE's location context, the AMF should reject the forwarding request of the Network Positioning message with a proper rejection cause value and steps 3-6 are skipped. 3. The AMF forwards the Network Positioning message to the serving NG-RAN node in an N2 Transport message. The AMF includes a Routing identifier, in the N2 Transport message, identifying the LMF. 4. The serving NG-RAN node obtains any location information for the UE requested in step 3. If UE unaware indication is received in the Network Positioning message, and the UE is in RRC_INACTIVE state, the NG-RAN rejects the Network Positioning message with appropriate rejection cause (e.g. UE cannot be paged). 5. The serving NG-RAN node returns any location information obtained in step 4 to the AMF in a Network Positioning message included in an N2 Transport message. The serving NG-RAN node shall also include the Routing identifier in the N2 Transport message received in step 3. 6. The AMF invokes the Namf_Communication_N2InfoNotify service towards the LMF indicated by the routing identifier received in step 5. The service operation includes the Network Positioning message received in step 5 and the LCS Correlation identifier. Steps 1 to 6 may be repeated to request further location information and further NG-RAN capabilities.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11.3 Obtaining Non-UE Associated Network Assistance Data	Figure 6.11.3-1 shows a procedure which may be used by an LMF to support network assisted and network based positioning. This procedure is not associated with a UE location session. It is used to obtain network assistance data from a NG-RAN node (e.g. gNB or ng-eNB). The procedure may be based on non-UE associated NRPPa signalling in TS 38.455 [15] between the LMF and NG-RAN. Figure 6.11.3-1: Procedure for Obtaining Non-UE Associated Network Assistance Data NOTE 1: It is not required that serving AMF to be used in this procedure. To support location service in the PNI-NPN, local AMF is used instead of serving AMF, as defined in clause 5.13. 1. The LMF invokes the Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF to request the transfer of a Network Positioning message to a NG-RAN node (gNB or ng-eNB) in the NG-RAN. The service operation includes the Network Positioning message and the target NG-RAN node identity. The Network Positioning message may request position related information from the NG-RAN. 2. The AMF forwards the Network Positioning message to the target NG-RAN node indicated in step 1 in an N2 Transport message. The AMF includes a Routing identifier, in the N2 Transport message, identifying the LMF. 3. The target NG-RAN node obtains any position related information requested in step 2. 4. The target NG-RAN node returns any position related information obtained in step 3 to the AMF in a Network Positioning message included in an N2 Transport message. The target NG-RAN node shall also include the Routing identifier in the N2 Transport message received in step 2. 5. The AMF invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 4. The service operation includes the Network Positioning message received in step 4. Steps 1 to 5 may be repeated to request further position related information from the NG-RAN. NOTE 2: LCS Correlation ID is not applicable to this procedure.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.11.4 Positioning Procedure over User Plane	The flow below shows a positioning procedure used by an LMF and/or UE over User Plane. The procedure is based on use of the LPP protocol defined in TS 37.355 [20] between the LMF and UE. Prerequisite of this procedures is User Plane establishment between UE and LMF described in in clause 6.18. Figure 6.11.4-1: Positioning Procedure over User Plane 1. [Optional] The UE or LMF use the Secure UP transfer one or multiple LPP message(s). If LMF starts the procedure the LMF may request location information and/or measurements from the UE, and/or provide assistance data to/from the UE and/or query for the capabilities; if UE starts procedure, UE may request assistance data from LMF and/or providing location data and/or capability information to LMF. 2. [Optional] The UE or LMF processes capabilities information, assistance data, and/or location measurements/calculations. 3. [Optional] The UE or LMF may send one or multiple LPP message(s) using the Secure UP transfer. NOTE: Step 1, step 2 and step 3 can occur in any order, sequentially or concurrently.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.12 UE Location Privacy Setting Procedure
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.12.1 UE Location Privacy Setting Procedure Initiated by UE	Figure 6.12.1-1: UE Location Privacy Setting procedure initiated by UE 0. NF (e.g. GMLC, NEF) may subscribe to UDM notifications of UE LCS privacy profile updates. NOTE: NF can decide to subscribe to such notifications while a deferred location request is on-going. 1. If the UE has generated or updated the UE Location Privacy Indication, the UE sends the Location Privacy Indication to the AMF via UE Location Privacy Setting Request in N1 NAS message. The UE Location Privacy Indication indicates whether allows or disallows the subsequent LCS requests for the UE, as defined in clause 5.4. If the UE has generated or updated the event report expected area and optionally the area usage indication, e.g. based on UE power status, the UE Location Privacy Setting Request includes the event report expected area and the area usage indication. 2. The AMF invokes a Nudm_ParameterProvision_Update (LCS privacy) service operation towards the UDM and the service operation carries the Location Privacy Indication information and may include event report expected area and the area usage indication. The UDM stores or updates the UE LCS privacy profile in the UDR by invoking a Nudr_DM_Update (SUPI, Subscription Data) service operation accordingly. 3. The AMF responses to the UE via UE Location Privacy Setting Response in N1 NAS message. 4. UDM notifies the subscribed Network Function (e.g. GMLC, NEF) of the updated UE LCS privacy profile via Nudm_SDM_Notification Notify message. 5. NF (e.g. GMLC, NEF) may unsubscribe to UDM notifications of UE LCS privacy profile updates e.g. if a deferred location procedure is cancelled.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.12.2 UE Location Privacy Setting Procedure Initiated by AF	The procedure is defined by using the procedure in clause 4.15.6.2 of TS 23.502 [19] to set the Location Privacy Indication parameters and should in addition unsubscribe to UDM notifications of UE LCS privacy profile updates e.g. if a deferred location procedure is cancelled.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.13 Procedures with interaction between 5GC and EPC
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.13.1 MT-LR Procedure	Figure 6.13.1-1 illustrates network positioning requested by the LCS clients or the AF external to the PLMN for the case where the LCS Client or AF is associated with a GMLC in 5GC domain and the UE is served by the EPC domain. Both non-roaming and roaming scenarios are described. For non-roaming scenario both the case of separate EPC GMLC and 5GC GMLC connected with Lr reference point and the case with combined 5GC GMLC and EPC GMLC are described. For roaming scenario, the 5GC GMLC in the HPLMN uses NL3 to interconnect with the combined 5GC+EPCGMLC in the VPLMN. Figure 6.13.1-1: MT-LR procedure with 5GC and EPC interaction 1. Steps 1-3 in clause 6.1.2 are performed. 2. For non-roaming case and if 5GC GMLC and EPC GMLC are combined, steps 2a and 2b are skipped. Otherwise the 5GC GMLC may derive an address of a EPC GMLC or 5GC+EPC GMLC, either received together with the network address of the current serving node) from the UDM/HSS in step 1, by internal configuration or by query to NRF. 2a. If an address of a EPC GMLC is derived, the 5GC GMLC then sends the Lr location request to the EPC GMLC. If the result of privacy check indicates that the notification (and verification) based on current location is needed, the 5GC GMLC shall send a location request to the VGMLC indicating "positioning allowed without notification". 2b. If an address of an 5GC+EPC GMLC is derived, the 5GC GMLC invokes a Ngmlc_Location_ProvideLocation service operation towards the 5GC+EPC GMLC. If the result of privacy check indicates that the notification (and verification) based on current location is needed, the 5GC GMLC invokes the service request indicating "positioning allowed without notification" 3 Steps 2-9 or 9b in clause 9.1.15 of TS 23.271 [4] are performed. 4. For non-roaming case and if 5GC GMLC and EPC GMLC are combined, step 4a and 4b are skipped. Otherwise the following applies: 4a. If step 2a was performed, the EPC GMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method to the 5GC GMLC. 4b. If step 2b was performed, the 5GC+EPC GMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method to the 5GC+EPC GMLC in a Ngmlc_Location_ProvideLocation service Response. 5. If the privacy check in step 1 indicates that further privacy checks are needed, the 5GC GMLC shall perform an additional privacy check in order to decide whether the 5GC GMLC can forward the location information to the LCS client or AF or send a notification if the result of the privacy check requires the notification and verification based on current location. One example when this additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations. When an additional privacy check is not needed, the (H)GMLC skips steps 6-8. 6. For non-roaming case and if5GC GMLC and EPC GMLC are combined, step 6a and 6b are skipped. Otherwise the following applies: 6a. If step 2a was performed and if the result of privacy checks in step 5 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the 5GC GMLC shall send a location request to the EPC GMLC indicating "notification only". 6b. If step 2b was performed and if the result of privacy checks in step 5 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the 5GC GMLC shall invokes a Ngmlc_Location_ProvideLocation service operation to the 5GC+EPC GMLC indicating "notification only". 7. The EPC post positioning notification and verification procedure in clause 9.1.18 of TS 23.271 [4] is performed. 8. For non-roaming case and if 5GC GMLC and EPC GMLC are combined, step 8a and 8b are skipped. Otherwise the following applies: 8a. If step 2a was performed, the EPC GMLC forwards an indication of the result of notification and verification procedure to the 5GC GMLC. 8b. If step 2b was performed, the 5GC+EPC GMLC forwards an indication of the result of notification and verification procedure to the 5GC GMLC. 9. Steps 24 in clause 6.1.2 are performed.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.13.2 MO-LR Transfer to a Third Party Procedure	Figure 6.13.2-1 illustrates the UE requesting its location to be sent to a Third Party (i.e. an external LCS Client) for the case where the LCS Client is associated with a GMLC in 5GC domain and the UE is served by the EPC domain. Both non-roaming and roaming scenarios are described. For non-roaming scenario both the case of separate 5GC GMLC and EPC GMLC connected with Lr reference point and the case with co-located 5GC GMLC and EPC GMLC are described. For roaming scenario, when the combined 5GC GMLC and EPC GMLC are deployed in the HPLMN, it uses NL3 to interconnect with the EPCGMLC in the VPLMN. Figure 6.13.2-1: MO-LR procedure with 5GC and EPC interaction 1Steps 1-6 in clause 9.2.6 of TS 23.271 [4] are performed. 2. For non-roaming case and if 5GC GMLC and EPC GMLC is combined, this step is skipped. Otherwise the EPC GMLC sends Location Update Notification Request towards to the 5GC GMLC including the information received in step 1. 3 Steps 9-10 in clause 6.2 are performed. 4. For non-roaming case and if 5GC GMLC and EPC GMLC are combined, this step is skipped. Otherwise if the identified LCS Client is not accessible, the EPC GMLC sends a Location Update Notification response to AMF with an appropriate error cause. Otherwise, the response shall include an acknowledgement. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step. 5 Steps 13-14 in clause 9.2.6 of TS 23.271 [4] are performed.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.14 Procedures for Broadcast of Assistance Data
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.14.1 Broadcast of Assistance Data by an LMF	The following procedure is used by the LMF to support broadcasting of network assistance data to target UEs. This procedure is not associated with a UE location session. It is used in an AMF to send network assistance data to an NG-RAN node for broadcasting by the NG-RAN node to target UEs. NG-RAN positioning procedures related to LMF and NG-RAN node communication are specified in TS 38.455 [15]. Figure 6.14.1-1: Broadcasting Network Assistance Data 0a. [Optional] Based on operator policy, LMF may subscribe from AMF the event of 'Number of UEs presence in a geographical area' with an event filter including LCS broadcasting assistance data type (e.g. GNSS assistance data) to broadcast, the event filter enables the AMF to only report number of UEs which are subscribed to receive ciphering keys to decipher corresponding LCS assistance data. This can be checked based on the subscription data listed in Table 7.1-3. The geographical area is presented as TAI list(s). The LMF may also indicates 'Event reporting mode' as 'reporting when threshold is reached' and provides 'Reporting Threshold' to AMF. 0b. [Optional] After receiving the subscription in step 0a, AMF notifies LMF the number of UEs presence in a geographical area subscribing corresponding LCS assistance data type, if LMF provided 'Reporting Threshold' in step 0a, AMF should check whether the number of UEs subscribing the LCS assistance data type(s) to be broadcasted in the geographical area reached the reporting threshold (including matching, less or greater than the threshold value). Based on the notification from AMF which includes the number of UEs, LMF decides whether to initiate step 1 to step 5 and whether to initiate step 1-2 of clause 6.14.2 to provide ciphering keys applicable to these areas to AMF. The LMF can be configured with a threshold value based on operator policy, only when the number of UEs reached to the threshold, LMF initiates the broadcasting procedure. UEs can optionally request assistance data using 5GC-MO-LR based on clause 6.2. LMF may count the number of UEs in a geographical area which requires assistance data based upon 5GC-MO-LR request. LMF may additionally decide to enable broadcast including which assistance data to be transmitted via broadcast based on the count. 1. The LMF invokes the Namf_Communication_NonUeN2MessageTransfer service operation towards the AMF to request the transfer of a Network Assistance Data message to an NG-RAN node (gNB or ng-eNB) in the NG-RAN. The service operation includes the Network Assistance Data message and the target NG-RAN node identity. The Network Assistance Data message includes assistance data which may be optionally ciphered. LMF may send one or multiple sets of GNSS assistance data to the target NG-RAN node. LMF receives the GNSS assistance data by means of describing in clause 6.15, or other means not specified in the present document. 2. The AMF forwards the Network Assistance Data message to the target NG-RAN node indicated in step 1 in an N2 Transport message. The AMF includes a Routing identifier, in the N2 Transport message, identifying the LMF. 3. The NG-RAN node broadcasts the assistance data contained in the Network Assistance Data message. 4. The target NG-RAN node may return feedback on assistance information broadcasting to the AMF in a Network Assistance Feedback message. The target NG-RAN node shall also include the Routing identifier in the N2 Transport message received in step 2. 5. The AMF invokes the Namf_Communication_NonUeN2InfoNotify service operation towards the LMF indicated by the routing identifier received in step 4. The service operation includes the Network Assistance Data Feedback message received in step 4.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.14.2 Delivery of Ciphering Keys to UEs for Broadcast Assistance Data	The following procedure is used by the LMF and the AMF to distribute ciphering keys to UEs to enable UEs to decipher broadcast assistance data that was ciphered by the LMF. This procedure is not associated with a UE location session. The procedure makes use of the Registration procedure defined in TS 23.502 [19]. Figure 6.14.2-1: Delivery of Ciphering Keys to UEs for Broadcast Assistance Data 1. The LMF invokes the Nlmf_Broadcast_CipheringKeyData Notify service operation towards the AMF carrying one or more ciphering keys used to cipher network assistance data that is broadcast to UEs according to the procedure in clause 6.14.1. For each ciphering key, the LMF includes a ciphering key value, a ciphering key identifier, a validity period, a set of applicable tracking areas and a set of applicable types of broadcast assistance data. NOTE 1: The LMF may send a new ciphering key to the AMF at a time T1 if this will start to be used to cipher network assistance data at a later time T2 (e.g. will replace a previous ciphering key which expires at time T2). The value of (T2 - T1) should exceed the longest periodic registration timer of any UE subscribed to receive ciphering keys to ensure that periodic registration can be used to request new ciphering keys as described in note 2. 2. The AMF stores the ciphering keys including the validity periods, applicable tracking areas and the types of applicable broadcast assistance data. 3. A UE sends a Registration Request to a RAN node. The Registration Request may be sent as part of normal mobility management, A Registration Request may also be sent specifically to request and obtain ciphering keys. The UE includes in the Registration Request an indication that ciphering keys are requested. Other details of the Registration Request are as defined in TS 23.502 [19]. NOTE 2: A UE should request new ciphering keys using a Registration Request caused by periodic registration if the remaining validity period for one or more ciphering keys received earlier by the UE is less than the periodic registration timer value. This can help avoid all UEs initiating a Registration procedure at the same time to obtain new ciphering keys when a validity period for a ciphering key is about to expire. A UE should also request new ciphering keys for a Registration Request caused by entering a new tracking area if previous ciphering keys are not applicable to the new tracking area. 4. The RAN node selects the AMF if the UE is in CM IDLE state or determines the AMF for CM CONNECTED state. 5. The RAN node forwards the Registration Request to the AMF. 6. The AMF returns a Registration Accept to the RAN node as defined in TS 23.502 [19]. If the UE is subscribed to receive ciphered broadcast data, the AMF includes in the Registration Accept one or more ciphering keys applicable to the current tracking area for the UE. The AMF also includes for each ciphering key the ciphering key value, the ciphering key identifier, the validity period, the set of applicable tracking areas and the set of applicable types of broadcast assistance data. NOTE 3: The AMF does not need to keep a record of ciphering keys delivered to a UE and may instead send all ciphering keys stored at step 2 that are applicable to the current tracking area, for which the UE has a subscription and whose validity period has not yet expired. 7. The RAN node forwards the Registration Accept to the UE. The UE may start to use each ciphering key to decipher network assistance data that is broadcast according to the procedure in clause 6.14.1 once the validity period for the ciphering key has started and if the UE is currently in an applicable tracking area. The UE shall cease using a ciphering key when entering a tracking area not applicable to the ciphering key. The UE shall cease using and shall delete a ciphering key when the validity period for the ciphering key has expired. NOTE 4: A UE that receives no ciphering keys in response to a request for ciphering keys may assume that the UE does not have a subscription to receive ciphering keys in the serving PLMN. 8. The AMF deletes all information for a ciphering key when the validity period has expired.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.15 Procedures for GNSS assistance data Collection
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.15.1 GNSS assistance data collection from untrusted AF via NEF	The following procedure is used by LMF to collect GNSS assistance information from AFs via the NEF. Figure 6.15.1-1: GNSS assistance data collection from untrusted AF 1a-1c. Reuse the steps 1a-1c in figure 6.2.2.3-1 of TS 23.288 [37] with following difference: - The AF should also provide its serving area to NEF. NEF should map the serving area into TA(s) if it is presented as geographical location and update the NEF profile in NRF including the serving area information. 1d-1e. Reuse the steps 1d-1e in figure 6.2.2.3-1 of TS 23.288 [37] with following difference: - When LMF needs to discovery the available data from AFs and the appropriated NEF to collect GNSS assistance data, LMF additionally provides TAs in the Nnrf_NFDiscovery_Request_request service operation. 2-5. Reuse the steps 2-5 in figure 6.2.2.3-1 of TS 23.288 [37] with following difference: - Besides available GNSS assistance data, AF also provides associated serving area of the GNSS assistance data and optional precise global coordinates of the source of the GNSS assistance data. NEF may map the serving area into a TA or TA list. - When subscribing for the event GNSS Assistance Data with the AF, the LMF may also indicate an event filter which contains a location area (i.e. TA or TA list) to AF via NEF. The NEF may map the location area into a geographical location. 6. After LMF gets the GNSS assistance data, it can send the assistance data to UE via the procedures described in clauses 6.14 or 6.11.1 during a positioning session.
f07a33accd7fdb2aa929bcb3619e29df	23.273	6.15.2 GNSS assistance data collection from trusted AF	For trusted AFs, LMF collects GNSS assistance data through AFs directly. LMF discovers trusted AFs covering LMF serving area through NRF and subscribes to GNSS assistance data exposure from discovered trusted AFs. Figure 6.15.2-1: GNSS assistance data collection from trusted AF 1a-1c. AF invokes Nnrf_NFManagement_NFUpdate_request service operation to register its GNSS related information including Event IDs, and associated AF identification, Application ID(s) and its serving area (TAs). NRF stores the received AF update information and sends Nnrf_NFManagement_NFUpdate_response message to AF. 1d-1e. When LMF needs to discovery the available GNSS assistance data from AFs, LMF provide TAs to NRF through Nnrf_NFDiscovery service to discover related AFs. 2. LMF subscribes to or cancels subscription to GNSS assistance data in AF by invoking the Naf_EventExposure_Subscribe/Naf_EventExposure_Unsubscribe service operation. The LMF may also indicate an event filter which contains a location area (i.e. TA or TA list) to AF. 3. AF notifies the LMF with the available GNSS assistance data by invoking Naf_EventExposure_Notify service operation. AF also provides associated serving area (TAs) of the GNSS assistance data and optional precise global coordinates of the source of the GNSS assistance data. The AF notifies the LMF with the data by invoking Nnef_EventExposure_Notify service operation. 4. After LMF gets the GNSS assistance data, it can send the data to UE via the procedures described in clauses 6.14 or 6.11.1 during a positioning session.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.