Content for  TS 23.273  Word version:  19.0.0

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).

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.

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.

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.

The SL-MT-LR request from AMF is Periodic-Triggered, and the Routing identifier is immediate Routing identifier.

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.

The SL-MT-LR response forwarded by AMF is Periodic-Triggered, and Correlation identifier is immediate Routing identifier.

The Ranging/Sidelink positioning location results returned by LMF to LCS Client or AF is initial one.

The UEs 1 to n periodically perform Ranging/Sidelink positioning in order to support steps 22 and 24.

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.

UE1 performs a UE triggered service request as defined in clause 4.2.3.2 of TS 23.502 if in CM-IDLE state in order to establish a signalling connection with the AMF.

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.

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.

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.

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.

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.

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.

UEs 1 to n continue to periodically perform Ranging/Sidelink positioning as in step 21.

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.