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

The location management client sends location reporting configuration request message to the location management server.

The location management server sends location reporting configuration message to the location management client(s) containing the initial location reporting event triggers configuration (or a subsequent update) , e.g. minimum time between consecutive reports, SAI changes, access RAT changes, or ECGI changes for reporting the location of the VAL UE. This message can be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time.

Figure 9.3.3.3-1: Location reporting procedure

The location management client stores or updates the location reporting event triggers configuration. A location reporting event occurs, triggering step 3.

9.3.3.3 Location reporting p. 73

Figure 9.3.3.3-1 illustrates the procedure for location reporting.

Reproduction of 3GPP TS 23.434, Fig. 9.3.3.3-1: Location reporting procedure

The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the location management client.

Figure 9.3.3.4-1: Location reporting configuration update procedure

Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client.

9.3.3.4 Update Location reporting configuration |R18| p. 74

The location management server may update the location reporting configuration information and inform the location management client of the update ones at any time by triggering the location reporting configuration update procedure.

Figure 9.3.3.4-1 illustrates the procedure for location reporting configuration update.

Reproduction of 3GPP TS 23.434, Fig. 9.3.3.4-1: Location reporting configuration update procedure

Based on the local configurations or the location information request from other entities (e.g., another location management client, VAL server) or if the VAL server updates the geographical location information of the existing VAL service area ID and there is triggering criteria corresponding to the updated VAL service area ID, the location management server decides to update the location reporting configuration and informs the updated information to the location management client.

The location management server sends location reporting configuration update request message to the location management client(s) which may contain the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. This message can be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time. If the location reporting trigger from VAL server contains the triggering criteria based on the VAL service area ID, then the location management server converts those triggers into geographical area based triggers while sending it to the location management client.

Figure 9.3.4-1: On-demand location information reporting procedure

The location management client(s) reply with location reporting configuration update response to the location management server with the update result.

Step 4.

The location management client stores or updates the new location reporting configuration received in step 2.

9.3.4 On-demand location reporting procedure p. 74

The location management server can request UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report.

Reproduction of 3GPP TS 23.434, Fig. 9.3.4-1: On-demand location information reporting procedure

Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client, VAL server), location management server initiates the immediately request location information from the location management client.

The location management server sends a location information request to the location management client.

Figure 9.3.5-1: Client-triggered location reporting procedure

If the target VAL UE ID or user ID is not equal to its own identity in the LM client, the LM client triggers off-network location management procedures as described in clause 9.5 to obtain target VAL UE location. If the received UE positioning method is PC5 SEAL LM, target VAL UE location information (including velocity) is obtained via off-network procedure as defined in clause 9.5; if the received UE positioning method is non-3GPP (e.g. WiFi, BT), target VAL UE location information (including velocity) is obtained via the corresponding non-3GPP method. If the target VAL UE ID or user ID is equal to its own identity in the LM client, VAL user or VAL UE is notified and asked about the permission to share its location. VAL user can accept or deny the request.

Step 4.

The location management client immediately responds to the location management server with a report containing location information identified by the location management server and available to the location management client.

Step 5.

9.3.5 Client-triggered or VAL server-triggered location reporting procedure p. 75

Figure 9.3.5-1 illustrates the high level procedure of client-triggered or VAL server-triggered location reporting.

Reproduction of 3GPP TS 23.434, Fig. 9.3.5-1: Client-triggered location reporting procedure

Location management client 2 (authorized VAL user or VAL UE) or VAL server sends a location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client 1. The location reporting event triggers as specified in Table 9.3.2.4-1, e.g. minimum time between consecutive reports, SAI changes, access RAT changes, or ECGI changes for reporting the location of the VAL UE, are included.

Location management server checks whether location management client 2 or VAL server is authorized to send a location reporting trigger. If the immediate report indicator is included in step 1 and there is valid location report of the target UE (i.e. the timer for the stored location report is not expired), the LM server reuses the stored UE location report and sends the report to the location management client 2 or VAL server.

If the adaptive reporting is requested in step 1, the location management server interacts with NWDAF (e.g., UE mobility analytics as defined in clause 6.7.2 of TS 23.288) to obtain the location management client 1 moving statistic and prediction
1. If "DIRECT UPDATE" is requested, the location management server determines the reporting configuration based on VAL service ID, VAL server ID, and the retrieved location management client 1 moving statistic and prediction. In order to adapt the configuration, the location management server may determine, for example, whether to increase or decrease the frequency of the report based on the UE's mobility pattern, or update location change condition (e.g., to change the location accuracy).
2. If "SUGGESTIVE UPDATE" is requested, the location management server initially uses the configuration provided by VAL server and later dynamically adjusts the reporting configuration to determine adaptive location configuration based on VAL service ID, VAL server ID, and by analysing the retrieved location management client 1 moving statistic and prediction and received location information. In order to adapt the configuration, the location management server may determine, for example, whether to increase or decrease the frequency of the report based on the UE's mobility pattern, or update the location change condition (e.g., to change the location accuracy).
If the valid location report is not available, depending on the information specified by the location reporting trigger or determined reporting configuration (if "DIRECT UPDATE" is requested), location management server initiates an on-demand location reporting procedure or an event-triggered location reporting procedure for the location of location management client 1.