Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.273  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   4.2a…   4.3…   5…   6…   6.1.2   6.2   6.3…   6.3.2…   6.4   6.5…   6.7…   6.8   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   7…   8…   A…   B…

 

6.3.2  Cancellation of Reporting of Location Events by a UEWord-p. 48
Figure 6.3.2-1 summarizes a procedure to enable a UE to cancel a deferred 5GC-MT-LR procedure for periodic, or triggered location events (e.g. if the UE is powered off or if the UE cancels the location request based on user's input). It is assumed that a deferred 5GC-MT-LR for periodic or triggered location events has already been initiated in the UE according to steps 1-17 for the procedure in clause 6.3.1. If a network entity (e.g. (H)GMLC, AMF or LMF) cancels a deferred 5GC-MT-LR procedure for periodic or triggered location events, part of the procedure in clause 6.3.3 for cancellation by an AF or external LCS Client would be used to cancel towards the UE and part of the procedure in this clause would be used to cancel towards the AF or external LCS Client.
Up
Step 1.
The UE 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.
Step 2.
The UE sends a Cancel Location request message to the LMF which is transferred via the serving AMF and is delivered to the LMF using an Namf_Communication_N1MessageNotify service operation. The UE includes the deferred routing identifier originally received in step 16 of the procedure in clause 6.3.1 (or as updated by step 26 in clause 6.3.1 or by the procedure in clause 6.4) in the NAS Transport message used to transfer the cancel location request from the UE to the AMF. The AMF then forwards the cancel location request to either the serving LMF or any suitable LMF based on whether the deferred routing identifier indicates a particular LMF or any (default) LMF. The UE also includes the (H)GMLC contact address and the LDR reference number.
Step 3.
In the case of roaming, the LMF selects a VGMLC. The LMF then invokes an Nlmf_Location_EventNotify service operation towards the selected VGMLC or (H)GMLC with an indication of the cancelation of location event reporting, the (H)GMLC contact address and LDR reference number.
NOTE 1:
In the case of roaming, the LMF may select the VGMLC for step 3 using the NRF service or using configuration information in the LMF or may use the same VGMLC as for steps 3-8 of clause 6.3.1 (e.g. if the LMF acts as a serving LMF and received the VGMLC address from the AMF as part of step 14 of clause 6.3.1).
Step 4.
This step is skipped for a non-roaming UE. For a roaming UE, the VGMLC invokes an Ngmlc_Location_EventNotify service operation to forward the cancel location request (including the LDR reference number) to the HGMLC which identifies the periodic and triggered location request from the LDR reference number.
NOTE 2:
As an optional optimization for a roaming UE, instead of performing steps 3 and 4, the LMF may invoke the Nlmf_Location_EventNotify service operation directly towards the HGMLC.
Step 5.
The (H)GMLC uses the LDR reference number received in step 3 or step 4 to identify the periodic and triggered location request received in step 1 of clause 6.3.1 and then forwards the cancel location to the external LCS client or AF (via the NEF).
Step 6.
The LMF returns an acknowledgment to the UE via the serving AMF.
Up
6.3.3  Cancellation of Reporting of Location Events by an AF or External LCS Client or GMLCWord-p. 49
Figure 6.3.3-1 summarizes a procedure to enable an AF or External LCS Client or GMLC to cancel a deferred 5GC-MT-LR procedure for periodic, or triggered location. It is assumed that a deferred 5GC-MT-LR for periodic or triggered location events has already been requested according to the procedure in clause 6.3.1 up until at least step 20.
Up
Step 1.
The external LCS client or AF (via an NEF) send a request to cancel the periodic or triggered location to the (H)GMLC, the external LCS client or AF shall include the identity of the deferred request.
The HGMLC may itself initiate the cancellation procedure, e.g. when it is notified that the UE LCS privacy profile stored in the UDM was changed. For every outstanding Deferred Location Request against that UE, the HGMLC shall perform a new privacy check based on the updated UE LCS privacy profile stored in the UDM. If the privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request shall be continued. Otherwise, if the privacy check does not pass, i.e. the Location estimate of the target UE is not allowed to be provided to the LCS Client, the HGMLC shall initiate a cancellation procedure
NOTE:
GMLC may perform privacy check for more than one location request as a bulk operation.
Step 2.
The (H)GMLC queries the UDM to determine the serving AMF address as in step 3 of clause 6.3.1.
Step 3.
For a roaming UE, the HGMLC obtains a VGMLC address if not received at step 2 and invokes an Ngmlc_Location_CancelLocation service operation to forward the cancellation request to the VGMLC. The (H)GMLC also includes the contact address for the (H)GMLC and the LDR reference number in the request and the latest LMF identification received in step 20 or step 29 in clause 6.3.1 if either step has occurred and included an LMF identification.
Step 4.
The (H)GMLC or VGMLC invokes the Namf_Location_CancelLocation service operation to forward the cancellation request to the serving AMF and includes the (H)GMLC contact address, LDR reference number and LMF identification if available.
Step 5.
If an LMF identification was included in step 4, the AMF forwards the cancelation request to the indicated LMF by invoking an Nlmf_Location_CancelLocation service operation and includes the (H)GMLC contact address and LDR reference number. The LMF then releases all resources for the location request.
Step 6.
If the UE is not currently reachable (e.g. is using eDRX or PSM), the AMF waits for the UE to become reachable.
Step 7.
Once the UE is reachable, if the UE is then in CM IDLE state, the AMF initiates a network triggered Service Request procedure as defined in clause 4.2.3.3 of TS 23.502 to establish a signalling connection with the UE.
Step 8.
The AMF sends the cancelation request to the target UE and includes the (H)GMLC contact address and the LDR reference number. The UE then releases all resources for the location request.
Step 9.
The UE returns an acknowledgment to the AMF.
Step 10.
The AMF responds to Namf_Location_CancelLocation, then V-GMLC or (H)GMLC releases all resources for the location request. AMF releases all resources for the location request.
Step 11.
For a roaming UE, the VGMLC responds to Ngmlc_Location_CancelLocation, then HGMLC releases all resources for the location request.
Step 12.
[Conditional] If the cancellation procedure is requested by HGMLC (i.e. the procedure is triggered in step 1c) and the cancelled location event is reported to external client or AF (via NEF).
Up

Up   Top   ToC