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.
The SEAL LMS sends a message to the VAL server (or authorized SEAL location management client). The message includes UE identity and suggested updates for location reporting trigger configuration.
Upon receiving the request from the SEAL LMS, the VAL server (or authorized SEAL location management 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 location management client of the target UE.
The VAL server sends a location tracing configuration request to the location management 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 location management server checks whether the VAL server is authorized to request the location tracing configuration service. If the request is approved, the location management server stores the configuration received in step 1. If the request includes multiple UEs, the location management server creates and stores the contexts for each UE.
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.
The VAL server sends a location history request to the location management 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 location management server checks the authorization for the request. If the request is authorized, the location management server matches the obtained UE location data with the location history request. Before the match, the location management server may transform the obtained UE location data into the same format of the location area information received in step 1 if needed.
The location management 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.
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.
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 location management server with the UE identities.
The location management 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.21.4.1-1 illustrates the high level procedure of provisioning the off-network location positioning and report configuration from location management server to the location management client. This procedure is also used to update the configuration.
The location management server sends an Off-network location positioning and report configuration request to the location management client to configure the off-network location positioning and report policy to be used later. The request includes events/conditions for triggering the location history report, requested location type (i.e., absolute location or relative location), location QoS, the required positioning mechanism (i.e., UE-only Operation SL/Ranging), time duration for the off-networking positioning and report.
The location management client checks whether the VAL server is authorized to configure off-network location positioning and report policy. If the request is approved, the location management client stores the configuration received in step 1.
Figure 9.3.21.4.2-1 illustrates the high level procedure of reporting the cached history location result to the location management server.
Pre-condition:
The location management client is configured with the off-networking location positioning and report policy.
The Off-network location positioning trigger is met, e.g., the reference VAL UE which hosts the location management client detects it is in off-network and the target VAL UE identified by the target UE identity is also in off-network.
The location management client checks whether it is within the valid period as indicated by the time duration if configured. If yes, the location management client initiates the UE-only Operation SL/Ranging as described in TS 23.586, obtains its own location or the target VAL UE location, and caches the location result with time stamp. This step may be performed periodically as configured.
When the connectivity is back and it is within the valid period as indicated by the time duration, the location management client sends the Off-network history location result to the location management server.
Figure 9.3.22-1 illustrates the procedure of surrounding UE(s) retrieval. The location management server can use this procedure to know how many UE(s) are close to the requested UE hosting the location management client, and their identities.
The location management server decides to Surrounding UE retrieval request to the location management client. The request may include surrounding UE retrieval method.
The location management client obtains UE(s) close to itself. The location management client considers the surrounding UE retrieval method (if received) during the obtaining procedure.