hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.4 End group call at the terminating participating MCPTT function | 10.1.1.3.4.1 Receipt of SIP BYE request for group call on-demand
Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
If the MCPTT session for group call was established as a result of receiving a remotely initiated call request and if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 9.2.2.2.14 to cancel the implicit affiliation of the initiator of this group call.
10.1.1.3.4.2 Receipt of SIP BYE request when ongoing pre-established session
Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.2.
If the MCPTT session for group call was established as a result of receiving a remotely initiated call request and if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in this procedure, shall perform the procedures of clause 9.2.2.2.14 to cancel the implicit affiliation of the initiator of this group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.5 Rejoin procedures | 10.1.1.3.5.1 Originating procedures - on demand prearranged group call
Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCPTT function shall follow the procedures specified in clause 10.1.1.3.1.1 with the clarification in step 10) of clause 10.1.1.3.1.1 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity which mapped to the MCPTT session identity provided in Request-URI of the "SIP INVITE request for originating participating MCPTT function".
10.1.1.3.5.2 Originating procedures - prearranged group call using pre-established session
Upon receipt of a "SIP REFER request for a pre-established session", with the Refer-To header containing an application/vnd.3gpp.mcptt-info+xml MIME type content in an hname "body" parameter in the headers portion of the SIP URI and with the <session-type> element set to "prearranged" the participating MCPTT function shall follow the procedures specified in clause 10.1.1.3.1.2 with the clarification in step 16) of clause 10.1.1.3.1.2 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity which mapped to the MCPTT session identity provided in the Refer-to header field of the "SIP REFER request for a pre-established session". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.6 Reception of a SIP re-INVITE request for terminating MCPTT client for priority call | In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a SIP re-INVITE request for a terminating MCPTT client of a MCPTT group containing an emergency indication or imminent peril indication, the participating MCPTT function:
1) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
2) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.2.10;
3) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.2.1; and
4) shall send the SIP re-INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the above SIP re-INVITE request sent to the MCPTT client, 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 interact with the media plane as specified in 3GPP TS 24.380 [5]; and
4) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.1 Originating Procedures | 10.1.1.4.1.1 INVITE targeted to an MCPTT client
This clause describes the procedures for inviting an MCPTT user to an MCPTT session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 10.1.1.4.2 or as the result of receiving a SIP 403 (Forbidden) response as described in this clause.
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited.;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating 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 3: If the terminating participating 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 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the MCPTT user to be invited or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: 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 set the P-Asserted-Identity header field to the public service identity of the controlling MCPTT function;
4) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request:
a) the <mcptt-request-uri> element set to the MCPTT ID of the terminating user; and
b) the <mcptt-calling-group-id> element set to the group identity;
NOTE 6: The <mcptt-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1).
5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1;
6) if the in-progress emergency state of the group is set to a value of "true" the controlling MCPTT function:
a) shall include a Resource-Priority header field populated with the values for an MCPTT emergency group call as specified in clause 6.3.3.1.19;
b) if the received SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true":
i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcptt-info+xml MIME body an <emergency-ind> element set to a value of "true"; and
ii) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCPTT user and MCPTT group are authorised for the initiation of MCPTT emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcptt-info+xml MIME body and the application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false"; and
c) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <imminentperil-ind> element set to a value of "false";
7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCPTT function:
a) shall include a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.3.3.1.19; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true";
8) void
9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [4].
Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" and containing a P-Answer-State header field with the value "Unconfirmed" in response to the SIP INVITE request the controlling MCPTT function:
1) shall send a SIP PRACK request towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
2) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.4; and
3) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1.
NOTE 7: The notifications above could be sent prior to the SIP 200 (OK) response being sent to the inviting MCPTT client. These notifications received by MCPTT clients that are group members do not mean that the group session will be successfully established.
NOTE 8: The procedures executed by the controlling MCPTT function prior to sending a response to the inviting MCPTT client are specified in clause 10.1.1.4.2.
10.1.1.4.1.2 INVITE targeted to the non-controlling MCPTT function of an MCPTT group
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Request-URI to the public service identity of the non-controlling MCPTT function serving the group identity of the MCPTT group owned by the partner MCPTT system;
NOTE 1: If the non-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 2: If the non-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 3: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function serving the MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 4: 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 set the P-Asserted-Identity to the public service identity of the controlling MCPTT function;
4) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request:
a) the <mcptt-request-uri> element set to the group identity of the MCPTT group hosted by the non-controlling MCPTT function in the partner MCPTT system; and
b) the <mcptt-calling-group-id> element set to the group identity of the group served by the controlling MCPTT function;
5) shall include the Recv-Info header field set to g.3gpp.mcptt-floor-request;
6) void
7) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and
8) shall send the SIP INVITE request towards the partner MCPTT system in accordance with 3GPP TS 24.229 [4].
Upon receiving SIP 403 (Forbidden) response for the SIP INVITE request, if according to local policy and if:
1) the response contains a Warning header field with the MCPTT warning code "128"; and
2) the response contains a P-Refused-URI-List header field and an application/resource-lists+xml MIME body as specified in IETF RFC 5318 [36];
NOTE 5: The application/resource-lists+xml MIME body contains MCPTT IDs identifying MCPTT users in a partner MCPTT system that needs to be invited to the prearranged group call in case of group regrouping using interrogating method as specified in 3GPP TS 23.379 [3] clause 10.6.2.4.2.
then the controlling MCPTT function:
1) shall check if the number of members of the MCPTT group exceeds the value contained in the <on-network-max-participant-count> element of the group document as specified in 3GPP TS 24.481 [31]. If exceeded, the controlling MCPTT function shall invite only <on-network-max-participant-count> members from the application/resource-lists+xml MIME body; and
NOTE 6: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the prearranged group session It is operator policy that determines which participants in the application/resource-lists+xml MIME body are invited to the group call.
2) shall invite MCPTT users as specified in this clause using the list of MCPTT IDs in URI-List.
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 7: The procedures executed by the controlling MCPTT function prior to sending a response to the inviting MCPTT client are specified in clause 10.1.1.4.2.
2) if at least one of the invited MCPTT clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCPTT function as specified in clause 10.1.3.4.3; and
3) if the 200 (OK) response includes the <floor-state> element set to "floor-taken", shall wait for a SIP INFO request containing a floor request from the non-controlling MCPTT function.
Upon receiving a SIP INFO request containing a floor request where:
1) the Request-URI contains an MCPTT session ID identifying an ongoing temporary group session; and
2) the application/vnd.3gpp.mcptt-info+xml MIME body contains the <mcptt-calling-group-id> element with the MCPTT group ID of a MCPTT group invited to the temporary group session;
then the controlling MCPTT function:
1) shall send a SIP 200 (OK) response to the SIP INFO request to the non-controlling MCPTT function as specified in 3GPP TS 24.229 [4]; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.2 Terminating Procedures | In the procedures in this clause:
1) MCPTT ID in an incoming SIP INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
3) MCPTT ID in an outgoing SIP INVITE request refers to the MCPTT ID of the called user in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request;
4) indication of required group members in a SIP 183 (Session Progress) response refers to the <required> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to "true" in a SIP 183 (Session Progress) sent by the non-controlling MCPTT function of an MCPTT group;
5) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
6) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP INVITE request for controlling MCPTT function of an MCPTT group", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating an MCPTT emergency group call as determined by clause 6.3.3.1.13.2, or for originating an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5, the controlling MCPTT function can according to local policy choose to accept the request.
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
4) if received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17;
5) if the group identity is associated with a group document maintained by the GMS:
NOTE 2: How the MCPTT server determines that a group identity represents a group for which a group document is stored in the GMS is an implementation detail.
a) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2;
a1) if the group document contains a <list -service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
b) if the group referred to by the group identity has been regrouped, shall:
i) stop processing the SIP INVITE request;
ii) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "148 group is regrouped" as specified in clause 4.4 "Warning header field";
iii) if the group referred to by the group identity has been regrouped based on a preconfigured group, shall send a copy of the notifying SIP MESSAGE that was generated and sent per clause 16.2.4.1 to the participating function for the MCPTT ID of the incoming SIP INVITE request; and
iv) skip the rest of the steps;
c) if the result of the initial processing in clause 6.3.5.2 was that a SIP 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCPTT function of an MCPTT group" has been sent, do not continue with the rest of the steps in this clause;
6) if the group identity is associated with a user or group regroup based on a preconfigured group:
a) shall retrieve the stored information for the group identity;
b) if there is no stored information for the group identity, the controlling MCPTT function:
i) shall return a SIP 404 (Not Found) response with the warning text set to "163 the group identity indicated in the request does not exist" as specified in clause 4.4 "Warning header field" and shall not continue with the rest of the steps;
NOTE 3: The user or group regroup can have been removed very recently and the client has sent the group call request prior to receiving the removal notification.
6a) if the group identity is associated with a TGI or the identity of a group regroup based a preconfigured group and the received SIP INVITE request does not include an <mcptt-calling-group-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall return a SIP 403 (Forbidden) response to "SIP INVITE request for controlling MCPTT function of an MCPTT group".
NOTE 4: This is the case where the MCPTT client has requested the setup of a regroup without including the identity of the constituent group, leading to the participating MCPTT function forwarding the SIP INVITE directly to the controlling MCPTT function. This is not allowed, since the originating client is required to include the identity of the constituent group.
7) shall perform the actions as described in clause 6.3.3.2.2;
8) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero;
9) shall determine if an MCPTT group call for the group identity is already ongoing by determining if an MCPTT session identity has already been allocated for the group call and the MCPTT session is active;
10) if the SIP INVITE request contains an unauthorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2:
a) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response as specified in clause 6.3.3.1.14; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
11) if the SIP INVITE request contains an unauthorised request for an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
12) if a Resource-Priority header field is included in the SIP INVITE request:
a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or
b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps;
13) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element, the controlling MCPTT function can remember the location information contained in the <location-info> root element;
14) if the MCPTT group call is not ongoing then:
a) if:
i) the user identified by the MCPTT ID is not affiliated to the group identity contained in the <mcptt-request-uri> element of the SIP INVITE request as specified in clause 6.3.6 and the <remotely-initiated-call-request-ind> element set to a value of "false" or does not exists;
ii) the group identity contained in an <mcptt-calling-group-id> element of the SIP INVITE request is not a constituent MCPTT group ID;
NOTE 5: If the SIP INVITE is for a temporary group or a group regroup based on preconfigured group, the affiliation of the calling user to the constituent group has been assured by the non-controlling MCPTT function of the constituent group before forwarding this SIP INVITE to the controlling function of the regroup.
iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or
iv) the received SIP INVITE request is an authorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2 or MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCPTT user identified in the <mcptt-calling-user-id> of the SIP INVITE is determined to not be eligible for implicit affiliation as specified in clause 9.2.2.3.6;
then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below;
b) if the user identified by the MCPTT ID is not authorised to initiate the prearranged group session as specified in clause 6.3.5.4, shall send a SIP 403 (Forbidden) response with the warning text set to: "119 user is not authorised to initiate the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
c) if the received SIP INVITE request contains an authorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2 or MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5 or the <remotely-initiated-call-request-ind> element set to a value of "true" and the MCPTT user is eligible to be implicitly affiliated with the MCPTT group as determined in step 14) a) iv) above, shall perform the implicit affiliation as specified in clause 9.2.2.3.7;
d) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
e) shall create a prearranged group session and allocate an MCPTT session identity for the prearranged group call, and shall handle timer TNG3 (group call timer) as specified in clause 6.3.3.5;
f) if the group identity in the "SIP INVITE request for controlling MCPTT function of an MCPTT group" is a TGI or the identity of a group regroup based on a preconfigured group:
i) shall, for each of the constituent MCPTT groups except for the calling MCPTT group identified in the <mcptt-calling-group-id> element of the incoming SIP INVITE, generate a SIP INVITE request towards the MCPTT server that owns the constituent MCPTT group identity by following the procedures in clause 10.1.1.4.1.2; and
NOTE 6: The MCPTT server that the SIP INVITE request is sent to acts as a non-controlling MCPTT function;
ii) shall send the SIP 200 (OK) response towards the inviting non-controlling MCPTT function according to 3GPP TS 24.229 [4];
g) if the group identity in the SIP INVITE request for controlling MCPTT function of an MCPTT group is an MCPTT group ID:
i) shall determine the members to invite to the prearranged MCPTT group call as specified in clause 6.3.5.5. If:
A) the number of affiliated members of the MCPTT group is lower than the value contained in the <on-network-minimum-number-of-affiliated-members> element of the group document as specified in 3GPP TS 24.481 [31]; or
B) the group document contains any <on-network-affiliation-to-group-required> group member as specified in 3GPP TS 24.481 [31] that is not affiliated;
then the controlling MCPTT function shall send a SIP 480 (Temporarily Unavailable) response to the MCPTT client that originated the group session with the warning text set to "112 group call abandoned due to required group members not part of the group session" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
ii) if necessary, shall start timer TNG1 (acknowledged call setup timer) according to the conditions stated in clause 6.3.3.3;
iii) if the received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element set to a value of "true":
A) shall cache the information that the MCPTT user has initiated an MCPTT emergency call;
B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCPTT emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that the MCPTT user has initiated an MCPTT emergency alert; and
C) if the in-progress emergency state of the group is set to a value of "false":
I) shall set the value of the in-progress emergency state of the group to "true"; and
II) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16;
iv) if the in-progress emergency state of the group is set to a value of "false" and if the received SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCPTT function shall:
A) shall cache the information that the MCPTT user has initiated an MCPTT imminent peril call; and
B) if the in-progress imminent peril state of the group is set to a value of "false", shall set the in-progress imminent peril state of the group to a value of "true";
v) shall invite each group member determined in step 13)g)i) above, to the group session, as specified in clause 10.1.1.4.1.1; and
vi) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3; and
15) if the MCPTT group call is ongoing then:
a) if:
i) the user identified by the MCPTT ID in the SIP INVITE request is not affiliated to the group identity contained in the <mcptt-request-uri> element of the SIP INVITE request as specified in clause 6.3.6 and the <remotely-initiated-call-request-ind> element set to a value of "false" or does not exists;
ii) the group identity contained in an <mcptt-calling-group-id> element of the SIP INVITE request is not a constituent MCPTT group ID;
iii) the received SIP INVITE request does not contain an emergency indication or imminent peril indication; or
iv) the received SIP INVITE request is an authorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2 or MCPTT imminent peril group call as determined clause 6.3.3.1.13.5 and is determined to not be eligible for implicit affiliation as specified in clause 9.2.2.3.6;
then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below;
b) if the user identified by the MCPTT ID in the SIP INVITE request is not authorised to join the prearranged group session as specified in clause 6.3.5.3, shall send a SIP 403 (Forbidden) response with the warning text set to "121 user is not authorised to join the group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
c) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
d) if <on-network-max-participant-count> as specified in 3GPP TS 24.481 [31] is already reached:
i) if, according to local policy, the user identified by the MCPTT ID in the SIP INVITE request is deemed to have a higher priority than an existing user in the group session, may remove a participant from the session by following clause 10.1.1.4.4.3, and skip the next step; and
NOTE 7: The local policy for deciding whether to admit a user to a call that has reached its maximum amount of participants can include the <user-priority> and the <participant-type> of the user as well as other information of the user from the group document as specified in 3GPP TS 24.481 [31]. The local policy decisions can also include taking into account whether the imminent-peril indicator or emergency indicator was received in the SIP INVITE request.
ii) shall return a SIP 486 (Busy Here) response with the warning text set to "122 too many participants" to the originating network as specified in clause 4.4 and skip the rest of the steps;
e) if the received SIP INVITE request contains an authorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2 or MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5 or the <remotely-initiated-call-request-ind> element set to a value of "true" and the MCPTT user is eligible to be implicitly affiliated with the MCPTT group as determined in step 15) a) iv) above, shall perform the implicit affiliation as specified in clause 9.2.2.3.7;
f) if the received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element set to a value of "true":
i) shall cache the information that the MCPTT user has initiated an MCPTT emergency call;
ii) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCPTT emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the information that the MCPTT user has initiated an MCPTT emergency alert;
iii) if the in-progress emergency state of the group is set to a value of "false":
A) shall set the value of the in-progress emergency state of the group to "true";
B) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16;
C) shall generate SIP re-INVITE requests for the MCPTT emergency group call to the other call participants of the MCPTT group as specified in clause 6.3.3.1.6; and
D) shall send the SIP re-INVITEs towards the other participants of the MCPTT group call;
iv) if the in-progress emergency state of the group is set to a value of "true":
A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCPTT user's emergency indication as specified in clause 6.3.3.1.11, setting the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
v) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
g) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true", the controlling MCPTT function:
i) shall cache the information that the MCPTT user has initiated an MCPTT imminent peril call; and
ii) if the in-progress imminent peril state of the group is set to a value of "false":
A) shall set the in-progress imminent peril state of the group to a value of "true";
B) shall generate SIP re-INVITE requests for the MCPTT imminent peril group call to the other call participants of the MCPTT group as specified in clause 6.3.3.1.15;
C) shall send the SIP re-INVITEs towards the other participants of the MCPTT group call; and
D) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
iii) if the in-progress imminent peril state of the group is set to a value of "true":
A) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCPTT user's imminent peril indication as specified in clause 6.3.3.1.11, setting the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
h) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.3.2;
i) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
j) shall include in the SIP 200 (OK) response with the warning text set to "123 MCPTT session already exists" as specified in clause 4.4;
k) if the received SIP re-INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
l) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
NOTE 8: In this case, the request was for an imminent peril call but a higher priority MCPTT emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority.
m) shall interact with media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 9: Resulting media plane processing is completed before the next step is performed.
n) shall send the SIP 200 (OK) response towards the inviting MCPTT client or inviting non-controlling MCPTT function according to 3GPP TS 24.229 [4];
o) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT User has joined in the MCPTT group call, as specified in clause 6.3.3.4;
NOTE 10: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
p) shall send a SIP NOTIFY request to each MCPTT client according to 3GPP TS 24.229 [4];
q) Upon receiving a SIP ACK to the above SIP 200 (OK) response and the SIP 200 (OK) response contained a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", shall follow the procedures in clause 6.3.3.1.18; and
r) shall not continue with the rest of the clause.
Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 10.1.1.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], the timer TNG1 (acknowledged call setup timer) is not running, the controlling MCPTT function supports media buffering and the SIP final response is not yet sent to the inviting MCPTT client:
1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2;
2) shall include the warning text set to "122 too many participants" as specified in clause 4,4 in the SIP 200 (OK) response, if the prearranged MCPTT group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [31];
3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
4) shall include a P-Answer-State header field with the value "Unconfirmed";
5) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
6) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
7) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 11: Resulting user plane processing is completed before the next step is performed.
8) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4];
9) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT User has joined in the MCPTT group call, as specified in clause 6.3.3.4; and
NOTE 12: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
10) shall send a SIP NOTIFY request to each MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 183 (Session Progress) response for a SIP INVITE request as specified in clause 10.1.1.4.1.2 containing an indication of required group members, the timer TNG1 (acknowledged call setup timer) is running and all SIP 200 (OK) responses have been received to all SIP INVITE requests sent to MCPTT clients specified in clause 10.1.1.4.1.1, then the controlling MCPTT function shall wait until the SIP 200 (OK) response has been received to the SIP INVITE request specified in clause 10.1.1.4.1.2 before generating a SIP 200 (OK) response to the "SIP INVITE request for controlling MCPTT function of an MCPTT group".
Upon receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 10.1.1.4.1 that was sent to an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [31]; and
1) if the MCPTT ID in the SIP 200 (OK) response matches to the MCPTT ID in the corresponding SIP INVITE request;
2) there are no outstanding SIP 200 (OK) responses to SIP INVITE requests which were sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [31]; and
3) there is no outstanding SIP 200 (OK) response to a SIP INVITE request sent in clause 10.1.1.4.1.2 where the SIP 183 (Session Progress) response contained an indication of required group members;
the controlling MCPTT function:
1) shall stop timer TNG1 (acknowledged call setup timer) as described in clause 6.3.3.3;
2) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps;
3) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCPTT group has been exceeded the <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [31];
4) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
5) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 13: Resulting media plane processing is completed before the next step is performed.
6) shall send a SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4];
7) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT user has joined in the MCPTT group call, as specified in clause 6.3.3.4; and
NOTE 14: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
8) shall send the SIP NOTIFY request to the MCPTT clients according to 3GPP TS 24.229 [4].
Upon:
1) receiving a SIP 200 (OK) response for a SIP INVITE request as specified in clause 10.1.1.4.1;
2) the timer TNG1 (acknowledged call setup timer) is not running;
3) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document;
4) the controlling MCPTT function supports media buffering; and
5) the SIP final response has not yet been sent to the inviting MCPTT client;
the controlling MCPTT function according to local policy:
1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3;
2) shall include the warning text set to "122 too many participants" as specified in clause 4.4 in the SIP 200 (OK) response, if all members were not invited because the prearranged MCPTT group has exceeded the <max-participant-count> members as specified in 3GPP TS 24.481 [31];
3) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
4) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
5) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
6) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 15: Resulting media plane processing is completed before the next step is performed.
7) shall send a SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4];
8) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT user has joined in the MCPTT group call, as specified in clause 6.3.3.4; and
NOTE 16: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
9) shall send the SIP NOTIFY request to the MCPTT clients according to 3GPP TS 24.229 [4].
Upon expiry of timer TNG1 (acknowledged call setup timer), if there are outstanding SIP 200 (OK) responses to SIP INVITE requests sent to affiliated and <on-network-required> group members as specified in 3GPP TS 24.481 [31], the controlling MCPTT function shall follow the procedures specified in clause 6.3.3.3.
If timer TNG1 (acknowledged call setup timer) is running and a final SIP 4xx, 5xx or 6xx response is received from an affiliated and <on-network-required> group member as specified in 3GPP TS 24.481 [31], the controlling MCPTT function shall follow the relevant procedures specified in clause 6.3.3.3.
If:
1) timer TNG1 (acknowledged call setup timer) is not running;
2) the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the value of the <on-network-minimum-number-to-start> element of the group document; and
3) a final SIP 4xx, 5xx or 6xx response is received from an invited MCPTT client;
then the controlling MCPTT function shall perform one of the following based on policy:
1) send the SIP final response towards the inviting MCPTT client, according to 3GPP TS 24.229 [4], if a SIP final response was received from all the other invited MCPTT clients and the SIP 200 (OK) response is not yet sent; or
2) remove the invited MCPTT client from the MCPTT Session as specified in clause 6.3.3.1.5, if a SIP final response other than 2xx or 3xx was received from all the invited MCPTT clients and the SIP 200 (OK) response is already sent. The controlling MCPTT function may invite an additional member of the prearranged MCPTT group as specified in clause 10.1.1.4.1 that has not already been invited, if the prearranged MCPTT group has more than <on-network-max-participant-count> members as specified in 3GPP TS 24.481 [31], and all members have not yet been invited.
If the group identity in the "SIP INVITE request for controlling MCPTT function of an MCPTT group" is a TGI or the identity of a group regroup based on a preconfigured group and constituent MCPTT groups were invited as specified in clause 10.1.1.4.1.2 and,
1) if all non-controlling MCPTT functions hosting the constituent MCPTT groups have responded with a SIP 2xx, SIP 3xx, SIP 4xx, SIP 5xx or SIP 6xx responses to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group"; and
2) if all expected SIP INFO requests containing a floor request are received;
then the controlling MCPTT function shall indicate to the media plane that all final responses are received.
NOTE 17: If the SIP 200 (OK) response to the SIP INVITE request for non-controlling MCPTT function of an MCPTT group included the application/vnd.3gpp.mcptt-info+xml MIME body with the <floor-state> element set to "floor-taken", the controlling MCPTT function expects that the non-controlling MCPTT functions sends a SIP INFO request containing a floor request.
Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCPTT client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.18. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.3 End group call at the terminating controlling MCPTT function | Upon receiving a SIP BYE request the controlling MCPTT function shall follow the procedures as specified in clause 6.3.3.2.4.
If the MCPTT session for group call was established as a result of receiving of a remotely initiated call request and if the implicit affiliation procedures of clause 9.2.2.3.7 were invoked in this procedure, shall perform the procedures of clause 9.2.2.3.11 to cancel the implicit affiliation of the initiator of this group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.4 End group call initiated by the controlling MCPTT function | 10.1.1.4.4.1 General
This clause describes the procedures of each functional entity for ending the group call initiated by the controlling MCPTT function.
10.1.1.4.4.2 SIP BYE request for releasing MCPTT session for a group call
When the MCPTT session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
If the MCPTT session for group call was established as a result of receiving a remotely initiated call request and if the implicit affiliation procedures of clause 9.2.2.3.7 were invoked in this procedure, shall perform the procedures of clause 9.2.2.3.11 to cancel the implicit affiliation of the initiator of this group call.
10.1.1.4.4.3 SIP BYE request toward a MCPTT client
When an MCPTT client needs to be removed from the MCPTT session (e.g. due to de-affiliation or admitting a higher priority user), the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
After successful removing the MCPTT client from the MCPTT session, the controlling MCPTT function may generate a notification to the MCPTT clients, which have subscribed to the conference event package that an MCPTT user has been removed from the MCPTT session, as specified in clause 6.3.3.4 and send the SIP NOTIFY request to the MCPTT client according to 3GPP TS 24.229 [4].
If the MCPTT session for group call was established as a result of receiving a remotely initiated call request and if the implicit affiliation procedures of clause 9.2.2.3.7 were invoked in this procedure, shall perform the procedures of clause 9.2.2.3.11 to cancel the implicit affiliation of the initiator of this group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.5 Rejoin procedures | 10.1.1.4.5.1 Terminating procedures
Upon receipt of a SIP INVITE request that includes an MCPTT session identity of an ongoing MCPTT session in the Request-URI the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating an MCPTT emergency group call as determined by clause 6.3.3.1.13.2, or for originating an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5, the controlling MCPTT function can according to local policy choose to accept the request.
2) shall reject the SIP request with a SIP 404 (Not Found) response if the MCPTT group call represented by the MCPTT session identity in Request-URI is not present;
3) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
4) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
5) shall determine the MCPTT ID of the calling user;
6) if the user identified by the MCPTT ID is not authorised to join the prearranged group session as specified in clause 6.3.5.3, shall send a SIP 403 (Forbidden) response with the warning text set to "121 user is not authorised to join the group call" in a Warning header field as specified in clause 4.4. Otherwise continue with the rest of the steps below;
7) shall perform the actions on receipt of an initial SIP INVITE request as described in clause 6.3.3.2.2;
8) if the user identified by the MCPTT ID is not affiliated to the MCPTT group ID associated with the MCPTT session identity as specified in clause 6.3.6, shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4;
9) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
10) if <on-network-max-participant-count> as specified in 3GPP TS 24.481 [31] is already reached:
a) if, according to local policy, the user identified by the MCPTT ID in the SIP INVITE request is deemed to have a higher priority than an existing user in the group session, may remove a participant from the session by following clause 10.1.1.4.4.3, and skip the next step; and
NOTE 2: The local policy for deciding whether to admit a user to a call that has reached its maximum amount of participants can include the <user-priority> and the <participant-type> of the user as well as other information of the user from the group document as specified in 3GPP TS 24.481 [31]. The local policy decisions can also include taking into account whether the imminent-peril indicator or emergency indicator was received in the SIP INVITE request.
b) shall return a SIP 486 (Busy Here) response with the warning text set to "122 too many participants" to the originating network as specified in clause 4.4 Otherwise, continue with the rest of the steps;
11) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.3.2;
12) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
13) shall interact with media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 3: Resulting media plane processing is completed before the next step is performed.
14) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4];
15) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT User has joined in the MCPTT group call, as specified in clause 6.3.3.4; and
NOTE 4: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
16) shall send a SIP NOTIFY request to each MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.6 Late call entry initiated by controlling MCPTT function | When controlling MCPTT function is notified that an MCPTT client is newly affiliated or comes back from out of coverage, the controlling MCPTT function shall invite the MCPTT client to join an ongoing MCPTT group call by following the procedures specified in clause 10.1.1.4.1.
NOTE: How the MCPTT function is informed when an MCPTT client is coming back from out of coverage is out of scope of present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.7 Receipt of a SIP re-INVITE request | In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a SIP re-INVITE request for an MCPTT session identity identifying an on-demand prearranged MCPTT group session, the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP re-INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: If the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true", the controlling MCPTT function can choose to accept the request.
2) if received SIP re-INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17;
3) if the received SIP re-INVITE request contains an unauthorised request to initiate an MCPTT emergency call as determined by clause 6.3.3.1.13.2:
a) shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response as specified in clause 6.3.3.1.14; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
4) if the received SIP re-INVITE request contains an imminent peril indication set to "true" for an MCPTT imminent peril group call and this is an unauthorised request for an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.6, shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
5) if a Resource-Priority header field is included in the received SIP re-INVITE request:
a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP re-INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; and
b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP re-INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps;
6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCPTT emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCPTT function:
a) shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency call i.e the group in-progress emergency state;
b) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCPTT emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency alert;
c) if the in-progress emergency state of the group is set to a value of "true" and another MCPTT user is indicating a new emergency indication:
i) for each of the other affiliated members of the group:
A) shall generate a SIP MESSAGE request notification of the MCPTT user's emergency indication as specified in clause 6.3.3.1.11;
B) shall set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true";
C) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP re-INVITE request; and
D) if indicated above in step 6) b), shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
ii) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
iii) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false"; and
d) if the in-progress emergency state of the group is set to a value of "false":
i) shall set the value of the in-progress emergency state of the group to "true";
ii) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16;
NOTE 2: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2.
iii) shall generate SIP re-INVITE requests for the MCPTT emergency group call to the other participants of the MCPTT group call as specified in clause 6.3.3.1.6;
iv) shall send the SIP re-INVITEs towards the other participants of the MCPTT group call;
v) for each of other affiliated members of the group that are not participating in the call:
A) shall generate a SIP MESSAGE request notification of the MCPTT user's emergency indication as specified in clause 6.3.3.1.11;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP re-INVITE request;
C) shall set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true";
D) if indicated above in step 6) b), shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
E) send the SIP MESSAGE request according to 3GPP TS 24.229 [4]; and
vi) upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an unauthorised request for an MCPTT emergency group call cancellation as determined by clause 6.3.3.1.13.4:
a) shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response;
b) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in annex F.1 with an <emergency-ind> element set to a value of "true";
c) if an <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is included in the SIP re-INVITE request set to "false", and there is an outstanding MCPTT emergency alert for the MCPTT user, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "true"; and
d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
7a) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency group call cancellation as determined by clause 6.3.3.1.13.4 and if another user is in emergency state and is transmitting media as determined by interacting with the media plane as specified in 3GPP TS 24.380 [5]:
a) shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response;
b) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in annex F.1 with an <emergency-ind> element set to a value of "true";
c) if an <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is included in the SIP re-INVITE request set to "false", and there is an outstanding MCPTT emergency alert for the MCPTT user, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "true"; and
d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
8) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the group to is set to a value of "true", the controlling MCPTT function:
a) shall set the in-progress emergency group state of the group to a value of "false";
b) shall clear the cache of the MCPTT ID of the MCPTT users having an outstanding MCPTT emergency group call;
c) if an <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCPTT emergency alert for the MCPTT user shall:
i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding MCPTT emergency alert; or
ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the sender of the SIP re-INVITE request as having an outstanding MCPTT emergency alert;
d) shall generate SIP re-INVITE requests to the participants in the group call as specified in clause 6.3.3.1.6. The MCPTT controlling function:
i) for each of the other participants in the group call shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
NOTE 3: Clause 6.3.3.1.6 will inform the group call participants of the cancellation of the MCPTT group's in-progress emergency state and the cancellation of the MCPTT emergency alert if applicable.
e) shall stop timer TNG2 (in-progress emergency group call timer); and
NOTE 4: The interactions of TNG2 with the TNG3 (group call timer) are explained in clause 6.3.3.5.2;
f) for each of the affiliated members of the group that are not participating in the call:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
ii) set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false";
iii) if indicated above in step 8) c), set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [4];
9) if the received SIP re-INVITE request contains an imminent peril indication and the in-progress emergency group state of the group is set to a value of "false", shall perform the procedures specified in clause 10.1.1.4.8 and skip the rest of the steps.
Upon receiving a SIP 200 (OK) response to a SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
1) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1;
3) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [22];
4) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
5) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true" and if this is an unauthorised request for an MCPTT emergency alert as determined by clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
6) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCPTT emergency alert cancellation as determined by clause 6.3.3.1.13.3, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
7) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCPTT imminent peril group call and the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCPTT emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority.
8) shall interact with media plane as specified in 3GPP TS 24.380 [5]; and
9) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCPTT client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.18.
Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, the controlling MCPTT function shall handle according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.4.8 Handling of a SIP re-INVITE request for imminent peril session | This procedure is initiated by the controlling MCPTT function as the result of an action in clause 10.1.1.4.7.
In the procedures in this clause:
1) imminent peril indication in an incoming SIP re-INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
When the controlling function receives a SIP re-INVITE request with an imminent peril indication set to "true", the controlling function:
1) if the in-progress emergency state of the group is set to a value of "false" and if the SIP re-INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group to "true", the controlling MCPTT function shall:
NOTE: 1 The calling procedure has already determined that this is not an unauthorised request for an MCPTT imminent peril call, therefore that check does not need to be repeated in the current procedure.
a) if the in-progress imminent peril state of the group is set to a value of "true" and the MCPTT user is indicating a new imminent peril indication:
i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCPTT user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications;
A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
b) if the in-progress imminent peril state of the group is set to a value of "false";
i) set the value of the in-progress imminent peril state of the group to "true";
ii) generate SIP re-INVITE requests for the MCPTT imminent peril group call to participants in the MCPTT group call as specified in clause 6.3.3.1.15;
iii) send the SIP re-INVITES to all of the other participants in the MCPTT group call;
iv) for each of the affiliated members of the group not participating in the group call, generate a SIP MESSAGE request notification of the MCPTT user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications;
A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
c) cache the information that the MCPTT user has initiated an MCPTT imminent peril call;
2) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is an unauthorised request for an MCPTT imminent peril group call cancellation as determined by clause 6.3.3.1.13.6 shall:
a) reject the SIP re-INVITE request with a SIP 403 (Forbidden) response to the SIP re-INVITE request; and
b) include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false";
c) send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4]; and
d) skip the rest of the steps;
3) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is determined to be an authorised request for an MCPTT imminent peril call cancellation as specified in clause 6.3.3.1.13.6 and the in-progress imminent peril state of the group to is set to a value of "true" the controlling MCPTT function shall:
a) set the in-progress imminent peril state of the group to a value of "false";
b) cache the information that the MCPTT user no longer has an outstanding MCPTT imminent peril group call;
c) generate SIP re-INVITES requests to the other participants in the MCPTT group call as specified in clause 6.3.3.1.15. The MCPTT controlling function:
i) for each participant shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 2: Clause 6.3.3.1.15 will inform the affiliated and joined members of the cancellation of the MCPTT group's in-progress emergency state and the cancellation of the MCPTT emergency alert if applicable.
d) for each of the affiliated members of the group not participating in the call shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's imminent peril call as specified in clause 6.3.3.1.11;
ii) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
iii) send the SIP MESSAGE request according to 3GPP TS 24.229 [4];
4) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1;
5) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [22];
6) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
7) shall interact with media plane as specified in 3GPP TS 24.380 [5]; and
8) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response for an outgoing SIP MESSAGE request, shall handle according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5 Non-controlling function of an MCPTT group procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5.1 Originating procedures | This clause describes the procedures for inviting an MCPTT user to an MCPTT session. The procedure is initiated by the non-controlling MCPTT function of an MCPTT group as the result of an action in clause 10.1.1.5.2 or clause 10.1.1.5.5.
The non-controlling MCPTT function:
1) shall invite the MCPTT clients as specified in clause 6.3.4.1.2;
2) shall include in each SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the controlling MCPTT function according to the procedures specified in clause 6.3.4.1.1; and
3) shall send each SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [4].
For each SIP 183 (Session Progress) response received to each SIP INVITE request sent to an MCPTT client, the non-controlling MCPTT function of an MCPTT group:
1) For each SIP 183 (Session Progress) response containing the option tag "100rel", shall send a SIP PRACK request towards the MCPTT client according to 3GPP TS 24.229 [4]; and
2) shall cache the received response;
For each SIP 200 (OK) response received to each SIP INVITE request sent to an MCPTT client, the non-controlling MCPTT function of an MCPTT group:
1) shall send a SIP ACK request towards the MCPTT client according to 3GPP TS 24.229 [4];
2) shall cache the SIP 200 (OK) response;
3) shall start the SIP session timer according to rules and procedures of IETF RFC 4028 [7]; and
4) if at least one of the participants has subscribed to the conference event package, shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.5.2.
On receipt of a SIP 3xx, 4xx, 5xx or 6xx response from an invited MCPTT client, the non-controlling MCPTT function of an MCPTT group:
1) shall send an SIP ACK request towards the MCPTT client as specified in 3GPP TS 24.229 [4];
2) shall remove the cached provisional responses received from the MCPTT client, if any cached provisional responses exists; and
3) if the procedures are initiated by the receipt of the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" as specified in clause 10.1.1.5.2, shall cache the SIP 3xx, 4xx, 5xx or 6xx response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5.2 Terminating procedures | 10.1.1.5.2.1 General
When receiving the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" the MCPTT server can be acting as a controller MCPTT function in an ongoing prearranged group call or, if an prearranged group call is not ongoing, be initiated as an non-controlling MCPTT function and invite MCPTT users.
If a prearranged group call is not ongoing the MCPTT server shall perform the actions specified in clause 10.1.1.5.2.2.
If the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" is received when a prearranged group call is ongoing, the controlling MCPTT function may switch from operating in a controlling MCPTT function mode to operate in a non-controlling MCPTT function mode as specified in clause 10.1.1.5.2.3.
When operating in the non-controlling mode and a SIP BYE request is received from the controlling MCPTT function, the non-controlling MCPTT function shall change from operating in the non-controlling mode to operating in the controlling mode as specified in clause 10.1.1.5.2.4.
10.1.1.5.2.2 Initiating a prearranged group call
Upon receipt of a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" and if a prearranged group call is not ongoing, the non-controlling MCPTT function of an MCPTT group:
NOTE 1: The Contact header field of the SIP INVITE request contains the isfocus media feature tag.
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
4) if the partner MCPTT system does not have a mutual aid relationship with the primary MCPTT system identified by the contents of the P-Asserted-Identity, shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "128 isfocus already assigned" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
5) if a trusted mutual aid relationship exists between the partner MCPTT system and the primary MCPTT system and the procedure in 3GPP TS 23.379 [3] clause 10.6.2.4.2 is supported:
a) shall generate a SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4];
b) shall retrieve the group members of the prearranged group identified by the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request, as specified in clause 6.3.5.2;
c) if the retrieval of group members was successful shall include a P-Refused-URI-List header field populated with affiliated members of the prearranged group in accordance with the IETF RFC 5318 [36]:
d) if the retrieval of group members was not successful, shall include the warning text set to "128 isfocus already assigned" in a Warning header field as specified in clause 4.4; and
e) shall send the SIP 403 (Forbidden) response towards the controlling MCPTT function as specified in 3GPP TS 24.229 [4]; and
f) shall not process the remaining steps;
6) shall retrieve the group document from the group management server for the MCPTT group ID contained in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2 and continue with the rest of the steps if the checks in clause 6.3.5.2 succeed;
7) shall cache the content of the SIP INVITE request, if received in the Contact header field and if the specific feature tags are supported;
8) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
9) determine the members to invite to the prearranged MCPTT group call as specified in clause 6.3.5.5;
10) if the group document retrieved from the group management server contains <on-network-required> group members as specified in 3GPP TS 24.481 [31], shall send a SIP 183 (Session Progress) response to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" as specified in clause 6.3.4.2.2.1 and shall populate the response with an application/vnd.3gpp.mcptt-info+xml MIME body containing the <required> element set to "true".
11) if the group document retrieved from the group management server does not contain any <on-network-required> group members as specified in 3GPP TS 24.481 [31], may, according to local policy, send a SIP 183 (Session Progress) response to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" as specified in clause 6.3.4.2.2.1;
12) shall invite each group member determined in step 9) above, to the group session, as specified in clause 10.1.1.5.1; and
13) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
Unless a SIP response has been sent to the controlling MCPTT function as specified in step 10 or 11 above, the non-controlling MCPTT function of an MCPTT group shall wait for the first SIP provisional response or first SIP 200 (OK) response from one of the invited MCPTT clients, before sending a response to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group".
Upon receiving the first 18x response to a SIP INVITE request sent to an invited MCPTT client as specified in clause 10.1.1.5.1, not containing a P-Answer-State header field, and if a SIP 183 (Session Progress) response has not already been sent in response to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group", the non-controlling MCPTT function of an MCPTT group:
1) shall generate a SIP 183 (Session Progress) response as described in clause 6.3.4.2.2.1; and
2) shall forward the SIP 183 (Session Progress) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receiving the first 18x response to a SIP INVITE request sent to an invited MCPTT client as specified in clause 10.1.1.5.1, containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], a SIP 183 (Session Progress) response has not already been sent in response to the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" and the non-controlling MCPTT function of an MCPTT group supports media buffering, the non-controlling MCPTT function of an MCPTT group:
1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.4.2.2.2 before continuing with the rest of the steps;
2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.4.2.1;
3) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3.5; and
NOTE 2: Resulting media plane processing is completed before the next step is performed.
4) shall send a SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
If the group document does not contain any <on-network-required> group members as specified in 3GPP TS 24.481 [31], then upon receiving the first SIP 200 (OK) response to a SIP INVITE request sent to an invited MCPTT client as specified in clause 10.1.1.5.1, the non-controlling MCPTT function of an MCPTT group:
1) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.4.2.2.2 before continuing with the rest of the steps;
2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.4.2.1;
3) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3.5; and
NOTE 3: Resulting media plane processing is completed before the next step is performed.
4) shall send a SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4];
If the group document contains <on-network-required> group member(s) as specified in 3GPP TS 24.481 [31], then the non-controlling MCPTT function of an MCPTT group shall wait until SIP 200 (OK) responses or SIP 3xx,4xx, 5xx or 6xx responses with a warning text set to "196 user participates under another constituent group" to SIP INVITE requests have been received from all the <on-network-required> MCPTT clients before sending a SIP 200 (OK) response back to the controlling MCPTT function, as specified above.
NOTE 4: The behavior of the non-controlling MCPTT function in the case where not all <on-network-required> MCPTT clients have responded positively to the sent SIP INVITE is beyond the scope of this specification and left to implementation.
If all invited MCPTT clients have rejected SIP INVITE requests with a SIP 3xx, 4xx, 5xx or 6xx response, the non-controlling MCPTT function of an MCPTT group:
1) shall generate a SIP reject response as specified in 3GPP TS 24.229 [4];
2) shall, from the list of reject response codes cached by the non-controlling MCPTT function of an MCPTT group, select the highest prioritized cached reject response code as specified in IETF RFC 3261 [24]; and
3) shall send the reject response towards the controlling MCPTT function as specified in 3GPP TS 24.229 [4].
10.1.1.5.2.3 Joining an ongoing prearranged group call
Upon receipt of a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" and if a prearranged group call is already ongoing, the non-controlling MCPTT function of an MCPTT group:
NOTE 1: The Contact header field of the SIP INVITE request contains the isfocus media feature tag.
1) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the MCPTT emergency group call state is set to either "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "166 constituent group is in an emergency call state" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
NOTE 2: 3GPP TS 23.280 [82] includes the possibility that local policy could allow a constituent group that is in an emergency state to be included in a group regroup; however, the transfer of that emergency state to the group regroup from the constituent group is not supported in the present document.
3) if the partner MCPTT system does not have a mutual aid relationship to merged an ongoing prearranged call with the primary MCPTT system identified by the contents of the P-Asserted-Identity, shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "128 isfocus already assigned" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
4) shall cache the content of the SIP INVITE request, if received in the Contact header field and if the specific feature tags are supported;
5) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
6) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.4.2.2.2 before continuing with the rest of the steps;
7) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.4.2.1;
8) shall instruct the media plane to initialise the switch to non-controlling mode as specified in 3GPP TS 24.380 [5] clause 6.5.2.3.2;
NOTE 3: Resulting media plane processing is completed before the next step is performed. The media plane indicates the state of the floor and if the state is "floor-taken", information about the current speaker.
9) if the media plane provided information about the current speaker, cache the information about the current speaker(s);
10) shall send a SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receipt of the SIP ACK request, the non-controlling MCPTT function of an MCPTT group:
1) if information about a current speaker is cached:
a) shall generate a SIP INFO request as specified in clause 6.3.4.1.3; and
b) shall send the SIP INFO request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4];
2) shall instruct the media plane to finalise the switch to the non-controlling mode as specified in 3GPP TS 24.380 [5] clause 6. 5.2.3.3; and
3) if at least one of the MCPTT clients in the pre-arranged group session has a subscription to the conference event package, shall subscribe to the conference event package from the controlling MCPTT function as specified in clause 10.1.3.5.3.
10.1.1.5.2.4 Splitting an ongoing prearranged group call
Upon receipt of a SIP BYE request or a final SIP reject response from the controlling MCPTT function, the non-controlling MCPTT function of an MCPTT group:
1) if keeping the prearranged group call active is according to the release policy in clause 6.3.8.1, shall request media plane to switch to controlling mode as specified in 3GPP TS 24.380 [5] clause 6.3.5;
NOTE 1: Resulting media plane processing is completed before the next step is performed.
2) if a SIP BYE request was received, shall send a SIP 200 (OK) response to the SIP BYE request; and
3) if keeping the prearranged group call active is according to the release policy in clause 6.3.8.1 and if at least one of the remaining MCPTT clients has subscribed to the conference package, shall send a NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.5.2.
NOTE 2: The SIP NOTIFY request will indicate that all participants, with the exception of the MCPTT users belonging to the constituent MCPTT group hosted by the non-controlling MCPTT function, have left the group session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5.3 Rejoin procedures | 10.1.1.5.3.1 Terminating procedures
Upon receipt of a SIP INVITE request that includes an MCPTT session identity of an ongoing MCPTT session in the Request-URI the non-controlling MCPTT function act as a controlling MCPTT function towards the MCPTT client and shall perform the actions in the clause 10.1.1.4.5.1 with the following clarifications:
1) the MCPTT session identity in the Contact header field of the SIP 200 (OK) response shall be the MCPTT session identity generated by the non-controlling MCPTT function; and
2) the clause 10.1.3.5.2 shall be used when sending the SIP NOTIFY request for subscriptions to the conference event package.
10.1.1.5.3.2 Late call entry initiated by non-controlling MCPTT function
When non-controlling MCPTT function is notified that an MCPTT client is newly affiliated or comes back from out of coverage, the non-controlling MCPTT function shall invite the MCPTT client to join an ongoing MCPTT group call by following the procedures specified in clause 10.1.1.5.1.
NOTE: How the MCPTT function is informed when an MCPTT client is coming back from out of coverage is out of scope of present document. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5.4 void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.5.5 Initiating a temporary group session | Upon receiving a "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" when a prearranged group session is not ongoing, the non-controlling MCPTT-function shall:
NOTE 1: The difference between a "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" and a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" (from the controlling MCPTT function) is that the latter SIP INVITE request contains the isfocus media feature tag in the Contact header field.
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The non-controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
4) shall retrieve the group document from the group management server for the MCPTT group ID contained in the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2 and continue with the rest of the steps, if the checks in clause 6.3.5.2 succeed;
NOTE 2: If the checks are not successful, the SIP response to the "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" is already sent in the clause 6.3.5.2.
5) shall cache the content of the SIP INVITE request;
6) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
7) shall check the authorization of the MCPTT user in the <mcptt-calling-user-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" as specified in clause 6.3.5.4. If the MCPTT user is unauthorized to initiate a pre-arranged group session, the non-controlling MCPTT function shall send a SIP 403 (Forbidden) response with the warning text set to "119 user is not authorised to initiate the group call" in a Warning header field as specified in clause 4.4.
8) if:
a) the MCPTT user identified in the <mcptt-calling-user-id> of the incoming SIP INVITE is not affiliated to the group identity contained in the <associated-group-id> element of the incoming SIP INVITE request as specified in clause 6.3.6;
b) the incoming SIP INVITE request does not contain an emergency indication or an imminent peril indication; or
c) the incoming SIP INVITE request is an authorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2 or for an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5 and the MCPTT user identified in the <mcptt-calling-user-id> of the incoming SIP INVITE is determined to not be eligible for implicit affiliation as specified in clause 9.2.2.3.6;
then shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4, and skip the rest of the steps below;
9) shall generate a SIP INVITE request towards the controlling MCPTT function as specified in clause 6.3.4.1.4; and
10) shall send the SIP INVITE request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the SIP INVITE request sent to the controlling MCPTT function as specified above, the non-controlling MCPTT function:
1) shall send the SIP ACK request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4];
2) shall generate a SIP 200 (OK) to the "SIP INVITE request for controlling MCPTT function of an MCPTT group" as specified in 3GPP TS 24.229 [4] populated as follows:
a) shall include an SDP answer as specified in clause 6.3.4.2.1 based on the SDP answer in the SIP 200 (OK) response;
b) shall include the public service identifier of the non-controlling MCPTT function in the P-Asserted-Identity header field;
c) shall include the warning text set to "148 group is regrouped" in a Warning header field as specified in clause 4.4; and
d) shall send the SIP 200 (OK) request according to 3GPP TS 24.229 [4];
NOTE 3: As long as the MCPTT group is regrouped the floor control messages in the media plane includes a grouped regrouped indication as specified in 3GPP TS 24.380 [5].
3) shall start acting as a non-controlling MCPTT function and interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.5;
4) shall determine the members to invite to the prearranged MCPTT group call as specified in clause 6.3.5.5; and
5) shall invite each group member determined in step 4) immediately above, to the group session, as specified in clause 10.1.1.5.1.
Upon receipt of other final SIP responses with the exception of the SIP 2xx response to the INVITE request sent to the controlling MCPTT function as specified above, the non-controlling MCPTT function:
1) shall send the SIP ACK response to the controlling MCPTT function as specified in 3GPP TS 24.229 [4]; and
2) shall start acting as a controlling MCPTT function as specified in clause 10.1.1.4 and invite members as specified in clause 6.3.4.1.2.
NOTE 4: Regardless if the controlling MCPTT function accepts or rejects the SIP INVITE request sent above, the prearranged group session continues to be initiated with only the members of the group homed on the non-controlling MCPTT function of the group being invited to the group call.
The non-controlling MCPTT function shall handle SIP responses (other than the SIP 2xx response) to the SIP INVITE requests sent to invited members as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to SIP INVITE requests sent to invited members, the non-controlling MCPTT function:
1) shall send the SIP ACK request as specified in 3GPP TS 24.229 [4]; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2 Chat group (restricted) call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.2 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.2.1 On-demand chat group call | 10.1.2.2.1.1 Procedure for initiating a chat MCPTT group call and procedure for joining a chat MCPTT group call
Upon receiving a request from an MCPTT user to initiate or join an MCPTT group call using an MCPTT group identity, identifying a chat MCPTT group, the MCPTT client shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
1) should indicate to the MCPTT user that calls are not allowed on the indicated group; and
2) shall skip the remainder of this procedure.
The MCPTT client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) if the MCPTT user has requested the origination of an MCPTT emergency group call or is originating an MCPTT chat group call and the MCPTT emergency state is already set, the MCPTT client shall comply with the procedures in clause 6.2.8.1.1;
2) if the MCPTT user has requested the origination of an MCPTT imminent peril group call, shall comply with the procedures in clause 6.2.8.1.9;
3) 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" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16];
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 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 INVITE request;
6) 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];
7) should include the "timer" option tag in the Supported header field;
8) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the refresher parameter is omitted. If included, the refresher parameter shall be set to "uac";
9) shall set the Request-URI of the SIP INVITE request to the public service identity identifying the participating MCPTT function serving the MCPTT user;
NOTE 1: The MCPTT client is configured with public service identity identifying the participating MCPTT function serving the MCPTT user.
10) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4];
11) if the MCPTT client emergency group state for this group is set to "MEG 2: in-progress" or "MEG 4: confirm-pending", the MCPTT client shall comply with the procedures in clause 6.2.8.1.2;
12) if the MCPTT client imminent peril group state for this group is set to "MIG 2: in-progress" or "MIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;
13) shall contain an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <session-type> element set to a value of "chat";
b) the <mcptt-request-uri> element set to the group identity;
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the group identity identifies a temporary group or a group regroup based on preconfigured group, the <associated-group-id> element set to the MCPTT group ID of a constituent group the MCPTT client is member of;
NOTE 2: The MCPTT client is informed about temporary groups regrouping MCPTT groups that the user is a member of as specified in 3GPP TS 24.481 [31]. The MCPTT client is informed about regroups based on a preconfigured group of MCPTT groups that the user is member of and affiliated to as specified in clause 16.
NOTE 3: If the MCPTT user selected a TGI or the identity of a group regroup based on a preconfigured group where there are several constituent MCPTT groups where the MCPTT user is a member, the MCPTT client selects one of those MCPTT groups.
e) if the MCPTT client is aware of active functional aliases, and an active functional alias is to be included in the initial SIP INVITE request, the <anyExt> element with the <functional-alias-URI> set to the URI of the used functional alias; and
f) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
NOTE 4: The MCPTT ID of the originating MCPTT user is not included in the body, as this will be inserted into the body of the SIP INVITE request that is sent by the originating participating MCPTT function.
14) shall include in the SIP INVITE request an SDP offer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.2.1;
15) if an implicit floor request is required, shall indicate this as specified in clause 6.4 and
a) 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 include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
16) shall send the SIP INVITE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP INVITE request, the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];
2) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" or the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted", the MCPTT client shall perform the actions specified in clause 6.2.8.1.4; and
3) may subscribe to the conference event package as specified in clause 10.1.3.1.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted"; 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";
the MCPTT client shall perform the actions specified in clause 6.2.8.1.5.
On receiving a SIP INFO request where the Request-URI contains an MCPTT session ID identifying an ongoing group session, the MCPTT client shall follow the actions specified in clause 6.2.8.1.13.
10.1.2.2.1.2 MCPTT client receives SIP re-INVITE request
This clause covers both on-demand session and pre-established sessions.
Upon receipt of a SIP re-INVITE request the MCPTT client:
1) if the SIP re-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":
a) should display to the MCPTT user the MCPTT ID of the originator of the MCPTT emergency group call and an indication that this is an MCPTT emergency group call;
b) if the <mcpttinfo> element containing the <mcptt-Params> element contains an <alert-ind> element set to "true", should display to the MCPTT user an indication of the MCPTT emergency alert and associated information;
c) shall set the MCPTT emergency group state to "MEG 2: in-progress";
d) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril";and
e) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
2) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "true":
a) should display to the MCPTT user the MCPTT ID of the originator of the MCPTT imminent peril group call and an indication that this is an MCPTT imminent peril group call; and
b) shall set the MCPTT imminent peril group state to "MIG 2: in-progress";
3) if the SIP re-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 "false":
a) should display to the MCPTT user the MCPTT ID of the MCPTT user cancelling the MCPTT emergency group call;
b) if the <mcpttinfo> element containing the <mcptt-Params> element contains an <alert-ind> element set to "false":
i) should display to the MCPTT user an indication of the MCPTT emergency alert cancellation and the MCPTT ID of the MCPTT user cancelling the MCPTT emergency alert; and
ii) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body including an <originated-by> element:
A) should display to the MCPTT user the MCPTT ID contained in the <originated-by> element of the MCPTT user that originated the MCPTT emergency alert; and
B) if the MCPTT ID contained in the <originated-by> element is the MCPTT ID of the receiving MCPTT user, shall set the MCPTT emergency alert state to "MEA 1: no-alert";
c) shall set the MCPTT emergency group state to "MEG 1: no-emergency"; and
d) if the MCPTT emergency group call state of the group is set to "MEGC 3: emergency-call-granted", shall set the MCPTT emergency group call state of the group to "MEGC 1: emergency-gc-capable";
4) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false":
a) should display to the MCPTT user the MCPTT ID of the MCPTT user cancelling the MCPTT imminent peril group call and an indication that this is an MCPTT imminent peril group call;
b) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
c) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
5) may check if a Resource-Priority header field is included in the incoming SIP re-INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
6) shall accept the SIP re-INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
7) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP 200 (OK) response;
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 SIP 200 (OK) response;
9) if the SIP re-INVITE request was received within an on-demand session, shall include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.2;
10) if the SIP re-INVITE request was received within a pre-established session, shall include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session; and
NOTE: The SIP re-INVITE request can be received within an on-demand session or a pre-established session associated with an MCPTT group call. If the SIP re-INVITE request is received within a pre-established session, the media-level section for the MCPTT speech media stream and the media-level section of the media-floor control entity are expected to be the same as was negotiated in the existing pre-established session.
11) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
10.1.2.2.1.3 MCPTT in-progress emergency cancel
This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to cancel the in-progress emergency condition on a chat MCPTT group, the MCPTT client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress emergency group state of the MCPTT group as determined by the procedures of clause 6.2.8.1.7, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress emergency group state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall, if the MCPTT user is cancelling an in-progress emergency condition and optionally an MCPTT emergency alert originated by the MCPTT user, include an application/vnd.3gpp.mcptt-info+xml MIME body populated as specified in clause 6.2.8.1.3;
3) shall, if the MCPTT user is cancelling an in-progress emergency condition and optionally an MCPTT emergency alert originated by another MCPTT user, include an application/vnd.3gpp.mcptt-info+xml MIME body populated as specified in clause 6.2.8.1.14;
4) shall, if the SIP re-INVITE request is to be sent within an on-demand session, include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.2.1;
5) if the SIP re-INVITE request is to be sent within a pre-established session, shall include an SDP offer in the SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session;
NOTE 1: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session associated with an MCPTT group call. If the SIP re-INVITE request is sent within a pre-established session, the media-level section for the MCPTT speech media stream and the media-level section of the media-floor control entity are expected to be the same as was negotiated in the existing pre-established session.
6) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; and
7) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP re-INVITE request, the MCPTT client:
1) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency";
2) shall set the MCPTT emergency group call state of the group to "MEGC 1: emergency-gc-capable"; and
3) if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", the sent SIP re-INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body 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 1: no-alert".
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request:
1) shall set the MCPTT emergency group state as "MEG 2: in-progress";
2) if the SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element set to a value of "true" and the sent SIP re-INVITE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
3) if the SIP 4xx response, SIP 5xx response or SIP 6xx response did not contain an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element and did not contain an <originated-by> element, the MCPTT emergency alert (MEA) state shall revert to its value prior to entering the current procedure.
NOTE 3: If the in-progress emergency group state cancel request is rejected, the state of the session does not change, i.e. continues with MCPTT emergency group call level priority.
On receiving a SIP INFO request where the Request-URI contains an MCPTT session ID identifying an ongoing group session, the MCPTT client shall follow the actions specified in clause 6.2.8.1.13.
10.1.2.2.1.4 MCPTT upgrade to in-progress emergency or imminent peril
This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to upgrade the MCPTT group call to an emergency condition or an imminent peril condition on a chat MCPTT group, the MCPTT client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [4], with the clarifications given below.
1) if the MCPTT user is requesting to upgrade the MCPTT group call to an in-progress emergency group state and is not authorised to do so as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to upgrade the MCPTT group call to an in-progress emergency group state; and
b) shall skip the remaining steps of the current clause;
2) if the MCPTT user is requesting to upgrade the MCPTT group session to an in-progress imminent peril state and is not authorised to do so as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to upgrade the MCPTT group call to an in-progress imminent peril group state; and
b) shall skip the remaining steps of the current clause;
3) if the MCPTT user has requested to upgrade the MCPTT group call to an MCPTT emergency call, the MCPTT client:
a) shall include an application/vnd.3gpp.mcptt-info+xml MIME body by following the procedures in clause 6.2.8.1.1; and
b) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2.
4) if the MCPTT user has requested to upgrade the MCPTT group call to an MCPTT imminent peril call, the MCPTT client:
a) shall include an application/vnd.3gpp.mcptt-info+xml MIME body by following the procedures in clause 6.2.8.1.9; and
b) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;
5) if the SIP re-INVITE request is to be sent within an on-demand session, shall include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.2.1;
6) if the SIP re-INVITE request is to be sent within a pre-established session, shall include an SDP offer in the SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session;
NOTE: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session associated with an MCPTT group call. If the SIP re-INVITE request is sent within a pre-established session, the media-level section for the offered MCPTT speech media stream and the media-level section of the offered media-floor control entity are expected to be the same as was negotiated in the existing pre-established session.
7) if an implicit floor request is required, shall indicate this as specified in clause 6.4 and:
a) 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"; and
b) if location information has not yet been included in the SIP re-INVITE request;
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
8) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2; and
9) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP re-INVITE request the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5]; and
2) shall perform the actions specified in clause 6.2.8.1.4.
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request the MCPTT client shall perform the actions specified in clause 6.2.8.1.5.
On receiving a SIP INFO request where the Request-URI contains an MCPTT session ID identifying an ongoing group session, the MCPTT client shall follow the actions specified in clause 6.2.8.1.13.
10.1.2.2.1.5 MCPTT in-progress imminent peril cancel
This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to cancel the in-progress imminent peril condition on a chat MCPTT group, the MCPTT client shall generate a SIP re-INVITE request by following the procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress imminent peril group state of the MCPTT group as determined by the procedures of clause 6.2.8.1.10, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress imminent peril group state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body populated as specified in clause 6.2.8.1.11;
3) shall include a Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;
4) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <session-type> element set to a value of "chat"; and
b) the <mcptt-request-uri> element set to the group identity;
NOTE 1: The MCPTT ID of the originating MCPTT user is not included in the body, as this will be inserted into the body of the SIP re-INVITE request that is sent by the originating participating MCPTT function.
5) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP re-INVITE request according to IETF RFC 3840 [16];
6) if the SIP re-INVITE request is to be sent within an on-demand session, shall include in the SIP re-INVITE request an SDP offer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.2.1;
7) if the SIP re-INVITE request is to be sent within a pre-established session, shall include an SDP offer in the SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session; and
NOTE 2: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session associated with an MCPTT group call. If the SIP re-INVITE request is sent within a pre-established session, the media-level section for the offered MCPTT speech media stream and the media-level section of the offered media-floor control entity are expected to be the same as was negotiated in the existing pre-established session.
8) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP re-INVITE request, the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];
2) shall set the MCPTT imminent peril group state of the group to "MIG 1: no-imminent-peril"; and
3) shall set the MCPTT imminent peril group call state of the group to "MIGC 1: imminent-peril-gc-capable".
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the SIP re-INVITE request:
1) if the SIP 4xx response, SIP 5xx response or SIP 6xx response:
a) contains an application/vnd.3gpp.mcptt-info+xml MIME body with an <imminentperil-ind> element set to a value of "true"; or
b) does not contain an application/vnd.3gpp.mcptt-info+xml MIME body with an <imminentperil-ind> element;
then the MCPTT client shall set the MCPTT imminent peril group state as "MIG 2: in-progress".
NOTE 2: This is the case where the MCPTT client requested the cancellation of the MCPTT imminent peril in-progress state and was rejected.
10.1.2.2.1.6 MCPTT client receives a SIP INVITE request for an MCPTT group call
This procedure is used for MCPTT emergency and MCPTT imminent peril calls when the MCPTT client is affiliated but not joined to the chat group.
In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of an initial SIP INVITE request, the MCPTT client:
1) may reject the SIP INVITE request if either of the following conditions is met:
a) MCPTT client does not have enough resources to handle the call;
b) the number of the maximum simultaneous MCPTT emergency group calls supported for the specific calling functional alias as specified in the <MaxSimultaneousEmergencyGroupCalls> element within the <FunctionalAliasList> list element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) has been reached; or
c) any other reason outside the scope of this specification;
2) if the SIP INVITE request is rejected in step 1), shall respond toward participating MCPTT function either with appropriate reject code as specified in 3GPP TS 24.229 [4] and warning texts as specified in clause 4.4.2 or with SIP 480 (Temporarily unavailable) response not including warning texts if the user is authorised to restrict the reason for failure and skip the rest of the steps of this clause;
NOTE 1: if the SIP INVITE request contains an emergency indication or imminent peril indication, the MCPTT client can by means beyond the scope of this specification choose to accept the request.
3) if the 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":
a) should display to the MCPTT user an indication that this is a SIP INVITE request for an MCPTT emergency group call and:
i) should display the MCPTT ID of the originator of the MCPTT emergency group call contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
ii) should display the MCPTT group identity of the group with the emergency condition contained in the <mcptt-calling-group-id> element; and
iii) if the <alert-ind> element is set to "true", should display to the MCPTT user an indication of the MCPTT emergency alert and associated information;
b) shall set the MCPTT emergency group state to "MEG 2: in-progress";
c) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
d) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable"; otherwise
4) if the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "true":
a) should display to the MCPTT user an indication that this is a SIP INVITE request for an MCPTT imminent peril group call and:
i) should display the MCPTT ID of the originator of the MCPTT imminent peril group call contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) should display the MCPTT group identity of the group with the imminent peril condition contained in the <mcptt-calling-group-id> element; and
b) shall set the MCPTT imminent peril group state to "MIG 2: in-progress";
5) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
6) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
7) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response;
8) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP 200 (OK) response;
9) 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 200 (OK) response;
10) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [7]. If no "refresher" parameter was included in the received SIP INVITE request the "refresher" parameter in the Session-Expires header field shall be set to "uas", otherwise shall include a "refresher" parameter set to the value received in the Session-Expires header field the received SIP INVITE request;
11) shall include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.2;
12) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4];
13) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
14) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing an <mcptt-Params> element containing an <anyExt> element which includes a <functional-alias-URI> element, may display to the MCPTT user the functional alias of the inviting MCPTT user. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.2.2 Chat group call within a pre-established session | 10.1.2.2.2.1 Procedure for initiating a chat MCPTT group call and procedure for joining a chat MCPTT group call
Upon receiving a request from an MCPTT user to initiate or join an MCPTT group call using an MCPTT group identity identifying a chat MCPTT group within the pre-established session, the MCPTT client shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
1) should indicate to the MCPTT user that calls are not allowed on the indicated group; and
2) shall skip the remainder of this procedure.
The MCPTT client shall generate a SIP REFER request outside a dialog as specified in IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27], and in accordance with the UE procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) shall set the Request URI of the SIP REFER request to the session identity of the pre-established session;
2) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20], and with the Content-ID header field set to this "cid" URL;
3) shall include in the application/resource-lists+xml MIME body a single <entry> element in a <list> element in the <resource-lists> element where the <entry> elment contains a "uri" attribute set to the chat group identity, extended with the following parameters in the headers portion of the SIP URI:
NOTE 1: Characters that are not formatted as ASCII characters are escaped in the following parameters in the headers portion of the SIP URI.
a) the 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];
b) 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]; and
c) an hname "body" parameter populated with:
i) an application/sdp MIME body containing an SDP offer, if the session parameters of the pre-established session require modification or if implicit floor control is required, according to the conditions specified in clause 6.4;
ii) an application/vnd.3gpp.mcptt-info MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
A) the <session-type> element set to a value of "chat";
B) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
C) if the chat group identity identifies a temporary group or a group regroup based on preconfigured group, the <associated-group-id> element set to the MCPTT group ID of a constituent group the MCPTT client is member of;
NOTE 2: The MCPTT client is informed about temporary groups regrouping MCPTT groups that the user is a member of as specified in 3GPP TS 24.481 [31]. The MCPTT client is informed about regroups based on a preconfigured group of MCPTT groups that the user is member of and affiliated to as specified in clause 16.
NOTE 3: If the MCPTT user selected a TGI or the identity of a group regroup based on a preconfigured group where there are several constituent MCPTT groups where the MCPTT user is a member, the MCPTT client selects one of those MCPTT groups.
D) if the MCPTT client is aware of active functional aliases, and an active functional alias is to be included in the SIP REFER request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
E) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value; and
iii) if:
A) implicit floor control is required; and
B) an application/vnd.3gpp.mcptt-info MIME body with 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";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
NOTE 4: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
4) if the MCPTT user has requested the origination of an MCPTT emergency group call or is originating an MCPTT group call and the MCPTT emergency state is already set:
a) if this is an authorised request for an MCPTT emergency group call as determined by the procedures of clause 6.2.8.8.1.8, shall comply with the procedures in clause 6.2.8.1.1; and
b) if this is an unauthorised request for an MCPTT emergency group call as determined in step a) above, should indicate to the MCPTT user that they are not authorised to initiate an MCPTT emergency group call;
5) if the MCPTT client emergency group state for this group is set to "MEG 2: in-progress" or "MEG 4: confirm-pending", shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2;
6) if the MCPTT user has requested the origination of an MCPTT imminent peril group call:
a) if this is an authorised request for an MCPTT imminent peril group call as determined by the procedures of clause 6.2.8.8.1.8, shall comply with the procedures in clause 6.2.8.1.9; and
b) if this is an unauthorised request for an MCPTT imminent peril group call as determined in step a) above, should indicate to the MCPTT user that they are not authorised to initiate an MCPTT imminent peril group call;
7) if the MCPTT client imminent peril group state for this group is set to "MIG 2: in-progress" or "MIG 4: confirm-pending" shall include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.12;
8) shall include a P-Preferred-Service header field set to the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), according to IETF RFC 6050 [9];
9) shall include the following according to IETF RFC 4488 [22]:
a) the option tag "norefersub" in the Supported header field; and
b) the value "false" in the Refer-Sub header field.
10) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session;
11) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP REFER request according to IETF RFC 3840 [16]; and
12) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
On receiving a final SIP 2xx response to the SIP REFER request, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
On receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP REFER request:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted"; 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";
the MCPTT client shall perform the actions specified in clause 6.2.8.1.5 and shall skip the remaining steps.
On receiving 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) shall perform the actions specified in clause 6.2.8.1.16;
2) shall check if a Resource-Priority header field is included in the incoming SIP re-INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
3) shall accept the SIP re-INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
4) shall include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session; and
5) shall send the SIP 200 (OK) response towards the participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4].
On call release by interaction with the media plane as specified in clause 9.2.2 of 3GPP TS 24.380 [5] 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 shall perform the procedures specified in clause 6.2.8.1.17.
On receiving a SIP INFO request where the Request-URI contains an MCPTT session ID identifying an ongoing group session, the MCPTT client shall follow the actions specified in clause 6.2.8.1.13. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.2.3 End group call | 10.1.2.2.3.1 Client originating procedures on-demand
When an MCPTT client wants to leave the MCPTT session that has been established using on-demand session, the MCPTT client shall follow the procedures as specified in clause 6.2.4.1 and if the MCPTT session is an MCPTT emergency group call or an MCPTT imminent peril group call, the MCPTT client shall perform the procedures specified in clause 6.2.8.1.17.
10.1.2.2.3.2 Client originating procedures using pre-established session
When an MCPTT client wants to leave the MCPTT session within a pre-established session, the MCPTT client shall follow the procedures as specified in clause 6.2.4.2 and if the MCPTT session is an MCPTT emergency group call or an MCPTT imminent peril group call, the MCPTT client shall perform the procedures specified in clause 6.2.8.1.17.
10.1.2.2.3.3 Client terminating procedures
Upon receiving a SIP BYE request for releasing the MCPTT chat session, the MCPTT client shall follow the procedures as specified in clause 6.2.6 and if the MCPTT session is an MCPTT emergency group call or an MCPTT imminent peril group call, the MCPTT client shall perform the procedures specified in clause 6.2.8.1.17. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.3.1 On-demand chat group call | 10.1.2.3.1.1 MCPTT chat session establishment
In the procedures in this clause:
1) group identity in an incoming SIP INVITE request refers to the group identity from the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
3) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP INVITE request for originating participating MCPTT function" for a group identity identifying a chat MCPTT group containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "chat", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to accept the request.
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if through local policy in the originating participating MCPTT function, the user identified by the MCPTT ID is not authorised to make chat group calls, shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "108 user not authorised to make chat group calls" in a Warning header field as specified in clause 4.4;
4) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
5) shall check if the number of maximum simultaneous MCPTT group calls supported for the MCPTT user as specified in the <MaxSimultaneousCallsN6> 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]) has been exceeded. If exceeded, the MCPTT function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCPTT group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps;
NOTE 3: If the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to allow for an exception to the limit for the maximum simultaneous MCPTT sessions supported for the MCPTT user.
6) if the user identified by the MCPTT ID is not affiliated to the group identified in the <mcptt-request-uri> or in <associated-group-id> element of the "SIP INVITE request for originating participating MCPTT function" as determined by clause 9.2.2.2.11, shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation; and
7) if the actions for implicit affiliation specified in step 6) above were performed but not successful in affiliating the MCPTT user due to the MCPTT user already having N2 simultaneous affiliations (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile), shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps.
NOTE 4: N2 is the total number of MCPTT groups that an MCPTT user can be affiliated to simultaneously as specified in 3GPP TS 23.379 [3].
NOTE 5: If the SIP INVITE request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to allow an exception to the N2 limit (specified in the <MaxAffiliationsN2> element of the <Common> element of the MCPTT user profile of the served MCPTT ID). Alternatively, a lower priority affiliation of the MCPTT user could be cancelled to allow for the new affiliation.
If the incoming SIP INVITE request does not contain an <associated-group-id> element, then the group identity contained in the <mcptt-request-uri> element is determined not to be a TGI or the identity of a group regroup based on a preconfigured group and the participating MCPTT function:
1) shall determine the public service identity of the controlling MCPTT function associated with the group identity in the SIP INVITE request. If the participating MCPTT function is unable to identify the 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 6: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 7: 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 8: 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 9: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 10: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
2) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3;
3) shall set the Request-URI to the public service identity of the controlling MCPTT function determined in step 1);
4) shall include the MCPTT ID of the calling user in <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request;
11a) if the received SIP request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, then check if the status of the functional alias is activated for the MCPTT ID. If the functional alias status is activated, then set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request to the received value, if the status is unequal activated then do not include a <functional-alias-URI> element;
NOTE 11: The participating MCPTT server learns the functional alias state for an MCPTT ID from procedures specified in clause 9A.2.2.2.7.
5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request as specified in clause 6.3.2.1.1.1;
6) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in Annex F.3;
a) if not already included, shall include a Content-Type header field set to "application/vnd.3gpp.location-info+xml"; and
b) if not already copied, shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body received in the SIP INVITE request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP request;
NOTE 12: Note that the application/vnd.3gpp.mcptt-info+xml MIME body will already have been copied into the outgoing SIP INVITE request by clause 6.3.2.1.3.
7) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource-Priority header field according to rules and procedures of IETF RFC 4412 [29] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCPTT client;
NOTE 13: The participating MCPTT function will leave verification of the Resource-Priority header field to the controlling MCPTT function.
8) if according to clause 6.4, the SIP INVITE request is regarded as being received with an implicit request to grant the floor to the originating MCPTT client:
if:
a) 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) 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";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP INVITE request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has available the location of the originating MCPTT client available; and
b) 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";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
9) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
If incoming SIP INVITE request contains an <associated-group-id> element, then the group identity contained in the <mcptt-request-uri> element is determined to be a TGI or the identity of a group regroup based on a preconfigured group and the participating MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10;
2) shall include an SDP offer based upon the SDP offer in the received SIP INVITE request from the MCPTT client as specified in clause 6.3.2.1.1.1; and
3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP INVITE request, the participating MCPTT function:
1) void;
2) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2 with the clarification that if an <MKFC-GKTPs> element was contained in the received SIP 2xx response it is not included in the generated SIP 200 (OK) response;
NOTE 14: If an <MKFC-GKTPs> element is received in a SIP 2xx response, the participating MCPTT function essentially ignores it and does not forward it, resulting in unicast media plane transmission being used for the originating client.
3) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
4) shall include Warning header field(s) that were received in the incoming 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 function;
6) shall include an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response;
7) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13;
8) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4];
9) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [7].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request, the participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response;
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4]; and
4) if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in the current procedure, shall perform the procedures of clause 9.2.2.2.14.
10.1.2.3.1.2 Reception of a SIP re-INVITE request from served MCPTT client
This clause covers both on-demand session and pre-established sessions.
Upon receipt of a SIP re-INVITE request for a served MCPTT client of a chat MCPTT group, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true", the participating MCPTT function may by means beyond the scope of this specification choose to accept the request.
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
NOTE 2: If the received SIP re-INVITE request is received within a pre-established session associated with an MCPTT group call, the media-level section for the offered MCPTT speech media stream and the media-level section of the offered media-floor control entity are expected to be the same as was negotiated in the existing pre-established session.
3) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.1.9;
4) shall include the MCPTT ID of the originating user in <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request;
5) shall, if the SIP re-INVITE request was received within an on-demand session, include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.1.1.1;
6) shall, if the SIP re-INVITE request was received within a pre-established session, include in the SIP re-INVITE request an SDP offer based upon the previously negotiated SDP for the pre-established session as specified in clause 6.3.2.1.1.2;
7) 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; and
NOTE 3: The controlling MCPTT function will determine the validity of the Resource-Priority header field.
8) shall forward the SIP re-INVITE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP re-INVITE request in step 7) the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2;
2) if the SIP 200 (OK) response is to be sent within an on-demand session, shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
3) if the SIP 200 (OK) response is to be sent within a pre-established session shall include in the SIP 200 (OK) response an SDP answer based upon the previously negotiated SDP for the pre-established session;
4) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response; and
5) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4];
Upon receipt of a SIP 403 (Forbidden) response to the sent SIP re-INVITE request the participating MCPTT function:
1) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [4];
2) shall copy, if included in the received SIP 403 (Forbidden) response, the application/vnd.3gpp.mcptt-info+xml MIME body MIME body to the outgoing SIP (Forbidden) response;
3) shall include Warning header field(s) that were received in the incoming SIP 403 (Forbidden) response; and
4) shall forward the SIP 403 (Forbidden) response to the MCPTT client according to 3GPP TS 24.229 [4];
10.1.2.3.1.3 Reception of a SIP INVITE request for terminating MCPTT client
This clause covers both on-demand session and pre-established sessions.
Upon receipt of a "SIP INVITE request for terminating participating MCPTT function", for a terminating MCPTT client of a chat MCPTT group, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: If the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true", the participating MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall check the presence of the isfocus media feature tag in the Contact header field and if it is not present then the participating MCPTT function shall reject the request with a SIP 403 (Forbidden) response with the warning text set to "104 isfocus not assigned" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps;
3) void;
NOTE 2: If an <MKFC-GKTPs> element is received in a SIP INVITE request, the participating MCPTT function essentially ignores it and does not forward it, resulting in unicast media plane transmission being used for the terminating client.
4) if:
a) the invited MCPTT client has a pre-established session without an associated MCPTT call such that:
i) 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
ii) 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 may according to local policy perform the actions specified in clause 10.1.2.3.2.2 and skip the remaining steps of the current procedure;
5) shall generate a SIP INVITE request as specified in clause 6.3.2.2.3;
6) shall set the Request-URI to the public user identity associated with the MCPTT ID of the MCPTT user to be invited based on the contents of the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the received "SIP INVITE request for terminating participating MCPTT function";
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;
10) shall perform the procedures specified in clause 6.3.2.2.9 to include any MIME bodies in the received SIP INVITE request; and
11) shall send the SIP INVITE request towards the MCPTT client 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) 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 interact with the media plane as specified in 3GPP TS 24.380 [5]; and
4) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [4].
10.1.2.3.1.4 Reception of a SIP re-INVITE request for terminating MCPTT client
This clause covers both on-demand session and pre-established sessions.
Upon receipt of a SIP re-INVITE request for a terminating MCPTT client of a chat MCPTT group, the participating MCPTT function:
1) shall check if a Resource-Priority header field is included in the incoming SIP re-INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
2) if the outgoing SIP re-INVITE request will be sent in the dialog of a pre-established session, perform the actions in clause 10.1.2.3.2.2 and skip the remaining steps of the current procedure;
3) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.2.10;
4) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in 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 200 (OK) response to the above SIP re-INVITE request sent to the MCPTT client, 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; and
3) shall forward the SIP 200 (OK) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.3.2 Chat group call within a pre-established session | 10.1.2.3.2.1 MCPTT chat session establishment
Upon receipt of a "SIP REFER request for a pre-established session", with:
1) the Refer-To header containing a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20] containing a <resource-lists> element that contains a <list> element that contains an <entry> element with a "uri" attribute containing a SIP URI set to a chat group identity;
2) an hname "body" parameter in the headers portion of the SIP URI specified above containing an application/vnd.3gpp.mcptt-info MIME body with the <session-type> element set to "chat"; and
3) a Content-ID header field set to the "cid" URL;
the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP REFER request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall not continue with the rest of the steps;
NOTE 1: If the application/vnd.3gpp.mcptt-info MIME body included in the SIP REFER request as described at the top of the present clause contains an <emergency-ind> element or <imminentperil-ind> element set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to accept the request.
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP REFER request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP REFER request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4and shall not continue with any of the remaining steps;
4) if through local policy in the participating MCPTT function, the user identified by the MCPTT ID is not authorised to make chat group calls, shall reject the SIP REFER request with a SIP 403 (Forbidden) response to the SIP REFER request, with warning text set to "108 user not authorised to make group calls" in a Warning header field as specified in clause 4.4.2;
5) shall retrieve the group identity in the "uri" attribute within the <entry> element of a <list> element within the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL contained in the Refer-To header field of the SIP REFER request;
6) shall check if the number of maximum simultaneous MCPTT group calls supported for the MCPTT user as specified in the <MaxSimultaneousCallsN6> 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]) has been exceeded. If exceeded, the participating MCPTT function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCPTT group calls reached" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
NOTE 3: If the SIP REFER request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to allow for an exception to the limit for the maximum simultaneous MCPTT sessions supported for the MCPTT user.
7) if received SIP REFER request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.2.1.8.3;
8) if the SIP REFER request contains in the application/vnd.3gpp.mcptt-info+xml MIME body:
a) an <emergency-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT emergency group call as determined by clause 6.3.2.1.8.1;
b) an <alert-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as determined by clause 6.3.2.1.8.2; or
c) an <imminentperil-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT imminent peril group call as determined by clause 6.3.2.1.8.1;
then shall reject the SIP REFER request with a SIP 403 (Forbidden) response and skip the rest of the steps;
9) if the user identified by the MCPTT ID is not affiliated to the group identified in the SIP REFER request or in the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined by clause 9.2.2.2.11, shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation;
10) if the actions for implicit affiliation specified in step 9) above were performed but not successful in affiliating the MCPTT user due to the MCPTT user already having N2 simultaneous affiliations (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile), shall reject the SIP REFER request with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps;
NOTE 4: N2 is the total number of MCPTT groups that an MCPTT user can be affiliated to simultaneously as specified in 3GPP TS 23.379 [3].
NOTE 5: If the SIP REFER request contains an emergency indication set to a value of "true" or an imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1, the participating MCPTT function can according to local policy choose to allow an exception to the N2 limit (specified in the <MaxAffiliationsN2> element of the <Common> element of the MCPTT user profile of the served MCPTT ID). Alternatively, a lower priority affiliation of the MCPTT user could be cancelled to allow for the new affiliation.
11) shall generate a final SIP 200 (OK) response to the "SIP REFER request for a pre-established session" according to 3GPP TS 24.229 [4];
12) if the "SIP REFER request for a pre-established session" contained a Refer-Sub header field containing the value "false" 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;
If the incoming SIP REFER request does not contain an <associated-group-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body, then the group identity contained in the application/resource-lists MIME body is determined not to be a TGI or the identity of a group regroup based on a preconfigured group and the participating MCPTT function:
1) shall determine the public service identity of the controlling MCPTT function associated with the group identity in the "uri" attribute within the <entry> element of a <list> element within the <resource-lists> element in the application/resource-lists+xml MIME body pointed to by the "cid" URL in the Refer-To header field of the SIP REFER request. If the participating MCPTT function is unable to identify the controlling MCPTT function associated with the group identity, it shall reject the REFER 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 the remaining steps;
NOTE 6: The public service identity can identify the controlling function in the primary MCPTT system or in a partner MCPTT system.
NOTE 7: 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 8: 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 9: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 10: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
2) shall send the SIP 200 (OK) response to the SIP REFER request towards the MCPTT client according to 3GPP TS 24.229 [4];
NOTE 11: 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.
3) shall generate a SIP INVITE request as specified in clause 6.3.2.1.4;
4) shall set the Request-URI of the SIP INVITE request to the public service identity of the controlling MCPTT function determined in step 13);
5) shall copy the group identity from the "uri" attribute of the <entry> element of a <list> element within the <resource-lists> element of the application/resource-lists+xml MIME body pointed to by the "cid" URL in the Refer-to header field of the SIP REFER request, to the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request;
6) if the received SIP REFER request contained a Resource-Priority header field, shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [4] set to the value indicated in the Resource-Priority header field of the received SIP REFER request from the MCPTT client;
7) 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 initiating MCPTT client:
if:
a) 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) 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";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP REFER request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has available the location of the initiating MCPTT client; and
b) 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";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
8) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
If incoming SIP REFER request contains an <associated-group-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body, then the group identity contained in the application/resource-lists MIME body is determined to be a TGI or the identity of a group regroup based on a preconfigured group and the participating MCPTT function:
1) shall send the SIP 200 (OK) response to the SIP REFER request towards the MCPTT client according to 3GPP TS 24.229 [4];
2) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10;
3) shall set the Request-URI of the SIP INVITE request to the public service identity of the non-controlling MCPTT function associated with the group identity contained in the <associated-gourp-id> element of the incoming SIP REFER request;
4) shall copy the group identity from the "uri" attribute of the <entry> element of the application/resource-lists MIME body pointed to by the "cid" URL in the Refer-to header field of the SIP REFER request, to the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request;
5) if the received SIP REFER request contained a Resource-Priority header field, shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [4] set to the value indicated in the Resource-Priority header field of the received SIP REFER request from the MCPTT client; and
6) shall include in the SIP INVITE request an SDP offer based upon the SDP offer negotiated during the pre-established session establishment, any subsequent pre-established session modification and the SDP offer (if any) included in the hname "body" parameter in the headers portion of the SIP URI contained in the <entry> 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 from the MCPTT client;
7) 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 initiating MCPTT client:
if:
a) 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) 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";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP REFER request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has available the location of the initiating MCPTT client; and
b) 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";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
8) shall send the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP INVITE request in step 19) the participating MCPTT function shall follow procedures specified in 3GPP TS 24.229 [4], with the clarifications given below:
1) shall cache the contact received in the Contact header field;
2) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13;
3) if the received SIP 2xx response was in response to a request for an MCPTT group call containing 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 and 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) shall generate a SIP re-INVITE request to be sent towards the MCPTT client within the pre-established session as specified in clause 6.3.2.1.8.5; and
b) shall send the SIP re-INVITE request to the MCPTT client according to 3GPP TS 24.229 [4]; and
4) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
NOTE 12: There are two cases covered in the handling of the received SIP 2xx response above. The first case is when the SIP INVITE request sent to the controlling MCPTT function contained a Resource-Priority header field populated appropriately to request emergency level or imminent peril level priority but did not contain in the application/vnd.3gpp.mcptt-info+xml MIME body either an <emergency-ind> element or an <imminentperil-ind> element. The second case is when the SIP INVITE request sent to the controlling MCPTT function contained a Resource-Priority header field and contained either an <emergency-ind> element or an <imminentperil-ind> element. In either case, the received SIP 2xx response did not warn of a pending SIP INFO request.
Upon receiving 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 send a SIP 200 (OK) response to the SIP INFO request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4];
2) shall generate a SIP re-INVITE request to be sent towards the MCPTT client within the pre-established session as specified in clause 6.3.2.1.8.5; and
3) shall send the SIP re-INVITE request to the MCPTT client according to 3GPP TS 24.229 [4].
NOTE 13: This is the case where the SIP REFER request previously received from the MCPTT client 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 but was also a request for either an MCPTT emergency group call or an MCPTT imminent peril group call.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request sent to the controlling MCPTT function, the participating MCPTT function:
1) if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in the present clause, shall perform the procedures of clause 9.2.2.2.14; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
10.1.2.3.2.2 MCPTT chat session establishment for terminating user within a pre-established session
NOTE 1: If an <MKFC-GKTPs> element is received in a SIP INVITE request, the participating MCPTT function essentially ignores it and does not forward it, resulting in unicast media plane transmission being used for the terminating client.
Upon receipt of a SIP INVITE request or a SIP re-INVITE request for a terminating MCPTT client of a chat MCPTT group using a pre-established session, the participating MCPTT function:
1) shall generate an outgoing SIP re-INVITE request as specified in clause 6.3.2.2.10 to be sent within the dialog of the pre-established session;
2) if the received SIP INVITE request or 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;
3) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request or SIP re-INVITE request as specified in clause 6.3.2.1.1.2; and
NOTE 2: The media-level section for the offered MCPTT speech media stream and the media-level section of the offered media-floor control entity are expected to be the same as in the existing pre-established session as per the conditions for pre-established session usage specified in clause 10.1.2.3.1.3.
4) shall send the SIP re-INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the above SIP re-INVITE request sent to the MCPTT client, 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 as specified in clause 6.3.2.2.2.2; and
3) shall send the SIP 200 (OK) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.3.3 End group call at the originating participating MCPTT function | 10.1.2.3.3.1 Receipt of SIP BYE request for ending on-demand chat session
Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6.
10.1.2.3.3.2 Receipt of SIP REFER "BYE" request for ending chat session using pre-established session
Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.3.4 End group call at the terminating participating MCPTT function | 10.1.2.3.4.1 Receipt of SIP BYE request for on-demand chat session
Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
10.1.2.3.4.2 Receipt of SIP BYE request for ongoing pre-established session
Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.4 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.4.1 On-demand chat group call | 10.1.2.4.1.1 Procedure for establishing an MCPTT chat session and procedure for joining an established MCPTT chat session
In the procedures in this clause:
1) MCPTT ID in an incoming SIP INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) group identity in an incoming SIP INVITE request refers to the group identity from the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
3) MCPTT ID in an outgoing SIP INVITE request refers to the MCPTT ID of the called user in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request;
4) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
5) alert indication in an incoming SIP INVITE request refers to the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP INVITE request for controlling MCPTT function of an MCPTT group" containing a group identity identifying a chat MCPTT group, the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: If the SIP INVITE request contains an emergency indication set to a value of "true", the controlling MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag;
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; or
c) the isfocus media feature tag is present in the Contact header field;
3) if received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17;
4) if the group identity is associated with a group document maintained by the GMS:
NOTE 2: How the MCPTT server determines that a group identity represents a group for which a group document is stored in the GMS is implementationspecific.
a) shall retrieve the necessary group document(s) from the group management server for the group identity contained in the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2;
b) if the group document contains a <list -service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 and skip the rest of the steps;
c) if the group referred to by the group identity has been regrouped:
i) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "148 group is regrouped" as specified in clause 4.4 "Warning header field";
ii) if the group referred to by the group identity has been regrouped based on a preconfigured group, shall send a copy of the notifying SIP MESSAGE that was generated and sent per clause 16.2.4.1 to the participating function for the MCPTT ID of the incoming SIP INVITE request; and
iii) shall skip the rest of the steps;
d) if the result of the initial processing in clause 6.3.5.2 was that a SIP 4xx, 5xx or 6xx response to the "SIP INVITE request for controlling MCPTT function of an MCPTT group" has been sent, do not continue with the rest of the steps in this clause;
5) if the group identity is associated with a user or group regroup based on a preconfigured group:
a) shall retrieve the stored information for the group identity;
b) if there is no stored information for the group identity, the controlling MCPTT function:
i) shall return a SIP 404 (Not Found) response with the warning text set to "163 the group identity indicated in the request does not exist" as specified in clause 4.4 "Warning header field" and shall not continue with the rest of the steps;
NOTE 3: The user or group regroup can have been removed very recently and the client has sent the group call request prior to receiving the removal notification.
5a) if the group identity is associated with a TGI or the identity of a group regroup based on a preconfigured group and the received SIP INVITE request does not include an <mcptt-calling-group-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall return a SIP 403 (Forbidden) response to "SIP INVITE request for controlling MCPTT function of an MCPTT group".
6) if the MCPTT user identified by the MCPTT ID in the SIP INVITE request is not affiliated with the MCPTT group identified by the group identity in the SIP INVITE request as determined by the procedures of clause 6.3.6:
a) if the MCPTT user is eligible to be implicitly affiliated with the MCPTT chat group as determined by clause 9.2.2.3.6; and
b) if the group identity contained in an <mcptt-calling-group-id> element of the SIP INVITE request is not a constituent MCPTT group ID;
NOTE 4: If the SIP INVITE is for a temporary group or a group regroup based on preconfigured group, the affiliation of the calling user to the constituent group has been assured by the non-controlling MCPTT function of the constituent group before forwarding this SIP INVITE to the controlling function of the regroup.
, then shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
7) if the SIP INVITE request contains unauthorised request for an MCPTT emergency group call as determined by clause 6.3.3.1.13.2:
a) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response as specified in clause 6.3.3.1.14; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
8) if the SIP INVITE request contains an unauthorised request for an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.6, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
9) if a Resource-Priority header field is included in the SIP INVITE request:
a) if the Resource-Priority header field is set to the value indicated for emergency calls and the SIP INVITE request does not contain an emergency indication and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the remaining steps; and
b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the SIP INVITE request does not contain an imminent peril indication and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response; and skip the remaining steps;
10) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps;
11) if the chat group session is not ongoing then:
a) shall create a chat group session and allocate an MCPTT session identity for the chat group session, and may handle timer TNG3 (group call timer) as specified in clause 6.3.3.5;
b) if the group identity in the "SIP INVITE request for controlling MCPTT function of an MCPTT group" is a TGI or the identity of a group regroup based on a preconfigured group:
i) shall, for each of the constituent MCPTT groups except for the calling MCPTT group identified in the <mcptt-calling-group-id> element of the incoming SIP INVITE, generate a SIP INVITE request towards the MCPTT non-controlling function that owns the constituent MCPTT group identity by following the procedures in clause 10.1.2.4.1.1A;
12) if the chat group session is ongoing and the <on-network-max-participant-count> as specified in 3GPP TS 24.481 [31] is already reached:
a) if, according to local policy, the user identified by the MCPTT ID in the SIP INVITE request is deemed to have a higher priority than an existing user in the chat group session, may remove a participant from the session by following clause 10.1.1.4.4.3, and skip the next step; and
NOTE 5: The local policy for deciding whether to admit a user to a call that has reached its maximum amount of participants can include the <user-priority> and the <participant-type> of the user as well as other information of the user from the group document as specified in 3GPP TS 24.481 [31]. The local policy decisions can also include taking into account whether the imminent-peril indicator or emergency indicator was received in the SIP INVITE request.
b) shall return a SIP 486 (Busy Here) response with the warning text set to "122 too many participants" to the originating network as specified in clause 4.4 Otherwise, continue with the rest of the steps;
13) if the received SIP INVITE request was determined to be eligible for implicit affiliation in step 5) and if clause 9.2.2.3.7 was not previously invoked in the present clause, shall perform the implicit affiliation as specified in clause 9.2.2.3.7;
14) if the SIP INVITE request contains an emergency indication set to a value of "true" or the in-progress emergency state of the group to "true" the controlling MCPTT function shall:
a) validate that the SIP INVITE request includes a Resource-Priority header field populated with the values for an MCPTT emergency group call as specified in clause 6.3.3.1.19, and if not:
i) perform the actions specified in clause 6.3.3.1.8;
ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP INVITE request according to 3GPP TS 24.229 [4]; and
iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8, proceed with the rest of the steps.
NOTE 6: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress emergency states of the specified group.
b) if the in-progress emergency state of the group is set to a value of "true" and the MCPTT user is indicating a new emergency indication:
i) for each of the other affiliated members of the group generate a SIP MESSAGE request notification of the MCPTT user's emergency indication as specified in clause 6.3.3.1.11 with the following clarifications:
A) set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true";
B) if the received SIP INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCPTT emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and
C) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
ii) cache the information that the MCPTT user has initiated an MCPTT emergency call; and
iii) if the SIP INVITE request contains an authorised request for an MCPTT emergency alert as determined in step i) B) above, cache the information that the MCPTT user has initiated an MCPTT emergency alert; and
c) if the in-progress emergency state of the group is set to a value of "false":
i) shall set the value of the in-progress emergency state of the group to "true";
ii) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16;
iii) shall generate SIP re-INVITE requests for the MCPTT emergency group call to the other affiliated and joined participants of the chat MCPTT group as specified in clause 6.3.3.1.6;
iv) shall generate SIP INVITE requests for the MCPTT emergency group call to the affiliated but not joined members of the chat MCPTT group as specified in clause 6.3.3.1.7;
A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
v) shall cache the information that the MCPTT user has initiated an MCPTT emergency call; and
vi) if the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is set to "true" and is an authorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall cache the information that the MCPTT user has initiated an MCPTT emergency alert; and
vii) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false";
15) if the in-progress emergency state of the group is set to a value of "false" and if the SIP INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group is set to "true", the controlling MCPTT function shall:
a) validate that the SIP INVITE request includes a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.3.3.1.19, and if not:
i) perform the actions specified in clause 6.3.3.1.8;
ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP INVITE request according to 3GPP TS 24.229 [4]; and
iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 proceed with the rest of the steps.
NOTE 7: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress imminent peril states of the specified group.
b) if the in-progress imminent peril state of the group is set to a value of "true" and the MCPTT user is indicating a new imminent peril indication:
i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCPTT user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications;
A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
ii) cache the information that the MCPTT user has initiated an MCPTT imminent peril call; and
c) if the in-progress imminent peril state of the group is set to a value of "false":
i) shall set the value of the in-progress imminent peril state of the group to "true";
ii) shall generate SIP re-INVITE requests for the MCPTT imminent peril group call to the other affiliated and joined participants of the chat MCPTT group as specified in clause 6.3.3.1.15;
iii) shall generate SIP INVITE requests for the MCPTT imminent peril call to the affiliated but not joined members of the chat MCPTT group as specified in clause 6.3.3.1.7;
A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
iv) shall cache the information that the MCPTT user has initiated an MCPTT imminent peril call;
16) shall accept the SIP request and generate a SIP 200 (OK) response to the SIP INVITE request according to 3GPP TS 24.229 [4];
17) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 13)a) or step 14)a) above;
18) should include the Session-Expires header field and start supervising the SIP session 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";
19) shall include the "timer" option tag in a Require header field;
20) shall include the following in a 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 MCPTT session identity; and
d) the media feature tag isfocus;
21) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
22) if the SIP INVITE request contains an alert indication set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
23) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true" and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
NOTE 8: In this case, the request was for an imminent peril call but a higher priority MCPTT emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority.
24) shall interact with media plane as specified in 3GPP TS 24.380 [5];
25) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4]; and
26) if the chat group session was already ongoing and if at least one of the participants has subscribed to the conference event package, shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.4.2.
Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCPTT client or towards the inviting non-controlling MCPTT function, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.18.
a) 10.1.2.4.1.1A SIP INVITE targeted to the non-controlling MCPTT function of an MCPTT group
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Request-URI to the public service identity of the non-controlling MCPTT function serving the group identity of the constituent MCPTT group;
NOTE 1: If the non-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 2: If the non-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 3: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function serving the MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 4: 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 set the P-Asserted-Identity to the public service identity of the controlling MCPTT function;
4) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request:
a) the <mcptt-request-uri> element set to the group identity of the constituent MCPTT group served by the non-controlling MCPTT; and
b) the <mcptt-calling-group-id> element set to the group identity of the group served by the controlling MCPTT function;
5) shall include the Recv-Info header field set to g.3gpp.mcptt-floor-request;
6) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and
7) shall send the SIP INVITE request towards the non-controlling MCPTT function in accordance with 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
2) if at least one MCPTT clients has subscribed to the conference package, shall subscribe to the conference event package in the non-controlling MCPTT function as specified in clause 10.1.3.4.3; and
3) if the 200 (OK) response includes the <floor-state> element set to "floor-taken", shall wait for a SIP INFO request containing a floor request from the non-controlling MCPTT function.
Upon receiving a SIP INFO request containing a floor request where:
1) the Request-URI contains an MCPTT session ID identifying an ongoing temporary group session; and
2) the application/vnd.3gpp.mcptt-info+xml MIME body contains the <mcptt-calling-group-id> element with the MCPTT group ID of a MCPTT group invited to the temporary group session;
then the controlling MCPTT function:
1) shall send a SIP 200 (OK) response to the SIP INFO request to the non-controlling MCPTT function as specified in 3GPP TS 24.229 [4]; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3.
10.1.2.4.1.2 Receipt of a SIP re-INVITE request
In the procedures in this clause:
1) emergency indication in an incoming SIP re-INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP re-INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a SIP re-INVITE request for an MCPTT session identity identifying a chat MCPTT group session, the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP re-INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP re-INVITE request contains an emergency indication or an imminent peril indication set to a value of "true" and this is an authorised request for originating an MCPTT emergency group call as determined by clause 6.3.3.1.13.2, or for originating an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5, the controlling MCPTT function can according to local policy choose to accept the request.
2) if the received SIP re-INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.17;
3) if the SIP re-INVITE request contains an unauthorised request to initiate an MCPTT emergency call as determined by clause 6.3.3.1.13.2:
a) shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response as specified in clause 6.3.3.1.14; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
4) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true" and is an authorised request to initiate an MCPTT emergency group call as determined by clause 6.3.3.1.13.2, the controlling MCPTT function shall:
a) validate that the SIP re-INVITE request includes a Resource-Priority header field is populated correctly for an MCPTT emergency group call as specified in clause 6.3.3.1.19, and if not:
i) shall perform the actions specified in clause 6.3.3.1.8; and
ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 shall proceed with the rest of the steps.
NOTE 2: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly-entered in-progress emergency states of the specified group.
b) if the in-progress emergency state of the group is set to a value of "true" and the MCPTT user is indicating a new emergency indication:
i) shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency call;
ii) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true" and is an authorised request for an MCPTT emergency alert as determined by clause 6.3.3.1.13.1, shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency alert; and
iii) for each of the other affiliated members of the group, generate a SIP MESSAGE request notification of the MCPTT user's emergency indication as specified in clause 6.3.3.1.11 with the following clarifications:
A) set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true";
B) if the received SIP re-INVITE contains an alert indication set to a value of "true" and this is an authorised request for an MCPTT emergency alert meeting the conditions specified in clause 6.3.3.1.13.1, perform the procedures specified in clause 6.3.3.1.12; and
C) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
c) if the in-progress emergency state of the group is set to a value of "false":
i) shall set the value of the in-progress emergency state of the group to "true";
ii) shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency call;
iii) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true" and this is an authorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall cache the MCPTT ID of the MCPTT user that has initiated an MCPTT emergency alert;
iv) shall start timer TNG2 (in-progress emergency group call timer) and handle its expiry as specified in clause 6.3.3.1.16;
v) shall generate SIP re-INVITE requests for the MCPTT emergency group call to the other affiliated and joined participants of the chat MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
vi) shall generate SIP INVITE requests for the MCPTT emergency group call to the affiliated but not joined members of the chat MCPTT group as specified in clause 6.3.3.1.7. The controlling MCPTT function:
A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
vii) if the in-progress imminent peril state of the group is set to a value of "true", shall set it to a value of "false";
5) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is an unauthorised request for an MCPTT emergency group call cancellation as determined by clause 6.3.3.1.13.4:
a) shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response;
b) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in annex F.1 with an <emergency-ind> element set to a value of "true";
c) if an <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is included set to "false" and there is an outstanding MCPTT emergency alert for the MCPTT user, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body and <alert-ind> element set to a value of "true"; and
d) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
6) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and is determined to be an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the group to is set to a value of "true" the controlling MCPTT function shall:
a) validate that the SIP re-INVITE request includes a Resource-Priority header field is populated correctly for a normal priority MCPTT group call as specified in clause 6.3.3.1.19, and if not:
i) shall perform the actions specified in clause 6.3.3.1.8; and
ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 shall proceed with the rest of the steps;
NOTE 3: Verify that the Resource-Priority header is included and properly populated for an in-progress emergency state cancellation of the specified group.
b) shall set the in-progress emergency group state of the group to a value of "false";
c) shall clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding MCPTT emergency group call;
d) if an <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is included and set to "false" and is determined to be an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and there is an outstanding MCPTT emergency alert for the MCPTT user shall:
i) if the received SIP re-INVITE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding MCPTT emergency alert; and
ii) if the received SIP re-INVITE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the sender of the SIP re-INVITE request as having an outstanding MCPTT emergency alert;
e) shall generate SIP re-INVITE requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
i) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 4: Clause 6.3.3.1.6 will inform the affiliated and joined members of the cancellation of the MCPTT group's in-progress emergency state and the cancellation of the MCPTT emergency alert if applicable.
f) for each of the affiliated but not joined members of the group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
ii) set the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false";
iii) if indicated above in step d), set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
iv) send the SIP MESSAGE request according to 3GPP TS 24.229 [4];
7) if a Resource-Priority header field is included in the SIP re-INVITE request:
a) if the Resource-Priority header field is set to the value indicated for emergency calls and the received SIP re-INVITE request does not contain an authorised request for an MCPTT emergency call as determined in step 4) above and the in-progress emergency state of the group is set to a value of "false", shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response and skip the remaining steps; or
b) if the Resource-Priority header field is set to the value indicated for imminent peril calls and the received SIP re-INVITE request does not contain an authorised request for an MCPTT imminent peril call as determined by the procedures of clause 6.3.3.1.13.5 and the in-progress imminent peril state of the group is set to a value of "false", shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response and skip the remaining steps;
8) if the received SIP re-INVITE request contains an imminent peril indication, shall perform the procedures specified in clause 10.1.2.4.1.3 and skip the rest of the steps;
9) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 6) a) i) above;
10) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
11) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true" and if this is an unauthorised request for an MCPTT emergency alert as determined by clause 6.3.3.1.13.1, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
12) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCPTT emergency alert cancellation as determined by clause 6.3.3.1.13.3, shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
13) if the received SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCPTT imminent peril group call and if the in-progress emergency state of the group is set to a value of "true", shall include in the SIP 200 (OK) response the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4;
NOTE 5: In this case, the request was for an imminent peril call but a higher priority MCPTT emergency call was already in progress on the group. Hence, the imminent peril call request aspect of the request is denied but the request is granted with emergency level priority.
14) shall interact with media plane as specified in 3GPP TS 24.380 [5]; and
15) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP ACK to the SIP 200 (OK) response sent towards the inviting MCPTT client, and the SIP 200 (OK) response was sent with the warning text set to "149 SIP INFO request pending" in a Warning header field as specified in clause 4.4, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.18.
10.1.2.4.1.3 Handling of a SIP re-INVITE request for imminent peril session
In the procedures in this clause:
1) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
When the controlling function receives a SIP re-INVITE request with and imminent peril indication, the controlling function:
1) if the SIP re-INVITE request contains an unauthorised request to initiate an MCPTT imminent peril group call as determined by clause 6.3.3.1.13.5, shall reject the SIP re-INVITE request with a SIP 403 (Forbidden) response with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
2) if the in-progress emergency group state of the group is set to a value of "false" and if the SIP re-INVITE request contains an imminent peril indication set to a value of "true" or the in-progress imminent peril state of the group to "true", the controlling MCPTT function shall:
a) validate that the SIP re-INVITE request includes a Resource-Priority header field with the namespace set to the MCPTT-specific namespace specified in IETF RFC 8101 [48] and the priority set to the priority designated for imminent peril calls and if not:
i) perform the actions specified in clause 6.3.3.1.8;
ii) send the SIP UPDATE request generated in clause 6.3.3.1.8 towards the initiator of the SIP re-INVITE request according to 3GPP TS 24.229 [4]; and
iii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 proceed with the rest of the steps.
NOTE 3: Verify that the Resource-Priority header is included and properly populated for both ongoing and newly- entered in-progress imminent peril states of the specified group.
b) if the in-progress imminent peril state of the group is set to a value of "true" and the MCPTT user is indicating a new imminent peril indication:
i) for each of the other affiliated member of the group generate a SIP MESSAGE request notification of the MCPTT user's imminent peril indication as specified in clause 6.3.3.1.11 with the following clarifications;
A) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "true"; and
B) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
ii) cache the information that the MCPTT user has initiated an MCPTT imminent peril call; and
c) if the in-progress imminent peril state of the group is set to a value of "false":
i) shall set the value of the in-progress imminent peril state of the group to "true";
ii) shall generate SIP re-INVITE requests for the MCPTT imminent peril group call to the other affiliated and joined participants of the chat MCPTT group as specified in clause 6.3.3.1.15;
iii) shall generate SIP INVITE requests for the MCPTT imminent peril group call to the affiliated but not joined members of the chat MCPTT group as specified in clause 6.3.3.1.7;
A) for each affiliated but not joined member shall send the SIP INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
iv) shall cache the information that the MCPTT user has initiated an MCPTT imminent peril call;
3) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is an unauthorised request for an MCPTT imminent peril group call cancellation as determined by clause 6.3.3.1.13.6 shall:
a) reject the SIP re-INVITE request with a SIP 403 (Forbidden) response to the SIP re-INVITE request; and
b) include in the SIP 403 (Forbidden) response:
i) include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false";
ii) send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4]; and
iii) skip the rest of the steps;
4) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false" and is determined to be an authorised request for an MCPTT imminent peril call cancellation as specified in clause 6.3.3.1.13.6 and the in-progress imminent peril state of the group to is set to a value of "true" the controlling MCPTT function shall:
a) validate that the SIP re-INVITE request includes a Resource-Priority header field with the namespace set to the MCPTT-specific namespace specified in IETF RFC 8101 [48], and the priority set to the priority level designated for a normal priority MCPTT group call, and if not:
i) shall perform the actions specified in clause 6.3.3.1.8; and
ii) upon receiving a SIP 200 (OK) response to the SIP UPDATE request sent in clause 6.3.3.1.8 shall proceed with the rest of the steps;
NOTE 3: verify that the Resource-Priority header is included and properly populated for an in-progress emergency group state cancellation of the specified group.
b) shall set the in-progress imminent peril state of the group to a value of "false";
c) shall cache the information that the MCPTT user no longer has an outstanding MCPTT imminent peril group call;
d) shall generate SIP re-INVITES requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.15. The MCPTT controlling function:
i) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
ii) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 4: clause 6.3.3.1.15 will inform the affiliated and joined members of the cancellation of the MCPTT group's in-progress emergency group state and the cancellation of the MCPTT emergency alert if applicable.
e) for each of the affiliated but not joined members of the group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's imminent peril call as specified in clause 6.3.3.1.11;
ii) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
iii) send the SIP MESSAGE request according to 3GPP TS 24.229 [4];
5) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1 unless the procedures of clause 6.3.3.1.8 were performed in step 2) or 4) above;
6) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [22];
7) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
8) shall interact with media plane as specified in 3GPP TS 24.380 [5]; and
9) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.4.2 End group call at the terminating controlling MCPTT function | Upon receiving a SIP BYE request the controlling MCPTT function shall follow the procedures as specified in clause 6.3.3.2.4. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.4.3 End group call initiated by the controlling MCPTT function | 10.1.2.4.3.1 General
This clause describes the procedures of each functional entity for ending the group call initiated by the controlling MCPTT function.
10.1.2.4.3.2 SIP BYE request for releasing MCPTT session for a group call
When the MCPTT session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
10.1.2.4.3.3 SIP BYE request toward a MCPTT client
When an MCPTT client needs to be removed from the MCPTT session (e.g. due to de-affiliation or admitting a higher priority user), the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
After successful removing the MCPTT client from the MCPTT session, the controlling MCPTT function may generate a notification to the MCPTT clients, which have subscribed to the conference event package that an MCPTT user has been removed from the MCPTT session, as specified in clause 6.3.3.4 and send the SIP NOTIFY request to the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.5 Non-controlling function of an MCPTT group procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.2.5.1 Terminating procedures | 10.1.2.5.1.1 General
When receiving the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" the MCPTT server can be acting as a controller MCPTT function in an ongoing chat group call or, if a chat group call is not ongoing, be initiated as an non-controlling MCPTT function and invite MCPTT users.
If a chat group call is not ongoing the MCPTT server shall perform the actions specified in clause 10.1.2.5.1.2.
If the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" is received when a chat group call is ongoing, the controlling MCPTT function may switch from operating in a controlling MCPTT function mode to operate in a non-controlling MCPTT function mode as specified in clause 10.1.2.5.1.3.
When operating in the non-controlling mode and a SIP BYE request is received from the controlling MCPTT function, the non-controlling MCPTT function shall change from operating in the non-controlling mode to operating in the controlling mode as specified in clause 10.1.2.5.1.4.
10.1.2.5.1.2 Initiating a chat group session
Upon receipt of a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" and if a chat group call is not ongoing, the non-controlling MCPTT function of an MCPTT group:
NOTE 1: The Contact header field of the SIP INVITE request contains the isfocus media feature tag.
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
4) if the partner MCPTT system does not have a mutual aid relationship with the primary MCPTT system identified by the contents of the P-Asserted-Identity, shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "128 isfocus already assigned" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
5) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
6) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.4.2.2.2 before continuing with the rest of the steps;
7) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.4.2.1;
8) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3.5; and
NOTE 2: Resulting media plane processing is completed before the next step is performed.
9) shall send a SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
10.1.2.5.1.3 Joining an ongoing chat group call
Upon receipt of a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" and if a chat group call is already ongoing, the non-controlling MCPTT function of an MCPTT group:
NOTE 1: The Contact header field of the SIP INVITE request contains the isfocus media feature tag.
1) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the MCPTT emergency group call state is set to either "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "166 constituent group is in an emergency call state" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
NOTE 2: 3GPP TS 23.280 [82] includes the possibility that local policy could allow a constituent group that is in an emergency state to be included in a group regroup; however, the transfer of that emergency state to the group regroup from the constituent group is not supported in the present document.
3) if the partner MCPTT system does not have a mutual aid relationship with the primary MCPTT system identified by the contents of the P-Asserted-Identity, shall reject the "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" with a SIP 403 (Forbidden) response, with warning text set to "128 isfocus already assigned" in a Warning header field as specified in clause 4.4, and shall not process the remaining steps;
4) shall cache the content of the SIP INVITE request, if received in the Contact header field and if the specific feature tags are supported;
5) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
6) shall generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.4.2.2.2 before continuing with the rest of the steps;
7) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.4.2.1;
8) shall instruct the media plane to initialise the switch to the non-controlling mode as specified in 3GPP TS 24.380 [5] clause 6.5.2.3;
NOTE 3: Resulting media plane processing is completed before the next step is performed. The media plane indicates the state of the floor and if the state is "floor-taken", information about the current speaker(s).
9) if the media plane provided information about the current speaker(s), cache the information about the current speaker(s); and
10) shall send a SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receipt of the SIP ACK request, the non-controlling MCPTT function of an MCPTT group:
1) if information about a current speaker(s) is cached:
a) shall generate a SIP INFO request as specified in clause 6.3.4.1.3; and
b) shall send the SIP INFO request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4];
2) shall instruct the media plane to finalise the switch to the non-controlling mode as specified in 3GPP TS 24.380 [5] clause 6.3.5.3; and
3) if at least one of the MCPTT clients in the chat group session has a subscription to the conference event package, shall subscribe to the conference event package from the controlling MCPTT function as specified in clause 10.1.3.5.3.
10.1.2.5.1.4 Splitting an ongoing chat group call
Upon receipt of a SIP BYE request, the non-controlling MCPTT function of an MCPTT group:
1) if keeping the chat group call active is according to the release policy in clause 6.3.8.1, shall request media plane to switch to controlling mode as specified in 3GPP TS 24.380 [5] clause 6.3.5;
NOTE 1: Resulting media plane processing is completed before the next step is performed.
2) shall send a SIP 200 (OK) response to the SIP BYE request; and
3) if at least one MCPTT client has subscribed to the conference package, shall send a NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.5.2.
NOTE 2: The SIP NOTIFY request will indicate that all participants, with the exception of the MCPTT users belonging to the constituent MCPTT group hosted by the non-controlling MCPTT function, have left the group session.
10.1.2.5.1.5 MCPTT client joining the temporary group chat session
Upon receiving of a "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" when a chat session is ongoing, the non-controlling MCPTT function shall act as a controlling MCPTT function towards the MCPTT client and shall perform the actions in the clause 10.1.2.4.1.1 with the following clarifications:
1) the MCPTT session identity in the Contact header field of the SIP 200 (OK) response shall be the MCPTT session identity generated by the non-controlling MCPTT function; and
2) the clause 10.1.3.5.2 shall be used when sending the SIP NOTIFY request for subscriptions to the conference event package.
10.1.2.5.1.6 Receipt of a SIP re-INVITE request from an MCPTT client
Upon receipt of a SIP re-INVITE request from an MCPTT client the non-controlling MCPTT function shall act as the controlling MCPTT function and shall perform the actions in clause 10.1.2.4.1.2.
10.1.2.5.1.7 void
10.1.2.5.1.8 Initiating a temporary group session
Upon receiving a "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" when a chat group session is not ongoing, the non-controlling MCPTT-function shall:
NOTE 1: The difference between a "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" and a "SIP INVITE request for non-controlling MCPTT function of an MCPTT group" (from the controlling MCPTT function) is that the latter SIP INVITE request contains the isfocus media feature tag in the Contact header field.
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The non-controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
4) shall retrieve the group document from the group management server for the MCPTT group ID contained in the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request and carry out initial processing as specified in clause 6.3.5.2 and continue with the rest of the steps if the checks in clause 6.3.5.2 succeed;
NOTE 2: If the checks are not successful, the SIP response to the "SIP INVITE request from participating MCPTT function for controlling MCPTT function of an MCPTT group" is already sent in the clause 6.3.5.2.
5) shall cache the content of the SIP INVITE request;
6) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
7) shall check the authorization of the MCPTT user in the <mcptt-calling-user-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the "SIP INVITE request from participating MCPTT function for controlling MCPTT function of an MCPTT group" as specified in clause 6.3.5.2. If the MCPTT user is unauthorized to join a chat group session, the non-controlling MCPTT function shall send a SIP 403 (Forbidden) response with the warning text set to "106 user not authorised to join chat group" in a Warning header field as specified in clause 4.4.
8) if the MCPTT user identified by the MCPTT ID in the SIP INVITE request is not affiliated with the MCPTT group identified by the group identity conained in the <associated-group-id> element element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP INVITE request as determined by the procedures of clause 6.3.6:
a) shall check if the MCPTT user is eligible to be implicitly affiliated with the MCPTT chat group as determined by clause 9.2.2.3.6; and
b) if the MCPTT user is not eligible for implicit affiliation, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
9) shall generate a SIP INVITE request towards the controlling MCPTT function as specified in clause 6.3.4.1.4; and
10) shall send the SIP INVITE request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the SIP INVITE request sent to the controlling MCPTT function as specified above, the non-controlling MCPTT function:
1) shall send the SIP ACK request to the controlling MCPTT function as specified in 3GPP TS 24.229 [4];
2) shall generate a SIP 200 (OK) to the "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" as specified in 3GPP TS 24.229, populated as follows:
a) shall include an SDP answer as specified in clause 6.3.4.2.1, based on the SDP answer in the SIP 200 (OK) response;
b) shall include the public service identifier of the non-controlling MCPTT function in the P-Asserted-Identity header field; and
c) shall include the warning text set to "148 group is regrouped" in a Warning header field as specified in clause 4.4; and
NOTE 3: As long as the MCPTT group is regrouped, the floor control messages in the media plane includes a grouped regrouped indication as specified in 3GPP TS 24.380 [5].
3) shall start acting as a non-controlling MCPTT function and interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.5.
Upon receipt of other final SIP responses with the exception of the SIP 2xx response to the INVITE request sent to the controlling MCPTT function as specified above, the non-controlling MCPTT function:
1) shall send the SIP ACK response to the controlling MCPTT function as specified in 3GPP TS 24.229 [4]; and
2) perform the actions in the clause 10.1.1.5.2.4.
NOTE 4: Regardless if the controlling MCPTT function accepts or rejects the SIP INVITE request sent above, the chat group session continues to be initiated with only the members of the group homed on the non-controlling MCPTT function of the group being invited to the group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3 Subscription to the conference event package | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.1 General | The IETF RFC 4575 [30] defines a conference event package that shall be used to obtain the status of participants in group sessions.
The MCPTT client may subscribe to the conference event package at any time in a group session that the MCPTT client participates in. The clause 10.1.3.2 specifies the procedures in the MCPTT client when subscribing to the conference events.
The participating MCPTT function shall forward conference state subscriptions and notifications as specified in clause 10.1.3.3.
The controlling MCPTT function shall handle subscriptions and notification of conference events as specified in clause 10.1.3.4.
The non-controlling MCPTT function shall handle subscriptions and notification of conference events as specified in clause 10.1.3.5.
When the non-controlling MCPTT function connection model is used, the controlling MCPTT function subscribes to the conference event package from the non-controlling MCPTT function as specified in clause 10.1.3.4.3 and the non-controlling MCPTT function subscribes to the conference event package from the controlling MCPTT function as specified in clause 10.1.3.5.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.2 MCPTT client | A MCPTT client may subscribe to the conference event package when a group call is ongoing and the ongoing group call is not initiated as a broadcast group call by sending a SIP SUBSCRIBE request to obtain information of the status of a group session.
When subscribing to the conference event package, the MCPTT client:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the MCPTT session identity of the group session;
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-Preferred-Service header field according to IETF RFC 6050 [9];
4) shall include an Accept-Contact header with the media feature tag g.3gpp.icsi-ref with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) if the MCPTT client wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
6) if the MCPTT client wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
7) shall include an Accept header field containing the application/conference-info+xml"MIME type;
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> element set to the MCPTT group ID of the group session; and
9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving a SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request the MCPTT client:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30]; and
2) may process the current state information to the MCPTT client based on the information in the SIP NOTIFY request body and may display to the MCPTT user the MCPTT IDs of the participating MCPTT users and the functional alias the participating MCPTT user has bound to that MCPTT group if available.
When needed the MCPTT client shall terminate the subscription and indicate it terminated according to IETF RFC 6665 [26].
NOTE 2: The contents of the received SIP NOTIFY request body is specified in clause 6.3.3.4. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.3 Participating MCPTT function | Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the participating function" from a MCPTT client served by the participating MCPTT function and if the SIP SUBSCRIBE request contains:
1) 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 header field according to IETF RFC 6050 [9];
2) an Accept header field containing the application/conference-info+xml"MIME type; and
3) an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-request-uri> set to a MCPTT group ID;
then the participating MCPTT function:
1) shall attempt to resolve the received Request-URI to an existing MCPTT session identity;
2) if the participating MCPTT function could not resolve the received Request-URI to an existing MCPTT session identity, shall reject the SIP SUBSCRIBE response with a SIP 404 (Not Found) response with a warning text set to "137 the indicated group call does not exist" as specified in clause 4.4 and shall skip the rest of the steps
3) shall generate a SUBSCRIBE request as specified in TS 24.229 [4]
4) shall set the SIP URI in the Request-URI with the MCPTT session identity that is mapped to the MCPTT session identity in the received Request-URI;
5) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body the <mcptt-calling-user-id> element set to the MCPTT ID of the served user: and
6) shall insert a Record-Route header containing a URI identifying its own address; and
7) shall send the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4].
Upon receiving a SIP response to the SIP SUBSCRIBE request the participating MCPTT function:
1) shall copy the content of the incoming SIP response to an outgoing SIP response;
2) if a SIP 200 (OK) response, shall include in the Contact header field of the outgoing SIP response an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response in the outgoing SIP response; and
3) shall forward the SIP response according to 3GPP TS 24.229 [4].
Upon receiving a SIP NOTIFY request within the dialog created by the SIP SUBSCRIBE request destined to a served MCPTT client, the participating MCPTT function:
1) shall include the public service identity of the MCPTT user in the Request-URI;
2) shall copy the content of the incoming SIP NOTIFY request to the outgoing SIP NOTIFY request; and
3) shall send the SIP NOTIFY request according to 3GPP TS 24.229 [4].
Upon receiving a SIP response to the SIP NOTIFY request the participating MCPTT function:
1) shall copy the content of the incoming SIP response to an outgoing SIP response;
2) if a SIP 200 (OK) response, shall include an MCPTT session identity constructed from the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response in the outgoing SIP response; and
3) shall forward the SIP response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.4 Controlling MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.4.1 Receiving a subscription to the conference event package | Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" and the SIP SUBSCRIBE request:
1) contains an application/vnd.3gpp.mcptt-info+xml MIME body with
a) the <mcptt-request-uri> element set to the group identity of the group session and the <mcptt-calling-user-id> element set to either:
i) the MCPTT ID of a participant in the group session; or
ii) a constituent MCPTT group ID of a non-controlling MCPTT function in a temporary group session;
2) contains 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 header field according to IETF RFC 6050 [9];
3) contains an Accept header field containing the application/conference-info+xml MIME type; and
4) is not received in a group call initiated as a broadcast group call;
then the controlling MCPTT function:
1) shall check if the <on-network-allow-conference-state> element in the group document in 3GPP TS 24.481 [31] allows the MCPTT ID or the constituent MCPTT group ID in the <mcptt-calling-user-id> element to subscribe to the conference event package and if not allowed:
a) shall reject the "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" with a SIP 403 (Forbidden) response to the SIP SUBSCRIBE request, with warning text set to "138 subscription of conference events not allowed" as specified in clause 4.4; and
b) shall not continue with the remaining steps;
2) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
3) shall cache information about the subscription;
4) shall send a conference state notification as specified in clause 10.1.3.4.2; and
5) if the SIP SUBSCRIBE request is the first SUBSCRIBE request from a participant in a temporary group session, shall subscribe to the conference event package from all non-controlling MCPTT functions in the group session as specified in clause 10.1.3.4.3.
Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function in an group call initiated as a broadcast group call, the controlling MCPTT function:
1) shall generate a SIP 480 (Temporarily Unavailable) response to the SIP SUBSCRIBE request as specified in 3GPP TS 24.229 [4];
2) shall include a Warning header field with the warning text set to "105 subscription not allowed in a broadcast group call" as specified in clause 4.4; and
3) send the SIP 480 (Temporarily Unavailable) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.4.2 Sending notifications to the conference event package | The procedures in this clause is triggered by:
1) the receipt of a SIP SUBSCRIBE request as specified in clause 10.1.3.4.1;
2) the receipt of a SIP BYE request from one of the participants in a pre-arranged or a chat group session; or
3) when a new participant is added in a pre-arranged or chat group session.
When sending a conference event notification, the controlling MCPTT function:
1) shall generate a notification package as specified in clause 6.3.3.4 to all MCPTT clients which have subscribed to the conference event package; and
NOTE: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
2) shall send a SIP NOTIFY request to all participants which have subscribed to the conference event package as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.4.3 Sending subscriptions to the conference event package | The procedure in this clause is triggered by:
1) the receipt of a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCPTT function of an MCPTT group and if at least one participant already has subscribed to the conference event package in the controlling MCPTT function as specified in clause 10.1.3.4.1; or
2) the receipt of the first SIP SUBSCRIBE request as specified in clause 10.1.3.4.1 and one or more participant in the group session is a non-controlling MCPTT function;
then, for each non-controlling MCPTT function from where a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCPTT function of an MCPTT group has been received and where a SIP SUBSCRIBE request is not already sent, the controlling MCPTT function:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the public service identity of the non-controlling MCPTT function serving the group identity of the MCPTT group owned by the partner MCPTT system;
3) shall include a P-Asserted-Identity header field in the outgoing SIP SUBSCRIBE request set to the public service identity of the controlling MCPTT function;
4) 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];
5) shall include an Accept-Contact header with the g.3gpp.mcptt along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
7) shall include an Accept header field containing the application/conference-info+xml MIME type;
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-request-uri> element set to the constituent MCPTT group ID; and
b) the <mcptt-calling-group-id> set to the temporary MCPTT group ID; and
9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving an incoming SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request, the controlling MCPTT function:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
2) shall modify the SIP NOTIFY request as specified in clause 6.3.3.4; and
3) shall forward the modified SIP NOTIFY request according to 3GPP TS 24.229 [4] to all other participants with a subscription to the conference event package.
NOTE: A non-controlling MCPTT function of an MCPTT group is regarded as a participant in a temporary group session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.4.4 Terminating a subscription | Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" that terminates the subscription of the conference event package as specified in IETF RFC 6665 [26], the controlling MCPTT function:
1) shall send a SIP 200 (OK) response as specified in IETF RFC 6665 [26]; and
2) if there are no remaining subscriptions to the event package in the ongoing MCPTT call in a temporary group session, shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [26] in all non-controlling MCPTT functions in the temporary group session.
Upon expiry of the subscription timer and if there are no remaining subscriptions to the event package in the ongoing MCPTT call in a temporary group session, the controlling MCPTT function shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [26] in all non-controlling MCPTT functions in the temporary group session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.5 Non-controlling MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.5.1 Receiving subscriptions to the conference event package | Upon receipt of "SIP SUBSCRIBE request for conference event status subscription in the non-controlling MCPTT function" and the SIP SUBSCRIBE request:
1) contains an application/vnd.3gpp.mcptt-info+xml MIME body with
a) the <mcptt-request-uri> element set to the constituent MCPTT group ID; and
b) the <mcptt-calling-user-id> element is set to:
i) a participant in the group session; or
ii) the temporary MCPTT group ID;
2) contains 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 header field according to IETF RFC 6050 [9];
3) contains an Accept header field containing the application/conference-info+xml MIME type; and
4) is not received in a group call initiated as a broadcast group call;
then the non-controlling MCPTT function:
1) shall check if the <on-network-allow-conference-state> element in the group document in 3GPP TS 24.481 [31] of the constituent group allows the MCPTT ID in the <mcptt-calling-user-id> element to subscribe to the conference event package and if not allowed:
a) shall reject the "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" with a SIP 403 (Forbidden) response to the SIP SUBSCRIBE request, with warning text set to "138 subscription of conference events not allowed" as specified in clause 4.4; and
b) shall not continue with the remaining steps;
2) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
3) shall cache information about the subscription;
4) shall generate a notification package as specified in clause 6.3.4.3 and send a SIP NOTIFY request according to 3GPP TS 24.229 [4] to the MCPTT client which have subscribed to the conference event package; and
5) if the SIP SUBSCRIBE request is the first SIP SUBSCRIBE request from a MCPTT client, shall subscribe to the conference event package from the controlling MCPTT functions in the group session as specified in clause 10.1.3.5.3.
Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" in a group call initiated as a broadcast group call, the controlling MCPTT function:
1) shall generate a SIP 480 (Temporarily Unavailable) response to the SIP SUBSCRIBE request as specified in 3GPP TS 24.229 [4];
2) shall include a Warning header field with the warning text set to "105 subscription not allowed in a broadcast group call" as specified in clause 4.4; and
3) send the SIP 480 (Temporarily Unavailable) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.5.2 Sending notifications to the conference event package | The procedures in this clause is triggered by:
1) the receipt of a receipt of a SIP BYE request from one of the participants in a pre-arranged or a chat group session; or
2) when a new participant is added in a pre-arranged or chat group session.
When sending a conference event notification, the non-controlling MCPTT function:
1) shall generate a notification package as specified in clause 6.3.4.3 to all participants which have subscribed to the conference event package; and
NOTE: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
2) shall send a SIP NOTIFY request to all participants which have subscribed to the conference event package as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.5.3 Sending a subscription to the conference event package | Upon receipt of the first subscription to the conference event package from an MCPTT client, the non-controlling MCPTT function:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the temporary MCPTT session identity;
NOTE: The SIP URI received in the Contact header field of the SIP INVITE request for non-controlling MCPTT function of an MCPTT group is the temporary MCPTT session identity. Towards MCPTT clients the non-controlling MCPTT function uses an internal generated MCPTT session identity.
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 header field according to IETF RFC 6050 [9];
4) shall include an Accept-Contact header with the media feature tag g.3gpp.icsi-ref with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
6) shall include an Accept header field containing the application/conference-info+xml MIME type;
7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-request-uri> element set to the temporary MCPTT group ID: and
b) the <mcptt-calling-group-id> set to the constituent MCPTT group ID; and
8) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The 2xx response to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving an incoming SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request the non-controlling MCPTT function:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
2) shall store conference information based on the SIP NOTIFY request content;
3) shall modify the SIP NOTIFY request as specified in clause 6.3.4.3; and
4) forward the modified SIP NOTIFY request according to 3GPP TS 24.229 [4] to all MCPTT clients with a subscription to the conference event package. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.5.4 Terminating a subscription | Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the non-controlling MCPTT function" that terminates the subscription of the conference event package as specified in IETF RFC 6665 [26], the non-controlling MCPTT function:
1) shall send a SIP 200 (OK) response as specified in IETF RFC 6665 [26]; and
2) if there are no remaining subscriptions to the event package (excluding any subscriptions to the event package made by the controlling MCPTT function), shall terminate the subscriptions to the conference event package in the controlling MCPTT function as specified in IETF RFC 6665 [26].
Upon expiry of the subscription timer and if there are no remaining subscriptions to the event package (excluding any subscriptions to the event package made by the controlling MCPTT function), the non-controlling MCPTT function shall terminate the subscriptions to the conference event package in the controlling MCPTT function as specified in IETF RFC 6665 [26].
NOTE: The subscription to the event package made by the controlling MCPTT function will be terminated by the controlling MCPTT function when the last subscription to the event package is terminated in the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.6 Coding | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.3.6.1 Extension of application/conference-info+xml MIME type | 10.1.3.6.1.1 Introduction
The present clause describes an extensions of the application/conference-info+xml MIME body specified in IETF RFC 4575 [30].
The functional alias extension is used to indicate per-user functional alias association with MCPTT group.
10.1.3.6.1.2 Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttConfInfo:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttConfInfo="urn:3gpp:ns:mcpttConfInfo:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCPTT specific child element of endpoint element -->
<xs:element name="functional-alias" type="xs:anyURI" use="optional"/>
</xs:schema>
The application/conference-info MIME body refers to namespaces using prefixes specified in table 10.1.3.6.1.2-1.
Table 10.1.3.6.1.2-1: Assignment of prefixes to namespace names in the application/pidf+xml MIME body
Prefix
Namespace
mcpttConfInfo
urn:3gpp:ns:mcpttConfInfo:1.0
NOTE: The "urn:ietf:params:xml:ns:conference-info" namespace is the default namespace so no prefix is used for it in the application/conference-info MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4 Remote change of an MCPTT user's selected group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.1 General | Clause 10.1.4 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for the on-network remote change of an MCPTT user's selected group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.2.1 Remote selected group change initiation | Upon receiving a request from the MCPTT user to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group, the MCPTT client:
1) if:
a) the <RemoteGroupSelectionURIList> element does not exist in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
b) the <RemoteGroupSelectionURIList> element exists in the MCPTT user profile document and the MCPTT ID of the targeted MCPTT user does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
a) should indicate to the requesting MCPTT user that they are not authorised to change the selected MCPTT group of the targeted MCPTT user; and
b) shall skip the rest of the steps of the present clause;
1A) shall determine whether the group document associated with the specific MCPTT group contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
a) should indicate to the MCPTT user that calls are not allowed on the specific MCPTT group; and
b) shall skip the remainder of this procedure;
2) 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) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) 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) the <mcptt-request-uri> set to the MCPTT group identity to be selected by the targeted MCPTT user; and
ii) the <request-type> element set to a value of "group-selection-change-request"; and
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20];
3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the MCPTT user the failure of the sent group selection change request and not continue with the rest of the steps.
Upon receiving a "SIP MESSAGE request for group selection change response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent group selection change request from the value of the <selected-group-change-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
2) should indicate to the MCPTT user the success or failure of the sent group selection change request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.2.2 Target client procedures for handling remote selected group change request | Upon receiving a "SIP MESSAGE request for group selection change request for terminating client", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing an <affiliation-required> element set to a value of "true":
a) shall invoke the procedures of clause 9.2.1.2 to affiliate to the MCPTT group identified by the contents of the <mcptt-calling-group-id> included in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if the MCPTT client has not already invoked the procedures of clause 9.2.1.3, shall invoke the procedures of clause 9.2.1.3; and
c) upon receiving a SIP NOTIFY request including a <p-id> element set to a value matching the <p-id> value included in the SIP PUBLISH request sent in step 1) a) above as specified in clause 9.2.1.3, shall determine if the affiliation procedure to the MCPTT group identified by the contents of the <mcptt-calling-group-id> in the received SIP MESSAGE request was successful;
2) if the received SIP MESSAGE request contained an application/vnd.3gpp.mcptt-info+xml MIME body containing an <affiliation-required> element set to a value of "true" and the affiliation was successful as determined in step 1) c) above, or if the <affiliation-required> element was not present in the received SIP MESSAGE request:
a) shall change the MCPTT client's selected group to the MCPTT group identified by the contents of the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall determine the success or failure of the change of selected group action;
3) 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) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request;
e) 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) the <mcptt-request-uri> set to the MCPTT group identity to be selected by the MCPTT user; and
ii) the <anyExt> element containing:
A) the <response-type> element set to a value of "group-selection-change-response";
B) if the MCPTT client was able to successfully change the selected group as determined in step 2) b) above, then a <selected-group-change-outcome> element set to a value of "success"; and
C) if the MCPTT client:
I) was required to affiliate to the MCPTT group identified by the contents of the <mcptt-calling-group-id> in the received SIP MESSAGE request and the affiliation failed as determined in step 1) c); or
II) failed to change the selected group as determined in step 2) b);
then a <selected-group-change-outcome> element set to a value of "fail";
4) should indicate to the MCPTT user the success or failure of the requested change of selected group action;
5) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.3.1 Originating procedures | Upon receiving a "SIP MESSAGE request for group-selection-change for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the "SIP MESSAGE request for group selection change for originating participating MCPTT function" contains the <request-type> element set to a value of "group-selection-change-request":
a) if:
i) the <RemoteGroupSelectionURIList> element does not exist in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
ii) if the MCPTT ID contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received "SIP MESSAGE request for group selection change for originating participating MCPTT function" does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
i) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "155 user not authorised to change user's selected group" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
4) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
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 group identity 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.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4);
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8) shall copy the contents of the application/resource-lists+xml MIME body into the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) 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;
11) 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];
12) 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];
13) 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; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the sent SIP MESSAGE request, the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.3.2 Terminating procedures | Upon receiving a "SIP MESSAGE request for group-selection-change for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall 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; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.4.4 Controlling MCPTT function procedures | Upon receiving:
- a "SIP MESSAGE request for group selection change request for controlling MCPTT function"; or
- a "SIP MESSAGE request for group selection change response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if there is a <request-type> element set to a value of "group-selection-change-request" contained in the <anyExt> element in the <mcptt-Params> element contained in the <mcpttinfo> root element contained in the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request:
a) if the MCPTT user identified by the MCPTT ID in the "uri" attribute of an <entry> element in a <list> element in the <resource-lists> element of the application/resource-lists+xml MIME body contained in the SIP MESSAGE request is not affiliated with the MCPTT group identified by the <mcptt-request-uri> in the application/vnd.3gpp. mcptt-info+xml MIME body as determined by the procedures of clause 6.3.6:
i) shall determine if the MCPTT user is eligible to be affiliated with the MCPTT group as determined by clause 9.2.2.3.8; and
ii) if the MCPTT user is not eligible for affiliation, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) 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];
6) 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];
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request with the following clarifications:
a) shall set the <mcptt-calling-group-id> to the MCPTT group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall set the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the MCPTT ID of the targeted MCPTT user contained in the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the received SIP MESSAGE request;
8) if the received SIP MESSAGE request is a "SIP MESSAGE request for group selection change request for controlling MCPTT function":
a) if the targeted MCPTT user is not affiliated to the identified MCPTT group and was determined to be eligible to be affiliated with the MCPTT group in step 3) a) i) above, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <anyExt> element an <affiliation-required> element set to a value of "true";
9) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating 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 3: If the terminating participating 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 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
10) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5 Remotely initiated group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.1 General | Clause 10.1.5 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for on-network remotely initiated group call.
In the procedures clause 10.1.5.2:
- the term "requesting MCPTT user" is used to refer to the user who sent a request to initiate a remotely initiated group call;
- the term "remote MCPTT user" is used to refer to the user who is sent a request to initiate a remotely initiated group call; and
- the term "targeted MCPTT group" is used to refer to the group that is to be called in the requested remotely initiated group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.2.1 Remotely initiated group call initiation request procedures | Upon receiving a request from the requesting MCPTT user to send a remotely initiated group call request to the remote MCPTT user for a targeted MCPTT group, the MCPTT client:
1) if:
a) the <allow-request-remote-init-group-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false":
then:
a) should indicate to the requesting MCPTT user that the requesting MCPTT user is not authorised to initiate a remotely initiated group call request to the remote MCPTT user; and
b) shall skip the rest of the steps of the present clause;
1A) shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
a) should indicate to the MCPTT user that calls are not allowed on the indicated group; and
b) shall skip the remainder of this procedure;
2) void; and
3) 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) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) 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) the <mcptt-request-uri> set to the MCPTT group identity of the targeted MCPTT group for the remotely initiated call; and
ii) an <anyExt> element containing:
A) the <request-type> element set to a value of "remotely-initiated-group-call-request";
B) the <notify-remote-user> element set to a value of "true" if the requesting MCPTT user has indicated that the remote MCPTT user be notified of the remotely initiated group call request;
C) the <notify-remote-user> element set to a value of "false" if the requesting MCPTT user has indicated that the remote MCPTT user not be notified of the remotely initiated group call request; and
D) may include <ric-app-level-priority> element set to a value of the namespace and priority values as specified in IETF RFC 8101 [48], and MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) to be used by the remote MCPTT user to request an application level priority while initiating a call as a result of received remotely initiated call request;
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the remote MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and
f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the remote MCPTT user; and
4) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the requesting MCPTT user the failure of the sent remotely initiated group call request and not continue with the rest of the steps.
Upon receiving a "SIP MESSAGE request for remotely initiated group call response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent remotely initiated group call request from the value of the <remotely-initiated-call -outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
2) should indicate to the requesting MCPTT user the success or failure of the sent remotely initiated group call request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.2.2 Remote client procedures for handling remotely initiated group call request | Upon receiving a "SIP MESSAGE request for remotely initiated group call request for terminating client", the MCPTT client:
1) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "true", may indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
2) if according to local policy on-demand sessions are to be used for remotely initiated group calls, shall invoke the procedures of clause 10.1.1.2.1.1 to originate an MCPTT group call to the targeted MCPTT group with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
ii) shall not give any indication to the remote MCPTT user that the remotely initiated call origination is in progress; and
b) if the <ric-app-level-priority> 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 contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP INVITE request with the value received in the <ric-app-level-priority> element; and
3) if according to local policy pre-established sessions are to be used for remotely initiated group calls and a pre-established session is available, shall invoke the procedures of clause 10.1.1.2.2.1 to originate an MCPTT group call to the targeted MCPTT group with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
ii) shall not give any indication to the remote MCPTT user that the remotely initiated call origination is in progress; and
b) if the <ric-app-level-priority> 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 contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP REFER request with the value received in the <ric-app-level-priority> element.
Editor's note: It is FFS that how the client will handle the request if according to local policy pre-established sessions are to be used for remotely initiated group calls and a pre-established session is not available.
Upon completion of the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1, the MCPTT client:
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) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and
e) 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) the <mcptt-request-uri> set to the MCPTT group identity called by the remote MCPTT user; and
ii) an <anyExt> element containing:
A) the <response-type> element set to a value of "remotely-initiated-group-call-response";
B) if the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1 were successful in originating an MCPTT group call to the targeted MCPTT group, a <remotely-initiated-call-outcome> element set to a value of "success"; and
C) if the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1 were not successful in originating an MCPTT group call to the targeted MCPTT group, a <remotely-initiated-call-outcome> element set to a value of "fail";
2) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the requesting MCPTT user; and
3) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.3.1 Originating procedures | In the procedures of this clause:
- the term "requesting MCPTT user" is used to refer to the user who sent a request to initiate a remotely initiated group call; and
- the term "remote MCPTT user" is used to refer to the user who is sent a request to initiate a remotely initiated group call.
Upon receiving a "SIP MESSAGE request for remotely initiated group call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1 The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the "SIP MESSAGE request for remotely initiated group call for originating participating MCPTT function" contains the <request-type> element set to a value of "remotely-initiated-group-call-request":
a) if the <allow-request-remote-init-group-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "157 user not authorised to request a remotely initiated group call" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
4) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
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 group identity 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.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4);
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8) shall copy the contents of the application/resource-lists+xml MIME body into the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> element of the <mcptt-Params> element of the <mcpttinfo> element to the MCPTT ID determined in step 2) above;
10) 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;
11) 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];
12) 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];
13) 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; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the sent SIP MESSAGE request, the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.3.2 Terminating procedures | Upon receiving a "SIP MESSAGE request for remotely initiated group call for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response and skip the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) 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; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.5.4 Controlling MCPTT function procedures | Upon receiving:
- a "SIP MESSAGE request for remotely initiated group call request for controlling MCPTT function"; or
- a "SIP MESSAGE request for remotely initiated group call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if:
a) there is a <request-type> element set to a value of "remotely-initiated-group-call-request" contained in the <anyExt> element in the <mcptt-Params> element contained in the <mcpttinfo> root element contained in the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request; and
b) if the MCPTT user identified by the MCPTT ID in the "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the SIP MESSAGE request is not affiliated with the MCPTT group identified by the <mcptt-request-uri> in the application/vnd.3gpp. mcptt-info+xml MIME body as determined by the procedures of clause 6.3.6;
then:
a) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) 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];
6) 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];
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request with the following clarifications:
a) shall set the <mcptt-calling-group-id> to the MCPTT group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall set the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the MCPTT ID contained in the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the received SIP MESSAGE request;
8) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated with the MCPTT user identified by the MCPTT ID contained in the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating 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 3: If the terminating participating 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 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
9) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
11) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, the controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6 Change of in-progress imminent peril state of the MCPTT group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.1 General | Clause 10.1.6 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for the on-network canceling of in-progress imminent peril state of the MCPTT group while there is no MCPTT session is ongoing on the MCPTT group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.2.1 MCPTT group in-progress imminent peril state cancel initiation | Upon receiving a request from an MCPTT user to cancel the in-progress imminent peril state on a prearranged MCPTT group on which there is no call ongoing, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress imminent peril state of the MCPTT group as determined by the procedures of clause 6.2.8.1.A and clause 6.2.8.1.10, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress imminent peril state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity;
b) the <imminentperil-ind> element set to a value of "false";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 2: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
6) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
7) shall set MCPTT imminent peril group state to "MIG 3: cancel-pending"; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT imminent peril group state to "MIG 1: no-imminent peril".
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT imminent peril group state to "MIG 2: in-progress". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.2.2 Reception of MCPTT group in-progress imminent peril state cancel notification | Upon receiving a "SIP MESSAGE request for imminent peril state change notification for terminating MCPTT client" for the cancellation of the in-progress imminent peril state of the MCPTT group, the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress imminent peril state of the MCPTT group including the following:
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril";
2) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
3) shall send the SIP 200 (OK) response towards the participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.3.1 Originating procedures | a) 10.1.6.3.1.1 Reception of MCPTT group in-progress imminent peril state cancel initiation
Upon receipt of a "SIP MESSAGE request for imminent peril state change request for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the MCPTT user is not affiliated with the MCPTT group as determined by clause 9.2.2.2.11, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
5) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
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 group identity 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.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5);
8) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) 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;
11) 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];
12) 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];
13) 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; and
14) shall send the SIP MESSAGE request towards the controlling MCPTT function as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent above:
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function; and
2) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.3.2 Terminating Procedures | b) 10.1.6.3.2.1 Reception of MCPTT group in-progress imminent peril state cancel notification
Upon receipt of a "SIP MESSAGE request for imminent peril state change notification for terminating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall 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; and
6) shall send the SIP MESSAGE request towards MCPTT client as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent above:
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4]; and
2) shall send the SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.4 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.6.4.1 Terminating Procedures | c) 10.1.6.4.1.1 Reception of MCPTT group in-progress imminent peril state cancel initiation
Upon receipt of a "SIP MESSAGE request for imminent peril state change request for controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the received SIP MESSAGE request is an unauthorised request for an MCPTT in-progress imminent peril state of group cancellation as specified in clause 6.3.3.1.13.B and clause 6.3.3.1.13.6, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
4) set the in-progress imminent peril state of the MCPTT group to a value of "false";
5) cache the information that the MCPTT user has cancelled the outstanding in-progress imminent peril state of the group and clear the cache of the all MCPTT ID of the MCPTT users that triggered the setting of the in-progress imminent peril state of the MCPTT group to "true";
6) for each of the affiliated members of the group shall:
a) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's imminent peril call as specified in clause 6.3.3.1.11;
b) set the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
c) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
d) send the SIP MESSAGE request towards the terminating participating MCPTT function according to 3GPP TS 24.229 [4];
7) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
8) shall send the SIP 200 (OK) response towards the originating participating MCPTT function to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx, SIP 4xx, 5xx or 6xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2 Off-network group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.1.1 Common Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.1.1.1 MONP message transport | In order to participate in a call of an MCPTT group, the MCPTT client:
1) shall send the MONP message as a UDP message to the multicast IP address of the MCPTT group, to UDP port 8809, with an IP time-to-live set to 255; and
2) shall treat UDP messages received on the multicast IP address of the MCPTT group and on port 8809 as received MONP messages.
The MONP message is the entire payload of the UDP message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.1.1.2 Session description | For an off-network MCPTT session, only MCPTT speech is used.
One off-network MCPTT session includes one media-floor control entity.
The MCPTT client shall generate an SDP body for a group call in accordance with rules and procedures of RFC4566 [12].
The MCPTT client:
1) shall include in the session-level section:
a) the "o=" field with the <username> portion set to a dash;
b) the "s=" field with the <session name> portion set to a dash; and
c) the "c=" field with the <nettype> portion set to "IN", the <addrtype> portion set to the IP version of a multicast IP address of the MCPTT group and the <connection-address> portions set to the multicast IP address of the MCPTT group;
2) shall include the media-level section for MCPTT speech consisting of:
a) the "m=" field with the <media> portion set to "audio", the <port> portion set to a port number for MCPTT speech of the MCPTT group, the <proto> field set to "RTP/AVP" and <fmt> portion set indicating RTP payload type numbers;
b) the "i=" field with the <session description> portion set to "speech";
c) the "a=fmtp:" attribute(s), the "a=rtpmap:" attribute(s) or both, indicating the codec(s) and media parameters of the MCPTT speech with the following clarification:
i) if the "/<x>/<x>/Common/PreferredVoiceCodec" leaf node is present in the group document configured on the group management client as specified in 3GPP TS 24.483 [45] containing an RTP payload format name as specified in IETF RFC 4566 [12], indicating a preferred voice codec for an MCPTT group; and
ii) if the MCPTT client supports the encoding name indicated in the value of the "name" attribute;
then the MCPTT client:
i) shall insert the value of the "/<x>/<x>/Common/PreferredVoiceCodec" leaf node in the <encoding name> field of the "a=rtpmap" attribute as defined in IETF RFC 4566 [12]; and
d) the "a=rtcp:" attribute indicating port number to be used for RTCP at the MCPTT client selected according to the rules and procedures of IETF RFC 3605 [13], if the media steam uses other than the default IP address; and
3) shall include the media-level section for media-floor control entity consisting of:
a) an "m=" line, with the <media> portion set to "application", the <port> portion set to a port number for media-floor control entity of the MCPTT group, the <proto> field set to "udp" and <fmt> portion set to "MCPTT"; and
b) the "a=fmtp:MCPTT" attribute indicating the parameters of the media-floor control entity as specified 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2 Basic call control | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.1 General | In this release of specification, media streams of off-network group call cannot be modified and the SDP is the same for the entire duration of the call.
The maximum number of simultaneous off-network group calls is limited by the value of "/<x>/Common/MCPTTGroupCall/MaxCallN4" leaf node present in the UE configuration as specified in 3GPP TS 24.483 [45]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.2 Basic call control state machine | The Figure 10.2.2.2-1 gives an overview of the main states and transitions on the UE for call control.
Each call control state machine is per MCPTT group ID.
Figure 10.2.2.2-1: Basic call control state machine
The following pieces of information are associated with the basic call control state machine:
a) the stored call identifier of the call;
b) the probe response value of the call;
c) the stored refresh interval of the call;
d) the stored SDP body of the call;
e) the stored originating MCPTT user ID of the call;
f) the stored MCPTT group ID of the call; and
g) the stored call start time of the call.
The basic call control state machine has a related call type control state machine described in clause 10.2.3.2.
When sending the message, MCPTT client indicates the stored current ProSe per-packet priority associated with the call type control state machine to the lower layers. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3 Call Control states | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.1 S1: start-stop | This state exists for UE, when the UE is not part of an ongoing call.
This state is the start state of this state machine.
This state is the stop state of this state machine. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.2 S2: waiting for call announcement | This state exists for UE, when the UE has sent a GROUP CALL PROBE message and is waiting for a GROUP CALL ANNOUNCEMENT message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.3 S3: part of ongoing call | This state exists for UE, when the UE is part of an ongoing group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.4 S4: pending user action without confirm indication | This state exists for UE, when the UE has presented a notification to the MCPTT user for the received GROUP CALL ANNOUNCEMENT message, is waiting for a response and is not expected to send confirm indication. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.5 S5: pending user action with confirm indication | This state exists for UE, when the UE has presented a notification to the MCPTT user for the received GROUP CALL ANNOUNCEMENT message, is waiting for a response and is expected to send confirm indication. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.6 S6: ignoring incoming call announcements | This state exists for UE, when the group call was rejected or released, GROUP CALL ANNOUNCEMENT message was sent or received and GROUP CALL ANNOUNCEMENT messages continue being received. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.3.7 S7: waiting for call announcement after call release | This state exists for UE, when the group call was released, GROUP CALL ANNOUNCEMENT message was neither sent nor received and GROUP CALL PROBE was sent. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.4 Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.4.1 General | 10.2.2.4.1.1 Call announcement timer calculation
10.2.2.4.1.1.1 Periodic call announcement timer calculation
The MCPTT client:
1) shall generate a random number, X, with uniform distribution between 0 and 1; and
2) shall set the TFG2 (periodic announcement) timer as follows:
- TFG2 (periodic announcement) = the refresh interval of the call * (2/3 + 2/3*X) seconds.
10.2.2.4.1.1.2 Call announcement timer calculation after CALL PROBE
The MCPTT client:
1) shall generate a random number, X, with uniform distribution between 0 and 1; and
2) shall set the TFG2 (periodic announcement) timer as follows:
- TFG2 (periodic announcement) = 1/12*X seconds.
10.2.2.4.1.2 Max duration timer calculation
The MCPTT client shall set the TFG6 (max duration) timer as follows:
- TFG6 (max duration) = X – (Y – Z) seconds, where:
- X = value of "/<x>/<x>/OffNetwork/MaxDuration" leaf node present in group configuration as specified in 3GPP TS 24.483 [45];
- Y = current UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds);
- Z = Call start time IE of the GROUP CALL ANNOUNCEMENT message or the stored call start time, if a GROUP CALL ANNOUNCEMENT message was not received that caused this max duration timer calculation to be invoked. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.4.2 Call Probe | 10.2.2.4.2.1 Call probe initiation
When in the "S1: start-stop" state, upon an indication from an MCPTT user to initiate a group call for an MCPTT group ID, the MCPTT client:
1) shall store the MCPTT group ID as the MCPTT group ID of the call;
2) shall create a call type control state machine as described in clause 10.2.3.2;
3) shall generate a GROUP CALL PROBE message as specified in clause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
4) shall send the GROUP CALL PROBE message as specified in clause 10.2.1.1.1;
5) shall start timer TFG3 (call probe retransmission);
6) shall start timer TFG1 (wait for call announcement); and
7) shall enter the "S2: waiting for call announcement" state.
10.2.2.4.2.2 Call probe retransmission
When in the "S2: waiting for call announcement" state, upon expiration of TFG3 (call probe retransmission), the MCPTT client:
1) shall generate a GROUP CALL PROBE message as specified in clause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
2) shall send the GROUP CALL PROBE message as specified in clause 10.2.1.1.1;
3) shall start timer TFG3 (call probe retransmission); and
4) shall remain in the "S2: waiting for call announcement" state.
10.2.2.4.2.3 Receiving GROUP CALL PROBE message when participating in the ongoing call
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL PROBE message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) if the stored probe response value of the call is set to "false":
a) shall stop timer TFG2 (call announcement);
b) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.2; and
c) shall set the stored probe response of the call to "true"; and
2) shall remain in the "S3: part of ongoing call" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.4.3 Call setup | 10.2.2.4.3.1 Not receiving any response to GROUP CALL PROBE message
When in the "S2: waiting for call announcement" state, upon expiry of timer TFG1 (wait for call announcement), the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission), if running;
2) shall generate an SDP body as specified in clause 10.2.1.1.2 and store it as the SDP body of the call;
3) shall generate a random number with uniform distribution between 0 and 65535 and store it as the call identifier of the call;
4) shall select refresh interval value and store it as the refresh interval of the call;
5) shall store own MCPTT user ID as the originating MCPTT user ID of the call;
6) shall store the current UTC time as the call start time of the call;
7) shall generate a GROUP CALL ANNOUNCEMENT message as specified in clause 15.1.3. In the GROUP CALL ANNOUNCEMENT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Call type IE to the stored current call type associated with the call type control state machine;
c) shall set the Refresh interval IE to the stored refresh interval of the call;
d) shall set the SDP IE to the stored SDP body of the call;
e) shall set the Originating MCPTT user ID IE to the stored originating MCPTT user ID of the call;
f) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
g) shall set the Call start time IE to the stored call start time of the call;
h) shall set the Last call type change time IE to the stored last call type change time of the call associated with call type control state machine;
i) shall set the Last user to change call type IE to last user to change call type associated with call type control state machine; and
j) may include the Confirm mode indication IE;
8) shall send the GROUP CALL ANNOUNCEMENT message as specified in clause 10.2.1.1.1;
9) shall establish a media session based on the stored SDP body of the call;
10) shall start floor control as originating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
11) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
12) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
13) shall enter the "S3: part of ongoing call" state.
Note: In this release of the specification, the refresh interval of the call is fixed to 10 seconds.
10.2.2.4.3.2 Receiving a GROUP CALL ANNOUNCEMENT message
When in the "S2: waiting for call announcement" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission);
2) shall stop timer TFG1 (wait for call announcement);
3) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
4) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
5) shall store the value of the originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the Originating MCPTT user ID of the call;
6) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
7) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
8) shall establish a media session based on the stored SDP body of the call;
9) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
10) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2;
11) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
12) shall enter the "S3: part of ongoing call" state.
10.2.2.4.3.3 Receiving a GROUP CALL ANNOUNCEMENT message when not participating in the ongoing call
When in the "S1: start-stop" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE not matching MCPTT group ID of the call stored for other state machines, the MCPTT client:
1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;
4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
5) shall store the value of the MCPTT group ID IE of the GROUP CALL ANNOUNCEMENT message as the MCPTT group ID of the call;
6) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
7) shall create a call type control state machine as described in clause 10.2.3.2;
8) if the terminating UE is configured that the terminating MCPTT user acknowledgement is required upon a terminating call request reception:
a) shall start timer TFG4 (waiting for the user);
b) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE, shall enter the "S5: pending user action with confirm indication" state; and
c) if the GROUP CALL ANNOUNCEMENT message does not contains the Confirm mode indication IE, shall enter the "S4: pending user action without confirm indication" state; and
9) if the terminating UE is configured that the terminating MCPTT user acknowledgement is not required upon a terminating call request reception:
a) shall establish a media session based on the stored SDP body of the call;
b) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
c) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE:
i) shall generate a GROUP CALL ACCEPT message as specified in clause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier of the call;
B) shall set the Sending MCPTT user ID IE to own MCPTT user id;
C) shall set the Call type IE to the stored current call type associated with the call type control state machine; and
D) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
ii) shall send the GROUP CALL ACCEPT message as specified in clause 10.2.1.1.1;
d) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2;
e) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
f) shall enter the "S3: part of ongoing call" state.
10.2.2.4.3.4 MCPTT user accepts the terminating call with confirm indication
When in the "S5: pending user action with confirm indication" state, upon indication from the MCPTT user to accept the incoming group call, the MCPTT client:
1) shall establish a media session based on the stored SDP body of the call;
2) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall generate a GROUP CALL ACCEPT message as specified in clause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Sending MCPTT user ID IE to own MCPTT user id;
c) shall set the Call type IE to the stored current call type associated with the call type control state machine; and
d) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
4) shall send the GROUP CALL ACCEPT message as specified in clause 10.2.1.1.1;
5) shall stop timer TFG4;
6) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
7) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
8) shall enter the "S3: part of ongoing call" state.
10.2.2.4.3.5 MCPTT user accepts the terminating call without confirm indication
When in the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to accept the incoming group call, the MCPTT client:
1) shall establish a media session based on the stored SDP body of the call;
2) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall stop timer TFG4;
4) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
5) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
6) shall enter the "S3: part of ongoing call" state.
10.2.2.4.3.6 Receiving GROUP CALL ACCEPT message
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ACCEPT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) can inform the MCPTT user about the call acceptance; and
2) shall remain in the "S3: part of ongoing call" state.
10.2.2.4.3.7 MCPTT user rejects the terminating call
When in the "S5: pending user action with confirm indication" state or the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to reject the incoming group call, the MCPTT client:
1) shall stop timer TFG4 (waiting for the user);
2) shall start timer TFG5 (not present incoming call announcements); and
3) shall enter the "S6: ignoring incoming call announcements" state.
10.2.2.4.3.8 MCPTT user does not act on terminating call
When in the "S5: pending user action with confirm indication" state or the "S4: pending user action without confirm indication" state, upon expiration of timer TFG4 (waiting for the user), the MCPTT client:
1) shall start timer TFG5 (not present incoming call announcements); and
2) shall enter the "S6: ignoring incoming call announcements" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.2.2.4.4 Periodic group call announcement | 10.2.2.4.4.1 Sending periodic call announcement
When in the "S3: part of ongoing call" state, upon expiry of timer TFG2 (call announcement), the MCPTT client:
1) shall generate a GROUP CALL ANNOUNCEMENT message as specified in clause 15.1.3. In the GROUP CALL ANNOUNCEMENT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Call type IE to the stored current call type associated with the call type control state machine;
c) shall set the Refresh interval IE to the stored refresh interval of the call;
d) shall set the SDP IE to the stored SDP body of the call;
e) shall set the Originating MCPTT user ID IE to the stored originating MCPTT user ID of the call;
f) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
g) shall set the Last call type change time IE to the stored last call type change time of the call associated with call type control state machine;
h) shall set the Last user to change call type IE to last user to change call type associated with call type control state machine;
i) shall set the Call start time IE to the stored call start time of the call;
j) if the stored probe response value of the call is set to "true", shall include Probe response IE;
2) shall send the GROUP CALL ANNOUNCEMENT message as specified in clause 10.2.2.1.1.1;
3) if the stored probe response value of the call is set to "true", shall set the stored probe response value of the call to "false";
4) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
5) shall remain in the "S3: part of ongoing call" state.
10.2.2.4.4.2 Receiving periodic call announcement
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the Call start time IE being the same as the stored call start time of the call, the Last call type change time IE being the same as the stored last call type change time of the call associated with the call type control state machine, the Last user to change call type IE being the same as the stored last user to change call type of the call associated with the call type control state machine and the Call identifier IE being the same as the stored call identifier of the call and Call type IE same as the stored current call type associated with the call type control state machine and:
1) if the stored probe response value of the call is set to "true" and GROUP CALL ANNOUNCEMENT message contains Probe response IE; or
2) if the stored probe response value of the call is set to "false":
the MCPTT client,
1) shall stop timer TFG2 (call announcement);
2) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1;
3) shall set the stored probe response of the call to "false", if set to "true"; and
4) shall remain in the "S3: part of ongoing call" state. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.