10.9.3 Procedure

23.2803GPPCommon functional architecture to support mission critical servicesRelease 18Stage 2TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

10.9.3.1 Event-triggered location reporting procedure

NOTE 1: This procedure is valid for single MC system operation only.

The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the location management server. The decision to report location information can be triggered at the location management client by different conditions. The conditions could include, for example, the reception of the location reporting configuration, initial registration, distance travelled, elapsed time, cell change, MBMS SAI change, MBMS session change, leaving a specific MBMS bearer service area, tracking area change, PLMN change, call initiation, or other types of events such as emergency alert, emergency call or imminent peril calls. The location report can include information described as time of measurement, accuracy, longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs.

Figure 10.9.3.1-1: Event-triggered location reporting procedure

1. The location management server sends location reporting configuration message to the location management client(s) containing the initial configuration (or a subsequent update) for reporting the location of the MC service 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.

NOTE 2: The location reporting configuration information can be made part of the user profile, in which case the sending of the message is not necessary.

NOTE 3: Different location management clients may be given different location reporting criteria.

2. A location reporting event occurs, triggering step 3.

3. 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.

4. 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. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.

10.9.3.2 On-demand location reporting procedure

NOTE: This procedure is valid for single MC system operation only.

The location management server can request MC service 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.

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

1. Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client, MC service server), location management server initiates the immediate request of location information to be sent from the location management client.

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

3. MC service user is notified and asked for permission to share location information. MC service user can accept or deny the request.

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.

5. 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, the location management server just stores the reporting location information for that location management client. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.

10.9.3.3 Client-triggered location reporting procedure

NOTE: This procedure is valid for single MC system operation only.

Figure 10.9.3.3-1 illustrates the high level procedure of client-triggered location reporting.

Figure 10.9.3.3-1: Client-triggered location reporting procedure

1. Location management client 2 (authorized MC service user) 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.

2. Location management server checks whether location management client 2 is authorized to send a location reporting trigger. Depending on the information specified by the location reporting trigger, 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.

10.9.3.4 Location reporting cancel procedure

NOTE: This procedure is valid for single MC system operation only.

The location reporting cancel procedure reuses the information flow of location reporting configuration.

Pre-conditions:

– The location management client has been provided with location reporting configuration information.

Figure 10.9.3.4-1: Location reporting cancel procedure

1. The location management server sends location reporting configuration without any information element to the location management client to stop location reporting from the MC service UE.

2. The location management client stops sending location information reports to the location management server.

10.9.3.5 Location information subscription procedure

NOTE 1: This procedure is valid for single MC system operation only.

Figure 10.9.3.5-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 MC service user location information.

Figure 10.9.3.5-1: Location information subscription request procedure

1. MC service server or location management client sends a location information subscription request to the location management server to subscribe location information of one or more MC service users.

2. The location management server checks if the location management client is authorized to initiate the location information subscription request.

NOTE 2: As the MC service server is implicitly trusted, the Location management server needs not to check the authorization for the MC service server.

3. The location management server replies with a location information subscription response indicating the subscription status.

10.9.3.6 Usage of location information procedure

10.9.3.6.1 Event-trigger location information notification procedure

NOTE 1: This procedure is valid for single MC system operation only.

Figure 10.9.3.6.1-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 MC service user.

Pre-condition:

1. The MC service server or location management client has subscribed to the location information of a target MC service user.

Figure 10.9.3.6.1-1: Event-trigger usage of location information procedure

1. Based on configuration, e.g., subscription, periodical location information timer, the location management server is triggered to report the latest user location information of the target MC service user to the subscribed MC service server or subscribed location management client.

2. The location management server sends the location information notification including the latest location information of one MC service user to the MC service server or to the location management client. The latest location information is derived from the location report procedure as described in clause 10.9.3.1, or from PLMN operator (e.g. LCS network). If the optional MC service UE label is present, the location management server sends it, as part of the location information notification, to the MC service user.

NOTE 2: The MC service server does not receive the MC service UE label.

10.9.3.6.2 On-demand usage of location information procedure

NOTE 1: This procedure is valid for single MC system operation only.

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

Figure 10.9.3.6.2-1 illustrates the high level procedure of on-demand usage of location information. The same procedure can be applied for other entities that would like to subscribe to location information at the location management server of an MC service user.

Figure 10.9.3.6.2-1: On-demand usage of location information procedure

1. MC service server or location management client send a location information request to the location management server.

2. The location management server checks if the location management client is authorized to request the location information.

NOTE 2: As the MC service server is implicitly trusted, the Location management server needs not to check the authorization for the MC service server.

3. The location management server acquires the latest location of the MC service clients being requested, by triggering an on-demand location report procedure as described in clause 10.9.3.2, or from PLMN operator (e.g. LCS network).

4. Then, location management server immediately sends the location information report including the latest location information acquired of one MC service user to the MC service server or to the location management client. If the optional MC service UE label is present, the location management server sends it, as part of the location information report, to the MC service user.

NOTE 3: The MC service server does not receive the MC service UE label.

10.9.3.7 Location information cancel subscription procedure

NOTE: This procedure is valid for single MC system operation only.

Figure 10.9.3.7-1 illustrates the high level procedure of location information cancel subscription request. The MC service server or the location management client can request the cancellation of location information subscriptions at any time from the location management server.

Pre-conditions:

– The authorized MC service user is in possession of the MC service ID of the MC service user as well as the location information subscriptions of this MC service ID.

Figure 10.9.3.7-1: Location information cancel subscription request procedure

1. MC service server or location management client sends a location information cancel subscription request to the location management server to cancel the subscription for location information of one or more MC service users.

2. The location management server checks the authorization of this request.

NOTE: Whether the authorization check is a specific check of the requesting MC service user or is a general policy check is outside the scope of this procedure.

3. The location management server replies with a location information cancel subscription response indicating the cancel subscription status.

10.9.3.8 Location management using functional alias

10.9.3.8.1 Client-triggered one-time location information report

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.

Figure 10.9.3.8.1-1: One-time location information report for shared functional alias

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.

2. Location management server checks whether location management client 1 is authorized to send a location reporting trigger.

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.

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.

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.

10.9.3.8.2 Client-triggered periodic location information report

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.

Figure 10.9.3.8.2-1: Periodic location information report for shared functional alias

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.

2. Location management server checks whether location management client 1 is authorized to send a location reporting trigger.

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.

4. Upon receiving the reports, the location management server updates location of the reporting location management clients.

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.

NOTE 1: If a functional alias is deactivated for an MC service client, the corresponding location management client stops sending periodic location information reports.

NOTE 2: If a functional alias has been newly activated for an MC service client, the location management server activates location information reporting for this location management client.

NOTE 3: If a functional alias is simultaneously shared between several MC service IDs, all location management clients with the associated MC service IDs will send the location report until the functional alias status change, e.g. take-over, for the individual MC service ID.

10.9.3.9 Usage of location history reporting procedure

10.9.3.9.1 General

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.

10.9.3.9.2 Report location history procedure

10.9.3.9.2.1 On-demand report location history procedure (LMC – LMS)

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.

Figure 10.9.3.9.2.1-1: On-demand based usage of report location history procedure (LMC – LMS)

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.

2. Location management server requests the stored location information.

NOTE 1: The location management client may provide the status of the stored location information prior to the request from location management server.

3. The location management client responds to the location management server with one or several stored location information history reports.

NOTE 2: The transmission of requested stored location information does not interrupt the reporting of location information.

NOTE 3: The most recent stored location information that qualifies for transmission is transmitted first.

NOTE 4: The transmission may be stopped at any time with the cancel location history reporting procedure, according to the procedure described in clause 10.9.3.9.4 of the present document.

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.

10.9.3.9.2.2 On-demand report location history procedure

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.

Figure 10.9.3.9.2.2-1: On-demand based usage of report location history procedure

1. The MC service server or the location management client 2 initiate the location information history request to the location management server.

NOTE: The MC service server or the location management client 2 may request the status on stored location information from location management client 1, prior to the location information history request.

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.

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.

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.

10.9.3.9.3 Usage of status location history reporting procedure

10.9.3.9.3.1 Status location history reporting procedure (LMC – LMS)

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.

Figure 10.9.3.9.3.1-1: Status location history reporting procedure (LMC – LMS)

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.

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)

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.

Figure 10.9.3.9.3.2-1: On-demand based usage of status location history reporting procedure (LMS – LMC)

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.

2. The location management server requests the status of the stored location information from the location management client.

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

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.

Figure 10.9.3.9.3.3-1: On-demand based usage of status location history reporting procedure

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.

2. The location management server checks the authorization of this request.

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.

4. The location management server forwards this information to the MC service server or location management client 2.

10.9.3.9.4 Usage of cancel location history reporting procedure

10.9.3.9.4.1 General

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.

10.9.3.9.4.2 Cancel location history reporting procedure (LMS – LMC)

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.

Figure 10.9.3.9.4.2-1: Cancel location history reporting procedure (LMS – LMC)

1. The location management client transmits stored location information while there is a communication link between the location management client and location management server.

2. The location management server requests the cancellation of the location information history reporting at any time during the transmission.

3. Location management client cancels the location information history reporting.

4. Location management client confirms the executed cancellation request.

10.9.3.9.4.3 Cancel location history reporting procedure

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.

Figure 10.9.3.9.4.3-1: Cancel location history reporting procedure

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.

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.

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.

4. The location management server executes the requested cancellation.

5. Location management server confirms the executed cancellation.

10.9.3.10 Usage of location information across MC systems procedure

10.9.3.10.1 General

Interconnected MC systems in either the same security domain or different security domains share location information either through the direct connection of the location management servers or through the connected MC gateway servers.

10.9.3.10.2 On-demand request of location information procedure

The MC service server or location management client in the primary MC system can request MC service user’s location information, which is in the partner MC system, at any time by sending a location information request to the location management server at primary MC system.

Figure 10.9.3.10.2-1 illustrates the high level procedure of on-demand request of location information.

Figure 10.9.3.10.2-1: On-demand request of location information procedure

1. The MC service server or a location management client in the primary MC system requests on-demand location information of MC service user located in the partner MC system.

2. The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 1: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

3. The location management server in the primary MC system determines that the request has a target in a different MC system.

4. The location management server in the primary MC system sends the on-demand location information request to the location management server in the partner MC system.

5. The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 2: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

6. The location management server at partner MC system updates the location information, according to the procedure described in clause 10.9.3.2 or provides stored location information, based on the configuration for on-demand requests.

7. The location management server in the partner MC system sends the location information report, described in clause 10.9.2.2, to the MC service server or location information client in the primary MC system by utilizing the location management server in the primary MC system.

10.9.3.10.3 Event-triggered location information notification procedure

The location management client in the partner MC system provides, based on configuration, periodic location information, which will be also forwarded to the subscribed entities.

Figure 10.9.3.10.3-1 illustrates the high level procedure of event-triggered sharing of location information.

Figure 10.9.3.10.3-1: Event-triggered location information notification procedure

1. The location management client in the partner MC system is triggered, based on configuration, to send a location information report, according to described triggers in clause 10.9.3.1.

2. The location management server in the partner MC system checks if the provided information along with the configuration permit the report to proceed.

NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

3. The location management server in the partner MC system determines that the report has a target in a different MC system.

4. The location management server in the partner MC system sends the location information notification to the location management server in the primary MC system, according to the described information flow in clause 10.9.2.7.

5. The location management server in the primary MC system forwards the received location information, according to the procedure described in clause 10.9.3.6.1.

10.9.3.10.4 Location information subscription procedure

The location management client in the partner MC system provides, based on configuration, event triggered location information, which will be also forwarded to the subscribed entities.

Figure 10.9.3.10.4-1 illustrates the high level procedure of subscription to location information between interconnected MC systems.

Figure 10.9.3.10.4-1: Location information subscription procedure

1. The MC service server or the location management client in the primary MC system request subscription to event-triggered location information of MC service users in the partner MC system by sending a location information subscription request to the location management server in the primary MC system, according to the described information flows in clause 10.9.2.5.

2. The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 1: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

3. The location management server in the primary MC system determines that the request has a target in a different MC system.

4. The location management server in the primary MC system sends the location information subscription request to the location management server in the partner MC system, according to the described information flow in clause 10.9.2.5.

5. The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 2: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

6. The location management server in the partner MC system applies the subscription.

7. The location management server in the partner MC system sends the location information subscription response to the location management server in the primary MC system as well as the location management server in the primary MC system to the requested entity in the primary MC system, according to the described information flow in clause 10.9.2.6.

10.9.3.10.5 Location information cancel subscription procedure

The location management client in the primary MC system receives location information updates according to the subscriptions requested in the partner MC system. Those subscriptions can be cancelled anytime from the primary MC system.

Figure 10.9.3.10.5-1 illustrates the high level procedure of the subscription cancellation to location information between interconnected MC systems.

Figure 10.9.3.10.5-1: Location information cancel subscription procedure

1. The MC service server or the location management client in the primary MC system request the cancellation of subscriptions to event-triggered location information of MC service users in the partner MC system by sending location information cancel subscription requests to the location management server in the primary MC system, according to the described information flows in clause 10.9.2.8.

2. The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 1: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

3. The location management server in the primary MC system determines that the request has a target in a different MC system.

4. The location management server in the primary MC system sends the location information cancel subscription request to the location management server in the partner MC system, according to the described information flow in clause 10.9.2.8.

5. The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 2: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

6. The location management server in the partner MC system cancels the subscription.

7. The location management server in the partner MC system sends the location information cancel subscription response to the location management server in the primary MC system as well as the location management server in the primary MC system to the requested entity in the primary MC system, according to the described information flow in clause 10.9.2.9.

10.9.3.10.6 Location reporting temporary configuration procedure

An authorized MC service user in the primary MC system in charge of MC service users either currently completely or partially operating in a partner MC system is able to configure event-based location information for the involved MC service users at any time by sending configuration parameters. Those configuration parameters are temporarily used, while the configuration parameters of the primary MC system reinstated either by the configuration expiration criteria or by request from the authorized MC service user.

Figure 10.9.3.10.6-1 illustrates the high level procedure of location reporting temporary configuration procedure.

Figure 10.9.3.10.6-1: Location reporting temporary configuration procedure

1. The location management client in the primary MC system requests to configure the location reporting of MC service user(s) located in the partner MC system.

2. The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 1: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

3. The location management server in the primary MC system determines that the request has a target in a different MC system.

4. The location management server in the primary MC system sends the location reporting temporary configuration request to the location management server in the partner MC system.

5. The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.

NOTE 2: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.

6. The location management server in the partner MC system forwards the location reporting temporary configuration request to the location management client in the partner MC system. The location management server in the partner MC system may adjusts the configuration parameters.

7. The location management client in the partner MC system applies the temporary configuration parameters and stores the original configuration parameters as well as sets the configuration expiration criteria.

8. The location management client in the partner MC system sends the location reporting temporary configuration response to the location management client in the primary MC system, while utilizing the location management servers in the partner and primary MC system, as described in clause 10.9.2.18 of the present document. The location reporting temporary configuration response includes the full status report on all configuration parameters, even if only one configuration parameter has received a request of adaptation.

10.9.3.11 Restrict location information dissemination procedure

The location management client can control the location information dissemination at any time by sending a restrict location information dissemination request to the location management server, which will indicate to the location management server whether the location information can be disseminated further or not.

Figure 10.9.3.11-1 illustrates the high level procedure whether to enable/disable the restriction to distribute the location information further or not.

Figure 10.9.3.11-1: Restrict the location information dissemination procedure

1. The location management client 1 initiates a request for restricting the location information dissemination, containing an indication to enable the restriction or disable the restriction. By default, the location management server can disable the restriction, i.e. location information of user can be distributed further. The request may provide the list of MC service IDs of MC service users (e.g. based on the role or selected users or any). The list could be pre-defined or dynamic or based on any other criteria.

NOTE 1: In accordance with local policies, the LMC can apply local restrictions by stopping providing location information when a location dissemination request has been activated.

2. The location management server checks if the location management client 1 is authorized to restrict the location information dissemination.

3. The location management server updates restriction information of the reporting location management client 1. If the location management server does not have the restriction record for the location information dissemination of the requesting location management client 1 before, then just store the restriction record for that location management client 1.

NOTE 2: The location server, depending on local policies, can choose to not apply the restriction of location information for emergency services (e.g. Emergency Call, Emergency alert, Imminent peril call, etc.) and for authorized users (e.g. dispatcher, supervisor).

4. The location management server sends the restrict location information dissemination response to the location management client 1 to confirm the status of the restrict location information dissemination request.

5. The location management server may inform all the subscribed users (in accordance with local policies and local requirements) that the location information from this particular user will be provided or not by sending the restrict location information dissemination notification upon successfully applying restrictions on location dissemination as described in step 3 above.