Tech-invite  3GPPspace  IETF RFCs  SIP
Quick  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   11…   11.5…   11.5.2…   11.5.3…   A…   B… 
10.9.3.8 Location management using functional alias  10.9.3.9 Usage of location history reporting procedure  10.9.3.9.1 General  10.9.3.9.2 Report location history procedure  10.9.3.9.3 Usage of status location history reporting procedure  10.9.3.9.4 Usage of cancel location history reporting procedure 
...

 

10.9.3.8  Location management using functional alias |R16|  Word‑p. 194

10.9.3.8.1  Client-triggered one-time location information report  Word‑p. 194
Figure 10.9.3.8.1-1 illustrates the procedure when a location management client requests one-time location information from other location management clients for location information reporting using functional alias, which can be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are reported.
Pre-conditions:
  1. MC service client 2 and MC service client 3 share the same functional alias.
  2. MC service client 2 and MC service client 3 activated the functional alias.
  3. MC service client 1 may have an activated functional alias.
  4. The location management server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.8.1-1: One-time location information report for shared functional alias
Figure 10.9.3.8.1-1: One-time location information report for shared functional alias
(⇒ copy of original 3GPP image)
Up
Step 1.
Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a one-time location report procedure which shall retrieve the location information of the MC service users that may share the contained functional alias. Location management client 1 may include its own activated functional alias.
Step 2.
Location management server checks whether location management client 1 is authorized to send a location reporting trigger.
Step 3.
The location management server uses on-demand location reporting procedures. The location information request contains the functional alias provided by the location management client 1 to address location management client 2 and location management client 3.
Step 4.
Upon receiving the report, the location management server updates location of the reporting location management clients. If the location management server does not have location information of a reporting location management client before, then just stores the reporting location information for that location management client.
Step 5.
The location management server sends location report responses to location management client 1 containing the provided location information for each location management client using the given functional alias. If the optional MC service UE label is present, the location management server sends it, as part of the location report response to location management client 1. If not all location management clients immediately respond to the location management server, i.e. other reports some time later, subsequent location reporting responses may be sent.
Up
10.9.3.8.2  Client-triggered periodic location information report  Word‑p. 195
Figure 10.9.3.8.2-1 illustrates the procedure when a location management client requests periodic location information from other location management clients for location information reporting using functional aliases which may be shared between several MC service users. Under this condition, the actual location of all MC service users sharing the same functional alias are reported.
Pre-conditions:
  1. MC service client 2 and MC service client 3 share the same functional alias.
  2. MC service client 2 and MC service client 3 activated the functional alias.
  3. MC service client 1 may have an activated functional alias.
  4. The location management server has subscribed to the functional alias controlling MC service server within the MC system for functional alias activation/de-activation updates.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.8.2-1: Periodic location information report for shared functional alias
Figure 10.9.3.8.2-1: Periodic location information report for shared functional alias
(⇒ copy of original 3GPP image)
Up
Step 1.
Location management client 1 sends a location reporting trigger, limited to one MC service at the time, to the location management server to activate a periodic location reporting procedure which shall retrieve the location information of the MC service users sharing the contained functional alias. Location management client 1 may include its own activated functional alias.
Step 2.
Location management server checks whether location management client 1 is authorized to send a location reporting trigger.
Step 3.
Depending on the information given by the location reporting trigger, the location management server uses event-triggered location information procedure and immediately send location information request to the location management clients that contains the functional alias requested by the location management client 1.
Step 4.
Upon receiving the reports, the location management server updates location of the reporting location management clients.
Step 5.
Based on the received location information reports, the location management server will periodically issue location report responses, one for each location management client at a time, encompassing the MC service ID, the associated functional alias, the individual location information of the addressed MC service ID and the optional MC service UE label, if present.
Up

10.9.3.9  Usage of location history reporting procedure |R17|  Word‑p. 196

10.9.3.9.1  General  Word‑p. 196
The location management client may get into a state not reporting 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 procedure  Word‑p. 196
10.9.3.9.2.1  On-demand report location history procedure (LMC - LMS)  Word‑p. 196
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.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.2.1-1: On-demand based usage of report location history procedure (LMC - LMS)
Figure 10.9.3.9.2.1-1: On-demand based usage of report location history procedure (LMC - LMS)
(⇒ copy of original 3GPP image)
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 procedure  Word‑p. 197
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.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.2.2-1: On-demand based usage of report location history procedure
Figure 10.9.3.9.2.2-1: On-demand based usage of report location history procedure
(⇒ copy of original 3GPP image)
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
10.9.3.9.3  Usage of status location history reporting procedure  Word‑p. 198
10.9.3.9.3.1  Status location history reporting procedure (LMC - LMS)  Word‑p. 198
The location management client can report the status of stored location information at any time to the location management server, following a return to report location information to the location management server.
Figure 10.9.3.9.3.1-1 illustrates the procedure for the usage of the status reporting from the location management client.
Pre-conditions:
  1. The location management client has returned to report location information and has stored location information reports.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.3.1-1: Status location history reporting procedure (LMC - LMS)
Figure 10.9.3.9.3.1-1: Status location history reporting procedure (LMC - LMS)
(⇒ copy of original 3GPP image)
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.
The location management client reports without a status request the status of the stored location information to the location information server.
10.9.3.9.3.2  On-demand status location history reporting procedure (LMS - LMC)  Word‑p. 199
The location management server can request the status of 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.3.2-1 illustrates the procedure for the on-demand based usage of requesting the status of the stored location information from the location management client.
Pre-conditions:
  1. The location management client has returned to report location information and has stored location information reports.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.3.2-1: On-demand based usage of status location history reporting procedure (LMS - LMC)
Figure 10.9.3.9.3.2-1: On-demand based usage of status location history reporting procedure (LMS - LMC)
(⇒ copy of original 3GPP image)
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.
The location management server requests the status of the stored location information from the location management client.
Step 3.
The location management client reports the status of the stored location information to the location information server.
10.9.3.9.3.3  On-demand status location history reporting procedure  Word‑p. 199
The MC service server or the location management client can request the status of stored location information at any time, following a return to report location information to the location management server.
Figure 10.9.3.9.3.3-1 illustrates the procedure for the on-demand based usage of the status location history reporting procedure.
Pre-conditions:
  1. The location management client 1 has returned to report location information and has stored location information reports.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.3.3-1: On-demand based usage of status location history reporting procedure
Figure 10.9.3.9.3.3-1: On-demand based usage of status location history reporting procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The MC service server or location management client 2 requests the status of the stored location information reports from the location management client 1.
Step 2.
The location management server checks the authorization of this request.
Step 3.
The location management server requests and receives the status report of the stored location information from location management client 1 according to the procedure described in clause 10.9.3.9.3.2 of the present document.
Step 4.
The location management server forwards this information to the MC service server or location management client 2.
Up
10.9.3.9.4  Usage of cancel location history reporting procedure  Word‑p. 200
10.9.3.9.4.1  General  Word‑p. 200
The location management server can request cancellation of the transmission of location information history reports at any time following the start of transmission by sending a location information history cancel request to the reporting location management client. The MC service server or location management client could initiate the cancellation request, if those entities are aware of ongoing location information history reporting. The transmission cancellation does not have any effect on the configured triggering criteria in emergency cases, triggering criteria in non-emergency cases nor on the triggering criteria in not reporting location information cases.
Up
10.9.3.9.4.2  Cancel location history reporting procedure (LMS - LMC)  Word‑p. 200
Figure 10.9.3.9.4.2-1 illustrates the procedure for the cancellation on location history reporting from the location management server to the location management client.
Pre-conditions:
  1. The location management client has returned to report location information and has stored location information reports.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.4.2-1: Cancel location history reporting procedure (LMS - LMC)
Figure 10.9.3.9.4.2-1: Cancel location history reporting procedure (LMS - LMC)
(⇒ copy of original 3GPP image)
Up
Step 1.
The location management client transmits stored location information while there is a communication link between the location management client and location management server.
Step 2.
The location management server requests the cancellation of the location information history reporting at any time during the transmission.
Step 3.
Location management client cancels the location information history reporting.
Step 4.
Location management client confirms the executed cancellation request.
10.9.3.9.4.3  Cancel location history reporting procedure  Word‑p. 201
Figure 10.9.3.9.4.3-1 illustrates the procedure for the cancellation on location history reporting from the MC service server or location management client to the location management server.
Pre-conditions:
  1. The location management client 1 has returned to report location information and has stored location information reports.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 10.9.3.9.4.3-1: Cancel location history reporting procedure
Figure 10.9.3.9.4.3-1: Cancel location history reporting procedure
(⇒ copy of original 3GPP image)
Up
Step 1.
The location management client 1 transmits stored location information while there is a communication link between the location management client and location management server.
Step 2.
The MC service server or location management client 2 requests the cancellation of the location information history reporting at any time during the transmission.
Step 3.
The location management server checks the authorization of this request and decides either to cancel the transmission from the reporting location management client 1 as described in clause 10.9.3.9.4.2, to cancel the transmission from the location management server or to cancel the transmission from both.
Step 4.
The location management server executes the requested cancellation.
Step 5.
Location management server confirms the executed cancellation.
Up

Up   Top   ToC