11.1.3 Ending the private call initiated by MCPTT client

24.3793GPPMission Critical Push To Talk (MCPTT) call controlProtocol specificationRelease 18TS

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

11.1.3.1 MCPTT client procedures

11.1.3.1.1 On-demand private call

11.1.3.1.1.1 Client originating procedures

Upon receiving a request from an MCPTT user to release an MCPTT private call session established using on-demand session signalling, the MCPTT client shall follow the procedures as specified in clause 6.2.5.1.

11.1.3.1.1.2 Client terminating procedures

Upon receiving a SIP BYE request for private call session, the MCPTT client shall follow the procedures as specified in clause 6.2.6.

11.1.3.1.2 Private call using pre-established session

11.1.3.1.2.1 Client originating procedures

Upon receiving a request from an MCPTT user to release an MCPTT private call within a pre-established session, the MCPTT client shall follow the procedures as specified in clause 6.2.5.2.

11.1.3.1.2.2 Client terminating procedures

The MCPTT client shall follow the procedures for terminating of request for MCPTT private call release as specified in clause 6.2.6.

11.1.3.2 Participating MCPTT function procedures

11.1.3.2.1 Originating procedures

11.1.3.2.1.1 Receipt of SIP BYE request for on-demand private call

Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6.

11.1.3.2.1.2 Receipt of REFER "BYE" request for private call using pre-established session

Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.

11.1.3.2.2 Terminating procedures

11.1.3.2.2.1 Receipt of SIP BYE request for private call on-demand

Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.

11.1.3.2.2.2 Receipt of SIP BYE request when ongoing pre-established session

Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function:

1) shall interact with the media plane as specified in clause 9.3 in 3GPP TS 24.380 [5] for disconnecting the media plane resources towards the controlling MCPTT function;

2) shall send a SIP 200 (OK) response to the controlling MCPTT function;

3) shall interact with the media plane as specified in clause 9.3 in 3GPP TS 24.380 [5] for disconnecting media plane resources towards the MCPTT client from the media plane resources towards the controlling MCPTT function; and

4) shall maintain the pre-established session towards the MCPTT client.

11.1.3.3 Controlling MCPTT function procedures

11.1.3.3.1 Terminating procedures

Upon receiving a SIP BYE request the controlling MCPTT function shall follow the procedures as specified in clause 6.3.3.2.4.