hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4 De-affiliation from MC service group(s)
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4.1 General
|
When an MC service user does not want to communicate with an MC service group anymore for a single MC service, then the MC service user can revoke its affiliation to the MC service group.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4.2 MC service group de-affiliation procedure
|
The procedure for revoking the affiliation with an MC service group for a single MC service is described in figure 10.8.4.2-1.
Pre-conditions:
1. MC service server has already subscribed to the MC service group information from group management server and has stored the data of MC service group(s) to which the MC service user is affiliated to;
2. The MC service client triggers the de-affiliation procedure. This is an explicit de-affiliation requested either by the MC service user or determined by a trigger event such as the MC service UE moving outside a permitted geographic operational area of an MC service group; and
NOTE: The geographical operational area beyond which de-affiliation occurs may be larger than the geographical operational area within which affiliation is permitted, to avoid repeated affiliation and de-affiliation by a user on the edge of an operational area.
3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
4. The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.8.4.2-1: MC service group de-affiliation procedure
1. MC service client requests the MC service server to de-affiliate from an MC service group or a set of MC service groups.
2. Based on the user profile and stored group policy from the group configuration, the MC service server checks if the user of the MC service client is authorized to de-affiliate from the requested MC service group(s) and if the user of the MC service client has affiliated to the requested MC service group(s). The authorisation check includes whether the MC service user has activated a certain functional alias which prevents de-affiliating or whether the MC service user is the last user who has bound a certain functional alias to the group which also prevents de-affiliating.
3. If the user of the MC service client has affiliated to the requested MC service group(s), is authorized to de-affiliate from the requested MC service group(s) then the MC service server removes the affiliation status of the user for the requested MC service group(s), either for the requesting specific MC service client only, or for all MC service clients, where this user has logged on to.
4. MC service server provides to the MC service client the group de-affiliation response (4a). When the MC service user has logged into multiple MC service clients concurrently, the MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s) only when the MC service ID de-affiliates for the provided MC service group(s) from the last MC service client. If the MC service user has logged into only one client then the MC service server and update the group management server with the de-affiliation status of the user for the requested MC service group(s) (4b).
NOTE: Steps 4a and 4b can occur in any order or in parallel.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4.3 De-affiliation from MC service group(s) defined in partner MC system
|
The procedure for de-affiliation from affiliated MC service group(s) which is defined in partner MC system for a single MC service is described in figure 10.8.4.3-1.
Pre-conditions:
1. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate; and
2. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Figure 10.8.4.3-1: De-affiliation from an MC service group defined in partner MC system
1. The MC service client requests the primary MC service server to de-affiliate from an MC service group or a set of MC service groups.
2. The primary MC service server checks if the MC service client is authorized to de-affiliate from the requested MC service group(s) based on the user profile. The primary MC service server performs the check if the user has affiliated to the MC service groups.
3. Based on the MC service group information included in the request, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes.
4. Based on the stored group policy from the group configuration, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s).
5. If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s), either for the requesting specific MC service client only, or for all MC service clients, where this user has logged on to.
6. The partner MC service server sends the MC service group de-affiliation response to primary MC service server (6a) . When the MC service user has logged into multiple MC service clients concurrently, the MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s) only when the MC service ID de-affiliates for the provided MC service group(s) from the last MC service client. If the MC service user has logged into only one client then the MC service server and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (6b).
NOTE: Steps 6a and 6b can occur in any order or in parallel.
7. The primary MC service server will remove any information stored about the user's affiliation with requested MC service group(s) of partner MC system, considering that the user may have logged on to multiple MC service clients and that de-affiliation may have been performed only for the specific MC service client from which the de-affiliation request has been sent, or for all MC service clients, where this user has been affiliated to this MC service group.
8. The primary MC service server sends the MC service group de-affiliation response to the MC service client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4.4 MC server initiated group de-affiliation procedure
|
The procedure for the MC service server to trigger a de-affiliation with an MC service group is described in figure 10.8.4.4-1.
Pre-conditions:
1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation;
2. Following a relevant trigger condition, e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified, causing user outside of the permitted geographical operational area, the MC service server de-affiliates the user from the MC service group; and
3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
4. The MC service server has subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.8.4.4-1: MC service server initiated group de-affiliation procedure
1. The MC service server determines the MC service client could be de-affiliated to the group again due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group.
2. The MC service server changes the affiliation status of the user.
3. The MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s).
4. The MC service server provides a de-affiliation notification with the group information to the MC service client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.4.5 MC server initiated group de-affiliation from group defined in partner MC system
|
The procedure for the MC service server to trigger a de-affiliation from an MC service group which is defined in partner MC system is described in figure 10.8.4.5-1.
Pre-conditions:
1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation;
2. Following a relevant trigger condition (e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified), the de-affiliation for the MC service user is initiated by the MC service server from the MC service group;
3. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate; and
4. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Figure 10.8.4.5-1: MC service server initiated group de-affiliation from group in partner system procedure
1. The MC service server determines the MC service client could be de-affiliated to the group due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group.
2. Based on the stored MC service group information, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes.
3. Based on the stored group policy from the group configuration, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s).
4. If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s).
5. The partner MC service server sends the MC service group de-affiliation response to primary MC service server (5a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (5b).
NOTE: Steps 5a and 5b can occur in any order or in parallel.
6. The primary MC service server changes the affiliation status of the user.
7. The MC service server provides a de-affiliation notification with the group information to the MC service client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5 Remote change of affiliation
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5.1 Remote change of affiliation for groups defined in primary MC system
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5.1.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) – mandatory mode
|
The procedure for an authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service without requiring the target user's approval is described in figure 10.8.5.1.1-1.
Pre-conditions:
1. The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with the target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated;
2. The primary MC service server may have retrieved the user profile or group policy from the group configuration e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data; and
3. The group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Figure 10.8.5.1.1-1: Remotely change MC service group affiliation – mandatory mode
1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
2. The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
3a. The primary MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server, then, the MC service server subscribes to the group policy from the group configuration from the group management server.
3b. The primary MC service server receives the group policy from the group configuration from the group management server via notification and locally caches the group policy from the group configuration.
4. Based on the group policy, the primary MC service server checks if the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s).
5. If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) then the primary MC service server stores the new requested affiliation status of the target MC service user 2 for the MC service group(s).
6. If the requested affiliation status is a change from the current affiliation status, then the primary MC service server updates the group management server with the affiliation status of the MC service user 2 for the MC service group(s).
7a. If the requested affiliation status is a change the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. The MC service client 2 may subscribe to the affiliated MC service groups information with the group management server.
7b. The MC service user 2 provides a response to the primary MC service server by sending an MC service group affiliation change response.
8. The primary MC service server sends the MC service group affiliation change response to MC service client 1. If the requested affiliation status was not changed (see 7a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
NOTE: Steps 6, 7a, 7b and 8 can occur in any order or in parallel, with the restriction that step 7b can only occur after step 7a occurred.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5.1.2 Authorized user remotely changes another MC service user's affiliated MC service group(s) – negotiated mode
|
The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service with the target MC service user's approval is described in figure 10.8.5.1.2-1.
Pre-conditions:
- The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated;
- The primary MC service server may have retrieved the user profile or group policy from the group configuration e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data.
Figure 10.8.5.1.2-1: Remotely change MC service group affiliation – negotiated mode
1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request to the primary MC service server. The information (i.e. target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
2. The primary MC service server checks if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server checks if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile and the group policy from the group configuration (i.e. if not available, the primary MC service server obtains the group policy from the group configuration from the group management server). The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
3. If the target MC service user 2 is authorized to accept the changes to its affiliated MC service group(s), then the primary MC service server sends the MC service group affiliation change request to the MC service client 2 of the target MC service user 2.
4. If the requested affiliation status is different from the current affiliation status, then the MC service client 2 notifies the MC service group affiliation change request to the target MC service user 2 to receive the approval from the user on the proposed changes to the affiliated MC service group(s).
NOTE 1: The procedure is aborted if the target MC service user 2 does not respond to the notification within an implementation dependent time.
5. If the target MC service user 2 provides a response (accept or reject) to the notification, then the MC service client 2 sends an MC service group affiliation change response to the primary MC service server. A response indicating target user 2's acceptance to the requested affiliation change by authorized user 1, triggers the affiliation or de-affiliation procedures at the primary MC service server (see subclause 10.8.3.1 or subclause 10.8.4.2) as per the MC service user 1's requested changes to the target user 2's affiliated group(s).
NOTE 2: In the case where the affiliation changes for target user 2 includes MC service groups defined in partner MC systems, the primary MC service server performs the affiliation or de-affiliation procedures by interacting with the partner MC systems (see subclause 10.8.3.2 or subclause 10.8.4.3).
6. The primary MC service server sends the MC service group affiliation change response to the MC service client 1. If the requested affiliation status was not changed (see 4), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
NOTE 3: If multiple MC service groups are included in step 1, and these MC service groups belong to different partner MC systems, the primary MC service server can wait until all the partner MC systems provides the MC service group affiliation change response messages.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5.2 Remote change of affiliation for groups defined in partner MC system
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.8.5.2.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) defined in partner MC system – mandatory mode
|
The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) defined in partner MC systems for a single MC service without requiring the target user's approval is described in figure 10.8.5.2.1-1.
Pre-conditions:
1. The MC service client 1 (authorized user) has already been provisioned (statically or dynamically) with the target MC service user 2's information and group information, that the target MC service user 2 is allowed to be affiliated or de-affiliated;
2. The MC service client 1 (authorized user 1), MC service client 2 (target MC service user 2), and the primary MC service server belong to the same MC system;
3. The partner MC service server may have retrieved the group related information from the group management server;
4. The primary MC service server may have retrieved the user policy e.g. user related information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data; and
5. The partner group management server has subscribed to the MC service server within the MC system where the group is defined for affiliation status updates.
Figure 10.8.5.2.1-1: Remote change MC service group affiliation defined in partner MC system – mandatory mode
1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information (i.e. target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included.
2. The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user profile. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously.
3. Based on the MC service group information included in the request, the primary MC service server determines to send MC service group affiliation change request to the corresponding partner MC service server (group host server).
4a. The partner MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the partner MC service server then the partner MC service server subscribes to the group policy from the group configuration from the group management server.
4b. The partner MC service server receives the group policy from the group configuration from the group management server via notification and locally caches the group policy from the group configuration.
5. Based on the group policy, the partner MC service server checks if the target MC service user 2 is authorized to affiliate to the MC service group(s). It is possible that the target MC service user 2 affiliates to one or more MC service groups and also de-affiliates from one or more MC service groups.
6. If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) and if the requested affiliation status is different to the current affiliation status, then the partner MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s).
7. The partner MC service server sends the MC service group affiliation change response to the primary MC service server.
8. The partner MC service server updates the group management server with the affiliation status of the target MC service user 2 for the MC service group(s).
NOTE: Steps 7 and 8 can occur in any order or in parallel.
9. If the requested affiliation status is different to the current affiliation status, then the primary MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s).
10a. If the requested affiliation status is different to the current affiliation status, then the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. Further the MC service client 2 may subscribe for the affiliated MC service groups information with the group management server.
10b. The target MC service client 2 provides an MC service group affiliation change response to the MC service server.
11. The primary MC service server sends the MC service group affiliation change response to MC service client 1 (authorized user). If the requested affiliation status was not changed (see 10a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9 Location management (on-network)
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.1 General
|
Location information of MC service user shall be provided by the location management client to the location management server. The location information may also be provided by the 3GPP core network (i.e., via the PLMN operator). The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.
NOTE 1: It is up to implementation whether location information reporting from the core network is considered as an optional or primary source of location information to the MC system.
The location information provided by the 3GPP core network can be obtained from the location services feature in EPS (i.e., LCS) as described in 3GPP TS 23.271 [29], or from the PCRF as part of the PCC mechanism once the MC service server subscribes to related notifications from the PCRF as described in 3GPP TS 23.203 [8].An authorized MC service user may subscribe to event-triggered location information of one or more MC service users. By default a subscribed MC service user will receive location information based on the location reporting configuration in the user profile of the reporting MC service user.
An authorized and subscribed MC service user may initiate a trigger request procedure to modify the location reporting triggers for one or more reporting MC service users. The location management server aggregates trigger requests from the MC service servers and from location management clients towards the same target location management client and may adjust the location reporting triggers of the reporting MC service users as required.
When a subscribed MC service user cancels the subscription, the location management server stops delivering location reports to this MC service user and the location management server may adjust the aggregated location reporting triggers of the reporting MC service users as required.
The location management client can be configured to store location information while not reporting location information to the location management server. The location management client may report stored location information to the location management server.
NOTE 2: Configuration and location information transmission may occur while there is a communication link between the location management client and location management server.
In the information flows of clause 10.9.2, and procedures of clause 10.9.3:
- the term "requesting MC service user" is used to refer to the MC service user which sends a request to subscribe to location information reports, to trigger a location information report or to modify existing location information triggers from another MC service user;
- the term "requested MC service user" is used to refer to the MC service user whose location information is requested or existing location information triggers are to be modified; and
- the term "reporting MC service user" is used to refer to the MC service user which provides location related information based on on-demand request or trigger criteria.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2 Information flows for location information
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.1 Location reporting configuration
|
Table 10.9.2.1-1 describes the information flow from the location management server to the location management client for the location reporting configuration.
Table 10.9.2.1-1: Location reporting configuration
Information element
Status
Description
MC service ID
M
Identity of the MC service user to which the location reporting configuration is targeted.
Requested non-emergency location information
O
(see NOTE 1)
Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts
Requested emergency location information
O
(see NOTE 1)
Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts
Triggering criteria in non- emergency cases
O
(see NOTE 1)
Identifies when the location management client will send the location report in non-emergency cases
Handling criteria in not reporting location information cases
O
Identifies when the location management client will store location information (e.g. never, off-network, IOPS)
Triggering criteria in not reporting location information cases
O
(see NOTE 2)
Identifies the causes when the location management client will generate location information
Minimum time between consecutive reports for emergency cases
O
(see NOTE 1)
Identifies the location update rate for emergency and imminent peril cases. Defaults to 0 if absent.
Minimum time between consecutive reports for non-emergency cases
O
(see NOTE 1)
Identifies the location update rate for non-emergency cases.
Triggering criteria in emergency cases
O
(see NOTE 1)
Identifies when the location management client will send the location report in emergency cases
NOTE 1: If none of the information elements is present, this represents a cancellation for location reporting based on Triggering criteria in emergency and non-emergency cases, if configured.
NOTE 2: If not present, location information is generated based on Triggering criteria in emergency and non-emergency cases, if configured.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.2 Location information report
|
Table 10.9.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting.
Table 10.9.2.2-1: Location information report (LMC – LMS)
Information element
Status
Description
Set of MC service IDs
M
Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID
(see NOTE 4)
O
Identity of the requesting MC service user.
Functional alias(es)
(see NOTE 1)
O
Functional alias that corresponds to the reporting MC service ID.
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service UE label (see NOTE 5)
O
Generic name of the reporting MC service UE
Triggering event
(see NOTE 3)
M
Identity of the event that triggered the sending of the report
Location Information (see NOTE 2)
M
Location information of the individual MC service user
NOTE 1: Each functional alias corresponds to an individual MC service ID.
NOTE 2: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 3: An on-demand request may be the triggering event.
NOTE 4: In case of an on-demand request of an MC service user the MC service ID shall be provided. In case of an MC service server request or an event-triggered report, no MC service ID is provided.
NOTE 5: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
Table 10.9.2.2-2 describes the information flow from the location management server to the location management client for location information reporting.
Table 10.9.2.2-2: Location information report (LMS – LMC)
Information element
Status
Description
Set of MC service IDs
M
Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID
M
Identity of the requesting MC service user.
Functional alias(es) (see NOTE 1)
O
Functional alias that corresponds to the reporting MC service ID.
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service UE label (see NOTE 4)
O
Generic name of the reporting MC service UE
Triggering event (see NOTE 3)
M
Identity of the event that triggered the sending of the report
Location Information (see NOTE 2)
M
Location information of the individual MC service user
NOTE 1: Each functional alias corresponds to an individual MC service ID.
NOTE 2: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 3: An on-demand request may be the triggering event.
NOTE 4: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
Table 10.9.2.2-3 describes the information flow from the location management server to the MC service server for location information reporting.
Table 10.9.2.2-3: Location information report (LMS – MC service server)
Information element
Status
Description
Set of MC service IDs
M
Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias(es) (see NOTE 1)
O
Functional alias that corresponds to the MC service ID.
Triggering event (see NOTE 3)
M
Identity of the event that triggered the sending of the report
Location Information (see NOTE 2)
M
Location information of the individual MC service user
NOTE 1: Each functional alias corresponds to an individual MC service ID.
NOTE 2: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 3: An on-demand request may be the triggering event.
Table 10.9.2.2-4 describe the information flow to support the handling of location information across MC systems.
Table 10.9.2.2-4: Location information report (LMS – LMS)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user at partner MC system
Functional alias
O (see NOTE 1)
Functional alias of the reporting MC service user at partner MC system
MC service ID
M (see NOTE 2)
Identity of the requesting MC service user at primary MC system
Functional alias
O (see NOTE 2)
Functional alias of the requesting MC service user at primary MC system
MC service UE label (see NOTE 5)
O
Generic name of the reporting MC service UE at partner MC system
Triggering event (see NOTE 3)
M
Identity of the event that triggered the sending of the report
Location Information (see NOTE 4)
M
Location information of the individual MC service user at partner MC system
NOTE 1: It shall be present if used with the Functional alias associated request.
NOTE 2: Only present, if provided with the associated request.
NOTE 3: An on-demand request may be the triggering event.
NOTE 4: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 5: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.3 Location information request
|
Tables 10.9.2.3-1, 10.9.2.3-2 and 10.9.2.3-3 describe the information flow from the MC service server to the location management server and from the location management server to the location management client and from location management client to location management server respectively for requesting an immediate location information report.
Table 10.9.2.3-1: Location information request (MC service server to location management server)
Information element
Status
Description
MC service ID list
O
(see NOTE 1)
List of MC service users whose location information is requested
Functional alias
O
(see NOTE 1)
Location information of MC service users who have activated this functional alias is requested
Requested non-emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: Either the MC service ID list or the functional alias must be present.
NOTE 2: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
Table 10.9.2.3-2: Location information request (Location management server to location management client)
Information element
Status
Description
MC service ID
M
Identity of MC service user whose location information is requested
MC service ID
O
Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Requested non-emergency location information
O
(see NOTE)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
Table 10.9.2.3-3: Location information request (Location management client to location management server)
Information element
Status
Description
MC service ID
M
Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID list
O
(see NOTE 1)
List of MC service users whose location information is requested
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
(see NOTE 1)
Functional alias that corresponds to the requested MC service user(s) (e.g. MCPTT ID, MCVideo ID, MCData ID)
Requested non-emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: Either the MC service ID list or the functional alias must be present.
NOTE 2: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
Tables 10.9.2.3-4 describe the information flow to support the handling of location information across MC systems.
Table 10.9.2.3-4: Location information request (Location management server to location management server)
Information element
Status
Description
MC service ID
M (see NOTE 1)
Identity of the requesting authorized MC service user at primary MC system
Functional alias
O (see NOTE 1)
Functional alias that corresponds to the requesting MC service user at primary MC system
MC service ID list
O (see NOTE 2)
List of identities of those MC service users at partner MC system whose location information are requested
Functional alias
O (see NOTE 2)
Functional alias of those MC service users at partner MC system whose location information are requested
Requested non-emergency location information
O
(see NOTE 3)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE 3)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: Only present if Location information client has initiated the request.
NOTE 2: Either the MC service ID list or the functional alias must be present.
NOTE 3: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.4 Location reporting trigger
|
Table 10.9.2.4-1 describes the information flow from the location management client to the location management server for triggering a location reporting procedure.
Table 10.9.2.4-1: Location reporting trigger
Information element
Status
Description
MC service ID
M
(see NOTE 1)
Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID list
O
(see NOTE 1)
(see NOTE 3)
Identity of the requested MC service users (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service group ID list
O
(see NOTE 3)
Group ID(s) that correspond to MC service user(s) whose location information is requested (e.g. MCPTT ID, MCVideo ID, MCData ID). This trigger is only for currently affiliated users to these group(s).
Functional alias list
O
(see NOTE 3)
Functional alias that corresponds to the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID).
Immediate Report Indicator
O
(see NOTE 2)
(see NOTE 4)
Indicates whether an immediate location report is required
Requested non-emergency location information
O
(see NOTE 2)
(see NOTE 4)
Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts
Requested emergency location information
O
(see NOTE 2)
(see NOTE 4)
Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts
Triggering criteria in non- emergency cases
O
(see NOTE 2)
(see NOTE 4)
Identifies when the client will send the location report in non-emergency cases
Triggering criteria in emergency cases
O
(see NOTE 2)
(see NOTE 4)
Identifies when the client will send the location report in emergency cases
Minimum time between consecutive reports for emergency cases
O
(see NOTE 2)
(see NOTE 4)
Identifies the location update rate for emergency and imminent peril cases. Defaults to 0 if absent.
Minimum time between consecutive reports for non-emergency cases
O
(see NOTE 2)
(see NOTE 4)
Identifies the location update rate for non-emergency cases.
Location reporting trigger override indicator
O
(see NOTE 2, NOTE 6)
Indicates that the existing location reporting triggers at the reporting location management client are to be replaced by the triggers in this flow
Location reporting trigger cancel override indicator
O
(see NOTE 2, NOTE 6, NOTE 7)
Indicates that location reporting trigger override of the reporting location management client is to be cancelled
Reason for overriding location reporting triggers
O
(see NOTE 5)
A text description indicating the reason for override
NOTE 1: The identity of the requesting MC service user and the requested MC service user shall belong to the same MC service. E.g. if requesting MC service user is using a MCPTT ID, then the requested MC service user identity shall be an MCPTT ID.
NOTE 2: At least one of these rows shall be present.
NOTE 3: Either the MC service ID or the MC service group ID list or the functional alias must be present.
NOTE 4: This configuration could contain IEs for emergency reporting, for non-emergency reporting or for both cases. If this configuration contains only the emergency case, reporting for the non-emergency case shall happen as per the relevant parameters in the default configuration. If this configuration contains only the non-emergency case, reporting for the emergency case shall happen as per the relevant parameters in the default configuration. (see Table A.8-1).
NOTE 5: This shall be present if the request is to override the location reporting trigger.
NOTE 6: Location reporting trigger override indicator cannot occur together with Location reporting trigger cancel override indicator
NOTE 7: A location reporting trigger cancel override shall not contain requested location information, triggering criteria and minimum time between consecutive reports
10.9.2.4a Location reporting trigger cancel
Table 10.9.2.4a-1 describes the information flow from the location management client to the location management server to stop triggering a location reporting procedure.
Table 10.9.2.4a-1: Location reporting trigger cancel
Information element
Status
Description
MC service ID
M
(see NOTE 1)
Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
Functional alias that corresponds to the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID list
O
(see NOTE 1)
(see NOTE 2)
List of MC service users whose location information reporting is to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service group ID list
O
(see NOTE 2)
Group ID(s) that correspond MC service user(s) whose location reporting triggers are to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). The location reporting triggers are cancelled only for currently affiliated users to these MC service group(s).
Functional alias
O
(see NOTE 2)
Functional alias that corresponds to the MC service users whose location information reporting is to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID).
NOTE 1: The identity of the requesting MC service user and the requested MC service user shall belong to the same MC service. E.g. if requesting MC service user is using a MCPTT ID, then the requested MC service user identity shall be an MCPTT ID.
NOTE 2: At least one of these information elements shall be present.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.5 Location information subscription request
|
Table 10.9.2.5-1 describes the information flow from the MC service server to the location management server for location information subscription request.
Table 10.9.2.5-1: Location information subscription request (MC service server – LMS)
Information element
Status
Description
MC service ID list
M
List of MC service users whose location information is requested
Time between consecutive reports
M (see NOTE 1)
Indicates the interval time between consecutive reports. The provided time is to be used for all MC service IDs provided in the MC service ID list.
Requested non-emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE 2)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: If the interval time has a value of zero then the location management server will send the Location information notification immediately the location information report is received from the MC service user in the MC service ID list.
NOTE 2: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
Table 10.9.2.5-2 describes the information flow from the location management client to the location management server for location information subscription request.
Table 10.9.2.5-2: Location information subscription request (LMC – LMS)
Information element
Status
Description
MC service ID
M
Identity of the requesting MC service user
MC service ID list
O
(see NOTE 1)
List of MC service users whose location information is requested
MC service group ID list
O
(see NOTE 1)
Group ID(s) that correspond MC service user(s) for whose location information subscription is requested (e.g. MCPTT ID, MCVideo ID, MCData ID). This request is only for currently affiliated users to these group(s).
Time between consecutive reports
M (see NOTE 2)
Indicates the interval time between consecutive reports. The provided time is to be used for all MC service IDs provided in the MC service ID list or the service group ID list.
Requested non-emergency location information
O
(see NOTE 3)
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information
O
(see NOTE 3)
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: Either the MC service ID list or the MC service group ID list must be present.
NOTE 2: If the interval time has a value of zero then the location management server will send the Location information notification immediately the location information report is received from the MC service user in the MC service ID list.
NOTE 3: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
Table 10.9.2.5-3 describes the information flow from the location management server in the primary MC system to the location management server in the partner MC system for the location information subscription request.
Table 10.9.2.5-3: Location information subscription request (LMS – LMS)
Information element
Status
Description
MC service ID (see NOTE 1)
M
Identity of the requesting MC service user in the primary MC system
MC service ID list
M
List of the identities of MC service users in the partner MC system whose location information are requested
Time between consecutive location notifications (see NOTE 2)
M
Indicates the interval time between consecutive location notifications
Requested non-emergency location information (see NOTE 3)
O
Identifies what location information elements (e.g. latitude, longitude, speed) are requested, except for emergency calls or imminent peril calls or emergency alerts or in emergency state
Requested emergency location information (see NOTE 3)
O
Identifies what location information elements (e.g. latitude, longitude, altitude, speed, ECGI) are requested, for emergency calls or imminent peril calls or emergency alerts or in emergency state
NOTE 1: This element is only present when the request is originated by an MC service client.
NOTE 2: If the interval time has a value of zero then the location management server will send the location information notification immediately after the location information update is received from the MC service user in the MC service ID list.
NOTE 3: This IE is included to indicate what location information is expected. If not present, LMS sends all the available location information received from the requested MC service user to the requester.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.6 Location information subscription response
|
Table 10.9.2.6-1 describes the information flow from the location management server to the MC service server or location management client and from the location management server in the partner MC system to the location management server in the primary MC system for the location information subscription response.
Table 10.9.2.6-1: Location information subscription response
Information element
Status
Description
MC service ID (see NOTE 1)
M
Identity of the requesting MC service user
Subscription status (see NOTE 2)
M
Indicates the subscription result
NOTE 1: This element is only present when the associated request was originated by an MC service client.
NOTE 2: The subscription status provides the status for each MC service ID listed with the associated request.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.7 Location information notification
|
Table 10.9.2.7-1 and Table 10.9.2.7-2 describe the information flows from the location management server to the MC service server and from the location management server to the location management client.
Table 10.9.2.7-1: Location information notification (LMS to MC service server)
Information element
Status
Description
MC service ID
M
Identity of the MC service user whose location information is being notified
Triggering event
M
Identity of the event that triggered the sending of the notification
Location Information (see NOTE)
M
Location information
NOTE: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
Table 10.9.2.7-2: Location information notification (LMS to LMC)
Information element
Status
Description
MC service ID
M
Identity of the MC service user whose location information is being notified
Functional alias
O
Functional alias that corresponds to the MC service user whose location information is being notified
MC service ID
M
Identity of the MC service user subscribed to location information
Triggering event
M
Identity of the event that triggered the sending of the notification
Location Information (see NOTE 1)
M
Location information
MC service UE label (see NOTE 2)
O
Generic name of the reporting MC service UE
NOTE 1: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 2: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
Table 10.9.2.7-3 describes the information flow from the location management server in the partner MC system to the location management server in the primary MC system.
Table 10.9.2.7-3: Location information notification (LMS to LMS)
Information element
Status
Description
MC service ID
M
Identity of the MC service user whose location information is being notified
Functional alias
O
Functional alias that corresponds to the MC service user whose location information is being notified
Triggering event
M
Identity of the event that triggered the sending of the notification
Location Information (see NOTE 1)
M
Location information
MC service UE label (see NOTE 2)
O
Generic name of the reporting MC service UE
NOTE 1: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 2: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
10.9.2.8 Location information cancel subscription request
Table 10.9.2.8-1 describes the information flow from the MC service server to the location management server for location information cancel subscription request.
Table 10.9.2.8-1: Location information cancel subscription request (MC service server to location management server)
Information element
Status
Description
MC service ID list
M
List of identities of the MC service users for whom location information is no longer required
Table 10.9.2.8-2 describes the information flow from the location management client to the location management server for location information cancel subscription request.
Table 10.9.2.8-2: Location information cancel subscription request (Location management client to location management server)
Information element
Status
Description
MC service ID (see NOTE 1)
M
Identity of the requesting MC service user
MC service ID (see NOTE 2)
O
Identity of the MC service user, whose subscription is to be cancelled
MC service ID list
O
(see NOTE 3)
List of identities of the MC service users for whom location information is no longer required
MC service group ID list
O
(see NOTE 3)
Group ID(s) that correspond MC service user(s) whose location information subscriptions are to be cancelled (e.g. MCPTT ID, MCVideo ID, MCData ID). This request is only for currently affiliated users to these group(s).
NOTE 1: Authorized or subscribed MC service user.
NOTE 2: Only used with the authorized MC service user.
NOTE 3: Either the MC service ID list or the MC service group ID list must be present.
Table 10.9.2.8-3 describes the information flow from the location management server in the primary MC system to the location management server in the partner MC system for the location information cancel subscription request.
Table 10.9.2.8-3: Location information cancel subscription request (Location management server to location management server)
Information element
Status
Description
MC service ID (see NOTE 1)
M
Identity of the requesting MC service user in the primary MC system
MC service ID (see NOTE 2)
O
Identity of the MC service user in the partner MC system, whose subscription is to be cancelled
MC service ID list
M
List of the identities of MC service users in the partner MC system for whom location information is no longer required
NOTE 1: Authorized or subscribed MC service user and only present when the request was originated by an MC service client.
NOTE 2: Only used with the authorized MC service user.
10.9.2.9 Location information cancel subscription response
Table 10.9.2.9-1 describes the information flow from the location management server to the MC service server for location information cancel subscription response.
Table 10.9.2.9-1: Location information cancel subscription response (Location management server to MC service server)
Information element
Status
Description
MC service ID list
M
List of identities of MC service users, whose subscription has been requested to be cancelled
Subscription cancel response
M
Indicates the cancel subscription result
Table 10.9.2.9-2 describes the information flow from the location management server to the location management client for location information cancel subscription response.
Table 10.9.2.9-2: Location information cancel subscription response (Location management server to location management client)
Information element
Status
Description
MC service ID
M
Identity of the requesting MC service user
MC service ID (see NOTE)
O
Identity of the MC service user, whose subscription has been requested to be cancelled
MC service ID list
M
List of identities of MC service users for whom location information is no longer required
Subscription cancel response
M
Indicates the cancel subscription result
NOTE: Only used with the authorized MC service user. Must be present, if used with the associated request.
Table 10.9.2.9-3 describes the information flow from the location management server in the partner MC system to the location management server in the primary MC system for location information cancel subscription response.
Table 10.9.2.9-3: Location information cancel subscription response (Location management server to location management server)
Information element
Status
Description
MC service ID (see NOTE 1)
M
Identity of the requesting MC service user in the primary MC system
MC service ID (see NOTE 2)
O
Identity of the MC service user in the partner MC system, whose subscription has been requested to be cancelled
MC service ID list
M
List of identities of MC service users in the partner MC system for whom location information is no longer required
Subscription cancel response (see NOTE 3)
M
Indicates the cancel subscription result
NOTE 1: This element is only present when the associated request was originated by an MC service client.
NOTE 2: Only used with the authorized MC service user. Must be present, if used with the associated request.
NOTE 3: Provides the status for each MC service ID listed with the associated request.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.10 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.11 Location information history status request
|
Table 10.9.2.11-1 describes the information flow from the location management client to the location management server to request the status of stored location information, following a return to report location information to the location management server.
Table 10.9.2.11-1: Location information history status request (LMC – LMS)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom status is requested
MC service ID
M
Identity of the MC service user, who has requested the status
Table 10.9.2.11-2 describes the information flow from the location management server to the location management client to request the status of stored location information, following a return to report location information to the location management server.
Table 10.9.2.11-2: Location information history status request (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom status is requested
Table 10.9.2.11-3 describes the information flow from the MC service server to the location management server to request the status of stored location information, following a return to report location information to the location management server.
Table 10.9.2.11-3: Location information history status request (MC service server – LMS)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom status is requested
MC service ID
O
Identity of the MC service user, who has requested the status
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.12 Location information history status report
|
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server.
Table 10.9.2.12-1 describes the information flow from the location management client to the location management server to report the status of stored location information.
Table 10.9.2.12-1: Location information history status report (LMC – LMS)
Information element
Status
Description
MC service ID list
M
List of identities (e.g. MCPTT ID, MCData ID, MCVideo ID) of the MC service user who reports the status
Number of stored reports
O
Indicates either zero or the number of available reports
Start time
O
First time of measurement of the available reports
End time
O
Last time of measurement of the available reports
Triggered event list (see NOTE)
M
Identifies the criteria when the location management client generated location information, while not reporting location information
NOTE: Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
Table 10.9.2.12-2 describes the information flow from the location management server to the location management client to report the status of stored location information.
Table 10.9.2.12-2: Location information history status report (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the MC service user who reports the status
MC service ID
M
Identity of the MC service user to receive the status report
Number of stored reports
O
Indicates either zero or the number of available reports
Start time
O
First time of measurement of the available reports
End time
O
Last time of measurement of the available reports
Triggered event list (see NOTE)
M
Identifies the criteria when the location management client generated location information, while not reporting location information
NOTE: Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
Table 10.9.2.12-3 describes the information flow from the location management server to the MC service server to report the status of stored location information.
Table 10.9.2.12-3: Location information history status report (LMS - MC service server)
Information element
Status
Description
MC service ID
M
Identity of the MC service user who reports the status
Number of stored reports
O
Indicates either zero or the number of available reports
Start time
O
First time of measurement of the available reports
End time
O
Last time of measurement of the available reports
Triggered event list (see NOTE)
M
Identifies the criteria when the location management client generated location information, while not reporting location information
NOTE: Each triggered criterion is shown once with either the associated Number of stored reports, or with the associated Start time, or with the associated Start time and End time or with the associated End time.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.13 Location information history request
|
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server. Either all or a subset of the stored location information may be requested prior to the location information history reporting.
Table 10.9.2.13-1 describes the information flow from the location management client to the location management server for the location information history request of stored location information.
Table 10.9.2.13-1: Location information history request (LMC – LMS)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom reports are requested
MC service ID
M
Identity of the MC service user who requests location information
Number of stored reports (see NOTE)
O
Indicates the number of requested reports
Start time (see NOTE)
O
Indicates to send reports having this time of measurement and newer
End time (see NOTE)
O
Indicates to send reports having this time of measurement and older
Triggered event list (see NOTE)
O
Identifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reports
O
Defaults to 0 if absent
NOTE: If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
Table 10.9.2.13-2 describes the information flow from location management server to the location management client for the location information history request of stored location information.
Table 10.9.2.13-2: Location information history request (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom reports are requested
Number of stored reports (see NOTE)
O
Indicates the number of requested reports
Start time (see NOTE)
O
Indicates to send reports having this time of measurement and newer
End time (see NOTE)
O
Indicates to send reports having this time of measurement and older
Triggered event list (see NOTE)
O
Identifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reports
O
Defaults to 0 if absent
NOTE: If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
Table 10.9.2.13-3 describes the information flow from the MC service server to the location management server for the location information history request of stored location information.
Table 10.9.2.13-3: Location information history request (MC service server – LMS)
Information element
Status
Description
MC service ID
M
Identity of the MC service user from whom reports are requested
Number of stored reports (see NOTE)
O
Indicates the number of requested reports
Start time (see NOTE)
O
Indicates to send reports having this time of measurement and newer
End time (see NOTE)
O
Indicates to send reports having this time of measurement and older
Triggered event list (see NOTE)
O
Identifies the criteria when the location management client generated location information, while not reporting location information
Minimum time between consecutive reports
O
Defaults to 0 if absent
NOTE: If none of these information elements is present, all stored location information shall be reported. Information elements may combined to request a subset of the available location information.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.14 Location information history report
|
The location management client stored location information, while not reporting location information to the location management server, and subsequently the reporting may start following the reestablishment of a communication link between the location management client and the location management server.
Table 10.9.2.14-1 describes the information flow from the location management client to the location management server for the location information history reporting of stored location information.
Table 10.9.2.14-1: Location information history report (LMC – LMS)
Information element
Status
Description
MC service ID list
M
List of identities of the reporting MC service user (e.g. MCPTT ID, MCData ID, MCVideo ID)
Triggered event
M
Identifies the criterion when the location management client generated location information, while not reporting location information
Location Information (see NOTE 1)
M
Location information
MC service UE label (see NOTE 3)
O
Generic name of the reporting MC service UE
History report (see NOTE 2)
O
Location information history report indicator
NOTE 1: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 2: Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
NOTE 3: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
Table 10.9.2.14-2 describes the information flow from the location management server to the location management client for the location information history reporting of stored location information.
Table 10.9.2.14-2: Location information history report (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
MC service ID
M
Identity of the MC service user, who has requested location information
Triggered event
M
Identifies the criterion when the location management client generated location information, while not reporting location information
Location Information
(see NOTE 1)
M
Location information
MC service UE label (see NOTE 3)
O
Generic name of the reporting MC service UE
History report (see NOTE 2)
O
Location information history report indicator
NOTE 1: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 2: Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
NOTE 3: This information element shall be present in case the “MC service UE label” parameter in the initial MC service UE configuration data has a non-null value.
Table 10.9.2.14-3 describes the information flow from the location management server to the MC service server for the location information history reporting of stored location information.
Table 10.9.2.14-3: Location information history report (LMS - MC service server)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
Triggered event
M
Identifies the criterion when the location management client generated location information, while not reporting location information
Location Information (see NOTE 1)
M
Location information
History report (see NOTE 2)
O
Location information history report indicator
NOTE 1: This may contain multiple sets of elements for the MC service user. The following elements shall accompany the location information elements: time of measurement and optional accuracy. The following location information elements shall be optional (configurable) present: longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs, with at least one provided.
NOTE 2: Only present, if triggering criteria in emergency cases or triggering criteria in non-emergency cases used.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.15 Location information history cancel request
|
Table 10.9.2.15-1 describes the information flow from the location management client to the location management server for the cancellation request of location information history reporting.
Table 10.9.2.15-1: Location information history cancel request (LMC – LMS)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
MC service ID
M
Identity of the MC service user, who has requested the cancellation
Cancellation type
O
Type of cancellation (e.g. from reporting LMC, from LMS, from LMC and LMS)
Table 10.9.2.15-2 describes the information flow from the location management server to the location management client for the cancellation request of location information history reporting.
Table 10.9.2.15-2: Location information history cancel request (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
Table 10.9.2.15-3 describes the information flow from the MC service server to the location management server for the cancellation request of location information history reporting.
Table 10.9.2.15-3: Location information history cancel request (MC service server - LMS)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
MC service ID
O
Identity of the MC service user, who has requested the cancellation
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.16 Location information history cancel response
|
Table 10.9.2.16-1 describes the information flow from the location management client to the location management server for the cancellation response of location information history reporting.
Table 10.9.2.16-1: Location information history cancel response (LMC – LMS)
Information element
Status
Description
MC service ID list
M
List of identities (e.g. MCPTT ID, MCData ID, MCVideo ID) of the reporting MC service user
Table 10.9.2.16-2 describes the information flow from the location management server to the location management client for the cancellation response of location information history reporting.
Table 10.9.2.16-2: Location information history cancel response (LMS – LMC)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
Response
M
Confirm cancellation from reporting LMC, from LMS or from reporting LMC and LMS
Table 10.9.2.16-3 describes the information flow from the location management server to the MC service server for the cancellation response of location information history reporting.
Table 10.9.2.16-3: Location information history cancel response (LMS - MC service server)
Information element
Status
Description
MC service ID
M
Identity of the reporting MC service user
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.17 Location reporting temporary configuration request
|
Table 10.9.2.17-1 describes the information flow from the location management client and location management server in the primary MC system to the location management server and location management client in the partner MC system for the location reporting temporary configuration request.
Table 10.9.2.17-1: Location reporting temporary configuration request
Information element
Status
Description
MC service ID
M
Identity of the authorized and configuring MC service user located in the primary MC system
Functional alias
O
Functional alias that corresponds to the authorized and configuring MC service user located in the primary MC system
MC service ID
M
Identity of the MC service user located in the partner MC system whose location reporting has to be configured
Functional alias
O
Functional alias that corresponds to MC service user located in the partner MC system whose location reporting has to be configured
MC service UE label
O
Generic name of the to be configured MC service UE
Temporary location reporting configuration (see NOTE 1)
M
Provides set of location reporting parameters to be used temporarily.
Configuration expiration criteria (see NOTE 2)
O
Criteria for restoration of original location reporting parameters (e.g. timer).
NOTE 1: All or a subset of the location reporting parameters described in clause 10.9.2.1 of the present document are used. If empty the original location reporting parameters are used, immediately.
NOTE 2: Ignored with an empty Temporary location reporting configuration.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.18 Location reporting temporary configuration response
|
Table 10.9.2.18-1 describes the information flow from the location management client and location management server in the partner MC system to the location management server and location management client in the primary MC system for the location reporting temporary configuration response.
Table 10.9.2.18-1: Location reporting temporary configuration response
Information element
Status
Description
MC service ID
M
Identity of the authorized and configuring MC service user located in the primary MC system
Functional alias
O
Functional alias that corresponds to the authorized and configuring MC service user located in the primary MC system
MC service ID
M
Identity of the MS service user located in the partner MC system whose location reporting has been configured
Functional alias
O
Functional alias that corresponds to the MS service user located in the partner MC system whose location reporting has been configured
MC service UE label
O
Generic name of the configured MC service UE
Result
M
Indicates the status of each configuration parameter
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.19 Restrict location information dissemination request
|
Table 10.9.2.19-1 describes the information flow from the location management client to the location management server for restricting the location information dissemination further.
Table 10.9.2.19-1: Restrict location information dissemination request information elements
Information Element
Status
Description
MC service ID
M
Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Restrict Location Information Dissemination
M
Indicates to enable or disable the location information dissemination
List of users
(see NOTE 1, NOTE 2)
O
Indicates that the restriction of the location information dissemination is applicable for the list of users.
Functional Alias
(see NOTE 1, NOTE 2, NOTE 3)
O
Indicates that the restriction of the location information dissemination is applicable for the list of users who have activated this functional alias.
NOTE 1: If not present, restricting of the location information dissemination is applicable to any users. Dissemination restriction to a particular set of users is not possible if the LMC client applies local restrictions to stop providing location information per local policies.
NOTE 2: Either the MC service ID list or the functional alias must be present.
NOTE 3: The LMS track the users activating and de-activating functional alias so that associated restriction record can be updated accordingly.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.20 Restrict location information dissemination response
|
Table 10.9.2.20-1 describes the information flow from the location management server to the location management client for response to restricting the location information dissemination request.
Table 10.9.2.20-1: Restrict location information dissemination response information elements
Information Element
Status
Description
MC service ID
M
Identity of the requesting MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Restrict Location Information Dissemination status
M
Indicates the result of restricting the location information dissemination
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.21 Restrict location information dissemination notification
|
Table 10.9.2.21-1 and Table 10.9.2.21-2 describes the information flow from the location management server to the location management client and from the location management server to the MC service server for notifying about restricting the location information dissemination of another location management client.
Table 10.9.2.21-1: Restrict location information dissemination notification information elements (LMS to LMC)
Information Element
Status
Description
MC service ID
M
Identity of the MC service user whose location information dissemination retriction information is being notified (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID
M
Identity of the MC service user subscribed to location information
Location Information Dissemination information
M
Indicates whether the dissemination of another MC service user’s location information is enabled or disabled
Table 10.9.2.21-2: Restrict location information dissemination notification information elements (LMS to MC service server)
Information Element
Status
Description
MC service ID
M
Identity of the MC service user whose location information dissemination retriction information is being notified (e.g. MCPTT ID, MCVideo ID, MCData ID)
Location Information Dissemination information
M
Indicates whether the dissemination of another MC service user’s location information is enabled or disabled
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.22 Location reporting trigger override indication
|
Table 10.9.2.22-1 describes the information flow from the location management server to the location management client for indicating a location reporting trigger override.
Table 10.9.2.22-1: Location reporting trigger override indication
Information element
Status
Description
MC service ID
M
Identity of the overriding MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
Functional alias
O
Functional alias that corresponds to the overriding MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID)
MC service ID list
M
List of identities of the MC service users for who triggers are overridden
Functional alias list
O
Functional alias that corresponds to the MC service users for who triggers are overridden
Reason for override
O
A text description indicating the reason for override
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.2.23 Location reporting cancel trigger override indication
|
Table 10.9.2.23-1 describes the information flow from the location management server to the location management client for indicating a location reporting cancel trigger override.
Table 10.9.2.23-1: Location reporting trigger override indication
Information element
Status
Description
MC service ID
M
Identity of the MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) who cancels the override
Functional alias
O
Functional alias that corresponds to the MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) who cancels the override
MC service ID list
M
List of identities of the MC service users for who trigger override is cancelled
Functional alias
O
Functional alias that corresponds to the MC service users for who trigger override is cancelled
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3 Procedure
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
NOTE 4: A subsequent update to the location reporting configuration may contain only the information elements that need updating, from Table 10.9.2.1-1. The IEs that are not changed will retain the previous values.
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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 of an authorized MC user whose MC service ID is among the list of MC service users which sharing location information of the target (requested) MC service user is authorised,, 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. 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.
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, 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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.3 Client-triggered location reporting procedure
|
NOTE 1: 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.
Pre-conditions:
1. If the trigger involves an MC service group ID (list), the LMS has previously subscribed to group dynamic data from the MC service server, as per 10.1.5.6.4.1.
If the trigger involves an MC service group ID (list), the LMS has previously subscribed to group dynamic data from the MC service server, as per 10.1.5.6.4.1.
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 start a location reporting procedure for obtaining the location information. The location reporting trigger request contains MC service ID list or MC service group ID list or Functional alias list to obtain the the location information. Location management server checks whether location management client 2 has subscribed to and is authorized to send a location reporting trigger for location management client 1's location information.
2. If step (1) involves an MC service group ID list:
- The MC service server notifies group affiliation status to the LMS as per 10.1.5.6.4.2. The LMS will update the list of currently affiliated users.
3. If the location reporting trigger request contains MC service ID list or Functional alias list, depending on the information specified by the location reporting trigger and aggregation of other trigger requests towards the same target location management client, 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.
If the location reporting trigger request contains MC service group ID list, the location management server initiates an event-triggered location reporting procedure. The LMS will trigger location reports for only the currently affiliated users of the group, based on the last notification from the MC service server, as per step 2. The LMS will cancel the current location reporting trigger for the users who have de-affiliated from the service group ID lists(s).
NOTE 2: If the location reporting trigger request contains MC service group ID list, steps 2 and 3 shall be repeated as per the group affiliation status notifications are received.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.4 Event-triggered location reporting cancel procedure
|
NOTE: This procedure is valid for single MC system operation only.
The event-triggered 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: Event-triggered 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.4a Client-triggered location reporting cancel procedure targeting MC service user(s)
NOTE 1: This procedure is valid for single MC system operation only.
Figure 10.9.3.4a-1 illustrates the high level procedure of client-triggered location reporting cancel procedure.
Pre-conditions:
- The location management client 1 has provided the location reporting trigger for the location management client 2.
Figure 10.9.3.4a-1: Client-triggered location reporting cancel procedure
1. Location management client 1 (authorized MC service user) sends a location reporting trigger cancel request to the location management server to deactivate a location reporting procedure for obtaining the location information of location management client 2.
2. Location management server checks whether location management client 1 is authorized to send a location reporting trigger cancel request for location management client 2's location information. If authorized, location management server initiates event-triggered location reporting cancel procedure for the location management client 2 as specified in the clause 10.9.3.4.
NOTE 2: The location management server, instead of cancelling the location reporting of location management client 2, can update the location reporting configuration if the location management client 2 is configured to report its location information based on the location reporting trigger received from other location management clients also other than location management client 1.
NOTE 3: The location management client (authorized MC service user) can cancel other location management clients (authorized MC service user) provided location reporting trigger for reporting location information.
10.9.3.4b Client-triggered location reporting cancel procedure targeting MC service group(s)
NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.4b-1 illustrates the high level procedure of client-triggered location reporting cancel procedure targeted to the MC service group(s).
Pre-conditions:
- The location management client 2 has provided the location reporting trigger for the MC service group(s).
- The location management server has subscribed to the dynamic data associated with the target MC service group(s).
Figure 10.9.3.4b-1: Client-triggered location reporting cancel procedure targeting MC service group(s)
1. Location management client 2 (authorized MC service user) sends a location reporting trigger cancel request to the location management server to deactivate a location reporting procedure for obtaining the location information from the affiliated members of the MC service group(s).
2. Location management server checks whether location management client 2 is authorized to send a location reporting trigger cancel request for MC service group(s). If authorized, the location management server initiates the event-triggered location reporting cancel procedure as specified in the clause 10.9.3.4 for the location management client(s) of the MC service user(s) affiliated to the MC service group(s) received in step 1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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. The request will contain the MC service ID list or the MC service group ID list.
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 need not to check the authorization for the MC service server.
3. If step (1) involves an MC service group ID list, the LMS subscribes to group dynamic data request as per clause 10.1.5.6.4.1, to obtain group affiliation data from the MC service server. The MC service server provides the response to this LMS request, as per clause 10.1.5.6.4.1.
4. The location management server replies with a location information subscription response indicating the subscription status.
5. If step (1) involves an MC service group ID list:
a) If the response in 3b) indicates success, the MC service server notifies group affiliation status of each MC service ID to the LMS as per 10.1.5.6.4.2, whenever there is a change in group affiliations.
b) The LMS will maintain and update a list of currently affiliated users inline with 5a) as the target user list to provide location information to the location management client as per this subscription.
6. If required, the location management server shall update the location reporting configuration of the target location management clients in order to provide the requested location information received in step 1.
NOTE 3: If the location reporting trigger request contains MC service group ID list, steps 5(a), 5(b) and step 6 shall be repeated as per the group affiliation status notifications are received.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.6 Usage of location information procedure
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
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. The location management server has verified that the subscribed MC service server or subscribed location management client is authorized to receive the user location information of the target MC service user.
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. If the location management client has subscribed to location information through a MC service group ID, the location management server will report back location information only for currently affiliated members to this MC service group.
NOTE 2: The MC service server does not receive the MC service UE label.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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 request on-demand location information at the location management server of an MC service user.
Pre-conditions:
- Requested location management clients has been provided with the location reporting configuration information.
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. Furthermore, it checks whether the requested location management client is authorised to share its location information with the requesting location management client.
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 location management clients being requested, by triggering an on-demand location report procedure as described in clause 10.9.3.2 depending on the requested location information (if any) in the location information request from the location management client or MC service server, 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. The request will contain the MC service ID list or the MC service group ID list.
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. If step (1) involves an MC service group ID, the LMS issues a group dynamic data cancel request to MC service server, as per clause 10.1.5.6.1.5. The MC service server will issue the response as per clause 10.1.5.6.1.6.
4. The location management server replies with a location information cancel subscription response indicating the cancel subscription status.
5. If step (1) involves an MC service group ID list, the LMS will delete the list of affiliated group members for the group ID(s).
6. The associated location reporting triggers (from the same authorized user or the MC service server to the same target MC service client(s) or group(s)) will be cancelled, as per procedure 10.9.3.4a
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.8 Location management using functional alias
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
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 resolves the target functional alias and checks whether location management client 1 is authorized to send a location reporting trigger for location information of location management clients 2 and 3. Furthermore, it checks whether each MC service user included in the location reporting trigger is authorized to share their location information with the requesting location management client, i.e., location management client 1.
3a, 3b. 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 reports, 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 information reports 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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
5. MC service client 2 has subscribed to location information from the functional alias that is shared by MC service client 2 and 3 as described in clause 10.9.3.5.
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 resolves the target functional alias and checks whether location management client 1 is authorized to send a location reporting trigger for location information for location management clients 2 and 3 that have activated the functional alias.
3a, 3b. Depending on the information given by the location reporting trigger and aggregation of other trigger requests towards the same target location management clients, the location management server uses event-triggered location information procedure to the location management clients that have activated the functional alias requested by the location management client 1.
NOTE 1: If the target functional alias is simultaneously shared between several MC service IDs, all location management clients with the associated MC service IDs will continue sending triggered location reports until the functional alias status change for the individual MC service ID.
NOTE 2: If the target functional alias has been newly activated for an MC service client, the location management server will also apply step 3 for this location management client.
NOTE 3: If the target functional alias is deactivated for an MC service client, the aggregated triggers for corresponding location management client may be updated and location reports from the corresponding location management client are no longer delivered to location management client 1.
4. Upon receiving the reports, the location management server updates location of the reporting location management clients.
5. The location management server checks whether location management client 2 and location management client 3 are authorized to share their location information with location management client 1.
6. Based on the received location information reports and the subscription by location management client 1, the location management server will periodically issue location information notifications, one at a time for each location management client for which location management client 1 is authorized to receive location information, 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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.8.3 Client-triggered location reporting cancel procedure targeting functional alias(es)
|
Figure 10.9.3.8.3-1 illustrates the procedure where a location management client requests to cancel the location reporting triggers targeted to the functional aliases which may be shared between several MC service users.
Pre-conditions:
1. MC service users at location management client 2 and location management client 3 share the same functional alias.
2. MC service users at location management client 2 and location management client 3 activated the functional alias.
3. MC service user at location management 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.3-1: Periodic location information report cancellation for shared functional alias
1. Location management client 1 (authorized MC service user) sends a location reporting trigger cancel request, limited to one MC service at the time, to the location management server to deactivate 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 cancel request for location information of the location management clients that have activated the functional alias. The location management server determines the functional alias to a corresponding list of related MC service IDs of location management client 2 and location management client 3 who have activated the functional alias.
3a-3b. Location management server initiates event-triggered location reporting cancel procedure for the location management client 2 and location management client 3 as specified in the clause 10.9.3.4
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.9 Usage of location history reporting procedure
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.9.1 General
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.9.2 Report location history procedure
|
10.9.3.9.2.1 On-demand report location history procedure (LMC – LMS)
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.
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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 whether 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. If there are no other authorized location management clients requesting the location history of location management client 1, the location management server executes the requested cancellation.
5. Location management server confirms the executed cancellation.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.10 Usage of location information across MC systems procedure
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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. It checks whether requesting location management client in the primary MC system is authorized to request the location information of the requested location management client in the partner MC system which is included in the location information request.
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. It checks whether the requested location management client in the partner MC system is authorised to share its location information with the requesting location management client in the primary MC system.
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 in the primary MC system.
8. If the requesting location information management client is still authorized to receive the location report, the location management server in the primary MC system sends the location information report to the requesting location information management client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
Pre-conditions:
1. The location management client in the primary MC system has subscribed to receive location reports from the location client in the partner MC system according to the procedure described in clause 10.9.3.10.4.
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 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 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 table 10.9.2.7-3.
5. The location management server in the primary MC system checks if the location management client is authorized to receive the location information and forwards the received location information, according to the procedure described in clause 10.9.3.6.1.
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
8. The location management server in the primary MC system sends the location information subscription response to the requesting entity in the primary MC system, according to the described information flow in clause 10.9.2.6.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
8. The location management server in the primary MC system sends the location information cancel subscription response to the requesting entity in the primary MC system, according to the described information flow in clause 10.9.2.9.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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 are 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 server in the partner MC system. 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.
9. The location management server in the partner MC system sends the location reporting temporary configuration response to the location management server in the primary MC system.
10. The location management server in the primary MC system sends the location reporting temporary configuration response to the location management client in the primary MC system.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.12 Location reporting trigger override
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.12.1 General
|
For operational/technical reasons (e.g., in order to reduce the signalling load in a cell) an authorized user can override the aggregated trigger configuration for one or more reporting location management clients.
The location reporting trigger override procedures only affect the triggers configured by requesting MC service users. The location management server shall ensure that triggers originating from the MC service servers are not affected, in order not to disturb system operation.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.12.2 Location reporting trigger override procedure
|
NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.12.2-1 illustrates the high level procedure of trigger override.
Pre-conditions:
1. MC service client 3 has subscribed to MC service client 1 as described in clause 10.9.3.5 and has applied location reporting triggers in MC service client 1 as described in clause 10.9.3.3.
Figure 10.9.3.12.2-1: Trigger override procedure
1. Location management client 2 (authorized MC service user) sends a location reporting trigger to the location management server requesting to override the existing triggers of location management client 1.
2. The location management server checks whether location management client 2 is authorized to override existing triggers of location management client 1.
3. The location management server stores locally the current location reporting configuration for location management client 1.
4. The location management server initiates an event-triggered location reporting procedure for location management client 1, applying the triggers requested by location management client 2 without performing aggregation of other trigger requests received from other location management clients.
5. The location management server informs location management client 3 about the location reporting trigger override by sending a location reporting trigger override indication.
NOTE 1: Location management clients that newly subscribe to location reports from MC service client 1 will receive a Location reporting trigger override indication at subscription until the trigger override for location management client 1 is cancelled.
NOTE 2: The location management server will apply newly initiated trigger requests for location management client 1 only to the stored configuration until the trigger override for location management client 1 is cancelled.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.9.3.12.3 Cancel location reporting trigger override procedure
|
NOTE: This procedure is valid for single MC system operation only.
Figure 10.9.3.12.3-1 illustrates the high level procedure of cancel trigger override.
Pre-conditions:
1. MC service client 3 has subscribed to MC service client 1 as described in clause 10.9.3.5 and has applied location reporting triggers in MC service client 1 as described in clause 10.9.3.3.
2. Previously MC service client 2 has initiated a trigger override procedure for MC service client 1 as described in clause 10.9.3.12.
Figure 10.9.3.12.3-1: Cancel trigger override procedure
1. Location management client 2 (authorized MC service user) sends a location reporting trigger to the location management server requesting to cancel the trigger override for location management client 1.
2. The location management server checks whether location management client 2 is authorized to override the existing triggers of location management client 1.
3. The location management server retrieves the location reporting configuration for location management client 1 which was stored locally.
4. The location management server initiates an event-triggered location reporting procedure for location management client 1, restoring the triggers that were retrieved in step 3.
5. The location management server informs location management client 3 about the cancellation of the location reporting trigger override by sending a location reporting cancel trigger override indication.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10 Emergency Alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1 On-network emergency alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.1 General
|
The following subclauses specify the procedures for emergency alert initiation, emergency alert cancel, entering emergency alert area and leaving emergency alert area that are utilised by the following MC services:
- MCPTT
- MCVideo
- MCData
10.10.1.1A Information flows
10.10.1.1A.1 MC service emergency alert request
Table 10.10.1.1A.1-1 describes the information flow MC service emergency alert request from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.1.1A.1-1: MC service emergency alert request information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
MC service group ID (see NOTE 1)
O
The target MC service group ID with which the alert is associated
MC service ID (see NOTE 2)
O
The target MC service ID of the alert.
Organization name
O
The alerting MC service user's mission critical organization name
Location
O
The alerting MC service client's location
NOTE 1: This information shall be present if the message is requesting an MC service emergency alert associated with a group.
NOTE 2: This information shall be present if the message is requesting an MC service emergency alert associated with an individual.
10.10.1.1A.2 MC service emergency alert response
Table 10.10.1.1A.2-1 describes the information flow MC service emergency alert response from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.1.1A.2-1: MC service emergency alert response information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
MC service group ID (see NOTE 1)
O
The target MC service group ID with which the alert is associated
MC service ID (see NOTE 2)
O
The target MC service ID of the alert.
NOTE 1: This information shall be present if the message is requesting an MC service emergency alert associated with a group.
NOTE 2: This information shall be present if the message is requesting an MC service emergency alert associated with an individual.
10.10.1.1A.3 MC service emergency alert cancel request
Table 10.10.1.1A.3-1 describes the information flow MC service emergency alert cancel request from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.1.1A.3-1: MC service emergency alert cancel request information elements
Information Element
Status
Description
MC service ID
M
MC service user identity of the cancelling party
Functional alias
O
The functional alias of the cancelling party
MC service ID (see NOTE 1)
O
MC service user identity whose emergency alert is to be cancelled
MC service group ID (see NOTE 2)
O
The MC service group ID to be informed about the alert cancellation
MC service ID (see NOTE 3)
O
MC service ID to be informed about the alert cancellation.
Group's in-progress emergency state cancel request
O
Requests cancellation of the in-progress emergency state of the group
NOTE 1: This information shall be present if the message is requesting cancellation of another MC service user's alert. If not present, then the alert of the MC service ID of the cancelling party is being cancelled
NOTE 2: This information shall be present if the message is requesting cancellation of an MC service emergency alert associated with a group.
NOTE 3: This information shall be present if the message is requesting cancellation of an MC service emergency alert associated with an individual.
10.10.1.1A.4 MC service emergency alert cancel response
Table 10.10.1.1A.4-1 describes the information flow MC service emergency alert cancel response from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.1.1A.4-1: MC service emergency alert cancel response information elements
Information Element
Status
Description
MC service ID
M
The identity of the cancelling party
MC service group ID
(see NOTE)
O
The MC service group ID with which the alert is associated
NOTE: This information shall be present if the message is requesting cancellation of an MC service emergency alert associated with a group.
10.10.1.1A.5 MC service emergency alert area notification
Table 10.10.1.1A.5-1 describes the information flow MC service emergency alert area notification from the MC service server to the MC service client.
Table 10.10.1.1A.5-1: MC service emergency alert area notification information elements
Information Element
Status
Description
MC service ID
M
MC service user identity of the party to be notified
Emergency Alert Area Indicator
M
An indicator that the MC service user is in an Emergency Alert Area or out of an Emergency Alert Area.
NOTE: Normally, the pre-defined area that triggers the emergency alert and the pre-defined area that triggers the out of MC service alert area notification is not the same.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.2 MC service emergency alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.2.1 MC service emergency alert initiation
|
10.10.1.2.1.1 General
These procedures describe cases where an MC service client is initiating an MC service emergency alert unicast signalling for communicating the alert with the affiliated MC service group members of an MC service group, or for communicating an alert to another MC service client. An MC service client in the MC service emergency state gains elevated access privilege for all of the MC service user's mission critical applications. These procedures will place the MC service client in the MC service emergency state if the MC service client is not already in that state.
10.10.1.2.1.2 MC service group emergency alert initiation
Figure 10.10.1.2.1.2-1 illustrates the procedure for the MC service client initiating an MC service emergency alert with an MC service group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same MC service group which is defined on group management server.
NOTE 1: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server.
Pre-conditions:
1. The MC service group to be used for emergency communications by MC service client 1 is previously defined on the group management server and MC service client 2 and MC service client 3 are affiliated to that MC service group.
NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the currently selected group.
2. All members of the MC service group belong to the same MC system.
3. The initiating MC service client 1 is affiliated with one or more MC service groups.
4. The initiating MC service client 1 may not have carried out an explicit affiliation procedure with the MC service group designated as the MC service emergency group.
5. Optionally, MC service client 1 may use an activated functional alias for the group communication.
6. The MC service server may have subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.10.1.2.1.2-1 MC service group emergency alert
1. The MC service user at the MC service client 1 initiates an MC service emergency alert. MC service client 1 sets its MC service emergency state. The MC service user at MC service client 1 may select a functional alias used for the MC service group emergency alert. The MC service emergency state is retained by the MC service client 1 until explicitly cancelled.
2. MC service client 1 requests the MC service server to send an MC service emergency alert request to the MC service group designated as the MC service emergency group.
3. MC service server checks whether the MC service user of MC service client 1 is authorized for initiation of MC service group emergency alerts for the indicated MC service group. The MC service server checks whether the provided functional alias, if present, can be used and has been activated for the user.
4. MC service server resolves the MC service group ID to determine the members of that MC service group and their affiliation status, based on the information from group management server.
5. The MC service server sends the MC service emergency alert response to the MC service user 1 to confirm the MC service emergency alert request. All MC service group calls made by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled. All MC service private calls made by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled.
6. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per user profile configuration) and the MC service user's mission critical organization name. If in step 2, the MC service client 1 does not include the location information in the MC service emergency alert request to the MC service server, the MC service server acquires the location information of the MC service user at the MC service client 1 from the location management server. If the location information is included in step 2, then the MC service server uses the location information from MC service client 1.
7. MC service users are notified of the MC service emergency alert. The functional alias of the group call initiating MC service user may be displayed.
8. The receiving MC service clients send the MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert.
9. The MC service server implicitly affiliates the client to the emergency group if the client is not already affiliated.
NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state.
NOTE 4: Sending the emergency alert does not put the other UEs in the group into an emergency state.
NOTE 5: The MC service client 1 need not initiate a group call. For example, the MC service client can be configured to only allow alerts or the MC service user can choose not to make an MC service emergency group call.
NOTE 6: It is configured whether MC service client 1 automatically triggers a subsequent MC service emergency group call.
Editor's note: How emergency alert is synchronized between MC services is FFS.
10.10.1.2.1.3 MC service individual emergency alert initiation
Figure 10.10.1.2.1.3-1 illustrates the procedure for the MC service client initiating an MC service individual emergency alert. This emergency alert can be sent at the time of emergency private call initiation as specified in subclause 10.7.2.4.1 of TS 23.379 [16], or it can also be sent standalone as described below.
Pre-conditions:
1. The MC service ID of MC service client 2 is previously defined to be used for emergency communications by MC service client 1.
2. Optionally, MC service client 1 may use an activated functional alias for individual communication.
3. The MC service server may have subscribed to the MC service functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.10.1.2.1.3-1 MC service individual emergency alert
1. The MC service user at the MC service client 1 initiates an MC service individual emergency alert. MC service client 1 sets its MC service emergency state. The MC service user at MC service client 1 may select a functional alias to be used for the MC service individual emergency alert. MCPTT client 1 retains the MC service emergency state until explicitly cancelled by the user of MC service client 1.
2. MC service client 1 requests the MC service server to send an MC service emergency alert request to MC service client 2 that has been designated as the target of MC service emergency communication by MC service client 1.
3. MC service server checks whether the MC service user of MC service client 1 is authorized for initiation of an MC service individual emergency alerts. The MC service server checks whether the provided functional alias, if present, can be used and has been activated for the user.
4. The MC service server sends the MC service emergency alert response to the MC service user 1 to confirm the MC service emergency alert request.
NOTE 1: While MC service client 1 is in the emergency state, all MC service group and private calls initiated by MC service client 1 are initiated as MC service emergency calls.
5. The MC service server sends an MC service emergency alert request toward MC service client 2. The MC service emergency alert request message shall contain the following information: Location, MC service ID, and the MC service user's mission critical organization name. If in step 2, the MC service client 1 does not include the location information in the MC service emergency alert request to the MC service server, the MC service server acquires the location information of the MC service user at the MC service client 1 from the location management server. If the location information is included in step 2, then the MC service server uses the location information from MC service client 1.
6. MC service user of MC service client 2 is notified of the MC service emergency alert. The functional alias of the initiating MC service user may be displayed.
NOTE 2: MC service client 2 does not set its emergency state as a result of receiving the MC service emergency alert.
7. The receiving MC service client 2 sends the MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert.
NOTE 3: The MC service client 1 need not initiate a private call to MC service client 2.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.2.2 MC service emergency alert cancel
|
10.10.1.2.2.1 General
These procedures describe cases where an MC service client has initiated an MC service emergency alert and entered the emergency state, and wishes to cancel the alert. For group-based alerts the cancellation informs the MC service server and other group members of this cancellation. By doing so, the MC service client may also request the cancellation of the in-progress emergency state of the group. For individual-based alerts the cancellation informs the MC service server and the MC service user designated as the target of MC service emergency communication.
In both cases the cancellation of the MC service emergency alert clears the emergency state of the MC service client.
For group-based emergency alerts, the emergency state of the MC service user can alternatively be cancelled using the MC service in-progress emergency group state cancellation procedures in 3GPP TS 23.379 [16], TS 23.281[12], and TS 23.282 [13].
10.10.1.2.2.2 MC service group emergency alert cancel
Figure 10.10.1.2.2.2-1 illustrates the procedure for the MC service client cancelling an MC service emergency alert with an MC service group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same MC service group which is defined on MC service group management server.
NOTE 1: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server.
Pre-conditions:
1. The MC service client 1 had previously successfully initiated an MC service emergency alert targeted to a group.
2. The MC service client 1 is still in the emergency state.
3. The initiating MC service client 1 has affiliated with the MC service group designated as the MC service emergency group.
Figure 10.10.1.2.2.2-1 MC service group emergency alert cancel
1. The MC service user at the MC service client 1 initiates an MC service emergency alert cancel to inform the server that MC service client 1 is no longer in the emergency state.
NOTE 2: The MC service emergency alert cancel request can carry an indication to also request that the in-progress emergency of the group is to be cancelled. The MC service server can accept or deny the request to cancel the in-progress emergency state of the group as a whole, separately from accepting or denying the request to cancel the emergency alert at MC service client 1. An authorized user (e.g. dispatcher, supervisor) can cancel either or both the in-progress emergency state of the group and the MC service emergency alert of another user. A MC service user is always authorized to cancel the emergency state of their own client. Determination of authorized users is implementation dependent.
2. MC service client 1 requests the MC service server to send an MC service emergency alert cancel to the MC service group to which MC service client 1 had previously sent the emergency alert.
3. MC service server resolves the MC service group ID to determine the members of that MC service group and their affiliation status, based on the information from group management server.
4. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 clears its emergency state.
5. The MC service server sends an MC service emergency alert cancel request towards the MC service clients of each of those affiliated MC service group members.
6. MC service users are notified of the MC service emergency alert cancellation of MC service client 1.
7. For a unicast MC service emergency alert cancel, the receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel. For a multicast MC service emergency alert cancel, these acknowledgements are not sent unless the MC service clients have been configured to do so.
10.10.1.2.2.3 MC service individual emergency alert cancel
Figure 10.10.1.2.2.3-1 illustrates the procedure for the MC service client cancelling an individual MC service emergency alert (i.e. without an associated MC service group).
Pre-conditions:
1. The MC service client 1 had previously successfully initiated an individual MC service emergency alert targeted to MC service client 2.
2. The MC service client 1 is still in the emergency state.
Figure 10.10.1.2.2.3-1 MC service individual emergency alert cancel
1. The MC service user at the MC service client 1 initiates an MC service individual emergency alert cancel for an individual emergency alert.
2. MC service client 1 sends the MC service emergency alert cancel request to the MC service server to inform the server that MC service client 1 is no longer in the emergency state. The emergency alert cancel request contains the MC service ID of MC service client 2.
3. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 clears its emergency state.
4. The MC service server sends an MC service emergency alert cancel request towards MC service client 2.
5. The MC service user of MC service client 2 is notified of the MC service emergency alert cancellation of MC service client 1.
6. MC service client 2 sends the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.2.3 Entering MC service emergency alert area
|
The procedure focuses on the case where an MC service emergency alert to be triggered when an MC service UE moves into a pre-defined area. This procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.
Procedures in figure 10.10.1.2.3-1 are the signalling control plane procedures for the MC service server triggering an MC service emergency alert with an MC service group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same MC service group which is defined on MC service group management server. This procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.
NOTE: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server.
Pre-conditions:
1. The MC service group is previously defined on the group management server with MC service client 2 and MC service client 3 affiliated to that MC service group.
2. All members of the MC service group belong to the same MC system.
3. An area in which the MC service client should send emergency alert is pre-defined in MC service server.
Figure 10.10.1.2.3-1 Entering MC service emergency alert area
1. MC service server acquires the latest location information of user at MC service client 1 from location management server as described in 10.9.3.6.
2. MC service server checks whether MC service client 1 has moved into a pre-defined area.
3. If so, MC service server sends an MC service emergency alert area notification to MC service client 1 to notify that it has moved into the area in potential danger.
4. MC service client 1 notifies the MC service user about the MC service emergency alert area.
5. MC service client 1 initiates MC service emergency alert procedure as described in 10.10.1.2.1.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.1.2.4 Leaving MC service emergency alert area
|
This procedure focuses on the case where a notification is sent when an MC service UE moves out of a pre-defined area. This procedure will notify the MC service client that it is now out of the pre-defined emergency alert area. It is up to the MC service user at that MC service client to determine if the emergency state is to be cleared or not.
Procedures in figure 10.10.1.2.4-1 are the signalling control plane procedures for the MC service server sends an MC service emergency alert area notification. It is optional if the MC service user wants to initiate the MC service emergency alert cancel procedure to inform the members in the MC service group that its emergency condition is over.
NOTE 1: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server.
Pre-conditions:
1. The MC service group is previously defined on the group management server with MC service client 2 and MC service client 3 affiliated to that MC service group. This MC service group has been pre-defined for communicating the emergency alert in the user profile.
2. All members of the MC service group belong to the same MC system.
3. An area in which the emergency alert for the MC service client should remain active is pre-defined in MC service server.
Figure 10.10.1.2.4-1 Leaving MC service emergency alert area
1. MC service server acquires the latest location information of user at MC service client 1 from location management server as described in subclause 10.9.3.6.
2. MC service server checks whether MC service client 1 has moved out a pre-defined area.
3. If so, MC service server sends an MC service emergency alert area notification to MC service client 1 to notify that it has moved out of the area in potential danger.
4. MC service client 1 notifies the MC service user about the MC service emergency alert area cancel. It is up to the MC service user at the MC service client 1 to determine if the emergency state is clear.
5. Optionally, the MC service user of MC service client 1 initiates MC service emergency alert cancel procedure as described in 10.10.1.2.2.
NOTE 2: It is up to the MC service user to clear the local emergency state on the client after the MC service UE has moved out of the emergency alert area, the MC service server cannot clear the client's local emergency state.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.2 Off-network emergency alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.2.1 General
|
The following subclauses specify the procedures for emergency alert initiation and emergency alert cancel that are utilised by the following MC services:
- MCPTT
- MCVideo
- MCData
10.10.2.1A Information flows
10.10.2.1A.1 MC service emergency alert announcement
Table 10.10.2.1A.1-1 describes the information flow for the MC service emergency alert announcement from the MC service client to the other MC service clients.
Table 10.10.2.1A.1-1: MC service emergency alert announcement information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting MC service user
MC service group ID
M
The MC service group ID with which the alert is associated
Location
O
The alerting client's location, if known
Organization name
M
The alerting user's mission critical organization name
10.10.2.1A.2 MC service emergency alert cancel announcement
Table 10.10.2.1A.2-1 describes the information flow for the MC service emergency alert cancel announcement from the MC service client to other MC service clients.
Table 10.10.2.1A.2-1: MC service emergency alert cancel announcement information elements
Information Element
Status
Description
MC service ID
M
The identity of the cancelling MC service user
MC service group ID
M
The MC service group ID with which the alert is associated
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.2.2 MC service emergency alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.2.2.1 Emergency alert initiation
|
Figure 10.10.2.2.1-1 describes procedures for the MC service client initiating an MC service emergency alert with an MC service group.
This procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state.
Pre-conditions:
1. The initiating MC service client 1 has been provisioned with an MC service group designated as the MC service emergency group.
NOTE 1: Alternatively, MC service client 1 could have been provisioned for emergency behaviour on the currently selected group.
2. Information for ProSe direct communications corresponding to the MC service group and its mapping to ProSe Layer-2 Group ID are pre-configured in MC service client 1.
3. MC service clients 2 and 3 belong to and are ready for off-network communications on the MC service group.
Figure 10.10.2.2.1-1: Emergency alert initiation
1. MC service client 1 sets its MC service emergency state. This MC service emergency state is retained by the MC service client until explicitly cancelled. Once MC service client1 is in the MC service emergency state, any communications initiated by MC service client 1, group or private, shall be initiated as emergency communications and shall receive priority treatment.
2. MC service client 1 sends an MC service emergency alert announcement to the other participants on the MC service emergency group. The MC service emergency alert announcement is sent periodically so that late joining MC service group members are notified.
NOTE 2: Sending the emergency alert without making a request to also start an MC service emergency communication does not put the group into the in-progress emergency state.
3. MC service users are notified of the MC service emergency state of the originating MC service user.
4. The MC service clients upon receiving the emergency alert announcement message acknowledge the MC service emergency alert to the originating MC service client.
NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state.
NOTE 4: The MC service client 1 needs not initiate a group communication. For example, the MC service client can be configured to only allow alerts or the MC service user can choose not to make an MC service emergency group communication.
NOTE 5: MC service clients need to respond only to the first emergency alert announcement message that is received.
NOTE 6: It is configured if MC service client 1 will automatically trigger a subsequent MC service emergency group call.
5. The originating MC service client 1 checks the responses and may inform the MC service user of the MC service group members whose MC service clients responded.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.2.2.2 Emergency alert cancel
|
An MC service client has initiated an MC service emergency alert, has entered the MC service emergency state and wishes to cancel the alert, informing the other MC service group members of the cancellation. As part of this process, the MC service client may also request the cancellation of the in-progress emergency state in the group if authorized to do so.
Procedures in figure 10.10.2.2.2-1 describe procedures for the MC service client cancelling an MC service emergency alert.
Pre-conditions:
1. The MC service client 1 has successfully initiated an MC service emergency alert and is in the MC service emergency state.
2. Information for ProSe direct communications corresponding to the MC service group and its mapping to ProSe Layer-2 Group ID are pre-configured in MC service client 1.
3. The initiating MC service client 1 and MC service clients 2 and 3 are still in off-network contact via the MC service group provisioned to MC service client 1 as for the MC service emergency group.
Figure 10.10.2.2.2-1 Emergency alert cancel
1. The user at the MC service client 1 initiates an MC service emergency alert cancel.
2. MC service client 1 sends an MC service emergency alert cancel announcement to the MC service group to which MC service client 1 had previously sent the emergency alert announcement message.
3. MC service users are notified of the MC service emergency alert cancellation by MC service client 1.
4. The receiving MC service clients acknowledge the MC service emergency alert cancel to the originating MC service client.
NOTE: MC service clients that track the MC service emergency alerts of other MC service users, e.g. clients that fail to receive subsequent periodic MC service emergency alert announcements after a configured timeout can consider the alert to be cancelled.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3 Ad hoc group emergency alert
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.1 General
|
The following subclauses specify the procedures for ad hoc group emergency alert initiation, ad hoc group emergency alert cancel, entering an ongoing ad hoc group emergency alert and leaving an ad hoc group emergency alert that are utilised by the following MC services:
- MCPTT
- MCVideo
- MCData
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.1 Ad hoc group emergency alert request (MC service client – MC service server)
|
Table 10.10.3.2.1-1 describes the information flow ad hoc group emergency alert request from the MC service client to the MC service server.
Table 10.10.3.2.1-1 Ad hoc group emergency alert request information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
Ad hoc group ID (see NOTE)
O
The group ID which is generated by the MC service user to be used for the ad hoc group alert
Organization name
O
The alerting MC service user's mission critical organization name
Location information
O
The alerting MC service client's location
Criteria for determining the participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MC service server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
Additional information
O
The alerting party may provide additional information related to the alert, e.g., medical help needed or reason for the alert
NOTE: If this information element is not included, then the MC service server shall assign one to be used for the ad hoc group emergency alert and shall return it to the alerting party.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.2 Ad hoc group emergency alert request (MC service server – MC service client)
|
Table 10.10.3.2.2-1 describes the information flow ad hoc group emergency alert request from the MC service server to the MC service client.
Table 10.10.3.2.2-1 Ad hoc group emergency alert request information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
Ad hoc group ID
M
The target group ID associated with the alert
Organization name
O
The alerting MC service user's mission critical organization name
Location information
O
The alerting MC service client's location
Additional information
O
The alerting party may provide additional information related to the alert, e.g., medical help needed or reason for the alert
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MC service server used for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
10.10.3.2.2a Ad hoc group emergency alert request return
Table 10.10.3.2.2a-1 describes the information flow ad hoc group emergency alert request return from the MC service server to the MC service client.
Table 10.10.3.2.2a-1 Ad hoc group emergency alert request return information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
Authorization result
M
Indicate if authorization is success or failure
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.3 Ad hoc group emergency alert response
|
Table 10.10.3.2.3-1 describes the information flow ad hoc group emergency alert response from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.3.2.3-1 Ad hoc group emergency alert response information elements
Information Element
Status
Description
MC service ID
M
The identity of the target party
Functional alias
O
The functional alias of the target party
Ad hoc group ID
M
The target group ID associated with the alert
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MC service server used for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.4 Ad hoc group emergency alert cancel request
|
Table 10.10.3.2.4-1 describes the information flow ad hoc group emergency alert cancel request from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.3.2.4-1 Ad hoc group emergency alert cancel request information elements
Information Element
Status
Description
MC service ID
M
MC service user identity of the cancelling party
Functional alias
O
The functional alias of the cancelling party
MC service ID (see NOTE)
O
MC service user identity whose emergency alert is requested to be cancelled
Ad hoc group ID
M
The ad hoc group ID with which the alert is associated
Group's in-progress emergency state cancel request
O
Requests cancellation of the in-progress emergency state of the group
Additional information
O
The cancelling party may provide additional information related to cancelling the alert, e.g., technical issue resolved or medical help provided.
NOTE: This information shall only be present if the message is requesting cancellation of another MC service user's alert. If not present, then the alert of the MC service ID of the cancelling party is being cancelled.
10.10.3.2.4a Ad hoc group emergency alert cancel request return
Table 10.10.3.2.4a-1 describes the information flow ad hoc group emergency alert cancel request return from the MC service server to the MC service client.
Table 10.10.3.2.4a-1 Ad hoc group emergency alert cancel request return information elements
Information Element
Status
Description
MC service ID
M
The identity of the cancelled party
Functional alias
O
The functional alias of the cancelled party
Authorization result
M
Indicate if authorization is success or failure
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.5 Ad hoc group emergency alert cancel response
|
Table 10.10.3.2.5-1 describes the information flow ad hoc group emergency alert cancel response from the MC service client to the MC service server and from the MC service server to the MC service client.
Table 10.10.3.2.5-1 Ad hoc group emergency alert cancel response information elements
Information Element
Status
Description
MC service ID
M
The identity of the cancelled party
Functional alias
O
The functional alias of the cancelled party
Ad hoc group ID
M
The ad hoc group ID associated with the alert
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.6 Ad hoc group emergency alert participants list notification
|
Table 10.10.3.2.6-1 describes the information flow ad hoc group emergency alert participants list notification from the MC service server to the MC service client.
Table 10.10.3.2.6-1: Ad hoc group emergency alert participants list notification information elements
Information Element
Status
Description
MC service ID
M
The identity of the notified participant
Functional alias
O
The functional alias of the notified participant
Ad hoc group ID
M
The group ID associated with the ad hoc group emergency alert
MC service user ID list
O
The total list of MC service users who belong to the ad hoc group irrespective of having acknowledged the ad hoc group emergency alert or not
MC service user ID list
O
The list of MC service users who belong to the ad hoc group but have not acknowledged the ad hoc group emergency alert
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which may be used by the authorized users to modify it.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.7 Ad hoc group emergency alert get userlist request
|
Table 10.10.3.2.7-1 describes the information flow of an ad hoc group emergency alert get userlist request sent from an MC service server at a primary MC system to another MC service server at a partner MC system.
Table 10.10.3.2.7-1: Ad hoc group emergency alert get userlist request
Information Element
Status
Description
Criteria for determining the participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MC service server for determining the participants, e.g., it can be a location-based criteria to invite participants in a particular area
MC group ID
M
The identity of the ad hoc group associated with the emergency alert
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.8 Ad hoc group emergency alert get userlist response
|
Table 10.10.3.2.8-1 describes the information flow of an ad hoc group emergency alert get userlist response sent from an MC service server at a partner MC system to the MC service server at the primary MC system, whose MC service user has initiated the ad hoc group emergency alert.
Table 10.10.3.2.8-1: Ad hoc group emergency alert get userlist response
Information Element
Status
Description
MC service ID list
M
List of MC service IDs meeting the criteria specified in the ad hoc group emergency alert get userlist request
MC group ID
M
The identity of the ad hoc group associated with the emergency alert
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.9 Ad hoc group emergency alert user add notification
|
Table 10.10.3.2.9-1 describes the information flow of an ad hoc group emergency alert user add notification sent from an MC service server at a partner MC system to the MC service server at the primary MC system, whose MC service user has initiated the ad hoc group emergency alert.
Table 10.10.3.2.9-1: Ad hoc group emergency alert user add notification
Information Element
Status
Description
MC service ID
M
The identity of an MC service client to be added to an ongoing ad hoc group emergency alert
MC group ID
M
The identity of the ad hoc group associated with the emergency alert
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.10 Ad hoc group emergency alert user remove notification
|
Table 10.10.3.2.10-1 describes the information flow of an ad hoc group emergency alert user remove notification sent from an MC service server at a partner MC system to the MC service server at the primary MC system, whose MC service user has initiated the ad hoc group emergency alert.
Table 10.10.3.2.10-1: Ad hoc group emergency alert user remove notification
Information Element
Status
Description
MC service ID
M
The identity of an MC service client to be removed from an ongoing ad hoc group emergency alert
MC group ID
M
The identity of the ad hoc group associated with the emergency alert
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.11 Ad hoc group emergency alert notify
|
Table 10.10.3.2.11-1 describes the information flow for an ad hoc group emergency alert notify sent from MC service server to MC service client.
Table 10.10.3.2.11-1: Ad hoc group emergency alert notify
Information element
Status
Description
MC service ID
M
The identity of the MC service client participating in the ad hoc group emergency alert
Functional alias
O
The associated functional alias of the MC service user of the ad hoc group emergency alert participant
MC group ID
M
The ad hoc MC group ID associated with the emergency alert
MC service ID list
O
The list of the invited MC service users who acknowledge the ad hoc group emergency alert request, when MC service users join or leave the ad hoc group emergency alert. Or the list of the participating MC service users in the terminated ad hoc group emergency alert.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.12 Ad hoc group emergency alert modify request
|
Table 10.10.3.2.12-1 describes the information flow ad hoc group emergency alert modify request from the MC service client to the MC service server and from the MC service server to the MC service server.
Table 10.10.3.2.12-1: Ad hoc group emergency alert modify request information elements
Information Element
Status
Description
MC service ID
M
The identity of the requesting MC service user who is authorised to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MC service user who is authorized to modify the ad hoc group criteria
Ad hoc group ID
M
The group ID used for the ad hoc group alert
Location information
O
The requesting MC service client's location
Criteria to determine the list of participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MC service server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
Additional information
O
The requesting party may provide additional information related to the alert, e.g., medical help needed or reason for the alert
10.10.3.2.12a Ad hoc group emergency alert modify request return
Table 10.10.3.2.12a-1 describes the information flow ad hoc group emergency alert modify request return from the MC service server to the MC service client.
Table 10.10.3.2.12a-1 Ad hoc group emergency alert modify request return information elements
Information Element
Status
Description
MC service ID
M
The identity of the requesting MC service user
Functional alias
O
The functional alias of the requesting MC service user
Authorization result
M
Indicate if authorization is success or failure
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.2.13 Ad hoc group emergency alert modify response
|
Table 10.10.3.2.13-1 describes the information flow ad hoc group emergency alert modify response from the MC service server to the MC service client and from the MC service server to the MC service server.
Table 10.10.3.2.13-1: Ad hoc group emergency alert modify response information elements
Information Element
Status
Description
MC service ID
M
The identity of the requesting MC service user who is authorised to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MC service user who is authorised to modify the ad hoc group criteria
MC service server Ad hoc group ID
M
The MC service server group ID of the ad hoc group whose criterion for determining the participants is modified
Result
M
Indicates the success or failure for the result
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MC service server used for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3 Procedures within single MC system
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3.1 Ad hoc group emergency alert initiation
|
Figure 10.10.3.3.1-1 illustrates the procedure for the MC service client initiating an ad hoc group emergency alert initiated by an authorized MC service user.
Pre-conditions:
1. The MC service user at MC service client 1 wants to send an ad hoc group emergency alert to the MC service users who are satisfying certain criteria.
2. All MC service clients belong to the same MC system.
3. The MC service user on MC service client 3 is authorized to receive ad hoc group participants information.
Figure 10.10.3.3.1-1: Ad hoc group emergency alert initiation
1. The MC service user at the MC service client 1 initiates an ad hoc group emergency alert to an ad hoc group with participants satisfying specific criteria. The MC service user may add additional information describing the reason for sending the alert.
2. MC service client 1 initiates the ad hoc group emergency alert by sending the ad hoc group emergency alert request containing the details of the criteria to be applied by the MC service server for determining the participants list or the list of participants. MC service client 1 may set its MC service emergency state. The MC service user at MC service client 1 may select a functional alias used for the MC service group emergency alert. If MC service client 1 is in MC service emergency state, the MC service emergency state is retained by the MC service client 1 until explicitly cancelled.
3. MC service server checks whether the MC service user of MC service client 1 is authorized for initiation of ad hoc group emergency alerts and whether the request is supported. The MC service server checks whether the provided functional alias, if present, can be used and has been activated for the user.
4. The MC service server sends the ad hoc group emergency alert request return to the MC service user 1 containing the result of whether the ad hoc group call is authorized or not. If the ad hoc group emergency alert request is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
5. The MC service server determines the list of participants to be invited for the ad hoc group emergency alert based on the information present in the information element Criteria for determining the participants. This information element could carry either criteria or indicator identifying the criteria or combination of both. The MC service server stores the ad hoc group ID together with the list of participants for the duration of the ad hoc group emergency alert. The MC service server considers the alerted participants as implicitly affiliated to the ad hoc group. Depending on the criteria provided and based on local policy, the MC service server may modify the content of the criteria received in step 1 to determine the list of participants.
6. The MC service server sends an ad hoc group emergency alert request including the ad hoc group ID, and the call resulting criteria towards the MC service clients 2 and 3.
7. MC service users are notified of the ad hoc group emergency alert. The functional alias of the MC service user initiating the ad hoc group emergency alert and additional information related to the alert may be displayed.
8. The receiving MC service clients send the ad hoc group emergency alert response to the MC service server to acknowledge the ad hoc group emergency alert.
9. The MC service server sends the ad hoc group emergency alert response to MC service client 1 to inform about successful alert establishment, containing the ad hoc group ID (generated by the MC service server in the case where the MC service ad hoc group ID created by the MC service client 1 is not acceptable or the case where the MC service ad hoc group ID was not provided by MC service client 1) and the call resulting criteria.
10. The authorized user on MC service client 3 is notified with the total list of MC service IDs of those MC service users who belong to the ad hoc group and a separate list of MC service IDs of MC service users who belong to the ad hoc group that have not acknowledged the ad hoc group emergency alert, and the call resulting criteria.
11. If configured, an MC service client may setup a subsequent ad hoc group emergency communication, using the ad hoc group ID from the ad hoc group emergency alert, according to 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] or 3GPP TS 23.282 [13].
NOTE 1: MC service client 1 may start the subsequent ad hoc group emergency communication after step 5.
NOTE 2: Sending the ad hoc group emergency alert without making a request to also start an ad hoc group emergency communication does not put the group into the in-progress emergency state.
NOTE 3: Sending the ad hoc group emergency alert does not put the other participants in the group into an MC service emergency state.
The MC service server shall resend an ad hoc group emergency alert request towards MC service client(s) who still satisfy the criteria but did not acknowledge the ad hoc group emergency alert.
The MC service server continuously checks whether other MC service clients meet or if participating MC service clients no longer meet the criteria for the ad hoc group emergency alert.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3.2 Ad hoc group emergency alert cancel
|
Figure 10.10.3.3.2-1 illustrates the procedure for the MC service client cancelling an ad hoc group emergency alert associated with an ad hoc group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same ad hoc group.
Pre-conditions:
1. The MC service client 1 is authorised to cancel the ad hoc group emergency alert (as configured in the user profile data according to 3GPP TS 23.379 [16], 3GPP TS 23.281 [4] or 3GPP TS 23.282 [5]).
2. The initiating MC service client 1 is a participant of the ad hoc group associated with the ongoing emergency alert.
Figure 10.10.3.3.2-1: Ad hoc group emergency alert cancel
1. The MC service user at the MC service client 1 initiates an ad hoc group emergency alert cancel to inform the MC service server that alert is to be cancelled.
NOTE 1: The ad hoc group emergency alert cancel request can carry an indication to also request that the in-progress emergency of the group is to be cancelled. The MC service server can accept or deny the request to cancel the in-progress emergency state of the group, separately from accepting or denying the request to cancel the emergency alert at MC service client 1.
2. MC service client 1 sends an ad hoc group emergency alert cancel request to the MC service server. If the cancel request is for another MC service user that initiated this emergency alert, that user’s MC service ID shall be included in the request.
3. MC service server checks whether the MC service user of MC service client 1 is authorized for cancellation of ad hoc group emergency alerts and whether the request is supported.
4. The MC service server sends the ad hoc group emergency alert cancel request return to the MC service client 1 containing the result of whether the ad hoc group emergency alert cancel is authorized or not. If the ad hoc group emergency alert cancel is not authorized, the MC service server and the MC service client 1 shall not proceed with the rest of the steps.
5. MC service server uses the ad hoc group ID to select the participants of that ad hoc group. If MC service client 1 has initiated the ad hoc group emergency alert and its MC service emergency state is set, then the MC service emergency state is cleared.
NOTE 2: If MC service client 1 has not initiated the ad hoc group emergency alert, the MC service emergency state on the MC service client which initiated the ad hoc group emergency alert is retained locally by the MC service client until explicitly manually cancelled by the MC service user.
NOTE 3: The MC service emergency state of an MC service client due to an ad hoc group emergency alert or an ad hoc group communication is considered as a different state as from an MC service emergency state set by an MC service emergency group call or an MC service group emergency alert.
6. The MC service server sends an ad hoc group emergency alert cancel request towards the participants of the ad hoc group associated with the ad hoc group emergency alert.
7. MC service users are notified of the ad hoc group emergency alert cancellation and the MC service emergency state is cleared.
8. The receiving MC service clients send the ad hoc group emergency alert cancel response to the MC service server to acknowledge the ad hoc group emergency alert cancel.
9. The MC service server sends the ad hoc group emergency alert cancel response to MC service client 1 to inform about successful alert cancellation.
NOTE 4: If there is no ongoing communication in the ad hoc group or once the ongoing communication in the ad hoc group is terminated, the MC service server removes the ad hoc group.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3.3 Entering an ongoing ad hoc group emergency alert
|
During an ongoing ad hoc group emergency alert, the MC service server continuously checks if additional MC service users meet the conditions of the ad hoc group emergency alert.
As illustrated in Figure 10.10.3.3.3-1 MC service client is added to the ad hoc group as the MC service client meets the criteria for receiving an ongoing ad hoc group emergency alert.
Pre-conditions:
1. An ad hoc group emergency alert has been initiated and the related ad hoc group exists.
2. The criteria for entering an ad hoc group emergency alert are known to the MC service server.
3. The MC service user on MC service client 2 is authorized to receive ad hoc group participants information.
Figure 10.10.3.3.3-1: Entering an ongoing ad hoc group emergency alert
1. MC service server acquires the latest information of the MC service user at the MC service client and checks whether the criteria for initiating an ad hoc group emergency alert to the MC service client are met. The MC service server considers the MC service client 1 to be implicitly affiliated to the ad hoc group associated to the emergency alert.
2. The MC service server sends an ad hoc group emergency alert request including the ad hoc group ID, and the call resulting criteria towards the MC service client 1 to notify that it has moved into potential danger. The MC service client 1 is added to the emergency ad hoc group.
3. MC service client 1 notifies the MC service user about the ad hoc group emergency alert.
4. The receiving MC service client 1 sends the ad hoc group emergency alert response to the MC service server to acknowledge the ad hoc group emergency alert.
5. The authorized user on MC service client 2 is notified with the total list of MC service IDs of those MC service users who belong to the ad hoc group including the newly added MC service client 1, and a separate list of MC service IDs of MC service users who belong to the ad hoc group that have not acknowledged the ad hoc group emergency alert, and the call resulting criteria.
6. If there is an ongoing ad hoc group emergency communication ongoing, the MC service server adds the MC service client to the list of ad hoc group emergency communication participants according to 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] or 3GPP TS 23.282 [13].
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.10.3.3.4 Leaving an ad hoc group emergency alert
|
During an ongoing ad hoc group emergency alert, the MC service server continuously checks if MC service users still meet the conditions of the emergency alert.
As illustrated in Figure 10.10.3.3.4-1 MC service client is removed from the ad hoc group associated with an ongoing ad hoc group emergency alert as the MC service client does not meet the criteria for the alert any longer and the emergency alert is removed from the MC service client.
Pre-conditions:
1. An ad hoc group emergency alert has been initiated and the related ad hoc group exists.
2. The MC service server is aware of the criteria for leaving an ad hoc emergency alert.
3. The MC service user on MC service client 2 is authorized to receive ad hoc group participants information.
Figure 10.10.3.3.4-1: Leaving an ad hoc group emergency alert
1. MC service server acquires the latest information of the MC service user at the MC service client 1 and checks whether the criteria for the ad hoc group emergency alert are still met. The MC service server deaffiliates the MC service client 1 from the ad hoc group associated to the emergency alert.
2. The MC service server sends an ad hoc group emergency alert cancel request to MC service client 1. The MC service client 1 is removed from the ad hoc group.
3. MC service client 1 notifies the MC service user that the emergency alert is cancelled.
4. The receiving MC service client 1 sends the ad hoc group emergency alert cancel response to the MC service server to acknowledge that the ad hoc group emergency alert is cancelled for this MC service user.
5. The authorized user on MC service client 2 is notified with the MC service IDs of those MC service users who are currently in the ad hoc group after removing MC service client 1 from the list.
NOTE: If a communication is ongoing in the ad hoc group for the MC service user, the MC service server will wait to remove the MC service user from the ad hoc group until the communication is terminated.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.