Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

10.9.3.9  Usage of location history reporting procedure |R17|p. 205

10.9.3.9.1  Generalp. 205
The location management client may get into a state where it cannot report location information to the location management server at any time after the initial location reporting configuration was provided by the location management server. If any location information trigger criterion applies, while not reporting location information to the location management server, the location management client stores the corresponding location information.
Trigger criteria while not reporting location information to the location management server may vary from trigger criteria while reporting location information to the location management server. Such trigger criteria may for example include not reported distance travelled, not reported elapsed time, not reported call initiation, not reported emergency alert, not reported emergency group call, not reported imminent peril group call and not reported emergency private call.
Up
10.9.3.9.2  Report location history procedurep. 205
10.9.3.9.2.1  On-demand report location history procedure (LMC - LMS)p. 205
The location management server can request stored location information at any time from the location management client, following a return to report location information to the location management server.
Figure 10.9.3.9.2.1-1 illustrates the procedure for the on-demand based usage of location information history reporting from the location management client to the location management server.
Pre-conditions:
  1. The location management client is configured to store location information, while not reporting location information to the location management server.
  2. The location management client has stored location information based on triggering criteria in not reporting location information cases.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.9.2.1-1: On-demand based usage of report location history procedure (LMC - LMS)
Up
Step 1.
The location management client returns to report location information while there is a communication link between the location management client and location management server.
Step 2.
Location management server requests the stored location information.
Step 3.
The location management client responds to the location management server with one or several stored location information history reports.
Step 4.
The location management server updates the available location information with one or several stored location information and the optional MC service UE label, if present, from the location management client.
Up
10.9.3.9.2.2  On-demand report location history procedurep. 206
The location management server can request stored location information at any time from the location management client, following a return to report location information to the location management server. The MC service server or the location management client may initiate the request of stored location information.
Figure 10.9.3.9.2.2-1 illustrates the procedure for the on-demand based usage of location history reporting.
Pre-conditions:
  1. The location management client 1 is configured to store location information, while not reporting location information to the location management server.
  2. The location management client 1 has stored location information based on triggering criteria in not reporting location information cases.
  3. The location management server may have none, a subset or all available stored location information reports from location management client 1.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.9.2.2-1: On-demand based usage of report location history procedure
Up
Step 1.
The MC service server or the location management client 2 initiate the location information history request to the location management server.
Step 2.
The location management server checks the authorization of this request and compares the location information history request with the already retrieved stored location information from location management client 1.
Step 3.
The location management server requests stored location information from location management client 1 according to the procedure described in clause 10.9.3.9.2.1 of the present document, if the desired stored location information is not available on the location management server.
Step 4.
The location management server reports the requested stored location information to the MC service server or location management client 2. The location management server reports the optional MC service UE label, if present, to the location management client 2.
Up

Up   Top   ToC