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.4  LMF Change ProcedureWord-p. 50
The LMF Change procedure supports change of a serving LMF during a deferred 5GC-MT-LR procedure for periodic, or triggered location events as defined in clause 6.3.1. When a serving LMF is used for the procedure in clause 6.3.1, mobility of the target UE may lead to a change of serving AMF for which the original serving LMF is not suitable. For example, the serving LMF may be very remote from the new serving AMF leading to higher resource utilisation for AMF to LMF signalling or the LMF may not be configured with information (e.g. a cell database) for the current access network for the UE to enable location. In such a case, the serving LMF may need to change. Figure 6.4-1 shows a procedure to enable change of the serving LMF when a UE sends an event report as at step 25 in clause 6.3.1.
Up
Precondition: Steps 1-23 in clause 6.3.1 have already been performed and steps 22-30 may have been performed or repeated. A serving LMF is used and the current serving LMF is LMF1.
Step 1.
The UE performs a service request if needed as for step 24 in clause 6.3.1.
Step 2.
The UE sends a NAS Transport message containing a supplementary services event report message to the serving AMF. The NAS Transport message includes a deferred routing identifier indicating LMF1. Step 2 corresponds to part of step 25 for clause 6.3.1.
Step 3.
Based on operator configuration and policy, the AMF may evaluate and determine that LMF1 is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF.
Step 4.
The AMF invokes the Namf_Communication_N1MessageNotify service operation towards LMF1. The service operation includes the event report received in step 2. If the AMF determined in step 3 that a new LMF2 should be used, it indicates that to the LMF1 as well.
Step 5.
If the AMF did not indicate a new LMF in step 4, based on the operator configuration and policy, LMF1 may evaluate and determine that it is unsuitable or unable to support location for the current UE access network or serving cell and determines LMF2 as being a more suitable LMF.
Step 6.
LMF1 invokes an Nlmf_Location_LocationContextTransfer Request service operation towards LMF2 to provide the current location context of the UE and includes the event report message received in step 4. The service operation includes the AMF identity and all the information originally received by LMF1 for the periodic or triggered location request either from the AMF according to the procedure in clause 6.3.1 or from an earlier serving LMF according to this procedure. The service operation may also include the current status of event reporting (e.g. the number of event reports so far received from the UE and/or the duration of event reporting so far) and may include location related information for the UE such a previous location estimate or location measurements.
Step 7.
LMF2 informs LMF1 of the location context transfer operation results. LMF1 then releases all resources for the procedure.
Step 8.
LMF2 invokes the Namf_Communication_N1N2MessageTransfer service operation towards the AMF to request the transfer of a supplementary services Event Report Acknowledgment message to the UE. The Event Report Acknowledgment indicates a change of LMF and includes a deferred routing identifier indicating LMF2.
Step 9.
The AMF forwards the Event Report Acknowledgment to the UE in a NAS Transport message. The AMF also informs the LMF2 of the result of the delivery of the Event Report Acknowledgement.
Step 10.
If a location estimate is needed for event reporting, LMF2 may perform positioning of the UE and determines the UE location as at step 27 in clause 6.3.1. The rest of the procedure in clause 6.3.1 then continues from step 28 with LMF2 retaining state information to enable support of subsequent event reports from the UE.
Up

Up   Top   ToC