Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.273  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.2a…   4.3…   5…   5.5…   6…   6.1.2   6.1.3   6.1.4   6.2   6.3…   6.3.2…   6.4   6.5…   6.7…   6.7.3   6.7.4   6.7.5   6.8   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.15…   6.16…   6.17…   6.18…   6.19…   6.19.3…   6.20…   6.20.4…   6.21…   7…   8…   A…   B…   C…

 

6.7.3  Event Reporting in RRC INACTIVE state for DL Positioning, RAT Independent Positioning or No Positioning |R17|p. 78

Figure 6.7.3-1 summarizes the initiation and reporting of location events for a deferred 5GC-MT-LR procedure for Periodic or Triggered Location Events when a UE is in RRC INACTIVE state and when DL positioning, RAT independent positioning or no positioning is used for event reporting. This procedure is only applicable to a UE with NR access to 5GC.
Reproduction of 3GPP TS 23.273, Fig. 6.7.3-1: Low Power Periodic and Triggered 5GC-MT-LR Procedure in RRC INACTIVE state with DL Positioning, RAT Independent Positioning or No Positioning
Up
Step 1.
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 DL positioning, RAT Independent positioning or no positioning will be used for subsequent location reporting events when the UE is in RRC INACTIVE state. If DL positioning or RAT independent positioning will be used, the LMF includes an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16, where the LPP positioning message requests DL location measurements, RAT independent location measurements or a location estimate based on these location measurements. If no location of the UE is needed for event reporting or if a location based on a Cell ID will suffice for the location QoS, the LMF does not include an LPP positioning message in the LCS Periodic-Triggered Invoke Request sent to the UE at step 16.
Step 2.
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.
Step 3.
The UE monitors for and detects a trigger event as described for step 22 in clause 6.3.1.
Step 4.
If DL positioning or RAT independent positioning was indicated at step 1, the UE obtains the location measurements or location estimate requested in the LPP message received in step 1. If DL positioning or RAT independent positioning was not indicated at step 1, this step is skipped.
Step 5.
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. If DL positioning or RAT independent positioning was indicated at step 1, the UE includes an LPP positioning message in the supplementary services event report message that includes the location measurements or location estimate obtained at step 4. If DL positioning or RAT independent positioning was not indicated at step 1, the UE does not include an LPP positioning message in the supplementary services event report message. The event report message also 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 include the deferred routing identifier received in step 16 in clause 6.3.1.
Step 6.
The receiving gNB node forwards the UL NAS TRANSPORT message to the serving AMF in an N2 Uplink NAS Transport message.
Step 7.
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.
Step 8.
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.
Step 9.
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.
Step 10.
The receiving gNB node sends a Subsequent DL SDT message to the UE and includes the NAS message received in step 10.
Step 11.
The receiving gNB node sends an RRC Release message to the UE to keep the UE in RRC INACTIVE state.
Step 12.
Following step 11, the UE remains in RRC INACTIVE state.
Step 13.
If a location estimate is needed for event reporting, the LMF determines the UE location using the location measurements or location estimate received at step 7 or a Cell ID provided by the AMF at step 7.
Step 14.
Steps 28-31 for clause 6.3.1 are performed to send the event report to the LCS client or AF.
Up

Up   Top   ToC