Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   5   6…   6.4…   6.5…   6.5.3…   7…   8…   8.2.2…   9…   9.3…   9.3.2.21…   9.3.3…   9.3.6…   9.3.11…   9.3.13…   9.3.14…   9.4…   9.4.6…   9.5…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.3.10…   10.4…   11…   11.3…   11.3.3…   11.4…   12…   12.3…   13…   14…   14.2.2.2…   14.3…   14.3.2.20…   14.3.2.40…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6   14.3.4.7…   14.3.4A…   14.3.4A.3…   14.3.4A.4…   14.3.4A.6…   14.3.4A.8…   14.3.4A.9…   14.3.4A.10…   14.3.5…   14.3.6…   14.3.9…   14.3.12…   14.4…   15…   16…   17…   18…   A   B…

 

9.3.6  Location reporting triggers configuration cancelp. 77

Figure 9.3.6-1 illustrates the procedure used for cancelling the location reporting triggers configuration at the target Location management client.
Pre-conditions:
  1. The location management server has subscribed the location management client 2 location with the location reporting event triggers.
  2. If multicast delivery mode is used, the MBMS bearer being used is activated by the location management server.
Reproduction of 3GPP TS 23.434, Fig. 9.3.6-1: Location reporting triggers configuration cancel
Up
Step 1.
The location management client 1 (authorized VAL user or VAL UE) or VAL server sends a location reporting configuration cancel request to the location management server (1a). The location management server sends the location reporting configuration cancel request to the location management client 2 to stop receiving the UE location information (1b). This message can be sent via unicast or multicast.
Step 2.
The location management client invalidates the location reporting triggers configuration and no longer reports its location to the location management server.
Step 3.
The location management client 2 sends the location reporting configuration cancel response to the location management server (3a) as an acknowledgement. The location management server sends the location reporting configuration cancel response to the location management client 1 (3b) as an acknowledgement.
Up

9.3.7  Location information subscription procedurep. 77

Figure 9.3.7-1 illustrates the high level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to VAL user or VAL UE location information. This procedure is also used for initiating tracking a UE's location. The procedure considers target UE location information provided by its surrounding UEs, the procedure can improve location accuracy and can be used also for target UE temporarily out of 3GPP radio coverage. LM client 1 is used as example in the figure as target UE that the VAL server is interested to know its location information.
Reproduction of 3GPP TS 23.434, Fig. 9.3.7-1: Location information subscription request procedure
Up
Step 1.
The VAL server sends a location information subscription request to the location management server to subscribe location information of one or more VAL users or VAL UEs. The request may include an indication for supplementary location information, the location QoS which contains the location accuracy, response Time and QoS class as defined in clause 4.1b of TS 23.273, the velocity information of target UEs, and an indication whether the statistic of target UE location is needed per e.g., temporal/spatial granularity. If the indication whether the statistic of target UE location is needed, the corresponding time/location information should also be included. In addition, the VAL server may request velocity information of the VAL UEs/Users in step 1.
Step 2.
The location management server shall check if the VAL server is authorized to initiate the location information subscription request and may retrieve the available and proper location access type and positioning methods (e.g. as described in TS 23.273 and TS 29.572) for the target VAL UE based on the received location QoS. Further, the location management server may initiate location reporting configuration optionally including the retrieved location access type and positioning methods with the location management client of the UE for immediate reporting.
Step 3.
The location management server may optionally subscribe for UE location information from 3GPP core network for the UE. If the indication for supplementary location information is included in step 1, then UE location information is obtained from the 3GPP core network and/or the 3rd party location management server.
If the velocity information of target UE is requested in step 1, the LM server asks the LM client or 3GPP core network to report the target UE location data with the requested velocity information.
Step 4.
The location management server determines the UE location information of the UE as received in steps 2 and 3 and checks if it meets the location QoS requirements (if any) or not.
If the indication whether the statistic of target UE location is included in step 1, the LM server performs the following actions based on different granularity.
If the indication whether the statistic of target UE location is needed per temporal granularity is included in step 1, the LM server calculates the UE location data received in step 3 per the temporal granularity with the requested time condition.
If the indication whether the statistic of target UE location is needed per spatial granularity is included in step 1, the LM server calculates the UE location data received in step 3 per the spatial granularity with the requested location information.
Step 5.
The LM server may optionally request the UE location from its surrounding UEs (as described in step 5 to 9). The LM server decides how to retrieve surrounding UEs which may be based on LM client 1 registered positioning method in location service registration. If the LM server decides to use UE-assisted surrounding UE retrieval, step 6 is executed; otherwise, NW-assisted surrounding UE retrieval is used as described in step 7.
Step 6.
The LM server requests the LM client 1 with an optional surrounding UE retrieval method (e.g. ProSe, BT, WiFi) to provide its surrounding UEs and the LM client 1 responds the LM server with VAL UE/User ID of discovered UEs as described in clause 9.3.22;
Step 7a.
The LM server derives an appropriate location area (where UE to UE communication is possible) internally using the location information of UE 1 (determined in step 4) as reference location. If the UE 1 location is last known UE location, the LM server uses UE mobility analytics service from 3GPP CN to derive UE location estimation for UE 1.
Step 7b.
The LM server uses 3GPP CN service (NEF service of Number of UEs present in a geographical area) to obtain all UEs within the derived location area in step 6.
Step 8.
The LM server selects a set of UEs (LM client 2..n) from UEs obtained in step 5 or step 7 based on registered location service information (e.g. positioning method) from LM client 2..n. Then LM server sends location request to LM client 2..n using On-demand location reporting procedure (as defined in clause 9.3.4) to obtain UE 1 location including an optional UE positioning method (e.g. PC5 SEAL LM, BT, WiFi) to be used to retrieve location.
Step 9.
The LM server takes the location information of UE 1 reported by LM client 2..n into consideration to calibrate UE 1 location determined in step 4.
Step 10.
The location management server replies with a location information subscription response indicating the subscription status and if immediate reporting was requested, the location information of the VAL UE(s).
Up

9.3.7a  Location information subscription update procedure |R19|p. 79

Figure 9.3.7a-1 illustrates the high level procedure for allowing a VAL server update an existing subscription about location information at the location management server.
Pre-conditions:
  • the VAL server has an active location information subscription at the location management server.
Reproduction of 3GPP TS 23.434, Fig. 9.3.7a-1: Location information subscription update procedure
Up
Step 1.
When the VAL server decides to update an active location information subscription, it sends a location information subscription update request to the location management server including the information specified in Table 9.3.2.5-1.
Step 2.
The location management server shall check if the VAL server is authorized to update the subscription.
Step 3.
If the VAL server is authorized to update the subscription, the location management server updates the location information subscription.
Step 4.
The location management server sends a location information subscription update response to the VAL server including the information as specified in Table 9.3.2.6-1.
Up

9.3.8  Event-trigger location information notification procedurep. 80

Figure 9.3.8-1 illustrates the high level procedure of event-trigger usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of VAL user or VAL UE. This procedure is also used for obtaining latest UE's location for tracking purpose.
Reproduction of 3GPP TS 23.434, Fig. 9.3.8-1: Event-trigger usage of location information procedure
Up
Step 1.
The location management server receives the latest location information of the UE as per the location report procedure described in clause 9.3.3.3.
Step 2.
The location management server may optionally receive the location information of the UE from 3GPP core and/or the 3rd party location management server network. If the indication for supplementary location information is included in the subscription, then UE location information is obtained from the 3GPP core network and/or the 3rd party location management server. If the velocity information of target UE is requested, the LM server asks the LM client or 3GPP core network to report the target UE location data with the requested velocity information.
Step 3.
Based on the configurations, e.g., subscription, periodical location information timer, location management server is triggered to report the latest user location information to VAL server. The location management server determines the location information of UE as received in steps 1 and 2, including the supplementary location information (if indicated). The Location management server may report the location to the VAL server considering the location information received via non-3GPP positioning technologies (e.g. GNSS, Bluetooth), for instance, to improve the location accuracy. The location management server may reuse the stored and valid UE location information (if any) to report to the VAL server/LM client to reduce the response time when the trigger condition is time-based.
If the indication whether the statistic of target UE location is included in the request from the VAL server/LM client, the LM server calculates the received UE location data per temporal/spatial granularity as requested and then expose them to the VAL server/LM client for the valued-added location information.
Step 4.
Same as step 5-9 of Figure 9.3.7-1.
Step 5.
The location management server sends the location information report including the latest location information of one or more VAL users or VAL UEs to the VAL server or to the location management client that has previously configured. In addition, velocity of the requested VAL UEs may be included as part of the location information report.
Step 6.
VAL server may further share this location information to a group or to another VAL user or VAL UE.
Up

9.3.9  On-demand usage of location information procedurep. 81

The VAL server can request UE location information at any time by sending a location information request to the location management server, which may trigger location management server to immediately send the location report.
Figure 9.3.9-1 illustrates the high level procedure of on demand usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of VAL user or VAL UE.
Reproduction of 3GPP TS 23.434, Fig. 9.3.9-1: On-demand usage of location information procedure
Up
Step 1.
VAL server sends a location information request to the location management server which may include the location QoS that contains the location accuracy, response Time and QoS class as defined in clause 4.1b of TS 23.273.
Step 2.
The location management server checks if there is stored and valid UE location report (e.g. the timer for the stored UE location report is not expired) for the target UE. If available, it reuses the stored UE location information and reports it to the VAL server. If there isn't, it acquires the latest location of the UEs being requested, by triggering an on-demand location report procedure as described in subclause 9.3.4, or from PLMN operator, and checks if the obtained location of the VAL UE could meet the location QoS requirements (if any).
Step 3.
Then, location management server immediately sends the location information report including the latest location information acquired of one or more VAL users or VAL UEs. The Location management server may report the location to the VAL server considering the location information received via non-3GPP positioning technologies (e.g. GNSS, Bluetooth), for instance, to improve the location accuracy.
Step 4.
VAL server may further share this location information to a group or to another VAL user or VAL UE.
Up

9.3.10  Obtaining UE(s) information at a location |R17|p. 82

Figure 9.3.10-1 describes the procedure for obtaining UE(s) information at a location. This procedure also applies for the Geofencing service that the VAL server may request the UE(s) information when the UE entering the Geofencing location area.
Pre-condition:
  • The VAL server has a jurisdiction over a geographical area for which the location management server is configured to operate.
  • The UE(s) in the geographical area have provided its location information to the location management server.
  • The location management server has obtained the requested UE location information either from 3GPP CN or the target location management client/VAL UE.
Reproduction of 3GPP TS 23.434, Fig. 9.3.10-1: Obtaining UE(s) information at a location
Up
Step 1.
The consumer (VAL server or group management server) sends get UE information request to the location management server. The request contains the location information (e.g. geographic area, VAL service area identified by the VAL service area ID, Geofencing location area represented by different types of shape, etc) and and application defined proximity range as defined in table 9.3.2.9-1.
Step 2.
The location management server authorizes the request and determines the VAL UE(s) or VAL User(s) whose location are within the application defined proximity range of the location information or VAL service area identified by the VAL service area ID or Geofencing location area provided in step 1.
Step 3.
The location management server sends get UE information response to the VAL server with a list of VAL UE(s) or VAL user(s) and its corresponding location information as determined in step 1.
Up

Up   Top   ToC