hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.1 General
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.1.1 Common procedures
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.1.1.1 Sending/Receiving a message
In order to participate in a private call, the MCPTT client: 1) shall send the MONP message as a UDP message to the local IP address of the MCPTT user, to UDP port 8809, with an IP time-to-live set to 255; and 2) shall treat UDP messages received on the port TBD as received 8809 messages. NOTE: An MCPTT client that ...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.1.1.2 Session description
For an off-network MCPTT session, only MCPTT speech is used. One off-network MCPTT session includes one media-floor control entity. The MCPTT client shall generate an SDP body for a private call in accordance with rules and procedures of IETF RFC 4566 [12] and IETF RFC 3264 [44]. The MCPTT client: 1) shall include ...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2 Basic call control
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.1 General
The maximum number of simultaneous off-network private calls is limited by the value of "/<x>/Common/PrivateCall/MaxCallN10" leaf node present in the UE configuration as specified in 3GPP TS 24.483 [45].
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.2 Private call control state machine
The figure 11.2.2.2-1 gives an overview of the main states and transitions on the UE for private call control. Each private call control state machine is per MCPTT user ID. Figure 11.2.2.2-1: Private call control state machine
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.3 Private call control states
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.3.1 P0: start-stop
In this state, no private call control entity exists.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4 Procedures
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.1 General
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.2 Private call setup
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 increme...
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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" s...
603c77cd0da93e5e476a024643c0ef1c
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 time...
603c77cd0da93e5e476a024643c0ef1c
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 A...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.3 Private call setup in automatic commencement mode
603c77cd0da93e5e476a024643c0ef1c
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 C...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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)...
603c77cd0da93e5e476a024643c0ef1c
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 sta...
603c77cd0da93e5e476a024643c0ef1c
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 c...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.4 Private call setup in manual commencement mode
603c77cd0da93e5e476a024643c0ef1c
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 messag...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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 th...
603c77cd0da93e5e476a024643c0ef1c
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)...
603c77cd0da93e5e476a024643c0ef1c
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 st...
603c77cd0da93e5e476a024643c0ef1c
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 c...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.5 Private call release
603c77cd0da93e5e476a024643c0ef1c
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 id...
603c77cd0da93e5e476a024643c0ef1c
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 sto...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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 st...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 sa...
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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 tim...
603c77cd0da93e5e476a024643c0ef1c
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); ...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.2.4.6 Error handling
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3 Call type control
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.3 Call type control states
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.4 Procedures
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.4.1 General
603c77cd0da93e5e476a024643c0ef1c
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/Auth...
603c77cd0da93e5e476a024643c0ef1c
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 "EMERGE...
603c77cd0da93e5e476a024643c0ef1c
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 emerg...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.4.5 Upgrade call
603c77cd0da93e5e476a024643c0ef1c
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 a...
603c77cd0da93e5e476a024643c0ef1c
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 (priv...
603c77cd0da93e5e476a024643c0ef1c
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 genera...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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-pac...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.4.6 Downgrade call
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 me...
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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 i...
603c77cd0da93e5e476a024643c0ef1c
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 ca...
603c77cd0da93e5e476a024643c0ef1c
24.379
11.2.3.4.8 Error handling
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
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.
603c77cd0da93e5e476a024643c0ef1c
24.379
12 Emergency alert
603c77cd0da93e5e476a024643c0ef1c
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 emergen...
603c77cd0da93e5e476a024643c0ef1c
24.379
12.1 On-network emergency alert
603c77cd0da93e5e476a024643c0ef1c
24.379
12.1.1 Client procedures
603c77cd0da93e5e476a024643c0ef1c
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...
603c77cd0da93e5e476a024643c0ef1c
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 [...
603c77cd0da93e5e476a024643c0ef1c
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,...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 ...
603c77cd0da93e5e476a024643c0ef1c
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 MC...
603c77cd0da93e5e476a024643c0ef1c
24.379
12.1.2 Participating MCPTT function procedures
603c77cd0da93e5e476a024643c0ef1c
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) res...
603c77cd0da93e5e476a024643c0ef1c
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+x...
603c77cd0da93e5e476a024643c0ef1c
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 <emergenc...
603c77cd0da93e5e476a024643c0ef1c
24.379
12.1.3 Controlling MCPTT function procedures