hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.16 Periodic and Triggered 5GC-MT-LR Procedure with User Plane
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 Client or AF via user plane
1. Steps 1-21 in clause 6.3.1 for the deferred 5GC-MT-LR procedure for periodic or triggered location are performed with the following differences.
- At step 1, the LCS Client or AF includes a request for user plane reporting in the LCS Service Request and may include a user plane address of the LCS Client or AF and security information to enable a secure connection. The H-GMLC verifies that both the target UE and the LCS Client or AF are subscribed to user plane reporting. If the LCS Client or AF did not include a user plane address or security information, the H-GMLC obtains a default user plane address and/or default security information from subscription data for the LCS Client or AF. The H-GMLC determines criteria for sending cumulative events reports over control plane. The criteria can include a cumulative event report timer and/or a maximum number of user plane event reports.
- At steps 4, 5 and 14, the request for user plane reporting, the user plane address, the security information and the criteria for sending cumulative events reports over control plane are forwarded in sequence to the V-GMLC (if used), serving AMF and LMF.
- At step 14 or step 15, the LMF gets the UE capabilities and verifies that the UE is able to support position methods that allow the UE to determine its own location.
- At step 16, the LMF includes the request for user plane reporting, the user plane address, the security information and the criteria for sending cumulative events reports in the supplementary services LCS Periodic-Triggered Invoke Request sent to the target UE.
- At step 17, the target UE indicates to the LMF whether event reporting via user plane can be supported by the target UE. If event reporting via user plane cannot be supported by the target UE, a failure response is returned to the LCS Client or AF at steps 18-21.
2. The UE establishes a secure user plane connection with TLS to the LCS Client or AF using the user plane address and the security information received at step 1.
3. The UE monitors for and detects the occurrence of a trigger or periodic event as described for step 22 of the procedure in clause 6.3.1.
4a. The UE obtains location measurements and determines a current location.
4b. If the UE is unable to determine its location at step 4a, the UE sends an event report to the LCS Client or AF over control plane as described for steps 24-30 in clause 6.3.1.
5. The UE sends an Event Report to the LCS Client or AF over the secure user plane connection established at step 2. The event report indicates the type of event being reported and includes the location determined at step 4a.
6. The LCS Client or AF may return an Event Report Acknowledgment to the UE over the secure user plane with TLS connection established at step 2.
7. The UE continues to monitor for and detect further trigger or periodic events as at step 3 and repeats steps 4-6 for each detected trigger or periodic event.
8. The UE monitors the criteria received at step 1 for sending of cumulative event reports. If a cumulative event report timer was received at step 1, the UE starts the timer following step 1 and after each cumulative event report is sent. If a maximum number of user plane event reports was received at step 1, the UE maintains a count of the number of user plane event reports sent at step 5. When the cumulative event report timer expires or when the count of user plane events reports sent at step 5 reaches the maximum number of user plane event reports, the UE sends a cumulative event report and restarts the timer and the count of user plane event reports. The UE sends the cumulative event report to the LMF, H-GMLC and LCS Client or AF over the control plane portion of the periodic or triggered deferred 5GC-MT-LR using steps 25-30 of the procedure in clause 6.3.1. The cumulative event report indicates to the LMF, H-GMLC and External LCS Client or AF that the control plane portion of the periodic or triggered deferred 5GC-MT-LR is still active, that the UE is reporting events via user plane and may include statistics on the events reported since the last cumulative event report was sent (e.g. the number of event reports).
A target UE may also send a cumulative event report at step 8 to obtain assistance data from the LMF to assist with location at step 4a. In this case, the target UE includes a positioning LPP request for assistance data in the cumulative event report sent to the LMF at step 25 in clause 6.3.1 and the LMF uses step 27 in clause 6.3.1. to return the requested assistance data to the target UE. In this case, the cumulative event report timer and the count of user plane event reports are restarted and a cumulative event report is sent on to the H-GMLC and LCS Client or AF by the LMF (but without the embedded positioning LPP request for assistance data).
During step 8, the LMF change procedure in clause 6.4 may be used to forward the cumulative event report (and any request for assistance data) to another LMF if the current LMF can no longer support the periodic or triggered MT-LR due to a change in target UE location (e.g. a change to the target UE TAI). In this case, the new LMF can return any assistance data to the UE (if this was requested) and can forward the cumulative event report to the H-GMLC and LCS Client or AF.
NOTE: When using step 8 to request assistance data, the UE may perform step 8 well before performing step 4a for a user plane event report in order to avoid extra delay in sending the user plane event report.
9. After the UE has sent the final event report and received an acknowledgment using steps 5 and 6 or step 4b, the UE shall release the user plane connection to the LCS Client or AF if the LCS Client or AF has not yet initiated release of the user plane connection
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 to the LCS Client or AF if the LCS Client or AF has not yet initiated release of the user plane connection.
An AF or External LCS Client or a GMLC may cancel a deferred 5GC-MT-LR procedure for periodic or triggered location where a user plane connection is used by the following the procedure defined in clause 6.3.3. After the UE has returned the acknowledgment of the cancellation at step 9 in clause 6.3.3, the UE shall release the user plane connection to the LCS Client or AF if the LCS Client or AF has not yet initiated release of the user plane connection.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.17 Procedures applicable to a PRU
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 the continued availability of the PRU or to inform the serving LMF of some change to the PRU such as a change of location (e.g. a change of tracking area or change of serving AMF) or a change of the PRU positioning capabilities. The PRU shall only perform the Association procedure in the HPLMN.
Figure 6.17.1-1: PRU Association Procedure
Precondition: The PRU is currently registered in the HPLMN. For initial PRU Association, a Routing Identifier may have been configured in the PRU indicating the serving LMF. For subsequent PRU Association, a Routing ID indicating a serving LMF has been returned to the PRU at step 6a or 6b of a previous PRU Association procedure.
NOTE 1: A Correlation ID and a Routing ID are different terms for the same identifier. The term "Correlation ID" is used for an identifier in service operations between an AMF and LMF while the term "Routing ID" is used for an identifier in a NAS message sent over the N1 reference point between a PRU and AMF.
1. The PRU performs a UE Triggered Service Request if in CM IDLE state.
2. The PRU sends a supplementary services PRU Association Request to the serving AMF in an UL NAS TRANSPORT message and includes any preconfigured Routing ID for an initial Association or the Routing ID if received at step 6a or step 6b for a previous PRU Association procedure. The PRU Association Request is included in the UL NAS TRANSPORT message at the NAS level. The PRU Association Request includes a reason for the PRU Association (e.g. initial PRU Association, or PRU Association update), the PRU's positioning capabilities, location information (if known) or PRU ON/OFF state.
3. The AMF verifies whether the sender of the PRU Association Request is a PRU using subscription information from the UDM. AMF verifies based on subscription information or local policy if PRU can work as stationary PRU.
4. The AMF selects the serving LMF based on the criteria defined in clause 5.1 or one of the Routing ID if included in the UL NAS TRANSPORT message of step 2. The AMF may override the Routing ID based on criteria of clause 5.1. The AMF transfers the PRU Association Request to the serving LMF using an Namf_Communication_N1MessageNotify service operation. The AMF includes in the Namf_Communication_N1MessageNotify service operation an indication of whether the request corresponds to a PRU subscription and indication if PRU is stationary. The AMF also includes the SUPI, TAI and cell ID of the PRU.
5a. If the AMF indicates in step 4 that the request corresponds to a PRU and if the LMF can accept the PRU Association, the serving LMF returns a PRU Association Accept, as a supplementary services message, using Namf_Communication_N1N2MessageTransfer service operation towards the AMF, and a Correlation ID. The Correlation ID is assigned by the serving LMF to identify the serving LMF and optionally the PRU. The PRU Association Accept indicates conditions for performing PRU Association updates with the serving LMF which may include a periodic PRU Association update timer and PRU Association update based on a change of PRU location, change of PRU TAI, change of serving AMF, or change of PRU ON/OFF state. For a PRU whose state is OFF, PRU information is kept at the serving LMF.
NOTE 2: A periodic PRU Association is independent of a periodic NAS Registration and may occur with greater, equal or lesser frequency.
6a. The serving AMF forwards the PRU Association Accept and a Routing ID equal to the Correlation ID to the PRU in a DL NAS TRANSPORT message. The PRU stores the Routing ID which is used for any further PRU Association update with the serving LMF. This Routing ID overrides any Routing ID used in previous Association updates, if any.
5b. If the AMF indicates in step 4 that the request does not correspond to a PRU subscription or if the serving LMF cannot accept the PRU Association for some other reason (e.g. the serving LMF is not the correct serving LMF for the PRU), the serving LMF returns a PRU Association Reject message, using Namf_Communication_N1N2MessageTransfer service operation towards the AMF, and may include the Routing ID of a new serving LMF if the request at step 4 corresponds to a PRU.
6b. The serving AMF forwards the PRU Association Reject in a DL NAS TRANSPORT message to the PRU.
7. If PRU Association is performed successfully as in steps 5a and 6a, the serving LMF may optionally verify any PRU location provided at step 4 or obtain a more accurate location of the PRU using the procedures defined in clause 6.11. The LMF also stores information received for the PRU. If PRU Association update including only a state change is performed, the serving LMF may consider the previously verified PRU location is valid.
8. If PRU Association is performed successfully as in steps 5a and 6a and if this is an initial PRU Association or if this is a PRU Association update and information for the PRU has changed and if PRU is stationary the serving LMF may optionally instigate an Nnrf_NFManagement_NFUpdate Request service operation towards an NRF and includes an existence indication of a PRU associated with a TAI.
The LMF also indicates to the NRF to remove the TAI associated existence of PRU(s) when there are no longer any PRUs associated in the LMF for this TAI.
9. If step 8 requested by LMF the NRF returns a confirmation response to the serving LMF.
10. After being rejected at step 6b, if there are new available Routing ID(s), the PRU may perform a PRU Association procedure with the new serving LMF.
NOTE 3: The PRU may be configured with a limit on the number and/or duration of unsuccessful PRU Association attempts. When this limit is reached the PRU considers itself disassociated.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 PRU Disassociation Procedure
Precondition: The PRU has previously associated with the serving LMF using the procedure in clause 6.17.1.
1. The serving LMF sends a PRU Disassociation Request as a supplementary services message, using the Namf_Communication_N1N2MessageTransfer service operation, and a Correlation ID identifying the serving LMF. The PRU Disassociation Request may include a Routing ID for a new serving LMF.
NOTE: The Correlation ID for the serving LMF is transferred to the serving AMF to provide the Routing ID for step 3. The Routing ID for a new serving LMF, if provided, is included inside the PRU Disassociation Request and is not visible to the serving AMF. This Routing ID is different to the Routing ID for steps 3, 4 and 5 and enables the PRU to perform an Association with a new serving LMF at step 8.
2. If the PRU is in CM IDLE state, the serving AMF performs a Network Triggered service request to place the PRU in CM CONNECTED state.
3. The serving AMF forwards the PRU Disassociation Request and a Routing ID equal to the Correlation ID to the PRU using DL NAS TRANSPORT message.
4. The PRU returns a supplementary services PRU Disassociation Accept to the serving AMF in an UL NAS TRANSPORT message and includes the Routing ID received in step 3.
5. The serving AMF forwards the PRU Disassociation Accept to the serving LMF indicated by the Routing ID received at step 4 and includes a Correlation ID equal to the Routing ID.
6. If the serving LMF has indicated the PRU to an NRF during PRU Association and if serving LMF does not have any PRU to the TAI, the serving LMF issues an Nnrf_NFManagement_NFUpdate Request service operation towards the NRF and requests an indication of PRU removal. The NRF then removes the TAI associated PRU existence indication.
7. The NRF returns a confirmation response to the serving LMF.
8. If the PRU received a new Routing ID for a new serving LMF at step 3, the PRU may perform a PRU Association with the new serving LMF as described in clause 6.17.1.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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
Precondition:
The PRU has previously associated with the serving LMF using the procedure in clause 6.17.1 and is currently registered in the HPLMN.
1. The PRU performs a UE Triggered Service Request if in CM IDLE state.
2. The PRU sends a supplementary services PRU Disassociation Request to the serving AMF in an UL NAS TRANSPORT message and includes the Routing ID received at step 6a for the procedure in clause 6.17.1 for a previous PRU Association procedure. The PRU also indicates whether an acknowledgment is expected. The PRU Disassociation Request is included in the UL NAS TRANSPORT message at the NAS level.
NOTE 1: A PRU could indicate whether an acknowledgment is expected according to whether the PRU expects to be still able to receive the acknowledgment at a later time.
3. The AMF verifies whether the sender of the PRU Disassociation Request is a PRU using subscription information from the UDM.
4. The AMF selects the serving LMF based on the Routing ID and optionally the current TAI and transfers the PRU Disassociation Request to the serving LMF using an Namf_Communication_N1MessageNotify service operation. The AMF includes in the Namf_Communication_N1MessageNotify service operation an indication of whether the sender of the PRU Disassociation Request is a PRU. The AMF also includes the SUPI of the PRU.
5. The serving LMF verifies that the PRU is currently associated in the serving LMF. If the PRU is not currently associated in the serving LMF, the serving LMF performs steps 6 and 7 but not steps 8 and 9.
NOTE 2: Inconsistency between Association in a PRU versus a serving LMF might arise if a PRU is powered off or loses network coverage and if the serving LMF then performs an LMF initiated PRU Disassociation.
6. If the PRU has indicated that an acknowledgment is expected, the serving LMF returns a PRU Disassociation Accept, as a supplementary services message, using an Namf_Communication_N1N2MessageTransfer service operation towards the AMF, and a Correlation ID.
7. The serving AMF forwards the PRU Disassociation Accept and a Routing ID equal to the Correlation ID to the PRU in a DL NAS TRANSPORT message.
8. If the serving LMF has indicated the PRU to an NRF during a previous PRU Association and if serving LMF does not have any PRU to the TAI, the serving LMF invokes an Nnrf_NFManagement_NFUpdate Request service operation towards the NRF and requests an indication of PRU removal. The NRF then removes the TAI associated PRU existence indication.
9. The NRF returns a confirmation response to the serving LMF.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 clause 6.11 to obtain location information from one or more PRUs associated in the serving LMF and in the other PRU serving LMFs that is not related to the target UE. For example, the location information may include location information for the PRU(s) or for the NG-RAN or both.
2. The serving LMF for the target UE receives a location request from the serving AMF for the target UE. The location request may be included in an Nlmf_Location_DetermineLocation Request service operation for a 5GC-MO-LR, 5GC-MT-LR or 5GC-NI-LR for the target UE. Alternatively, the location request may be implied by receipt of an Namf_Communication_N1MessageNotify service operation carrying a supplementary services event report from the target UE for a periodic or triggered 5GC-MT-LR.
3. The serving LMF uses the procedures defined in clause 6.11 to obtain location information for the target UE from the target UE and/or from the NG-RAN and may determine pre-calculated location of target UE. During the procedures, the LMF decides to use PRUs to improve the positioning result.
If the serving LMF uses the procedure defined in clause 6.11.1 to obtain location information for the target UE and decides to use PRUs to improve the positioning result, the step 3 is performed after step 10 and the step 11 is skipped. During the procedure defined in clause 6.11.1, the LMF provides the assistance data including PRU measurements and the associated timestamp obtained in step 8 or step 10 to UE.
4. The serving LMF selects one or more PRUs associated with the serving LMF based on the PRU ON/OFF state information to assist in locating the target UE. The selected PRU(s) may be nearby to an initial location estimate for the target UE obtained at step 3 or indicated by a serving cell identifier for the target UE received at step 2.
NOTE 1: The PRU selection criteria are implementation specific and may be based on operator policies.
5. The serving LMF may optionally invoke an Nnrf_NFDiscovery Request service operation to an NRF. The service operation includes a PRU indication and an area which could be TAs decided by the serving LMF of the target UE based on the serving cell of the target UE.
6. If step 5 is performed, the NRF selects one or more other PRU serving LMFs based on the PRU indication and the area received in step 5 and sends an Nnrf_NFDiscovery Response to the serving LMF of target UE. The service operation includes the profiles of the other PRU serving LMFs selected by the NRF.
7. If steps 5 and 6 are performed, the serving LMF of the target UE may send an Nlmf_Location_MeasurementData Request service operation to one or more of the other PRU serving LMFs indicated at step 6. The service operation for each of the other PRU serving LMFs includes target UE cell ID or pre-calculated location of target UE in step 3.
When the serving LMF of the target UE determines to use target UE measurements and PRU measurements in time window(s) to calculate location of target UE:
- If network assisted positioning is used by the serving LMF of target UE, it provides the positioning method, time window(s) and the identifier of TRPs for the measurements to the serving LMF of PRU. The serving LMF triggers network assisted positioning procedure defined in clause 6.11.2 based on the received information.
- If UE assisted positioning is determined by the serving LMF of target UE, it provides the positioning method and time window(s) to the serving LMF of PRU. The serving LMF of PRU triggers UE assisted positioning procedure defined in clause 6.11.1 based on the received information.
NOTE 2: The time window(s) is the Time Window Information SRS List and the Time Window Information Measurement List specified in TS 38.455 [15] when network assisted positioning is used and is the NR-DL-PRS-MeasurementTimeWindowsConfig specified in TS 37.355 [20] when UE assisted positioning is used.
8. The serving LMF uses the procedures defined in clause 6.11 to obtain location information (e.g. PRU location coordinates, associated location quality/uncertainty of the PRU together with any performed location measurements) related to the target UE from the PRU(s) selected at step 4.
9. If steps 5-7 are performed and if PRU information is included in the PRU serving LMF profile sent by the NRF to the target UE serving LMF, each of the other PRU serving LMFs for step 7 uses the procedures defined in clause 6.11 to obtain the location measurements and/or location requested at step 7 from each of the PRUs identified at step 7 for this LMF.
If steps 5-7 are performed PRU serving LMFs for step 7 selects one or more PRUs based on the locally associated PRU information and information in the location measurements requested (the target UE cell ID, or pre-calculated location of target UE), and uses the procedure defined in clause 6.11 to obtain the location measurements requested at step 7 from each of the selected PRUs.
NOTE 3: Steps 3, 8 and 9 can be performed in any order, including simultaneously. If the LMF determines that simultaneous measurements for UE and PRU(s) are needed, the LMF determines time window(s) in a positioning method dependent manner for simultaneous measurements and sends the time window(s) to UE, PRU(s) and NG-RAN. Definition of the time window and the associated configuration parameters, and the corresponding positioning methods are specified in TS 37.355 [20] and TS 38.455 [15].
10. If step 9 is performed, each of the other PRU serving LMFs for step 9 returns the location measurements and the known PRU location obtained from PRUs at step 9 to the serving LMF for the target UE.
11. [Conditional] If the LMF determines to use the network assisted positioning in step 3, this step is performed. The serving LMF for the target UE determines the location of the target UE based on the location information obtained at step 1 (if step 1 is performed), step 3, step 8 and step 10.
12a. If an Nlmf_Location_DetermineLocation Request service operation for a 5GC-MO-LR, 5GC-MT-LR or 5GC-NI-LR was received at step 2, the serving LMF returns the location estimate of the target UE to the serving AMF.
12b. If an Namf_Communication_N1MessageNotify service operation carrying a supplementary services event report from the target UE for a periodic or triggered 5GC-MT-LR was received at step 2, the serving LMF sends an event report for the target UE to a GMLC with the location estimate obtained at step 11 as described in clause 6.3.1.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.18 Procedures of User Plane Connection between UE and LMF
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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.
Precondition:
The LMF can send its user plane information (i.e. IP address or FQDN) to the UE via a DL NAS TRANSPORT message of the AMF. If LMF sends its FQDN to the UE, a DNS server/resolver is used to resolve the IP address of LMF (e.g. EASDF or local DNS for local LMF address resolution). UE uses URSP which includes user plane positioning related PDU session parameters (e.g. a dedicated DNN and S-NSSAI) to establish a PDU session used for user plane positioning. SMF should select a PSA UPF (located in central site or local site) connecting with the LMF for this PDU session, based on S-NSSAI, DNN and UE location information, etc.
Session break out for local LMF service for user plane positioning can be supported by preconfiguring SMF with local LMF(s) IP address(es)/network prefix(es) and their DNAIs for positioning dedicated PDU session in certain service area(s) for local PSA and UL CL/BP insertion.
NOTE 1: Based on preconfigured local LMF information, SMF can subscribe to UE location information from AMF and perform additional local PSA and UL CL/BP insertion and corresponding forwarding rules configuration if UE moves to a location where it can be served by local LMF(s).
NOTE 2: In this Release, to avoid LMF selection conflicts, the LMFs use their dedicated FQDNs which are different from each other, but their FQDNs can have common parts in support of usage as Traffic descriptor in URSP.
NOTE 3: It is up to operator to determine appropriate QoS parameters for user plane connection between UE and LMF.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 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 plane positioning. Figure 6.18.1-1 shows a procedure triggered by LMF to support positioning over the user plane connection between UE and LMF.
Figure 6.18.1-1: Positioning via a User Plane Connection between UE and LMF initiated by LMF
NOTE 1: User Plane protocol (LCS-UPP) to support generic transport between the UE and the LMF is defined in TS 24.572 [48].
1. Based on UE user plane positioning capability, control plane congestion status (e.g. AMF load status) and other implementation factors, LMF decides whether to use the positioning procedure via a user plane connection between UE and LMF.
LMF may invoke Nnrf_NFDiscovery service operation to retrieve control plane congestion status (e.g. AMF load information). LMF may also invoke Nnrf_NFManagement_NFStatusSubscribe service to subscribe specific AMF load information. Based on AMF load information, LMF may determine to use user plane positioning, if there is available user plane connection between UE and LMF.
Steps 2-8 are skipped if there is already a user plane connection context of the target UE in LMF and LMF determines to utilize the user plane connection for positioning.
NOTE 2: LMF can select user plane positioning for specific positioning methods (e.g. motion sensor-based method) and it is based on implementation and local configuration to determine which positioning method requires user plane transport.
NOTE 3: The procedure can also be triggered when LMF receives a location request from AMF via control plane signalling as defined in clause 6.1 and clause 6.3.
2. [Conditional] If LMF decides to utilize user plane for positioning and there is no established secure user plane connection between the UE and LMF, LMF invokes Namf_communication_N1N2MessageTransfer service operation to send the user plane information to AMF in a NAS container to indicate UE to utilize user plane over TLS for positioning. The user plane information includes the user plane positioning address of the LMF. The LMF allocates LCS-UP binding ID to be used to associate the user plane connection to be established with the target UE and includes this LCS-UP binding ID in the user plane information. The LMF associates the target UE identity (SUPI and/or GPSI) with this LCS-UP binding ID.
If the UE supports the user plane positioning capability and AMF has not subscribed the status of LCS user plane connection, the AMF may subscribe from LMF the status of LCS user plane connection.
NOTE 4: Security mechanism to support user plane positioning is defined in Annex Q.2 of TS 33.501 [50].
3. [Conditional] When AMF receives the user plane information from LMF in step 2, AMF sends it to UE via a DL NAS TRANSPORT message.
4. [Conditional] If there is no established applicable PDU session for the user plane positioning, the UE uses the URSP as defined in TS 23.503 [41] which includes user plane positioning related PDU session parameters, e.g. a dedicated DNN and S-NSSAI, to establish the PDU session for user plane positioning. UE establishes a secured user plane connection with LMF. If LMF send its FQDN to the UE, a DNS server/resolver is used to resolve the IP address of LMF (e.g. EASDF or local DNS for local LMF address resolution). After the secured user plane connection been established successfully, the UE sends the LCS-UP binding ID received in step 3 to LMF via the secured user plane connection to enable LMF to perform the correlation of the UE with the secured user plane connection. The LCS-UP binding ID will be released once the correlation is complete.
5. [Conditional] UE sends an acknowledgement to LMF through AMF to indicate a success of user plane connection establishment for positioning service or a failure to utilize the user plane connection as defined in TS 24.572 [48].
6 [Conditional] AMF sends the acknowledgement received in step 5 to the LMF via Namf_N1messageNotify service.
7. [Conditional] LMF indicates AMF in the Nlmf_Location_UPNotify message that user plane connection between the UE and LMF has been established.
8. [Conditional] The AMF stores the LCS-UP connection context as part of UE context.
9. If LMF or UE determines to utilize the user plane connection for positioning and the secure user plane connection is established, LPP messages are transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data. Supplementary services messages including event report messages, periodic triggered invoke messages and MS cancel deferred location messages may also be transferred between LMF and UE via the established user plane connection.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 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 LMF, initiated by UE
1. UE sends a user plane connection establishment request to AMF via NAS Message, if there is no established secure user plane connection between the UE and LMF and UE decides to request a user plane connection for upcoming positioning requests.
2. [Conditional] If the UE is authorized based on UE Subscription to use the user plane positioning, AMF selects an LMF which capable to establish a user plane session for positioning with the UE. AMF may either query the NRF or based on local configuration to discover and select a proper LMF.
3. [Conditional] The AMF sends a Nlmf_Location_UPConfig Request towards LMF to request set up of an LCS-UP connection. The AMF shall include the target UE identity (see TS 29.572 [12]) (SUPI and/or GPSI) in the request.
4. [Conditional] If LMF accepts to utilize user plane for positioning and there is no established secure user plane connection between the UE and LMF, LMF sends a user plane information to AMF to indicate UE to accept and utilize user plane for positioning. The user plane information includes the user plane positioning address of the LMF. The LMF allocates a LCS-UP binding ID to associate the user plane connection to be established with the target UE and includes the LCS-UP binding ID in the user plane information. The LMF associates the target UE identity (SUPI and/or GPSI) with the LCS-UP binding ID.
5. [Conditional] When AMF receives the user plane information from LMF in step 4, AMF forwards it to UE via a DL NAS TRANSPORT message.
6. [Conditional] If there is no established secure user plane connection, UE establishes a secured user plane connection with LMF. UE uses the user plane positioning address of the LMF, together with the information in the URSP, to determine the PDU session parameters including DNN+S-NSSAI. UE uses the PDU session parameter to establish PDU session. When SMF receives the request, it selects a proper UPF based on the DNN+S-NSSAI, and establishes the connection between the UPF and LMF.
After the secured user plane connection has been established successfully, the UE sends the LCS-UP binding ID received in step 4 to LMF via the secured user plane connection to enable LMF to perform the correlation of the UE with this secured user plane connection. The LCS-UP binding ID will be released once the correlation is complete.
7. [Conditional] UE sends an acknowledgement to LMF through AMF to indicate a success of user plane connection establishment for positioning service or a failure to utilize the user plane connection as defined in TS 24.572 [48].
8. [Conditional] AMF sends the acknowledgement received in step 7 to the LMF via Namf_N1messageNotify service.
9. [Conditional] LMF responds to AMF that user plane connection between the UE and LMF has been established.
10. [Conditional] The AMF stores the LCS-UP connection context as part of UE context
11. [Conditional] After the secure user plane connection is established, if LMF determines to utilize the user plane connection for positioning after receiving a positioning request from AMF, or UE determines to utilize the user plane connection for positioning, LPP messages are transferred between UE and LMF for UE based positioning, UE assisted positioning and delivery of assistance data. Supplementary services messages including event report messages, periodic triggered invoke messages and MS cancel deferred location messages may also be transferred between LMF and UE via the established user plane connection.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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: Connection modification between UE and LMFs
1a. [Conditional] The LMF discovers a need to change LMF or re-establish the user plane connection between UE and LMF or terminate the user plane connection, e.g. after receiving an event report via user plane from UE or after receiving an AMF relocation information from a target AMF (target AMF obtains from source AMF the UE LCS-UP context which indicates UE has maintained LCS-UP connection with the source LMF, the target AMF may inform the source LMF about the AMF change using the Nlmf_Locatoion_UPConfig request). The LMF sends an Nlmf_Location_UPNotify message that includes connection move (termination and establishment) or termination is required and if connection move is requested then message may include target LMF identification. The address of the AMF was provided to LMF as a "Notification Target Address" in latest Nlmf_Location_UPConfig message or Nlmf_Location_UP Subscribe message. If the LMF is going to terminate the user plane connection, step 1a, step 3, step 6 and step 7 are performed and other steps are skipped.
If the request is to terminate the user plane connection, the AMF releases the LCS-UP context.
NOTE 1: The LMF change procedure is independent from the SSC mode of the PDU Session with dedicated DNN used for positioning. For SSC mode 2/3, PSA UPF connection with the LMF can be relocated with UE movement and LMF can discover the need to change LMF to reduce the user plane path latency.
1b. [Conditional] AMF should perform LMF reselection if a target LMF identification received from source LMF for user plane positioning, or AMF may perform LMF reselection if a UE established a LCS UP connection with the source LMF to a new location (which may be out of serving area of source LMF and in serving area of target LMF) and select the target LMF for the current UE location based on LMF service area, LMF user plane positioning capability information and other information listed in clause 5.1. LMF needs to be capable to establish a user plane session for positioning with the UE. After AMF relocation, the target AMF may trigger the LMF reselection and LCS-UP connection modification procedure, e.g. if the source LMF does not perform LMF reselection.
2. [Conditional] Steps 3-10 of figure 6.18.2-1 are performed between AMF (or Target AMF), UE, and Target LMF with addition that UE also terminate connection to Source LMF.
3. The AMF sends an Nlmf_Location_UPConfig Request towards the source LMF. The message may include a request for the Source LMF to terminate a specific user plane connection to the UE and the Target LMF identification. Alternatively, it may include information about AMF reallocation.
NOTE 2: AMF relocation does not necessarily always cause LMF reselection, the AMF relocation information can keep the LMF informed.
4-5.[Conditional] The source LMF may invoke an Nlmf_Location_LocationContextTransfer Request service operation towards the target LMF to provide the current location context(s) of the UE, if there is user plane based periodic and triggered UE location events report context(s). The target LMF informs source LMF of the location context transfer operation results.
6. [Conditional] If the user plane connection to source LMF is still active, the source LMF terminates the connection to the UE.
7. The LMF sends Nlmf_Location_UPConfig Response message to AMF to confirm connection termination or acknowledge change of AMF. If this procedure is used for termination, the AMF will release the LCS-UP context after receiving the response message.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.19 Location Service Continuity between EPS and 5GS
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 the non-standardized Lr' interface.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.19.1 Location Service Continuity for Immediate Location Request
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 EPS handover happens successfully as described in figure 4.11.1.2.1-1 of TS 23.502 [19] - AMF receives the relocation complete notification message from MME and record the target MME ID.
4. AMF instructs the LMF to cancel the ongoing LCS session.
5. The LCS Session on 5GS is cancelled by LMF.
6. LMF sends the Nlmf_Location_DetermineLocation Response to AMF after the cancellation is complete, LMF may include the current available location result in the response even it doesn't meet the requested QoS.
7. [Conditional] If the location request is received from 5GC-GMLC, AMF responds failure to the 5GC-GMLC with Namf_Location_ProvidePositioningInfo Response indicating failure of the LCS session with cause = HO to EPC while also including the target MME ID for the UE. The response may contain the location result from LMF at step 6.
NOTE: The LCS session cancellation with the UE and NG-RAN is to be completed before the UE is handed over to LTE.
8. [Conditional] If the step 7 is performed, the 5GC-GMLC forwards the location request to the EPC-GMLC including all the parameters of the LCS Request and the target MME ID. The location result from step 6 and 7 may also be included as one of the candidates of EPC-GMLC's location result.
9. The EPC-GMLC may reconstruct the request (e.g. area information in EUTRA for area event), it forwards the LCS Request to the Target MME received at step 8 in the case of MT-LR. The LCS session is started in EPS (e.g. steps 2-10 in Figure 9.18 of TS 23.271 [4]). In the case of MO-LR, the UE restarts the EPC-MO-LR.
10. [Conditional] If step 8 is performed, the UE location estimate is returned by the EPC-GMLC to the 5GC-GMLC
11. [Conditional] If step 10 is performed, 5GC-GMLC forwards the result from EPC-GMLC to the AF/LCS Client. AF/LCS Client is transparent to the Handover process.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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, EPS to 5GS handover happens successfully, as described in steps 1-14 in figure 4.11.1.2.2.2-1 of TS 23.502 [19] - MME receives Forward Relocation Complete Notification from the AMF and stored the AMF ID.
3. [Conditional] If the location request is received from EPC-GMLC, MME sends Subscriber Location Report to GMLC with Handover event type, UE identifies and AMF ID as target node information, EPC-GMLC identifies the handover by event type and target AMF.
4. The LCS session is cancelled as described in clause 9.4.3a of TS 23.271 [4].
5. [Conditional] If step 3 is performed, the EPC-GMLC forwards the location request to the 5GC-GMLC including all the parameters of the LCS Request and the target AMF ID.
6. The 5GC-GMLC may reconstruct the request (e.g. convert the area information for area event), it forwards the LCS Request to the Target AMF received in the case of MT-LR. The LCS session is started in 5GS. In the case of MO-LR, the UE restarts the 5GC-MO-LR.
7. [Conditional] If step 5 is performed, the response is returned by the 5GC-GMLC to the EPC-GMLC.
8. [Conditional] If step 7 is performed, EPC-GMLC forwards the response from 5GC-GMLC to the LCS Client.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 message in step 4 or step 5 in Figure 6.1.2-1, 5GC-GMLC invokes the Nudm_EventExposure_Subscribe to HSS+UDM to subscribe the CN Type change event report.
3. LMF handles the ongoing LCS session.
4. 5GS to EPS mobility happens successfully as described in Figure 4.11.2.2-1 of TS 23.502 [19].
5. [Conditional] If step 2 is performed, the UDM detects that the CN Type of UE changes, the UDM notifies the CN Type of UE to 5GC-GMLC by invoking the Nudm_EventExposure_Notify service operation.
6a. The LMF invokes Nlmf_Location_DetermineLocation Response including failure.
6b. The AMF invokes Namf_Location_ProvidePositioningInfo Response including failure.
7. The steps 8~ 11 in the location service continuity from 5GS to EPS with N26 interface for immediate location request in clause 6.19.1.1 are performed in the case of MT-LR. In the case of MO-LR, the UE restarts the EPC-MO-LR procedure.
NOTE: The 5GC-MT-LR in 5GS may be failed because of timeout of the location request. The 5GC-GMLC can trigger the step 6 when the LIR in 5GS is failed.
8. [Conditional] If step 2 is performed, 5GC-GMLC invokes the Nudm_EventExposure_UnSubscribe to HSS+UDM to cancel the subscription of the CN Type change event report.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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-GMLC initiates the location request, the EPC-GMLC requests the 5GC-GMLC to subscribe the CN Type change event report. The 5GC-GMLC invokes the Nudm_EventExposure_Subscribe to HSS+UDM to subscribe the CN Type change event report.
3. E-SMLC handles the ongoing LCS session.
4. EPS to 5GS mobility happens successfully as described in Figure 4.11.2.3-1 of TS 23.502 [19].
5. [Conditional] If step 2 is performed, the UDM detects that the CN Type of UE changes, the UDM notifies the CN Type of UE to 5GC-GMLC by invoking the Nudm_EventExposure_Notify service operation. The 5GC-GMLC notifies the CN Type of UE to EPC-GMLC.
6. The steps 5~ 8 in the location service continuity from EPS to 5GS with N26 interface for immediate location request in clause 6.19.1.2 are performed in the case of MT-LR. In the case of MO-LR, the UE restarts the EPC-MO-LR procedure.
NOTE: The EPC-MT-LR in EPS may be failed because of timeout of the location request. The EPC-GMLC can trigger the step 6 when the LIR in EPS is failed.
7. [Conditional] If step 2 is performed, 5GC-GMLC invokes the Nudm_EventExposure_UnSubscribe to HSS+UDM to cancel the subscription of the CN Type change event report.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 still supported using the procedures in clause 6.3.2 and clause 6.3.3 and clauses 9.1.19.2 and 9.1.19.3 of TS 23.271 [4], with the enhancement that for the UE or Client initiated cancel procedure in EPS, after EPC-(H)GMLC receiving LCS Cancel Service request, it also transfers the request to 5GC-(H)GMLC then 5GC-(H)GMLC initiate the cancel procedure of clause 6.3.3; for UE or Client initiated cancel procedure in 5GS, after 5GC-(H)GMLC receiving LCS Cancel Service request, it also transfers the request to EPC-(H)GMLC to release context in EPC-(H)GMLC.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 service request in this step contains multiple location QoS, location QoS mapping is performed by 5GC-(H)GMLC and a mapped location QoS applicable to EPS is also transferred to LMF.
NOTE 1: Multiple QoS class is supported in 5GS but not in EPS.
2. Target UE positioning starts in 5GS with steps 2~15 of deferred 5GC-MT-LR procedure in clause 6.3.1.
- If handover happens before step 16 in clause 6.3.1, the UE has not received the LCS Periodic-Triggered Invoke Request message. After handover complete, the AMF notifies 5GC-GMLC. The 5GS to EPS handover notification also includes the MME ID for the target UE. The 5GC-GMLC sends the location request with the mapped location QoS to EPC-GMLC to trigger the deferred/periodic MT-LR in EPS (i.e. steps 3-11 in clause 6.19.1.1 are performed with the enhancement in step 8 that 5GC-GMLC perform location QoS mapping, then obtain and forward the mapped location QoS which can be applicable to EPS to EPC-GMLC, the mapping may be performed by choosing the most stringent values from the "LocationQoS" and set the "LcsQoSClass" in "LocationQoS" as the "Best Effort" and with the difference that in step 9 in clause 6.19.1.1, the performed procedure is the steps 3-20 of Deferred EPC-MT-LR in clause 9.1.19.1 in TS 23.271 [4]) and steps 3a-9 are not performed;
- If handover or UE movement with IDLE state happens after step 16 in clause 6.3.1, the UE has received the LCS Periodic-Triggered Invoke Request message. The UE does not release the deferred MT-LR context after handover or movement with IDLE state. The following steps 3a-9 are performed;
3a. [Conditional] In the periodic or triggered 5GC-MT-LR case, if the LCS QoS class in location request is "multiple QoS class" and there is a mapped location QoS mapped by GMLC in the location request, the LMF includes the mapped location QoS in step 3b if the access type allowed for the UE for event reporting includes "E-UTRAN connected to EPC".
3b~3c. [Conditional] In the deferred periodic or triggered 5GC-MT-LR case, LMF sends the LCS Periodical-Triggered Invoke Request to UE. If step 3a is performed, besides the multiple location QoS, the request also includes the mapped location QoS used for EPS. UE response to LMF with the LCS Periodical-Triggered Invoke Return Result.
4. [Conditional] LMF sends the Nlmf_Location_DetermineLocation Response to AMF.
5. [Conditional] UE may stay in 5GC over a period of time and the deferred 5GC-MT-LR procedure can continue in 5GS.
6. [Conditional] 5GS to EPS handover happens or UE moves to EPS with IDLE state. The LMF in 5GS does not release resource for the deferred MT-LR session after this step.
7-8. [Conditional] For the deferred periodic or triggered MT-LR case, when the event is detected by UE in EPS, the UE shall send an LCS MO-LR Invoke message for event report to the MME. If the location QoS is multiple QoS in 5GS, the UE shall include the mapped location QoS which is applicable to EPS in the LCS MO-LR Invoke message.
9. [Conditional] For the deferred periodic or triggered MT-LR case, the procedure continues with step 15-23 as described in Figure 9.1.19.1-1 of TS 23.271 [4]
10-11. [Conditional] EPC-(H)GMLC sends LCS Service Response to 5GC-(H)GMLC and 5GC-(H)GMLC performs the step 30 of Figure 6.3.1-1.
NOTE 2: If UE detects handover is not complete but the event is triggered, i.e. Step 8 happens before handover complete, the UE waits for handover complete to send the triggered LCS MO-LR Invoke message. For area event, the geographical area can be mapped into cell(s)/TAI(s) corresponding to 5GS and EPS, so UE can detect area event based on received cell(s)/TAI(s) no matter it is in 5GS or EPS.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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. The 5GC-GMLC derives the address of EPC-GMLC by using the mechanisms described in step 2 in clause 6.13.1.
3. Target UE positioning starts in EPS with steps 1-16 of deferred EPC-MT-LR procedure for Periodic and Triggered Location procedure in Figure 9.1.19.1-1 of TS 23.271 [4], with enhancement that EPC-(H)GMLC obtains LDR reference number and 5GC-(H)GMLC address from 5GC-(H)GMLC for the periodic or triggered location session.
- If handover happens before step 9 in clause 9.1.19.1 of TS 23.271 [4], the UE has not received the LCS Periodic-Triggered Event Invoke message. After handover complete, the MME notifies EPC-GMLC. The EPS to 5GS handover notification also includes the AMF ID for the target UE. The EPC-GMLC sends the location request to 5GC-GMLC to trigger the deferred/periodic MT-LR in 5GS (i.e., steps 3-8 in clause 6.19.1.2 are performed with the difference that in step 6, the performed procedure is the steps 2-29 of Deferred 5GC-MT-LR procedure clause 6.3.1) and steps 4-7 are not performed;
- If handover or UE movement with IDLE state happens after step 9 in clause 9.1.19.1, the UE has received the LCS Periodic-Triggered Event Invoke message. The following steps 4-7 are performed.
4. [Conditional] 5GS to EPS handover happens or UE moves to EPS with IDLE state.
5-7. [Conditional] For the deferred periodic or triggered MT-LR case, when the event is detected by UE in 5GS, the UE should send an Event Report message to the LMF through AMF.
For the deferred periodic or triggered MT-LR case, the procedure continues with steps 26-30 as described in clause 6.3.1.
NOTE: If UE detects handover is not complete but the event is triggered, i.e. Step 5 happens before handover complete, the UE waits for handover complete to send the event report message.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.20 Ranging/Sidelink Positioning procedures
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 directions from other UEs, velocities and relative velocities, depending on the service request. The Ranging/Sidelink Positioning location results may be represented by a geographical coordinate or a local coordinate or both.
If the Target UE decides to initiate SL-MO-LR procedure, it includes one or multiple SL reference UE(s) / Located UE (s) in the service request. See TS 23.586 [40] for more information on how this generic procedure can be used.
Figure 6.20.1-1: SL-MO-LR Procedure
Precondition: UE1 is in coverage and registered with a serving PLMN that supports Ranging/Sidelink Positioning. UEs 2 to n may or may not be in coverage and, if in coverage and are registered in the same serving PLMN as UE1 as specified in clause 5.5.1 of TS 23.586 [40].
In this procedure, the information in the SLPP messages sent between UEs 2 to n and UE-1 is included in the SLPP messages in the supplementary service messages sent between UE-1 and the LMF. For this case, the supplementary service messages are used in the following steps 8, 9, 10, 11, 13, 14, 15, 19 and 23. When information other than SLPP message(s) for UE1 need to be included, supplementary service message is used to send the information, otherwise, only the SLPP message(s) is used between UE-1 and LMF.
1. The procedures and signalling specified in clause 6.2 of TS 23.586 [40] are used to provision the Ranging/Sidelink positioning service authorization and policy/parameter provisioning to UEs 1 to n.
2. Based on a trigger of service request (e.g. received from the application layer), which includes UE1/.../UEn, UE discovery is performed for Ranging/Sidelink positioning as specified in clause 6.4 of TS 23.586 [40]:
- If UE1 is the target UE, UE1 discovers UEs 2 to n.
3. Secure groupcast and/or unicast links are established between UEs 1 to n to enable UE1 to exchange Ranging and Sidelink Positioning Protocol (RSPP) messages over PC5-U reference point with each of UEs 2 to n and possibly enabling UEs 2 to n to exchange RSPP over PC5-U between each other as defined in clause 5.3 of TS 23.586 [40]. Groupcast and/or unicast links are only established between UEs 1 to n that are registered in the same PLMN.
Security mechanisms defined for V2X unicast mode communication in TS 33.536 [44] and for 5G ProSe unicast mode Direct Communication in TS 33.503 [45] are reused. The Security procedures for RSPP signalling using groupcast mode is specified in TS 33.533 [46].
4. UE1 and UEs 2 to n may communicate over PC5 for authorization of Ranging/Sidelink positioning. Each UE verifies that Ranging/Sidelink positioning is permitted, including whether Ranging/SL positioning results may be transferred to an LCS Client or AF if this is used, according to any service authorization and policy/parameter provisioning received at step 1. This step is specified in TS 33.533 [46].
5. The Ranging/Sidelink positioning capabilities exchange between UE-1 and UEs 2 to n is performed using SLPP message(s) as specified in TS 38.355 [47] via the groupcast and/or unicast links established in step 3.
Step 4 and 5 may be performed to transfer the information of UEs which are not served by the LMF.
NOTE 1: UE2/.../UEn is not assumed to be served by the same LMF serving UE1.
6. Based on the Ranging/Sidelink positioning capabilities of UE1/.../UEn, the target UE determines SL-MO-LR is to be performed.
7. If UE1 is in CM-IDLE state, UE1 instigates a UE triggered Service Request in order to establish a signalling connection with the serving AMF of UE1.
8. UE1 sends a supplementary services SL-MO-LR request message to the serving AMF in an UL NAS TRANSPORT message. The SL-MO-LR request indicates the other UEs 2 to n (using Application Layer ID), indicates any assistance data needed, indicates whether location calculation assistance is needed, and indicates whether location results should be transferred to an LCS client or AF. The message may 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 indicating which MO-LR service of the LCS Client is requested by the UE may be included. For location calculation assistance from the LMF, the preferred type of Ranging/Sidelink positioning location results (e.g. absolute locations, relative locations or distances and directions between pairs of UEs, velocities and relative velocities) and the required QoS are included.
9. The serving AMF selects an LMF serving UE1 (e.g. an LMF that supports Ranging/Sidelink positioning) and sends an Nlmf_Location_DetermineLocation service operation towards the LMF with the information from the SL-MO-LR Request. The service operation includes a LCS Correlation identifier. AMF may include its stored information from step 21, the sidelink positioning capabilities of UE1 in the service operation.
10. The LMF may send a request to UE1 for the required capabilities of UEs 2 to n using supplementary service message with embedded SLPP message(s) as specified in TS 38.355 [47] and the correlated application layer ID(s) for SLPP message(s) for UEs 2 to n. The LMF requests for the capabilities of UE1 by SLPP message.
LMF may also provide the list of candidate Located UE(s), identified by the Application Layer ID by supplementary service message to UE1, if absolute location is requested at step 8. LMF also includes capabilities of each candidate Located UE in the request, if available, when Target UE selecting Located UE is indicated.
11. UE 1 returns its capabilities to the LMF using SLPP message as specified in TS 38.355 [47] if requested by the LMF at step 10. UE1 may additionally return the capabilities of the other UEs if requested by the LMF at step 10 using supplementary service message(s) with embedded SLPP message(s) and the correlated Application Layer ID(s). UE1 requests the capabilities of UE2 to n separately using SLPP message over PC5 if step 5 is not performed. After checking the capabilities of the UEs, LMF may downselect the UEs (so called, down-selected list of UEs) for SL positioning operation. UE 1 also indicates the selected Located UE(s) to the LMF in the response.
NOTE 2: The embedded SLPP message(s) can be differentiated by the correlated Application Layer ID(s) included in the supplementary service message.
12. If Target UE's absolute location information is required at step 8, LMF can either retrieved the location of the Located UE(s) locally if available or triggers 5GC-MT-LR procedure to the (V)GMLC to acquire the absolute location of the Located UE(s) using Application Layer ID of the Located UE(s). LMF may use the QoS requirement for Target UE's positioning received at step 8 to derive the required QoS for Located UE(s) positioning and includes the required QoS for Located UE positioning in the request to GMLC. If scheduled location time is used in step 15, LMF includes the same scheduled location time in the request to GMLC. (V)GMLC requests to retrieve the mapping of Application Layer ID to GPSI as specified in clause 4.3.9 of TS 23.586 [40]. If mapping of Application Layer ID to GPSI is not available for any of these Located UE(s), the UE(s) is considered as roaming UE. The (V)GMLC uses local configuration to get home PLMN ID. The (V)GMLC triggers 5GC-MT-LR procedure to the home GMLC of each of these roaming Located UE(s) to acquire the absolute location of the UE(s).
13. UE1 may send a request for specific assistance data to the LMF, if not requested in step 8.
- For the specific assistance data used by UE1, the request is transmitted by SLPP message.
- For the specific assistance data used by UE2/…/UEn, the request is transmitted by supplementary service message with embedded SLPP messages and correlated Application Layer IDs.
14. LMF sends the requested assistance data to UE1 and optionally a down-selected list of UEs using an SLPP message for UE1 assistance data and using supplementary service message(s) with embedded SLPP message(s) for UE 2 to n assistance data as specified in TS 38.355 [47] and the correlated Application Layer ID(s). UE1 forwards the assistance data received from LMF to UE2/.../UEn (or the indicated downselection thereof) using SLPP messages as specified in TS 38.355 [47]. The assistance data may assist UEs 1 to n (or the indicated downselection thereof) to obtain Sidelink location measurements at step 16 and/or may assist UE1 to calculate Ranging/Sidelink positioning location results at step 18 and may include the absolute location(s) of Located UE(s) in case the LMF determines to use Network-assisted SL Positioning and if absolute location information is requested in step 8.
NOTE 3: Steps 10 and 11 can be omitted if UE1 includes messages containing the capabilities of UEs 1 to n in the SL-MO-LR request at step 8 and step 9. Step 13 can be omitted if UE1 includes a message containing the request for specific assistance data in the SL-MO-LR request at step 8.
15. If the SL-MO-LR request at step 8 indicated location calculation assistance is needed and/or indicated transfer of Ranging/Sidelink positioning location results to an LCS Client or AF, the LMF sends a request for location information of UE1 by SLPP message and location information of UE2-UEn by supplementary service message. If LMF determines to apply Network-assisted Sidelink Positioning, LMF includes in the request the indication of Network-assisted Sidelink Positioning. If scheduled location time is not received at step 9. LMF may generate a scheduled location time, e.g. based on response time, and include the scheduled location time in the request.
16. UE1 performs a Ranging/Sidelink positioning procedure among UEs 1 to n (or the indicated downselection thereof) in which UEs obtain Sidelink location measurements and UEs 2 to n (or the indicated downselection thereof) transfer their Sidelink location measurements to UE1. If scheduled location time is received at step 15, Sidelink positioning/ranging is performed at the scheduled location time. This procedure is specified in TS 38.355 [47].
17. For the case of Network-assisted SL Positioning (i.e., the indication of Network-assisted SL Positioning is received in step 15), if Target UE's absolute location information is required at step 8 and if absolute location of Located UE(s) is not available, the Target UE may send a supplementary services request to the Located UE(s) to request their locations. The Located UEs may already know their locations or may trigger 5GC-MO-LR procedure to acquire their own absolute location, after which a Located UE may provide the location of the Located UE to the Target UE. The QoS requirement for Target UE's positioning, is used by the Target UE to derive the required QoS for Located UE(s) positioning. The required QoS for Located UE(s) positioning is included in the request.
NOTE 4: Based on implementation, a Located UE may locally check whether it is allowed to share its absolute location.
18. If LMF determined in step 15 to use Network-assisted Sidelink Positioning, at least one of UE1/.../UEn calculates Ranging/Sidelink positioning location results based on the Sidelink location measurements obtained at step 16 and possibly using assistance data received at step 14 as specified in TS 38.355 [47]. The Ranging/Sidelink positioning location results can include absolute locations, relative locations i.e. distance and/or directions related to the UEs.
19. If UE1 received a request for location information at step 15, UE1 sends a response using supplementary service message with embedded SLPP message(s) as specified in TS 38.355 [47] and the correlated Application Layer ID(s) for SLPP message(s) for UEs 2 to n to the LMF to include the Sidelink location measurements obtained at step 16 or the Ranging/Sidelink positioning location results obtained at step 18 if step 18 was performed. In the response message, UEs 2 to n (or the indicated downselection thereof) are identified by its Application Layer ID. If only UE1's location information is sent, UE1 sends a response using SLPP message for UE1 to LMF.
20. If the LMF will calculate location results, the LMF calculates Ranging/Sidelink positioning location results for the target UE based on the Sidelink location measurements received at step 19 and absolute location of Located UE(s) at step 12 or step 17. The Ranging/Sidelink positioning location results can include absolute locations, relative locations i.e. distance and/or directions related to the UEs, depending on the location request received in step 8.
21. The LMF returns an Nlmf_Location_DetermineLocation service operation response to the AMF and includes the Ranging/Sidelink positioning location results received at step 19 or calculated at step 20. The service operation may also contain the UE1's sidelink positioning capabilities if the capabilities are received in step 11 including an indication that the capabilities are non-variable and not received from AMF in step 9.
22. If Ranging/Sidelink positioning location results were received at step 21, the AMF performs steps 7-12 of clause 6.2 to send the Ranging/Sidelink positioning location results to the GMLC and to an AF or LCS Client if this was requested at step 8. The Ranging/Sidelink positioning location results include the identities for the respective UEs received at step 8. The AMF may store the UE1's sidelink positioning capabilities from step 21.
NOTE 5: Sending location results to an AF or LCS Client may require privacy verification from UEs and/or from the HPLMNs of UEs.
23. The AMF returns a supplementary services SL-MO-LR response to UE1 in a DL NAS TRANSPORT message and includes any Ranging/Sidelink positioning location results received at step 21 if the SL-MO-LR request at step 8 indicated location calculation assistance is needed.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 Positioning capability into account for LMF selection.
- In step 4, the AMF provides the UE's Ranging/Sidelink Positioning capability to LMF.
- Step 5 is replaced by step 10-16 of clause 6.20.3 with the following adaptations:
- UE1 is the target UE, and UE2/.../UEn is the Located UE.
- In step 10, the type of required location results is absolute location, and the other UEs 2 to n are the candidate Located UE(s) if included. After LMF determines that the assistance of Located UE is needed for Target UE Positioning, LMF decides that Target UE or LMF selects Located UE, and SL-MT-LR request also includes the indication of Target UE/LMF selecting Located UE. LMF includes capabilities of each candidate Located UE in the request, if available, when Target UE selecting Located UE is indicated.
- In step 14, if UE1 receives the indication of LMF selecting Located UE in step 11, SL-MT-LR response includes the obtained information of all the discovered Located UEs. LMF performs the Located UE selection based on the obtained information of all the discovered Located UEs, and sends Application Layer ID of the selected Located UEs to the UE1 in step 16. If UE1 receives the indication of Target UE selecting Located UE in SL-MT-LR request, UE1 performs the Located UE selection, and SL-MT-LR response includes Application Layer ID of the selected Located UEs.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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, ..., UEn. In the procedure, the GMLC determines a UE among the n UEs to be designated UE1 (i.e. Target UE in TS 23.586 [40]) and one or more other UEs designated UE2, UE3, ..., UEn (n≥2) (i.e. Reference/Located UEs in TS 23.586 [40]). The Ranging/Sidelink Positioning location results may include absolute locations, relative locations or distances and directions related to the UEs, velocities and relative velocities based on the service request. The Ranging/Sidelink Positioning location results may be represented by a geographical coordinate or a local coordinate or both.
Procedure for periodic and triggered SL-MT-LR is defined in clause 6.20.4.
Figure 6.20.3-1: SL-MT-LR Procedure
Precondition: At least one of the n UEs is in coverage and registered with a serving PLMN that supports Ranging/Sidelink Positioning.
1. The LCS Client or the AF (via NEF) sends an LCS service request by invoking the Ngmlc_Location_ProvideLocation service operation to the (H)GMLC for Ranging/Sidelink Positioning location results for the n UEs which may each be identified by an Application Layer ID and/or a GPSI and/or a SUPI. The request may include the required QoS, the required location results (e.g. absolute locations, relative locations or distances and/or directions related to the UEs, velocities and relative velocities), the SL reference UE(s) in case of relative locations, distance, or direction, Located UE(s) and Coordinate ID defined in TS 38.455 [15] representing a local coordinate in case of absolute locations. The information of UE initiating the Ranging/SL Positioning may be included to help (H)GMLC select the corresponding UE in step 3. The (H)GMLC or NEF authorizes the LCS Client or the AF for the usage of the LCS service. If the authorization fails, the remaining steps are skipped and the (H)GMLC or NEF responds to the LCS Client or the AF with the failure of the service authorization.
In addition, an Application Layer ID shall be used for each of the n UEs to enable discovery of the UEs at step 12. If any of the UEs belongs to another PLMN, then (H)GMLC requests the Home GMLC of each of those UEs to retrieve the mapping information between Application Layer ID and GPSI. The Home GMLC of each of those UEs queries the NEF in its own PLMN for the mapping Application Layer ID as specified in clause 4.3.9 of TS 23.586 [40].
2. The (H)GMLC invokes a Nudm_SDM_Get service operation towards the UDM of each of the n UEs to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the UE Privacy setting of the UE. The (H)GMLC checks the UE Ranging/SL Positioning privacy profile. If only the UE's SUPI is provided to the (H)GMLC, (H)GMLC can get the UE's GPSI along with the privacy settings. If Application layer IDs of the UEs are not provided to the (H)GMLC, the (H)GMLC can query the NEF for the mapping Application Layer ID as specified in clause 4.3.9 of TS 23.586 [40]. If any of UEs belong to another PLMN, then (H)GMLC sends a request to the Home GMLC of each of those UEs to check the Ranging/SL positioning privacy information of those UE(s) identified by GPSI or SUPI. The Home GMLC of each of those UEs queries the UDM in its own PLMN via Nudm_SDM_Get service operation to get the privacy settings of the UE and sends back the privacy check result to the (H)GMLC.
3. The (H)GMLC invokes a Nudm_UECM_Get service operation towards the UDM of each of the n UEs (for which GPSI or SUPI is available), one at a time, using the GPSI or SUPI of each UE. The (H)GMLC selects the UE (e.g. which is treated as UE1 in following steps) that initiates the Ranging/SL Positioning and selects the corresponding serving AMF, based on UE subscription and UE reachability. If the UE is not reachable, the (H)GMLC does not select such UE to initiate the Ranging/SL Positioning.
NOTE: 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 (V)GMLC address at UE registration on an AMF as defined in clause 4.2.2.2.2 of TS 23.502 [19].
4. For a non-roaming case, this step is skipped. In the case of roaming, the (H)GMLC may receive an address of a (V)GMLC (together with the network address of the current serving AMF) from the UDM in step 3, otherwise, the (H)GMLC may use the NRF service in the (H)PLMN to select an available (V)GMLC in the (V)PLMN, based on the (V)PLMN identification contained in the AMF address received in step 3. The (H)GMLC then sends the location request to the (V)GMLC by invoking the Ngmlc_Location_ProvideLocation service operation towards the (V)GMLC. In the cases when the (H)GMLC did not receive the address of the (V)GMLC, or when the (V)GMLC address is the same as the (H)GMLC address, or when both PLMN operators agree, the (H)GMLC sends the location service request message to the serving AMF. In this case, step 4 is skipped. The (H)-GMLC also provides the LCS client type of AF, if received in step 1, 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 (V)GMLC first authorizes that the location request is allowed from this (H)GMLC, PLMN or from this country. If not, an error response is returned. The (H)GMLC or (V)GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF serving UE1 to request Ranging/Sidelink positioning location results of the n UEs. The service operation includes the SUPI of UE1, Application layer IDs of the UEs, the client type and may include the required LCS QoS, the required location results (e.g. relative locations i.e. distances and directions between pairs of UEs, velocities and relative velocities) and other attributes as received or determined in step 1.
6. If UE1 is in CM-IDLE state, the AMF initiates a network triggered Service Request procedure to establish a signalling connection with UE1.
If signalling connection establishment fails, steps 7-17 are skipped.
7-8. If the indicator of privacy check indicates an action is needed, then same operation as that of step 7-8 of clause 6.1.2 is carried out.
9. The serving AMF selects an LMF serving UE1 (e.g. an LMF that supports Ranging/Sidelink Positioning) and sends an Nlmf_Location_DetermineLocation service operation towards the LMF with the information received at step 5 e.g. required location results (e.g. relative locations i.e. distances and directions between pairs of UEs velocities and relative velocities), SL reference UE(s) in case of relative locations, Located UE(s) in the case of absolute location, Application layer IDs of the UEs if received in step 5 and whether UE1 supports RSPP. The service operation includes a LCS Correlation identifier. The AMF may include its stored sidelink positioning capabilities of UE1 provided in step 17.
10. The LMF sends an SL-MT-LR request to the serving AMF as a supplementary services message, using the Namf_Communication_N1N2MessageTransfer service operation, and the session ID parameter is set to the LCS Correlation identifier.
The SL-MT-LR request may include the Application Layer IDs of the other UEs 2 to n, the types of required location results (e.g. relative locations or distances and/or directions) and SL reference UE(s) in the case of relative locations.
The SL-MT-LR request may include the Application Layer IDs of the other UEs 2 to n, the types of required location results (absolute location), Located UE(s) and Coordinate ID in the case of absolute locations.
11. The serving AMF forwards the SL-MT-LR request and a Routing identifier equal to the LCS Correlation identifier to UE1 using a DL NAS TRANSPORT message.
12. UE1 attempts to discover the other UE 2 to n using their Application Layer IDs, if not already discovered using procedure defined in clause 6.4 of TS 23.586 [40].
13. UE1 obtains the required sidelink positioning capabilities of the discovered UEs via SLPP if not already obtained.
14. UE1 returns a supplementary services SL-MT-LR response to the serving AMF in an UL NAS TRANSPORT message and includes the Routing identifier received in step 11. Supplementary services message may include embedded SLPP message(s) which contain UEs' Ranging capabilities and the correlated Application Layer ID(s).
The SL-MT-LR response indicates which of UEs 2 to n have been discovered and the sidelink positioning capabilities of the discovered UEs.
15. The serving AMF forwards the SL-MT-LR response to the LMF indicated by the Routing identifier received at step 14 and includes a LCS Correlation identifier equal to the Routing identifier.
16. Ranging/Sidelink Positioning of UE1 and the other discovered UEs occurs as for an SL-MO-LR as described for steps 12-20 of clause 6.20.1 with the difference that Ranging/Sidelink Positioning location measurement data or results are always returned to the LMF and the LMF indicates to UE1 at step 15 of clause 6.20.1 whether the Ranging/Sidelink Positioning location results will be calculated by the LMF (at step 20) or by UE1 (at step 18).
For the undiscovered UEs or UEs for which the Ranging/Sidelink Positioning location measurements cannot be obtained based on their sidelink positioning capabilities among the other UEs 2 to n, the LMF may interact with GMLC to initiate the 5GC-MT-LR procedure using Application Layer ID for UE2 to n to get their absolute locations. In order to calculate the relative locations or distances and/or directions between UE1 and these UEs, if the absolute location of UE1 is not known yet, the LMF will trigger the 5GC-MT-LR procedure to derive the location of UE1. The LMF uses the absolute locations of all the UEs to calculate the relative locations or distances and/or directions between the pairs of these UEs. LMF may determine the Ranging/Sidelink Positioning location results in local coordinate if Coordinate ID is received in step 9.
To fulfil the required QoS, the LMF may determine to use both Ranging/SL Positioning and Uu absolute Positioning to obtain the location results.
17-20. The LMF returns the Ranging/Sidelink positioning location results via AMF and GMLC to the LCS Client or AF as in steps 13-15 and step 24 of clause 6.1.2. The LMF result may also include the UE1's sidelink positioning capabilities if the capabilities are received in step 15 including an indication that the capabilities are non-variable and not received from the AMF in step 9. The results also include failure information of the UE(s) that was not discovered or the requested information was not possible to derive.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 of n UEs (n≥2), i.e. UE1, UE2, ..., UEn either periodically or when certain trigger events occur.
Figure 6.20.4-1: Periodic and Triggered SL-MT-LR Procedure
In this figure, the SLPP messages between UE 2 to n and LMF are forwarded by UE1 to the LMF or sent by the LMF to UE1 in the embedded SLPP message(s) in the supplementary services request/response.
The following additions apply compared to the procedure in clause 6.20.3:
1. The LCS service request further includes periodic or trigger event parameters. For periodic location, the LCS Service Request includes the time interval between successive location reports and the total number of reports. For triggered location. the LCS Service Request includes details of the trigger event, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location results shall be included in event reports, and whether only one location report is required or more than one. Trigger events can be one of the following;
- ranging event with distance threshold and threshold type (a, b, c or d): a trigger event occurs if the distances between at least one UE of the n UEs and each of the other UEs are such that any distance for the one UE is less than the threshold (type a), any distance for the one UE exceeds the threshold (type b), all distances for the one UE are less than the threshold (type c), or all distances for the one UE exceed the threshold (type d).
4. In the message sent by (H)GMLC, 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 24-31 defined for periodic and triggered SL-MT-LR procedure only. The LDR reference number is either allocated by (H-)GMLC based on predefined rule or allocated by NEF, if the location request is sent by an NEF at step 1.
5. The message Namf_Location_ProvidePositioningInfo service operation towards the AMF is to request periodic or triggered Ranging/Sidelink positioning location results of the n UEs. The service operation further includes the periodic or trigger event parameters and other attributes as received or determined in steps 1 and 4.
NOTE 1: The location request is sent to one VGMLC at step 4 for roaming and to one AMF at step 5, which is the serving AMF for UE1.
10. The LMF sends a supplementary services Periodic-Triggered SL-MT-LR request to the serving AMF. The LCS Periodic-Triggered SL-MT-LR request further 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 SL-MT-LR request may include the QoS and allowed or required location results at step 24 for each location event reported. The LCS Periodic-Triggered SL-MT-LR request also includes the Application Layer IDs of UEs 2 to n, the address for the (H)GMLC and LDR reference number. The requested location results (e.g. absolute locations, relative locations, distances, directions, velocities and relative velocities) for the target UE and QoS.
11. The SL-MT-LR request from AMF is Periodic-Triggered, and the Routing identifier is immediate Routing identifier.
NOTE 2: 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 steps 24 and 25. The immediate routing identifier included by the AMF in step 11 is used for routing in steps 14 and 15.
14. The SL-MT-LR response from UE1 is Periodic-Triggered, and Routing identifier is immediate Routing identifier. The supplementary services Periodic-Triggered SL-MT-LR response indicates whether UE1 and other UEs 2 to n accept the periodic or triggered location request and which of UEs 2 to n were discovered by UE1 at step 12.
15. The SL-MT-LR response forwarded by AMF is Periodic-Triggered, and Correlation identifier is immediate Routing identifier.
NOTE 3: Step 16 in clause 6.20.3 enables the LMF to obtain the capabilities and initial location results for the UEs 1 to n.
17-20. The Ranging/Sidelink positioning location results returned by LMF to LCS Client or AF is initial one.
The following additional steps are dedicated for Periodic and Triggered SL-MT-LR Procedure:
21. The UEs 1 to n periodically perform Ranging/Sidelink positioning in order to support steps 22 and 24.
NOTE 4: The UEs 1 to n may perform Ranging/Sidelink positioning at intervals of the maximum event sampling interval provided at step 1.
22. UE1 monitors for occurrence of the trigger or periodic event requested in step 11. For a trigger event, UE1 monitors the requested event at intervals equal to or less than the maximum event sampling interval. An event trigger is detected by UE1 when any of the following occur: (i) a requested non-periodic trigger 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 a non-periodic trigger event has expired.
23. UE1 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.
24. UE1 sends a supplementary services event report message to the serving AMF using the Namf_Communication_N1N2MessageTransfer service operation, and includes the deferred Routing ID received in step 11. The event report indicates the type of event being reported (e.g. whether a normal event or expiration of the maximum reporting interval) and may include location results obtained at step 21. UE1 also includes the (H)GMLC contact address, the LDR reference number, whether location results are to be reported and if so the location QoS in the event report.
25. The AMF forwards the event report to the LMF indicated by the deferred Routing ID received at step 24 and includes a Correlation ID equal to the deferred Routing ID.
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 UE1 and/or the duration of event reporting so far) and returns a supplementary services acknowledgment for the event report to the serving AMF using the Namf_Communication_N1N2MessageTransfer service operation, and a Correlation ID identifying the LMF. The acknowledgment may optionally include a new deferred routing identifier indicating a new serving LMF or a default (any) LMF.
27. The serving AMF forwards the event report Ack and an immediate Routing ID equal to the Correlation ID to UE1 using a DL NAS TRANSPORT message. If UE1 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, UE1 may re-send the report one or more times.
NOTE 5: 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 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.
28. If location results are needed for event reporting and not received at step 25, the LMF may instigate Ranging/Sidelink Positioning of UEs 1 to n as at step 16.
29-31. The LMF returns the event report and any location results obtained at step 25 or step 28 to the LCS Client or AF as in steps 28-30 of clause 6.3.1.
32. UEs 1 to n continue to periodically perform Ranging/Sidelink positioning as in step 21.
33. UE1 continues to monitor for further periodic or trigger events as in step 22 and instigates steps 23-31 each time a periodic or trigger event is detected.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 request cannot fulfil the required QoS.
Procedure of Figure 6.1.2-1 can be reused, with the following adaptations:
- In step 10 of Figure 6.1.2-1, the AMF may take the UE's Ranging/Sidelink Positioning capability into account for LMF selection.
- In step 11 of Figure 6.1.2-1, the AMF provides the UE's Ranging/Sidelink Positioning capability to LMF.
- Step 12 of Figure 6.1.2-1 replaced by the step 10-16 of Figure 6.20.3-1 with the following adaptations:
- UE1 is the Target UE, and UEs 2 to n are Located UEs.
- In step 10, the type of required location results is absolute location, and the other UEs 2 to n are the candidate Located UE(s) if included. After LMF determines that the assistance of Located UE is needed for Target UE Positioning, LMF decides that Target UE or LMF selects Located UE, and SL-MT-LR request also includes the indication of Target UE/LMF selecting Located UE. LMF includes capabilities of each candidate Located UE in the request, if available, when Target UE selecting Located UE is indicated.
- In step 14, if UE1 receives the indication of LMF selecting Located UE in step 11, SL-MT-LR response includes the obtained information of all the discovered Located UEs. LMF performs the Located UE selection based on the obtained information of all the discovered Located UEs, and sends Application Layer ID of the selected Located UEs to the UE1 in step 16. If UE1 receives the indication of Target UE selecting Located UE in SL-MT-LR request, UE1 performs the Located UE selection, and SL-MT-LR response includes Application Layer ID of the selected Located UEs.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.21 Procedure for NWDAF assistance to location services
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 retrieved by LMF.
Clause 6.21.3 describes the procedures of UE Mobility Analytics retrieved by AMF.
NOTE: In this release of specification, only AMF and LMF can be NF service consumers to NWDAF.
The procedure in Figure 6.21-1 can be used by a 5GC NF involved in 5GC location services to get optional assistance from NWDAF as shown below.
Figure 6.21-1: Procedure for NWDAF assistance to location services
1. The AMF may invoke Nlmf_Location_DeterminationLocation service operation towards the LMF to request the current location of the UE.
2. Assistance from NWDAF for location services may be requested from the LMF and/or AMF.
3. The LMF may trigger UE positioning.
4. The LMF may return the location estimate to AMF as specified in clause 8.3.2.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 has a trained supervised ML model for deriving Location Accuracy Analytics.
NOTE: To assist the determination of the positioning methods for the requested LCS accuracy with the LCS accuracy analytics, LMF may know the accuracy of the positioning method(s) and NLOS/LOS measurement indication if the positioning method is NR based.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 satellite access.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.22 Procedures of data collection for LMF-based AI/ML Positioning
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
6.22.2 Data Collection at LMF for the LMF-based AI/ML positioning based on UE measurements
|
The LMF may obtain input data from the UEs (including PRUs) for ML model training and performance monitoring for LMF-based AI/ML Positioning, and the input data include measurement data and locations of the UEs. The LMF-based AI/ML Positioning model is trained to perform UE positioning for UEs located in an area of interest that may expand over multiple TAs or cover multiple NG-RAN nodes.
Figure 6.22.2-1: Data collection by LMF for LMF-based AI/ML positioning based on UE measurements
1. The LMF decides to start data collection from UEs for the purpose to train an ML Model or perform model performance monitoring for LMF-based AI/ML Positioning. This may be based on an internal trigger in the LMF or a request from the NWDAF. The LMF invokes an Nnrf_NFDiscovery_Request service operation to an NRF to discover AMF(s) that served for the area of interest.
Editor's note: Whether the LMF will subscribe at NWDAF for Network Performance Analytics to decide when to trigger data collection is FFS.
2. The LMF subscribes to the AMF(s) to retrieve the list of SUPIs located in an area of interest and optionally the UE Positioning Capability for each UE using Namf_EventExposure_Subscriber request (Target of Event Reporting = "any UE", Event ID = "UEs in/out area of interest", [indication of requesting UE Positioning Capability]).
Editor's note: Whether and how to limit the number of UEs is FFS.
3. The AMF sends Namf_EventExposure_Subscriber response (list of SUPIs in the area of interest). If UE Positioning Capability is also requested in step 1, AMF includes UE Positioning Capability and optionally UE User Plane Positioning Capabilities, if available, for each UE in the response message sent to LMF.
4. The LMF checks whether each SUPI provided user consent for data collection with UDM using Nudm_SDM_Get including subscription data type "User consent". If user consent is not granted, the data collection for this SUPI stops here and no other steps for this SUPI are performed.
5. The LMF subscribes to UDM to notifications of changes on subscription data type "User consent" for this SUPI using Nudm_SDM_Subscribe. If user consent is not granted, no data collection for this SUPI will be performed.
The LMF further determines the UEs from the list of SUPIs that are received from AMF in step 3 for data collection based on e.g. UE Positioning Capability, UE User Plane Positioning Capabilities, the PRU information available in the LMF and operator's policy. The User consent check is not needed for data collection from PRU for model performance monitoring. The LMF may query the UE for UE Positioning Capability and optionally UE User Plane Positioning Capabilities if not received in step 3.
Editor's note: Further details on user consent for data collection for a specific purpose, e.g. for model training and/or model performance monitoring for LMF-based AI/ML Model positioning will be aligned with SA WG3.
6. For each UE where the user provides consent to data collection and the UE can support data collection, the LMF initiates a request for input data. The UE may reject the data collection request from the LMF (e.g. considering UE status, user's input). If the UE accepts data collection request, the UE may cancel the data collection later as defined in clause 6.3.4.
7. The UDM may notify the LMF on changes of user consent at any time after step 5, then the LMF checks if the user consent is not granted. If user consent was revoked for a UE for which data have been collected, the LMF performs step 8. The LMF may unsubscribe to be notified of user consent updates from UDM for each SUPI for which data consent has been revoked.
8. The LMF stops any collection of data from the UE.
Editor's note: The procedure to collect the input data for AI/ML based positioning calculation by the LMF from the UE is FFS. The procedure will be coordinated with RAN WGs.
Editor's note: The input data used for AI/ML based positioning will be decided by RAN WGs.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 Model for UE positioning for a number of UEs or to monitor the ML Model performance. The LMF may also initiate the data collection upon the request of an NWDAF containing MTLF as described in step 3 in figure 6.22.4-1.
2. The LMF may know the SUPIs of the UEs for which to collect location measurement data from the NG-RAN, e.g. when training an ML model using the PRU(s) associated to this LMF. The LMF may optionally invoke an Nnrf_NFDiscovery Request service operation to an NRF to discover other PRU serving LMF(s) which has associated PRUs in the area of interest and send an Nlmf_Location_MeasurementData Request service operation to the selected PRU serving LMFs to collect the measurement data from the NG-RAN for the PRUs and the PRU locations.
If the LMF does not know the SUPIs of the UEs for which to collect location measurement data from the NG-RAN, the LMF tries to get the list of SUPIs from the AMF. Before that the LMF discovers the AMF(s) that serves the area of interest via the NRF using Nnrf_NFDiscoveryRequest.
3. The LMF subscribes to the list of SUPIs in an area of interest from the AMF(s) using Namf_EventExposure_Subscribe request (Target of Event Reporting = "any UE", Event ID = "UEs in/out area of interest").
The AMF sends Namf_EventExposure_Subscribe response or Namf_EventExposure_Notify (list of SUPIs in the area of interest).
For each SUPI in the area of interest, the following steps are performed.
4. The LMF checks whether the SUPI provided user consent for data collection for a purpose with UDM using Nudm_SDM_Get including subscription data type set to "User consent" for this SUPI.
5. The LMF subscribes to UDM to notifications of changes on subscription data type "User consent" for this SUPI using Nudm_SDM_Subscribe. If user consent is provided, then step 6 follows, otherwise no data is collected for this SUPI, i.e. Steps 6 to step 9 are not performed.
Editor's note: Further details on user consent for data collection for a specific purpose, e.g. for model training and/or for performance monitoring for LMF-based AI/ML positioning will be aligned with SA WG3.
6. The LMF requests input data for the UE from the NG-RAN.
7. The LMF requests ground truth data from the UE.
8. The LMF may determine that the UE is no longer in the area of interest, based on the AMF notification using Namf_EventExposure service, then the LMF performs step 10 and step 11, the LMF may unsubscribe to be notified on user consent updates if the UE is not in the area of interest any longer.
9. The UDM may notify the LMF on changes of user consent at any time after step 5 using Nudm_SDM_Notification including SUPI and Subscription data type set to "User consent". If user consent is no longer granted for a user for which data has been collected the LMF performs step 10 and step 11. The LMF may unsubscribe to be notified of user consent updates from UDM for each SUPI for which data consent has been revoked, using Nudm_SDM_Unsubscribe including SUPI and Subscription data type set to "User consent".
10. The LMF request NG-RAN to stop reporting input data for the target UE.
11. The LMF stop any retrieval of ground truth data from the UE.
The measurements and ground truth data are used for ML model training. The UE location is derived from the measurements data by using LMF-based AI/ML Positioning. The derived UE location and ground truth data are used for ML model performance monitoring.
The LMF may initiate data collection for multiple UEs simultaneously, as such steps 6 and 7 may occur in parallel for a number of SUPIs as determined by the LMF.
Editor's note: The procedure to collect the input data for AI/ML based positioning calculation by the LMF from the NG-RAN is subject to RAN WG progress and feedback.
Editor's note: Whether and how the LMF takes the RAN load into account in this procedure is FFS.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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) 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 train a ML model for LMF-based AI/ML Positioning based on the request from LMF or internal trigger, or the NWDAF containing MTLF determines to perform ML model performance monitoring for LMF-based AI/ML Positioning.
2. The NWDAF invokes an Nnrf_NFDiscovery_Request service operation to an NRF to discover an LMF, the service operation includes an AoI and the Nlmf_DataExposure service as discovery parameters. If the NWDAF wants to collect the input data of PRUs, the NWDAF may also include a PRU existence indication for discovering the LMF(s) associated with PRUs (the PRU association procedures are defined in clause 6.17). The NRF selects one or more LMFs based on the AoI, the Nlmf_DataExposure service, and the PRU existence indication (if available), and sends an Nnrf_NFDiscovery_Request Response which includes the profiles of the selected LMFs to the NWDAF.
Editor's note: The input data used for LMF-based AI/ML Positioning will be decided by RAN WGs.
3. The NWDAF subscribes to or cancels subscription to input data from LMF by invoking Nlmf_DataExposure_Subscribe / Nlmf_DataExposure_UnSubscribe service operation. The NWDAF includes an AoI and a notification target address to request the input data from LMF. The NWDAF may also include requested number of data samples, time window of data samples, quality threshold, ML model identifier (for ML model performance monitoring), data source type (UE or NG-RAN). The quality threshold indicates to the LMF to provide ground truth data only when the ground truth data meets the quality threshold. The detailed parameters are defined in clause 8.3.4.
NOTE: If the quality threshold is included in step 3 and the collected data sample does not include quality indicator of the ground truth data, the LMF does not send this data sample to the NWDAF.
4. For ML model training and ML model performance monitoring, the LMF performs the procedure for data collection in clause 6.22.2 and/or clause 6.22.3 to collect data from PRUs/UEs and/or the NG-RAN. For ML model performance monitoring, the LMF may also calculate the location estimation of PRU(s)/UE(s) using the collected data and the ML model identified by the ML model identifier if received in step 3.
5. The LMF sends the collected data samples (i.e. location measurement data from PRUs/UEs and/or the NG-RAN, the corresponding ground truth data (i.e. location of PRUs or UEs) and the quality indicator of the ground truth data) to the NWDAF by invoking Nlmf_DataExposure_Notify service operation. The LMF may send a cause code to the NWDAF when the requested number of data samples cannot be met. The LMF may also send the location estimation of PRU(s)/UE(s) calculated in step 4 (if applicable). Then the NWDAF trains the ML model or performs ML model performance monitoring based on the data samples received from the LMF.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 on local policy.
2. The LMF discovers an NWDAF that can provide trained ML model(s) for LMF-based AI/ML positioning, by invoking the Nnrf_NFdiscovery_Request service operation including parameters as specified in clause 5.18.
3. The LMF receives from the NRF a list of candidates NWDAF instances that match the attributes provided in the Nnrf_NFDiscovery_Request, as specified in clause 5.2.7.3 of TS 23.502 [3].
4. The LMF selects a NWDAF out of the list of candidates NWDAF instances, and then requests trained ML Model(s) using Nnwdaf_MLModelInfo_Request or Nnwdaf_MLModelProvision_Subscribe including parameters as described in clause 5.18.
5. The NWDAF provides one or more trained ML Models for LMF-based AI/ML positioning to the LMF including parameters as described in clause 5.18. If the LMF receives ADRF (Set) ID in the ML Model Information, the LMF may retrieve the ML Model from ADRF as described in clause 6.2B.7 of TS 23.288 [37].
6. If the LMF subscribes to receive trained ML Model(s) for LMF-based AI/ML positioning from the NWDAF in step 4, the NWDAF provides information of either a new trained or the re-trained ML model including parameters as described in clause 5.18 to the LMF by invoking Nnwdaf_MLModelProvision_Notify service operation .
7. Based on the information of either a new trained or the re-trained ML model provided in step 6 by the NWDAF, the LMF may update the trained ML Model(s) accordingly.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
7 Information storage
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 of each LCS privacy profile data type and included data, refer to clause 5.4.2.
Table 7.1-1: LCS privacy profile data stored in the UDM for a UE Subscriber
Privacy Profile Data Type
Presence
UDM data
Location Privacy Indication
M
O
Indication of one of the following mutually exclusive global settings:
- Location is disallowed.
- Location is allowed (default).
Time period when the Location Privacy Indication is valid.
Call/session Unrelated Class
M
O
O
O
O
O
O
O
O
O
O
O
O
O
For any LCS client or AF not in the external LCS client list or otherwise identified for the Call/session Unrelated Class, the following data may be present:
- One of the following mutually exclusive options:
- Location not allowed (default case)
- 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.
- Time period when positioning is allowed.
- Geographical area where positioning is allowed.
- Indication that codeword shall be checked in UE or one or more codeword values to be checked in GMLC.
External LCS client list: a list of zero or more LCS clients, AFs and LCS Client groups with the following data for each entry:
- One of the following mutually exclusive options:
- Location allowed without notification (default case).
- 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
- Time period when positioning is allowed
- Geographical area where positioning is allowed
Service types list: a list of one or more service types for which the LCS client is allowed to locate the particular UE. The possible service types are defined in TS 22.071 [2]. The following data may be present for each service type in the list:
- One of the following mutually exclusive options:
- Location allowed without notification (default case)
- 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.
- Time period when positioning is allowed.
- Geographical area where positioning is allowed.
- Indication that codeword shall be checked in UE or one or more codeword values to be checked in GMLC.
PLMN Operator Class
O
LCS client list: a list of one or more generic classes of LCS client that are allowed to locate the particular UE. The following classes are distinguished:
- LCS client broadcasting location related information.
- O&M LCS client in the HPLMN.
- O&M LCS client in the VPLMN.
- LCS client recording anonymous location information.
- LCS Client supporting a bearer service, teleservice or supplementary service to the target UE.
- NWDAF in the HPLMN (when the UE is currently being served by the HPLMN).
- NWDAF in the VPLMN.
User Plane Connection between UE and LCS Client or AF
O
Indication of one of the following mutually exclusive global settings:
- UE is allowed to report periodic or triggered location events via user plane to an LCS Client or AF
- UE is not allowed to report periodic or triggered location events via user plane to an LCS Client or AF (default).
Event report expected area
O
Presents a geographical area generated by UE, which is used by GMLC to determine event report allowed area for the UE.
Area usage indication
O
Indication of one of the following mutually exclusive global settings on using event report allowed area:
- Inside reporting (default).
- Outside reporting.
GMLC address list
O
Addresses of GMLC located in local network(s) which are allowed to be used for the UE positioning. The GMLC address is used to identify the local network for verification of location service in PNI-NPN.
The Mobile Originating data is defined in table 7.1-2 containing the LCS MO-LR services that a UE can receive.
Table 7.1-2: LCS Mobile Originated data for a UE Subscriber
MO-LR Data
Presence
UDM data
Mobile Originated data
M
List of MO-LR services allowed for a UE subscriber:
- Basic Self Location (UE can receive its own location).
- Autonomous Self Location (UE can receive location assistance data).
- Transfer to Third Party.
List of Assistance Data Types for MO-LR
O
A list of one or more types of location assistance data that may be provided to the UE in the MO-LR procedure.
The LCS broadcasting data is defined in table 7.1-3 containing a list of assistance data types for which ciphering keys should be provided to the UE if requested by the UE.
Table 7.1-3: LCS broadcasting data for a UE subscriber
Broadcasting Data
Presence
Description
List of Assistance Data Types
O
A list of one or more types of location assistance data for which ciphering keys should be provided to the UE if requested by the UE when the assistance data is broadcast using ciphering.
Other UE LCS subscriber data is defined in table 7.1-4 containing UE's subscription data related with LCS.
Table 7.1-4: UE LCS subscriber data
UE LCS subscriber data
Presence
Description
PRU indication
O
When present, it is used to indicate that the UE is allowed to serve as a PRU.
LPHAP indication
O
When present, it indicates a UE requires low power and high accuracy positioning.
LMF ID
O
An LMF ID which presents an LMF deployed in local network to support location service for the UE.
Indication of user plane positioning between UE and LMF
O
When present, it indicates that the UE is allowed to use the user plane positioning between UE and LMF.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
7.2 GMLC
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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
Description
LCS Client Type
M
Identifies the type of LCS client from among the following:
- Emergency Services
- Value Added Services
- PLMN Operator Services
- Lawful Intercept Services
External identifier
O
A list of one or more identifiers used to identify an external LCS client. The identifier may be used for a 5GC-MT-LR and/or 5GC-MO-LR. The format of the identifier is an international E.164 address, ITU-T Recommendation E.164 [23].
Authentication data
MO
Data employed to authenticate an external LCS client if the authentication is not done by a security gateway – details are outside the scope of the present document
Internal identifier
O
Identifies the sub-type of a PLMN operator services LCS Client from among the following:
- LCS client broadcasting location related information
- O&M LCS client in the HPLMN
- O&M LCS client in the VPLMN
- LCS client recording anonymous location information
- LCS Client supporting a bearer service, teleservice or supplementary service to the target UE
Client name
O
An address string which is associated with the LCS client's external identity (i.e. E.164 address).
Client name type
O
Indication of the type of the LCS client name. The type of the LCS client name can be one of the following:
- Logical name
- MSISDN
- E-mail address (RFC 2396 [25])
- URL (RFC 2396 [25])
- SIP URL (RFC 3261 [26])
- IMS public identity (1 23.228 [27])
- GPSI
Privacy Override Indication
O
Indication of whether the LCS client possesses the POI capability (only applicable to lawful intercept and emergency services clients)
Authorized UE List
O
A list of SUPIs and/or groups of SUPI for which the LCS client may issue a request for a 5GC-MT-LR for immediate or deferred location.
Priority
O
The priority of the LCS client
QoS parameters
M
The default QoS requirements for the LCS client, comprising:
- Accuracy
- Response time
- LCS QoS Class
Service Coverage
O
A list of E.164 country codes for geographic areas, ITU-T Recommendation E.164 [23] where the LCS client is permitted to request and receive UE location information.
Allowed LCS Request Types
M
Indicates which of the following are allowed:
- Request of current immediate location
- Request of current or last known immediate location
- Request of deferred location for the UE available event
- Request of deferred location for UE periodic events
- Request of deferred location for the Area Event
- Request of deferred location for the Motion Event
Local Co-ordinate System
O
Definition of the co-ordinate system(s) in which a location estimate shall be provided – details are outside the scope of the present document
Access Barring List(s)
O
List(s) of SUPIs or groups of SUPI for which a location request is barred
Service types
O
List of service type allowed for the LCS client.
Maximum Target UE Number
O
The maximum number of the Target UEs in one LCS request. For a specific LCS Client, this parameter may have different values for different service types.
User Plane location reporting
O
Indicates whether or not the LCS Client is allowed to request event reporting for a periodic or triggered MT-LR over user plane.
O
Default user plane address for event reporting over user plane.
O
Default security information for event reporting over user plane.
Correlated LMF ID
O
An LMF ID correlated with the LCS client, and/or
An LMF ID correlated with a group ID and the LCS client.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8 Network Function Services
| |
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.1 AMF Services
|
AMF services related to location service are defined in clause 5.2.2 of TS 23.502 [19].
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.2 UDM Services
|
UDM services related to location service are defined in clause 5.2.3 of TS 23.502 [19].
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.3 LMF Services
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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
LocationContextTransfer
Request/Response
LMF
MeasurementData
Request/Response
LMF
UPConfig
Request/Response
AMF
UPSubcribe
Subscribe/Notify
AMF
UPNotify
Subscribe/Notify
AMF
Nlmf_Broadcast
CipheringKeyData
Notify
AMF
Nlmf_DataExposure
Subscribe
Subscribe/Notify
NWDAF
Notify
Subscribe/Notify
NWDAF
UnSubscribe
Subscribe/Notify
NWDAF
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.3.2 Nlmf_Location service
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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/unsubscribe the geodetic and optionally local and/or civic location of a target UE for some certain events.
- 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.
- Allows the consumer NF to cancel location event reporting for a target UE.
- Allows the consumer NF to cancel a 5GC-MT-LR or 5GC-MO-LR during UE mobility from 5GS to EPS with N26 interface.
- Allows the consumer NF to transfer location context information for location event reporting for a target UE.
- Allows the consumer NF to request the PRU location measurement.
- Allows the consumer NF to request to set up, modify or terminate a secure LCS-UP connection for a target UE.
- Allows the consumer NF to get notified about status or modification of a secure LCS-UP connection for a target UE.
The events to trigger location estimation notification are defined in clause 4.1a.5.1
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 Identifier.
Input, Optional: Serving cell identifier 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 if the UE is using 3GPP access, required Location QoS instance(s), Supported GAD shapes, target UE identity (see clause 6.1.6.2.2, TS 29.572 [12]), service type, indication of requiring reliable UE location information, AMF identity if a UE associated Namf_Communication service is to be invoked by LMF, Type of request for a 5GC-MO-LR, Embedded LPP message(s) for a 5GC-MO-LR (1-3 messages), subscribed assistance data for a 5GC-MO-LR, Deferred location type, Deferred location parameters, indication if UE supports LPP or not, UE connectivity state per access type, Notification Target Address, Notification Correlation ID, indication of UE geographical area determination for PLMN selection verification, UE Positioning Capability, UE User Plane Positioning Capabilities (the user plane positioning using LCS-UPP and/or the user plane positioning using SUPL [49]), Ranging/Sidelink Positioning Capability, TNAPId (see TS 29.571 [33]), TWAPId (see TS 29.571 [33]), Scheduled Location Time, request for user plane reporting to an LCS Client or AF, user plane address of an LCS Client or AF, user plane security information for an LCS Client or AF, cumulative event report timer, maximum number of user plane event reports to an LCS Client or AF, event report allowed area, reporting indication, UE unaware indication, LPHAP indication, the serving cell identity belongs to a MBSR indication, the serving cell identity belongs to a MWAB indication, Additional ULI, Application layer IDs of the UEs for Ranging/Sidelink positioning.
Output, Required: Success/Failure indication
Output, Optional: Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, LOS/NLOS measurement indication, Position Methods Used (in the case of success indication provided), Serving LMF identification, Failure Cause (in the case of failure indication provided), achieved Location QoS Accuracy, UE geographical area where a PLMN is or is not allowed to operate, UE Positioning Capability, Ranging/Sidelink Positioning Capability, the timestamp of the Location, indication that the location determination will be sent directly to GMLC.
See clause 6.1, clause 6.2, clause 6.3.1, clause 6.9.1, clause 6.20.3 and clause 6.20.4 for examples of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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_DetermineLocation service operation or the cancellation of reporting of periodic or triggered location events.
Input, Required: Notification Correlation ID, UE (SUPI and if available GPSI).
Input, Optional: Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, LOS/NLOS measurement indication, Position Methods Used (in the case of success indication provided), Notification Target address, Serving LMF identification, Failure Cause (in the case of failure indication provided), achieved Location QoS Accuracy, the timestamp of the Location, Type of event (e.g. including a cumulative event report for events reported via user plane), statistics on events reported via a user plane since the last cumulative event report.
Output, Required: None.
Output, Optional: Success/Failure indication.
See clause 6.3.1 and clause 6.3.2 for examples of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 Correlation ID for deferred 5GC-MT-LR procedure cancellation. LCS Correlation ID for 5GC-MT-LR and 5GC-MO-LR procedures cancellation.
Input, Optional: None.
Output, Required: Success/Failure indication
Output, Optional: None.
See clause 6.3.3 for an example of usage of this service operation to cancel a deferred 5GC-MT-LR procedure for periodic or triggered location request. See clause 6.19.1.1 for an example of usage of this service operation to cancel 5GC-MT-LR and 5GC-MO-LR procedures during UE mobility from 5GS to EPS with N26 interface.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.3.2.5 Nlmf_Location_LocationContextTransfer service operation
|
Service operation name: Nlmf_Location_LocationContextTransfer
Description: Transfers location context information for location event reporting for a target UE from the consumer NF.
Input, Required: AMF identity, Location QoS, Supported GAD shapes, Deferred location type, Deferred location parameters, Notification Target Address, Notification Correlation ID, Embedded event report message.
Input, Optional: Event reporting status, UE location information, LOS/NLOS measurement indication, Indoor/Outdoor indication, UE Positioning Capabilities, Scheduled Location Time, the timestamp of the Location, request for user plane reporting to an LCS Client or AF, cumulative event report timer, maximum number of user plane event reports to an LCS Client or AF.
Output, Required: Success/Failure indication
Output, Optional: None.
See clause 6.4 for an example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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.
NOTE: The time window(s) is the Time Window Information SRS List and the Time Window Information Measurement List specified in TS 38.455 [15] when network assisted positioning is used and is the NR-DL-PRS-MeasurementTimeWindowsConfig specified in TS 37.355 [20] when UE assisted positioning is used.
Output, Required: PRU location measurement(s) and associated PRU known location.
Output, Optional: None.
See clause 6.17 for an example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 (GPSI, SUPI).
Input, Optional: AMF reallocation indication, LCS-UP connection termination indication, LCS-UP connection set up request indication, Target LMF identifier.
Output, Required: Success/Failure indication
Output, Optional: Failure Cause (in the case of failure indication provided).
See clauses 6.18.2 and 6.18.3 for an example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 and if available GPSI).
Input, Optional: None.
Outputs, Required: Subscription Correlation ID.
Outputs, Optional: None.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 identifier (only applicable in case of move of the connection).
Output, Required: None.
Output, Optional: None.
See clauses 6.18.1 and 6.18.3 for an example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.3.3 Nlmf_Broadcast service
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 ciphering key notification are defined in clause 6.14.2.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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: set of applicable tracking areas.
Output, Required: For each ciphering key: ciphering key identifier, success/failure indication.
Output, Optional: none.
See clause 6.14.2 for an example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.3.4 Nlmf_DataExposure service
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 identifier (applicable for ML model performance monitoring), data source type, Time window of data samples (indicating that only data samples that have been collected in the specified time interval are required), requested number of data samples, quality threshold, Subscription Correlation ID (in the case of modification of the subscription), Expiry time.
Outputs Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription). When the subscription is not accepted, an error response.
Outputs, Optional: None.
When the requested number of data samples has been provided or the time window of data samples has elapsed, the subscription is automatically terminated.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 measurement data) from PRUs/UEs or the NG-RAN, Ground truth data (i.e. location of PRUs or UEs) and the corresponding quality indicator of the ground truth data), ML model identifier (applicable for ML model performance monitoring), location estimation of PRU(s)/UE(s) (applicable for ML model performance monitoring), Subscription Correlation ID (this parameter shall be present if the notification is for informing the assignment of a new Subscription Correlation ID by the LMF), cause code.
Editor's note: The data samples used for LMF-based AI/ML Positioning will be decided by RAN WGs.
Output, Required: Operation execution result indication.
Output, Optional: None.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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: Operation execution result indication.
Output, Optional: None.
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.4 GMLC Services
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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
LocationUpdateNotify
Notify
NEF, NWDAF
CancellLocation
Request / Response
GMLC, NEF, NWDAF
EventNotify
Notify
GMLC, NEF, NWDAF
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.4.2 Ngmlc_Location service
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 location of a target UE.
- Allow the consumer NF to subscribe/unsubscribe the geodetic and optionally local and/or civic location of a target UE for some certain events.
- Allow the consumer NF to cancel an on-going periodic or triggered location request of a target UE.
- 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.
- Allow the consumer NF to request the relative locations, distance, or direction between UEs.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 GMLC, this service operation is used to implicitly subscribe to the notification of UE location information
Input, Required: UE identifier (GPSI, SUPI, Application layer ID of the UEs for Ranging/Sidelink positioning, Internal Group Identifier or External Group Identifier), Client Type.
Input, Optional: Required QoS instance(s), Supported GAD shapes, UE privacy requirements, LCS Client Identification, Service type, indication of requiring reliable UE location information, Notification Target Address, Notification Correlation ID, Event Type (defined in clause 4.1a.5.1), Scheduled Location Time, request for user plane reporting to an LCS Client or AF, user plane address of an LCS Client or AF, user plane security information for an LCS Client or AF, cumulative event report timer, maximum number of user plane event reports to an LCS Client or AF, event report expected area, reporting indication, LPHAP indication, MWAB indication and:
- For periodic event type, optional input further includes the time interval between successive location reports, the total number of reports, location QoS.
- For area event type, optional input further includes target geographical area(s) with optionally associated required QoS instance, 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 and associated location QoS shall be included in event reports, and whether only one location report is required or more than one.
- For motion event type, optional input further 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 and associated location QoS shall be included in event reports, and whether only one location report is required or more than one.
- For ranging and Sidelink positioning, input further includes related UE identifiers for Located UEs or SL Reference UEs (GPSI, Application layer ID), requested location type (absolute locations, relative locations or distances and/or directions related to the UEs, velocities and relative velocities), Local Co-ordinate or Global Co-ordinate, and Coordinate ID.
Output, Required: Success/Failure indication
Output, Optional: Geodetic location, Local Location including Coordinate ID, civic location, age of location, Indoor/Outdoor indication, LOS/NLOS measurement indication, position methods used (in the case of success indication provided), failure cause (in the case of failure indication provided), achieved Location QoS Accuracy, the timestamp of the Location, Ranging result.
See clauses 6.3.1 and 6.8 for examples of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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: pseudonym indicator, identity of the LCS client, identity of the AF, GMLC address, service type specified by UE, the timestamp of the location estimate.
Output, Required: Success/Failure indication
Output, Optional: Failure Cause (in the case of failure indication provided).
See clause 6.2 for example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 operation, or the cancellation of reporting of periodic or triggered location events, are detected or at bulk reporting of location.
Input, Required: Notification Correlation ID, UE (SUPI and if available GPSI), Type of location related event (e.g. deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location, cumulative event report for events reported via user plane).
Input, Optional: Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, LOS/NLOS measurement indication, Position Methods Used (in the case of success indication provided), Failure Cause (in the case of failure indication provided), address of a new AMF or MME, achieved Location QoS Accuracy, the timestamp of the Location, statistics on events reported since the last cumulative event report.
Output, Required: None.
Output, Optional: None.
See clauses 6.3 and 6.8 for examples of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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.
Output, Required: None.
Output, Optional: None.
See clause 6.3.3 for example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 class.
Input, Optional: Service identity (mapped from service type by HGMLC), the timestamp of the location estimate.
Output, Required: Success/Failure indication.
Output, Optional: Failure Cause (in the case of failure indication provided).
See clause 6.2 for example of usage of this service operation.
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 (Application Layer ID, GPSI).
Output, Optional: Failure Cause (in the case of failure indication provided).
|
f07a33accd7fdb2aa929bcb3619e29df
|
23.273
|
8.4.2.8 Void
| |
f07a33accd7fdb2aa929bcb3619e29df
|
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 request and response are listed in clause 5.5.
For 5GC-MO-LR procedure, if UE requests to report its location to AF, the location reporting is supported by Nnef_Location_LocationUpdateNotify service operation defined in clause 5.2.6.21 of TS 23.502 [19].
|
f07a33accd7fdb2aa929bcb3619e29df
|
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 those applicable to a UE with EPS access in the case of TS 23.271 [4] and do not include all differences applicable to GERAN or UTRAN access. A.1 Differences in Parameters for a Location Request Table A.1-1 shows a list of parameters applicable to a location request sent by an external LCS client to a GMLC which are defined in TS 23.271 [4], differences if any with this TS, and comments on these including any significant consequences. Table A.1-1: Differences in Parameters for a Location Request with TS 23.271 [4] Location Request Parameter Difference Comments Target UE Identity GPSI, SUPI or pseudonym in this TS MSISDN, IMSI or pseudonym in TS 23.271 [4] LCS QoS None Supported GAD shapes None LCS Client type None Called Party Number Not supported in this TS If provided, this parameter should be ignored by a GMLC APN NI Not supported in this TS If provided, this parameter should be ignored by a GMLC Service Identity None Codeword None Service coverage information None Requestor Identity Not supported in this TS If provided, this parameter should be ignored by a GMLC Type of Requestor Identity Not supported in this TS If provided, this parameter should be ignored by a GMLC Type of a deferred location request None Periodic Location parameters None Area Event parameters None Motion Event parameters None A.2 Differences in Information Storage in the UDR/UDM versus HSS/GMLC for EPS Table A.2-1 shows a list of LCS information storage items for a UE in the UDR and UDM defined in this TS and for the HSS and/or GMLC defined in TS 23.271 [4], differences if any between this TS and TS 23.271 [4], and comments on these including any significant consequences. Table A.2-1: Differences in Information Storage for a UE in the UDR/UDM versus HSS/GMLC for EPS Information Storage Item(s) Difference Comments UE Privacy Universal Class Not supported in this TS This privacy class should not be supported for 5GC capable UEs on the EPS side to avoid differences in LCS privacy support between EPS access and 5GS access for the same UE. (Note 1) UE Location Privacy Indication Not supported in TS 23.271 [4] This indication can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) UE Privacy Call/Session related Class Not supported in this TS This privacy class should not be supported for 5GC capable UEs on the EPS side to avoid differences in LCS privacy support between EPS access and 5GS access for the same UE. (Note 1) UE Privacy Call/Session unrelated Class Supported as defined in TS 23.271 [4] with the following differences: - Information related to an RGMLC is not included - An optional time period is not supported in TS 23.271 [4] - An optional geographic area is not supported in TS 23.271 [4] This privacy class can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) UE Privacy PLMN Operator Class None UE LCS Mobile Originating Data None NOTE 1: A PLMN operator can avoid any difference in UE privacy support for EPS access versus 5GS access by only storing information for UE privacy (in the UE LCS privacy profile) in a UDR (and UDM) and not in an HSS or GMLC. A.3 Differences in Information Storage in the GMLC Table A.3-1 shows a list of information storage items in the GMLC for an LCS Client defined in this TS and in TS 23.271 [4], differences if any between this TS and TS 23.271 [4], and comments on these including any significant consequences. Table A.3-1: Differences in Information Storage for an LCS Client in the GMLC Information Storage Item(s) Difference Comments LCS Client Type None LCS Client Type None External identity None Authentication data None Call/session related identity Not supported in this TS This information item can create differences between LCS client access to a UE which has 5GS access versus EPS access. (Note 1) Internal identity None Client name None Client name type No difference except that this TS adds a Client Name type in the form of a GPSI. A GPSI can be an MSISDN or External Identifier in the form of "username@realm" as defined in TS 23.003 [28]. TS 23.271 [4] allows an MSISDN but the External Identifier is not included. Override capability None Authorized UE List None Priority None QoS parameters None Service Coverage None Allowed LCS + Request Types TS 23.271 [4] includes the following items which are not in this TS: - Non-call related CS-MT-LR/PS-MT-LR/EPC-MT-LR - Call/session related CS-MT-LR/PS-MT-LR/EPC-MT-LR - Specification or negotiation of priority - Specification or negotiation of QoS parameters - Specification or negotiation of Service Coverage parameter This TS includes the following items which are not in TS 23.271 [4]: - Request of deferred location for the UE available event - Request of deferred location for UE periodic events - Request of deferred location for the Area Event - Request of deferred location for the Motion Event This TS should take precedence (Note 1) Local Co-ordinate System None Access Barring List(s) TS 23.271 [4] includes a list of MSISDNs. This TS includes a list of SUPIs This TS can take precedence (Note 1) Service Identities None Maximum Target UE Number None NOTE 1: A PLMN operator can avoid any difference in LCS Client support for a target UE with EPS access versus 5GS access by only storing information for an LCS Client in a GMLC as defined in this TS. A.4 Differences with TS 23.271 [4] on Privacy A.4.1 Differences in UE LCS Privacy Table A.4.1-1 shows a list of UE LCS privacy features defined in this specification and in TS 23.271 [4], differences if any between these, and comments on these including any significant consequences. Table A.4.1-1: Differences in UE LCS Privacy with TS 23.271 [4] UE LCS Privacy Feature Difference Comments Privacy Override Indicator (POI) None UE Privacy Universal Class Not supported in this TS This class allows a UE to subscribe to location by any LCS client. For such a UE, a 5GC GMLC will not support such location. Location Privacy Indication Not supported in TS 23.271 [4] As defined in clause 5.4.2.3. UE Privacy Call/Session related Class Not supported in this TS This class permits location by LCS clients to which the UE has established a PS session. A 5GC GMLC will not allow such location. However, the location can be allowed as part of the Call/Session unrelated class. UE Privacy Call/Session unrelated Class Supported as defined in TS 23.271 [4] with the following differences: An optional valid time period is added An optional valid geographic area is added The optional valid time period and valid geographic area allow more precise control of location reporting. For example, tracking of employees by an employer can be restricted to a work location and/or normal work hours. UE Privacy PLMN Operator Class Supported as defined in TS 23.271 [4] Annex B (informative): LCS privacy selection rule in serving NF B.1 LCS privacy selection flow rule A 5GS-MT-LR may be applied to more than one LCS privacy data in the LCS privacy profile, e.g. one or more privacy classes as defined in clause 5.4.2.2 and LPI as defined in clause 5.4.2.3. The 5GS-MT-LR may also require POI as defined in clause 5.4.4. The Privacy selection flow is shown in Figure B.1-1. Figure B.1-1: Privacy selection flow diagram Annex C (informative): PNI-NPN architecture to support location service with signalling optimisation Figure C-1 shows the PNI-NPN architecture to support location services with optimisation of signalling latency and privacy, with the corresponding functional descriptions are defined in clause 5.13. 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. Assuming NG-RAN 1 is the serving RAN of UE. NG-RAN 2 and NG-RAN 3 illustrated in the figure below is for positioning signal measurement. Figure C-1 PNI-NPN architecture to support location service with signalling optimisation Annex D (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2019-05 SP#84 SP-190455 - - - MCC Editorial update for presentation to TSG SA#84 for approval 1.0.0 2019-06 SP#84 - - - - MCC editorial update for publication after approval at TSG SA#84 16.0.0 2019-09 SP#85 SP-190606 0001 1 F Correction on UE Assisted and UE Based Positioning Procedure 16.1.0 2019-09 SP#85 SP-190606 0002 1 F Correction on LCS privacy selection flow rule 16.1.0 2019-09 SP#85 SP-190606 0003 - F Corrections to EPC Interconnection 16.1.0 2019-09 SP#85 SP-190606 0005 1 F Corrections to LCS Privacy feature 16.1.0 2019-09 SP#85 SP-190606 0006 3 B Support of Concurrent Location Request 16.1.0 2019-09 SP#85 SP-190606 0008 - F Clarification on positioning access selection in the 5GC-MO-LR procedure 16.1.0 2019-09 SP#85 SP-190606 0010 2 B Broadcast of Assistance Data for NR 16.1.0 2019-09 SP#85 SP-190606 0011 1 F Correction and Improvement of Low Power Periodic and Triggered Location 16.1.0 2019-09 SP#85 SP-190606 0021 1 F Handling of NG-RAN Location Service Exposure Procedure 16.1.0 2019-09 SP#85 SP-190606 0022 1 F 3GPP access specific aspects 16.1.0 2019-09 SP#85 SP-190606 0024 1 F Clarification of 5GC-MT-LR procedure for the commercial location service 16.1.0 2019-09 SP#85 SP-190606 0025 1 F Completion of 5GC-MO-LR Procedure for TS 23.273 16.1.0 2019-09 SP#85 SP-190606 0028 2 F Completion of Unified Location Service Exposure Procedure for TS 23.273 16.1.0 2019-09 SP#85 SP-190606 0030 2 F Clarification of CHF in eLCS architecture 16.1.0 2019-09 SP#85 SP-190606 0032 1 F IMS Interworking for location service 16.1.0 2019-09 SP#85 SP-190606 0036 1 F Update of location service exposure description 16.1.0 2019-12 SP#86 SP-191070 0033 3 F Package of corrections 16.2.0 2019-12 SP#86 SP-191070 0037 2 F Delete Editor's Notes 16.2.0 2019-12 SP#86 SP-191070 0041 F Update the status of event reporting 16.2.0 2019-12 SP#86 SP-191070 0045 - F Add Coordinate Reference System 16.2.0 2019-12 SP#86 SP-191070 0046 - F Corrections to bulk operation MT-LR procedure 16.2.0 2019-12 SP#86 SP-191070 0047 1 F Corrections to MT-LR procedure for 3GPP and Non-3GPP access 16.2.0 2019-12 SP#86 SP-191070 0048 2 F Removal of the EN on the location information in Clause 5.3.1 16.2.0 2019-12 SP#86 SP-191070 0049 2 F Correction on Broadcast of Assistance Data by an LMF 16.2.0 2019-12 SP#86 SP-191070 0055 1 F Completion of Deferred 5GC-MT-LR procedure for TS 23.273 16.2.0 2019-12 SP#86 SP-191070 0056 1 F Completion of 5GC-MT-LR Procedure for TS 23.273 16.2.0 2019-12 SP#86 SP-191070 0057 1 F Corrections to Location Services for Miscellaneous Errors and Inconsistencies 16.2.0 2019-12 SP#86 SP-191070 0059 - F Update of the LMF selection function 16.2.0 2019-12 SP#86 SP-191070 0060 2 F Correction of the procedure of obtaining Non-UE Associated Network Assistance Data 16.2.0 2019-12 SP#86 SP-191061 0061 1 F Corrections to MO-LR procedure 16.2.0 2019-12 SP#86 SP-191070 0062 1 F Corrections to LCS Assistance Data Broadcast procedure 16.2.0 2019-12 SP#86 SP-191070 0074 1 F Completion of Cancellation of a Deferred 5GC-MT-LR procedure for TS 23.273 16.2.0 2019-12 SP#86 SP-191070 0076 2 F Completion of Unified Location Service Exposure Procedure 16.2.0 2019-12 SP#86 SP-191070 0080 - F Addition of exception support for Periodic or Triggered Location Reporting 16.2.0 2020-03 SP#87E SP-200064 0070 2 F Package of editorial modification for procedures 16.3.0 2020-03 SP#87E SP-200064 0075 2 F Clarification on LCS QoS 16.3.0 2020-03 SP#87E SP-200064 0081 1 F Clarification on GMLC and NEF authorization and privacy check 16.3.0 2020-03 SP#87E SP-200064 0089 1 F Incorrect Services Operation for LMF non UE message transfer 16.3.0 2020-03 SP#87E SP-200064 0091 - F Corrections to LMF selection 16.3.0 2020-03 SP#87E SP-200064 0092 1 F TS23.273 - Correction on User Location Information 16.3.0 2020-03 SP#87E SP-200064 0095 1 F Clarification on group authorization and location reporting method for bulk operation 16.3.0 2020-03 SP#87E SP-200064 0103 1 F Complementing the function of EventNotify service operation 16.3.0 2020-03 SP#87E SP-200064 0105 1 F Correction to cancellation of reporting of location events procedure 16.3.0 2020-03 SP#87E SP-200064 0106 1 D Package of editorial modification 16.3.0 2020-03 SP#87E SP-200064 0107 1 F Correction to roaming architecture for NEF 16.3.0 2020-03 SP#87E SP-200064 0108 F Correction to LMF function 16.3.0 2020-03 SP#87E SP-200064 0111 1 F Correction to the service operation between AF and NEF 16.3.0 2020-03 SP#87E SP-200064 0112 1 F Update the functionality of GMLC 16.3.0 2020-03 SP#87E SP-200064 0113 1 F Update the Cancellation procedure of deferred MT-LR 16.3.0 2020-03 SP#87E SP-200064 0114 1 F Update the Response Method 16.3.0 2020-03 SP#87E SP-200064 0115 1 F Location Exposure 16.3.0 2020-07 SP#88E SP-200423 0116 1 F Correction to service exposure descriptions 16.4.0 2020-07 SP#88E SP-200423 0117 - F Correction to use of NEF Service operations in procedures 16.4.0 2020-07 SP#88E SP-200423 0119 1 F Clarification on MT-LR procedure 16.4.0 2020-07 SP#88E SP-200423 0120 1 F Add NEF function in location service exposure procedure 16.4.0 2020-07 SP#88E SP-200423 0121 1 F Location Exposure 16.4.0 2020-07 SP#88E SP-200423 0122 1 F Clarification on Information Elements in location procedure 16.4.0 2020-07 SP#88E SP-200423 0123 1 F Location QoS 16.4.0 2020-07 SP#88E SP-200423 0124 - F Resolve EN for NG-RAN Location Service Exposure 16.4.0 2020-07 SP#88E SP-200423 0125 1 F Clarification of several procedures 16.4.0 2020-07 SP#88E SP-200422 0126 - F Removal of I-NEF 16.4.0 2020-12 SP#90E SP-200948 0131 1 F Correction to Bulk Operation 16.5.0 2020-12 SP#90E SP-200948 0136 1 F Correction of NAS message used for event reporting 16.5.0 2021-03 SP#91E SP-210056 0140 - F Clarification on UDM interaction 16.6.0 2021-03 SP#91E SP-210056 0141 - F Correction on source of Client type information 16.6.0 2021-03 SP#91E SP-210056 0142 - F Correction of NEF service type in bulk operation procedure 16.6.0 2021-03 SP#91E SP-210056 0143 - F Correction to conveyed area event information 16.6.0 2021-03 SP#91E SP-210056 0153 1 F Clarification of LCS client type provided by AF 16.6.0 2021-03 SP#91E SP-210063 0144 1 C Location estimate in Local Coordinates 17.0.0 2021-03 SP#91E SP-210063 0145 - C Add MO-LR subscribed Assistance Data 17.0.0 2021-03 SP#91E SP-210063 0146 - C Clarification on requesting current location from AMF. 17.0.0 2021-03 SP#91E SP-210063 0157 - F Correction on Access Network 17.0.0 2021-03 SP#91E SP-210063 0159 1 C LMF Change Procedure 17.0.0 2021-06 SP#92E SP-210338 0150 4 C Support for Multiple QoS Class in deferred location requests 17.1.0 2021-06 SP#92E SP-210325 0161 1 F Assistance Data Delivery in 5G-MO-LR 17.1.0 2021-06 SP#92E SP-210338 0163 1 C Add a new procedure for unified location service exposure for NF in serving PLMN 17.1.0 2021-06 SP#92E SP-210338 0164 1 C Add the usage of the requested maximum age of location in the 5GC-MO-LR 17.1.0 2021-06 SP#92E SP-210338 0165 1 C Add local co-ordinate in procedures 17.1.0 2021-06 SP#92E SP-210338 0166 B Add definition and usage for 5G positioning area and 5G enhanced positioning area 17.1.0 2021-06 SP#92E SP-210338 0167 1 C Add description of GMLC corrects the area event report 17.1.0 2021-06 SP#92E SP-210338 0170 - F Correction the spec number for LPP protocol 17.1.0 2021-06 SP#92E SP-210338 0172 - F Add UE connectivity state per access type as the input of Nlmf_Location_DetermineLocation service 17.1.0 2021-06 SP#92E SP-210338 0174 1 C LMF Parameters Support for non-3GPP Access 17.1.0 2021-06 SP#92E SP-210338 0175 1 C Support for Area Decision of Satellite Access 17.1.0 2021-06 SP#92E SP-210338 0176 1 B UE positioning capability storage 17.1.0 2021-09 SP#93E SP-210913 0147 4 F Add time of position determination to Deferred MT-LR periodic 17.2.0 2021-09 SP#93E SP-210905 0182 - A Inconsistent Location Information for Non-3GPP Access 17.2.0 2021-09 SP#93E SP-210905 0184 1 A Clarify conveyance of Service type 17.2.0 2021-09 SP#93E SP-210913 0185 1 F Update LMF function and service operation 17.2.0 2021-09 SP#93E SP-210913 0186 1 F Update 5GC-NI-LR procedure 17.2.0 2021-09 SP#93E SP-210913 0187 1 B Introduction of the Scheduled Location Time 17.2.0 2021-09 SP#93E SP-210913 0192 1 F Satellite RAT Type in LMF selection 17.2.0 2021-12 SP#94E SP-211280 0151 6 B Addition of a Scheduled Location Time 17.3.0 2021-12 SP#94E SP-211273 0194 2 A Clarification on use of service type and service identity in MO-LR procedure 17.3.0 2021-12 SP#94E SP-211280 0196 1 F Add timestamp of location estimate 17.3.0 2021-12 SP#94E SP-211280 0200 1 F Store UE positioning capability in failed case 17.3.0 2021-12 SP#94E SP-211280 0201 - F Removal of Editor's Note concerning storage of UE Positioning Capabilities 17.3.0 2021-12 SP#94E SP-211280 0202 1 F Identification of Position Methods not able to support Local Coordinates 17.3.0 2021-12 SP#94E SP-211273 0204 - A Remove SUPI in response to Nudm_SDM 17.3.0 2021-12 SP#94E SP-211280 0206 1 F Editorial changes for eLCS_Ph2 17.3.0 2021-12 SP#94E SP-211273 0208 - A Correct the allowed access type for event report 17.3.0 2021-12 SP#94E SP-211280 0209 1 F Location Services applicable to SNPN(s) 17.3.0 2021-12 SP#94E SP-211273 0213 1 A Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event 17.3.0 2021-12 SP#94E SP-211273 0215 1 A Update MO-LR procedure 17.3.0 2021-12 SP#94E SP-211280 0218 1 F Update AMF functionality for satellite access UE 17.3.0 2021-12 SP#94E SP-211273 0220 1 A Removal of description that LMF ID is provided by UE 17.3.0 2022-03 SP#95E SP-220049 0222 - F Multiple QoS Class applicable procedure 17.4.0 2022-03 SP#95E SP-220049 0223 - F PLMN Operator Class applicable to SNPN 17.4.0 2022-03 SP#95E SP-220049 0225 1 F Update to Scheduled Location Time 17.4.0 2022-06 SP#96 SP-220392 0228 1 B Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state 17.5.0 2022-06 SP#96 SP-220391 0230 1 A Correction to the 5GC-MT-LR Procedure for the commercial location service 17.5.0 2022-09 SP#97E SP-220772 0231 1 F Clarification and correction on country verification for satellite access 17.6.0 2022-09 SP#97E SP-220772 0232 1 C Addition of GNSS integrity requirement to in the location request 17.6.0 2022-12 SP#98E SP-221064 0243 2 F Support an indication of reliable UE location information requirement 17.7.0 2022-12 SP#98E SP-221094 0237 1 B Multiple location report for MT-LR Immediate Location Request for the regulatory service 18.0.0 2022-12 SP#98E SP-221141 0240 3 B Support of Mobile Base Station Relay for Location Service 18.0.0 2022-12 SP#98E SP-221081 0242 2 B UE location reporting only when the UE locates in the target area defined with finer granularity 18.0.0 2022-12 SP#98E SP-221081 0246 2 B Support of User Plane Positioning 18.0.0 2022-12 SP#98E SP-221081 0247 - B Support of GNSS assistance data collection from AF 18.0.0 2022-12 SP#98E SP-221081 0249 2 B Privacy Check for NWDAF requesting UE location from GMLC 18.0.0 2022-12 SP#98E SP-221081 0251 1 B Support of UE Positioning without UE/User Awareness 18.0.0 2022-12 SP#98E SP-221081 0253 3 B Introduce new feature: support of LCS in PNI-NPN 18.0.0 2022-12 SP#98E SP-221081 0254 1 B Introduce new feature: local LMF and GMLC selection 18.0.0 2022-12 SP#98E SP-221081 0258 2 B Verification of location for NTN access 18.0.0 2022-12 SP#98E SP-221081 0264 1 B Support of a UE user plane connection to an LCS Client or AF for periodic or triggered 5GC-MT-LR event reporting 18.0.0 2023-03 SP#99 SP-230045 0244 9 B General description to support PRUs 18.1.0 2023-03 SP#99 SP-230045 0263 7 B Support of PRUs 18.1.0 2023-03 SP#99 SP-230045 0265 1 B PRU verification by AMF during PRU positioning 18.1.0 2023-03 SP#99 SP-230045 0269 1 B Enable additional check in target area in deferred area event 18.1.0 2023-03 SP#99 SP-230045 0271 4 B Enhance the Triggered Location for UE power saving purpose 18.1.0 2023-03 SP#99 SP-230045 0272 1 F Update LMF and GMLC service operations to support cumulative event report 18.1.0 2023-03 SP#99 SP-230045 0274 1 F Update LMF service operation to support UE unaware indication 18.1.0 2023-03 SP#99 SP-230045 0276 1 B Support of User Unaware Positioning 18.1.0 2023-03 SP#99 SP-230045 0283 6 B Introduce new feature: support of low power and high accuracy positioning 18.1.0 2023-03 SP#99 SP-230045 0284 5 C Positioning procedure update for PNI-NPN deployment 18.1.0 2023-03 SP#99 SP-230045 0285 - C Clarification on additional check for location events 18.1.0 2023-03 SP#99 SP-230045 0286 4 B introduce new feature: NWDAF assisted positioning 18.1.0 2023-03 SP#99 SP-230045 0287 1 C Procedure update with additional LCS NF discovery and selection method 18.1.0 2023-03 SP#99 SP-230078 0288 1 B MT-LR procedure for when a MBSR is involved in the location of a UE. 18.1.0 2023-03 SP#99 SP-230045 0289 1 F Clarification on LMF Discovery and Selection 18.1.0 2023-03 SP#99 SP-230045 0290 F Clarification on Location service in PNI-NPN 18.1.0 2023-03 SP#99 SP-230032 0294 1 A AMF instead of LMF for NI and HO correlation with GMLC 18.1.0 2023-03 SP#99 SP-230035 0296 - A Update of GNSS integrity requirement provisioning 18.1.0 2023-03 SP#99 SP-230074 0297 2 B Introduce Sidelink positioning procedure into LCS architecture 18.1.0 2023-03 SP#99 SP-230045 0298 4 B Adding NWDAF to LCS architecture 18.1.0 2023-03 SP#99 SP-230046 0304 1 F Clarification on Location service in PNI-NPN 18.1.0 2023-03 SP#99 SP-230046 0305 4 B Inclusion of NWDAF as GMLC services 18.1.0 2023-03 SP#99 SP-230046 0306 4 B NWDAF assisted LMF positioning method determination 18.1.0 2023-03 SP#99 SP-230046 0308 - B Clarification on establishment of LCS user plane connection 18.1.0 2023-03 SP#99 SP-230046 0310 2 B Procedures of positioning over the user plane connection between UE and LMF 18.1.0 2023-03 SP#99 SP-230046 0311 1 F Terminology clarification of eLCS_ph3 18.1.0 2023-03 SP#99 SP-230046 0312 1 F UE LCS subscriber data 18.1.0 2023-03 SP#99 SP-230046 0313 1 F Update AMF and UDM functionality description to support local LMF selection 18.1.0 2023-03 SP#99 SP-230046 0314 1 F Correct an editorial error 18.1.0 2023-03 SP#99 SP-230074 0320 1 B Support of Ranging and Sidelink Positioning 18.1.0 2023-03 SP#99 SP-230046 0323 2 C Update of Collection of GNSS assistance data 18.1.0 2023-03 SP#99 SP-230046 0325 2 B LCS User Plane Architecture and Interface 18.1.0 2023-03 SP#99 SP-230046 0327 2 B Location service bi-directional continuity between EPS and 5GS 18.1.0 2023-06 SP#100 SP-230485 0318 1 B Updates to LMF selection to suport Ranging/Sidelink Positioning 18.2.0 2023-06 SP#100 SP-230485 0321 11 B Support of MT-LR for Ranging and Sidelink Positioning 18.2.0 2023-06 SP#100 SP-230485 0322 10 B Ranging and Sidelink Positioning MO-LR procedure 18.2.0 2023-06 SP#100 SP-230445 0328 1 B Update PRU's NRF impact 18.2.0 2023-06 SP#100 SP-230445 0329 3 B Adding Positioning Procedure over LCS-UP 18.2.0 2023-06 SP#100 SP-230496 0334 - F Clarification on conditions for privacy check for MBSR 18.2.0 2023-06 SP#100 SP-230445 0335 4 B Resolve two ambiguous aspects of event report allowed area 18.2.0 2023-06 SP#100 SP-230445 0336 1 B The terminology replacing of power saving area 18.2.0 2023-06 SP#100 SP-230445 0337 1 B Clarifications on NWDAF assisting LCS 18.2.0 2023-06 SP#100 SP-230445 0338 7 B LCS services assisted by NWDAF analytics 18.2.0 2023-06 SP#100 SP-230496 0339 4 B Update of the Location Services involving Mobile Base Station Relay 18.2.0 2023-06 SP#100 SP-230445 0349 3 B Location service continuity between EPS and 5GS (bi-direction) for deferred MT-LR 18.2.0 2023-06 SP#100 SP-230445 0354 4 F Add new LMF service operations 18.2.0 2023-06 SP#100 SP-230445 0355 4 F Update the Architecture of Location Service for interconnection between 5GC and EPC 18.2.0 2023-06 SP#100 SP-230445 0356 1 F Update the Location Service Continuity between EPS and 5GS for Immediate Location Request 18.2.0 2023-06 SP#100 SP-230445 0357 1 F Remove the Editor's Notes 18.2.0 2023-06 SP#100 SP-230445 0364 3 C Resolve the EN on the session break out for local LMF service 18.2.0 2023-06 SP#100 SP-230445 0365 2 F Clarification on the low power or high accuracy positioning 18.2.0 2023-06 SP#100 SP-230445 0367 3 F Procedure update for multiple set of GNSS assistance data broadcast 18.2.0 2023-06 SP#100 SP-230445 0368 1 F Clarification of PRU UE using NR satellite access 18.2.0 2023-06 SP#100 SP-230446 0369 4 F Further clarification on the support of PRUs 18.2.0 2023-06 SP#100 SP-230446 0373 1 B Clarification of Missing LMF ID in AMF logic 18.2.0 2023-06 SP#100 SP-230446 0379 2 F Alignment of description for Routing identifier of LMF with RAN3 incoming LS 18.2.0 2023-06 SP#100 SP-230446 0380 3 B NLOS/LOS measurement indication 18.2.0 2023-06 SP#100 SP-230446 0381 1 B Update PRU related positioning procedure 18.2.0 2023-06 SP#100 SP-230446 0383 2 B LMF initiated User Plane Disconnection 18.2.0 2023-06 SP#100 SP-230465 0385 1 F Revisions on UE unaware positioning 18.2.0 2023-06 SP#100 SP-230446 0387 3 B Functional description update for UP positioning 18.2.0 2023-06 SP#100 SP-230446 0388 1 F Removal of functional description of inter-LMF GNSS assistance data transfer 18.2.0 2023-06 SP#100 SP-230446 0389 1 B Support of AMF reselection of LMF for user plane positioning 18.2.0 2023-06 SP#100 SP-230446 0392 2 C Clarification on user plane positioning determination 18.2.0 2023-06 SP#100 SP-230446 0393 3 B LCS User Plane EN removal and alignments 18.2.0 2023-06 SP#100 SP-230446 0394 3 B LCS Supplementary Service with UE verification 18.2.0 2023-09 SP#101 SP-230839 0402 1 F Fix Modification of User Plane Connection between UE and LMF 18.3.0 2023-09 SP#101 SP-230839 0403 1 F Fix Missing Interface between LMF and GMLC 18.3.0 2023-09 SP#101 SP-230839 0406 2 F Clarification on the UE user plane Positioning capability 18.3.0 2023-09 SP#101 SP-230839 0407 2 F Clarification on the Nlmf_location_UP service operation 18.3.0 2023-09 SP#101 SP-230839 0408 1 F Clarification on NWDAF-assisted LCS services section 18.3.0 2023-09 SP#101 SP-230860 0410 1 F Updates on functionalities on supporting multiple location reports 18.3.0 2023-09 SP#101 SP-230839 0411 - F Indoor or outdoor indication addition on GMLC services 18.3.0 2023-09 SP#101 SP-230839 0412 2 F Signalling optimization alignment for UE available location event 18.3.0 2023-09 SP#101 SP-230839 0414 2 F QoS parameters clarification for user plane positioning between UE and LMF 18.3.0 2023-09 SP#101 SP-230839 0415 2 F UE user plane positioning capability clarification 18.3.0 2023-09 SP#101 SP-230839 0424 1 F Correction on PRU discovery 18.3.0 2023-09 SP#101 SP-230855 0426 2 F Cleanup about the usage of GPSI 18.3.0 2023-09 SP#101 SP-230839 0430 3 F Clarification on user plane positioning connection establishment 18.3.0 2023-09 SP#101 SP-230839 0431 - F Clarification on determination to use UP positioning 18.3.0 2023-09 SP#101 SP-230839 0436 3 F Further clarification on PRU on/off states 18.3.0 2023-12 SP#102 SP-231270 0416 8 F SL-MO-LR for Ranging and Sidelink Positioning corrections 18.4.0 2023-12 SP#102 SP-231270 0417 1 F Ranging and Sidelink Positioning feature corrections 18.4.0 2023-12 SP#102 SP-231270 0418 1 F SL-MT-LR for periodic, triggered Location Events corrections 18.4.0 2023-12 SP#102 SP-231270 0421 2 F Update on 5GC-MT-LR Procedure using SL positioning 18.4.0 2023-12 SP#102 SP-231270 0423 3 F Updates to MO and MT LR for SL positioning 18.4.0 2023-12 SP#102 SP-231270 0428 4 F Updates about the discovery and selection of Located UE 18.4.0 2023-12 SP#102 SP-231270 0435 9 F Solution update for ranging procedure 18.4.0 2023-12 SP#102 SP-231276 0444 1 F Update of the Location Services involving Mobile Base Station Relay 18.4.0 2023-12 SP#102 SP-231270 0445 1 F Missing information in the subscription data for exposure via CP 18.4.0 2023-12 SP#102 SP-231246 0447 1 F Clarification and correction on multiple QoS Class Handling During Service Continuity from 5GS to EPS 18.4.0 2023-12 SP#102 SP-231246 0451 1 F Clarification on the scope of LCS-SS messages transferred via the LCS user plane 18.4.0 2023-12 SP#102 SP-231246 0452 3 F Solution update on user plane positioning 18.4.0 2023-12 SP#102 SP-231276 0461 - F MBSR support in 5GC-MO-LR procedure 18.4.0 2023-12 SP#102 SP-231276 0462 - F Adding the LMF to the consumers of GMLC services 18.4.0 2023-12 SP#102 SP-231246 0464 3 B The AMF notifies the UE protocol capability to the LMF 18.4.0 2023-12 SP#102 SP-231246 0467 2 F Update for trigger for secure user plane establishment via user plane 18.4.0 2023-12 SP#102 SP-231270 0469 1 F Resolving the SLPP message forwarding 18.4.0 2023-12 SP#102 SP-231270 0472 1 F Adding SLPP to SL-MT-LR supplementary service response 18.4.0 2023-12 SP#102 SP-231246 0473 1 F Introduce LPHAP Assistance Information 18.4.0 2023-12 SP#102 SP-231246 0474 2 F Update simultaneous measurements for target UE and PRU 18.4.0 2023-12 SP#102 SP-231246 0475 1 F Update integrity requirements 18.4.0 2023-12 SP#102 SP-231246 0476 1 F Parameters update for LMF user plane service operation 18.4.0 2023-12 SP#102 SP-231246 0479 1 F Update of Procedures of User Plane Connection between UE and LMF 18.4.0 2023-12 SP#102 SP-231276 0482 2 F Adding the Additional ULI to the LMF service operation 18.4.0 2023-12 SP#102 SP-231608 0486 4 F UE Capability Update for SL-MT-LR and SL-MO-LR 18.4.0 2024-03 SP#103 SP-240087 0409 3 F Clarification on the reporting indication 18.5.0 2024-03 SP#103 SP-240108 0443 3 F Update about the usage of SUPI in SL-MT-LR 18.5.0 2024-03 SP#103 SP-240108 0450 3 F Handling ID Translation and privacy check in case of UEs belong to different PLMNs 18.5.0 2024-03 SP#103 SP-240087 0481 1 F Description Update on LCS in PNI-NPN Feature 18.5.0 2024-03 SP#103 SP-240108 0489 4 F Update on GMLC and LMF Services 18.5.0 2024-03 SP#103 SP-240087 0490 1 F Clarifications on determination of user plane positioning 18.5.0 2024-03 SP#103 SP-240087 0495 1 F Update integrity requirements 18.5.0 2024-03 SP#103 SP-240087 0496 1 F Update LMF service operation 18.5.0 2024-03 SP#103 SP-240087 0498 1 F Update of user plane positioning solution 18.5.0 2024-03 SP#103 SP-240108 0499 1 F Corrections for alignments to TS 23.273/TS 23.586/SA3/RAN WGs 18.5.0 2024-03 SP#103 SP-240108 0504 4 F Corrections of usage of SLPP and supplementary service messages for Ranging_SL procedures 18.5.0 2024-03 SP#103 SP-240108 0505 1 F Corrections to SL-MT-LR procedure 18.5.0 2024-03 SP#103 SP-240078 0509 1 A Adding GPSI to 5GC-MT-LR Procedure without UDM Query procedure 18.5.0 2024-03 SP#103 SP-240079 0511 - A Update GMLC local coordinate functionality 18.5.0 2024-06 SP#104 SP-240601 0516 3 F Removal of Ranging exposure service to Client UE through 5GC 18.6.0 2024-06 SP#104 SP-240601 0517 2 F Support for UE Ranging/SL Positioning privacy profile 18.6.0 2024-06 SP#104 SP-240587 0521 2 F Add the binding mechanism between LCS user plane connection and the UE 18.6.0 2024-06 SP#104 SP-240587 0522 C Clean up the user plane positioning 18.6.0 2024-09 SP#105 SP-241253 0534 1 F Alignment of clauses 4.3.12 and 5.1 18.7.0 2024-09 SP#105 SP-241242 0540 2 F Update LCS Architecture with user plane positioning 18.7.0 2024-09 SP#105 SP-241250 0545 - F Corrections to application ID in SL-MT-LR and LMF service operation 18.7.0 2024-09 SP#105 SP-241242 0552 2 F Clarify AMF relocation for LCS-UP connection modification 18.7.0 2024-09 SP#105 SP-241242 0557 3 F Update on the LCS-UP procedure 18.7.0 2024-09 SP#105 SP-241242 0563 2 F Location Service Continuity Update and Editorial Update 18.7.0 2024-09 SP#105 SP-241240 0565 1 A Clarification on the usage of reliable indication 18.7.0 2024-09 SP#105 SP-241264 0532 3 B KI#1 - LMF enhancements for UE positioning using a ML model 19.0.0 2024-09 SP#105 SP-241272 0541 2 B Support of on-demand broadcast of GNSS assistance data 19.0.0 2024-09 SP#105 SP-241264 0543 3 B Introduction of LMF enhancement for Direct AI/ML based Positioning 19.0.0 2024-09 SP#105 SP-241270 0546 3 B LCS with MWAB support 19.0.0 2024-09 SP#105 SP-241270 0547 3 B General Support for MWAB involved positioning 19.0.0 2024-12 SP#106 SP-241486 0537 3 B ML Model based UE positioning support 19.1.0 2024-12 SP#106 SP-241464 0573 1 A The deferred 5GC-MT-LR procedure correction 19.1.0 2024-12 SP#106 SP-241486 0574 2 B LMF enhancements for LMF-based AI/ML Positioning 19.1.0 2024-12 SP#106 SP-241467 0576 1 A LCS-UP clarification 19.1.0 2024-12 SP#106 SP-241467 0580 2 A Clarification of event filter for GNSS assistance data collection 19.1.0 2024-12 SP#106 SP-241486 0584 11 B Update on Data Collection by LMF procedure 19.1.0 2024-12 SP#106 SP-241467 0586 - A Remove N6 from roaming reference architecture 19.1.0 2024-12 SP#106 SP-241492 0589 2 B Adding Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports 19.1.0 2024-12 SP#106 SP-241467 0592 1 A Clarification on the User Plane LCS 19.1.0 2024-12 SP#106 SP-241486 0595 2 B Support AI/ML model performance monitoring by LMF 19.1.0 2024-12 SP#106 SP-241486 0597 13 B KI#1 - Addressing Editors Note: Procedure for Data Collection for AI/ML based positioning from NG-RAN 19.1.0 2024-12 SP#106 SP-241492 0608 2 B Multiple Location Report for Next Generation Emergency Routing 19.1.0 2024-12 SP#106 SP-241467 0610 2 A Clarification of LCS Correlation ID in NRPPa 19.1.0 2024-12 SP#106 SP-241467 0612 - A LCS UP security attributes alignment to TS 33.501 19.1.0 2024-12 SP#106 SP-241467 0613 1 A One Transmission Path used for One Positioning Procedure 19.1.0 2024-12 SP#106 SP-241515 0614 B Support of PRU Usage Extension 19.1.0 2024-12 SP#106 SP-241467 0616 - A Support of PRU Usage Extension 19.1.0 2024-12 SP#106 SP-241479 0617 - A Updates on UE privacy checking for SA3 alignment 19.1.0 2024-12 SP#106 SP-241496 0631 1 F Solve FFS related to the interaction between the GMLCs in different PLMNs 19.1.0 2025-03 SP#107 SP-250041 0642 8 C Updates to AI/ML-based positioning general descriptions 19.2.0 2025-03 SP#107 SP-250041 0643 7 C Updates to AI/ML-based positioning procedures 19.2.0 2025-03 SP#107 SP-250037 0647 - F Move NOTE 2 back to the user plane positioning text 19.2.0 2025-03 SP#107 SP-250049 0649 1 A Correction on Ranging/SideLink positioning procedure 19.2.0 2025-03 SP#107 SP-250041 0656 1 F Clarification on data collection by LMF for LMF-based AIML Positioning 19.2.0 2025-03 SP#107 SP-250041 0657 5 F Clarification on LMF requesting ML model for LMF-based AI/ML Positioning from the NWDAF containing MTLF 19.2.0 2025-03 SP#107 SP-250041 0658 4 F Clarification on model performance monitoring for LMF-based AIML Positioning 19.2.0 2025-03 SP#107 SP-250031 0662 - A Clarification on LMF re-selection of LCS UP positioning 19.2.0 2025-03 SP#107 SP-250059 0665 1 F LCS Client alignment to Routing Entities using HELD in Emergency LCS 19.2.0 2025-03 SP#107 SP-250041 0669 9 B Procedures to collect data from the UE and from NG-RAN, resolution of Editors Note. 19.2.0 2025-03 SP#107 SP-250063 0670 2 F Clarification of location services when a UE is served by a MWAB-gNB 19.2.0 2025-03 SP#107 SP-250041 0676 2 F Adding new LMF Selection Factor 19.2.0 2025-03 SP#107 SP-250059 0677 1 F Adding the reference and correcting the format error 19.2.0 2025-03 SP#107 SP-250041 0682 2 F Clarification on data collection by LMF from NG-RAN for LMF-based AIML Positioning 19.2.0 2025-03 SP#107 SP-250041 0688 2 F User consent check during performance monitoring 19.2.0 2025-03 SP#107 SP-250031 0693 2 A Common Procedure Types Sync with 38.305 19.2.0 2025-03 SP#107 SP-250059 0696 1 F Add Positioning Deactivation step in Cancellation of Reporting of Periodic Events 19.2.0
|
701465bc5227ddf47bbba259b7283444
|
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 [5].
The present document is applicable primarily to mission critical services using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [17]. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
701465bc5227ddf47bbba259b7283444
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[4] 3GPP TS 22.281: "Mission Critical Video services".
[5] 3GPP TS 22.282: "Mission Critical Data services".
[6] 3GPP TS 23.002: "Network Architecture".
[7] 3GPP TS 23.179: "Functional architecture and information flows to support mission critical communication services; Stage 2"
[8] 3GPP TS 23.203: "Policy and charging control architecture".
[9] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[10] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[11] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[12] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[13] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[14] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[15] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows".
[16] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[17] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[18] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[19] 3GPP TS 29.283: "Diameter Data Management Applications".
[20] Void
[21] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[22] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[23] GSMA PRD IR.92 v10.0: "IMS Profile for Voice and SMS".
[24] GSMA PRD IR.88 v15.0: "LTE and EPC Roaming Guidelines".
[25] 3GPP TS 33.180: "Security of the mission critical service".
[26] IETF RFC 6733 (October 2012): "Diameter Base Protocol".
[27] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[28] 3GPP TS 22.011: "Service accessibility".
[29] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[30] 3GPP TS 25.305: "Stage 2 functional specification of User Equipment (UE) positioning in UTRAN".
[31] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[32] IETF RFC 2865 (June 2000): "Remote Authentication Dial In User Service (RADIUS)".
[33] IETF RFC 3162 (August 2001): "RADIUS and IPv6".
[34] 3GPP TS 25.501: "System architecture for the 5G System (5GS)".
[35] IETF RFC 1541 (October 1993): "Dynamic host configuration protocol".
[36] IETF RFC 8415 (November 2018): "Dynamic host configuration protocol for IPv6 (DHCPv6)".
[37] IETF RFC 9330:"Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture".
[38] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[39] 3GPP TS 23.380: "IMS Restoration Procedures".
[40] IETF RFC 7866 (May 2016): "Session Recording Protocol"
[41] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
3 Definitions, symbols and abbreviations
| |
701465bc5227ddf47bbba259b7283444
|
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 uncertainty of the location at the moment of location measurement, e.g. see 3GPP TS 25.305 [30] and 3GPP TS 23.032 [31].
ACM: Administrative Configuration Management, which enables the exchange of administrative configuration data between interconnected MC systems.
ACMC: Administrative Configuration Management Client, client entity which initiates administrative configuration exchange request to an interconnected partner MC system and which could make decision on such request received from an ACMC of a partner MC system.
ACMS: Administrative Configuration Management Server, server entity which receives administrative configuration exchange requests from an ACMC belonging to the same primary MC system or via an ACMS of an interconnected partner MC system.
Active MC service user profile: The MC service user profile that is currently used by an MC service client of an MC service user while receiving MC service.
Ad hoc Group Communication: The combining of a multiplicity of MC service users into a group for the duration of a communication. When the communication is released, the group no longer exists. If the communication is associated with an alert, then the group continues to exist until the alert is also cancelled.
Ad hoc Group emergency alert: The combining of a multiplicity of MC service users into a group for sending an emergency alert. When the alert is cancelled, the group no longer exists. If the alert is associated with a communication, then the group continues to exist until the communication is also cancelled.
Altitude: Third dimension for the geographical coordinates at the moment of location measurement, e.g. see 3GPP TS 25.305 [30] and 3GPP TS 23.032 [31].
Bearing: Direction at the moment of location measurement, e.g. see 3GPP TS 25.305 [30].
Chat group: An MC service group that is pre-defined with MC service group ID and member list in the group management server. Group members must join the pre-established group call to participate.
ECGI: E-UTRAN Cell Global Identifier, which is used to identify cells globally, where the ECGI is constructed from the Mobile Country Code (MCC), Mobile Network Code (MNC) and the E-UTRAN Cell Identifier (ECI).
Interconnection: A means of communication between MC systems whereby MC service users obtaining MC service from one MC system can communicate with MC service users who are obtaining MC service from one or more other MC systems.
Interconnection group: An MC service group that is configured to allow inclusion of MC service group members who are MC service users from partner MC system(s).
LCS network: The 3GPP network that provides location service as defined in 3GPP TS 23.271 [29].
Location: The current physical location of the MC service UE.
Logging: Storing of metadata (signalling) to a storing device (mass storage). This metadata can either belong to a MC user's communication session or can be non-communication session related signalling. If the term ‘recording’ is used without explicitly mentioning "logging", then logging is implicitly part of that recording activity.
MBMS SAI: Multimedia Broadcast Multicast Service Area Identity which is mapped to the MBMS service area.
MC gateway server: A server providing topology hiding for MC service interconnection with a partner MC system, where that partner MC system is in a different trust domain.
MC service: A generic name for any one of the three mission critical services: either MCPTT, or MCVideo, or MCData.
MC service affiliated group member: An MC service user who has indicated an interest in a particular MC service group and has been accepted to participate in MC service group communication for that MC service group.
MC service client: A generic name for the client application function of a specific MC service. MC service client could be replaced by MCPTT client, or MCVideo client, or MCData client depending on the context.
MC service group: A defined set of MC service users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions) configured for the use with one or more MC services.
MC service group affiliation: A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is determined.
MC service group call: A mechanism by which an MC service user can make a one-to-many MC service(s) transmission to other users that are members of MC service group(s).
MC service group de-affiliation: A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is removed.
MC service group home system: The MC system where the MC service group is defined.
MC service group host MC service server: The MC service server within an MC system which provides centralised support for a particular MC service of an MC service group defined in a MC service group home system.
MC service group member: An MC service user, whose MC service ID is listed in a particular MC service group.
MC service ID: A generic name for the user ID of a mission critical user within a specific MC service. MC service ID could be replaced by MCPTT ID, MCVideo ID, or MCData ID depending on the context.
MC service server: A generic name for the server application function of a specific MC service. MC service server could be replaced by MCPTT server, MCVideo server, or MCData server depending on the context.
MC service user: An authorized user, who can use an MC service UE to participate in one or more MC services.
MC service user profile: The set of information associated to an MC service user that allows that user to employ one or more MC services in a given role and from a given MC service UE.
MC service UE: A UE that can be used to participate in one or more MC services and recording admin and replay services.
MC service UE label: A generic name for identification of a specific MC service UE.
MC system: The collection of applications, services, and enabling capabilities required to provide a single mission critical service or multiple mission critical services to one or more mission critical organizations.
MC user: A user, identified by an MC ID, who, after authorization, obtains mission critical service(s).
Migration: A means for an MC Service user to obtain MC service directly from a partner MC system.
Partner MC system: Allied MC system that provides MC services to an MC service user based on the MC service user profiles that are defined in the primary MC system of that MC service user.
Preconfigured MC service group: an MC service group used only for regrouping that has been configured in advance of a group or user regrouping operation to serve as the source of regroup group configuration.
Pre-arranged group: An MC service group that is pre-defined with MC service group ID and member list in the group management server. Affiliated group members are invited when the group communication is setup.
Pre-selected MC service user profile: The MC service user profile that is to be selected as the active MC service user profile through configuration, and applicable for an authenticated MC service user upon MC service authorization.
Primary MC system: MC system where the MC service user profiles of an MC service user are defined.
Recording: Recording of media – voice/video/data – of user communication sessions. If term "logging" is not explicitly mentioned with "recording", then the recording activity implicitly includes also logging.
Recording admin UE: A UE that can be used to configure targets for recording. Recording admin UE can be a mobile device or a (computer) workstation.
Recording admin and replay service user profile: A set of parameters defining the authorizations for a recording administrator and/or replay user.
Recording administrator: A user, identified by MCRec ID, who, after authorization, is able to set and modify target users and target groups for recording.
Recording admin client: A client application that a recording administrator can use to set target users and target groups for recording.
Recording server: A server that is able to log the metadata and record the media of MCPTT and MCVideo group communications and private communications. This server is also able to retrieve the logged/recorded data when requested by an authorized replay user.
Replay: Fetching stored recordings and logs (i.e. media and metadata) of a user communication from a mass storage and replaying them to an authorized user. Equivalent to term "Audit" that is used in other 3GPP specifications.
Replay user: A user, identified by an MCRec ID, who, after authorization, is able to fetch and replay recorded MCPTT and MCVideo metadata and media of MC service group communications and MC service private communications under the user’s authority.
Replay UE: A user equipment that can be used to fetch and replay recorded MCPTT and MCVideo metadata and media of MC service group communications and MC service private communications under the UE user’s authority. The Replay UE can be a mobile device or a (computer) workstation.
Replay client: A client application that an authorized replay user can use to fetch and replay recorded metadata and media from a recording server.
Requested Priority: A value for use in a MC service group or MC private communication that, if accepted, is used by the MCX service server to temporarily replace the priority level that is predefined in the MC service group or MC service user profile. This value is used in combination with other factors to determine the application priority for the requested communication.
Selected MC service user profile: The MC service user profile that is to be selected as the active MC service user profile for an MC service upon request by an MC service user.
Serving MC service server: The MC service server which is providing MC service to an MC service client.
NOTE 1: There is one serving MC service server for each MC service, which can be the primary MC service server of the MC service user of the MC service client, or can be a partner MC service server to which the MC service user has migrated.
Serving MC system: The MC system which is providing MC service to an MC user.
NOTE 2: The MC system can be the primary MC system of the MC service user, or can be a partner MC system to which the MC service user has migrated.
Speed: Movement at the moment of location measurement, e.g. see 3GPP TS 25.305 [30] and 3GPP TS 23.032 [31].
Time of measurement: Date and time expressed with a certain precision to reflect the moment of the location measurement.
For the purposes of the present document, the following terms given in 3GPP TS 22.280 [3] apply
Mission Critical
Mission Critical Applications
Mission Critical Organization
Mission Critical Service
Functional alias
For the purposes of the present document, the following terms given in 3GPP TS 22.179 [2] apply
Multi-talker control
Group-broadcast group
For the purposes of the present document, the following terms related to a MC gateway UE function apply
MC gateway UE: A UE with functionality that enables access to the MC service for non-3GPP devices.
MC client: Aggregates a set of clients (i.e. Group management client, Configuration management client, Identity management client, Key management client, Location management client and MC service client).
MC server: Aggregates a set of servers (i.e. Group management server, Configuration management server, Identity management server, Key management server, Location management server and MC service server) which serves the MC client accordingly.
Non-3GPP device: A device that enables connectivity towards an MC gateway UE using an access method not specified by 3GPP. A subset of these devices can host an MC client specified by 3GPP.
GW Client: Functional entity residing on the non-3GPP UE for supporting the location management and MBMS transmission for the MC client.
GW Server: Functional entity residing on the MC gateway UE for supporting the location management and MBMS transmission for the MC clients residing on the non-3GPP UE.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
3.2 Symbols
|
For the purposes of the present document, the symbols given in 3GPP TS 22.280 [3] apply
Nc6
|
701465bc5227ddf47bbba259b7283444
|
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
CMS Configuration Management Server
CSC Common Services Core
CSCF Call Server Control Function
DPF Direct Provisioning Function
E-UTRAN Evolved Universal Terrestrial Radio Access Network
EPC Evolved Packet Core
EPS Evolved Packet System
FEC Forward Error Correction
GBR Guaranteed Bit Rate
GCS AS Group Communication Service Application Server
GCSE_LTE Group Communication Service Enabler over LTE
GMS Group Management Server
GRUU Globally Routable User agent URI
HSS Home Subscriber Server
HTTP Hyper Text Transfer Protocol
I-CSCF Interrogating CSCF
IARI IMS Application Reference Identifier
ICE Interactive Connectivity Establishment
ICSI IMS Communication Service Identifier
IdMS Identity Management Server
IM CN IP Multimedia Core Network
IMPI IP Multimedia Private Identity
IMPU IP Multimedia PUblic identity
IMS IP Multimedia Subsystem
IMSI International Mobile Subscriber Identity
KMS Key Management Server
LCS Location Services
LMC Location Management Client
LMS Location Management Server
MBMS Multimedia Broadcast and Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MC Mission Critical
MC ID Mission Critical user identity
MCPTT AS MCPTT Application Server
MCRec ID Recording admin and replay user identity
MCPTT ID MCPTT user identity
NAT Network Address Translation
P-CSCF Proxy CSCF
PLMN Public Land Mobile Network
ProSe Proximity-based Services
PSI Public Service Identity
QoS Quality of Service
RAN Radio Access Network
RF Radio Frequency
ROHC RObust Header Compression
S-CSCF Serving CSCF
SIP Session Initiated Protocol
SSL Secure Sockets Layer
TLS Transport Layer Security
TMGI Temporary Mobile Group Identity
UDC User Data Convergence
UDR User Data Repository
USB Universal Serial Bus
URI Uniform Resource Identifier
WLAN Wireless Local Area Network
For the purposes of the present document, the abbreviations given in 3GPP TS 22.280 [3] apply
MCData
MCPTT
MCVideo
|
701465bc5227ddf47bbba259b7283444
|
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 architecture of the MC gateway UE to enable access to the MC system from MC clients residing on non-3GPP devices. A subset of these devices can host an MC client specified by 3GPP.
Each MC service supports several types of communications amongst the users (e.g. group call, private call). There are several common functions and entities (e.g. group, configuration, identity) which are used by the MC services.
The common functional architecture to support MC services utilises aspects of the IMS architecture defined in 3GPP TS 23.228 [9], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [14], the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in 3GPP TS 23.468 [18] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [10].
The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [17]. Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN or using MC service UEs via non-3GPP access networks. External applications usage of MC services can be enabled via E-UTRAN or non-3GPP access networks.
NOTE: Dispatch consoles and devices used by MC service administrators are considered MC service UEs in the common functional architecture to support MC services.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
5 Assumptions and architectural requirements
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
5.1 Assumptions
| |
701465bc5227ddf47bbba259b7283444
|
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 subclause 6.2.2.3.
- Remote Leg Update as defined in subclause 6.3.1.5.
- PS-PS Access Transfer with full media transfer as defined in subclause 6.2.2.1.
The MC service UE, prior to going out of E-UTRAN coverage, should attempt to make use of a ProSe UE-to-network relay to support service continuity.
|
701465bc5227ddf47bbba259b7283444
|
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 in different trust domains:
- A public user identity shall not identify an MC service user in a different trust domain (see subclause 8.3.1);
- A public service identity shall not identify an MC service group ID in a different trust domain (see subclause 8.3.2);
- A SIP database shall not pass responses to a registrar or registrar finder in a different trust domain (see subclause 7.4.3.2.1); and
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
5.2 Architectural requirements
| |
701465bc5227ddf47bbba259b7283444
|
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 with their existing network architecture.
Hence a functional decomposition of MC service architecture into distinct logical functions is required.
b) The MC service architecture should enable an application plane and signalling control plane split for the provisioning of the MC service.
c) To enable parts of the MC service architecture to be shared for other applications, the architecture should enable the group management functions (e.g. admission control; linking of groups;) to be implemented on a separate node from the main application functions of the MC service (e.g. "call" setup/termination; allocation of TMGI to UE; floor control;).
d) There is a need to promptly form (and release) groups of users that span multiple public safety network administrations. To enable this, the MC service architecture should provide the relevant interfaces between public safety networks.
|
701465bc5227ddf47bbba259b7283444
|
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 Preferred PLMN Selector list (see 3GPP TS 22.011 [28]) may be configured with a list of PLMNs that can be used to migrate to one or more partner MC systems (see subclause 5.2.9.2).
|
701465bc5227ddf47bbba259b7283444
|
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. For each allowed MC service group, a unique associated relay service code should be allocated and it may be provided to the relay UE from MC service server or DPF.
NOTE: According to the PLMN operator's configuration, one relay service code can map to one or multiple MC service group(s).
|
701465bc5227ddf47bbba259b7283444
|
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 an index to uniquely distinguish the MC service user profile from other MC service user profiles associated to the same MC service user.
For the set of MC service user profiles associated to a single MC service user, one of the MC service user profiles shall be indicated as the pre-selected MC service user profile to the MC service client and the MC service server.
The MC service user shall be able to:
- change the pre-selected MC service user profile; and
- change the selected MC service user profile.
The MC service user profile may be modified at the configuration management server.
5.2.4a Recording admin and/or replay service user profile requirements
The Recording admin and/or replay service user profile shall:
- be provisioned subject to the user authentication by the identity management server;
- be stored at the configuration management server;
- be available for obtaining by group management server and recording server;
- be valid only in the user’s home MC system i.e. if the user migrates to another MC system, his/her recording admin and/or replay service user profile becomes invalid; and
- be associated with an MC service user (MC ID).
The recording admin and/or replay service user profile can be modified at the configuration management server by an authorized user. A recording admin and/or replay service user shall not be able to modify his/her user profile.
|
701465bc5227ddf47bbba259b7283444
|
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 affiliation and de-affiliation shall be performed as per the MC service selected by the MC service user. For individual MC service group affiliation and MCservice group de-affiliation, the requirements are specified in the corresponding MC service TS.
NOTE 1: A combined affiliation to multiple MC services for a single MC service group is not specified in the current document.
MC service group affiliation can be achieved through the following two methods:
a) Explicit affiliation: An MC service client indicates interest in one or many MC service groups to the MC service server. This interest may be initiated either by an MC service user using the MC service UE, or by an automatic procedure within the MC service client that indicates that the MC service user is interested in the MC service group at that MC service client. An authorized MC service user may remotely modify another MC service user's affiliation to an MC service group.
b) Implicit affiliation: An MC service user's affiliations to MC service groups are determined through configurations and policies within the MC service and performed by the associated MC service server.
NOTE 2: MC service group affiliation is not the same as MC service group membership; however, an MC service user is a member of an MC service group prior to becoming an affiliated member of that MC service group.
The MC service server may refuse a request for affiliation from an MC service user to an MC service group, in which case the MC service user will be unable to take part in the requested MC service associated with that MC service group, and the MC service client should make the MC service user aware that the MC service user is not affiliated to the MC service group for the requested MC service. The MC service server may also de-affiliate an MC service client from an MC service group following a relevant trigger condition.
MC service group de-affiliation indicates that the MC service user is no longer interested in that MC service group, either at the MC service client, or across all MC service clients depending on MC service group configuration, and therefore is unable to perform any actions that are associated with an affiliated member (e.g. receive media, notifications). MC service group de‑affiliation can occur due to either an MC service client's explicit request, or implicitly i.e. changed by the MC service server as the result of another action e.g. the MC service user logging off. When the MC service user is logged off from the MC service, all affiliations shall be revoked in the MC service server even if no explicit de-affiliation signalling is sent.
Editor's note: The interaction of logoff and de-affiliation when moving to off network case is FFS.
NOTE 3: When the MC service user next performs successful service authorization, re-affiliation occurs in the MC service server without explicit affiliation signalling for all MC service groups that are configured for implicit affiliation after service authorization.
NOTE 4: The MC service client may also store MC service groups to which the MC service user was affiliated prior to that user logging off, and may re-affiliate through an explicit affiliation to these groups following the next service authorization. Such a function is outside the scope of the present document.
|
701465bc5227ddf47bbba259b7283444
|
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 can be represented (in a simplified diagram) as shown in figure 5.2.6-1:
Figure 5.2.6-1: MC service on-network architecture showing MBMS
The MC service server is shown being bundled with the GCS AS within the same network entity. It is illustrated this way for simplicity of the diagram.
MC service media content is transmitted via LTE bearers, which are communication pipes with one end in the MC service server and the other end in the MC service UE. The uplink bearers are always allocated as unicast, but the downlink bearers can be allocated as unicast or as MBMS bearers, or both.
An MBMS bearer (both network and radio part) is uniquely identified via a TMGI or via a combination of a TMGI and a flow identifier (see 3GPP TS 23.246 [11]). The MC service server is capable, via the MB2 interface, to request the creation of MBMS bearers and associate a unique TMGI or a combination of a TMGI and a flow identifier (see 3GPP TS 23.468 [18]). The MC service server may determine the MBMS broadcast area based on the cell identities of the affiliated group members received over GC1. The MC service server may determine for a user the switching from MBMS bearer to unicast bearer based on the information reported over GC1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
5.2.7 Bearer management
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
5.2.7.0 General
|
The MC service UE shall use the following APNs:
- an MC services APN for the SIP-1 reference point;
- an MC common core services APN for the HTTP-1 reference point; and
- an MC identity management service APN for the CSC-1 reference point.
The value of each of these APNs:
- may be the same or may differ;
- may be the same as other non-MC services that have compatible QoS and PDN (see NOTE); and
- shall be made available to the UE either via UE (pre)configuration or via initial UE configuration (see subclause 10.1.1) on a per HPLMN and optionally also a per VPLMN basis.
NOTE: The APN value of "IMS" is a well-known APN, whose PDN connection characteristics are defined in GSMA PRD IR.92 [23] and GSMA PRD IR.88 [24], and which is used in some deployments for operator IMS‑based services e.g. Voice over LTE. This well-known APN can be used for the MC service APN if the SIP core belongs to the PLMN operator and both the PLMN operator and MC service provider have agreed which QoS aspects to utilise i.e. either the QoS aspects defined in subclause 5.2.7.2 or the QoS aspects defined in GSMA PRD IR.92 [23] and GSMA PRD IR.88 [24].
The MC service UE may utilise PDN access credentials as specified in 3GPP TS 23.401 [17] (e.g. PAP, CHAP) to access the PDNs identified by the MC service APN, the MC common core services APN and the MC identity management service APN. If PDN access credentials are required, then they shall be made available to the MC service UE via initial MC service UE configuration (see subclause 10.1.1) on a per APN basis.
The PDN connection to the APNs defined within the present subclause can be of type "IPv4", "IPv6" or "IPv4v6" (see 3GPP TS 23.401 [17]). If a PDN connection to an APN defined within the present subclause is of type "IPv4v6" then the MC service client shall use configuration data to determine whether to use IPv4 or IPv6.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.