hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.16.1 Reporting of Location Events to an LCS Client or AF via user plane
| Figure 6.16.1-1 shows a procedure for event reporting from a UE to an LCS Client or AF when a User Plane connection is established directly from the UE to the LCS Client or AF. This procedure is applicable when the target UE is able to determine its location.
Figure 6.16.3-1: Reporting of Location Events to an LCS C... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.16.2 Cancellation of Reporting of Location Events with a User Plane Connection
| A UE may cancel a deferred 5GC-MT-LR procedure for periodic, or triggered location events where a user plane connection is used by the following the procedure defined in clause 6.3.2. After the UE receives the acknowledgment of the cancellation at step 6 in clause 6.3.2, the UE shall release the user plane connection t... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.17 Procedures applicable to a PRU
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.17.1 PRU Association Procedure
| Figure 6.17.1-1 shows a procedure used by a PRU to associate as a PRU with a serving LMF. The procedure is used for initial PRU Association with the serving LMF which may occur when the PRU first starts to access the HPLMN. The procedure can also be used to perform a PRU Association update to inform the serving LMF of ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.17.2 LMF Initiated PRU Disassociation Procedure
| Figure 6.17.2-1 shows a procedure used by a serving LMF to disassociate an already associated PRU. The procedure may be used prior to the serving LMF becoming unavailable (e.g. for maintenance, removal or replacement) or to transfer the PRU to a different serving LMF for other reasons.
Figure 6.17.2-1: LMF Initiated... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.17.3 PRU Initiated PRU Disassociation Procedure
| Figure 6.17.3-1 shows a procedure used by a PRU to disassociate from a serving LMF. The procedure may be used prior to the PRU becoming unavailable (e.g. for a software upgrade or power down) or when the PRU will be transferred to a different serving LMF.
Figure 6.17.3-1: PRU Initiated PRU Disassociation Procedure
... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.17.4 Positioning of a target UE
| Figure 6.17.4-1 shows a procedure used by a serving LMF for a target UE to obtain a location of the target UE using location information provided by one or more PRUs.
Figure 6.17.4-1: Location of a target UE using PRUs
1. The serving LMF for the target UE and other PRU serving LMFs may use the procedures defined in... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.18 Procedures of User Plane Connection between UE and LMF
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.18.0 General
| Clause 6.18 describes the management of the user plane connection between UE and LMF. LMF or UE may trigger the establishment of the user plane connection.
UE and LMF may maintain the established user plane connection. LMF may modify or terminate the established user plane connection between UE and LMF. UE may have mu... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.18.1 LMF initiated User Plane Connection
| LMF may trigger the user plane connection establishment after receiving a location request from AMF if target UE does not have user plane connection with this LMF. AMF may subscribe from LMF the status of LCS user plane connection for the target UE, using a Nlmf_Location_UP Subscribe message if the UE supports user pla... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.18.2 UE initiated User Plane Connection
| UE may trigger the user plane connection establishment if the UE does not have user plane connection with a specific LMF. Figure 6.18.2-1 shows a procedure triggered by UE to support positioning over the user plane connection between UE and LMF.
Figure 6.18.2-1: Positioning via a User Plane Connection between UE and... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.18.3 Modification of User Plane Connection between UE and LMF
| The figure 6.18.3-1 shows how a secure user plane connection between UE and LMF is modified. The flow describes change of LMF but applies also when source and target LMF is the same. The procedure can also be used to terminate the user plane connection to Source LMF not selecting any Target LMF.
Figure 6.18.3-1: Con... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19 Location Service Continuity between EPS and 5GS
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.0 General
| Clause 6.19.1 describes the location service continuity procedure for Immediate Location Request. Clause 6.19.2 describes the location service continuity procedure for deferred MT-LR. The GMLC in clause 6.19.1 and clause 6.19.2 can be a single co-located EPC-GMLC and 5GC-GMLC or a separate EPC-GMLC and 5GC-GMLC with th... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.1 Location Service Continuity for Immediate Location Request
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.1.1 Location Service Continuity from 5GS to EPS with N26 Interface for Immediate Location Request
|
Figure 6.19.1.1-1: Location Service Continuity from 5GS to EPS with N26 Interface for Immediate Location Request
1. Target UE positioning is started in 5GS, e.g. steps 1-12 of 5GC-MT-LR procedure in clause 6.1.2, or steps 1-5 of 5GC-MO-LR procedure in clause 6.2.
2. LMF handles the ongoing LCS session
3. 5GS to EP... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.1.2 Location Service Continuity from EPS to 5GS with N26 Interface for Immediate Location Request
|
Figure 6.19.1.2-1: Location Service Continuity from EPS to 5GS with N26 Interface for Immediate Location Request
1. Target UE positioning is started in EPS, e.g. Steps 1-7 of EPC-MT-LR procedure in Figure 9.18 or steps 1-4 of EPC-MO-LR procedure in Figure 9.8d of TS 23.271 [4].
2. During the EPC-MT-LR or EPC-MO-LR,... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.1.3 Location Service Continuity from 5GS to EPS without N26 Interface for Immediate Location Request
|
Figure 6.19.1.3-1: Location Service Continuity from 5GS to EPS without N26 Interface for Immediate Location Request
1. Target UE positioning is started in 5GS, e.g. Steps 1-12 of 5GC-MT-LR procedure in clause 6.1.2, or steps 1-5 of 5GC-MO-LR procedure in clause 6.2.
2. [Conditional] If the 5GC-GMLC sends the messag... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.1.4 Location Service Continuity from EPS to 5GS without N26 Interface for Immediate Location Request
|
Figure 6.19.1.4-1: Location Service Continuity from EPS to 5GS without N26 Interface for Immediate Location Request
1. Target UE positioning is started in EPS, e.g. Steps 1-7 of EPC-MT-LR procedure in Figure 9.18, or steps 1-4 of EPC-MO-LR procedure in Figure 9.8d in TS 23.271 [4].
2a-2c. [Conditional] If the EPC-G... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.2 Location Service Continuity between EPS and 5GS (bi-direction) for deferred MT-LR
| This clause shows the procedure to support location service continuity between EPS and 5GS (bi-direction) for deferred MT-LR. Clause 6.19.2.1 shows the procedure for 5GS to EPS handover case and clause 6.19.2.2 shows the procedure for the EPS to 5GS handover case.
Cancellation of the reporting of location events is st... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.2.1 Location Service Continuity from 5GS to EPS
|
Figure 6.19.2.1-1: LCS Continuity Solution for 5GS to EPS Mobility
1. Same as step 1 of deferred 5GC-MT-LR procedure in clause 6.3.1, with the enhancement that 5GC-(H)GMLC obtains the LDR reference number and EPC-(H)GMLC address from EPC-(H)GMLC for the periodic or triggered location session. If the deferred LCS ser... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.19.2.2 Location Service Continuity from EPS to 5GS
|
Figure 6.19.2.2-1: LCS Continuity Solution for EPS to 5GS Mobility
1. Target UE positioning starts in 5GS with steps 1-3 of deferred 5GC-MT-LR for periodic, triggered and UE available location events procedure in clause 6.3.1.
2. The target UE is registered in EPC, 5GC-GMLC sends LCS Service Request to EPC-GMLC. Th... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20 Ranging/Sidelink Positioning procedures
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20.1 Procedures of SL-MO-LR involving LMF
| Figure 6.20.1-1 illustrates a procedure to enable a UE to obtain Ranging/Sidelink Positioning location results using one or more other UEs with the assistance of an LMF in a serving PLMN for UE1.
The Ranging/Sidelink Positioning location results may include absolute locations, relative locations, i.e. distances and/or... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20.2 5GC-MO-LR Procedure using Ranging/SL positioning
| This procedure is used to estimate the location of a UE based on the location of one or more Located UEs and the distance and/or direction between the UE and the Located UE(s). 5GC-MO-LR Procedure as defined in clause 6.2 applies with the following differences:
- In step 3, the AMF may take the UE's Ranging/Sidelink ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20.3 Procedures of SL-MT-LR involving LMF
| The SL-MT-LR procedure is used to estimate the relative locations or distances and/or directions between the UEs or absolute location of a Target UE.
Figure 6.20.3-1 illustrates a procedure to enable an LCS Client or AF to obtain Ranging/Sidelink Positioning location results for a group of n UEs (n≥2), i.e. UE1, UE2, ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20.4 Procedures of SL-MT-LR for periodic, triggered Location Events
| The periodic and triggered SL-MT-LR procedure is based on SL-MT-LR procedure in clause 6.20.3, and used to estimate the relative locations or distances and/or directions between the UEs periodically or following certain trigger events. LCS Client or AF to obtain Ranging/Sidelink Positioning location results for a group... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.20.5 5GC-MT-LR Procedure using Ranging/SL positioning
| The procedure is used to estimate the location of a UE by using the location of one or more Located UEs and the distance and/or direction between the UE and the Located UE(s).
NOTE: The procedure can be triggered by GMLC, e.g. if the location result of Target UE determined by previous MT-LR procedure for the same requ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.21 Procedure for NWDAF assistance to location services
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.21.1 General
| This clause specifies procedures for NF in the LCS system to interact with NWDAF for data analytics. General framework for NF in the LCS system to interact with NWDAF for data analytics refers to the clauses 6.1.1 and 6.1.2 of TS 23.288 [37].
Clause 6.21.2 describes the procedures of Location Accuracy Analytics retrie... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.21.1 Location Accuracy Analytics Retrieval by LMF
| LMF may request Location Accuracy Analytics from NWDAF to retrieve the location accuracy.
The procedure to request Location accuracy analytics by LMF is referred to clause 6.17.4 of TS 23.288 [37]. In Figure 6.17.4-1 of TS 23.288 [37] the Analytics consumer is replaced by LMF. Pre-condition of the procedure is NWDAF h... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.21.2 UE Mobility Analytics Retrieval by AMF
| AMF may request assistance for UE location verification for NR satellite access as described in clause 6.10.1 by requesting or subscribing to UE mobility analytics from NWDAF. With NWDAF-based UE location statistics and predictions and UE location estimated by LMF, AMF can further assist UE location verification for NR... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22 Procedures of data collection for LMF-based AI/ML Positioning
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22.1 General
| This clause describes the procedure for data collection by the LMF for input data to train or monitor the performance of the ML model for LMF-based AI/ML positioning.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22.2 Void
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22.3 Data collection to train models for LMF-based AI/ML positioning based on NG RAN measurements
| The procedure for data collection from NG-RAN is used to e.g. train the ML Model for LMF-based AI/ML positioning.
Figure 6.22.3-1: Data collection by LMF to train the AI/ML based positioning model using NG-RAN measurements
1. The LMF determines that data collection from the NG-RAN is required e.g. to train an ML Mo... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22.4 Input data collection by NWDAF for AI/ML positioning ML model training or ML model performance monitoring
| The NWDAF containing MTLF may subscribe to input data (i.e. location measurement data and ground truth UE location) from LMF for ML model training or ML model performance monitoring for LMF-based AI/ML Positioning.
Figure 6.22.4-1: Procedure of input data collection from LMF
1. NWDAF containing MTLF determines to t... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.22.5 LMF retrieval of a trained AI/ML Model for positioning
| The LMF may retrieve a trained ML Model from the NWDAF and perform UE positioning using the trained ML model.
Figure 6.22.5-1: Retrieval of trained ML model(s) for LMF-based AI/ML positioning from NWDAF
1. The LMF determines to request trained ML model(s) from the NWDAF for LMF-based AI/ML positioning, e.g. based o... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.23 Procedures of data collection for NG RAN-sided models for AI/ML positioning
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.23.1 General
| This clause describes the procedure for data collection by the NG-RAN for input data to train or monitor the performance of the ML model for NG-RAN node assisted positioning with gNB-sided model.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 6.23.2 Data Collection for NG RAN-sided models for UEs under positioning
| Figure 6.23.2-1 shows a procedure of data collection for UEs under positioning by the NG-RAN, in order to train or monitor the performance of the gNB-sided ML model for NG-RAN node assisted positioning.
Figure 6.23.2-1: Data Collection for NG RAN-sided models for UEs under positioning
Precondition: There is an ongo... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 7 Information storage
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 7.1 UDM
| For each UE subscriber the UDM stores LCS related data as part of the Subscriber Data Management (SDM) service as defined in clause 5.2.3.3.1 of TS 23.502 [19].
The privacy profile data is defined in table 7.1-1 containing data for the privacy classes for which location of the target UE is permitted. For the meaning o... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 7.2 GMLC
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 7.2.1 Information for an LCS Client
| The GMLC holds information for external LCS clients which are permitted to request location information for UE subscribers. Table 7.2.1-1 shows the information which may be stored in the GMLC for an external LCS Client.
Table 7.2.1-1: GMLC Information for an External LCS Client
LCS Client Information
Status
Descrip... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8 Network Function Services
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.1 AMF Services
| AMF services related to location service are defined in clause 5.2.2 of TS 23.502 [19].
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.2 UDM Services
| UDM services related to location service are defined in clause 5.2.3 of TS 23.502 [19].
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3 LMF Services
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.1 General
| The following table shows the LMF Services and LMF Service Operations.
Table 8.3.1-1: List of LMF Services
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nlmf_Location
DetermineLocation
Request/Response
AMF
EventNotify
Notify
GMLC
CancelLocation
Request/Response
AMF
Locat... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2 Nlmf_Location service
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.1 General
| Service description: This service enables an NF to request location determination for a target UE. The following are the key functionalities of this NF service.
- Allow the consumer NF to request the current geodetic and optionally local and/or civic location of a target UE.
- Allow the consumer NF to subscribe/unsub... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.2 Nlmf_Location_DetermineLocation service operation
| Service operation name: Nlmf_Location_DetermineLocation
Description: Provides UE location information to the consumer NF.
NOTE: For deferred location request, this service operation is used to implicitly subscribe to the notification of the UE location information.
Input, Required: Client Type, LCS Correlation Ident... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.3 Nlmf_Location_EventNotify service operation
| Service operation name: Nlmf_Location_EventNotify.
Service operation description: Allow the consumer NF to get notified about the geodetic and optionally local and/or civic location of a target UE when some certain events are detected, either the events implicitly subscribed by the AMF using Nlmf_Location_DetermineLoc... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.4 Nlmf_Location_CancelLocation service operation
| Service operation name: Nlmf_Location_CancelLocation
Description: The consumer NF cancels a deferred 5GC-MT-LR procedure for periodic or triggered location request, 5GC-MT-LR and 5GC-MO-LR procedure during UE mobility from 5GS to EPS with N26 interface.
Input, Required: Notification Target Address and Notification Co... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.5 Nlmf_Location_LocationContextTransfer service operation
| Service operation name: Nlmf_Location_LocationContextTransfer
Description: Transfers user plane connection existing indication and/or location context information for location event reporting for a target UE from the consumer NF.
Input, Required: AMF identity.
Inputs, Conditional Required: UE identifier (SUPI), user... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.6 Nlmf_Location_MeasurementData service operation
| Service operation name: Nlmf_Location_MeasurementData
Description: Provides PRU location measurements to the consumer NF.
Input, Required: Target UE cell ID.
Input, Optional: Pre-calculated location of target UE, time window(s), positioning method, the identifiers of TRPs if the network assisted positioning is used.... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.7 Nlmf_Location_UPConfig service operation
| Service operation name: Nlmf_Location_UPConfig
Description: The consumer NF requests to set up, modify or terminate a secure LCS-UP connection for a target UE.
Input, Required: Notification Target Address, Notification Correlation ID, UE identifier (SUPI).
Input, Optional: AMF reallocation indication, LCS-UP connect... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.8 Nlmf_Location_UPSubscribe service operation
| Service operation name: Nlmf_Location_UPSubscribe
Description: Allow the consumer NF to subscribe about status of a secure LCS-UP connection for a target UE.
Input, Required: Notification Target Address, Notification Correlation ID, UE identifier (SUPI).
Input, Optional: UE identifier (GPSI).
Outputs, Required: Sub... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.9 Nlmf_Location_UPNotify service operation
| Service operation name: Nlmf_Location_UPNotify
Description: Allow the consumer NF get notified about status or modification of a secure LCS-UP connection for a target UE.
Input, Required: Notification Correlation ID, LCS-UP connection status (established, released or move indication).
Input, Optional: Target LMF ide... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.2.10 Nlmf_Location_UPUnSubscribe service operation
| Service operation name: Nlmf_Location_UPUnSubscribe
Description: Allow the consumer NF to unsubscribe about status of a secure LCS-UP connection for a target UE.
Input, Required: Subscription Correlation ID.
Input, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.3 Nlmf_Broadcast service
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.3.1 General
| Service description: This service enables an NF to receive information related to broadcast of location assistance by an LMF. The following are the key functionalities of this NF service.
- Allow the consumer NF to be notified about ciphering keys used to cipher broadcast assistance data.
The events to trigger cipher... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.3.2 Nlmf_Broadcast_CipheringKeyData service operation
| Service operation name: Nlmf_Broadcast_CipheringKeyData
Description: Provides ciphering key data to the consumer NF.
Input, Required: For each ciphering key: ciphering key value, ciphering key identifier, validity period, set of applicable types of broadcast assistance data.
Input, Optional: For each ciphering key: ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.4 Nlmf_DataExposure service
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.4.1 General
| Service description: This service enables an NF service consumer to subscribe to input data for model training or model performance monitoring. See clause 6.22.4 for examples of usage of this service.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.4.2 Nlmf_DataExposure_Subscribe service operation
| Service operation name: Nlmf_DataExposure_Subscribe
Description: Allow the consumer NF to subscribe the input data used for ML model training or ML model performance monitoring for LMF-based AI/ML Positioning.
Input, Required: Notification Target Address, Notification Correlation ID, AoI.
Input, Optional: ML model i... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.4.3 Nlmf_DataExposure_Notify service operation
| Service operation name: Nlmf_DataExposure_Notify
Description: Allow the consumer NF to get notification about the input data used for ML model training or ML model performance monitoring for LMF-based AI/ML Positioning.
Input, Required: Notification Correlation ID.
Input, Optional: Data samples (i.e. location measur... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.3.4.4 Nlmf_DataExposure_UnSubscribe service operation
| Service operation name: Nlmf_DataExposure_UnSubscribe
Description: Allow the consumer NF to cancel subscription to input data used for ML model training or ML model performance monitoring for LMF-based AI/ML Positioning.
Input, Required: Subscription Correlation ID.
Input, Optional: None.
Output, Required: Operatio... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4 GMLC Services
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.1 General
| The following table shows the GMLC Services and GMLC Service Operations.
Table 8.4.1-1: List of GMLC Services
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Ngmlc_Location
ProvideLocation
Request / Response
GMLC, NEF, NWDAF, LMF
LocationUpdate
Request / Response
AMF, GMLC
Loca... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2 Ngmlc_Location service
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.1 General
| Service description: This service enables an NF to request location determination for a target UE or to request relative locations, distance, or direction between UEs. The following are the key functionalities of this NF service.
- Allow the consumer NF to request the current geodetic and optionally local and/or civic... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.2 Ngmlc_Location_ProvideLocation service operation
| Service operation name: Ngmlc_Location_ProvideLocation
Description: Provides UE location information to the consumer NF.
NOTE 1: For deferred location request, this service operation is used to implicitly subscribe to the notification of the UE location information.
NOTE 2: For bulk LCS service request from NEF to G... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.3 Ngmlc_Location_LocationUpdate service operation
| Service operation name: Ngmlc_Location_LocationUpdate
Description: Consumer NF provides UE location information to the GMLC.
Input, Required: UE identifier (GPSI or SUPI), event causing the location estimate (5GC-MO-LR), location estimate, age of location estimate, accuracy indication, LCS QoS class.
Input, Optional... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.4 Ngmlc_Location_EventNotify service operation
| Service operation name: Ngmlc_Location_EventNotify
Description: Allow the consumer NF to get notified about the geodetic and optionally local and/or civic location of one or more target UEs when some certain events, either the events implicitly subscribed by the AMF using Ngmlc_Location_ProvideLocation service operati... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.5 Ngmlc_Location_CancelLocation service operation
| Service operation name: Ngmlc_Location_CancelLocation
Description: The consumer NF uses this service operation to cancel a deferred 5GC-MT-LR procedure for periodic or triggered location.
Input, Required: UE Identification (SUPI), Notification Target address, Notification Correlation ID.
Input, Optional: None.
Outp... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.6 Ngmlc_Location_LocationUpdateNotify service operation
| Service operation name: Ngmlc_Location_LocationUpdateNotify
Description: Provides UE location information to the consumer NF.
Input, Required: UE identifier (GPSI or SUPI), identity of the AF, event causing the location estimate (5GC-MO-LR), location estimate, age of location estimate, accuracy indication, LCS QoS cl... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.7 Ngmlc_Location_PrivacyCheck_IDMapping service operation
| Service operation name: Ngmlc_Location_PrivacyCheck_IDMapping
Description: Consumer NF requests privacy check and ID mapping for certain UEs involved in Ranging.
Input, Required: UEs identifier (GPSI, Application Layer ID).
Input, Optional: None.
Output, Required: Success/Failure indication, UEs identifier (Applica... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.4.2.8 Void
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.5 NEF Services
| For 5GC-MT-LR procedures, location reporting is one of the monitoring events, as defined in clause 4.15.3.1 of TS 23.502 [19], supported by Nnef_EventExposure service.
Nnef_EventExposure service operations are defined in clause 5.2.6.2 of TS 23.502 [19].
The attributes that may be included in the location service req... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 8.6 UDR Services
| UDR services related to location service are defined in clause 5.2.3 of TS 23.502 [19].
Annex A (informative):
Differences with TS 23.271 [4]
A.0 General
Differences with TS 23.271 [4] are described here where these may impact service to a target UE, LCS client, or client AF or NF. The differences are restricted to... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 1 Scope
| This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture.
The corresponding service requirements are defined in 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 3 Definitions, symbols and abbreviations
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. Not all definitions are used in this document.
Accuracy: Reflects the unc... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 3.2 Symbols
| For the purposes of the present document, the symbols given in 3GPP TS 22.280 [3] apply
Nc6
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
APN Access Point Name
BM-SC Broadcast Multicast Service Centre
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 4 Introduction
| A common functional architecture to support MC services (i.e., MCPTT defined in 3GPP TS 23.379 [16], MCVideo defined in 3GPP TS 23.281 [12], MCData defined in 3GPP TS 23.282 [13]) including common application plane and signalling plane entities is specified in this document. It also deals with the functional architectu... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5 Assumptions and architectural requirements
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.1 Assumptions
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.1.1 Service continuity
| Service continuity shall be supported between on-network MC services and UE-to-network relay MC services. The following 3GPP TS 23.237 [9] procedures are needed:
- Originating sessions that use only PS media flow(s) as defined in subclause 6.2.1.3.
- Terminations sessions that use only PS media flow(s) as defined in... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.1.2 Trust domain
| For an MC system, the trust domain consists of one or more MC service functions that are administered by the same or different service providers (e.g. MC service provider, PLMN operator) that have an agreement to share sensitive information.
For the MC system architecture, the following rules are implied for functions... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2 Architectural requirements
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.1 General architectural requirements
| General MC service architectural requirements include:
a) To develop economies of scale, it will be useful if PLMN operators can reuse the MC service architecture for non-public safety customers that require similar functionality. These PLMN operators may want to integrate many components of the MC service solution wi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.2 PLMN change requirements
| The MC applications can provide MC services to users in various PLMNs. An MC service UE may connect to PLMNs using EPC-level roaming, IMS-level roaming or local subscription.
For EPC-level roaming, in order to prioritize for network selection PLMNs that allow migration to partner MC systems, the MC service UE's User P... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.3 UE-to-network relay MC service requirements
| To support the requirement that a public safety ProSe UE-to-network relay shall be able to restrict the relayed group communication on a per group basis, the MC service should be able to provide a means for an MC service administrator to configure a ProSe UE-to-network relay with a list of allowed MC service groups. Fo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.4 MC service user profile requirements
| The MC service user profile shall:
- be provisioned subject to the user authentication by the identity management server;
- be available at configuration management server;
- be available at MC service servers with the corresponding user profile information;
- be associated with an MC service user; and
- contain ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.5 MC service group affiliation and MC service group de-affiliation
| The MC system shall support affiliation and de-affiliation to an MC service group for one or more MC services. For affiliation and de-affiliation, the MC service client shall indicate interest in one or more MC services for the MC service group. For a single MC service group configured for multiple MC services, the aff... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 5.2.6 GCS AS requirements for the MC services
| Point to multipoint broadcast offered by the LTE MBMS technology is well suited to group communications, which form a major part of the public safety related communications. The MC service on-network architecture, is based in part on 3GPP TS 23.468 [18] with the MC service server assuming the function of the GCS AS and... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.