hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.1 P0: start-stop
|
In this state, no private call control entity exists.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.2 P1: ignoring same call id
|
This state exists for UE, when the UE is not part of an ongoing private call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.3 P2: waiting for call response
|
This state exists for UE, when the UE has sent a PRIVATE CALL SETUP REQUEST message and is waiting for a response, PRIVATE CALL ACCEPT or PRIVATE CALL REJECT message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.4 P3: waiting for release response
|
This state exists for UE, when the UE has sent a PRIVATE CALL RELEASE message and is waiting for a PRIVATE CALL RELEASE ACK message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.5 P4: part of ongoing call
|
This state exists for UE, when the UE is part of an ongoing private call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.3.6 P5: pending
|
This state exists for UE, when the UE has presented a notification to the user for the received PRIVATE CALL SETUP REQUEST message and is waiting for a user indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4 Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.1 General
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2 Private call setup
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.1 Initiating a private call
|
When in the "P0: start-stop" state or "P1: ignoring same call id", upon an indication from MCPTT User to initiate a private call and the value of "/<x>/<x>/Common/PrivateCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", the MCPTT client:
1) shall generate and store the call identifier as a random number uniformly distributed between (0, 65536);
2) shall store own MCPTT user ID as caller ID;
3) shall store MCPTT user ID of the callee as callee ID;
4) shall store "AUTOMATIC COMMENCEMENT MODE" as commencement mode, if requested and the value of "/<x>/<x>/Common/PrivateCall/AutoCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise if the value of "/<x>/<x>/Common/PrivateCall/ManualCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", store "MANUAL COMMENCEMENT MODE" as commencement mode;
5) shall create a call type control state machine as described in clause 11.2.3.2;
6) if an end-to-end security context needs to be established then:
a) shall use keying material provided by the key management server to generate a PCK as described in 3GPP TS 33.180 [78];
b) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];
c) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID and KMS URI of the invited user as determined by the procedures of clause 6.2.8.3.9 and a time related parameter as described in 3GPP TS 33.180 [78];
d) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];
e) shall add the MCPTT ID of the originating MCPTT user to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
f) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user's signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78] and;
g) shall store the MIKEY-SAKKE I_MESSAGE for later inclusion in an SDP body;
7) may store current user location as user location;
8) shall generate and store offer SDP, as defined in clause 11.2.1.1.2;
9) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE with the stored commencement mode;
e) shall set the Call type IE with the stored current call type associated with the call type control state machine;
f) shall set the SDP offer IE with the stored offer SDP; and
g) may set the User location IE with the stored user location if the stored current call type associated with the call type control state machine is "EMERGENCY PRIVATE CALL".
10) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
11) shall initialize the counter CFP1 (private call request retransmission) with the value set to 1;
12) shall start timer TFP1 (private call request retransmission);
13) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
14) shall enter the "P2: waiting for call response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.2 Private call setup request retransmission
|
When in the "P2: waiting for call response" state, upon expiry of timer TFP1 (private call request retransmission) and the value of the counter CFP1 (private call request retransmission) is less than the upper limit, the MCPTT client:
1) may update the stored user location with current user location;
2) shall increment the value of counter CFP1 (private call request retransmission) by 1;
3) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE with the stored commencement mode;
e) shall set the Call type IE with the stored current call type associated with the call type control state machine;
f) shall set the SDP offer IE with the stored offer SDP; and
g) may set the User location IE with stored user location if the stored current call type is "EMERGENCY PRIVATE CALL" associated with the call type control state machine.
4) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
5) shall start timer TFP1 (private call request retransmission); and
6) shall remain in the "P2: waiting for call response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.3 Ringing notification to the user
|
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL RINGING message, the MCPTT client:
1) shall remain in the "P2: waiting for call response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.4 No response to private call setup request with automatic commencement mode
|
In the "P2: waiting for call response" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit and the stored commencement mode is "AUTOMATIC COMMENCEMENT MODE", the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.5 No response to private call setup request with manual commencement mode
|
When in the "P2: waiting for call response" state when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit and the stored commencement mode is "MANUAL COMMENCEMENT MODE", the MCPTT client:
1) shall start timer TFP9 (waiting for call response message); and
2) shall remain in the "P2: waiting for call response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.6 No response to private call setup request after waiting for user acknowledgement
|
When in the "P2: waiting for call response" state, upon expiry of timer TFP9 (waiting for call response message), the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.7 Private call setup request rejected
|
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as the stored call identifier, the MCPTT client:
1) shall stop timer TFP1 (private call request retransmission), if running;
2) shall stop timer TFP9 (waiting for call response message), if running;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.8 Private call setup request accepted
|
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall store the SDP answer IE received in the PRIVATE CALL ACCEPT message as answer SDP;
2) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
3) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
4) shall stop timer TFP1 (private call request retransmission), if running;
5) shall stop timer TFP9 (waiting for call response message), if running;
6) shall establish a media session based on the SDP body of the stored answer SDP;
7) shall start floor control as originating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
8) shall start timer TFP5 (max duration); and
9) shall enter the "P4: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.2.9 User cancels the private call setup request
|
When in the "P2: waiting for call response" state, upon an indication from MCPTT User to cancel the private call request, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP1 (private call request retransmission);
4) shall stop timer TFP9 (waiting for call response message);
5) shall start timer TFP3 (private call release retransmission);
6) shall initialize the counter CFP3 with value set to 1; and
7) shall enter the "P3: waiting for release response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3 Private call setup in automatic commencement mode
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3.1 Unable to establish media
|
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Call identifier IE different than stored call identifier and media session declared in SDP body of PRIVATE CALL SETUP REQUEST message cannot be established, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall store the MCPTT user ID of the caller IE in the received PRIVATE CALL SETUP message as caller ID;
3) shall store own MCPTT user ID as callee ID;
4) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
a) shall set the Call identifier IE to the cached call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID; and
d) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the Reason IE as "MEDIA FAILURE".
5) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
6) shall start timer TFP7 (waiting for any message with same call identifier); and
7) shall enter the "P1: ignoring same call id" state if current state is the "P0: start-stop" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3.2 Responding to private call setup request when not participating in the ongoing call
|
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Commencement mode IE set to "AUTOMATIC COMMENCEMENT MODE" and Call identifier IE different than stored call identifier and media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall create the call type control state machine as described in clause 11.2.3.2;
3) shall store the MCPTT user ID of the caller IE in the received PRIVATE CALL SETUP REQUEST message as caller ID;
4) shall store own MCPTT user ID as callee ID;
5) if the SDP offer contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:
a) shall extract the MCPTT ID of the originating MCPTT user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
b) shall convert the MCPTT ID to a UID as described in 3GPP TS 33.180 [78];
c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if the validation of the signature failed, shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
i) shall set the call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID;
iv) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "E2E SECURITY CONTEXT FAILURE";
v) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall release call type control state machine; and
vii) shall remain in the current state;
e) if the validation of the signature was successful:
i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78];
ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
iii) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
iv) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier; and
B) shall set the MCPTT user ID of the caller IE with stored caller ID.
C) shall set the MCPTT user ID of the callee IE with stored callee ID; and
D) shall set the SDP answer IE with the stored answer SDP;
v) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall establish a media session based on the SDP body of the stored answer SDP;
vii) shall initialize the counter CFP4 with value set to 1;
viii) shall start timer TFP4 (private call accept retransmission);
ix) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
x) shall enter the "P5: pending" state; and
NOTE: With the PCK successfully shared between the originating MCPTT client and the terminating MCPTT client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.
6) if the SDP offer does not contain an "a=key-mgmt" attribute, the MCPTT client:
a) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with stored caller ID.
iii) shall set the MCPTT user ID of the callee IE with stored callee ID; and
iv) shall set the SDP answer IE with the stored answer SDP;
c) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
d) shall establish a media session based on the SDP body of the stored answer SDP;
e) shall initialize the counter CFP4 with value set to 1;
f) shall start timer TFP4 (private call accept retransmission);
g) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
h) shall enter the "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3.3 Private call accept retransmission
|
When in the "P5: pending" state, upon expiry of timer TFP4 (private call accept retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the SDP answer IE with the stored answer SDP;
2) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the counter CFP4 (private call accept retransmission) by 1;
4) shall start timer TFP4 (private call accept retransmission); and
5) shall remain in the "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3.4 Establishing the call
|
When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCPTT client:
1) shall stop timer TFP4(private call accept retransmission);
2) shall start floor control as terminating MCPTT client as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall start timer TFP5 (max duration); and
4) shall enter the "P4: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.3.5 Call failure
|
In the "P5: pending" state, when timer TFP4 (private call accept retransmission) expires and the value of the counter CFP4 (private call accept retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4 Private call setup in manual commencement mode
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.1 Incoming private call
|
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Commencement mode IE set to "MANUAL COMMENCEMENT MODE" and Call identifier IE different from stored call identifier, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall create the call type control state machine as described in clause 11.2.3.2;
3) shall store the MCPTT user ID of the caller IE as received in the PRIVATE CALL SETUP REQUEST as caller ID;
4) shall store own MCPTT user ID as callee ID;
5) shall generate a PRIVATE CALL RINGING message as specified in clause 15.1.6;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
6) shall send PRIVATE CALL RINGING message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
7) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier);
8) shall start timer TFP2 (waiting for user to respond); and
9) shall enter the "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.2 No response from the user
|
When in the "P5: pending" state, upon expiry of timer TFP2 (waiting for user to respond), the MCPTT client:
1) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the Reason IE as "FAILED".
2) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.3 User accepts the private call setup request
|
When in the "P5: pending" state, upon an indication from MCPTT User to accept the incoming private call, the MCPTT client:
1) if the SDP offer contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:
a) shall extract the MCPTT ID of the originating MCPTT user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
b) shall convert the MCPTT ID to a UID as described in 3GPP TS 33.180 [78];
c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if the validation of the signature failed, shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
i) shall set the call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID;
iv) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "E2E SECURITY CONTEXT FAILURE";
v) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall stop timer TFP2 (waiting for user to respond);
vii) if timer TFP 7 is not running, shall start timer TFP7 (waiting for any message with same call identifier);
viii) shall release the call type control state machine; and
ix) shall enter the "P1: ignoring same call id" state;
e) if the validation of the signature was successful:
i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78];
ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
iii) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
iv) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier;
B) shall set the MCPTT user ID of the caller IE with the stored caller ID;
C) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
D) shall set the SDP answer IE with the stored answer SDP;
v) shall send the PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall establish a media session based on the SDP body of the private call;
vii) shall stop timer TFP2 (waiting for user to respond);
viii) shall initialize the counter CFP4 with value set to 1;
ix) shall start timer TFP4 (private call accept retransmission); and
x) shall remain in the "P5: pending" state; and
NOTE: With the PCK successfully shared between the originating MCPTT client and the terminating MCPTT client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.
2) if the SDP offer does not contain an "a=key-mgmt" attribute, the MCPTT client:
a) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
iv) shall set the SDP answer IE with the stored answer SDP;
c) shall send the PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
d) shall establish a media session based on the SDP body of the private call;
e) shall stop timer TFP2 (waiting for user to respond);
f) shall initialize the counter CFP4 with value set to 1;
g) shall start timer TFP4 (private call accept retransmission); and
h) shall remain in the "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.4 Private call accept retransmission
|
When in the "P5: pending" state, upon expiry of timer TFP4 (private call accept retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the SDP answer IE with the stored answer SDP;
2) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the (counter CFP4 private call accept retransmission) by 1;
4) shall start timer TFP4 (private call accept retransmission); and
5) shall remain in the "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.5 Establishing the call
|
When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCPTT client:
1) shall stop timer TFP4 (private call accept retransmission);
2) shall start floor control as terminating MCPTT client as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall start timer TFP5 (max duration); and
4) shall enter the "P4: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.6 Call failure
|
In the "P5: pending" state, when timer TFP4 (private call accept retransmission) expires and the value of the counter CFP4 (private call accept retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.7 User rejects the private call setup request
|
When in the "P5: pending" state, upon an indication from MCPTT User to reject the incoming private call, the MCPTT client:
1) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID; and
d) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the Reason IE as "REJECT";
2) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP2 (waiting for user to respond);
4) shall start timer TFP7 (waiting for any message with same call identifier);
5) shall release the call type control state machine; and
6) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.4.8 Caller cancels the private call setup request before call establishment
|
When in the "P5: pending" state or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL RELEASE message, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE ACK message as specified in clause 15.1.10. In the PRIVATE CALL RELEASE ACK message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and.
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) if in the "P5: pending" state and timer TFP7 (waiting for any message with same call identifier) is not running, shall start timer TFP7 (waiting for any message with same call identifier);
4) shall stop timer TFP2 (waiting for user to respond), if running;
5) shall stop timer TFP4 (private call accept retransmission) if running;
6) shall release the call type control state machine, if the current state is "P5: pending" state; and
7) shall enter the "P1: ignoring same call id" state, if the current state is "P5: pending" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5 Private call release
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.1 Releasing a private call
|
When in the "P4: part of ongoing call" state, upon an indication from MCPTT User to release a private call, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9. In the PRIVATE CALL RELEASE message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with stored callee ID.
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP5 (max duration);
4) shall initialize the counter CFP3 (private call release retransmission) with the value set to 1;
5) shall start timer TFP3 (private call release retransmission); and
6) shall enter the "P3: waiting for release response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.2 Private call release retransmission
|
When in the "P3: waiting for release response" state, upon expiry of timer TFP3 (private call release retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9. In the PRIVATE CALL RELEASE message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of timer CFP3 by 1;
4) shall start timer TFP3 (private call release retransmission); and
5) shall remain in the "P3: waiting for release response" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.3 No response to private call release
|
In the "P3: waiting for release response" state, when timer TFP3 (private call request retransmission) expires and the value of the counter CFP3 (private call release retransmission) is equal to the upper limit, the MCPTT client:
1) shall terminate the media session;
2) shall start timer TFP7 (waiting for any message with same call identifier);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.4 Acknowledging private call release after call establishment
|
When in the "P4: part of ongoing call" state, upon receiving a PRIVATE CALL RELEASE message, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE ACK message as specified in clause 15.1.10;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall terminate the media session for private call;
4) shall stop timer TFP5 (max duration);
5) shall start timer TFP7 (waiting for any message with same call identifier);
6) shall release the call type control state machine; and
7) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.5 Private call release acknowledged
|
When in the "P3: waiting for release response" state, upon receiving a PRIVATE CALL RELEASE ACK to PRIVATE CALL RELEASE message, the MCPTT client:
1) shall stop timer TFP3 (private call release retransmission), if running;
2) shall terminate the media session;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.6 Max duration reached
|
When in the "P4: part of ongoing call" state, upon expiry of timer TFP5 (max duration), the MCPTT client:
1) shall terminate the media session;
2) shall start timer TFP7 (waiting for any message with same call identifier);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.7 Stop ignoring same call id
|
When in the "P1: ignoring same call id" state, upon expiry of timer TFP7 (waiting for any message with same call identifier) the MCPTT client:
1) shall clear the stored call identifier; and
2) shall enter the "P0: start-stop" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.8 No response to emergency private call setup request
|
In the "P4: part of ongoing call" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall stop timer TFP5 (max duration);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.5.9 No response to emergency private call cancel
|
In the "P4: part of ongoing call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall stop timer TFP5 (max duration);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.6 Error handling
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.6.1 Unexpected MONP message received
|
Upon receiving a MONP message in a state where there is no handling specified for the MONP message, the MCPTT client shall discard the MONP message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.6.2 Unexpected indication from MCPTT user
|
Upon receiving an indication from the MCPTT user in a state where there is no handling specified for the indication, the MCPTT client shall ignore the indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.2.4.6.3 Unexpected expiration of a timer
|
Upon expiration of a timer in a state where there is no handling specified for expiration of the timer, the MCPTT client shall ignore the expiration of the timer.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3 Call type control
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.1 General
|
This state machine exists in parallel with the call control state machine for off-network private call as specified in clause 11.2.2.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.2 Call type control state machine
|
The Figure 11.2.3.2-1 gives an overview of the states and transitions of the state machine.
Figure 11.2.3.2-1: Call type control state machine
When sending the message, MCPTT client indicates the stored current ProSe per-packet priority associated with the call type control state machine to the lower layers.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.3 Call type control states
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.3.1 Q0: waiting for the call to be established
|
This state is the start state of this state machine.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.3.2 Q1: in-progress private call
|
This state exists for UE, when the UE is part of an in-progress private call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.3.3 Q2: in-progress emergency private call
|
This state exists for UE, when the UE is part of an in-progress emergency private call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4 Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.1 General
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.2 Outgoing call initiated
|
When in "Q0: waiting for the call to be established" state, upon an indication from the MCPTT user to initiate a call, the MCPTT client:
1) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "true" and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true":
a) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45]; or
2) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "false":
a) if the user initiates an MCPTT emergency private call and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true":
i) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45]; or
b) if the user initiates an MCPTT private call:
i) shall set the stored current call type to "PRIVATE CALL"; and
ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.3 Received incoming call
|
When in "Q0: waiting for the call to be established" state, upon receipt of a PRIVATE CALL SETUP REQUEST message by an idle MCPTT client, the MCPTT client:
1) if the Call type IE of the received PRIVATE CALL SETUP REQUEST message is set to "EMERGENCY PRIVATE CALL":
a) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
2) if the Call type IE of the received PRIVATE CALL SETUP REQUEST message is set to "PRIVATE CALL":
a) shall set the stored current call type to "PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.4 Establishing the private call
|
When in "Q0: waiting for the call to be established" state, upon receiving PRIVATE CALL ACCEPT message or PRIVATE CALL ACCEPT ACK message, the MCPTT client:
1) if the stored current call type is set to "EMERGENCY PRIVATE CALL":
a) shall start TFP8 (implicit downgrade) timer; and
b) shall enter "Q2: in-progress emergency private call" state; or
2) if the stored current call type is set to "PRIVATE CALL":
a) shall enter "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5 Upgrade call
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.1 User upgrades private call to emergency private call
|
When in the "Q1: in-progress private call" state, upon an indication from MCPTT User to upgrade the call to emergency and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", the MCPTT client:
1) shall generate and store emergency offer SDP as defined in clause 11.2.1.1.2;
2) shall update stored caller ID as own MCPTT user ID;
3) shall update stored callee ID as MCPTT user ID of the other user;
4) shall store current user location as user location;
5) shall set the stored current call type to "EMERGENCY PRIVATE CALL";
6) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE as "AUTOMATIC COMMENCEMENT MODE";
e) shall set the Call type IE to the stored current call type;
f) shall set the SDP offer IE with emergency offer SDP; and
g) may set the User location IE with user location.
7) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
8) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
9) shall initialize the counter CFP1 (private call request retransmission) with value set to 1;
10) shall start timer TFP1 (private call request retransmission);
11) shall stop timer TFP6 (emergency private call cancel retransmission), if running; and
12) shall enter the "Q2: in-progress emergency private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.2 Emergency private call setup request retransmission
|
When in the "Q2: in-progress emergency private call" state, upon expiry of timer TFP1 (private call request retransmission) and the value of CFP1 is less than the limit for CFP1, the MCPTT client:
1) may update the stored user location with current user location;
2) shall increment the value of the counter CFP1 (private call request retransmission) by 1;
3) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID;
d) shall set the Commencement mode IE as "AUTOMATIC COMMENCEMENT MODE";
e) shall set the Call type IE to the stored current call type;
f) shall set the SDP offer IE with the stored emergency offer SDP; and
g) may set the User location IE with stored user location;
4) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
5) shall start timer TFP1 (private call request retransmission); and
6) shall remain in the "Q2: in-progress emergency private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.3 Emergency private call setup request accepted
|
When in the "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall store the SDP answer IE received in the PRIVATE CALL ACCEPT message as emergency answer SDP;
2) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
3) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
4) shall stop timer TFP1 (private call request retransmission), if running;
5) if timer TFP8 is not running, shall start TFP8 (implicit downgrade) timer;
6) shall establish a media session based on the SDP body of the stored emergency answer SDP, if not already established based on the received SDP body of the stored emergency answer SDP; and
7) shall remain in the current state.
NOTE: PRIVATE CALL ACCEPT ACK message is retransmitted, as described in this clause, every time a PRIVATE CALL ACCEPT message is received.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.4 Emergency private call setup request rejected
|
When in the "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as stored call identifier, the MCPTT client:
1) shall stop timer TFP1 (private call request retransmission), if running;
2) shall set the ProSe per-packet priority to the value corresponding to the MCPTT off-network private call as described in 3GPP TS 24.483 [45];
3) shall set the stored current call type to "PRIVATE CALL"; and
4) shall enter the "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.5 No response to emergency private call setup request
|
In the "Q2: in-progress emergency private call" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper, the MCPTT client:
1) shall release the stored current call type;
2) shall release the stored Prose per-packet priority; and
3) shall enter "Q0: waiting for the call to be established".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.5.6 Responding to emergency private call setup request when participating in the ongoing call
|
When in the "Q1: in-progress private call" state or "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL SETUP REQUEST message with the Call identifier IE same as the stored call identifier of the call, the Call type IE set as "EMERGENCY PRIVATE CALL", the MCPTT client:
1) if the media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established:
a) shall generate and store emergency answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall update the stored caller ID with the MCPTT user ID of the caller IE as received in the PRIVATE CALL SETUP REQUEST message;
c) shall update the stored callee ID with own MCPTT user ID;
d) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the callee IE with stored callee ID;
iii) shall set the MCPTT user ID of the caller IE with stored caller ID; and
iv) shall set the SDP answer IE with the stored emergency answer SDP;
e) if in the "Q1: in-progress private call" state, shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
f) if in the "Q1: in-progress private call" state, shall stop timer TFP6 (emergency private call cancel retransmission), if running;
g) if in the "Q1: in-progress private call" state, shall start timer TFP8 (implicit downgrade);
h) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
i) if in the "Q1: in-progress private call" state, shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
j) if in the "Q1: in-progress private call" state, shall enter the "Q2: in-progress emergency private call" state; otherwise remain in the "Q2: in-progress emergency private call" state;
2) if the media session declared in SDP body of PRIVATE CALL SETUP REQUEST message cannot be established:
a) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8;
b) shall set the call identifier IE with the call identifier in the received message;
c) shall set the MCPTT user ID of the caller IE with the caller ID in the received message;
d) shall set the MCPTT user ID of the callee IE with the callee ID in the received message;
e) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "MEDIA FAILURE";
f) shall send a PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1; and
g) shall remain in the current state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6 Downgrade call
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6.1 User cancels the emergency private call
|
When in the "Q2: in-progress emergency private call" state, upon an indication from:
1) the caller of the emergency private call; or
2) the recipient of the emergency private call with the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/CancelPriority" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] set to "true",
to cancel the emergency private call, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in clause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller; and
c) shall set the MCPTT user ID of the callee IE with the stored callee.
2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop TFP1 (private call request retransmission), if running;
4) shall stop TFP8 (implicit downgrade) timer;
5) shall initialize the counter CFP6 (emergency private call cancel retransmission) with the value set to 1;
6) shall start timer TFP6 (emergency private call cancel retransmission);
7) shall set the stored current call type to "PRIVATE CALL"; and
8) shall enter the "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6.2 Emergency private call cancel retransmission
|
When in the "Q1: in-progress private call" state, upon expiry of timer TFP6 (emergency private call cancel retransmission) and the value of the counter CFP6 (emergency private call cancel retransmission) is less than upper limit, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in clause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with store callee ID.
2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the timer CFP6 (emergency private call cancel retransmission) by 1;
4) shall start timer TFP6 (emergency private call cancel retransmission); and
5) shall remain in the "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6.3 Emergency private call cancel accepted
|
When in the "Q1: in-progress private call" state, upon receiving a PRIVATE CALL EMERGENCY CANCEL ACK message response to PRIVATE CALL EMERGENCY CANCEL message with the same "call identifier", the MCPTT client:
1) shall stop timer TFP6 (emergency private call cancel retransmission), if running;
2) shall establish a media session based on the SDP body of the stored answer SDP;
3) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]; and
4) shall remain in the "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6.4 No response to emergency private call cancel
|
In the "Q1: in-progress private call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:
1) shall release the stored current call type;
2) shall release the stored Prose per-packet priority; and
3) shall enter "Q0: waiting for the call to be established".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.6.5 Responding to emergency private call cancel
|
When in the "Q1: in-progress private call" state or "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL EMERGENCY CANCEL message with the same "call identifier" IE, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL ACK as specified in clause 15.1.13:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the callee IE with own MCPTT user ID; and
c) shall set the MCPTT user ID of the caller IE with MCPTT user ID of the caller IE in received message;
2) shall send PRIVATE CALL EMERGENCY CANCEL ACK message according to rules and procedures as specified in clause 11.2.1.1.1;
3) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP8 (implicit downgrade);
4) shall establish a media session based on the SDP body of the stored answer SDP;
5) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]; and
6) shall enter the "Q1: in-progress private call" state and set the stored current call type to "PRIVATE CALL", if current state is the "Q2: in-progress emergency private call" state.
11.2.3.4.6A Implicit downgrade
When in the "Q2: in-progress emergency private call" state, upon expiry of TFP8 (implicit downgrade) timer, the MCPTT client:
1) shall establish a media session based on the SDP body of the stored answer SDP;
2) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45];
3) shall set the stored current call type to "PRIVATE CALL"; and
4) shall enter the "Q1: in-progress private call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.7 Call Release
|
When in state "Q1: in-progress private call" or "Q2: in-progress emergency private call", upon receiving an indication from MCPTT user to release the call or upon receiving PRIVATE CALL RELEASE message, the MCPTT client:
1) shall release the stored current call type;
2) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP1 (private call request retransmission), if running;
3) if in the "Q1: in-progress private call" state, shall stop timer TFP6 (emergency private call cancel retransmission), if running;
4) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP8 (implicit downgrade);
5) shall release the stored Prose per-packet priority; and
6) shall enter "Q0: waiting for the call to be established".
11.2.3.4.7A Private call setup request accepted
When in the "Q1: in-progress private call" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
2) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1; and
3) shall remain in the current state.
NOTE: PRIVATE CALL ACCEPT ACK message is retransmitted, as described in this clause, every time a PRIVATE CALL ACCEPT message is received.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.8 Error handling
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.8.1 Unexpected MONP message received
|
Upon receiving a MONP message in a state where there is no handling specified for the MONP message, the MCPTT client shall discard the MONP message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.8.2 Unexpected indication from MCPTT user
|
Upon receiving an indication from the MCPTT user in a state where there is no handling specified for the indication, the MCPTT client shall ignore the indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
11.2.3.4.8.3 Unexpected expiration of a timer
|
Upon expiration of a timer in a state where there is no handling specified for expiration of the timer, the MCPTT client shall ignore the expiration of the timer.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12 Emergency alert
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.0 General
|
This clause describes the emergency alert procedures for on-network and off-network.
For on-network emergency alert, the procedures for originating and terminating MCPTT clients, participating MCPTT functions and controlling MCPTT function are specified in clause 12.1. MCPTT emergency call procedures that have emergency alerts as an optional capability shall be performed as defined in clause 10.1 for on-network group call and defined in clause 11.1 for on-network private call.
For off-network emergency alert, the procedures for each functional entity is specified in clause 12.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1 On-network emergency alert
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1 Client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.1 Emergency alert origination
|
Upon receiving a request from the MCPTT user to send an MCPTT emergency alert to the indicated MCPTT group shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
1) should indicate to the MCPTT user that alerts are not allowed on the indicated group; and
2) shall skip the remainder of this procedure.
If this is an authorised request for an MCPTT emergency alert as determined by clause 6.2.8.1.6, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to:
i) if the <EmergencyAlert> element of the MCPTT user profile exists, then:
A) if the <entry-info> attribute of the <entry> element of the <EmergencyAlert> element is set to the value 'DedicatedGroup', the value in the <uri-entry> element of the <entry> element of the <EmergencyAlert> element; and
B) if the <entry-info> attribute of the <entry> element of the <EmergencyAlert> element is set to the value 'UseCurrentlySelectedGroup' and there is no currently selected group, the value in the <uri-entry> element of the <entry> element of the <EmergencyAlert> element; and
ii) if the <EmergencyAlert> element of the MCPTT user profile does not exist, the group identity selected by the MCPTT user;
b) the <alert-ind> element set to a value of "true";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
NOTE 2: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
5) shall include in the SIP MESSAGE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
6) shall set the MCPTT emergency state if not already set;
7) shall set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending";
8) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
9) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated".
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT emergency alert state to "MEA 1: no-alert".
NOTE 3: The MCPTT emergency state is left set in this case as the MCPTT user presumably is in the best position to determine whether or not they are in a life-threatening condition. The assumption is that the MCPTT user can clear the MCPTT emergency state manually if need be.
NOTE 4: Based on implementation the MCPTT client can subsequently automatically originate an MCPTT emergency group call as specified in clause 10.1.1.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.2 Emergency alert cancellation
|
Upon receiving a request from the MCPTT user to send an MCPTT emergency alert cancellation to the indicated MCPTT group and this is an authorised request for an MCPTT emergency alert cancellation as determined by clause 6.2.8.1.6, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity;
b) the <alert-ind> element set to a value of "false";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
NOTE 1A: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user is cancelling an MCPTT emergency alert originated by another MCPTT user, include the <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT emergency alert;
5) if the MCPTT user has additionally requested the cancellation of the in-progress emergency state of the MCPTT group and this is an authorised request for an in-progress emergency group state cancellation as determined by clause 6.2.8.1.7, shall include an <emergency-ind> element set to a value of "false" in the <mcpttinfo> element containing the <mcptt-Params> element;
6) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
7) if the generated SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind-rcvd> element set to true and an <mcptt-client-id> matching the MCPTT client ID included in the sent SIP MESSAGE request:
1) if the <alert-ind> element is set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall:
a) set the MCPTT emergency alert state to "MEA 1: no-alert"; and
b) clear the MCPTT emergency state if not already cleared;
2) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT emergency alerts but not have the authority to clear them. Hence, the case is covered here.
3) if an <emergency-ind> element is present in the application/vnd.3gpp.mcptt-info+xml MIME body of received SIP MESSAGE request is set to a value of "false" and the sent SIP MESSAGE request contains an <emergency-ind> element set to a value of "false":
a) shall set the MCPTT emergency group call state of the group to "MEGC 1: emergency-gc-capable"; and
b) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency".
NOTE 3: The case where an <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:
1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true", the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 4: In this case, an <emergency-ind> element would either not be present or would be set to true. In either case, no change in state would result. Hence, this case is not specified above.
2) if the received SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request does not contain an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element, the sent SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.3 MCPTT client receives an MCPTT emergency alert or call notification
|
Upon receipt of a "SIP MESSAGE request for emergency notification", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true", may display to the MCPTT user the functional alias of the originating MCPTT user, if provided, and should display to the MCPTT user an indication of the MCPTT emergency alert and associated information, including:
a) the MCPTT group identity contained in <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
b) the originator of the MCPTT emergency alert contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
c) the mission critical organization of the MCPTT emergency alert originator contained in the <mc-org> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE 1: This is the case of the MCPTT client receiving the notification of another MCPTT user's emergency alert.
2) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the MCPTT emergency alert cancellation and associated information, including:
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
ii) the originator of the MCPTT emergency alert contained in:
A) if present, the <originated-by> element of the application/vnd.3gpp.mcptt-info+xml MIME body; or
B) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) if the MCPTT ID contained in the <originated-by> element is the MCPTT ID of the receiving MCPTT user, shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
c) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element is set to a value of "false":
i) shall set the MCPTT emergency group state to "MEG 1: no-emergency"; and
ii) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
NOTE 2: This is the case of the MCPTT client receiving the notification of the cancellation by a third party of an MCPTT emergency alert. This can be the MCPTT emergency alert of another MCPTT user or the MCPTT emergency alert of the recipient, as determined by the contents of the <originated-by> element. Optionally, notification of the cancellation of the in-progress emergency state of the MCPTT group can be included.
3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true":
a) should display to the MCPTT user an indication of the additional emergency MCPTT user participating in the MCPTT emergency group call including the following if not already displayed as part of step 1):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT emergency group state to "MEG 2: in-progress" if not already set to that value;
NOTE 3: This is the case of the MCPTT client receiving notification of an additional MCPTT user in an MCPTT emergency state (i.e., not the MCPTT user that originally triggered the in-progress emergency state of the group) joining the in-progress emergency group call or in the case of MCPTT client not participating in an in-progress emergency group call but affiliated to group to receive notification of an MCPTT users having MCPTT outstanding emergency call. An emergency alert indication, if included, is handled in step 1).
4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress emergency state of the MCPTT group call including the following if not already displayed as part of step 2):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT emergency group state to "MEG 1: no-emergency"; and
c) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
NOTE 4: This is the case of the MCPTT client receiving the notification of the cancellation of the in-progress emergency state of the MCPTT group. In this case, the receiving MCPTT client is affiliated with the MCPTT group but not participating or participating in the session. An emergency alert cancellation, if included, is handled in step 2).
5) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true":
a) should display to the MCPTT user an indication of the MCPTT user participating in the MCPTT imminent peril group call including the following if not already displayed as part of step 1):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall set the MCPTT imminent peril group state to "MIG 2: in-progress" if not already set to that value;
NOTE 5: This is the case of the MCPTT client receiving notification of an additional MCPTT user initiating an imminent peril group call when there is already an in-progress imminent peril state in effect on the group.
6) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress imminent peril state of the MCPTT group including the following if not already displayed as part of step 2):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
c) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
NOTE 6: This is the case of the MCPTT client receiving notification of the cancellation of the in-progress imminent peril state of the group.
7) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
8) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.4 MCPTT client receives notification of entry into or exit from a group geographic area
|
Upon receipt of a "SIP MESSAGE request for notification of entry into or exit from a group geographic area", the MCPTT client;
1) shall send a SIP 200 (OK) to the participating MCPTT function that sent the SIP MESSAGE request; and
2) if the <group-geo-area-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is:
a) set to "true":
i) may display to the MCPTT user an indication that a group geographic area has been entered; and
ii) shall execute the procedure in clause 9.2.1.2 to affiliate to the group indicated by the participating MCPTT function; or
b) set to "false":
i) may display to the MCPTT user an indication that a group geographic area has been exited; and
ii) shall execute the procedure in clause 9.2.1.2 to de-affiliate from the group indicated by the participating MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.5 MCPTT group in-progress emergency group state cancel
|
Upon receiving a request from an MCPTT user to cancel the in-progress emergency condition on a prearranged MCPTT group on which there is no call ongoing, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress emergency group state of the MCPTT group as determined by the procedures of clause 6.2.8.1.7, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress emergency group state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity; and
b) the <emergency-ind> element set to a value of "false";
6) if the MCPTT user has additionally requested the cancellation of an MCPTT emergency alert originated by MCPTT user, shall include an <alert-ind> element set to a value of "false" in the <mcpttinfo> element containing the <mcptt-Params> element;
7) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
8) if the generated SIP MESSAGE request contain an <alert -ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
9) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind-rcvd> element set to a value of "true" and an <mcptt-client-id> matching the MCPTT client ID included in the sent SIP MESSAGE request:
1) if an <emergency-ind> element is present in the application/vnd.3gpp.mcptt-info+xml MIME body of received SIP MESSAGE request and is set to a value of "false":
a) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency".
NOTE 3: The case where an <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.
2) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT emergency alerts but not have the authority to clear them. Hence, the case is covered here.
3) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "false" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body, shall:
a) set the MCPTT emergency alert state to "MEA 1: no-alert"; and
b) clear the MCPTT emergency state if not already cleared;
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:
1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 4: In this case, <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.1.6 MCPTT client receives notification of entry into or exit from an emergency alert area
|
Upon receipt of a "SIP MESSAGE request for notification of entry into or exit from an emergency alert area", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-alert-area-ind> element value:
a) set to "true":
i) may display to the MCPTT user an indication that MCPTT client has entered a pre-defined emergency alert area; and
ii) if the MCPTT user is not in emergency state, shall initiate the emergency alert origination procedure as specified in clause 12.1.1.1; or
b) set to "false":
i) may display to the MCPTT user an indication that MCPTT client has exited a pre-defined emergency alert area;
NOTE: In this case, the MCPTT emergency state remains set, as the MCPTT user is in the best position to determine whether or not they are in a life-threatening condition. The MCPTT user can clear the MCPTT emergency state manually, if needed.
2) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
3) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.2 Participating MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.2.1 Receipt of a SIP MESSAGE request for emergency notification from the served MCPTT client
|
Upon receipt of a "SIP MESSAGE request for emergency notification for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can, according to local policy, choose to accept the request.
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the MCPTT user is not affiliated with the MCPTT group as determined by clause 9.2.2.2.11, shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation;
4) if the actions for implicit affiliation specified in step 3) above were performed but not successful in affiliating the MCPTT user due to the MCPTT user already having N2 simultaneous affiliations(specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile of the served MCPTT ID), shall reject the "SIP MESSAGE request for emergency notification for originating participating MCPTT function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps.
NOTE 3: N2 is the total number of MCPTT groups that an MCPTT user can be affiliated to simultaneously as specified in 3GPP TS 23.379 [3].
NOTE 4: As this is a request for MCPTT emergency services, the participating MCPTT function can choose to accept the request.
5) shall determine the public service identity of the controlling MCPTT function associated with the group identity in the received SIP MESSAGE request;
NOTE 5: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 6: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 7: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 8: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 9: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5) above;
8) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8a) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID. If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise it shall not include a <functional-alias-URI> element;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3 shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP MESSAGE request;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
12) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 10):
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
2) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13; and
3) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the sent SIP MESSAGE request and if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in the present clause, the participating MCPTT function shall perform the procedures of clause 9.2.2.2.14.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.2.2 Receipt of a SIP MESSAGE request for emergency notification for terminating MCPTT client
|
In the procedures in this clause:
1) emergency indication in an incoming SIP MESSAGE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) alert indication in an incoming SIP MESSAGE request refers to the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP MESSAGE request for emergency notification for terminating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.2.3 Receipt of a SIP MESSAGE request indicating successful delivery of emergency notification
|
Upon receipt of a SIP MESSAGE request routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind-rcvd> or <emergency-ind-rcvd> element present, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCPTT ID of the MCPTT user that was in the Request-URI of the incoming SIP MESSAGE request;
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; and
d) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.3 Controlling MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.3.1 Handling of a SIP MESSAGE request for emergency notification
|
Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE: If the SIP MESSAGE request contains an alert indication set to a value of "true", the controlling MCPTT function can, according to local policy, choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "168 alert is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false", the <emergency-ind> element present or not and call is ongoing on associated group on which outstanding alert exists, shall perform the procedures specified in clause 12.1.3.2 and skip the rest of the steps;
3a) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false", the <alert-ind> element present or not and no call is ongoing on the group on which in-progress emergency state cancelation request is recieved, shall perform the procedures specified in clause 12.1.3.3 and skip the rest of the steps;
4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true":
a) if the received SIP MESSAGE request is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1 shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "false"; and
ii) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps; and
b) if the received SIP MESSAGE request is an authorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1:
i) if the sending MCPTT user identified by the <mcptt-calling-user-id> element included in the application/vnd.3gpp.mcptt-info+xml MIME body is not affiliated with the MCPTT group identified by the <mcptt-request-uri> element of the MIME body as determined by the procedures of clause 6.3.6:
I) shall check if the MCPTT user is eligible to be implicitly affiliated with the MCPTT group as determined by clause 9.2.2.3.6;
II) if the MCPTT user is determined not to be eligible to be implicitly affiliated to the MCPTT group shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; or
III) if the procedures of clause 9.2.2.3.6 determined the MCPTT user to be eligible to be implicitly affiliated to the MCPTT group shall, perform the implicit affiliation as specified in clause 9.2.2.3.7;
ii) for each of the other affiliated members of the group:
A) generate an outgoing SIP MESSAGE request notification of the MCPTT user's emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.12;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request; and
C) send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4];
iii) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
A) shall cache the information that the MCPTT user has initiated an MCPTT emergency alert;
iv) shall send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4].
v) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an emergency alert, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body:
A) the <alert-ind> element set to a value of "true";
B) the <alert-ind-rcvd> element set to a value of true; and
C) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
vi) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.3.2 Handling of a SIP MESSAGE request for emergency alert cancellation
|
Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false", the controlling MCPTT function:
1) if the received SIP MESSAGE request is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.1:
a) and if the received SIP MESSAGE request does not contain an <emergency-ind> element set to a value of "false" or is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true";
ii) if the received SIP MESSAGE request contains an <emergency-ind> element of the <mcpttinfo> element set to a value of "false" and if the in-progress emergency state of the group is set to a value of "true" and this is an unauthorised request for an MCPTT emergency call cancellation as determined in step i) above, shall include an <emergency-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP 403 (Forbidden) response; and
iii) shall send the SIP 403 (Forbidden) response according to rules and procedures of 3GPP TS 24.229 [4] and skip the rest of the steps; and
b) and if the received SIP MESSAGE request contains an <emergency-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the MCPTT group is set to a value of "true":
i) shall set the in-progress emergency state of the group to a value of "false";
ii) shall clear the cache of the MCPTT ID of the MCPTT user that triggered the setting of the in-progress emergency state of the MCPTT group to "true";
iii) shall generate SIP re-INVITE requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
iv) for each of the affiliated but not joined members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request; and
C) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
v) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
vi) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
vii) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation
viii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request:
A) the <alert-ind> element set to a value of "true";
B) the <alert-ind-rcvd> element set to a value of true;
C) the <emergency-ind> element set to a value of "false"; and
D) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
ix) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4]; and
2) if the received SIP MESSAGE request is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3:
a) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding MCPTT emergency alert;
b) if the received SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the sender of the SIP MESSAGE request as having an outstanding MCPTT emergency alert;
c) if the received SIP MESSAGE request does not contain an <emergency-ind> element set to a value of "false" or is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, for each of the affiliated members of the group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency alert as specified in clause 6.3.3.1.11;
ii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
iii) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
iv) shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
v) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
d) if the received SIP MESSAGE request contains an <emergency-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the MCPTT group is set to a value of "true":
i) shall set the in-progress emergency state of the group to a value of "false";
ii) cache the information that the MCPTT user has cancelled the outstanding in-progress emergency state of the group;
iii) shall generate SIP re-INVITES requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
iv) for each of the affiliated but not joined members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
B) include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
C) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
D) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "false"; and
E) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
e) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
f) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4].
g) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation;
h) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body, the <alert-ind> element set to a value of "false" and the <alert-ind-rcvd> set to "true";
i) shall populate the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
j) if the received SIP MESSAGE request contains an <emergency-ind> element of the <mcpttinfo> element set to a value of "false":
i) if this is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
ii) otherwise, if this is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, and the in-progress emergency state of the group is set to a value of "true", shall include an <emergency-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
k) shall send the SIP MESSAGE request according to according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.3.3 Handling of a SIP MESSAGE request for in-progress emergency group state cancellation
|
Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and no call is ongoing on the group on which in-progress emergency cancellation request is made, the controlling MCPTT function:
1) if the received SIP MESSAGE request is an unauthorised request for an MCPTT in-progress emergency group state cancellation as specified in clause 6.3.3.1.13.4:
a) and if the received SIP MESSAGE request does not contain an <alert-ind> element or is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <emergency-ind> element set to a value of "true";
ii) if the received SIP MESSAGE request contains an <alert-ind> element of the <mcpttinfo> element set to a value of "false" and this is an unauthorised request for an MCPTT emergency alert cancellation as determined in step a) above and the emergency state of the MCPTT user has outstanding emergency state, shall include an <alert-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP 403 (Forbidden) response; and
iii) shall send the SIP 403 (Forbidden) response according to rules and procedures of 3GPP TS 24.229 [4] and skip the rest of the steps; and
b) and if the received SIP MESSAGE request contains an <alert-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and the MCPTT user has outstanding emergency state:
i) shall clear the cache of the MCPTT ID of the MCPTT user that has the outstanding emergency alert state;
ii) for each of the affiliated members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency alert as specified in clause 6.3.3.1.11;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request; and
C) shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
D) send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4];
iii) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
iv) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
v) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation
vi) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request:
A) the <emergency-ind> element set to a value of "true";
B) the <emergency-ind-rcvd> element set to a value of "true";
C) the <alert-ind> element set to a value of "false"; and
D) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
vii) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4]; and
2) if the received SIP MESSAGE request is an authorised request for an MCPTT in-progress emergency group state cancellation as specified in clause 6.3.3.1.13.4:
a) shall set the in-progress emergency state of the group to a value of "false";
b) cache the information that the MCPTT user has cancelled the outstanding in-progress emergency state of the group and clear the cache of the all MCPTT ID of the MCPTT users that triggered the setting of the in-progress emergency state of the MCPTT group to "true";
c) if the received SIP MESSAGE request contains an <alert-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and the MCPTT user has outstanding emergency state, clear the cache of the MCPTT ID of the sender of the SIP MESSAGE request as having an outstanding MCPTT emergency alert;
d) for each of the affiliated members of the group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's/group emergency state as specified in clause 6.3.3.1.11;
ii) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
iii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
iv) if the received SIP MESSAGE request contains an <alert-ind> element of the <mcpttinfo> element set to a value of "false" and this is an authorised request for an MCPTT emergency alert cancellation as determined in step c) above, shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
v) send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4];
e) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
f) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4].
g) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for in-progress emergency group cancellation;
h) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body, the <emergency-ind> element set to a value of "false" and the <emergency-ind-rcvd> set to "true";
i) shall populate the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
j) if the received SIP MESSAGE request contains an <alert-ind> element of the <mcpttinfo> element set to a value of "false":
i) if this is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
B) otherwise, if this is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, shall include an <alert-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
k) shall send the SIP MESSAGE request according to according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.1.3.4 Late emergency alert initiated by controlling MCPTT function
|
When controlling MCPTT function is notified that an MCPTT client is newly affiliated or comes back from out of coverage, the controlling MCPTT function:
NOTE: How the MCPTT function is informed when an MCPTT client is coming back from out of coverage is out of scope of present document.
1) if there is an outstanding MCPTT emergency alert for the MCPTT group to which the user affiliated, and the call is not ongoing on associated group on which outstanding alert exists, for the MCPTT client:
a) generate an outgoing SIP MESSAGE request notification of the MCPTT user's emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.12;
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the MCPTT ID of the MCPTT user who has initiated an MCPTT emergency alert; and
c) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
12.1A On-network MCPTT adhoc group emergency alert
12.1A.1 Client procedures
12.1A.1.1 Ad hoc group emergency alert origination
Upon receiving a request from the MCPTT user to send an MCPTT adhoc group emergency alert, the MCPTT client shall determine if this is an authorised request for the origination of an MCPTT adhoc group emergency alert as specified in the clause 6.2.8.1.19.
If this is an unauthorised request for an MCPTT adhoc group emergency alert, the MCPTT client:
1) should indicate to the MCPTT user that adhoc group emergency alerts are not allowed; and
2) shall skip the remainder of this procedure.
If this is an authorised request, MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) if the MCPTT client needs to include an identity of adhoc group, the <mcptt-request-uri> element set to the identity of the adhoc group;
NOTE 2: The MCPTT client can optionally include an identity of adhoc group if it learns by any means or generated by the MCPTT client using required parameters.
b) the <anyExt> element with the <adhoc-alert-ind> element set to a value of "true";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 3: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
f) if the MCPTT user has requested to include additional information related to the MCPTT adhoc emergency alter, the <anyExt> element with the <adhoc-additional-information> element set to the user provided value; and
g) a <call-participants-criterias> with one or more criteria as a comma separated list into <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request;
5) shall include in the SIP MESSAGE request the specific location information for MCPTT adhoc group emergency alert as specified in clause 6.2.9.1;
6) may set the MCPTT emergency state if not already set;
7) may set the MCPTT adhoc group emergency alert state to "AH-MEA 2: adhoc-emergency-alert-confirm-pending";
8) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
9) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated", if the current MCPTT adhoc group emergency alert state is "AH-MEA 2: adhoc-emergency-alert-confirm-pending".
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert".
NOTE 4: The MCPTT emergency state is left set in this case as the MCPTT user presumably is in the best position to determine whether or not they are in a life-threatening condition. The assumption is that the MCPTT user can clear the MCPTT emergency state manually if need be.
NOTE 5: Based on implementation the MCPTT client can subsequently automatically originate an MCPTT emergency group call as specified in clause 17.2.2.1.1.
12.1A.1.2 Ad hoc group emergency alert cancellation
Upon receiving a request from the MCPTT user to send an MCPTT adhoc group emergency alert cancellation, the MCPTT client shall determine if this is an authorised request for an MCPTT adhoc group emergency alert cancellation as specified in the clause 6.2.8.1.19.
If this is an unauthorised request for an MCPTT adhoc group emergency alert cancellation, the MCPTT client:
1) should indicate to the MCPTT user that adhoc group emergency alert cancellations are not allowed; and
2) shall skip the remainder of this procedure.
If this is an authorised request, MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT adhoc group identity;
b) the <anyExt> element with the <adhoc-alert-ind> element set to a value of "false";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 1A: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user is cancelling an MCPTT adhoc group emergency alert originated by another MCPTT user, include the <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT adhoc group emergency alert;
f) set the MCPTT adhoc group emergency alert state to "AH-MEA 4: adhoc-emergency-alert-cancel-pending"; and
g) if the MCPTT user has requested to include additional information related to the MCPTT ad hoc emergency alert, the <anyExt> element with the <adhoc-additional-information> element set to the user provided value;
5) void
6) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
7) if the generated SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT adhoc group emergency alert state to "AH-MEA 4: adhoc-emergency-alert-cancel-pending"; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-alert-ind-rcvd> element set to true and an <mcptt-client-id> matching the MCPTT client ID included in the sent SIP MESSAGE request:
1) if the <adhoc-alert-ind> element is set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request and if the MCPTT adhoc group emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall:
a) set the MCPTT adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert"; and
b) clear the MCPTT emergency state if not already cleared;
2) if the <adhoc-alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCPTT adhoc group emergency alert state is set to "AH-MEA 4: adhoc-emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT adhoc group emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT adhoc group emergency alerts but not have the authority to clear them. Hence, the case is covered here.
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:
1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the <adhoc-alert-ind> element set to a value of "true", the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT adhoc group emergency alert state is set to "AH-MEA 4: adhoc-emergency-alert-cancel-pending", shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated"; and
2) if the received SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request does not contain an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-alert-ind> element, the sent SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT adhoc group emergency alert state is set to "AH-MEA 4: adhoc-emergency-alert-cancel-pending", shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated".
12.1A.1.3 MCPTT client receives an MCPTT adhoc group emergency alert notification
Upon receipt of a "SIP MESSAGE request for adhoc group emergency alert notification", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "true", may display to the MCPTT user the functional alias of the originating MCPTT user, if provided, and should display to the MCPTT user an indication of the MCPTT adhoc group emergency alert and associated information, including:
a) the MCPTT group identity contained in <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
b) the originator of the MCPTT adhoc group emergency alert contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
c) the mission critical organization of the MCPTT adhoc group emergency alert originator contained in the <mc-org> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
d) the additional information related to the MCPTT adhoc group emergency alert contained in the <anyExt> element with the <adhoc-additional-information> element of the application/vnd.3gpp.mcptt-info+xml MIME body, if present;
NOTE 1: This is the case of the MCPTT client receiving the notification of another MCPTT user’s adhoc group emergency alert.
2) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the MCPTT adhoc group emergency alert cancellation and associated information, including:
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
ii) the originator of the MCPTT adhoc group emergency alert contained in:
A) if present, the <originated-by> element of the application/vnd.3gpp.mcptt-info+xml MIME body; or
B) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) if the MCPTT ID contained in the <originated-by> element is the MCPTT ID of the receiving MCPTT user, shall set the MCPTT adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert";
NOTE 2: This is the case of the MCPTT client receiving the notification of the cancellation by an MCPTT authorized user of an MCPTT adhoc group emergency alert. This can be the MCPTT adhoc group emergency alert of another MCPTT user or the MCPTT adhoc group emergency alert of the recipient, as determined by the contents of the <originated-by> element.
3) void;
4) void;
5) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
6) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
12.1A.1.4 Void
12.1A.1.5 Sending a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCPTT function"
Upon receiving a request from the MCPTT user to modify criteria of participants for an MCPTT ad hoc group emergency alert, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the identity of the ad hoc group;
b) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
c) an <anyExt> element containing:
i) an <adhoc-alert-ind> element set to a value of "true";
ii) a <req-type> set to a value of "ad-hoc-emergency-alert-participant-criteria-modification";
iii) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, a <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 2: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
iv) if the MCPTT user has requested to include additional information related to the MCPTT ad hoc emergency alert, an <adhoc-additional-information> element set to the user provided value; and
v) a <call-participants-criterias> with one or more criteria as a comma separated list;
5) may include in the SIP MESSAGE request the specific location information for MCPTT ad hoc group emergency alert as specified in clause 6.2.9.1;
6) may set the MCPTT emergency state if not already set;
7) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
12.1A.1.6 Receiving a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from participating MCPTT function"
Upon receipt of a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from the participating MCPTT function", the MCPTT client:
1) shall store:
a) the ad hoc group identity in the <mcptt-calling-group-id> element; and
b) the criteria in the <call-participants-criterias> element in the <anyExt> element;
in the <mcptt-Params> element in the <mcpttinfo> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
2) may notify the user with the ad hoc group identity and the criteria stored in step 1); and
3) shall generate and send the SIP 200 (OK) response to the participating MCPTT function according to 3GPP TS 24.229 [4].
12.1A.2 Participating MCPTT function procedures
12.1A.2.1 Receipt of a SIP MESSAGE request for adhoc group emergency notification from the served MCPTT client
Upon receipt of a "SIP MESSAGE request for adhoc emergency notification for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can, according to local policy, choose to accept the request.
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) shall determine the public service identity of the controlling MCPTT function for the adhoc group emergency alert service associated with the originating user's identity i.e. MCPTT ID;
NOTE 3: How the participating MCPTT function determines the public service identity of the controlling MCPTT function for the adhoc group emergency alert service associated with the originating user's identity is out of the scope of the present document.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4) above;
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
7A) may modify based on local policy the content of the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
8) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID. If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise it shall not include a <functional-alias-URI> element;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3 shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP MESSAGE request;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
12) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 10):
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
2) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
12.1A.2.2 Receipt of a SIP MESSAGE request for adhoc group emergency notification for terminating MCPTT client
In the procedures in this clause:
1) alert indication in an incoming SIP MESSAGE request refers to the <adhoc-alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP MESSAGE request for adhoc emergency notification for terminating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
5) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.2.3 Receipt of a SIP MESSAGE request indicating successful delivery of adhoc group emergency notification of originating MCPTT client
Upon receipt of a SIP MESSAGE request routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-alert-ind-rcvd> element present, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCPTT ID of the MCPTT user that was in the Request-URI of the incoming SIP MESSAGE request;
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; and
d) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] towards the originating MCPTT client of the adhoc group emergency alert.
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.2.4 Adhoc group emergency alert participants determination procedure
The participating MCPTT function shall follow the procedures as specified in the clause 17.3.6.1.
12.1A.2.5 Adhoc group emergency alert participants determination stop procedure
The participating MCPTT function shall follow the procedures as specified in the clause 17.3.6.2.
12.1A.2.6 Adhoc group emergency alert participants modify procedure initiated by participating MCPTT function
When the participating MCPTT function determines that new MCPTT users are meeting the specified criteria or the MCPTT users who were meeting the specified criteria are no longer meeting the specified criteria, the participating MCPTT function shall follow the procedures as specified in the clause 17.3.5.2.1.
12.1A.2.7 Receiving a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCPTT function"
Upon receipt of a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can, according to local policy, choose to accept the request.
2) shall determine the MCPTT ID of the requesting user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 2: The MCPTT ID of the requesting user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) shall determine the public service identity of the controlling MCPTT function;
5) shall check whether the user is authorized to modify participant criteria;
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4) above;
8) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
9) may modify based on local policy the content of the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
10) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID determined in step 2). If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise, it shall not include a <functional-alias-URI> element;
11) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
12) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3 shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP MESSAGE request;
13) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 14):
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
2) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client.
12.1A.2.8 Receiving a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from controlling MCPTT function"
Upon receipt of a "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from controlling MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE: If the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; and
6) shall send the SIP MESSAGE request to the MCPTT client identified by the MCPTT ID used in step 2) as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.3 Controlling MCPTT function procedures
12.1A.3.1 Handling of adhoc group emergency alert notification
Upon receipt of a "SIP MESSAGE request for adhoc emergency notification for controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP MESSAGE request contains an alert indication set to a value of "true", the controlling MCPTT function can, according to local policy, choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2a) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false", shall perform the procedures specified in clause 12.1A.3.2 and skip the rest of the steps;
3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "true":
a) if the received SIP MESSAGE request is an unauthorised request for an adhoc group emergency alert as specified in clause 6.3.3.1.13.8, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the < adhoc-alert-ind> element set to a value of "false"; and
ii) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
b) if the received SIP MESSAGE request is an authorised request for an adhoc group emergency alert as specified in clause 6.3.3.1.13.8, shall determine the MCPTT users that meet the criteria contained in the <call-participants-criterias> contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request:
NOTE 2: The determination of meeting the criteria is left to implementation and can use additional predefined data stored on the controlling MCPTT function.
i) shall create the adhoc group and generate the group identity to be associated with the adhoc group if the identity of adhoc group included in the <mcptt-request-uri> element of the <mcptt-Params> element of the <mcpttinfo> element containing in an application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP MESSAGE request is not acceptable or not included;
ii) shall determine the participants of the adhoc group emergency alert and send the adhoc group emergency alert, as specified in clause 12.1A.3.4;
iii) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
A) shall include the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
I) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in this clause; and
II) the <call-participants-criterias> element in the <anyExt> element as determined in step 5)/b) in clause 17.4.6.1;
iv) shall send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4];
v) shall cache the information that the MCPTT user has initiated an adhoc group emergency alert;
vi) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an adhoc group emergency alert to the initiator, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing:
A) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
B) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in this clause; and
C) an <anyExt> element containing:
I) an <adhoc-alert-ind> element set to a value of "true";
II) an <adhoc-alert-ind-rcvd> element set to a value of "true"; and
III) a <call-participants-criterias> element as determined in step 5) b) in clause 17.4.6.1; and
vii) shall send the SIP MESSAGE request towards the originating participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]; and
4) shall continue to include the MCPTT users meeting or to remove MCPTT users no longer meeting the criteria as specified in the clause 12.1A.3.3.
12.1A.3.2 Handling of adhoc group emergency alert cancellation
Upon receipt of a "SIP MESSAGE request for adhoc emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE: If the SIP MESSAGE request contains an alert indication set to a value of "false", the controlling MCPTT function can, according to local policy, choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the received SIP MESSAGE request is an unauthorised request for an adhoc group emergency alert cancellation as specified in clause 6.3.3.1.13.9, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing the anyExt> element with the <adhoc-alert-ind> element set to a value of "true"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
4) if the received SIP MESSAGE request is an authorised request for an adhoc group emergency alert cancellation as specified in clause 6.3.3.1.13.9:
a) shall stop determining the participants of the adhoc group emergency alert, as specified in clause 12.1A.3.5;
b) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding adhoc group emergency alert;
c) if the received SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the sender of the SIP MESSAGE request as having an outstanding adhoc group emergency alert;
d) for each members of the adhoc group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the adhoc group emergency alert as specified in clause 6.3.3.1.11;
ii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
iii) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
iv) if the received SIP MESSAGE request contains an <adhoc-additional-information> element in the <anyExt> element in the <mcptt-Params> element in the <mcpttinfo> element in the application/vnd.3gpp.mcptt-info+xml MIME body, copy the contents of the received <adhoc-additional-information> element to an <adhoc-additional-information> element in the <anyExt> element in the <mcptt-Params> element in the <mcpttinfo> element in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
v) shall include an <adhoc-alert-ind> element set to a value of "false" in an <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
vi) send the SIP MESSAGE request towards the terminating MCPTT clients as specified in 3GPP TS 24.229 [4];
e) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
f) shall send the SIP 200 (OK) response to the received SIP MESSAGE request towards the originating MCPTT client as specified in 3GPP TS 24.229 [4];
g) to indicate successful receipt of an adhoc group emergency alert cancellation shall:
i) generate a SIP MESSAGE request as described in clause 6.3.3.1.20, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing:
A) the <anyExt> element with the <adhoc-alert-ind> element set to a value of "false";
B) the <anyExt> element with the <adhoc-alert-ind-rcvd> element set to a value of true;
C) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
D) the <mcptt-calling-group-id> element set to the adhoc group identity received in the incoming SIP MESSAGE request; and
ii) shall send the SIP MESSAGE request towards the originating participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]; and
h) if no call is in-progress on ad hoc group or once the ongoing adhoc group call is terminated, the cached information about adhoc group is cleared.
12.1A.3.3 Handling of ongoing adhoc group emergency alert
When the controlling MCPTT function is notified that a new MCPTT client is meeting the criteria, or that an MCPTT client does not meet the criteria any more, the controlling MCPTT function:
1) shall for each new user determined to meet the criteria:
a) generate an outgoing SIP MESSAGE request notification of the MCPTT user's adhoc group emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.23;
b) include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <adhoc-alert-ind> element to a value of "true"; and
c) include the <call-participants-criterias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5)/b) in clause 12.1A.3.4; and
d) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4];
2) shall for each new user determined to not meet the criteria anymore:
a) generate an outgoing SIP MESSAGE request notification of the MCPTT user's adhoc group emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.23;
b) include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <adhoc-alert-ind> element to a value of "false"; and
c) include the <call-participants-criterias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5)/b) in clause 12.1A.3.4; and
d) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4];
3) shall cache the information of the adhoc group identity and the list of MCPTT users that meet the criteria for the duration of the adhoc group emergency alert.
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests shall:
1) cache the information of the adhoc group identity and a separate list of MCPTT users that meet the criteria but did not respond with a SIP 2xx response to the above SIP MESSAGE request for notification of the MCPTT user's adhoc group emergency alert indication, for the duration of the adhoc group emergency alert;
2) determine the users that are authorized to receive adhoc group emergency alert participant information as described in clause 6.3.3.1.13.10;
3) for each new user determined to be authorized to receive adhoc group emergency alert participant information:
a) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.24; and
b) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
2) follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.3.4 Adhoc group emergency alert participants determination procedures
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.6.1.
12.1A.3.5 Adhoc group emergency alert participants determination stop procedures
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.6.2.
12.1A.3.6 Handling of adhoc group emergency alert participants modify procedure initiated by participating MCPTT function
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.5.2.1.
12.1A.3.7 Receiving a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to controlling MCPTT function"
Upon receipt of a "SIP MESSAGE request to modify participant criteria for ad hoc group emergency alert to controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP MESSAGE request contains an alert indication set to a value of "true", the controlling MCPTT function can, according to local policy, choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) shall determine the MCPTT users that meet the criteria contained in the <call-participants-criterias> contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request:
NOTE 2: The determination of meeting the criteria is left to implementation and can use additional predefined data stored on the controlling MCPTT function.
a) shall determine the participants of the ad hoc group emergency alert and send the ad hoc group emergency alert, as specified in clause 12.1A.3.4;
b) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
c) shall send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4];
d) shall cache the information that the MCPTT user has initiated an ad hoc group emergency alert;
e) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an ad hoc group emergency alert to the initiator, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) an <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
ii) an <mcptt-calling-group-id> element set to the ad hoc group identity; and
iii) an <anyExt> element containing:
A) a <resp-type> set to a value of "ad-hoc-emergency-alert-participant-criteria-modification";
B) an <adhoc-alert-ind-rcvd> element set to a value of "true"; and
C) a <call-participants-criterias> element; and
4) shall send the SIP MESSAGE request towards the participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]; and
5) shall continue to include the MCPTT users meeting or to remove MCPTT users no longer meeting the criteria included in the incoming SIP MESSAGE request as specified in the clause 12.1A.3.3.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.2 Off-network emergency alert
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.2.1 General
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.2.2 Basic state machine
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
12.2.2.1 General
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.