Content for &nbsp; TS 23.434 &nbsp; Word version:&nbsp; 19.3.0

The LM Server receives a location reporting trigger from VAL server and activates a location reporting procedure as defined in clause 9.3.5.

Figure 9.3.15-1: Location service registration procedure

The Fused Location Function determines a mapping of the vertical location services to a location service profile based on the location request information, the location profiles and the location capability of VAL UE which registered to the LM Server before.

Step 3a.

The LM Server requests from the LMC the location information of the target VAL UE optionally with the requested location information (the access type, positioning method) based on the determined location profiles in LM server obtained in step 2.

Step 3b.

The LM Client responds to the LM Server the location report based on the request.

Step 4.

The LM Server performs a location information request to one or more of the following (based on the location profile):

to GMLC directly or via NEF (as defined in TS 23.273), acting as AF.
to 3rd party location servers.

Step 5.

The Fused Location Function calculates the location information based on combined location reports from step 3~4 and checks whether the location reports fulfil the location profile requirements.

Step 6-7.

If the requirements are not fulfilled, the LM Server will repeat the step 3~5 iteratively to request location information and re-check whether the requirements are met or not.

Step 8.

If the requirements are fulfilled, the LM Server sends the location information report to the VAL server.

9.3.15 Location service registration procedure |R18| p. 94

Before the Location Management Server requesting the location information for the target UE, the Location Management Client may register the available location services to the LM Server to report the UE's location capabilities.

Figure 9.3.15-1 illustrates the procedure of client-triggered location service registration.

Reproduction of 3GPP TS 23.434, Fig. 9.3.15-1: Location service registration procedure

The LM Client of a VAL UE sends location service registration request to the LM Server, with the identifier of the UE (e.g. GPSI) and UE-based location capabilities.

The LM Server checks authorization for the VAL UE's registration request.

Figure 9.3.16-1: Location information unsubscribe procedure

After successful authorization, LM Server sends location service registration response to the LM Client and stores the UE identifier information and location capabilities.

9.3.16 Location information unsubscribe procedure |R18| p. 94

Figure 9.3.16-1 illustrates the high level procedure of location information unsubscribe request. The same procedure can be applied for the location management client and other entities that would like to unsubscribe to the VAL UE's location information.

Reproduction of 3GPP TS 23.434, Fig. 9.3.16-1: Location information unsubscribe procedure

The VAL server sends location information unsubscribe request to the location management server to unsubscribe the subscription to the VAL UE's location information.

Figure 9.3.17-1: Monitor location unsubscribe procedure

The location management server replies with location information unsubscribe response indicating the unsubscribe status.

9.3.17 Monitor location unsubscribe procedure |R18| p. 95

Figure 9.3.17-1 illustrates the high level procedure of location monitoring unsubscribe request. The same procedure can be applied for other entities that would like to unsubscribe the subscription to monitor the VAL UE's location in a given area of interest.

Reproduction of 3GPP TS 23.434, Fig. 9.3.17-1: Monitor location unsubscribe procedure

The VAL server sends Monitor location unsubscribe request to the location management server to unsubscribe the subscription to monitor the VAL UE's location in a given area of interest.

Figure 9.3.18-1: Location service registration update procedure

The location management server replies with Monitor location unsubscribe response indicating the unsubscribe status.

9.3.18 Location service registration update procedure |R18| p. 95

Figure 9.3.18-1 illustrates the procedure of client-triggered location service registration update. The Location Management Client may update its supported location capabilities (e.g. location access type, position methods) which has registered to the Location Management Server before.

Pre-condition:

The Location Management Client has registered to the Location Management Server.

Reproduction of 3GPP TS 23.434, Fig. 9.3.18-1: Location service registration update procedure

The LM Client decides to trigger the registration update request to LM Server to update the location capabilities which have registered to the LM Server before.

The LM Client sends location service registration update request to the LM Server with the identifier of the VAL UE, the VAL service ID and updated location capabilities.

Figure 9.3.19-1: Location service deregistration procedure

The LM server checks the authorization for the VAL UE's registration update request. If the authorization is successful, the LM server will update the UE's location capabilities received in step 2.

Step 4.

The LM Server sends location service registration update response to the LM Client.

9.3.19 Location service deregistration procedure |R18| p. 96

Figure 9.3.19-1 illustrates the procedure of client-triggered location service deregistration. By deresgistration, the Location Management Client may deregister the available location services which have registered to the Location Management Server before.

Pre-condition:

The Location Management Client has registered to the Location Management Server.

Reproduction of 3GPP TS 23.434, Fig. 9.3.19-1: Location service deregistration procedure

The LM Client decides to trigger the deresgistration request to LM Server to deregister the location services which have registered to the LM Server before.

The LM Client sends location service deregistration request to the LM Server with the identifier of the UE.

Figure 9.3.20-1: Adaptive location reporting configuration provisioning

The LM Server sends location service deregistration response to the LM Client and removes all registration information of the UE.

9.3.20 SEAL location management server provides adaptive configuration |R19| p. 97

Figure 9.3.20-1 illustrates procedure for SEAL LMS to provide adaptive location configuration suggestion to the VAL server for the VAL UE for which VAL server has requested for adaptive reporting (as specified in clause 9.3.5).

Pre-conditions:

The VAL server has requested to SEAL LMS to suggest adaptive configuration for VAL UE;
The VAL server has provided endpoint information in the Location reporting trigger to the SEAL LMS.
The SEAL LMS has received location reports from SEAL client and based on the different information the SEAL LMS as determined the new/adaptive location configuration.

Reproduction of 3GPP TS 23.434, Fig. 9.3.20-1: Adaptive location reporting configuration provisioning

The SEAL LMS sends a message to the VAL server (or authorized SEAL LM client). The message includes UE identity and suggested updates for location reporting trigger configuration.

Figure 9.3.21.1-1: Location tracing configuration procedure

Upon receiving the request from the SEAL LMS, the VAL server (or authorized SEAL LM client) sends a response message. The response message includes whether the VAL server accepts or rejects the updated location reporting configuration suggestion or not. If the VAL server accepts the location reporting configuration as suggested by the SEAL LMS, then the SEAL LMS updates the location reporting configuration to the SEAL LM client of the target UE.

9.3.21 Location history querying procedure |R19| p. 97

9.3.21.1 Location tracing configuration create procedure p. 97

Figure 9.3.21.1-1 illustrates the high level procedure of creating location tracing configuration from VAL server to the LM server.

Reproduction of 3GPP TS 23.434, Fig. 9.3.21.1-1: Location tracing configuration procedure

The VAL server sends a location tracing configuration request to the LM server to configure the location tracing service in advance. The location tracing configuration request may contain the geographical area for history location tracing, events/conditions for triggering the location history report, location QoS, the identities for the UE and service, the time till when the SEAL LM needs to store the location history data and the required positioning method(s) , etc.

The LM server checks whether the VAL server is authorized to request the location tracing configuration service. If the request is approved, the LM server stores the configuration received in step 1. If the request includes multiple UEs, the LM server creates and stores the contexts for each UE.

Figure 9.3.21.2-1: Location history request procedure

The LM server sends the location tracing configuration responses to the VAL server.

9.3.21.2 Location history request procedure p. 98

Figure 9.3.21.2-1 illustrates the high level procedure of location history request which the VAL server triggers to query the history location data for some specific UEs in some specific conditions.

Pre-conditions:

The location management server has obtained the UE location data from multiple sources as defined in clause 9.3.3 and clause 9.3.5 periodically based on the event triggers or conditions received in the request of step 1 in clause 9.3.21.1.

Reproduction of 3GPP TS 23.434, Fig. 9.3.21.2-1: Location history request procedure

The VAL server sends a location history request to the LM server with the specific conditions (e.g. the given location area, time/period, etc.) to query the history location data for a single UE or multiple UEs.

The LM server checks the authorization for the request. If the request is authorized, the LM server matches the obtained UE location data with the location history request. Before the match, the LM server may transform the obtained UE location data into the same format of the location area information received in step 1 if needed.

Figure 9.3.21.3-1: Location tracing configuration cancel procedure

The LM server sends a location history response to the VAL server with the matched UE location information. If there is no matched UE location data, the failure reason can be included.

9.3.21.3 Location tracing configuration cancel procedure p. 99

Figure 9.3.21.3-1 illustrates the high level procedure of location tracing configuration cancel request which the VAL server triggers to cancel the location tracing configuration for a single UE or multiple UEs.

Reproduction of 3GPP TS 23.434, Fig. 9.3.21.3-1: Location tracing configuration cancel procedure

If the VAL server decides to stop the location tracing services for the UE(s), it sends a location tracing configuration cancel request to the LM server with the UE identities.

The LM server stops getting the UE's location and deletes the stored UE location data and the location tracing configuration for the service.

Figure 9.3.22-1: Surrounding UE(s) retrieval procedure

The LM server sends location tracing configuration cancel response to the VAL server.

9.3.22 Surrounding UEs retrieval procedure |R19| p. 100

Figure 9.3.22-1 illustrates the procedure of surrounding UE(s) retrieval. The LM server can use this procedure to know how many UE(s) are close to the requested UE hosting the LM client, and their identities.

Reproduction of 3GPP TS 23.434, Fig. 9.3.22-1: Surrounding UE(s) retrieval procedure

The LM server decides to Surrounding UE retrieval request to the LM client. The request may include surrounding UE retrieval method.

The LM client obtains UE(s) close to itself. The LM client considers the surrounding UE retrieval method (if received) during the obtaining procedure.