Content for  TS 23.273  Word version:  19.0.0

Steps 1-21 for the deferred 5GC-MT-LR procedure for periodic or triggered location events in clause 6.3.1 are performed with the following differences.

• At step 16 in clause 6.3.1, the LMF indicates to the UE that UL positioning may be used for subsequent location reporting events when the UE is in RRC INACTIVE state by not including an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16.

The UE enters RRC INACTIVE state some time before an event is detected at step 22 or step 31 in clause 6.3.1. If the UE is not in RRC INACTIVE state when an event is detected at step 22 or step 31 in clause 6.3.1, then the UE follows the procedure described for steps 22-31 in clause 6.3.1 to report the event to the LMF and to the LCS Client or AF.

The UE monitors for and detects a trigger event as described for step 22 in clause 6.3.1.

The UE sends an RRC Resume Request with small data transmission (SDT) to a receiving gNB node in the NG-RAN. The RRC Resume Request includes an RRC UL Information Transfer message containing an UL NAS TRANSPORT message that includes a supplementary services event report message. The UE does not include an LPP positioning message in the supplementary services event report message. The event report message includes other information described in step 25 in clause 6.3.1 (e.g. the type of event being reported). The UL NAS TRANSPORT message also includes the deferred routing identifier received in step 16 in clause 6.3.1.

The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message.

The AMF checks the integrity of the NAS message and deciphers its contents. The AMF then invokes an Namf_Communication_N1MessageNotify service operation to forward the event report to the serving LMF as described for step 25 in clause 6.3.1.

The LMF uses the Network Assisted Positioning Procedure in clause 6.11.2 to request the receiving gNB node to provide an UL configuration to the UE at step 11. The receiving gNB node then determines an UL Configuration to be used later at step 11 and indicates this to the LMF. The LMF also uses the Non-UE Associated Network Assistance Data procedure in clause 6.11.3 to request UL location measurements of the UE by NG-RAN gNB nodes.

The LMF invokes an Namf_Communication_N1N2MessageTransfer operation to return an acknowledgment for the event report as described for step 26 in clause 6.3.1.

The AMF forwards the acknowledgment to the receiving gNB node in a DL NAS TRANSPORT message which is encapsulated in an N2 Downlink NAS Transport message.

The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 10.

The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state and includes the UL Configuration determined at step 7.

The UE transmits UL positioning signals according to the UL Configuration received at step 11. The NG-RAN gNB nodes that were requested to obtain UL location measurements at step 7 obtain the UL location measurements of the UL positioning signals transmitted by the UE.

The NG-RAN gNB nodes transfer the UL location measurements obtained at step 12 to the LMF according to the Non-UE Associated Network Assistance Data Procedure in clause 6.11.3.

Following step 13, the UE remains in RRC INACTIVE state.

The LMF determines the UE location using the UL location measurements received at step 13.

Steps 28-31 in clause 6.3.1 are performed to send the event report to the LCS client or AF.