hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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 f... |
691e61617b7dc9da01beed39caa1e157 | 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 pr... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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: ... |
691e61617b7dc9da01beed39caa1e157 | 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 de... |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.7 Support of Concurrent Location Requests
| |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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 pri... |
691e61617b7dc9da01beed39caa1e157 | 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 requir... |
691e61617b7dc9da01beed39caa1e157 | 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 require... |
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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.
... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.9 Location Service involving Mobile Base Station Relay
| |
691e61617b7dc9da01beed39caa1e157 | 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 o... |
691e61617b7dc9da01beed39caa1e157 | 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 tri... |
691e61617b7dc9da01beed39caa1e157 | 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 requ... |
691e61617b7dc9da01beed39caa1e157 | 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 indic... |
691e61617b7dc9da01beed39caa1e157 | 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 a... |
691e61617b7dc9da01beed39caa1e157 | 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/... |
691e61617b7dc9da01beed39caa1e157 | 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 A... |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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 subscrib... |
691e61617b7dc9da01beed39caa1e157 | 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 o... |
691e61617b7dc9da01beed39caa1e157 | 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 pos... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.18 Support for UE positioning based on a ML Model at the LMF
| |
691e61617b7dc9da01beed39caa1e157 | 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 pos... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.18.1 Void
| |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.19 Location Service involving Mobile Wireless Access Backhaul
| |
691e61617b7dc9da01beed39caa1e157 | 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 per... |
691e61617b7dc9da01beed39caa1e157 | 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 Broad... |
691e61617b7dc9da01beed39caa1e157 | 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 a MWAB ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6 Location Service Procedures
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.1 5GC-MT-LR Procedure
| |
691e61617b7dc9da01beed39caa1e157 | 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 cu... |
691e61617b7dc9da01beed39caa1e157 | 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 t... |
691e61617b7dc9da01beed39caa1e157 | 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 locati... |
691e61617b7dc9da01beed39caa1e157 | 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.... |
691e61617b7dc9da01beed39caa1e157 | 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 furt... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.3 Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events
| |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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.... |
691e61617b7dc9da01beed39caa1e157 | 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.3, 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).
Fi... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.3.5 Deferred 5GC-MT-LR Procedure for Periodic Location Events based on NRPPa Periodic Measurement
| |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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 proce... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.4 LMF Change Procedure
| |
691e61617b7dc9da01beed39caa1e157 | 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 servin... |
691e61617b7dc9da01beed39caa1e157 | 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 Event... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.5 Unified Location Service Exposure Procedure
| |
691e61617b7dc9da01beed39caa1e157 | 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 Servic... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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, cancellat... |
691e61617b7dc9da01beed39caa1e157 | 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 Proce... |
691e61617b7dc9da01beed39caa1e157 | 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 repea... |
691e61617b7dc9da01beed39caa1e157 | 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 ... |
691e61617b7dc9da01beed39caa1e157 | 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-... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.9 Procedures to Support Non-3GPP Access
| |
691e61617b7dc9da01beed39caa1e157 | 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 cla... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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 Proced... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.10 Procedures dedicated to Support Regulatory services
| |
691e61617b7dc9da01beed39caa1e157 | 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. d... |
691e61617b7dc9da01beed39caa1e157 | 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 co... |
691e61617b7dc9da01beed39caa1e157 | 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 sid... |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 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 locati... |
691e61617b7dc9da01beed39caa1e157 | 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 di... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.11 Common Sub-Procedures
| |
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 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
P... |
691e61617b7dc9da01beed39caa1e157 | 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 i... |
691e61617b7dc9da01beed39caa1e157 | 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 NRPP... |
691e61617b7dc9da01beed39caa1e157 | 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: Posit... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.12 UE Location Privacy Setting Procedure
| |
691e61617b7dc9da01beed39caa1e157 | 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 Loca... |
691e61617b7dc9da01beed39caa1e157 | 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.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.13 Procedures with interaction between 5GC and EPC
| |
691e61617b7dc9da01beed39caa1e157 | 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... |
691e61617b7dc9da01beed39caa1e157 | 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 c... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.14 Procedures for Broadcast of Assistance Data
| |
691e61617b7dc9da01beed39caa1e157 | 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 procedure... |
691e61617b7dc9da01beed39caa1e157 | 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].
Fi... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.15 Procedures for GNSS assistance data Collection
| |
691e61617b7dc9da01beed39caa1e157 | 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. ... |
691e61617b7dc9da01beed39caa1e157 | 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_N... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.16 Periodic and Triggered 5GC-MT-LR Procedure with User Plane
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.