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.13  Procedures with interaction between 5GC and EPCWord-p. 74
6.13.1  MT-LR Procedure
Figure 6.13.1-1 illustrates network positioning requested by the LCS clients or the AF external to the PLMN for the case where the LCS Client or AF is associated with a GMLC in 5GC domain and the UE is served by the EPC domain. Both non-roaming and roaming scenarios are described. For non-roaming scenario both the case of separate EPC GMLC and 5GC GMLC connected with Lr reference point and the case with combined 5GC GMLC and EPC GMLC are described. For roaming scenario, the 5GC GMLC in the HPLMN uses NL3 to interconnect with the combined 5GC+EPCGMLC in the VPLMN.
Up
Step 1.
Steps 1-3 in clause 6.1.2 are performed.
Step 2.
For non-roaming case and if 5GC GMLC and EPC GMLC are combined, steps 2a and 2b are skipped. Otherwise the 5GC GMLC may derive an address of a EPC GMLC or 5GC+EPC GMLC, either received together with the network address of the current serving node) from the UDM/HSS in step 1, by internal configuration or by query to NRF.
Step 2a.
If an address of a EPC GMLC is derived, the 5GC GMLC then sends the Lr location request to the EPC GMLC. If the result of privacy check indicates that the notification (and verification) based on current location is needed, the 5GC GMLC shall send a location request to the VGMLC indicating "positioning allowed without notification".
Step 2b.
If an address of an 5GC+EPC GMLC is derived, the 5GC GMLC invokes a Ngmlc_Location_ProvideLocation service operation towards the 5GC+EPC GMLC. If the result of privacy check indicates that the notification (and verification) based on current location is needed, the 5GC GMLC invokes the service request indicating "positioning allowed without notification"
Step 3.
Steps 2-9 or 9b in TS 23.271, clause 9.1.15 are performed.
Step 4.
For non-roaming case and if 5GC GMLC and EPC GMLC are combined, step 4a and 4b are skipped. Otherwise the following applies:
Step 4a.
If step 2a was performed, the EPC GMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method to the 5GC GMLC.
Step 4b.
If step 2b was performed, the 5GC+EPC GMLC forwards the location estimation of the target UE, its age, its accuracy and optionally the information about the positioning method to the 5GC+EPC GMLC in a Ngmlc_Location_ProvideLocation service Response.
Step 5.
If the privacy check in step 1 indicates that further privacy checks are needed, the 5GC GMLC shall perform an additional privacy check in order to decide whether the 5GC GMLC can forward the location information to the LCS client or AF or send a notification if the result of the privacy check requires the notification and verification based on current location. One example when this additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations. When an additional privacy check is not needed, the (H)GMLC skips steps 6-8.
Step 6.
For non-roaming case and if5GC GMLC and EPC GMLC are combined, step 6a and 6b are skipped. Otherwise the following applies:
Step 6a.
If step 2a was performed and if the result of privacy checks in step 5 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the 5GC GMLC shall send a location request to the EPC GMLC indicating "notification only".
Step 6b.
If step 2b was performed and if the result of privacy checks in step 5 indicates that the notification (and verification) based on current location is needed, and in the case of roaming, the 5GC GMLC shall invokes a Ngmlc_Location_ProvideLocation service operation to the 5GC+EPC GMLC indicating "notification only".
Step 7.
The EPC post positioning notification and verification procedure in TS 23.271, clause 9.1.18 is performed.
Step 8.
For non-roaming case and if 5GC GMLC and EPC GMLC are combined, step 8a and 8b are skipped. Otherwise the following applies:
Step 8a.
If step 2a was performed, the EPC GMLC forwards an indication of the result of notification and verification procedure to the 5GC GMLC.
Step 8b.
If step 2b was performed, the 5GC+EPC GMLC forwards an indication of the result of notification and verification procedure to the 5GC GMLC.
Step 9.
Steps 24 in clause 6.1.2 are performed.
Up
6.13.2  MO-LR Transfer to a Third Party ProcedureWord-p. 75
Figure 6.13.2-1 illustrates the UE requesting its location to be sent to a Third Party (i.e. an external LCS Client) for the case where the LCS Client is associated with a GMLC in 5GC domain and the UE is served by the EPC domain. Both non-roaming and roaming scenarios are described. For non-roaming scenario both the case of separate 5GC GMLC and EPC GMLC connected with Lr reference point and the case with co-located 5GC GMLC and EPC GMLC are described. For roaming scenario, when the combined 5GC GMLC and EPC GMLC are deployed in the HPLMN, it uses NL3 to interconnect with the EPCGMLC in the VPLMN.
Up
Step 1.
Steps 1-6 in TS 23.271, clause 9.2.6 are performed.
Step 2.
For non-roaming case and if 5GC GMLC and EPC GMLC is combined, this step is skipped. Otherwise the EPC GMLC sends Location Update Notification Request towards to the 5GC GMLC including the information received in step 1.
Step 3.
Steps 9-10 in clause 6.2 are performed.
Step 4.
For non-roaming case and if 5GC GMLC and EPC GMLC are combined, this step is skipped. Otherwise if the identified LCS Client is not accessible, the EPC GMLC sends a Location Update Notification response to AMF with an appropriate error cause. Otherwise, the response shall include an acknowledgement. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step.
Step 5.
Steps 13-14 in TS 23.271, clause 9.2.6 are performed.
Up

Up   Top   ToC