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

Content for  TS 23.280  Word version:  19.3.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   A…   B…   C…   E… 
10.10 Emergency Alert  10.10.1 On-network emergency alert  10.10.1.1 General  10.10.1.1A Information flows  10.10.1.1A.1 MC service emergency alert request  10.10.1.1A.2 MC service emergency alert response  10.10.1.1A.3 MC service emergency alert cancel request  10.10.1.1A.4 MC service emergency alert cancel response  10.10.1.1A.5 MC service emergency alert area notification  10.10.1.2 MC service emergency alert  10.10.1.2.1 MC service emergency alert initiation  10.10.1.2.1.1 General   10.10.1.2.1.2 MC service group emergency alert initiation   10.10.1.2.1.3 MC service individual emergency alert initiation   10.10.1.2.2 MC service emergency alert cancel  10.10.1.2.2.1 General   10.10.1.2.2.2 MC service group emergency alert cancel   10.10.1.2.2.3 MC service individual emergency alert cancel  
...

 

10.10  Emergency Alert  p. 219

10.10.1  On-network emergency alert  p. 219

10.10.1.1  General  p. 219

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 |R18|  p. 219

10.10.1.1A.1  MC service emergency alert request  p. 219
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.
Information element Status Description
MC service IDMThe identity of the alerting party.
Functional aliasOThe functional alias of the alerting party.
MC service group ID (see NOTE 1)OThe target MC service group ID with which the alert is associated.
MC service ID (see NOTE 2)OThe target MC service ID of the alert.
Organization nameOThe alerting MC service user's mission critical organization name
LocationOThe 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.
Up
10.10.1.1A.2  MC service emergency alert response  p. 220
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.
Information element Status Description
MC service IDMThe identity of the alerting party.
MC service group ID (see NOTE 1)OThe target MC service group ID with which the alert is associated.
MC service ID (see NOTE 2)OThe 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.
Up
10.10.1.1A.3  MC service emergency alert cancel request  p. 220
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.
Information element Status Description
MC service IDMMC service user identity of the cancelling party.
Functional aliasOThe functional alias of the cancelling party.
MC service ID (see NOTE 1)OMC service user identity whose emergency alert is to be cancelled.
MC service group ID (see NOTE 2)OThe MC service group ID to be informed about the alert cancellation.
MC service ID (see NOTE 3)OMC service ID to be informed about the alert cancellation.
Group's in-progress emergency state cancel requestORequests 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.
Up
10.10.1.1A.4  MC service emergency alert cancel response  p. 220
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.
Information element Status Description
MC service IDMThe identity of the cancelling party.
MC service group ID
(see NOTE)		OThe 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.
Up
10.10.1.1A.5  MC service emergency alert area notification  p. 221
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.
Information element Status Description
MC service IDMMC service user identity of the party to be notified.
Emergency Alert Area IndicatorMAn indicator that the MC service user is in an Emergency Alert Area or out of an Emergency Alert Area.
Up

10.10.1.2  MC service emergency alert  p. 221

10.10.1.2.1  MC service emergency alert initiation  p. 221
10.10.1.2.1.1  General   p. 221
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.
Up
10.10.1.2.1.2  MC service group emergency alert initiation   p. 222
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.
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.
  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.
Reproduction of 3GPP TS 23.280, Fig. 10.10.1.2.1.2-1: MC service group emergency alert
Figure 10.10.1.2.1.2-1: MC service group emergency alert
Up
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 9.
The MC service server implicitly affiliates the client to the emergency group if the client is not already affiliated.
Up
10.10.1.2.1.3  MC service individual emergency alert initiation   p. 223
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, 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.
Reproduction of 3GPP TS 23.280, Fig. 10.10.1.2.1.3-1: MC service individual emergency alert
Figure 10.10.1.2.1.3-1: MC service individual emergency alert
Up
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Up
10.10.1.2.2  MC service emergency alert cancel  p. 225
10.10.1.2.2.1  General   p. 225
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 TS 23.379, TS 23.281, and TS 23.282.
Up
10.10.1.2.2.2  MC service group emergency alert cancel   p. 225
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.
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.
Reproduction of 3GPP TS 23.280, Fig. 10.10.1.2.2.2-1: MC service group emergency alert cancel
Figure 10.10.1.2.2.2-1: MC service group emergency alert cancel
Up
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 6.
MC service users are notified of the MC service emergency alert cancellation of MC service client 1.
Step 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.
Up
10.10.1.2.2.3  MC service individual emergency alert cancel   p. 226
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.
Reproduction of 3GPP TS 23.280, Fig. 10.10.1.2.2.3-1: MC service individual emergency alert cancel
Figure 10.10.1.2.2.3-1: MC service individual emergency alert cancel
Up
Step 1.
The MC service user at the MC service client 1 initiates an MC service individual emergency alert cancel for an individual emergency alert.
Step 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.
Step 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.
Step 4.
The MC service server sends an MC service emergency alert cancel request towards MC service client 2.
Step 5.
The MC service user of MC service client 2 is notified of the MC service emergency alert cancellation of MC service client 1.
Step 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.
Up

Up   Top   ToC