hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.3.1.2 Automatic commencement mode for group calls | When performing the automatic commencement mode procedures, the MCPTT client shall follow the procedures in clause 6.2.3.1.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.3.2 Manual commencement mode | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.3.2.1 Manual commencement mode for private calls | When performing the manual commencement mode procedures:
1) if the MCPTT user declines the MCPTT session invitation the MCPTT client shall send a SIP 480 (Temporarily Unavailable) response towards the MCPTT server with the warning text set to: "110 user declined the call invitation" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause; and
2) if the MCPTT user requests to forward the MCPTT private call based on manual user input, the MCPTT client shall send a SIP 480 (Temporarily Unavailable) response including warning text set to "175 call is forwarded" in a Warning header field as specified in clause 4.4 and follow the procedures as specified in clause 11.1.9.2.1, and not continue with the rest of the steps in this clause.
The MCPTT client:
1) shall accept the SIP INVITE request and generate a SIP 180 (Ringing) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the option tag "timer" in a Require header field of the SIP 180 (Ringing) response;
3) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP 180 (Ringing) response;
4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP 180 (Ringing) response; and
5) shall send the SIP 180 (Ringing) response to the MCPTT server.
When sending the SIP 200 (OK) response to the incoming SIP INVITE request, the MCPTT client shall follow the procedures in clause 6.2.3.1.1.
When NAT traversal is supported by the MCPTT client and when the MCPTT client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [15]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.3.2.2 Manual commencement mode for group calls | When performing the manual commencement mode procedures:
1) the terminating MCPTT client may automatically generate a SIP 183 (Session Progress) in accordance with 3GPP TS 24.229 [4], prior to the MCPTT user's acknowledgement; and
2) if the MCPTT user declines the MCPTT session invitation the MCPTT client shall send a SIP 480 (Temporarily Unavailable) response towards the MCPTT server with the warning text set to: "110 user declined the call invitation" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause.
When generating a SIP 183 (Session Progress) response, the MCPTT client:
1) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag; and
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
When sending the SIP 200 (OK) response to the incoming SIP INVITE request, the MCPTT client shall follow the procedures in clause 6.2.3.1.2.
When NAT traversal is supported by the MCPTT client and when the MCPTT client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [15]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.4 Leaving an MCPTT session initiated by MCPTT client | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.4.1 On-demand session case | Upon receiving a request from an MCPTT user to leave an MCPTT session established using on-demand session signalling, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
3) shall set the Request-URI to the MCPTT session identity to leave; and
4) shall send a SIP BYE request towards MCPTT server according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request, the MCPTT client shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.4.2 Pre-established session case | Upon receiving a request from an MCPTT user to leave an MCPTT session within a pre-established session, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate an initial SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27];
3) shall set the Request-URI of the SIP REFER request to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
4) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
5) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
6) shall set the Refer-To header field of the SIP REFER request to the MCPTT session identity to leave;
7) shall include the "method" SIP URI parameter with the value "BYE" in the URI in the Refer-To header field;
8) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session; and
9) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response to the SIP REFER request, the MCPTT client shall interact with media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.5 Releasing an MCPTT session initiated by MCPTT client | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.5.1 On-demand session case | When the MCPTT client wants to release an MCPTT session using on-demand session signalling, the MCPTT client:
1) if the session is in the process of being established, shall send a SIP CANCEL request according to 3GPP TS 24.229 [4] and skip the rest of the steps;
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
3) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
4) shall set the Request-URI to the MCPTT session identity to release; and
5) shall send a SIP BYE request towards MCPTT server according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.5.2 Pre-established session case | When the MCPTT client wants to release an MCPTT call using a pre-established session, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate an initial SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27];
3) shall set the Request-URI of the SIP REFER request to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
4) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
5) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
6) shall set the Refer-To header field of the SIP REFER request to the MCPTT session identity to release;
7) shall include the "method" SIP URI parameter with the value "BYE" in the URI in the Refer-To header field;
8) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session; and
9) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response to the SIP REFER request, the MCPTT client shall interact with media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.6 Receiving an MCPTT session release request | Upon receiving a SIP BYE request, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
2) shall send SIP 200 (OK) response towards MCPTT server according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.7 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8 Priority call conditions | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.0 General | The clauses of the parent clause contain common procedures to be used for MCPTT emergency group calls and MCPTT imminent peril group calls. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1 MCPTT emergency group call conditions | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.1 SIP INVITE request or SIP REFER request for originating MCPTT emergency group calls | This clause is referenced from other procedures.
When the MCPTT emergency state is set and the MCPTT user is authorised to initiate an MCPTT emergency group call on the targeted MCPTT group as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request or SIP REFER request, an <emergency-ind> element set to "true";
2) if the MCPTT emergency group call state is set to "MEGC 1: emergency-gc-capable", shall set the MCPTT emergency group call state to "MEGC 2: emergency-call-requested";
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, and the MCPTT emergency alert state is set to "MEA 1: no-alert", shall:
a) set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "true" and set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP INVITE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent and the MCPTT emergency alert state is set to "MEA 1: no-alert", shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT client emergency group state of the group is set to a value other than "MEG 2: in-progress" set the MCPTT client emergency group state of the MCPTT group to "MEG 4: confirm-pending".
NOTE 1: This is the case of an MCPTT user already being in the MCPTT emergency state it initiated previously while originating an MCPTT emergency group call or MCPTT emergency alert. All group calls the MCPTT user originates while in MCPTT emergency state will be MCPTT emergency group calls.
When the MCPTT emergency state is clear and the MCPTT emergency group call state is set to "MEGC 1: emergency-gc-capable" and the the MCPTT user is authorised to initiate an MCPTT emergency group call on the targetted MCPTT group as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) shall set the MCPTT emergency state;
2) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request or SIP REFER request an <emergency-ind> element set to "true" and set the MCPTT emergency group call state to "MEGC 2: emergency-call-requested" state;
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, shall:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body the <alert-ind> element set to "true" and set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP INVITE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT client emergency group state of the group is set to a value other than "MEG 2: in-progress" shall set the MCPTT client emergency group state of the MCPTT group to "MEG 4: confirm-pending".
NOTE 2: This is the case of an initial MCPTT emergency group call and optionally an MCPTT emergency alert being sent. As the MCPTT emergency state is not sent, there is no MCPTT emergency alert outstanding.
NOTE 3: An MCPTT group call originated by an affiliated member of an MCPTT group which is in an in-progress emergency state (as tracked on the MCPTT client by the MCPTT client emergency group state) but is not in an MCPTT emergency state of their own will also be an MCPTT emergency group call. The <emergency-ind> and <alert-ind> elements of the application/vnd.3gpp.mcptt-info+xml MIME body do not need to be included in this case and hence no action needs to be taken in this clause. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.2 Resource-Priority header field for MCPTT emergency group calls | This clause is referenced from other procedures.
If the MCPTT emergency group call state is set to either "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" and this is an authorised request for an MCPTT emergency group call as determined by the procedures of clause 6.2.8.1.8, or the MCPTT client emergency group state of the group is set to "MEG 2: in-progress", the MCPTT client shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for an MCPTT emergency group call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress emergency state of the group (as tracked on the MCPTT client by the MCPTT client emergency group state) but can use this knowledge to provide a Resource-Priority header field set to emergency level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
If this is an authorised request to cancel the MCPTT emergency group call as determined by the procedures of clause 6.2.8.1.7, and the MCPTT client emergency group state of the group is "no-emergency" or "cancel-pending", the MCPTT client shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.2.8.1.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.3 SIP re-INVITE request for cancelling MCPTT in-progress emergency group state | This clause is referenced from other procedures.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to "MEA 1: no-alert", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
NOTE 1: This procedure assumes that the calling procedure has verified that the MCPTT user has made an authorised request for cancelling MCPTT in-progress emergency group state of the group.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall clear the MCPTT emergency state; and
3) shall set MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending"
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT emergency group call and wants to cancel it.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to a value other than "MEA 1: no-alert" and the MCPTT user has indicated only the MCPTT emergency group call should be cancelled, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false"; and
2) shall set the MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending".
NOTE 3: This is the case of an MCPTT user has initiated both an MCPTT emergency group call and an MCPTT emergency alert and wishes to only cancel the MCPTT emergency group call. This leaves the MCPTT emergency state set.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to a value other than "MEA 1: no-alert" and the MCPTT user has indicated that the MCPTT emergency alert on the MCPTT group should be cancelled in addition to the MCPTT emergency group call, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall if this is an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to "false";
b) set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
c) clear the MCPTT emergency state;
3) should, if this is not an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, indicate to the MCPTT user that they are not authorised to cancel the MCPTT emergency alert; and
4) shall set the MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending".
NOTE 4: This is the case of an MCPTT user that has initiated both an MCPTT emergency group call and an MCPTT emergency alert and wishes to cancel both. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.4 Receiving a SIP 2xx response to a SIP request for a priority call | In the procedures in this clause, a priority group call refers to an MCPTT emergency group call or an MCPTT imminent peril group call.
On receiving a SIP 2xx response to a SIP request for a priority group call, the MCPTT client:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted":
a) shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress" if it was not already set;
b) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending" and the SIP 2xx response to the SIP request for a priority group call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated;
c) shall set the MCPTT emergency group call state to "MEGC 3: emergency-call-granted"; and
d) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable" and the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; or
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted" and the SIP 2xx response to the SIP request for an imminent peril group call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149":
a) set the MCPTT imminent peril group call state to "MIGC 3: imminent-peril-call-granted"; and
b) set the MCPTT imminent peril group state to "MIG 2: in-progress". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a priority group call | In the procedures in this clause, a priority group call refers to an MCPTT emergency group call or an MCPTT imminent peril group call.
Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for a priority group call the MCPTT client:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
b) if the MCPTT client emergency group state of the group is "MEG 4: confirm-pending" shall set the MCPTT client emergency group state of the group to "MEG 1: no-emergency"; and
c) if the sent SIP request for a priority group call contained an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element set to a value of "true", shall set the MCPTT emergency alert state to "MEA 1: "no-alert"; and
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted":
a) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.6 Determining authorisation for initiating or cancelling an MCPTT emergency alert | If the MCPTT client receives a request from the MCPTT user to send an MCPTT emergency alert and:
1) if the <allow-activate-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
2) if the "entry-info" attribute of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of:
a) "DedicatedGroup", and if the <uri-entry> element of the <entry> element of the <EmergencyAlert> element of the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the MCPTT group identity of the MCPTT group targeted by the calling MCPTT user; or
b) "UseCurrentlySelectedGroup" and the <allow-MCPTT-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the <list-service> element of the group document identified by the MCPTT group identity targeted for the emergency alert is set to a value of "true" as specified in 3GPP TS 24.481 [31];
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency alert to an MCPTT group, and if the <allow-cancel-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request to cancel an MCPTT emergency alert. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.7 Determining authorisation for cancelling the in-progress emergency state of an MCPTT group | When the MCPTT client receives a request from the MCPTT user to cancel the in-progress emergency state of a group the MCPTT client, determines, based on local policy (e.g if the requester is dispatcher or initiator of the MCPTT emergency group call etc), whether to send the emergency group state cancel request or not. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.8 Determining authorisation for originating a priority group call | When the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency group call the MCPTT client shall check the following:
1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" and
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the MCPTT emergency group call request shall be considered to be an authorised request for an MCPTT emergency group call;
In all other cases, the request to originate an MCPTT emergency group call shall be considered to be an unauthorised request to originate an MCPTT emergency group call.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril group call the MCPTT client shall check the following:
1 if the <allow-imminent-peril-call> element of <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" and:
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the MCPTT imminent peril group call request shall be considered to be an authorised request for an MCPTT imminent peril group call;
In all other cases, the request to originate an MCPTT imminent peril group call shall be considered to be an unauthorised request to originate an MCPTT imminent peril group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.9 SIP request for originating MCPTT imminent peril group calls | This clause is referenced from other procedures.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril group call, and this is an authorised request for an MCPTT imminent peril group call as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) if the MCPTT client imminent peril call group state is set to "MIGC 1: imminent-peril-gc-capable" and the MCPTT client emergency group state of the MCPTT group is set to "MEG 1: no-emergency":
a) shall include in the SIP request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in Annex F.1 with the <imminentperil-ind> element set to "true" and set the MCPTT imminent peril group call state to "MIGC 2: imminent-peril-call-requested" state; and
b) if the MCPTT client imminent peril group state of the group is set to a value other than "MIG 2: in-progress" shall set the MCPTT client imminent peril group state of the MCPTT group to "MIG 4: confirm-pending".
NOTE: An MCPTT group call originated by an affiliated member of an MCPTT group which is in an in-progress imminent peril state (as tracked on the MCPTT client by the MCPTT client imminent peril group state) will also have the priority associated with MCPTT imminent peril group calls. The <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info MIME body does not need to be included in this case, nor do any state changes result and hence no action needs to be taken in this clause. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.10 Determining authorisation for cancelling an imminent peril group call | When the MCPTT client receives a request from the MCPTT user to cancel an MCPTT imminent peril group call the MCPTT client shall:
1) if the <allow-cancel-imminent-peril> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" the MCPTT imminent peril call cancellation request shall be considered to be an authorised request to cancel the MCPTT imminent peril group call; or
2) if the <allow-cancel-imminent-peril> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false" the MCPTT imminent peril call cancellation request shall be considered to be an unauthorised request to cancel the MCPTT imminent peril group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.11 SIP re-INVITE request for cancelling MCPTT in-progress imminent peril group state | This clause is referenced from other procedures.
If the MCPTT imminent peril group call state is set to "MIGC 3: imminent-peril-call-granted" or the MCPTT imminent peril group state of the MCPTT group is set to "MIG 2: in-progress", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
NOTE 1: This procedure assumes that the calling procedure has verified that the MCPTT user has made an authorised request for cancelling the in-progress imminent peril group state of the group.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <imminentperil-ind> element set to "false"; and
2) shall set MCPTT imminent peril group state of the MCPTT group to "MIG 3: cancel-pending".
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT imminent peril group call and wants to cancel it, or another authorised member of the group who wishes to cancel the in-progress imminent peril state of the group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.12 Resource-Priority header field for MCPTT imminent peril group calls | This clause is referenced from other procedures.
When the MCPTT imminent peril group call state is set "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted" and the MCPTT user is authorised to initiate an MCPTT imminent peril group call on the targeted MCPTT group as determined by the procedures of clause 6.2.8.1.8, or the MCPTT client imminent peril state of the group is set to "MIG 2: in-progress", the MCPTT client:
1) shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress imminent peril state of the group (as tracked on the MCPTT client by the MCPTT client imminent peril group state) but can use this knowledge to provide a Resource-Priority header field set to imminent peril level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
When the MCPTT imminent peril group call state is set to "MIGC 1: imminent-peril-gc-capable" and the MCPTT user is authorised to cancel MCPTT imminent peril group calls as determined by the procedures of clause 6.2.8.1.10, or the MCPTT client imminent peril group state of the group is "MIG 1: no-imminent-peril" or "MIG 3: cancel-pending", the MCPTT client:
1) shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.2.8.1.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.13 Receiving a SIP INFO request in the dialog of a SIP request for a priority group call | This clause is referenced from other procedures.
Upon receiving a SIP INFO request within the dialog of the SIP request for a priority group call:
- with the Info-Package header field containing the g.3gpp.mcptt-info package name;
- with the application/vnd.3gpp.mcptt-info+xml MIME body associated with the info package according to IETF RFC 6086 [64]; and
- with one or more of the <alert-ind>, <imminentperil-ind> and <emergency-ind> elements set in the application/vnd.3gpp.mcptt-info+xml MIME body;
the MCPTT client:
1) shall send a SIP 200 (OK) response to the SIP INFO request as specified in 3GPP TS 24.229 [4];
2) if the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted":
a) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending":
i) if the <alert-ind> element is set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
ii) if the <alert-ind> element is set to a value of "true", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated";
3) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted":
a) if the <imminentperil-ind> element is set to a value of "false" and an <emergency-ind> element is set to a value of "true", shall:
i) set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril";
ii) set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable"; and
iii) set the MCPTT client emergency group state of the group to "MEG 2: in-progress"; and
NOTE 1: This is the case of an MCPTT client attempting to make an imminent peril group call when the group is in an in-progress emergency group state. The MCPTT client will then receive a notification that the imminent peril call request was denied, however they will be participating at the emergency level priority of the group. This could occur for example when an MCPTT client requests an imminent peril call to a group that they are not currently affiliated with.
NOTE 2: the MCPTT client emergency group state above is the MCPTT client's view of the in-progress emergency state of the group.
4) if the SIP request for a priority group call sent by the MCPTT client did not contain an <originated-by> element and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending":
a) if the <alert-ind> element contained in the SIP INFO request is set to a value of "true", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
b) if the <alert-ind> element contained in the SIP INFO request is set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.14 SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a third-party | This clause is referenced from other procedures.
Upon receiving an authorised request to cancel an in-progress emergency group state of a group as determined by the procedures of clause 6.2.8.1.7 from an MCPTT user, the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall set MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending"; and
3) if the MCPTT user has indicated that an MCPTT emergency alert on the MCPTT group originated by another MCPTT user should be cancelled and this is an authorised request for an MCPTT emergency alert cancellation as determined by the procedures of clause 6.2.8.1.6:
a) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set a value of "false"; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT emergency alert.
NOTE: When an MCPTT emergency alert is cancelled by a MCPTT user other than its originator, the <originated-by> element is needed to identify which MCPTT emergency alert is being cancelled, as more than one MCPTT user could have originated emergency alerts to the same group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.15 Retrieving Resource-Priority header field values | This clause is referenced from other procedures.
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT emergency group call or MCPTT emergency private call or MCPTT emergency adhoc group call, the MCPTT client:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT imminent peril group call or MCPTT imminent peril adhoc group call, the MCPTT client:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for a normal MCPTT group or private call or normal MCPTT adhoc group call, the MCPTT client:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
NOTE: The "normal" Resource-Priority header field value is needed to return to a normal priority value from a priority value adjusted for an MCPTT emergency group or private call or an MCPTT imminent peril group call. The "normal" priority received from the EPS by use of the "normal" Resource-Priority header field value is expected to be the same as the "normal" priority received from the EPS when initiating a call with no Resource-Priority header field included. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.16 Handling receipt of a SIP re-INVITE request for priority group call origination status within a pre-established session | This clause is referenced from other procedures.
Upon receipt of a SIP re-INVITE request within the pre-established session targeted by the sent SIP REFER request, and if the sent SIP REFER request was a request for an MCPTT emergency group call or an MCPTT imminent peril group call, the MCPTT client:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested":
a) if there is no <emergency-ind> element or an <emergency-ind> element set to a value of "true" contained in the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP re-INVITE request, and if no <imminentperil-ind> element is included:
i) shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress" if it was not already set; and
ii) shall set the MCPTT emergency group call state to "MEGC 3: emergency-call-granted"; and
b) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending":
i) if the SIP re-INVITE request contains an <alert-ind> element set to a value of "true" or does not contain an <alert-ind> element, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; or
ii) if the SIP re-INVITE request contains an <alert-ind> element set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested:
a) if the sip re-INVITE request contains an <imminentperil-ind> element set to a value of "true" or does not contain an <imminentperil-ind> element, shall:
i) set the MCPTT imminent peril group call state to "MIGC 3: imminent-peril-call-granted"; and
ii) set the MCPTT imminent peril group state to "MIG 2: in-progress"; or
b) if the SIP re-INVITE request contains <imminentperil-ind> element set to a value of "false" and an <emergency-ind> element set to a value of "true", shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress".
NOTE: This is the case of an MCPTT client attempting to make an imminent peril group call when the group is in an in-progress emergency group state. The MCPTT client will then receive a notification that the imminent peril call request was denied, however they will be participating at the emergency level priority of the group. This could occur for example when an MCPTT client requests an imminent peril call to a group that they are not currently affiliated with. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.17 Priority group call conditions upon receiving call release | This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT emergency group call or an MCPTT imminent peril group call in an MCPTT group session is in-progress or is in the process of being established:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
b) if the MCPTT client emergency group state of the group is "MEG 4: confirm-pending" shall set the MCPTT client emergency group state of the group to "MEG 1: no-emergency"; and
c) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending" shall set the MCPTT emergency alert state to "MEA 1: "no-alert";
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested":
a) if the MCPTT imminent peril group call state of the group is "MIG 4: confirm-pending", shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
3) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-granted":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable"; and
4) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent peril-call-granted":
a) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-capable".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.18 Emergency private call conditions upon receiving call release | This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT session when an MCPTT emergency private call is in-progress or is in the process of being established:
1) if the MCPTT emergency private call state is set to "MEPC 2: emergency-call-requested":
a) shall set the MCPTT emergency private call state to "MEPC 1: emergency-pc-capable";
b) if the MCPTT emergency private priority state of the private call is "MEPP 4: confirm-pending" shall set the MCPTT emergency private priority state of the private call to "MEPP 1: no-emergency"; and
c) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending shall set the MCPTT private emergency alert state to "MPEA 1: no-alert".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 of 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.19 Determining authorisation for initiating or cancelling an MCPTT adhoc group emergency alert | If the MCPTT client receives a request from the MCPTT user to send an MCPTT adhoc group emergency alert and:
1) if the <allow-activate-adhoc-group-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the initiating user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then the MCPTT adhoc group emergency alert origination request shall be considered to be an authorised request to originate the MCPTT adhoc group emergency alert. In all other cases, it shall be considered to be an unauthorised request for the origination of the MCPTT adhoc group emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT adhoc group emergency alert to an MCPTT adhoc group, and:
1) if the <allow-cancel-adhoc-group-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the initiating MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then the MCPTT adhoc group emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT adhoc group emergency alert. In all other cases, it shall be considered to be an unauthorised request for cancellation of an MCPTT adhoc group emergency alert. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.20 Determining authorisation for initiating or cancelling the in-progress emergency state of an MCPTT adhoc group | When the MCPTT client receives a request from the MCPTT user to cancel the in-progress emergency state of a group the MCPTT client, determines, based on local policy (e.g., if the requester is dispatcher or initiator of the MCPTT emergency group call etc.), whether to send the emergency group state cancel request or not. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.21 SIP INVITE request or SIP REFER request for originating MCPTT emergency adhoc group calls | This clause is referenced from other procedures.
If the MCPTT user is authorised to initiate an MCPTT emergency adhoc group call on the targeted MCPTT adhoc group as determined by the procedures of clause 6.2.8.1.24, the MCPTT client:
1) if the MCPTT emergency state is clear, shall set the MCPTT emergency state;
2) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request or SIP REFER request, an <adhoc-emergency-ind> element set to "true";
3) shall set the MCPTT emergency adhoc group call state to "MEAGC 2: emergency-call-requested";
4) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 4: confirm-pending"; and
5) shall include the Resource-Priority header field populated with the values for an MCPTT emergency adhoc group call as specified in clause 6.2.8.1.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.22 Receiving a SIP 2xx response to a SIP request for a priority adhoc group call | In the procedures in this clause, a priority adhoc group call refers to an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call.
On receiving a SIP 2xx response to a SIP request for a priority adhoc group call, the MCPTT client:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 2: in-progress" if it was not already set;
b) shall set the MCPTT emergency adhoc group call state to "MEAGC 3: emergency-call-granted"; and
c) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable" and the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; or
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) set the MCPTT imminent peril adhoc group call state to "MIAGC 3: imminent-peril-call-granted"; and
b) set the MCPTT imminent peril adhoc group state to "MIAG 2: in-progress". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.23 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a priority adhoc group call | In the procedures in this clause, a priority adhoc group call refers to an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call.
Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for a priority adhoc group call the MCPTT client:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
b) if the MCPTT emergency adhoc group state of the MCPTT adhoc group is "MEAG 4: confirm-pending", shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency"; or
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) if the MCPTT imminent peril adhoc group state of the MCPTT adhoc group is "MIAG 1: confirm-pending", shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.24 Determining authorisation for originating a priority adhoc group call | When the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency adhoc group call the MCPTT client shall check the following:
1) if the <allow-emergency-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", the MCPTT emergency adhoc group call request shall be considered to be an authorised request for an MCPTT emergency adhoc group call.
In all other cases, the request to originate an MCPTT emergency adhoc group call shall be considered to be an unauthorised request to originate an MCPTT emergency adhoc group call.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril adhoc group call the MCPTT client shall check the following:
1 if the <allow-imminent-peril-adhoc-group-call> element of <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", the MCPTT imminent peril adhoc group call request shall be considered to be an authorised request for an MCPTT imminent peril adhoc group call;
In all other cases, the request to originate an MCPTT imminent peril adhoc group call shall be considered to be an unauthorised request to originate an MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.25 SIP request for originating MCPTT imminent peril adhoc group calls | This clause is referenced from other procedures.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril adhoc group call, and this is an authorised request for an MCPTT imminent peril adhoc group call as determined by the procedures of clause 6.2.8.1.24, the MCPTT client:
1) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 1: imminent-peril-gc-capable" and the MCPTT emergency adhoc group state of the MCPTT group is set to "MEAG 1: no-emergency":
a) shall include in the SIP request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in Annex F.1 with the <imminentperil-ind> element set to "true";
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 2: imminent-peril-call-requested" state;
c) shall set the MCPTT imminent peril adhoc group state of the MCPTT adhoc group to "MIAG 4: confirm-pending"; and
d) shall include the Resource-Priority header field populated with the values for an MCPTT imminent peril adhoc group call as specified in clause 6.2.8.1.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.26 Handling receipt of a SIP re-INVITE request for priority adhoc group call origination status within a pre-established session | This clause is referenced from other procedures.
Upon receipt of a SIP re-INVITE request within the pre-established session targeted by the sent SIP REFER request, and if the sent SIP REFER request was a request for an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call, the MCPTT client:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) if there is no <adhoc-emergency-ind> element or an <adhoc-emergency-ind> element set to a value of "true" contained in the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP re-INVITE request, and if no <imminentperil-ind> element is included:
i) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 2: in-progress" if it was not already set; and
ii) shall set the MCPTT emergency adhoc group call state to "MEAGC 3: emergency-call-granted";
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested:
a) if the sip re-INVITE request contains an <imminentperil-ind> element set to a value of "true" or does not contain an <imminentperil-ind> element, shall:
i) set the MCPTT imminent peril adhoc group call state to "MIAGC 3: imminent-peril-call-granted"; and
ii) set the MCPTT imminent peril adhoc group state to "MIAG 2: in-progress"; or
b) if the SIP re-INVITE request contains <imminentperil-ind> element set to a value of "false" and an <adhoc-emergency-ind> element set to a value of "true", shall set the MCPTT emergency adhoc group state of the adhoc group to "MEAG 2: in-progress".
NOTE: This is the case of an MCPTT client attempting to make an imminent peril adhoc group call when the adhoc group is in an in-progress emergency adhoc group state. The MCPTT client will then receive a notification that the imminent peril adhoc call request was denied, however they will be participating at the emergency level priority of the adhoc group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.27 Priority adhoc group call conditions upon receiving call release | This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call in an MCPTT group session is in-progress or is in the process of being established:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
b) if the MCPTT emergency adhoc group state of the MCPTT adhoc group is "MEAG 3: confirm-pending", shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency";
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable"; and
b) if the MCPTT imminent peril adhoc group state of the MCPTT adhoc group is "MIAG 3: confirm-pending", shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril";
3) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-granted":
a) shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency"; and
b) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
4) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent peril-call-granted":
a) shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-capable".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.1.28 Determining authorisation for cancelling the in-progress imminent peril state of an MCPTT group | When the MCPTT client receives a request from the MCPTT user to cancel the in-progress imminent peril state of a group, the MCPTT client, determines, based on local policy (e.g if the requester is dispatcher or initiator of the MCPTT imminent peril group call etc), whether to send the in-progress imminent peril state of a group cancel request or not. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.2 Request for an originating broadcast group call | NOTE: This clause is referenced from other procedures.
When the MCPTT user initiates a broadcast group call, the MCPTT client:
1) in the case of the prearranged group call is initiated on-demand, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body the <broadcast-ind> element set to "true" as defined in clause F.1; and
2) in the case the prearranged group call is initiated using a pre-established session, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field the <broadcast-ind> element set to "true" as defined in clause F.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3 MCPTT emergency private call conditions | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.1 Authorisations | 6.2.8.3.1.1 Determining authorisation for initiating an MCPTT emergency private call
If the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency private call and:
1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
a) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UsePreConfigured" and if the <uri-entry> element of the <entry> element of the <MCPTTPrivateRecipient> element contains the MCPTT ID of the MCPTT user targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "LocallyDetermined";
then the MCPTT client shall consider the MCPTT emergency private call request to be an authorised request for an MCPTT emergency private call. In all other cases the MCPTT client shall consider the MCPTT emergency private call request to be an unauthorised request for an MCPTT emergency private call.
6.2.8.3.1.2 Determining authorisation for cancelling an MCPTT emergency private call
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency private call and if the <allow-cancel-private-emergency-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency private call cancellation request shall be considered to be an authorised request for an MCPTT emergency private call cancellation.
In all other cases, the MCPTT emergency private call cancellation request shall be considered to be an unauthorised request for an MCPTT emergency private call cancellation.
6.2.8.3.1.3 Determining authorisation for initiating or cancelling an MCPTT emergency alert to a MCPTT user
If the MCPTT client receives a request from the MCPTT user to send an MCPTT emergency alert to an MCPTT user and:
1) if the <allow-activate-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user as specified in 3GPP TS 24.484 [50] is set to a value of "true"; and
2) if the "entry-info" attribute of the <entry> element of the <PrivateEmergencyAlert> element contained within the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of:
a) "UsePreConfigured", and if the <uri-entry> element of the <entry> element of the <PrivateEmergencyAlert> element of the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the MCPTT ID of the targeted MCPTT user; or
b) "LocallyDetermined";
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency alert to an MCPTT user, and if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user as specified in 3GPP TS 24.484 [50] is set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request to cancel an MCPTT emergency alert. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.2 SIP request for originating MCPTT emergency private calls | This clause is referenced from other procedures.
When the MCPTT emergency private call state is set to "MEPC 1: emergency-pc-capable" and this is an authorised request for an MCPTT emergency private call as determined by the procedures of clause 6.2.8.3.1.1, the MCPTT client:
1) shall set the MCPTT emergency state if not already set;
2) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP request an <emergency-ind> element set to "true" and set the MCPTT emergency private call state to "MEPC 2: emergency-pc-requested";
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3, shall:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body the <alert-ind> element set to "true" and set the MCPTT private emergency alert state to "MPEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT emergency private priority state of this private call is set to a value other than "MEPP 2: in-progress" shall set the MCPTT emergency private priority state to "MEPP 4: confirm-pending". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.3 Resource-Priority header field for MCPTT emergency private calls | This clause is referenced from other procedures.
If the MCPTT emergency private call state is set to either "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted" and this is an authorised request for an MCPTT emergency private call as determined by the procedures of clause 6.2.8.3.1.1, or the MCPTT emergency private priority state of the call is set to "MEPP 2: in-progress", the MCPTT client shall include in the SIP request a Resource-Priority header field populated with the values for an MCPTT emergency private call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress emergency state of the call (as tracked on the MCPTT client by the MCPTT client emergency private state) but can use this knowledge to provide a Resource-Priority header field set to emergency level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
If this is an authorised request to cancel the MCPTT emergency private call as determined by the procedures of clause 6.2.8.3.1.2, or the MCPTT emergency private priority state of the private call is "MEPP 1: no-emergency" or "MEPP 3: cancel-pending", the MCPTT client shall include in the SIP request a Resource-Priority header field populated with the values for a normal MCPTT private call as specified in clause 6.2.8.1.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.4 Receiving a SIP 2xx response to a SIP request for an MCPTT emergency private call | This clause is referenced from other procedures.
On receiving a SIP 2xx response to a SIP request for an MCPTT emergency private call and if the MCPTT emergency private call state is set to "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted", the MCPTT client:
1) shall set the MCPTT emergency private priority state of the call to "MEPP 2: in-progress" if it was not already set;
2) shall set the MCPTT emergency private call state to "MEPC 3: emergency-pc-granted"; and
3) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending" and the SIP 2xx response to the SIP request for a priority private call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for an MCPTT emergency private call | Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for an MCPTT emergency private call and if the MCPTT emergency private call state is set to "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted", the MCPTT client:
1) shall set the MCPTT emergency private call state to "MEPC 1: emergency-pc-capable";
2) if the MCPTT emergency private priority state of the private call is "MEPP 4: confirm-pending" shall set the MCPTT emergency private priority state of the private call to "MEPP 1: no-emergency"; and
3) if the sent SIP request for an MCPTT emergency private call contained an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.6 SIP re-INVITE request for cancelling MCPTT emergency private call state | This clause is referenced from other procedures.
When the MCPTT emergency private call state is set to "MEPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to "MPEA 1: no-alert", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
NOTE 1: This procedure assumes that the MCPTT client in the calling procedure has verified that the MCPTT user has made an authorised request for cancelling MCPTT the in-progress emergency private call state of the call.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall clear the MCPTT emergency state; and
3) shall set MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending".
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT emergency private call and wants to cancel it.
When the MCPTT emergency private call state is set to "MEPPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to a value other than "MPEA 1: no-alert" and the MCPTT user has indicated only the MCPTT emergency private call should be cancelled, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false"; and
2) shall set the MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending";
NOTE 3: This is the case of an MCPTT user has initiated both an MCPTT emergency private call and an MCPTT emergency alert and wishes to only cancel the MCPTT emergency private call. This leaves the MCPTT emergency state set.
When the MCPTT emergency private call state is set to "MEPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to a value other than "MPEA 1: no-alert" and the MCPTT user has indicated that the MCPTT emergency alert on the MCPTT private call should be cancelled in addition to the MCPTT emergency private call, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in annex F.1 with the <emergency-ind> element set to "false";
2) shall, if this is an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to "false"; and
b) set the MCPTT private emergency alert state to "MPEA 4: emergency-alert-cancel-pending";
3) if this is not an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3, should indicate to the MCPTT user they are not authorised to cancel the MCPTT emergency alert;
4) shall set the MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending"; and
5) shall clear the MCPTT emergency state.
NOTE 4: This is the case of an MCPTT user that has initiated both an MCPTT emergency private call and an MCPTT emergency alert and wishes to cancel both. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.7 Receiving a SIP INFO request in the dialog of a SIP request for a priority private call | This clause is referenced from other procedures.
Upon receiving a SIP INFO request within the dialog of the SIP request for a priority private call:
- with the Info-Package header field containing the g.3gpp.mcptt-info package name;
- with the application/vnd.3gpp.mcptt-info+xml MIME body associated with the info package according to IETF RFC 6086 [64]; and
- with one or more of the <alert-ind>, <imminentperil-ind> and <emergency-ind> elements set in the application/vnd.3gpp.mcptt-info+xml MIME body;
the MCPTT client:
1) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending":
a) if the <alert-ind> element is set to a value of "false", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert"; and
b) if the <alert-ind> element set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated"; and
2) if the MCPTT private emergency alert state is set to "MPEA 4: Emergency-alert-cancel-pending":
a) if the <alert-ind> element is set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated"; and
b) if the <alert-ind> element is set to a value of "false", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.8 SIP re-INVITE request for cancelling the MCPTT emergency private call state by a third-party | This clause is referenced from other procedures.
Upon receiving a request to cancel the MCPTT emergency private call state from an MCPTT user other than the originator of the MCPTT emergency private call, the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
The MCPTT client:
NOTE 1: This procedure assumes that the calling procedure has verified that the MCPTT user has made an authorised request for cancelling the MCPTT emergency private call state of the call.
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall set the MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending"; and
3) if the MCPTT user has indicated that an MCPTT emergency alert associated with the MCPTT emergency private call originated by another MCPTT user should be cancelled and this is an authorised request for an MCPTT emergency alert cancellation as determined by the procedures of clause 6.2.8.3.1.3:
a) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "false"; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT emergency alert.
NOTE 2: When an MCPTT emergency alert is cancelled by a MCPTT user other than its originator, the <originated-by> element is needed to identify which MCPTT emergency alert is being cancelled, as conceivably each participant in the MCPTT emergency private call could have originated an MCPTT emergency alert. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.8.3.9 Retrieving a KMS URI associated with an MCPTT ID | If the MCPTT client needs to retrieve a KMS URI associated to an identified MCPTT ID for on network operation, the MCPTT client:
1) shall search for the <entry> element of the <PrivateCallURI> element of the <PrivateCallList> element entry of the <Common> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) containing the identified MCPTT ID;
a) if the identified MCPTT ID is found and if the <entry> element of the <PrivateCallKMSURI> element of the <anyExt> element of the <PrivateCallList> element entry identified is not empty, shall retrieve the KMS URI contained therein; or
b) if the identified MCPTT ID is not found or the <entry> element of the <PrivateCallKMSURI> element is empty, shall retrieve the <kms> element of the <App-Server-Info> element of the <on-network> element of the MCPTT UE initial configuration document (see the MCPTT UE initial configuration document in 3GPP TS 24.484 [50]) and consider that to be the KMS URI associated with the MCPTT ID.
If the MCPTT client needs to retrieve a KMS URI associated to an identified MCPTT ID for off network operation, the MCPTT client:
1) shall search for /<x>/<x>/Common/PrivateCall/UserList/<x>/Entry/MCPTTID leaf node containing the identified MCPTT ID (see the MCPTT user profile MO in 3GPP TS 24.483 [45]);
a) if the identified MCPTT ID is found:
i) shall retrieve the /<x>/<x>/Common/PrivateCall/UserList/<x>/Entry/PrivateCallKMSURI leaf node (see the MCPTT user profile MO in 3GPP TS 24.483 [45]); and
ii) if the PrivateCallKMSURI leaf node in the same /<x>/<x>/Common/PrivateCall/UserList/<x>/Entry/ interior node as the MCPTTID leaf node containing the identified MCPTT ID is not empty, shall consider its value to be the KMS URI associated with the MCPTT ID; and
b) if the identified MCPTT ID is not found or if the /<x>/<x>/Common/PrivateCall/UserList/<x>/Entry/PrivateCallKMSURI leaf node is empty:
i) shall retrieve /<x>/OnNetwork/AppServerInfo/KMS leaf node (see the MCPTT UE initial configuration document in 3GPP TS 24.483 [45]); and
ii) shall consider the value of the /<x>/OnNetwork/AppServerInfo/KMS leaf node to be the KMS URI associated with the MCPTT ID. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.9 Location information | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.9.1 Location information for location reporting | This procedure is initiated by the MCPTT client when it is including location report information:
1) as part of a SIP request containing an MCPTT emergency alert; or
2) as part of a SIP request for a specified location trigger.
The MCPTT client:
1) if location information is being included as part of a SIP request for a specified location trigger criteria as configured in a <TriggeringCriteria> element and <EmergencyTriggeringCriteria> element contained in a <Configuration> element contained in an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3 as received in a SIP MESSAGE request by the procedures of clause 13.3.2:
a) shall include in the SIP request the specific location information as specified by the procedures of clause 13.3.4.2; and
b) shall skip the rest of the steps;
2) if location information is being included as part of a SIP request containing an MCPTT emergency alert:
a) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3 with a <Report> element included in the <location-info> root element;
b) shall set the <ReportType> element of the <Report> element to a value of "Emergency";
c) if the MCPTT client has been configured with an <EmergencyLocationInformation> element contained in a <Configuration> element contained in an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3 and received in a SIP MESSAGE request by the procedures of clause 13.3.2;
i) shall populate the <CurrentLocation> element of the <Report> element as indicated by the <EmergencyLocationInformation> element contained in the <Configuration> element contained in an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3 and previously received by the procedures of clause 13.3.2; and
ii) shall skip the rest of the steps; and
d) if the MCPTT client has not been configured with an <EmergencyLocationInformation> element contained in a <Configuration> element contained in an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3 and received in a SIP MESSAGE request by the procedures of clause 13.3.2:
i) shall include in the <CurrentLocation> element of the <Report> element of the application/vnd.3gpp.mcptt-location-info+xml MIME body a <CurrentCoordinate> element populated as specified in Annex F.3.3.
NOTE: According to local policy, additional location information elements specified in Annex F.3.3 can be included in the <CurrentLocation> element in the event that no <EmergencyLocationInformation> element was previously received. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.2.10 Support for multiplexing | If multiplexing is supported the SSRC of the RTCP header is used to enable multiplexing of media plane control channels for different communications over the same IP address and port. The SSRCs to be used in the RTCP messages over the media plane control channel for one communication are allocated at session establishment by each receiving entity.
If multiplexing is supported the SSRC of the RTP header is used to enable multiplexing of media streams for different communications over the same IP address and port. The SSRCs to be used in the RTP messages over the media stream for one communication are allocated in floor control server and exchange with the floor control protocol.
The floor control server shall generate globally unique SSRC to avoid collision of SSRC.
NOTE: If SSRC collision is detected by the MCPTT client, it will not be possible to determine the source of the media streams during one transmission (i.e. one talk burst) for a MCPTT client. It is up to the MCPTT client implementation on how to handle such SSRC collision.
Before the useage of multiplexing, the MCPTT client, the participating MCPTT function, the controlling MCPTT function and the non-controlling MCPTT function shall determine that both endpoints of a session support multiplexing.
The participating MCPTT function may determine the MCPTT client's support of multiplexing from the <multiplex-support> element of the MCPTT client poc-settings.
The MCPTT client, the participating MCPTT function, the controlling MCPTT function and the non-controlling MCPTT function may determine the support for multiplexing of another entity based on the presence of "mc_floor_ssrc" fmtp attribute in the SDP offere/answer, according to 3GPP TS 24.380 [5], sub clause 14.4. The participating MCPTT function, the controlling MCPTT function and the non-controlling MCPTT function may determine the support for multiplexing in another MCPTT server function based on local configuration, which is outside the scope of the present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3 MCPTT server procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.1 Distinction of requests sent to the MCPTT server | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.1.1 SIP INVITE request | The MCPTT server needs to distinguish between the following initial SIP INVITE requests for originations and terminations:
- SIP INVITE requests routed to the participating MCPTT function with the Request-URI set to a public service identity of the participating MCPTT function that identifies the pre-established session set-up. Such requests are known as "SIP INVITE request for establishing a pre-established session" in the procedures in the present document;
- SIP INVITE requests routed to the participating MCPTT function and the Request-URI is set to a public service identity of the participating MCPTT function that does not identify the pre-established session set-up. Such requests are known as "SIP INVITE request for originating participating MCPTT function" in the procedures in the present document;
- SIP INVITE requests routed to the participating MCPTT function and the Request-URI contains a PSI of the terminating participating MCPTT function. Such requests are known as "SIP INVITE request for terminating participating MCPTT function" in the procedures in the present document;
- SIP INVITE requests routed to the controlling MCPTT function, the Request-URI is set to a public service identity for MCPTT private call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCPTT function of a private call" in the procedures in the present document;
- SIP INVITE requests routed to the controlling MCPTT function, the Request-URI is set to a public service identity serving an MCPTT group and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCPTT function of an MCPTT group" in the procedures in the present document;
- SIP INVITE requests routed to the non-controlling MCPTT function of an MCPTT group, the Request-URI is set to a public service identity serving an MCPTT group and the Contact header field contains the isfocus media feature tag specified in IETF RFC 3840 [16]; Such requests are known as "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" in the procedures in the present document;
- SIP INVITE requests routed to the non-controlling MCPTT function of an MCPTT group, the Request-URI is set to a public service identity serving an MCPTT group and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]; Such requests are known as "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" in the procedures in the present document;
- SIP INVITE requests routed to the controlling MCPTT function, the Request-URI is set to a public service identity for first-to-answer call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCPTT function of a first-to-answer call" in the procedures in the present document; and
- SIP INVITE requests routed to the controlling MCPTT function, the Request-URI is set to a public service identity for MCPTT ambient listening call and the Contact header field does not contain the isfocus media feature tag specified in IETF RFC 3840 [16]. Such requests are known as "SIP INVITE request for controlling MCPTT function of an ambient listening call" in the procedures in the present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.1.2 SIP REFER request | The MCPTT server needs to distinguish between the following initial SIP REFER request for originations and terminations:
- SIP REFER requests routed to the participating MCPTT function with the Request-URI set to a public service identity identifying the pre-established session on the participating MCPTT function. Such requests are known as "SIP REFER request for a pre-established session" in the procedures in the present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.1.3 SIP MESSAGE request | The MCPTT server needs to distinguish between the following SIP MESSAGE request for originations and terminations:
- SIP MESSAGE requests routed to the participating MCPTT function with the Request-URI set to the MBMS public service identity of the participating MCPTT function. Such requests are known as "SIP MESSAGE request for an MBMS listening status update" in the procedures in the present document;
- SIP MESSAGE request routed to the participating MCPTT function containing a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml" and including an XML body containing a Location root element containing a Report element. Such requests are known as "SIP MESSAGE request for location reporting" in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <emergency-ind> element or an <alert-ind> element. Such requests are known as "SIP MESSAGE request for emergency notification for originating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <emergency-ind> element or an <alert-ind> element. Such requests are known as "SIP MESSAGE request for emergency notification for terminating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <emergency-ind> element or an <alert-ind> element. Such requests are known as "SIP MESSAGE request for emergency notification for controlling MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "private-call-call-back-request" or "private-call-call-back-cancel-request", or with the <response-type> element set to a value of "private-call-call-back-response" or "private-call-call-back-cancel-response". Such requests are known as "SIP MESSAGE request for private call call-back for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "private-call-call-back-request" or "private-call-call-back-cancel-request", or with the <response-type> element set to a value of "private-call-call-back-response" or "private-call-call-back-cancel-response". Such requests are known as "SIP MESSAGE request for private call call-back for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "private-call-call-back-request". Such requests are known as "SIP MESSAGE request for private call call-back request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "private-call-call-back-cancel-request". Such requests are known as "SIP MESSAGE request for private call call-back cancel request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "private-call-call-back-response" or "private-call-call-back-cancel-response". Such requests are known as "SIP MESSAGE request for private call call-back responses for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "group-selection-change-request" or with the <response-type> element set to a value of "group-selection-change-response". Such requests are known as "SIP MESSAGE request for group-selection-change for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "group-selection-change-request" or with the <response-type> element set to a value of "group-selection-change -response". Such requests are known as "SIP MESSAGE request for group-selection-change for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "group-selection-change-request". Such requests are known as "SIP MESSAGE request for group selection change request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "group-selection-change-response". Such requests are known as "SIP MESSAGE request for group selection change response for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-group-call-request" or with the <response-type> element set to a value of "remotely-initiated-group-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated group call for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-group-call-request" or with the <response-type> element set to a value of "remotely-initiated-group-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated group call for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-group-call-request". Such requests are known as "SIP MESSAGE request for remotely initiated group call request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "remotely-initiated-group-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated group call response for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-private-call-request" or with the <response-type> element set to a value of "remotely-initiated-private-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated private call for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-private-call-request" or with the <response-type> element set to a value of "remotely-initiated-private-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated private call for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "remotely-initiated-private-call-request". Such requests are known as "SIP MESSAGE request for remotely initiated private call request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "remotely-initiated-private-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated private call response for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function and the Request-URI is set to a public service identity of the originating participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <groups-for-regroup> element. Such requests are known as "SIP MESSAGE request to the originating participating MCPTT function to request creation of a group regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function and the Request-URI is set to a public service identity of the originating participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <users-for-regroup> element. Such requests are known as "SIP MESSAGE request to the originating participating MCPTT function to request creation of a user regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function and the Request-URI is set to a public service identity of the originating participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body and a <regroup-action> element set to "remove". Such requests are known as "SIP MESSAGE request to the originating participating MCPTT function to remove a regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function and the Request-URI is set to a public service identity of the participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <groups-for-regroup> element. Such requests are known as "SIP MESSAGE request to the terminating participating MCPTT function to create a group regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function and the Request-URI is set to a public service identity of the terminating participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create"and a non-empty <users-for-regroup> element. Such requests are known as "SIP MESSAGE request to the terminating participating MCPTT function to create a user regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function and the Request-URI is set to a public service identity of the terminating participating MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-info+xml MIME body and a <regroup-action> element set to "remove". Such requests are known as "SIP MESSAGE request to the terminating participating MCPTT function to remove a regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function and the Request-URI is set to a public service identity of the controlling MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <groups-for-regroup> element. Such requests are known as "SIP MESSAGE request to the controlling MCPTT function to request creation of a group regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function and the Request-URI is set to a public service identity of the controlling MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <users-for-regroup> element. Such requests are known as "SIP MESSAGE request to the controlling MCPTT function to request creation of a user regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function and the Request-URI is set to a public service identity of the controlling MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup +xml MIME body and a <regroup-action> element set to "remove". Such requests are known as "SIP MESSAGE request to the controlling MCPTT function to remove a regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to a non-controlling MCPTT function and the Request-URI is set to a public service identity of the non-controlling MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body, a <regroup-action> element set to "create", and a non-empty <groups-for-regroup> element. Such requests are known as "SIP MESSAGE request to a non-controlling MCPTT function to request creation of a group regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the non-controlling MCPTT function and the Request-URI is set to a public service identity of the non-controlling MCPTT function that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body and a <regroup-action> element set to "remove". Such requests are known as "SIP MESSAGE request to the non-controlling MCPTT function to remove a group regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "transfer-private-call-request" or with the <response-type> element set to a value of "transfer-private-call-response". Such requests are known as "SIP MESSAGE request for transfer private call for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "transfer-private-call-request" or with the <response-type> element set to a value of "transfer-private-call-response". Such requests are known as "SIP MESSAGE request for transfer private call for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "transfer-private-call-request". Such requests are known as "SIP MESSAGE request for transfer private call request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "transfer-private-call-response". Such requests are known as "SIP MESSAGE request for transfer private call response for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing an <mcpttinfo> root element with an <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "forward-private-call-request" or with the <response-type> element set to a value of "forward-private-call-response". Such requests are known as "SIP MESSAGE request for forwarding private call for originating participating MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing an <mcpttinfo> root element with an <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "forward-private-call-request" or with the <response-type> element set to a value of "forward-private-call-response". Such requests are known as "SIP MESSAGE request for forwarding private call for terminating participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing an <mcpttinfo> root element with an <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "forward-private-call-request". Such requests are known as "SIP MESSAGE request for forwarding private call request for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing an <mcpttinfo> root element with an <mcptt-Params> element containing an <anyExt> element with the <response-type> element set to a value of "forward-private-call-response". Such requests are known as "SIP MESSAGE request for forwarding private call response for controlling MCPTT function";
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "fa-group-binding-req". Such requests are known as "SIP MESSAGE request for binding of a functional alias with the MCPTT group(s) for the MCPTT user for originating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "fa-group-binding-req". Such requests are known as "SIP MESSAGE request for binding of a functional alias with the MCPTT group(s) for the MCPTT user for controlling MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests which is routed to the primary MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function in the primary MCPTT system and includes an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing a <req-type> element set to "migration-service-authorization-request". Such requests are known as "SIP MESSAGE request for migration service authorization request" in the procedures in the present document;
- SIP MESSAGE requests which is routed to the partner MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function in the partner MCPTT system and includes an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing a <resp-type> element set to "migration-service-authorization-response". Such requests are known as "SIP MESSAGE request for migration service authorization response" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function in the primary MCPTT system with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <req-type> element set to a value of "mc-service-authorisation-notify-request". Such requests are known as "SIP MESSAGE request to notify about MCPTT service authorisation result for terminating participating MCPTT function in primary MCPTT system";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <req-type> element set to a value of "get-userlist-adhoc-group-call-request". Such requests are known as "SIP MESSAGE request to get userlist for adhoc group call request for participating MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <resp-type> element set to a value of "get-userlist-adhoc-group-call-response". Such requests are known as "SIP MESSAGE request to get userlist for adhoc group call response for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <req-type> element set to a value of "adhoc-group-call-add-participants-request". Such requests are known as "SIP MESSAGE request to add user to adhoc group call notification for controlling MCPTT function";
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <req-type> element set to a value of "adhoc-group-call-remove-participants-request". Such requests are known as "SIP MESSAGE request to remove user from adhoc group call notification for controlling MCPTT function";
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element with a <mcptt-Params> element containing an <anyExt> element with the <req-type> element set to a value of "adhoc-group-call-release-notification-request". Such requests are known as "SIP MESSAGE request to stop determining the participant list for participating MCPTT function";
- SIP MESSAGE requests which is routed to the partner MCPTT function and includes an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing a <req-type> element set to "migration-service-deauthorization-notification". Such requests are known as "SIP MESSAGE request for migration service deauthorization notification" in the procedures in the present document;
SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element containing an <adhoc-alert-ind> element. Such requests are known as "SIP MESSAGE request for adhoc emergency notification for originating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element containing an <adhoc-alert-ind> element. Such requests are known as "SIP MESSAGE request for adhoc emergency notification for terminating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <adhoc-alert-ind> element. Such requests are known as "SIP MESSAGE request for adhoc emergency origination notification for controlling MCPTT function" in the procedures in the present document; and
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <imminentperil-ind> element. Such requests are known as "SIP MESSAGE request for imminent peril state change request for originating participating MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the originating participating MCPTT function with the Request-URI set to the public service identity of the originating participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element containing an <adhoc-alert-ind-rcvd> element. Such requests are known as "SIP MESSAGE request indicating successful delivery of adhoc group emergency notification of originating MCPTT client" in the procedures in the present document;
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element containing an <adhoc-alert-ind> element. Such requests are known as "SIP MESSAGE request for adhoc emergency notification for controlling MCPTT function" in the procedures in the present document;
- SIP MESSAGE requests routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <imminentperil-ind> element. Such requests are known as "SIP MESSAGE request for imminent peril state change notification for terminating participating MCPTT function" in the procedures in the present document; and
- SIP MESSAGE requests routed to the controlling MCPTT function with the Request-URI set to the public service identity of the controlling MCPTT function and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <imminentperil-ind> element. Such requests are known as "SIP MESSAGE request for imminent peril state change request for controlling MCPTT function" in the procedures in the present document.
If a SIP MESSAGE request is received at an MCPTT server that is not in accordance with the SIP MESSAGE requests listed above, then the MCPTT server shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response.
If a SIP MESSAGE request is received at an MCPTT server that is not in accordance with the SIP MESSAGE requests listed above, then the MCPTT server shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.1.4 SIP SUBSCRIBE request | The MCPTT server needs to distinguish between the following SIP SUBSCRIBE request for originations and terminations:
- SIP SUBSCRIBE requests routed to the participating MCPTT function with the Request-URI set to the MCPTT session identity identifying the participating MCPTT function and the Event header field set to "conference". Such requests are known as "SIP SUBSCRIBE request for conference event status subscription in the participating function" in the procedures in the present document;
- SIP SUBSCRIBE requests routed to the controlling MCPTT function with the Request-URI set to the MCPTT session identity identifying the controlling MCPTT function and containing an Event header field set to "conference". Such requests are known as "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" in the procedures in the present document; and
- SIP SUBSCRIBE requests routed to the non-controlling MCPTT function with the Request-URI set to the MCPTT session identity identifying the non-controlling MCPTT function and containing an Event header field set to "conference". Such requests are known as "SIP SUBSCRIBE request for conference event status subscription in the non-controlling MCPTT function" in the procedures in the present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2 Participating MCPTT Function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1 Requests initiated by the served MCPTT user | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.1 SDP offer generation | 6.3.2.1.1.1 On-demand session
This clause is referenced from other clauses.
The SDP offer is generated based on the received SDP offer. The SDP offer generated by the participating MCPTT function:
1) shall contain only one SDP media-level section for MCPTT speech as contained in the received SDP offer; and
2) shall contain one SDP media-level section for media plane control messages, if present in the received SDP offer.
When composing the SDP offer according to 3GPP TS 24.229 [4], the participating MCPTT function:
1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the participating MCPTT function, if required;
NOTE 1: Requirements can exist for the participating MCPTT function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist.
2) shall replace the IP address and port number for the offered media plane control channel, if any, in the received SDP offer with the IP address and port number of the participating MCPTT function;
3) shall replace the mc_floor_ssrc 'fmtp' attribute for the offered media plane control channel, if any, in the received SDP offer with the RTCP SSRC that the participating MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the answerer (i.e. MCPTT client or controlling MCPTT function) in the floor control messages sent to the participating MCPTT function for this session; and
NOTE 2: The participating MCPTT function will receive in the SDP answer the RTP SSRC it will have to use in the floor control message it will send to the answerer in this session.
NOTE 3: If the participating MCPTT function and the controlling MCPTT function or the participating MCPTT function and the non-controlling MCPTT function are in the same MCPTT server, and the participating MCPTT function does not have a dedicated IP address or a dedicated port number for media plane control channel or media stream, the replacement of the IP address or the port number is omitted.
4) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value, if present in the received SDP offer.
6.3.2.1.1.2 Pre-established session
This clause is referenced from other clauses.
When composing an SDP offer according to 3GPP TS 24.229 [4], the participating MCPTT function:
1) shall use the IP address of the participating MCPTT function for MCPTT speech from the SDP negotiated during the pre-established session establishment;
2) shall use the IP address of the participating MCPTT function for the offered media plane control channel from the SDP negotiated during the pre-established session establishment, if present in the received SDP offer;
3) shall contain only one SDP media-level section for MCPTT speech obtained from the SDP negotiated during the pre-established session establishment consisting of:
a) the port number for the MCPTT speech; and
b) the codec(s), media parameters and attributes as in the SDP negotiated during the pre-established session establishment;
4) shall include the media-level section of the offered media plane control channel from the SDP negotiated during the pre-established session establishment, if any media plane control channel is offered consisting of:
a) the media plane control channel parameters as in the SDP negotiated during the pre-established session establishment;
b) the port number for the selected media plane control channel selected as specified in 3GPP TS 24.229 [4]; and
c) the mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14 for the selected media plane control channel with the RTCP SSRC that the participating MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the answerer in the floor control messages sent to the participating MCPTT function for this session; and
NOTE: The participating MCPTT function will receive in the SDP answer the RTP SSRC it will have to use in the floor control message it will send to the answerer in this session.
5) shall contain an "a=key-mgmt" attribute field with a "mikey" attribute value if present in the received SDP offer. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.2 SDP answer generation | 6.3.2.1.2.1 On-demand session
When composing the SDP answer according to 3GPP TS 24.229 [4], the participating MCPTT function:
1) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCPTT function, for the accepted media stream in the received SDP offer, if required;
NOTE 1: Requirements can exist for the participating MCPTT function to be always included in the path of the offered media stream, for example: for the support of features such as MBMS, lawful interception and recording. Other examples can exist.
2) shall replace the IP address and port number in the received SDP answer with the IP address and port number of the participating MCPTT function, for the accepted media plane control channel, if present in the received SDP offer; and
3) shall replace the mc_floor_ssrc 'fmtp' attribute for the accepted media plane control channel, if present in the received SDP answer with the RTCP SSRC that the participating MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the offerer (i.e. MCPTT client or controlling MCPTT function) in the floor control messages sent to the participating MCPTT function for this session.
NOTE 2: The participating MCPTT function has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the offerer in this session.
NOTE 3: If the participating MCPTT function and the controlling MCPTT function or the participating MCPTT function and the non-controlling MCPTT function are in the same MCPTT server, and the participating MCPTT function does not have a dedicated IP address or a dedicated port number for media plane control channel or media stream, the replacement of the IP address or the port number is omitted.
6.3.2.1.2.2 Pre-established session establishment
When composing the SDP answer according to 3GPP TS 24.229 [4], the participating MCPTT function:
1. shall set the IP address and port number to those of the participating MCPTT function for each accepted media stream from the list contained in the received SDP offer and for each accepted media stream in the received SDP offer;
2. shall set the IP address,and port number to those of the participating MCPTT function, for the accepted media plane control channel, if present in the received SDP offer; and
3) shall set the mc_floor_ssrc 'fmtp' attribute for the accepted media plane control channel, if present in the received SDP offer, with the RTCP SSRC that the participating MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the offerer in the floor control messages sent to participating MCPTT function for this session.
NOTE: The participating MCPTT function has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the offerer in this session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.3 Sending an INVITE request on receipt of an INVITE request | This clause is referenced from other procedures.
When generating an initial SIP INVITE request according to 3GPP TS 24.229 [4], on receipt of an incoming SIP INVITE request, the participating MCPTT function:
1) shall include in the SIP INVITE 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] if included in the incoming SIP INVITE request;
2) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
3) shall include the option tag "timer" in the Supported header field;
4) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to the public service identity of the originating participating MCPTT function;
5) shall include the g.3gpp.mcptt media feature tag into the Contact header field of the outgoing SIP INVITE request;
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request;
7) if the incoming SIP INVITE request contained an application/resource-lists+xml MIME body, shall copy the application/resource-lists+xml MIME body, according to rules and procedures of IETF RFC 5366 [20];
8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request to the outgoing SIP INVITE request; and
9) if, according to clause 6.4, the SIP INVITE request is regarded as being not received with an implicit floor request, then:
a) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
b) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the SIP INVITE request into the outgoing SIP INVITE. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.4 Sending an INVITE request on receipt of a REFER request | This clause is referenced from other procedures.
When generating an initial SIP INVITE request according to 3GPP TS 24.229 [4], on receipt of an incoming SIP REFER request, the participating MCPTT function:
1) shall include in the SIP INVITE request all header fields included in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field in the incoming SIP REFER request;
2) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
3) shall include the option tag "timer" in the Supported header field;
4) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to the public service identity of the participating MCPTT function;
5) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" into the Contact header field of the outgoing SIP INVITE request;
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request;
7) shall include in the SIP INVITE request the option tag "tdialog" in a Supported header field according to the rules and procedures of IETF RFC 4538 [23];
8) shall include in the SIP INVITE request an SDP offer as specified in clause 6.3.2.1.1.2 based upon:
a) the SDP negotiated during the pre-established session establishment and any subsequent pre-established session modification;
b) the SDP offer (if any) included in the hname "body" parameter in the headers portion of the SIP URI contained in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists MIME body, referenced by the "cid" URL in the Refer-To header field in the incoming SIP REFER request for a pre-established session; and
c) the SDP offer (if any) included in an application/sdp MIME body of the incoming SIP REFER request for adhoc group call for a pre-established session, according to the conditions specified in clause 6.4;
9) shall determine if the SIP REFER request is regarded as being received with an implicit floor request;
a) if according to clause 6.4, the SIP REFER request is regarded as being received with an implicit floor request, the participating MCPTT function shall include the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer of the SIP INVITE request; and
b) if, according to clause 6.4, the SIP REFER request is regarded as being not received with an implicit floor request, the participating MCPTT function shall not include the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer of the SIP INVITE request;
10) shall determine if the SIP REFER request is regarded as being received with an implicit request to grant the floor to the terminating MCPTT client;
a) if according to clause 6.4, the SIP REFER request is regarded as being received with an implicit request to grant the floor to the terminating MCPTT client, the participating MCPTT function shall include the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer of the SIP INVITE request; and
b) if, according to clause 6.4, the SIP REFER request is regarded as being not received with an implicit request to grant the floor to the terminating MCPTT client, the participating MCPTT function shall not include the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer of the SIP INVITE request;
11) shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP INVITE request;
a) from the hname "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field of the SIP REFER request; or
b) from MIME body part of the incoming SIP REFER request for adhoc group call;
11A) if the application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP INVITE request contains a <functional-alias-URI> element, shall check the status of the functional alias. If the status is not active, then the participating MCPTT function shall remove the <functional-alias-URI> element from the application/vnd.3gpp.mcptt-info+xml MIME body;
12) shall include the <mcptt-calling-user-id> element set to the MCPTT ID of the calling user in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request;
13) shall copy the application/resource-lists+xml MIME body to the SIP INVITE request:
a) without the hname "body" parameter (if included) in the headers portion of the SIP URI contained in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body; or
b) from MIME body part of the incoming SIP REFER request for adhoc group call;
14) if, according to clause 6.4, the SIP REFER request is regarded as being not received with an implicit floor request, then:
a) if the incoming SIP REFER request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
b) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the SIP REFER request into the outgoing SIP INVITE. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.5 Response to an INVITE request | 6.3.2.1.5.1 Provisional responses
NOTE: This clause is referenced from other procedures
When sending SIP provisional responses other than the SIP 100 (Trying) response, the participating MCPTT function shall generate a SIP provisional response according to 3GPP TS 24.229 [4] and:
1) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
c) the isfocus media feature tag; and
d) an MCPTT session identity mapped to the MCPTT session identity if provided in the Contact header field of the incoming provisional response;
2) shall include the "norefersub" option tag in a Supported header field in accordance with 3GPP TS 24.229 [4];
3) may include a Resource-Share header field in accordance with clause 5.7.1.20.2 in 3GPP TS 24.229 [4]; and
4) if the incoming SIP provisional response contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP provisional response.
6.3.2.1.5.2 Final response
This clause is referenced from other procedures.
When sending SIP 200 (OK) responses, the participating MCPTT function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [4] and:
1) shall include the option tag "timer" in a Require header field;
2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7], "UAS Behavior". If the "refresher" parameter is not included in the received request, the "refresher" parameter in the Session-Expires header field shall be set to "uac";
3) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
c) the isfocus media feature tag;
4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23];
5) shall include the option tag "norefersub" in a Supported header field according to rules and procedures of IETF RFC 4488 [22];
6) may include a Resource-Share header field in accordance with clause 5.7.1.20.2 in 3GPP TS 24.229 [4]; and
7) if the incoming SIP 200 (OK) response contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP 200 (OK) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.6 Sending a SIP BYE request on receipt of a SIP BYE request | Upon receiving a SIP BYE request from the MCPTT client, the participating MCPTT function:
1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5];
2) shall generate a SIP BYE request as specified in 3GPP TS 24.229 [4];
3) shall set the Request-URI to the MCPTT session identity as included in the received SIP BYE request;
4) shall include a P-Asserted-Identity header field in the outgoing SIP BYE request set to the public service identity of the participating MCPTT function;
5) if the received SIP BYE request contains an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body into the outgoing SIP BYE request; and
6) shall send the SIP BYE request toward the controlling MCPTT function, according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request the terminating MCPTT function shall forward a SIP 200 (OK) response to the MCPTT client and shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5] for releasing media plane resources associated with the SIP session with the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.7 Sending a SIP BYE request on receipt of a SIP REFER request | Upon receiving a SIP REFER request with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field from the MCPTT client, the participating MCPTT function:
1) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP REFER request;
2) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID shall reject the SIP REFER request with a SIP 403 (Forbidden) 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 SIP REFER request contained a Refer-Sub header field containing "false" value and a Supported header field containing "norefersub" value, shall handle the SIP REFER request as specified in 3GPP TS 24.229 [4], IETF RFC 3515 [25] as updated by IETF RFC 6665 [26], and IETF RFC 4488 [22] without establishing an implicit subscription;
4) shall generate a SIP 200 (OK) response to the SIP REFER request, and in the SIP 200 (OK) response:
a) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22]; and
b) shall check the presence of the Refer-Sub header field of the SIP REFER request and if it is present and set to the value "false" shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
NOTE: In accordance with IETF RFC 4488 [22], the participating MCPTT function inserts the Refer-Sub header field containing the value "false" in the SIP 200 (OK) response to the SIP REFER request to indicate that it has not created an implicit subscription.
5) shall send the SIP 200 (OK) response to the SIP REFER request towards MCPTT client according to 3GPP TS 24.229 [4];
6) shall generate a SIP BYE request, and in the SIP BYE request:
a) shall set the Request-URI to the MCPTT session identity which was included at the Refer-To header field of the received REFER request; and
b) shall include a P-Asserted-Identity header field in the outgoing SIP BYE request set to the public service identity of the participating MCPTT function; and
7) shall send the SIP BYE request toward the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCPTT function shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5] for releasing media plane resources associated with the SIP session with the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.8 Priority call conditions | 6.3.2.1.8.0 General
The clauses of the parent clause contain common procedures to be used for MCPTT emergency group calls and MCPTT imminent peril group calls.
6.3.2.1.8.1 Determining authorisation for originating a priority group call
When the participating MCPTT function receives a request from the MCPTT client to originate an MCPTT emergency group call and needs to determine if the request is an authorised request for an MCPTT emergency call, the participating MCPTT function shall check the following:
1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" and:
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the participating MCPTT function shall consider the MCPTT emergency group call request to be an authorised request for an MCPTT emergency group call;
In all other cases, the participating MCPTT function shall consider the request to originate an MCPTT emergency group call to be an unauthorised request to originate an MCPTT emergency group call.
When the participating MCPTT function receives a request from the MCPTT client to originate an MCPTT imminent peril group call and needs to determine if the request is an authorised request for an MCPTT imminent peril group call the participating MCPTT function shall check the following:
1) if the <allow-imminent-peril-call> element of <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
a) if the "entry-info" attribute of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the participating MCPTT function shall consider the MCPTT imminent peril group call request to be an authorised request for an MCPTT emergency group call;
In all other cases, the participating MCPTT function shall consider the request to originate an MCPTT imminent peril group call to be an unauthorised request to originate an MCPTT imminent peril call.
6.3.2.1.8.2 Determining authorisation for initiating or cancelling an MCPTT emergency alert
If the participating MCPTT function receives a SIP request from the MCPTT client including a request for an MCPTT emergency alert and:
1) if the <allow-activate-emergency-alert> element of the <actions> element of the <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
2) if the "entry-info" attribute of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of:
a) "DedicatedGroup", and if the <uri-entry> element of the <entry> element of the <EmergencyAlert> element of the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the MCPTT group identity of the MCPTT group targeted by the calling MCPTT user; or
b) "UseCurrentlySelectedGroup" and the <allow-MCPTT-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the <list-service> element of the group document identified by the MCPTT group identity targeted for the emergency alert is set to a value of "true" as specified in 3GPP TS 24.481 [31].
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert.
If the participating MCPTT function receives a SIP request from the MCPTT client including a request to cancel an MCPTT emergency alert to an MCPTT group, and if the <allow-cancel-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request to cancel an MCPTT emergency alert.
6.3.2.1.8.3 Validate priority request parameters
This clause is referenced from other procedures.
To validate the combinations of <emergency-ind>, <imminentperil-ind> and <alert-ind> which are received in SIP requests, the participating MCPTT function shall follow the procedures specified in clause 6.3.3.1.17.
6.3.2.1.8.4 Retrieving Resource-Priority header field values
This clause is referenced from other procedures.
The participating MCPTT function shall follow the procedures specified in clause 6.3.3.1.19 with the clarification that references in that procedure to the controlling MCPTT function should be replaced with references to the participating MCPTT function.
6.3.2.1.8.5 Generating a SIP re-INVITE request for priority group call origination within a pre-established session
This clause is referenced from other procedures.
Upon receipt of a SIP 2xx response which does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149" to a SIP INVITE request sent to the controlling MCPTT function which contained a Resource-Priority header field populated for an MCPTT emergency group call or MCPTT imminent peril group call as specified in clause 6.3.2.1.8.4, the participating MCPTT function:
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session;
2) shall include in the SIP re-INVITE request an SDP offer based upon the previously negotiated SDP for the pre-established session;
3) shall include in the SIP re-INVITE request a Resource-Priority header field with the contents set as in the Resource-Priority header field included in the SIP INVITE request sent to the controlling MCPTT function; and
4) shall skip the remaining steps.
NOTE 1: This is the case where the MCPTT client's previously sent SIP REFER request was either 1) a request for an MCPTT emergency group call or MCPTT imminent peril group call or 2), was not a request for an MCPTT emergency group call or MCPTT imminent peril group call but targeted an MCPTT group which is in an in-progress emergency group state or in-progress imminent peril group state. In either case no SIP INFO pending warning was expected or received.
Upon receipt of a SIP 2xx response from the controlling MCPTT function to a request for an MCPTT emergency call or MCPTT imminent peril call, that contains a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", the participating MCPTT function shall wait for the receipt of a SIP INFO request from the controlling MCPTT function.
Upon receipt of a SIP INFO request from the controlling MCPTT function within the dialog of the SIP INVITE request for an MCPTT emergency call or MCPTT imminent peril call, the participating MCPTT function:
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session;
2) shall include in the SIP re-INVITE request an SDP offer based upon the previously negotiated SDP for the pre-established session;
3) shall include in the SIP re-INVITE request a Resource-Priority header field with the contents set as in the Resource-Priority header field included in shall include a Resource-Priority header field with the contents set as in the SIP INVITE request sent to the controlling MCPTT function; and
4) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body containing:
a) an <emergency-ind> element if included in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP INFO request, set to the value of the <emergency-ind> in the SIP INFO request;
b) an <alert-ind> element if included in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP INFO request, set to the value of the <alert-ind> in the SIP INFO request; and
c) an <imminentperil-ind> element if included in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP INFO request, set to the value of the <imminentperil-ind> in the SIP INFO request.
NOTE 2: This is the case where the MCPTT client's previously sent SIP REFER request was a request for an MCPTT emergency group call or an MCPTT imminent peril group call and a SIP INFO request was received in the dialog with the controlling MCPTT function for the MCPTT emergency group call or MCPTT imminent peril group call.
6.3.2.1.8.6 Generating a SIP re-INVITE request for emergency private call origination within a pre-established session
This clause is referenced from other procedures.
Upon receipt of a SIP 2xx response which does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149" to a SIP-INVITE request sent to the controlling MCPTT function which contained a Resource-Priority header field populated for an MCPTT emergency private call as specified in clause 6.3.2.1.8.4, the participating MCPTT function:
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session;
2) shall include in the SIP re-INVITE request an SDP offer:
a) based upon the previously negotiated SDP for the pre-established session; and
b) if the received SIP 2xx response was in response to a request for a first-to-answer call and the SDP answer contained an a=key-mgmt attribute, shall include the a=key-mgmt attribute and its value in the SDP offer as specified in IETF RFC 4567 [47];
3) shall include in the SIP re-INVITE request a Resource-Priority header field with the contents set as in the Resource-Priority header field included in the SIP INVITE request sent to the controlling MCPTT function; and
4) shall skip the remaining steps.
NOTE 1: This is the case where the MCPTT client's previously sent SIP REFER request was either 1) a request for an MCPTT emergency private call or 2), was not a request for an MCPTT emergency private call but MCPTT emergency private priority state was already set to "in-progress". In either case no SIP INFO pending warning was expected or received.
Upon receipt of a SIP 2xx response from the controlling MCPTT function to a request for an MCPTT emergency private call, that contains a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", the participating MCPTT function shall wait for the receipt of a SIP INFO request from the controlling MCPTT function.
Upon receipt of a SIP INFO request from the controlling MCPTT function within the dialog of the SIP INVITE request for an MCPTT emergency private call, the participating MCPTT function :
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session;
2) shall include in the SIP re-INVITE request an SDP offer:
a) based upon the previously negotiated SDP for the pre-established session; and
b) if the received SIP 2xx response was in response to a request for a first-to-answer call and the SDP answer contained an a=key-mgmt attribute, shall include the a=key-mgmt attribute and its value in the SDP offer as specified in IETF RFC 4567 [47];
3) shall include in the SIP re-INVITE request a Resource-Priority header field with the contents set as in the Resource-Priority header field included in the SIP INVITE request sent to the controlling MCPTT function; and
4) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body containing:
a) an <alert-ind> element if included in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP INFO request, set to the value of the <alert-ind> in the SIP INFO request.
NOTE 2: This is the case where the MCPTT client's previously sent SIP REFER request was a request for an MCPTT emergency private call and a SIP INFO request was received in the dialog with the controlling MCPTT function for the MCPTT emergency private call.
6.3.2.1.8.7 Generating a SIP re-INVITE request for first-to-answer call origination within a pre-established session
This clause is referenced from other procedures.
Upon receipt of a SIP 2xx response to a SIP INVITE request for a first-to-answer call which contains an SDP answer including an a=key-mgmt attribute, the participating MCPTT function:
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session; and
2) shall include in the SIP re-INVITE request an SDP offer:
a) based upon the previously negotiated SDP for the pre-established session; and
b) containing the a=key-mgmt attribute and value as received in the SDP answer in the SDP offer as specified in IETF RFC 4567 [47].
6.3.2.1.8.8 Determining authorisation for originating a priority adhoc group call
When the participating MCPTT function receives a request from the MCPTT client to originate an MCPTT emergency adhoc group call and needs to determine if the request is an authorised request for an MCPTT adhoc group emergency call, the participating MCPTT function shall check the following:
1) if the <allow-emergency-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", shall consider the MCPTT emergency adhoc group call request to be an authorised request for an MCPTT emergency adhoc group call.
In all other cases, the participating MCPTT function shall consider the request to originate an MCPTT emergency adhoc group call to be an unauthorised request to originate an MCPTT emergency adhoc group call.
When the participating MCPTT function receives a request from the MCPTT client to originate an MCPTT imminent peril adhoc group call and needs to determine if the request is an authorised request for an MCPTT imminent peril adhoc group call the participating MCPTT function shall check the following:
1) if the <allow-imminent-peril-adhoc-group-call> element of <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", shall consider the MCPTT imminent peril adhoc group call request to be an authorised request for an MCPTT imminent peril adhoc group call.
In all other cases, the participating MCPTT function shall consider the request to originate an MCPTT imminent peril adhoc group call to be an unauthorised request to originate an MCPTT imminent peril adhoc group call.
6.3.2.1.8.9 Validate adhoc group priority request parameters
This clause is referenced from other procedures.
To validate the combinations of <adhoc-emergency-ind>, and <imminentperil-ind> which are received in SIP requests, the participating MCPTT function shall follow the procedures specified in clause 6.3.3.1.25.
6.3.2.1.8.10 Generating a SIP re-INVITE request for priority adhoc group call origination within a pre-established session
This clause is referenced from other procedures.
Upon receipt of a SIP 2xx response which does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149" to a SIP INVITE request sent to the controlling MCPTT function which contained a Resource-Priority header field populated for an MCPTT emergency adhoc group call or MCPTT imminent peril adhoc group call as specified in clause 6.3.2.1.8.4, the participating MCPTT function:
1) shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] to be sent within the SIP dialog of the pre-established session;
2) shall include in the SIP re-INVITE request an SDP offer based upon the previously negotiated SDP for the pre-established session;
3) shall include in the SIP re-INVITE request a Resource-Priority header field with the contents set as in the Resource-Priority header field included in the SIP INVITE request sent to the controlling MCPTT function; and
4) shall skip the remaining steps. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.9 Generating a SIP re-INVITE request on receipt of a SIP re-INVITE request | This clause is referenced from other procedures.
When generating a SIP re-INVITE request according to 3GPP TS 24.229 [4] on receipt of an incoming SIP re-INVITE request, the participating MCPTT function:
1) if the incoming SIP re-INVITE request contained an application/resource-lists MIME body with the MCPTT ID of the invited MCPTT user, shall copy the application/resource-lists MIME body, according to rules and procedures of IETF RFC 5366 [20];
2) if the incoming SIP re-INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body; and
3) if the incoming SIP re-INVITE request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.1.10 Sending a SIP INVITE request towards the non-controlling MCPTT function | This clause is referenced from other procedures.
The participating MCPTT function shall generate a SIP INVITE request according to rules and procedures of 3GPP TS 24.229 [4].
The participating MCPTT function:
1) shall determine the public service identity of the non-controlling MCPTT function associated with the group identity of the constituent group contained in the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request. If the participating MCPTT function is unable to identify the non-controlling MCPTT function for the on demand prearranged group call, it shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text "142 unable to determine the controlling function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
NOTE 1: The public service identity can identify the non-controlling MCPTT function in the local MCPTT system or in an interconnected MCPTT system.
NOTE 2: If the non-controlling MCPTT function is in an interconnected 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 interconnected MCPTT system from the local MCPTT system.
NOTE 3: If the non-controlling MCPTT function is in an interconnected MCPTT system in a different trust domain, then the local MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the local MCPTT system to the interconnected MCPTT system
NOTE 4: How the participating MCPTT function determines the public service identity of the non-controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the interconnected MCPTT system is out of the scope of the present document.
NOTE 5: How the local MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
2) shall set the Request-URI of the generated SIP INVITE request to the public service identity determines in step 1;
3) shall include in the SIP INVITE 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] if included in the original incoming SIP INVITE or SIP REFER request from the MCPTT client;
4) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
5) shall include the option tag "timer" in the Supported header field;
6) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to the public service identity of the participating MCPTT function;
7) shall include the g.3gpp.mcptt media feature tag into the Contact header field of the outgoing SIP INVITE request;
8) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the outgoing SIP INVITE request;
9) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request;
10) if a SIP INVITE request was received from the client containing an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body of the original incoming SIP INVITE request to the outgoing SIP INVITE request;
11) if a SIP REFER request was received from the client with a "cid" URL pointing to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20] containing SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body and the SIP URI contains an hname "body" parameter in the headers portion of the SIP URI containing an application/vnd.3gpp.mcptt-info MIME body, shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP REFER request to the outgoing SIP INVITE request; and
12) shall set the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user that was determined when the participating MCPTT function received the SIP INVITE request or SIP REFER request from the client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2 Requests terminated to the served MCPTT user | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.1 SDP offer generation | The participating MCPTT function shall follow the procedures in clause 6.3.2.1.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.2 SDP answer generation | 6.3.2.2.2.1 On-demand session
The participating MCPTT function shall follow the procedures in clause 6.3.2.1.2.1.
6.3.2.2.2.2 Pre-established session
When composing an SDP answer according to 3GPP TS 24.229 [4], the participating MCPTT function:
1) shall set the IP address of the participating MCPTT function for the accepted MCPTT speech media stream from the received SDP offer, which was also negotiated during the pre-established session establishment;
2) shall set the IP address of the participating MCPTT function for the accepted media-floor control entity from the received SDP offer, which was also negotiated during the pre-established session establishment, if present in the received SDP offer;
3) shall include the media-level section for the accepted MCPTT speech media stream from the received SDP offer, which was also negotiated in pre-established session establishment, consisting of:
a) the port number for MCPTT speech; and
b) the codec(s) and media parameters selected by the participating MCPTT function from the received SDP offer; and
4) shall include for the media plane control channel, that is offered in the SDP offer from the controlling MCPTT function and accepted in the SDP answer by MCPTT client, the media-level section of each offered media plane control channel consisting of:
a) the media plane control channel parameters contained in the received SDP offer, restricted to media plane control channel parameters negotiated during the pre-established session establishment;
b) the port number for selected media plane control channel selected as specified in 3GPP TS 24.229 [4]; and
c) an mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14 for the accepted media plane control channel, with the RTCP SSRC that the participating MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the offerer in the floor control messages sent to participating MCPTT function for this session.
NOTE: The participating MCPTT function has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the offerer in this session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.3 SIP INVITE request towards the terminating MCPTT client | The participating MCPTT function shall generate an initial SIP INVITE request according to 3GPP TS 24.229 [4] and:
1) shall include in the SIP INVITE 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] if included in the incoming SIP INVITE request;
2) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
3) shall include the option tag "timer" in the Supported header field;
4) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
c) the isfocus media feature tag;
d) an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the incoming SIP INVITE request; and
e) any other uri-parameter provided in the Contact header field of the incoming SIP INVITE request;
5) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23];
6) shall include the option tag "norefersub" in a Supported header field according to rules and procedures of IETF RFC 4488 [22];
7) may include a Resource-Share header field in accordance with clause 5.7.1.20.3 in 3GPP TS 24.229 [4]; and
8) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP INVITE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.4 Response to a SIP INVITE request | 6.3.2.2.4.1 Provisional response
This clause is referenced from other procedures.
When sending a SIP provisional response other than the SIP 100 (Trying) response to the SIP INVITE request, the participating MCPTT function shall generate a SIP provisional response according to 3GPP TS 24.229 [4] and:
1) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag; and
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2) if the outgoing SIP provisional response is to be sent in response to the receipt of a SIP provisional response and the response contains an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP provisional response; and
3) if the incoming SIP INVITE request included the Supported header field with the value "100rel" and according to local policy, may include the Require header field with the value "100rel".
6.3.2.2.4.2 Final response
This clause is referenced from other procedures.
When sending SIP 200 (OK) responses, the participating MCPTT function shall generate a SIP 200 (OK) response according to 3GPP TS 24.229 [4] and:
1) shall include the option tag "timer" in a Require header field;
2) shall include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7], "UAS Behavior". If no "refresher" parameter was included in the SIP INVITE request, the "refresher" parameter in the Session-Expires header field shall be set to "uas";
3) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
c) an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP INVITE request from the controlling MCPTT function;
4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23]; and
5) if the incoming SIP response contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing SIP 200 (OK) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.5 Automatic Commencement Mode | 6.3.2.2.5.1 General
When receiving a "SIP INVITE request for terminating participating MCPTT function" that requires automatic commencement mode:
1) if:
a) the invited MCPTT client has one or more pre-established sessions without an associated MCPTT call;
b) the media-level section for the offered MCPTT speech media stream is the same as the media-level section for MCPTT speech media stream in an existing pre-established session; and
c) the media-level section of the offered media-floor control entity is the same as the media-level section for media-floor control entity in an existing pre-established session;
then the participating MCPTT function shall perform the actions specified in clause 6.3.2.2.5.3; or
2) otherwise the participating MCPTT function shall perform the actions specified in clause 6.3.2.2.5.2.
6.3.2.2.5.2 Automatic commencement for On-Demand session
When receiving a "SIP INVITE request for terminating participating MCPTT function" for an on-demand session that requires automatic commencement mode the participating MCPTT function:
1) if:
a) the incoming SIP INVITE request contained a Priv-Answer-Mode header field set to the value of "Auto";
b) no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; or
c) the incoming SIP INVITE request contained an Answer-Mode header field set to "Auto" and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer";
then:
a) shall generate a SIP 183 (Session Progress) response to the "SIP INVITE request for terminating participating MCPTT function" as specified in clause 6.3.2.2.4.1;
b) if the received SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <ambient-listening-type> element set to a value of "remote-init" shall include in the SIP 183 (Session Progress) response an alert-info header field set to a value of "<file:///dev/null>" according to IETF RFC 3261 [24] and as updated by IETF RFC 7462 [77]; and
NOTE: The SIP 183 (session Progress) response can be sent reliably or unreliably depending on the content of the received SIP INVITE request. Regardless of if the SIP 183 (Session Progress) response is sent reliably or unreliably, SDP is not included in the SIP 183 (Session Progress) response.
c) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 183 (Session Progress) response;
2) shall include a P-Asserted-Identity header field in the SIP 183 (Session Progress) response set to the public service identity of the participating MCPTT function;
3) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3;
4) shall set the Request-URI to the public user identity associated to the MCPTT ID of the MCPTT user to be invited;
5) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request, into the outgoing SIP INVITE request;
6) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to the public service identity of the participating MCPTT function;
7) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request with a value of "Auto", shall include a Priv-Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request. Otherwise, if the Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCPTT function shall include an Answer-Mode header field with the value "Auto" in the outgoing SIP INVITE request;
8) if no Answer-Mode header field or Priv-Answer-Mode header field were received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as defined in clause 7.3.3 or clause 7.3.4 is set to "auto-answer", shall set the Answer-Mode header field to "Auto" in the outgoing SIP INVITE request;
9) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCPTT function" as specified in clause 6.3.2.2.1;
10) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource-Priority header field with the contents set as in the received Resource-Priority header field; and
11) shall send the SIP INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4].
If the SIP 183 (Session Progress) response was sent reliably, then upon receiving a SIP PRACK request, the participating MCPTT function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the above SIP INVITE request sent to the MCPTT client, the participating MCPTT function:
1) if the SIP 183 (Session Progress) was sent unreliably, shall send the SIP 200 (OK) response immediately; and
2) if the SIP 183 (Session Progress) was sent reliably and,
a) if the SIP PRACK request to the SIP 183 (Session Progress) response has been received by the participating MCPTT function and the SIP 200 (OK) response to the SIP PRACK request has been sent, shall send the SIP 200 (OK) response immediately;
b) if the SIP PRACK request to the SIP 183 (Session Progress) response has not yet been received, then upon receipt of the SIP PRACK request, the participating MCPTT function shall generate a SIP 200 (OK) response to the SIP PRACK request and forward the SIP 200 (OK) response, according to 3GPP TS 24.229 [4], before sending the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCPTT function".
When the participating MCPTT function sends the SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCPTT function", the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2;
2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in clause 6.3.2.2.2.1;
3) 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;
3A) if the SIP 183 (Session Progress) was sent with the P-Answer-State header field set to "Unconfirmed", shall set the P-Answer-State header field to "Confirmed" in the outgoing SIP 200 (OK) response;
4) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [4].
The participating MCPTT function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [4].
6.3.2.2.5.3 Automatic commencement for pre-established session
NOTE 1: This clause is referenced from other procedures.
When receiving a "SIP INVITE request for terminating participating MCPTT function" for a pre-established session that requires automatic commencement mode the participating MCPTT function:
1) if the received SIP INVITE request contains:
a) an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <emergency-ind> element set to a value of "true" or with the <imminentperil-ind> element set to a value of "true"; or
b) a Priv-Answer-Mode header field;
shall perform the procedures of clause 6.3.2.2.5.2 with the following clarifications:
a) include in the outgoing SIP INVITE request a Replaces header field populated with the call-id, to-tag and from-tag of the targeted pre-established session as specified in IETF RFC 3891 [65];
b) include in the SDP offer the current media parameters used by the targeted pre-established session identified by the Replaces header field; and
c) if the SIP core supports resource sharing, include in the outgoing SIP INVITE request a Resource-Share header field as specified in 3GPP TS 24.229 [4] with:
i) the value "media-sharing";
ii) an "origin" header field parameter set to "session-receiver";
iii) a "timestamp" header field parameter; and
iv) a "rules" header field parameter with one resource sharing rule per media stream in the same order the corresponding m-line appears in the SDP. Each resource sharing rule is constructed as follows:
- a "new-sharing-key" part containing the same key as that included when the media bearer for the pre-established session was established; and
- a "directionality" part indicating the direction of the pre-established media bearer;
and shall skip the remaining steps of this clause;
2) shall generate a SIP 200 (OK) response to the "SIP INVITE request for terminating participating MCPTT function" as described in the clause 6.3.2.2.4.2;
3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.2.2.2 based on the SDP negotiated during the pre-established session establishment and SDP offer received in the "SIP INVITE request for terminating participating MCPTT function";
4) shall set the P-Answer-State header field to "Unconfirmed" in the SIP 200 (OK) response;
5) 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 functionshall include a P-Asserted-Identity header field set to the;
6) shall send the SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [4]; and
7) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 9.
NOTE 2: Received SIP INVITE requests handled by the present clause in steps 2) through 7) will result in the terminating client not receiving data normally contained in an application/ vnd.3gpp.mcptt-info+xml MIME body. This includes but is not limited to call type indicators such as XML elements <broadcast-ind> or <associated-group>. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.6 Manual Commencement Mode | 6.3.2.2.6.1 General
When receiving a "SIP INVITE request for terminating participating MCPTT function" that requires manual commencement mode:
1) if:
a) the invited MCPTT client has one or more pre-established sessions without an associated MCPTT call;
b) the media-level section for the offered MCPTT speech media stream is the same as the media-level section for MCPTT speech media stream in the existing pre-established session; and
c) the media-level section of the offered media-floor control entity is the same as the media-level section for media-floor control entity in the existing pre-established session;
then the participating MCPTT function shall perform the actions specified in clause 6.3.2.2.6.3; or
2) otherwise the participating MCPTT function shall perform the actions specified in clause 6.3.2.2.6.2.
6.3.2.2.6.2 Manual commencement for On-Demand session
When receiving a "SIP INVITE request for terminating participating MCPTT function" for an on-demand session that requires manual commencement mode the participating MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3;
2) shall set the Request-URI to the public user identity associated to the MCPTT ID of the MCPTT user to be invited;
3) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request;
4) if the Answer-Mode header field is present in the incoming SIP INVITE request, participating MCPTT function, shall include an Answer-Mode header field with the value "Manual";
5) if no Answer-Mode header field was received in the incoming SIP INVITE request and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as defined in clause 7.3.3 or clause 7.3.4 is set to "manual-answer", shall set the Answer-Mode header field to "Manual" in the outgoing SIP INVITE request;
6) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request, the participating MCPTT function shall include a Priv-Answer-Mode header field with the value "Manual";
7) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to the public service identity of the participating MCPTT function;
8) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for terminating participating MCPTT function" as specified in clause 6.3.2.2.1;
9) if the received SIP INVITE request contains a Resource-Priority header field, shall include a Resource-Priority header field with the contents set as in the received Resource-Priority header field; and
10) shall send the SIP INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 180 (Ringing) response to the above SIP INVITE request, the participating MCPTT function:
NOTE 1: A SIP 180 (Ringing) response is received from a terminating MCPTT client in the case of a private call or first-to-answer call.
1) shall generate a SIP 180 (Ringing) response as specified in clause 6.3.2.2.4.1;
2) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function; and
3) shall forward the SIP 180 (Ringing) response according to 3GPP TS 24.229 [4].
Upon receiving a SIP 183 (Session Progress) response to the above SIP INVITE request, the participating MCPTT function:
NOTE 2: A SIP 183 (Session Progress) response can be received from a terminating MCPTT client in the case of a group call.
1) shall generate a SIP 183 (Session Progress) response as specified in clause 6.3.2.2.4.1;
2) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function;
3) void; and
4) shall forward the SIP 183 (Session Progress) response according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP INVITE request sent to the MCPTT client, the participating MCPTT function:
When the participating MCPTT function sends the SIP 200 (OK) response the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2;
2) shall include in the SIP 200 (OK) response an SDP answer based on the SDP answer in the received SIP 200 (OK) response as specified in clause 6.3.2.2.2.1;
3) 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;
4) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.4; and
5) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [4].
The participating MCPTT function shall forward any other SIP response that does not contain SDP along the signalling path to the originating network according to 3GPP TS 24.229 [4].
6.3.2.2.6.3 Manual commencement for Pre-established session
When receiving a "SIP INVITE request for terminating participating MCPTT function" for a pre-established session that requires manual commencement mode the participating MCPTT function:
1) if:
a) the received SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <emergency-ind> element set to a value of "true" or with the <imminentperil-ind> element set to a value of "true"; or
b) if the Priv-Answer-Mode header field is present in the incoming SIP INVITE request;
then:
a) shall perform the procedures of clause 6.3.2.2.6.2 with the following clarifications:
i) include in the outgoing SIP INVITE request a SIP Replaces header field populated with the call-id, to-tag and from-tag of the targeted pre-established session as specified in IETF RFC 3891 [65];
ii) include in the SDP offer the current media parameters used by the targeted pre-established session identified by the Replaces header field; and
iii) if the SIP core supports resource sharing, include in the outgoing SIP INVITE request a Resource-Share header field as specified in 3GPP TS 24.229 [4] with:
A) the value "media-sharing";
B) an "origin" header field parameter set to "session-receiver";
C) a "timestamp" header field parameter; and
D) a "rules" header field parameter with one resource sharing rule per media stream in the same order the corresponding m-line appears in the SDP. Each resource sharing rule is constructed as follows:
- a "new-sharing-key" part containing the same key as that included when the media bearer for the pre-established session was established; and
- a "directionality" part indicating the direction of the pre-established media bearer; and
b) shall skip the remaining steps;
2) shall generate a SIP re-INVITE request as described in clause 6.3.2.2.3;
NOTE 1: A SIP re-INVITE request cannot include an Answer-Mode header field as specified in IETF RFC 5373 [18] so Manual Answer is implied with a SIP re-INVITE request within the existing SIP dialog of the pre-established session.
3) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming "SIP INVITE request for terminating participating MCPTT function" to the outgoing SIP re-INVITE request;
4) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request as specified in the clause 6.3.2.2.1; and
5) shall send the SIP re-INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4];
Upon receiving a SIP 180 (Ringing) response to the above SIP re-INVITE request, the participating MCPTT function:
NOTE 2: A SIP 180 (Ringing) response is received from a terminating MCPTT client in the case of a private call.
1) shall generate a SIP 180 (Ringing) response as specified in clause 6.3.2.2.4.1;
2) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function; and
3) shall forward the SIP 180 (Ringing) response according to 3GPP TS 24.229 [4].
Upon receiving a SIP 183 (Session Progress) response to the above SIP re-INVITE request, the participating MCPTT function:
NOTE 3: A SIP 183 (Session Progress) response can be received from a terminating MCPTT client in the case of a group call.
1) shall generate a SIP 183 (Session Progress) response as specified in clause 6.3.2.2.4.1;
2) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function;
3) void; and
4) shall forward the SIP 183 (Session Progress) response according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request, the participating MCPTT function:
1) if the received SDP answer includes changes in codecs or media formats, shall interact with the media plane as specified in 3GPP TS 24.380 [5] for updating the media plane with the newly negotiated codecs and media parameters from the received SDP answer;
2) shall generate a SIP 200 (OK) response as described in the clause 6.3.2.2.4.2;
3) 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;
4) shall include in the SIP 200 (OK) response, an SDP answer based on the SDP answer in the received SIP 200 (OK) response, as specified in clause 6.3.2.2.2.1;
5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 4: The participating MCPTT function sends a MCPC Connect message, in order to give MCPTT session identity to the terminating MCPTT client.
6) shall send the SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.7 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.8 SIP BYE request towards the terminating MCPTT client | 6.3.2.2.8.1 On-demand
Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function:
1) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5] for releasing media plane resource associated with the SIP session with the controlling MCPTT function;
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
3) shall include a P-Asserted-Identity header field in the outgoing SIP BYE request set to the public service identity of the participating MCPTT function;
4) if the received SIP BYE request contains an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body into the outgoing SIP BYE request; and
5) shall send the SIP BYE request to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request the participating MCPTT function:
1) shall send a SIP 200 (OK) response to the SIP BYE request received from the controlling MCPTT function according to 3GPP TS 24.229 [4]; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for releasing media plane resources associated with the SIP session with the MCPTT client.
6.3.2.2.8.2 Using pre-established session
Upon receiving a SIP BYE request from the controlling 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 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. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.9 Populate MIME bodies | This clause is referenced from other procedures.
If the incoming SIP request contains an application/vnd.3gpp.mcptt-info+xml MIME body, the participating MCPTT function:
1) if not already copied:
a) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP request; and
b) if an <MKFC-GKTP> element was included in the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP request, the <MKFC-GKTP> element shall not be copied into the application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP request.
If the received SIP request contains an application/vnd.3gpp.location-info+xml MIME body as specified in Annex F.3:
1) if not already copied, shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body received in the SIP request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP request.
If the received SIP request contains an application/resource-lists+xml MIME body:
1) if not already copied, shall copy the contents of the application/resource-lists+xml MIME body received in the SIP request into an application/resource-lists+xml MIME body included in the outgoing SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.10 Generating a SIP re-INVITE request towards the terminating MCPTT client | This clause is referenced from other procedures.
The participating MCPTT function shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] and:
1) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23];
2) may include a Resource-Share header field in accordance with clause 5.7.1.20.3 in 3GPP TS 24.229 [4];
3) shall perform the procedures specified in clause 6.3.2.2.9 to copy any MIME bodies in the received SIP (re‑)INVITE request to the outgoing SIP re-INVITE request; and
4) if the received SIP (re-)INVITE request contains a Resource-Priority header field, shall include a Resource-Priority header field with the contents set as in the received Resource-Priority header field. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.2.11 Generating a SIP MESSAGE request towards the terminating MCPTT client | This clause is referenced from other procedures.
The participating MCPTT function shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
1) 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;
2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCPTT ID of the terminating MCPTT user;
3) shall populate the outgoing SIP MESSAGE request MIME bodies as specified in clause 6.3.2.2.9; and
4) 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. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.3 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.4 Request initiated by the participating MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.4.1 Generating a SIP MESSAGE request for notification of entry into or exit from an emergency alert area | This clause describes the procedures for generating a SIP MESSAGE request to notify an MCPTT client that it has entered a pre-defined emergency alert area or exited from a pre-defined emergency alert area. The procedure is initiated by the participating MCPTT function when the participating MCPTT function determines that the MCPTT client has entered a pre-defined emergency alert area or exited from a pre-defined emergency alert area.
NOTE: The participating MCPTT function can use additional implementation-specific selection criteria to decide the recipients of the notification, i.e., whether and when an entry/exit notification is sent. The additional criteria can be the activated functional alias, ongoing emergency or conditions related to position such as speed, heading etc. The determination of the specific region is left to implementation.
The participating MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall set the Request-URI to the public user identity associated to the MCPTT ID of the targeted MCPTT user;
5) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function;
6) 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-Asserted-Service-Id header field according to IETF RFC 6050 [9];
7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user;
8) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <emergency-alert-area-ind> element:
a) set to a value of "true", if the MCPTT client has entered a pre-defined emergency alert area; or
b) set to a value of "false", if the MCPTT client has exited from a pre-defined emergency alert area; and
9) shall send the SIP MESSAGE request towards the MCPTT client according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP MESSAGE request, if the <emergency-alert-area-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request was:
1) set to a value of "true", shall record that the MCPTT client has received the notification that it has entered the pre-defined emergency alert area; and
2) set to a value of "false", shall record that the MCPTT client has received the notification that it has exited the pre-defined emergency alert area. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.4.2 Generating a SIP MESSAGE request for notification of entry into or exit from a group geographic area | This clause describes the procedures for generating a SIP MESSAGE request to notify an MCPTT client that it has entered a pre-defined group geographic area or exited from a pre-defined group geographic area requiring affiliation to or de-affiliation from a group. The procedure is initiated by the participating MCPTT function when the participating MCPTT function determines that the MCPTT client has entered a pre-defined group geographic area or exited from a pre-defined group geographic area.
NOTE: The participating MCPTT function can use additional implementation-specific selection criteria to decide the recipients of the notification, i.e., whether and when an entry/exit notification is sent. The additional criteria can be the activated functional alias, ongoing emergency or conditions related to position such as speed, heading etc. The determination of the specific region is left to implementation.
The participating MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall set the Request-URI to the public user identity associated to the MCPTT ID of the targeted MCPTT user;
5) shall include a P-Asserted-Identity header field set to the public service identity of the participating MCPTT function;
6) 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-Asserted-Service-Id header field according to IETF RFC 6050 [9];
7) void;
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcpttinfo> element containing the <mcptt-Params> element with:
a) an <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user;
b) an <associated-group-id> element set to the MCPTT group ID of the group for which a pre-defined group geographic area has been entered or exited; and
c) a <group-geo-area-ind> element:
i) set to a value of "true", if the MCPTT client has entered a pre-defined group geographic area; or
ii) set to a value of "false", if the MCPTT client has exited from a pre-defined group geographic area; and
9) shall send the SIP MESSAGE request towards the MCPTT client according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP MESSAGE request, if the <group-geo-area-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request was:
1) set to a value of "true", shall record that the MCPTT client has received the notification that it has entered the pre-defined group geographic area; and
2) set to a value of "false", shall record that the MCPTT client has received the notification that it has exited the pre-defined group geographic area. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.5 Handling of the no answer timer (TNP1) | When the terminating participating MCPTT function receives a SIP INVITE request to initiate a private call:
If:
1) the <allow-call-forwarding> element exists in the MCPTT user profile document, and the value is set to "true" (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
2) the <call-forwarding-on> element exists in the MCPTT user profile document, and the value is set to "true" (see the MCPTT user profile document in 3GPP TS 24.484 [50]); and
3) the <call-forwarding-condition> element exists and has a value of "no-answer" as specified in 3GPP TS 24.484 [50] set;
then:
1) the terminating participating MCPTT function shall start timer TNP1 (call forwarding no answer timer) with a timer value as described in clause B.2.2, prior to sending out a SIP INVITE request inviting the called MCPTT user to a private call.
When the terminating participating MCPTT function receives a SIP 200 (OK) response to the SIP INVITE request, from the called MCPTT user before expiry of TNP1 (call forwarding no answer timer), then the terminating participating MCPTT function shall stop timer TNP1 (call forwarding no answer timer) and forward the SIP 200 (OK) response to the controlling MCPTT function.
After expiry of timer TNP1 (call forwarding no answer timer) the terminating participating MCPTT function:
1) if the received SIP INVITE request contained a <forwarding-other-list> element with one or more <entry> elements shall reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "174 maximum number of allowed forwardings exceeded" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
2) shall generate and send a SIP CANCEL request to the called MCPTT user, according to IETF RFC 3261 [24], to cancel the SIP request for which the no answer timer has been expired;
3) shall reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 480 (Temporarily Unavailable) response including warning text set to "175 call is forwarded" in a Warning header field as specified in clause 4.4;
4) shall generate a SIP MESSAGE request as described in clause 6.3.2.6 to trigger the call forwarding of a private call and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body;
a) a <forwarding-reason> element set to a value of "no-answer"; and
5) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the terminating participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.2.6 Generating a SIP MESSAGE request for call forwarding of a private call | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request for call forwarding of a private call.
The terminating participating MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) 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;
b) 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];
c) 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 containing:
i) an <anyExt> element containing:
A) the <request-type> element set to a value of "forward-private-call-request";
B) if the <forward-to-functional-alias> element of the <ruleset> element is present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) on the participating MCPTT function with the value "true", then the <call-to-functional-alias-ind> element set to "true"; otherwise, the <call-to-functional-alias-ind> element set to "false";
NOTE 1: For a call forwarding to an MCPTT ID the value of the <forwarding-target-orig-id> is the MCPTT ID of the target user, while for call forwarding to a functional alias the value is the functional alias of the target user.
C) the <forwarding-target-orig-id> element set to the value of <call-forwarding-target> element in the MCPTT user profile document in 3GPP TS 24.484 [50];
D) the <forwarded-by-mcptt-id> element set to the MCPTT ID present in the <mcptt-request-uri> received in the SIP application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request; and
E) a <forwarded-by-functional-alias> element set to the <called-functional-alias-URI> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request, if present;
d) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the forwarded-calling-client user, according to the rules and procedures of IETF RFC 5366 [20];
2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function associated with the call forwarding service for the forwarded-calling-client user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: 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 4: 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 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the private call service for the calling user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include a P-Asserted-Identity header field set to the public service identity of participating MCPTT function;
4) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6]; and
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3 Controlling MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1 Request initiated by the controlling MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.1 SDP offer generation | The SDP offer is generated based on the received SDP offer. The SDP offer generated by the controlling MCPTT function:
1) when initiating a new MCPTT session the SDP offer;
a) shall contain only one SDP media-level section for MCPTT speech media stream as contained in the received SDP offer; and
b) shall contain one SDP media-level section for media plane control messages, if present in the received SDP offer; and
2) when adding a new MCPTT user to an existing MCPTT Session, the SDP offer shall contain the media stream currently used in the MCPTT session.
When composing the SDP offer according to 3GPP TS 24.229 [4], the controlling MCPTT function:
1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the media distribution function of the controlling MCPTT function;
2) for the MCPTT speech media stream, shall include all media-level attributes from the received SDP offer;
3) shall replace the IP address and port number for the offered media plane control channel, if any, in the received SDP offer with the IP address and port number of the floor control server of the controlling MCPTT function;
4) shall include an mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14 for the selected media plane control channel with the RTCP SSRC that the controlling MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the answerer in the floor control messages sent to the controlling MCPTT function for this session; and
NOTE: The controlling MCPTT function will receive in the SDP answer the RTP SSRC it will have to use in the floor control message it will send to the answerer in this session.
5) for the offered media plane control channel, shall include any other necessary 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.2 Sending an INVITE request | This clause is referenced from other procedures.
The controlling MCPTT function shall generate an initial SIP INVITE request according to 3GPP TS 24.229 [4].
The controlling MCPTT function:
1) shall include in the Contact header field an MCPTT session identity for the MCPTT session with the g.3gpp.mcptt media feature tag, the isfocus media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" according to IETF RFC 3840 [16];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) 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-Asserted-Service-Id header field according to IETF RFC 6050 [9] in the SIP INVITE request;
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
5) void ;
6) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7]. The refresher parameter shall be omitted;
7) shall include the Supported header field set to "timer";
8) if the received SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body containing an <ambient-listening-type> element and:
a) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [18] was included in the received SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the received SIP INVITE request; or
b) a Priv-Answer-Mode header field was received containing a value other than "Auto";
shall include a Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request;
9) if the received SIP INVITE request contained a Priv-Answer-Mode header field and did not contain an application/vnd.3gpp.mcptt-info+xml MIME body containing an <ambient-listening-type> element, shall include an unmodified Priv-Answer-Mode header field;
10) if the received SIP INVITE request did not contain an application/vnd.3gpp.mcptt-info+xml MIME body containing an <ambient-listening-type> element and did not contain a Priv-Answer-Mode header field, shall include an unmodified Answer-Mode header field if present in the incoming SIP INVITE request; and
11) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body, shall copy the application/vnd.3gpp.mcptt-info+xml MIME body to the outgoing INVITE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.3 Receipt of a SIP response to a SIP INVITE request | 6.3.3.1.3.1 Final response
On receipt of the SIP 200 (OK) response to the initial outgoing SIP INVITE request the controlling MCPTT function:
1) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [7]; and
2) shall cache SIP feature tags, if received in the Contact header field, and if the specific feature tags are supported. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.4 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.5 Sending a SIP BYE request | When a participant needs to be removed from the MCPTT session, the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for the MCPTT session release;
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [4]; and
3) shall send the SIP BYE request to the MCPTT clients according to3GPP TS 24.229 [4].
If timer TNG3 (group call timer) has not expired, then when the last MCPTT client is removed from the MCPTT session, the controlling MCPTT function shall stop timer TNG3 (group call timer).
When the MCPTT group session needs to be released, the controlling MCPTT function shall send SIP BYE requests as described in this clause, to all participants of the group session.
Upon receiving a SIP 200 (OK) response to a SIP BYE request the controlling MCPTT function shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.380 [5] for releasing media plane resources associated with the SIP session with the MCPTT clients. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.