hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.1 General | The MCPTT server obtains information that it needs to implement service authorization specific requirements from:
a) any received third-party SIP REGISTER request (e.g. including information contained in the body of the third-party SIP REGISTER request) as specified in 3GPP TS 24.229 [4]. The body will carry the SIP REGISTER request as sent by the MCPTT client and may contain information needed for service authorization; or
b) any received SIP PUBLISH request for MCPTT server settings containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters. The body of the SIP PUBLISH request will contain information needed for service authorization.
7.3.1A Confidentiality and Integrity Protection
When the MCPTT server receives a SIP REGISTER request sent from the MCPTT client contained within a message/sip MIME body of a received third-party SIP REGISTER request or a SIP PUBLISH request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCPTT server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the MCPTT server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the MCPTT server decrypts the protected content.
Upon receiving:
- a SIP REGISTER request containing an application/vnd.3gpp.mcptt-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client; or
- a SIP PUBLISH request containing an application/vnd.3gpp.mcptt-info+xml MIME body and an application/poc-settings+xml MIME body;
the MCPTT server:
1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in clause 6.6.3.4.1 for each XML MIME body;
2) if integrity protection has been applied, shall use the keying data described in clause 6.6.3.2 and the procedures described in clause 6.6.3.4.2 to verify the integrity of each of the XML MIME bodies; and
3) if all integrity protection checks succeed, shall continue with the remaining steps of this clause.
Upon receiving:
- a SIP REGISTER request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-access-token> element and an <mcptt-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client; or
- a SIP PUBLISH request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-access-token> element and an <mcptt-client-id> element, and an application/poc-settings+xml MIME body;
the MCPTT server:
1) shall determine if confidentiality protection has been applied to the <mcptt-access-token> element and the <mcptt-client-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body, by following the procedures in clause 6.6.2.4.1;
2) if confidentiality protection has been applied to the <mcptt-access-token> element and <mcptt-client-id> element:
a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [78], along with the procedures described in clause 6.6.2.4.2 to:
i) decrypt the received access token in the <mcptt-access-token> element in the application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) decrypt the received MCPTT client ID in the <mcptt-client-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if the decryption procedure succeeds, shall identify the MCPTT ID and the MCPTT client ID from the decrypted values; and
c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful;
3) if confidentiality protection has been applied to only one of the <mcptt-access-token> element or the <mcptt-client-id> element:
a) shall determine that confidentiality protection has not been successful;
4) if confidentiality protection has not been applied:
a) shall identify the MCPTT ID from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall identify the MCPTT client ID from the <mcptt-client-id> element received in the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receiving a SIP PUBLISH request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element, an <mcptt-client-id> element, and an application/poc-settings+xml MIME body, the MCPTT server:
1) shall determine if confidentiality protection has been applied to the <mcptt-request-uri> element and the <mcptt-client-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body by following the procedures in clause 6.6.2.4.1;
2) if confidentiality protection has been applied to the <mcptt-request-uri> element and the <mcptt-client-id> element:
a) shall use the keying information described in clause 6.6.2.2 along with the procedures described in clause 6.6.2.4.2 to:
i) decrypt the received encrypted MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) decrypt the received encrypted MCPTT client ID in the <mcptt-client-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if all decryption procedures succeed, shall identify the MCPTT ID and MCPTT client ID from the decrypted values; and
c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful;
3) if confidentiality protection has been applied to only one of the <mcptt-request-uri> element or <mcptt-client-id> element:
a) shall determine that confidentiality protection has not been successful;
4) if confidentiality protection has not been applied:
a) shall identify the MCPTT ID from the contents of the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall identify the MCPTT client ID from the <mcptt-client-id> element received in the application/vnd.3gpp.mcptt-info+xml MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.2 SIP REGISTER request for service authorisation | The MCPTT server shall support obtaining service authorization specific information from the SIP REGISTER request sent from the MCPTT client and included in the body of a third-party SIP REGISTER request.
NOTE 1: 3GPP TS 24.229 [4] defines how based on initial filter criteria the SIP REGISTER request sent from the UE is included in the body of the third-party SIP REGISTER request.
Upon receiving a third party SIP REGISTER request with a message/sip MIME body containing the SIP REGISTER request sent from the MCPTT client containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-access-token> element and an <mcptt-client-id> element within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client, the MCPTT server:
1) shall identify the IMS public user identity from the third-party SIP REGISTER request;
2) shall identify the MCPTT ID from the SIP REGISTER request sent from the MCPTT client and included in the message/sip MIME body of the third-party SIP REGISTER request by following the procedures in clause 7.3.1A;
2a) shall check if the number of maximum simultaneous authorizations supported for the MCPTT user is specified in the <user-max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT user profile (see the MCPTT user profile configuration document in 3GPP TS 24.484 [50]), and if present, shall check whether it has been reached. If reached, the MCPTT server shall not continue with the rest of the steps in this clause;
2b) if the <user-max-simultaneous-authorizations> element of the <anyExt> element is not present in the <OnNetwork> element of the MCPTT user profile (see the MCPTT user profile configuration document in 3GPP TS 24.484 [50]), shall check if the number of maximum simultaneous authorizations supported for any MCPTT user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) has been reached. If reached, the MCPTT server shall not continue with the rest of the steps in this clause;
2c) if the <gw-mcptt-usage> element is present and set to true, the MCPTT server shall check that the MCPTT gateway UE used is service authorized. If the MCPTT gateway UE is not service authorized, the MCPTT server shall reject the request and not continue with the rest of the steps in this clause;
NOTE 2: The <gw-mcptt-usage> element indicates to the MCPTT system that this client uses a MCPTT gateway UE in 3GPP network and resources can be allocated over Rx, N5 or N33.
3) shall perform service authorization for the identified MCPTT ID as described in 3GPP TS 33.180 [78];
4) if service authorization was successful, shall bind the MCPTT ID and the MCPTT client ID to the IMS public user identity;
4a) if service authorization was successful and if the service authorization request was from an MCPTT user who is previously MCPTT service authorized on another MCPTT client (as determined by a comparison of the received MCPTT client ID with the MCPTT client ID of existing bindings), keep the current bindings and create a new binding between the MCPTT ID and the IMS public user identity;
NOTE 3: The MCPTT server will store the binding of the MCPTT ID, MCPTT client ID, IMS public user identity and an identifier addressing the MCPTT server in an external database.
5) if a Resource-Share header field with the value "supported" is contained in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCPTT ID and the MCPTT client ID to the identity of the MCPTT UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the incoming third-party REGISTER request;
6) if more than one binding exists for the MCPTT ID, shall include in the SIP 200 (OK) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in annex F.1 with an <multiple-devices-ind> element set to the value "true"; and
7) if the service authorization was successful in the partner MCPTT system to which the MCPTT user is migrating, shall follow the procedures in clause 7A.3.6. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.3 SIP PUBLISH request for service authorisation and service settings | The MCPTT server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCPTT server settings.
Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value;
2) an application/poc-settings+xml MIME body; and
3) an application/vnd.3gpp.mcptt-info+xml MIME body containing an <mcptt-access-token> element and an <mcptt-client-id> element;
the MCPTT server:
1) shall identify the IMS public user identity from the P-Asserted-Identity header field;
2) shall perform the procedures in clause 7.3.1A;
3) if the procedures in clause 7.3.1A were not successful shall send a SIP 403 (Forbidden) response towards the MCPTT client with the warning text set to: "140 unable to decrypt XML content" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
3a) shall check if the number of maximum simultaneous authorizations supported for the MCPTT user is specified in the <user-max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT user profile (see the MCPTT user profile configuration document in 3GPP TS 24.484 [50]) and, if present, shall check whether it has been reached. If reached, the MCPTT server shall send a SIP 486 (Busy Here) response towards the MCPTT client with the warning text set to: "164 maximum number of service authorizations reached" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps in this clause;
3b) if the <user-max-simultaneous-authorizations> element of the <anyExt> element is not present in the <OnNetwork> element of the MCPTT user profile (see the MCPTT user profile configuration document in 3GPP TS 24.484 [50]), shall check if the number of maximum simultaneous authorizations supported for any MCPTT user as specified in the <max-simultaneous-authorizations> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) has been reached. If reached, the MCPTT server shall send a SIP 486 (Busy Here) response towards the MCPTT client with the warning text set to: "164 maximum number of service authorizations reached" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps in this clause;
3c) if the <gw-mcptt-usage> element is present and set to true, the MCPTT server shall check that the MCPTT gateway UE used is service authorized. If the MCPTT gateway UE is not service authorized, the MCPTT server shall reject the request and not continue with the rest of the steps in this clause;
NOTE 1: The <gw-mcptt-usage> element indicates to the MCPTT system that this client uses a MCPTT gateway UE in 3GPP network and resources can be allocated over Rx, N5 or N33.
4) shall perform service authorization for the identified MCPTT ID as described in 3GPP TS 33.180 [78];
5) if service authorization was successful:
a) shall bind the MCPTT ID and MCPTT client ID to the IMS public user identity;
b) if the service authorization request was from an MCPTT user who is previously MCPTT service authorized on another MCPTT client (as determined by a comparison of the received MCPTT client ID with the MCPTT client ID of existing bindings), keep the current bindings and create a new binding between the MCPTT ID, MCPTT client ID and the IMS public user identity; and
c) if a Resource-Share header field with the value "supported" was included in the "message/sip" MIME body of the third-party REGISTER request, shall bind the MCPTT ID to the identity of the MCPTT UE contained in the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request that contained this IMS public user identity;
NOTE 2: The MCPTT server will store the binding MCPTT ID, MCPTT client ID, IMS public user identity and an identifier addressing the MCPTT server in an external database.
6) if service authorization was not successful, shall send a SIP 403 (Forbidden) response towards the MCPTT client with the warning text set to: "101 service authorisation failed" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [37] and if processing of the SIP request was not successful, do not continue with the rest of the steps;
8) shall cache the received MCPTT service settings until the MCPTT service settings expiration timer expires;
9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [4] with:
a) if more than one binding exists for the MCPTT ID, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with a <multiple-devices-ind> element set to the value "true";
10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCPTT client.
10a) If the <multiplex-support> element is present and set to true the MCPTT server shall use this as an indication that the MCPTT client supports multiplexing of media plane control channels and media streams. Absence of the <multiplex-support> element or if the <multiplex-support element is set to false shall be used as an indication that the MCPTT client does not support multiplexing of media plane control channels and media streams.
NOTE 3: The MCPTT server uses the information about support of multiplexing received from the served MCPTT clients to determine when and where to use multiplexing of media plane control channels and/or media streams.
11) shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73], if not already stored at the MCPTT server, and use the <selected-user-profile-index> element of the poc-settings event package, if included, to identify the active MCPTT user profile for the MCPTT client;
NOTE 4: If the <selected-user-profile-index> element of the poc-settings event package is included, then only that MCPTT user profile is needed to be downloaded from the MCPTT user database.
12) if there is no <selected-user-profile-index> element included in the poc-settings event package, then, if multiple MCPTT user profiles are stored at the MCPTT server or downloaded for the MCPTT user from the MCPTT user database, shall determine the pre-selected MCPTT user profile to be used as the active MCPTT user profile by identifying the MCPTT user profile (see the MCPTT user profile document in 3GPP TS 24.484 [50]) in the collection of MCPTT user profiles that contains a <Pre-selected-indication> element;
NOTE 5: If only one MCPTT user profile is stored at the MCPTT server or only one MCPTT user profile is downloaded from the MCPTT user database, then, by default, this MCPTT user profile is the pre-selected MCPTT user profile.
13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCPTT user profile document with one or more <entry> elements containing an MCPTT group ID (see the MCPTT user profile document in 3GPP TS 24.484 [50]) for the served MCPTT ID, shall perform implicit affiliation as specified in clause 9.2.2.2.15; and
14) if the service authorization was successful in the partner MCPTT system to which the MCPTT user is migrating, shall follow the procedures in clause 7A.3.6. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.4 Receiving SIP PUBLISH request for MCPTT service settings only | Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value;
2) an application/poc-settings+xml MIME body; and
3) an application/vnd.3gpp.mcptt-info+xml MIME body containing an <mcptt-request-uri> element and an <mcptt-client-id> element;
The MCPTT server:
1) shall identify the IMS public user identity from the P-Asserted-Identity header field;
2) shall perform the procedures in clause 7.3.1A;
3) if the procedures in clause 7.3.1A were not successful, shall send a SIP 403 (Forbidden) response towards the MCPTT client with the warning text set to: "140 unable to decrypt XML content" 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 verify that a binding between the IMS public user identity in the Request-URI and the MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml exists at the MCPTT server;
5) if a binding exists between the IMS public user identity and the MCPTT ID in the request and the validity period of the binding has not expired shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73] if not already stored at the MCPTT server;
6) if a binding does not exist between the IMS public user identity and the MCPTT ID in the request or the binding exists, but the validity period of the binding has expired, shall reject the SIP PUBLISH 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;
7) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [37] and if processing of the SIP request was not successful, do not continue with the rest of the steps;
8) shall cache the received MCPTT service settings until the MCPTT service settings expiration timer expires;
9) shall send a SIP 200 (OK) response according 3GPP TS 24.229 [4];
10) shall use the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package as the current Answer-Mode Indication of the MCPTT client.
10a) If the <multiplex-support> element is present and set to true the MCPTT server shall use this as an indication that the MCPTT client supports multiplexing of media plane control channels and media streams. Absence of the <multiplex-support> element or if the <multiplex-support element is set to false shall be used as an indication that the MCPTT client does not support multiplexing of media plane control channels and media streams.
NOTE 1: The MCPTT server uses the information about support of multiplexing received from the served MCPTT clients to determine when and where to use multiplexing of media plane control channels and/or media streams.
11) shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73] if not already stored at the MCPTT server and use the <selected-user-profile-index> element of the poc-settings event package if included to identify the active MCPTT user profile for the MCPTT client;
NOTE 2: If the <selected-user-profile-index> element of the poc-settings event package is included then only that MCPTT user profile is needed to be downloaded from the MCPTT user database.
12) if there is no <selected-user-profile-index> element included in the poc-settings event package then if multiple MCPTT user profiles are stored at the MCPTT server or downloaded for the MCPTT user from the MCPTT user database, shall determine the pre-selected MCPTT user profile to be used as the active MCPTT user profile by identifying the MCPTT user profile (see the MCPTT user profile document in 3GPP TS 24.484 [50]) in the collection of MCPTT user profiles that contains a <Pre-selected-indication> element; and
NOTE 3: If only one MCPTT user profile is stored at the MCPTT server or only one MCPTT user profile is downloaded from the MCPTT user database, then by default this MCPTT user profile is the pre-selected MCPTT user profile.
13) if an <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCPTT user profile document with one or more <entry> elements containing an MCPTT group ID (see the MCPTT user profile document in 3GPP TS 24.484 [50]) for the served MCPTT ID, shall perform implicit affiliation as specified in clause 9.2.2.2.15. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.5 Receiving SIP PUBLISH request with "Expires=0" | Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value; and
2) an Expires header field set to 0;
the MCPTT server:
1) shall identify the IMS public user identity from the P-Asserted-Identity header field;
2) shall process the SIP PUBLISH request according to rules and procedures of IETF RFC 3903 [37] and if processing of the SIP request was successful, continue with the rest of the steps;
3) shall remove the MCPTT service settings;
NOTE: Removal of MCPTT service settings includes removal of all group affiliations.
4) shall remove the binding between the MCPTT ID and public user identity; and
5) shall send a SIP 200 (OK) response according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.6 Subscription to and notification of MCPTT service settings | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.6.1 Receiving subscription to MCPTT service settings | Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCPTT function of the served MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID served by the MCPTT server;
3) 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]; and
3) the Event header field of the SIP SUBSCRIBE request contains the 'poc-settings' event type.
the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) if the originating MCPTT ID is different than the served MCPTT ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and
4) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26] and IETF RFC 4354 [55].
For the duration of the subscription, the MCPTT server shall notify subscriber about changes of the MCPTT service settings of the subscribed MCPTT user, as described in clause 7.3.6.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.6.2 Sending notification of change of MCPTT service settings | In order to notify the subscriber about changes of the MCPTT service settings of the subscribed MCPTT client of the subscribed MCPTT user, the MCPTT server:
1) shall generate an application/poc-settings+xml MIME body containing:
a) the <am-settings> element of the poc-settings event package set to the current answer mode setting of the MCPTT client according to IETF RFC 4354 [55]; and
b) the <selected-user-profile-index> element as defined in clause 7.4.1.2.2 identifying the active MCPTT user profile; and
2) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26] and IETF RFC 4354 [55] with the constructed application/poc-settings+xml MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3.7 Sending a CSK key download message | If confidentiality protection is enabled as specified in clause 6.6.2.3.1, and if the participating MCPTT function received a Client Server Key (CSK) within a SIP REGISTER request for service authorisation or SIP PUBLISH request for service authorisation, the participating MCPTT function may decide to update the CSK. In this case, the participating MCPTT function shall perform a key download procedure for the CSK. The participating MCPTT function:
1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
5) shall include an application/mikey MIME body containing the CSK-ID and the CSK encrypted within a MIKEY message to the MC client as specified in clause 9.2.1 of 3GPP TS 33.180 [78] in the body of the SIP MESSAGE request;
6) shall send the SIP MESSAGE request towards the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4 Coding | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4.1 Extension of MIME types | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4.1.1 General | The parent clause of this clause defines extensions of MIME type defined in other documents. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4.1.2 Extension of application/poc-settings+xml MIME type | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4.1.2.1 Introduction | The parent clause of this clause describes extension of the application/poc-settings+xml MIME body specified in IETF RFC 4354 [55]. The extension is used to indicate the selected MCS user profile at an MC client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.4.1.2.2 Syntax | The application/poc-settings+xml MIME body indicating the selected MCS user profile at an MC client is constructed according to IETF RFC 4354 [55] and:
1) contains a <poc-settings> root element according to IETF RFC 4354 [55];
2) contains one or more <entity> child element according to IETF RFC 4354 [55] of the <poc-settings> element;
3) contains one <selected-user-profile-index> child element defined in the XML schema defined in table 7.4.1.2.2-2, of the <entity> element; and
NOTE: The <selected-user-profile-index> element is validated by the <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <entity> element.
4) contains zero or one <multiplex-support> child element defined in the XML schema defined in table 7.4.1.2.2-2, of the <entity> element.
The application/poc-settings+xml MIME body refers to namespaces using prefixes specified in table 7.4.1.2.2-1.
Table 7.4.1.2.2-1: Assignment of prefixes to namespace names in the application/poc-settings+xml MIME body
Prefix
Namespace
PoC1Set
urn:oma:params:xml:ns:poc:poc-settings
mcs10Set
urn:3gpp:mcsSettings:1.0
Table 7.4.1.2.2-2: XML schema with elements and attributes extending the application/poc-settings+xml MIME body
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:mcsSettings:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcs10Set="urn:3gpp:mcsSettings:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCS specific "entity" child elements -->
<xs:element name="selected-user-profile-index" type="mcs10Set:selected-user-profile-indexType"/>
<xs:element name="multiplex-support" type="xs:boolean"/>
<xs:complexType name="selected-user-profile-indexType">
<xs:sequence>
<xs:element name="user-profile-index" type="xs:nonNegativeInteger"/>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:schema>
An example application/poc-settings+xml MIME body showing the MC service settings for two MC clients as might be included in the body of a SIP NOTIFY request is shown in table 7.4.1.2.2-3.
Table 7.4.1.2.2-3: Example application/poc-settings+xml MIME body showing the MC service settings for two MC clients as might be included in the body of a SIP NOTIFY request
<?xml version="1.0" encoding="UTF-8"?>
<poc-settings xmlns="urn:oma:params:xml:ns:poc:poc-settings">
<entity id="urn:uuuid:do39s8zksn2d98x">
<am-settings>
<answer-mode>automatic</answer-mode>
</am-settings>
<selected-user-profile-index>
<user-profile-index>1</user-profile-index>
</selected-user-profile-index>
<multiplex-support>true</multiplex-support>
</entity>
<entity id="urn:uuuid:ksn2d98xdo39s8z">
<am-settings>
<answer-mode>manual</answer-mode>
</am-settings>
<selected-user-profile-index>
<user-profile-index>2</user-profile-index>
</selected-user-profile-index>
<multiplex-support>true</multiplex-support>
</entity>
</poc-settings>
7A Migration procedures
7A.1 General
This clause describes the migration service authorization procedure and the migration service deauthorization procedure for the MCPTT client. The MCPTT client uses SIP REGISTER to perform authorization for migration.
This clause also covers the notification handling about the successful completion of MCPTT user service authorization during migration to the partner MCPTT system.
7A.2 MCPTT client procedures
7A.2.1 SIP REGISTER request for migration service authorization
When the MCPTT client performs SIP registration for migration service authorization, the MCPTT client shall perform the registration procedures as specified in 3GPP TS 24.229 [4].
The MCPTT client shall include the following media feature tags in the Contact header field of the SIP REGISTER request:
1) the g.3gpp.mcptt media feature tag; and
2) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt".
If the MCPTT client, upon performing SIP registration:
1) has successfully finished the user authentication procedure as described in 3GPP TS 24.482 [49];
2) has available an access token from the partner IdM server;
4) confidentiality protection is disabled as specified in clause 6.6.2.3.1; and
5) integrity protection is disabled as specified in clause 6.6.3.3.1;
then the MCPTT client shall include in the SIP REGISTER request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in annex F.1 with:
1) the <mcptt-access-token> element set to the value of the access token received from the partner IdM server;
NOTE: The access token contains the MCPTT ID of the user in the partner MCPTT system.
2) the <mcptt-request-uri> element set to the value of the MCPTT ID of the user in the primary MCPTT system; and
3) the <selected-user-profile-index> element set to the value contained in the "user-profile-index" attribute of the MCPTT user profile selected according to clause 4.2.2.1.2.3 of 3GPP TS 24.484 [50].
If the MCPTT client, upon performing SIP registration:
1) has successfully finished the user authentication procedure as described in 3GPP TS 24.482 [49];
2) has an available access token; and
3) either confidentiality protection is enabled as specified in clause 6.6.2.3.1 or integrity protection is enabled as specified in clause 6.6.3.3.1;
then the MCPTT client:
1) shall include an application/mikey MIME body with the CSK as MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [78] in the body of the SIP REGISTER request;
2) if confidentiality protection is enabled as specified in clause 6.6.2.3.1, shall include in the body of the SIP REGISTER request, an application/vnd.3gpp.mcptt-info+xml MIME body with the following clarifications:
a) shall encrypt the received access-token using the client server key (CSK) and include the <mcptt-access-token> element set to the encrypted access-token, as specified in clause 6.6.2.3.3;
b) shall encrypt the MCPTT ID of the user in the primary MCPTT system and include the <mcptt-request-uri> element set to the encrypted MCPTT ID; and
c) shall encrypt the value contained in the "user-profile-index" attribute of the MCPTT user profile selected according to clause 4.2.2.1.2.3 of 3GPP TS 24.484 [50] and include the <selected-user-profile-index> element set to the encrypted value;
3) if confidentiality protection is disabled as specified in clause 6.6.2.3.1, shall include an application/vnd.3gpp.mcptt-info+xml MIME body as defined in Annex F.1 with:
a) the <mcptt-access-token> element set to the access token received from the partner IdM server;
b) the <mcptt-request-uri> element set to the MCPTT ID of the user in the primary MCPTT system; and
c) the <selected-user-profile-index> element set to the value contained in the "user-profile-index" attribute of the MCPTT user profile selected according to clause 4.2.2.1.2.3 of 3GPP TS 24.484 [50]; and
4) if integrity protection is enabled as specified in clause 6.6.3.3.1, shall use the CSK to integrity protect the application/vnd.3gpp.mcptt-info+xml MIME body by following the procedures in clause 6.6.3.3.3.
7A.2.2 Receiving a CSK key download message
The MCPTT client server shall operate as specified in clause 7.2.5.
7A.2.3 Receiving a SIP MESSAGE for migration service deauthorization notification
When the MCPTT client receives a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
1) the <req-type> element set to "migration-service-deauthorization-notification";
2) the <primary-mcptt-id> element set to the MCPTT ID of the user in the primary MCPTT system; and
3) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system;
the MCPTT client shall consider that the MCPTT client is deauthorized from migration service.
7A.3 Partner MCPTT server procedures
7A.3.1 General
In order to perform initial authorization to verify whether the MCPTT user is permitted to migrate to the partner MCPTT system, the partner MCPTT server obtains information from any received third-party SIP REGISTER request (e.g., including information contained in the body of the third-party SIP REGISTER request) as specified in 3GPP TS 24.229 [4]. The body will carry the SIP REGISTER request as sent by the MCPTT client and may contain information needed for initial authorization.
7A.3.2 Confidentiality and integrity protection
When the partner MCPTT server receives a SIP REGISTER request sent from the MCPTT client contained within a message/sip MIME body of a received third-party SIP REGISTER request, it first determines whether XML MIME bodies included in the request are integrity protected. If XML MIME bodies are integrity protected the MCPTT server validates the signature of each of the XML MIME bodies. If the integrity protection check(s) pass or the XML MIME bodies are not integrity protected, the partner MCPTT server then determines whether the content in specific XML elements is confidentiality protected. If XML content is confidentiality protected, the partner MCPTT server decrypts the protected content.
Upon receiving a SIP REGISTER request containing an application/vnd.3gpp.mcptt-info+xml MIME body within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client, the MCPTT server:
1) shall determine if integrity protection has been applied to XML MIME bodies in the SIP request by following the procedures in clause 6.6.3.4.1 for each XML MIME body;
2) if integrity protection has been applied, shall use the keying data described in clause 6.6.3.2 and the procedures described in clause 6.6.3.4.2 to verify the integrity of each of the XML MIME bodies; and
3) if all integrity protection checks succeed, shall continue with the remaining steps of this clause.
Upon receiving a SIP REGISTER request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-access-token> element, an <mcptt-request-uri> element, and a <selected-user-profile-index> element within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client, the MCPTT server:
1) shall determine if confidentiality protection has been applied to the <mcptt-access-token> element, the <mcptt-request-uri> element, and the <selected-user-profile-index> element in the application/vnd.3gpp.mcptt-info+xml MIME body, by following the procedures in clause 6.6.2.4.1;
2) if confidentiality protection has been applied to the <mcptt-access-token> element, the <mcptt-request-uri> element, and the <selected-user-profile-index> element:
a) shall use the keying information received in the MIKEY-SAKKE I_MESSAGE as specified in 3GPP TS 33.180 [78], along with the procedures described in clause 6.6.2.4.2 to:
i) decrypt the received access token in the <mcptt-access-token> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
ii) decrypt the received MCPTT ID of the user in the primary MCPTT system in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body; and
iii) decrypt the received selected user profile index in the <selected-user-profile-index> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if the decryption procedure succeeds, shall identify:
i) the MCPTT ID of the user in the partner MCPTT system from the decrypted access token;
ii) the MCPTT ID of the user in the primary MCPTT system from the decrypted MCPTT ID of the user in the primary MCPTT system; and
iii) the selected user profile index from the decrypted selected user profile index; and
c) if the decryption procedure fails, shall determine that confidentiality protection has not been successful;
3) if confidentiality protection has been applied to only one or two of the <mcptt-access-token> element, the <mcptt-request-uri> element, and the <selected-user-profile-index> element:
a) shall determine that confidentiality protection has not been successful; and
4) if confidentiality protection has not been applied:
a) shall identify the MCPTT ID of the user in the partner MCPTT system from <mcptt-access-token> element received in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall identify the MCPTT ID of the user in the primary MCPTT system from the <mcptt-request-uri> element received in the application/vnd.3gpp.mcptt-info+xml MIME body; and
c) shall identify the selected user profile index from the <selected-user-profile-index> element received in the application/vnd.3gpp.mcptt-info+xml MIME body.
7A.3.3 SIP REGISTER request for initial authorization
The partner MCPTT server shall support obtaining migration service authorization specific information from the SIP REGISTER request sent from the MCPTT client and included in the body of a third-party SIP REGISTER request.
NOTE 1: 3GPP TS 24.229 [4] defines how based on initial filter criteria the SIP REGISTER request sent from the UE is included in the body of the third-party SIP REGISTER request.
Upon receiving a third party SIP REGISTER request with a message/sip MIME body containing the SIP REGISTER request sent from the MCPTT client containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-access-token> element, an <mcptt-request-uri> element, and a <selected-user-profile-index> within a message/sip MIME body of the SIP REGISTER request sent from the MCPTT client, the MCPTT server:
1) shall perform initial authorization to verify whether the MCPTT user is permitted to migrate to the partner MCPTT system; and
NOTE 2: The criteria for the initial authorization is outside the scope of the present document.
2) if the initial authorization was successful:
a) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user in the primary MCPTT system;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
0) the <req-type> element set to "migration-service-authorization-request";
i) the <mcptt-request-uri> element set to the MCPTT ID of the user in the primary MCPTT system identified in clause 7A.3.2;
ii) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system identified in clause 7A.3.2; and
iii) the <selected-user-profile-index> element set to the selected user profile index identified in clause 7A.3.2; and
d) shall send the SIP MESSAGE request towards the partner MCPTT gateway according to the rules and procedures of 3GPP TS 24.229 [4].
7A.3.4 Sending a CSK key download message
The partner MCPTT server shall operate as specified in clause 7.3.7.
7A.3.5 SIP MESSAGE request for migration service authorization response
The partner MCPTT server shall support obtaining migration service authorization specific information from a SIP MESSAGE request sent from the partner MCPTT gateway server containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
0) the <resp-type> element set to "migration-service-authorization-response";
1) the <mcptt-request-uri> element set to the MCPTT ID of the user in the primary MCPTT system;
2) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system; and
3) the <migration-auth-result> element.
Upon receiving a SIP MESSAGE request from the partner MCPTT gateway server, if the <migration-auth-result> is set to "true", the partner MCPTT server shall:
1) store the mapping between the MCPTT IDs of the user in the primary MCPTT system and the partner MCPTT system; and
2) generate and send a SIP 200 OK response to the MCPTT client according to 3GPP TS 24.229 [4].
7A.3.6 Sending SIP MESSAGE for MCPTT service authorization notification
To update the primary MCPTT system of the MCPTT user about the successful completion of MCPTT user service authorization at the partner MCPTT system as described in clause 7.3.2 and clause 7.3.3, after migrating to the partner MCPTT system, the participating MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) set the Request-URI in the SIP MESSAGE request to the public service identity identifying the participating MCPTT function serving the MCPTT user in the primary MCPTT system;
NOTE 1: If the participating MCPTT function is in a primary 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 primary MCPTT system from the partner MCPTT system.
NOTE 2: If the participating MCPTT function is in a primary MCPTT system in a different trust domain, then the partner MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the partner MCPTT system to the primary MCPTT system.
NOTE 3: How the participating MCPTT function determines the public service identity of the participating MCPTT function serving the MCPTT user in the primary MCPTT system or of the MCPTT gateway server in the primary MCPTT system is out of the scope of the present document.
NOTE 4: How the partner MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <req-type> element set to a value of "mc-service-authorisation-notify-request";
b) the <primary-mcptt-id> element set to the MCPTT ID of the user in the primary MCPTT system;
c) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system; and
d) the <mc-service-auth-result> element set to "true"; and
4) send the SIP MESSAGE request towards the primary MCPTT gateway according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
7A.3.7 SIP MESSAGE request for migration service deauthorization notification
The partner MCPTT server shall support obtaining migration service deauthorization specific information from a SIP MESSAGE request sent from the partner MCPTT gateway server containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
1) the <req-type> element set to "migration-service-deauthorization-notification";
2) the <primary-mcptt-id> element set to the MCPTT ID of the user in the primary MCPTT system; and
3) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system.
Upon receiving the SIP MESSAGE request from the partner MCPTT gateway server, the partner MCPTT server shall:
1) delete the mapping between the MCPTT IDs of the user in the primary MCPTT system and the partner MCPTT system; and
NOTE: The MCPTT server does not have to delete mapping immediately after the MCPTT server received the SIP MESSAGE request. The period of how long the mapping is maintained is left for implementation.
2) send the SIP MESSAGE to the MCPTT client according to 3GPP TS 24.229 [4].
7A.4 Partner MCPTT gateway server procedures
7A.4.1 SIP MESSAGE from the partner MCPTT server
The partner MCPTT gateway server shall operate as specified in clause 6.8.2.
7A.4.2 SIP MESSAGE request from the primary MCPTT gateway server
The partner MCPTT gateway server shall operate as specified in clause 6.8.3.
7A.5 Primary MCPTT gateway server procedures
7A.5.1 SIP MESSAGE from the partner MCPTT gateway
The primary MCPTT gateway server shall operate as specified in clause 6.8.3.
7A.5.2 SIP MESSAGE request from the primary MCPTT server
The partner MCPTT gateway server shall operate as specified in clause 6.8.2.
7A.6 Primary MCPTT server procedures
7A.6.1 SIP MESSAGE request for migration service authorization request
The primary MCPTT server shall support obtaining migration service authorization specific information from a SIP MESSAGE request sent from the primary MCPTT gateway server containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
- the <req-type> element set to "migration-service-authorization-request";
- the <mcptt-request-uri> element set to the MCPTT ID of the user in the primary MCPTT system;
- the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system; and
- the <selected-user-profile-index> element set to the selected user profile index.
Upon receiving a SIP MESSAGE request from the primary MCPTT gateway server, the primary MCPTT server shall:
1) perform an authorization check to verify whether the user identified by the <mcptt-request-uri> element is permitted to migrate to the partner MCPTT system whose identity can be derived using the <partner-mcptt-id> element, the <selected-user-profile-index> element, and the MCPTT user profile configuration document for the user; and
2) if the migration is permitted:
a) mark the user identified by the <mcptt-request-uri> element as having migrated;
b) store the partner MCPTT system ID derived according to bullet 1) above;
c) store the mapping between the MCPTT IDs of the user in the primary MCPTT system and the partner MCPTT system;
d) generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
e) set the Request-URI in the SIP MESSAGE request to the public service identity identifying the participating MCPTT function serving the MCPTT user in the partner MCPTT system;
f) include, in the SIP MESSAGE request, an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
0) the <resp-type> element set to "migration-service-authorization-response";
i) the <mcptt-request-uri> element set to the MCPTT ID of the user in the primary MCPTT system;
ii) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system; and
iii) the <migration-auth-result> element set to "true"; and
g) send the SIP MESSAGE request towards the primary MCPTT gateway according to the rules and procedures of 3GPP TS 24.229 [4].
7A.6.2 Receiving SIP MESSAGE for MCPTT service authorization notification
Upon receipt of a "SIP MESSAGE request to notify about MCPTT service authorisation result for terminating participating MCPTT function in primary MCPTT system", the participating MCPTT function:
1) shall identify the stored information using primary-mcptt-id> and <partner-mcptt-id> elements included in an application/vnd.3gpp.mcptt-info+xml MIME body and update the determined stored information with MCPTT user’s MC service authorisation at partner MCPTT system;
2) shall use the stored necessary information for proper MCPTT call redirection;
3) shall generate and send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4]; and
4) shall execute the procedures as defined in the clause 7A.6.2 for sending the migration service deauthorization notification.
7A.6.2 SIP MESSAGE request for migration service deauthorization notification
If an MCPTT client that has been authorized for migration service in the partner MCPTT system is to be deauthorized because the MCPTT client completes the MCPTT service authorization in the primary MCPTT system or a different partner MCPTT system, the primary MCPTT server shall:
1) generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) set the Request-URI in the SIP MESSAGE request to the public service identity identifying the participating MCPTT function serving the MCPTT user in the partner MCPTT system;
3) include, in the SIP MESSAGE request, an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing:
a) the <req-type> element set to "migration-service-deauthorization-notification";
b) the <primary-mcptt-id> element set to the MCPTT ID of the user in the primary MCPTT system; and
c) the <partner-mcptt-id> element set to the MCPTT ID of the user in the partner MCPTT system; and
4) send the SIP MESSAGE request towards the primary MCPTT gateway according to the rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8 Pre-established session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.1 General | The MCPTT client may establish one or more pre-established sessions to the participating MCPTT function at any time after SIP registration and setting the service settings as defined in clause 7.2.2 or clause 7.2.3.
The MCPTT client may use the pre-established session for originating MCPTT calls after pre-established session establishment.
The participating MCPTT function may use the pre-established session for terminating MCPTT calls after pre-established session establishment.
The MCPTT client may initiate the modification of the media parameters of a pre-established session as defined in clause 8.3.1.1.
The participating MCPTT function may initiate the modification of the media parameters of a pre-established session as defined in clause 8.3.2.2.
The MCPTT client may initiate the release of a pre-established session as defined in clause 8.4.1.1.
The participating MCPTT function may initiate the release of a pre-established session as defined in clause 8.4.2.2.
The use of a pre-established session requires the use of resource sharing as specified in 3GPP TS 29.214 [79] and 3GPP TS 24.229 [4] by the participating MCPTT function. The participating MCPTT function use of resource sharing is defined in clause 8.1A.
8.1A Participating MCPTT function use of resource sharing
The participating MCPTT function utilises resource sharing either:
1) via the SIP core as specified in 3GPP TS 24.229 [4]; or
2) by directly interfacing to PCC to control resource sharing via the Rx reference point as specified in 3GPP TS 29.214 [79].
If resource sharing is supported then the participating MCPTT function shall allow the use of pre-established sessions by the MCPTT client.
The participating MCPTT function can determine that the SIP core supports resource sharing from the received third-party SIP REGISTER request if the Resource-Share header field with the value "supported" is contained in the "message/sip" MIME body of the third-party SIP REGISTER request as specified in 3GPP TS 24.229 [4].
When using resource sharing the participating MCPTT function uses the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request to identify the MCPTT UE that is registering and to identify whether resource sharing and pre-established sessions can be used with a specific MCPTT UE. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.2 Session establishment | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.2.1 MCPTT client procedures | When the MCPTT client initiates a pre-established session the MCPTT client shall:
1) gather ICE candidates according to IETF RFC 8445 [89]; and
NOTE 1: ICE candidates are only gathered on interfaces that the MCPTT UE uses to obtain MCPTT service.
2) 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) shall set the Request-URI of the SIP INVITE request to the public service identity of the participating MCPTT function serving the MCPTT user;
2) 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];
3) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16];
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" 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 media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall include the "timer" option tag in the Supported header field;
8) should include the Session-Expires header field according to IETF RFC 4028 [7] and should not include the "refresher" header field. The "refresher" header field parameter shall be set to "uac" if included;
9) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1, and include ICE candidates in the SDP offer as per IETF RFC 8839 [90]; and
10) shall send the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response to the SIP INVITE request the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
NOTE 2: If ICE candidate evaluation results in candidate pairs other than the default candidate pair being selected a further offer answer exchange using the procedures in clause 8.3 will be needed. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.2.2 Participating MCPTT function procedures | Upon receipt of a "SIP INVITE request for establishing a pre-established session" the participating MCPTT function:
1) shall check whether the public service identity is allocated and perform the actions specified in clause 6.3.7.1 if it is not allocated. Otherwise, continue with the rest of the steps;
2) shall determine the MCPTT ID of the MCPTT user establishing the pre-established session and perform actions to verify the MCPTT ID of the MCPTT client and authorise the request according to local policy, and if not authorised, the participating MCPTT function shall return a SIP 403 (Forbidden) response with the warning text set to "100 function not allowed due to <detailed reason>" as specified in clause 4.4. Otherwise, continue with the rest of the steps;
3) shall determine whether resource sharing is supported (see clause 8.1A);
4) if resource sharing is supported by the SIP core, determine that there is a binding between the MCPTT ID of the MCPTT user establishing the pre-established session and the MCPTT UE identified by the "+g.3gpp.registration-token" header field parameter in the Contact header field of the third-party REGISTER request (see clause 8.1A) and that this UE identity matches the identity in the "+g.3gpp.registration-token" header field parameter in the Feature-Caps header field in the "SIP INVITE request for establishing a pre-established session";
5) if resource sharing is not supported or if there is no binding between the MCPTT ID of the MCPTT user and the identity of the MCPTT UE identified by the "+g.3gpp.registration-token" header field parameter in the Feature-Caps header field, then the participating MCPTT function shall return a SIP 403 (Forbidden) response with the warning text set to "100 function not allowed due to pre-established session not supported" as specified in clause 4.4 and not continue with the rest of the steps;
6) shall validate the media parameters and if the MCPTT speech codec is not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
7) shall verify that the media resources are available to support the media parameters and if not shall reject the request with a SIP 500 (Server Internal Error) response, and shall not continue with the rest of the steps;
8) shall allocate a URI to be used to identify the pre-established session;
9) shall generate a SIP 200 (OK) response to the SIP INVITE request according to clause 6.3.2.1.5.2; and
a) shall include a Contact header field containing the URI that identifies the pre-established session;
b) shall include the public service identity of the participating MCPTT function in the P-Asserted-Identity header field;
c) shall include a Supported header field containing the "norefersub" option tag;
d) shall if the SIP core supports resource sharing, include a Resource-Share header field answer as specified in 3GPP TS 24.229 [4] with:
A) the value "media-sharing";
B) an "origin" header field parameter set to "session-initiator";
C) a "timestamp" header field parameter; and
D) a "rules" header field parameter with one resource sharing rule per media stream in the same order the corresponding m-line appears in the SDP. Each resource sharing rule is constructed as follows:
- a "new-sharing-key" part; and
- a "directionality" part indicating the direction of the pre-established media stream; and
e) shall include an SDP answer as specified in 3GPP TS 24.229 [4] with the clarifications in clause 6.3.2.1.2.2 and include ICE candidates in the SDP answer as per IETF RFC 8839 [90];
10) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
NOTE 1: Resulting media plane processing is completed before the next step is performed.
11) shall send the SIP 200 (OK) response towards the MCPTT client according to the rules and procedures of the 3GPP TS 24.229 [4]; and
12) shall evaluate the ICE candidates according to IETF RFC 8445 [89].
NOTE 2: If ICE candidate evaluation results in candidate pairs other than the default candidate pair being selected a further offer answer exchange using the procedures in clause 8.3 will be needed. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3 Session modification | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.1 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.1.1 MCPTT client initiated | When the MCPTT client needs to modify the pre-established session outside of an MCPTT call, the MCPTT client:
1) shall generate a SIP UPDATE request or a SIP re-INVITE request according to 3GPP TS 24.229 [4];
2) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1, and include ICE candidates in the SDP offer as per IETF RFC 8839 [90], if required; and
3) shall send the SIP request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of the SIP 200 (OK) response the MCPTT client:
1) shall interact with media plane as specified in 3GPP TS 24.380 [5], if there is change in media parameters or codecs in the received SDP answer, compared to those in the previously agreed SDP; and
2) shall interact with media plane as specified in 3GPP TS 24.380 [5], if there is a media stream, that is currently used in the pre-established session, marked as rejected in the received SDP answer.
NOTE: The MCPTT client keeps resources for previously agreed media stream, media parameters and codecs until it receives a SIP 200 (OK) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.1.2 Participating MCPTT function initiated | Upon receiving a SIP UPDATE request or a SIP re-INVITE request to modify an existing pre-established session without an associated MCPTT call, the MCPTT client:
1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec is acceptable by the MCPTT client and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; and
2) shall generate a SIP 200 (OK) response as follows:
a) shall include an SDP answer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.2, and include ICE candidates in the SDP answer as per IETF RFC 8839 [90], if required. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.2 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.2.1 MCPTT client initiated | Upon receiving a SIP UPDATE request or a SIP re-INVITE request to modify an existing pre-established session without associated MCPTT call, the participating MCPTT function:
1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec is acceptable by the participating MCPTT function and if not reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps; and
2) shall generate a SIP 200 (OK) response as follows:
a) include an SDP answer according to 3GPP TS 24.229 [4] based on the received SDP offer with the clarifications given in the 6.3.2.1.2.2, and include ICE candidates in the SDP answer as per IETF RFC 8839 [90], if required; and
b) include a Contact header field containing the URI that identifies the pre-established session and send a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.3.2.2 Participating MCPTT function initiated | When the participating MCPTT function needs to modify the pre-established session outside of an MCPTT call, the participating MCPTT function:
1) shall generate a SIP UPDATE request or a SIP re-INVITE request according to 3GPP TS 24.229 [4];
2) shall include an SDP offer according to 3GPP TS 24.229 [4], and include ICE candidates in the SDP offer as per IETF RFC 8839 [90], if required;
3) shall interact with the media plane as specified in 3GPP TS 24.380 [5], if removing a media-floor control entity; and
4) shall send the SIP request towards the MCPTT client according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of the SIP 200 (OK) response, the participating MCPTT function:
1) shall interact with media plane as specified in 3GPP TS 24.380 [5], if there is change in media parameters or codecs in the received SDP answer, compared to those in the previously agreed SDP;
2) shall interact with media plane as specified in 3GPP TS 24.380 [5], if there is a media stream, that is currently used in the pre-established session, marked as rejected in the received SDP answer; and
3) shall interact with media plane as specified in 3GPP TS 24.380 [5], if there is a media stream accepted in the received SDP answer, that is not currently used by the participant in the pre-established session.
NOTE: The participating MCPTT function keeps resources for previously agreed media stream, media-floor control entities, media parameters and codecs until it receives a SIP 200 (OK) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4 Session release | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.1 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.1.1 MCPTT client initiated | NOTE: The MCPTT client needs to be prepared to release the pre-established session when receiving a SIP BYE request generated by the SIP core (e.g. due to network release of media plane resources).
When a MCPTT client needs to release a pre-established session as created in clause 8.2.1, the MCPTT client:
1) shall generate a SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP BYE request to the URI that identifies the pre-established session;
3) shall send the SIP BYE request towards the participating MCPTT function within the SIP dialog of the pre-established session according to rules and procedures of the 3GPP TS 24.229 [4]; and
4) shall, upon receiving a SIP 200 (OK) response to the SIP BYE request interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.1.2 Participating MCPTT function initiated | Upon receiving a SIP BYE request from the participating MCPTT function within a pre-established session the MCPTT client shall check whether there are any MCPTT calls using the pre-established session, and:
1) if there is an established MCPTT call then the MCPTT client shall remove the MCPTT client from the MCPTT call by performing the procedures for session release for each MCPTT session as specified in 3GPP TS 24.380 [5]; and
2) if there is no MCPTT call using the pre-established session, then the MCPTT client shall:
a) interact with the media plane as specified in 3GPP TS 24.380 [5] for disconnecting the media plane resources towards the participating MCPTT function; and
b) shall generate and send a SIP 200 (OK) response to the SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.2 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.2.1 MCPTT client initiated | Upon receiving a SIP BYE request from the MCPTT client within a pre-established session the participating MCPTT function:
1) shall check whether there is a MCPTT call using the pre-established session, and:
a) if there is an established MCPTT session then the participating MCPTT function shall remove the MCPTT client from the MCPTT session by performing the procedures as specified in clause 6.3.2.1.6; and
b) if there is a MCPTT session in the process of being established, then the participating MCPTT function:
i) shall send a SIP CANCEL request to cancel the MCPTT session in the process of being established as specified in 3GPP TS 24.229 [4]; and
ii) shall release the MCPTT session as specified in the clause clause 6.3.2.1.6, if a SIP 200 (OK) response for the SIP INVITE request is received from the remote side; and
c) if there is no MCPTT call using the pre-established session, then the participating MCPTT function shall:
i)_ interact with the media plane as specified in 3GPP TS 24.380 [5] for disconnecting the media plane resources towards the MCPTT client; and
ii) shall generate and send a SIP 200 (OK) response to the SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request from the remote side, the participating MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for releasing media plane resources towards the remote side;
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for releasing media plane resources towards the MCPTT client; and
3) shall send a SIP 200 (OK) response to the SIP BYE request to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 8.4.2.2 Participating MCPTT function initiated | When a participating MCPTT function needs to release a pre-established session as created in clause 8.2.2, the participating MCPTT function:
1) shall first release any participants of all MCPTT calls that are using the pre-established session using the procedures as follows. The participating MCPTT function:
a) shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5];
b) shall generate a SIP BYE request as specified in 3GPP TS 24.229 [4];
c) shall set the Request-URI to the MCPTT session identity;
d) shall include a P-Asserted-Identity header field in the outgoing SIP BYE request set to the public service identity of the participating MCPTT function;
e) shall send the SIP BYE request toward the controlling MCPTT function, according to 3GPP TS 24.229 [4]; and
f) shall, upon receiving a SIP 200 (OK) response to the SIP BYE request the terminating MCPTT function shall interact with the media plane as specified in clause 6.4 in 3GPP TS 24.380 [5];
2) shall generate a SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4];
3) shall set the Request-URI of the SIP BYE request to the URI that identifies the pre-established session;
4) shall send the SIP BYE request towards the MCPTT client within the SIP dialog of the pre-established session according to rules and procedures of the 3GPP TS 24.229 [4]; and
5) shall, upon receiving a SIP 200 (OK) response to the SIP BYE request interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9 Affiliation | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.1 General | Clause 9.2 contains the procedures for explicit affiliation at the MCPTT client, the MCPTT server serving the MCPTT user and the MCPTT server owning the MCPTT group.
Clause 9.2 contains the procedures for implicit affiliation at the MCPTT server serving the MCPTT user and the MCPTT server owning the MCPTT group.
Clause 9.3 describes the coding used for explicit affiliation.
The procedures for implicit affiliation in this clause are triggered at the MCPTT server serving the MCPTT user in the following circumstances:
- on receipt of a SIP INVITE request or a SIP REFER request from an MCPTT client to join an MCPTT chat group, where the MCPTT client is not already affiliated to the MCPTT group;
- on receipt of a SIP INVITE request or a SIP REFER request from an MCPTT client when attempting to initiate an MCPTT emergency group call or MCPTT imminent peril group call and the MCPTT client is not already affiliated to the MCPTT group;
- on receipt of a SIP MESSAGE request from an MCPTT client when initiating an MCPTT emergency alert targeted to an MCPTT group and the MCPTT client is not already affiliated to the MCPTT group; and
- on receipt of a SIP REGISTER request for service authorisation (as described in clause 7.3.2) or SIP PUBLISH request for service authorisation and service settings (as described in clause 7.3. 3), as determined by configuration in the MCPTT user profile document as specified in 3GPP TS 24.484 [50].
The procedures for implicit affiliation in this clause are triggered at the MCPTT server owning the MCPTT group in the following circumstances:
- on receipt of a SIP INVITE request from the MCPTT server serving the MCPTT user where an MCPTT user wants to join an MCPTT chat group and the MCPTT client is not already affiliated to the MCPTT group;
- on receipt of a SIP INVITE request from the MCPTT server serving the MCPTT user where an MCPTT user initiates an MCPTT emergency group call or MCPTT imminent peril group call and the MCPTT client is not already affiliated to the MCPTT group; and
- on receipt of a SIP MESSAGE request from the MCPTT server serving the MCPTT user when the MCPTT user initiates an MCPTT emergency alert targeted to an MCPTT group and the MCPTT client is not already affiliated to the MCPTT group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2 Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.1 General | The MCPTT client procedures consist of:
- an affiliation status change procedure;
- an affiliation status determination procedure;
- a procedure for sending affiliation status change request in negotiated mode to target MCPTT user;
- a procedure for receiving affiliation status change request in negotiated mode from authorized MCPTT user; and
- a rules based affiliation status change procedure.
In order to obtain information about success or rejection of changes triggered by the affiliation status change procedure for an MCPTT user, the MCPTT client needs to initiate the affiliation status determination procedure for the MCPTT user before starting the affiliation status change procedure for the MCPTT user. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.2 Affiliation status change procedure | In order:
- to indicate that an MCPTT user is interested in one or more MCPTT group(s) at an MCPTT client;
- to indicate that the MCPTT user is no longer interested in one or more MCPTT group(s) at the MCPTT client;
- to indicate that the MCPTT user continues to have interest in one or more MCPTT group(s) at an MCPTT client due to near expiration of the expiration time of an MCPTT group with the affiliation status set to the "affiliated" state received in a SIP NOTIFY request in clause 9.2.1.3;
- to send an affiliation status change request in mandatory mode to another MCPTT user;
- to indicate that an MCPTT user is interested in one or more MCPTT group(s) at an MCPTT client triggered by a location or functional alias activation criteria;
- to indicate that the MCPTT user is no longer interested in one or more MCPTT group(s) at the MCPTT client client triggered by location or functional alias deactivation criteria; or
- any combination of the above;
the MCPTT client shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37], and IETF RFC 3856 [51].
When the MCPTT user indicates that he is no longer interested in one or more MCPTT group(s) at the MCPTT client, the MCPTT client shall first check the <manual-deaffiliation-not-allowed-if-affiliation-rules-are-met> element within the <anyExt> element of the <entry> element corresponding to the group information within the <GroupList> list element of the <anyExt> element of the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]). If the affiliation to the group has been activated due to a rule being fulfilled and the <manual-deaffiliation-not-allowed-if-affiliation-rules-are-met> element is set to a value of "true", the MCPTT client shall suppress the MCPTT user's request.
NOTE 1: If the request is suppressed, a notification message can be displayed to the user
In the SIP PUBLISH request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the MCPTT user;
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) if the targeted MCPTT user is interested in at least one MCPTT group at the targeted MCPTT client, shall set the Expires header field according to IETF RFC 3903 [37], 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].
5) if the targeted MCPTT user is no longer interested in any MCPTT group at the targeted MCPTT client, shall set the Expires header field according to IETF RFC 3903 [37], to zero; and
6) shall include an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1. In the MIME body, the MCPTT client:
a) shall include all MCPTT groups where the targeted MCPTT user indicates its interest at the targeted MCPTT client;
b) shall include the MCPTT client ID of the targeted MCPTT client;
c) shall not include the "status" attribute and the "expires" attribute in the <affiliation> element; and
d) shall set the <p-id> child element of the <presence> root element to a globally unique value.
NOTE: This procedure deviates from IETF RFC 3903 [37] by possibly including an application/pidf+xml MIME body when refreshing the expiration time for one or more groups. The use of this MIME body provides the ability to refresh affiliation or to deaffiliate multiple groups in a single message.
The MCPTT client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.3 Affiliation status determination procedure | NOTE 1: The MCPTT UE also uses this procedure to determine which MCPTT groups the MCPTT user successfully affiliated to.
In order to discover MCPTT groups:
1) which the MCPTT user at an MCPTT client is affiliated to; or
2) which another MCPTT user is affiliated to;
the MCPTT client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the targeted MCPTT user;
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) 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 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) 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; and
6) shall include an Accept header field containing the application/pidf+xml MIME type; and
7) if requesting MCPTT groups where the MCPTT user is affiliated to at the MCPTT client, shall include an application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information according to clause 9.3.2, indicating the MCPTT client ID of the MCPTT client.
In order to re-subscribe or de-subscribe, the MCPTT client shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT client:
1) 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 3: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
2) if the MCPTT client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero; and
3) shall include an Accept header field containing the application/pidf+xml MIME type.
Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-user affiliation information constructed according to clause 9.3.1, then the MCPTT client shall determine affiliation status of the MCPTT user for each MCPTT group at the MCPTT client(s) in the MIME body. If the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request is included, the <p-id> element value indicates the SIP PUBLISH request which triggered sending of the SIP NOTIFY request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.4 Procedure for sending affiliation status change request in negotiated mode to target MCPTT user | NOTE: Procedure for sending affiliation status change request in negotiated mode to several target MCPTT users is not supported in this version of the specification.
Upon receiving a request from the MCPTT user to send an affiliation status change request in negotiated mode to a target MCPTT user, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. In the SIP MESSAGE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the target MCPTT user;
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] in the SIP MESSAGE request;
4) shall include an application/vnd.3gpp.mcptt-affiliation-command+xml MIME body as specified in Annex F.4; and
5) 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 indicate to the user that the request has been delivered to an MCPTT client of the target MCPTT user. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.5 Procedure for receiving affiliation status change request in negotiated mode from authorized MCPTT user | Upon receiving a SIP MESSAGE request containing:
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]; and
2) an application/vnd.3gpp.mcptt-affiliation-command+xml MIME body with a list of MCPTT groups for affiliation under the <affiliate> element and a list of MCPTT groups for de-affiliation under the <de-affiliate> element;
then the MCPTT client:
1) shall send a 200 (OK) response to the SIP MESSAGE request;
2) shall seek confirmation of the list of MCPTT groups for affiliation and the list of MCPTT groups for de-affiliation, resulting in an accepted list of MCPTT groups for affiliation and an accepted list of MCPTT groups for de-affiliation; and
3) if the user accepts the request:
a) shall perform affiliation for each entry in the accepted list of MCPTT groups for affiliation for which the MCPTT client is not affiliated, as specified in clause 9.2.1.2; and
b) shall perform de-affiliation for each entry in the accepted list of MCPTT groups for de-affiliation for which the MCPTT client is affiliated, as specified in clause 9.2.1.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.6 Subscription to group dynamic data | In order to subscribe to changes in per-group dynamic data, the MCPTT client shall generate an initial SIP SUBSCRIBE request specified in 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT group ID of the targeted MCPTT group;
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 specified in IETF RFC 6050 [9];
4) if the MCPTT client wants to receive the current status and later notification, shall set the Expires header field specified in 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].
5) if the MCPTT client wants to fetch the current state only, shall set the Expires header field specified in IETF RFC 6665 [26], to zero;
6) shall include an Accept header field containing the application/pidf+xml MIME type; and
7) shall include an application/simple-filter+xml MIME body indicating per-group restrictions of presence event package notification information specified in clause 9.3.2, indicating the MCPTT group ID.
In order to re-subscribe or de-subscribe, the MCPTT client shall generate an in-dialog SIP SUBSCRIBE request specified in 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT client:
1) if the MCPTT client wants to receive the current status and later notification, shall set the Expires header field specified in 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].
2) if the MCPTT client wants to de-subscribe, shall set the Expires header field specified in IETF RFC 6665 [26], to zero; and
3) shall include an Accept header field containing the application/pidf+xml MIME type.
Upon receiving a SIP NOTIFY request specified in 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if the SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-group dynamic data information constructed according to clause 9.3.1, then the MCPTT client shall determine per-group dynamic data of the MCPTT group in the MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.7 Rules based affiliation status change procedure | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.7.1 General | The MCPTT client can based on configuration decide to affiliate or de-affiliate to a group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.7.2 User profile defined rules | User profile based affiliation rules are controlled by the elements <RulesForAffiliation> or <RulesForDeAffiliation> of the MCPTT user profile document identified by the MCPTT ID of the MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]). The rules can be composed of location criteria (including heading and speed) or functional alias based criteria. A rule is fulfilled if any of the location criteria and any of the functional alias based criteria are met. If, any defined rule is fulfilled, the MCPTT client shall initiate the affiliation status change procedure as specified in clause 9.2.1.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.1.7.3 Group configuration defined rules | If the <permitted-geographic-area> element of the <list-service> element of an MCS group document is present and the MCPTT client is within the area specified in the <permitted-geographic-area> element, the MCPTT client is allowed to affiliate to the group.
If the <mandatory-geographic-area> element of the <list-service> element of an MCS group document is present and the MCPTT client is not within the area specified in the <mandatory-geographic-area> element the MCPTT client shall de-affiliate from the group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2 MCPTT server procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.1 General | The MCPTT server procedures consist of:
- procedures of MCPTT server serving the MCPTT user; and
- procedures of MCPTT server owning the MCPTT group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2 Procedures of MCPTT server serving the MCPTT user | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.1 General | The procedures of MCPTT server serving the MCPTT user consist of:
- a receiving affiliation status change from MCPTT client procedure;
- a receiving subscription to affiliation status procedure;
- a sending notification of change of affiliation status procedure;
- a sending affiliation status change towards MCPTT server owning MCPTT group procedure;
- an affiliation status determination from MCPTT server owning MCPTT group procedure;
- a procedure for authorizing affiliation status change request in negotiated mode sent to served MCPTT user;
- a forwarding affiliation status change towards another MCPTT user procedure;
- a forwarding subscription to affiliation status towards another MCPTT user procedure
- an affiliation status determination procedure;
- an affiliation status change by implicit affiliation procedure;
- an implicit affiliation status change completion procedure;
- an implicit affiliation status change cancellation procedure;
- an implicit affiliation to configured groups procedure; and
- forwarding subscription to group dynamic data towards the controlling MCPTT server procedure. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.2 Stored information | The MCPTT server shall maintain a list of MCPTT user information entries. The list of the MCPTT user information entries contains one MCPTT user information entry for each served MCPTT ID.
In each MCPTT user information entry, the MCPTT server shall maintain:
1) an MCPTT ID. This field uniquely identifies the MCPTT user information entry in the list of the MCPTT user information entries; and
2) a list of MCPTT client information entries.
In each MCPTT client information entry, the MCPTT server shall maintain:
1) an MCPTT client ID. This field uniquely identifies the MCPTT client information entry in the list of the MCPTT client information entries; and
2) a list of MCPTT group information entries.
In each MCPTT group information, the MCPTT server shall maintain:
1) an MCPTT group ID. This field uniquely identifies the MCPTT group information entry in the list of the MCPTT group information entries;
2) an affiliation status;
3) an expiration time;
4) an affiliating p-id; and
5) a next publishing time. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.3 Receiving affiliation status change from MCPTT client procedure | Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID served by the MCPTT server;
3) 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) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1;
then the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
2) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request;
3) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
4) if the originating MCPTT ID is different than the served MCPTT ID and the originating MCPTT ID is not authorized to modify affiliation status of the served MCPTT ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps;
5) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
6) if the Expires header field of the SIP PUBLISH request has nonzero value, shall determine the candidate expiration interval to according to IETF RFC 3903 [37];
7) if the Expires header field of the SIP PUBLISH request has zero value, shall set the candidate expiration interval to zero;
8) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37]. In the SIP 200 (OK) response, the MCPTT server:
a) shall set the Expires header field according to IETF RFC 3903 [37], to the candidate expiration time;
9) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCPTT ID, shall not continue with the rest of the steps;
10) shall identify the served MCPTT client ID in the "id" attribute of the <tuple> element of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request;
11) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
12) shall consider an MCPTT client information entry such that:
a) the MCPTT client information entry is in the list of MCPTT client information entries of the served MCPTT user information entry; and
b) the MCPTT client ID of the MCPTT client information entry is equal to the served MCPTT client ID;
as the served MCPTT client information entry;
13) shall consider a copy of the list of the MCPTT group information entries of the served MCPTT client information entry as the served list of the MCPTT group information entries;
14) if the candidate expiration interval is nonzero:
a) shall construct the candidate list of the MCPTT group information entries as follows:
i) for each MCPTT group ID which has an MCPTT group information entry in the served list of the MCPTT group information entries, such that the expiration time of the MCPTT group information entry has not expired yet, and which is indicated in a "group" attribute of an <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
A) shall copy the MCPTT group information entry into a new MCPTT group information entry of the candidate list of the MCPTT group information entries;
B) if the affiliation status of the MCPTT group information entry is "deaffiliating" or "deaffiliated", shall set the affiliation status of the new MCPTT group information entry to the "affiliating" state and shall set the affiliating p-id of the new MCPTT group information entry to the value of the <p-id> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
C) shall set the expiration time of the new MCPTT group information entry to the current time increased with the candidate expiration interval;
ii) for each MCPTT group ID which has an MCPTT group information entry in the served list of the MCPTT group information entries, such that the expiration time of the MCPTT group information entry has not expired yet, and which is not indicated in any "group" attribute of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
A) shall copy the MCPTT group information entry into a new MCPTT group information entry of the candidate list of the MCPTT group information entries; and
B) if the affiliation status of the MCPTT group information entry is "affiliated" or "affiliating":
- shall set the affiliation status of the new MCPTT group information entry to the "de-affiliating" state; and
- shall set the expiration time of the new MCPTT group information entry to the current time increased with twice the value of timer F; and
iii) for each MCPTT group ID:
A) which does not have an MCPTT group information entry in the served list of the MCPTT group information entries; or
B) which has an MCPTT group information entry in the served list of the MCPTT group information entries, such that the expiration time of the MCPTT group information entry has already expired;
and which is indicated in a "group" attribute of the <affiliation> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
A) shall add a new MCPTT group information entry in the candidate list of the MCPTT group information list for the MCPTT group ID;
B) shall set the affiliation status of the new MCPTT group information entry to the "affiliating" state;
C) shall set the expiration time of the new MCPTT group information entry to the current time increased with the candidate expiration interval; and
D) shall set the affiliating p-id of the new MCPTT group information entry to the value of the <p-id> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request;
b) determine the candidate number of MCPTT group IDs as number of different MCPTT group IDs which have an MCPTT group information entry:
i) in the candidate list of the MCPTT group information entries; or
ii) in the list of the MCPTT group information entries of an MCPTT client information entry such that:
A) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry; and
B) the MCPTT client ID of the MCPTT client information entry is not equal to the served MCPTT client ID;
with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and
c) if the candidate number of MCPTT group IDs is bigger than N2 value of the served MCPTT ID (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile), shall based on MCPTT service provider policy reduce the candidate MCPTT group IDs to that equal to N2;
NOTE: The MCPTT service provider policy can determine to remove an MCPTT group ID based on the order it appeared in the PUBLISH request or based on the importance or priority of the MCPTT group or some other policy to determine which MCPTT groups are preferred.
15) if the candidate expiration interval is zero, constructs the candidate list of the MCPTT group information entries as follows:
a) for each MCPTT group ID which has an entry in the served list of the MCPTT group information entries:
i) shall copy the MCPTT group entry of the served list of the MCPTT group information into a new MCPTT group information entry of the candidate list of the MCPTT group information entries;
ii) shall set the affiliation status of the new MCPTT group information entry to the "de-affiliating" state; and
iii) shall set the expiration time of the new MCPTT group information entry to the current time increased with twice the value of timer F;
16) shall replace the list of the MCPTT group information entries stored in the served MCPTT client information entry with the candidate list of the MCPTT group information entries;
17) shall perform the procedures specified in clause 9.2.2.2.6 for the served MCPTT ID and each MCPTT group ID:
a) which does not have an MCPTT group information entry in the served list of the MCPTT group information entries and which has an MCPTT group information entry in the candidate list of the MCPTT group information entries with the affiliation status set to the "affiliating" state;
b) which has an MCPTT group information entry in the served list of the MCPTT group information entries with the expiration time already expired, and which has an MCPTT group information entry in the candidate list of the MCPTT group information entries with the affiliation status set to the "affiliating" state;
c) which has an MCPTT group information entry in the served list of the MCPTT group information entries with the affiliation status set to the "deaffiliating" state or the "deaffiliated" state and with the expiration time not expired yet, and which has an MCPTT group information entry in the candidate list of the MCPTT group information entries with the affiliation status set to the "affiliating" state; or
d) which has an MCPTT group information entry in the served list of the MCPTT group information entries with the affiliation status set to the "affiliated" state and with the expiration time not expired yet, and which has an MCPTT group information entry in the candidate list of the MCPTT group information entries with the affiliation status set to the "de-affiliating" state;
18) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
19) shall perform the procedures specified in clause 9.2.2.2.5 for the served MCPTT ID. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.4 Receiving subscription to affiliation status procedure | Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID served by the MCPTT server;
3) 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]; and
4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
4) if the originating MCPTT ID is different than the served MCPTT ID and the originating MCPTT ID is not authorized to modify affiliation status of the served MCPTT ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps; and
5) shall generate a 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify the subscriber about changes of the information of the served MCPTT ID, as described in clause 9.2.2.2.5. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.5 Sending notification of change of affiliation status procedure | In order to notify the subscriber about changes of the served MCPTT ID, the MCPTT server:
1) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
2) shall consider the list of the MCPTT client information entries of the served MCPTT user information entry as the served list of the MCPTT client information entries;
3) shall generate an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1 and the served list of the MCPTT client information entries with the following clarifications:
a) the MCPTT server shall not include information from an MCPTT group information entry with the expiration time already expired;
b) the MCPTT server shall not include information from an MCPTT group information entry with the affiliation status set to the "deaffiliated" state;
c) if the SIP SUBSCRIBE request creating the subscription of this notification contains an application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information according to clause 9.3.2, the MCPTT server shall restrict the application/pidf+xml MIME body according to the application/simple-filter+xml MIME body; and
d) if this procedures is invoked by procedure in clause 9.2.2.2.3 where the handled p-id value was identified, the MCPTT server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and
4) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9.2.2.2.4. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-user affiliation information. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.6 Sending affiliation status change towards MCPTT server owning MCPTT group procedure | NOTE 1: Usage of one SIP PUBLISH request to carry information about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order:
- to send an affiliation request of a served MCPTT ID to a handled MCPTT group ID;
- to send an de-affiliation request of a served MCPTT ID from a handled MCPTT group ID; or
- to send an affiliation request of a served MCPTT ID to a handled MCPTT group ID due to near expiration of the previously published information;
the MCPTT server shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51]. In the SIP PUBLISH request, the MCPTT server:
1) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled MCPTT group ID;
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 handled MCPTT group ID 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.
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
a) shall include the <mcptt-request-uri> element set to the handled MCPTT group ID; and
b) shall include the <mcptt-calling-user-id> element set to the served MCPTT ID;
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) if sending an affiliation request, shall set the Expires header field according to IETF RFC 3903 [37], to 4294967295;
NOTE 7: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) if sending an de-affiliation request, shall set the Expires header field according to IETF RFC 3903 [37], to zero;
6) shall include an P-Asserted-Identity header field set to the public service identity of the MCPTT server according to 3GPP TS 24.229 [4];
7) shall set the current p-id to a globally unique value;
8) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
9) for each MCPTT group information entry such that:
a) the MCPTT group information entry has the "affiliating" affiliation status, the MCPTT group ID set to the handled MCPTT group ID, the expiration time has not expired yet and the affiliating p-id is not set;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry; and
c) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry;
shall set the affiliating p-id of the MCPTT group information entry to the current p-id; and
10) shall include an application/pidf+xml MIME body indicating per-group affiliation information constructed according to clause 9.3.1.2. The MCPTT server shall indicate all served MCPTT client IDs, such that:
a) the affiliation status is set to "affiliating" or "affiliated", and the expiration time has not expired yet in an MCPTT group information entry with the MCPTT group ID set to the handled MCPTT group;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry;
c) the MCPTT client information entry has the MCPTT client ID set to the served MCPTT client ID; and
d) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry.
The MCPTT server shall set the <p-id> child element of the <presence> root element to the current p-id.
The MCPTT server shall not include the "expires" attribute in the <affiliation> element.
The MCPTT server shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
If timer F expires for the SIP PUBLISH request sent for a (de)affiliation request of served MCPTT ID to the MCPTT group ID or upon receiving a SIP 3xx, 4xx, 5xx or 6xx response to the SIP PUBLISH request, the MCPTT server:
1) shall remove each MCPTT group ID entry such that:
a) the MCPTT group information entry has the MCPTT group ID set to the handled MCPTT group ID;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry; and
c) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.7 Affiliation status determination from MCPTT server owning MCPTT group procedure | NOTE 1: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order to discover whether a served MCPTT user was successfully affiliated to a handled MCPTT group in the MCPTT server owning the handled MCPTT group, the MCPTT server shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT server:
1) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled MCPTT group ID;
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 handled MCPTT group ID 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.2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
a) shall include the <mcptt-request-uri> element set to the handled MCPTT group ID; and
b) shall include the <mcptt-calling-user-id> element set to the served MCPTT ID;
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) if the MCPTT server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 7: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) if the MCPTT server wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
6) shall include an Accept header field containing the application/pidf+xml MIME type; and
7) shall include an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to clause 9.3.2, indicating the served MCPTT ID.
In order to re-subscribe or de-subscribe, the MCPTT server shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT server:
1) if the MCPTT server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 8: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
2) if the MCPTT server wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero; and
3) shall include an Accept header field containing the application/pidf+xml MIME type.
Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to clause 9.3.1, then the MCPTT server:
1) for each served MCPTT ID and served MCPTT client ID such that the application/pidf+xml MIME body of SIP NOTIFY request contains:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID;
c) an <affiliation> child element of the <status> element of the <tuple> element;
d) the "client" attribute of the <affiliation> element indicating the served MCPTT client ID; and
d) the "expires" attribute of the <affiliation> element indicating expiration of affiliation;
perform the following:
a) if an MCPTT group information entry exists such that:
i) the MCPTT group information entry has the "affiliating" affiliation status, the MCPTT group ID set to the handled MCPTT group ID, and the expiration time has not expired yet;
ii) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry with the MCPTT client ID set to the served MCPTT client ID;
iii) the MCPTT client information entry is in the list of the MCPTT client information entries of a served MCPTT user information entry with the MCPTT ID set to the served MCPTT ID; and
iv) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
shall set the affiliation status of the MCPTT group information entry to "affiliated"; and
shall set the next publishing time of the MCPTT group information entry to the current time and half of the time between the current time and the expiration of affiliation; and
2) for each MCPTT group information entry such that:
a) the MCPTT group information entry has the "affiliated" affiliation status or the "deaffiliating" affiliation status, the MCPTT group ID set to the handled MCPTT group ID, and the expiration time has not expired yet;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry with the MCPTT client ID set to a served MCPTT client ID;
c) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry with the MCPTT ID set to a served MCPTT ID; and
d) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID;
c) an <affiliation> child element of the <status> child element of the <tuple> element; and
d) the "client" attribute of the <affiliation> element indicating the served MCPTT client ID.
perform the following:
a) shall set the affiliation status of the MCPTT group information entry to "deaffiliated"; and
b) shall set the expiration time of the MCPTT group information entry to the current time; and
3) if a <p-id> element is included in the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request, then for each MCPTT group information entry such that:
a) the MCPTT group information entry has the "affiliating" affiliation status, the MCPTT group ID set to the handled MCPTT group ID, the expiration time has not expired yet and with the affiliating p-id set to the value of the <p-id> element;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry with the MCPTT client ID set to a served MCPTT client ID;
c) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry with the MCPTT ID set to a served MCPTT ID; and
d) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID;
c) an <affiliation> child element of the <status> child element of the <tuple> element; and
d) the "client" attribute of the <affiliation> element indicating the served MCPTT client ID;
perform the following:
a) shall set the affiliation status of the MCPTT group information entry to "deaffiliated"; and
b) shall set the expiration time of the MCPTT group information entry to the current time. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.8 Procedure for authorizing affiliation status change request in negotiated mode sent to served MCPTT user | Upon receiving a SIP MESSAGE request such that:
1) Request-URI of the SIP MESSAGE request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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]; and
4) the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-affiliation-command+xml MIME body;
then the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request;
2) shall identify the originating MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request;
3) if the originating MCPTT ID is not authorized to send an affiliation status change request in negotiated mode to the served MCPTT ID, shall send a 403 (Forbidden) response and shall not continue with the rest of the steps;
4) shall set the Request-URI of the SIP MESSAGE request to the public user identity bound to the served MCPTT ID in the MCPTT server; and
5) 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];
before forwarding the SIP MESSAGE request further. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.9 Forwarding affiliation status change towards another MCPTT user procedure | Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID not served by the MCPTT server;
3) 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) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user affiliation information according to clause 9.3.1;
then the MCPTT server:
1) shall identify the target MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info MIME body of the SIP PUBLISH request;
2) shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request;
3) shall generate a SIP PUBLISH request from the received SIP PUBLISH request. In the generated SIP PUBLISH request, the MCPTT server:
a) shall set the Request-URI to the public service identity identifying the terminating participating MCPTT function serving the target MCPTT ID;
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 originating participating MCPTT function determines the public service identity of the terminating participating MCPTT function serving the target MCPTT ID 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.
b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
A) shall include the <mcptt-request-uri> element set to the target MCPTT ID; and
B) shall include the <mcptt-calling-user-id> element set to the originating MCPTT ID; and
d) shall include other signalling elements from the received SIP PUBLISH request; and
4) shall send the generated SIP PUBLISH request according to 3GPP TS 24.229 [4].
The MCPTT server shall forward received SIP responses to the SIP PUBLISH request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.10 Forwarding subscription to affiliation status towards another MCPTT user procedure | Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID not served by MCPTT server;
3) 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]; and
4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
then the MCPTT server:
1) shall identify the target MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info MIME body of the SIP SUBSCRIBE request;
2) shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCPTT server:
a) shall set the Request-URI to the public service identity identifying the terminating participating MCPTT function serving the target MCPTT ID;
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 originating participating MCPTT function determines the public service identity of the terminating participating MCPTT function serving the target MCPTT ID 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.
b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
A) shall include the <mcptt-request-uri> element set to the target MCPTT ID; and
B) shall include the <mcptt-calling-user-id> element set to the originating MCPTT ID; and
d) shall include other signalling elements from the received SIP SUBSCRIBE request; and
4) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [4].
The MCPTT server shall forward any received SIP responses to the SIP SUBSCRIBE request, any received SIP NOTIFY request and any received SIP responses to the SIP NOTIFY request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.11 Affiliation status determination | This clause is referenced from other procedures.
If the participating MCPTT function needs to determine the affiliation status of an MCPTT user to an MCPTT group, the participating function:
1) shall find the user information entry in the list of MCPTT user information entries described in clause 9.2.2.2.2 such that the MCPTT ID of the MCPTT user information entry is equal to the MCPTT ID of the originator of the received SIP request;
a) if the applicable MCPTT group information entry cannot be found, then the participating MCPTT function shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the skip the rest of the steps;
2) shall find the MCPTT client information entry in the list of MCPTT client information entries of MCPTT user information entry found in step 1) in which the MCPTT client id matches the value of the <mcptt-client-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP request;
a) if the applicable MCPTT client information entry cannot be found, then the participating MCPTT function shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the skip the rest of the steps;
3) shall find the MCPTT group information entry in the list of MCPTT group information entries of MCPTT client information entry found in step 2 such that the MCPTT group identity matches the value of the identity of the targeted MCPTT group;
a) if the applicable MCPTT group information entry was found in step 3) and the affiliation status of the MCPTT group information entry is "affiliating" or "affiliated", shall determine that the MCPTT user at the MCPTT client to be affiliated to the targeted MCPTT group and skip the rest of the steps;
b) if the applicable MCPTT group information entry was found in step 3) and the affiliation status of the MCPTT group information entry is "deaffiliating" or "deaffiliated", shall determine that the MCPTT user at the MCPTT client to not be affiliated to the targeted MCPTT group and skip the rest of the steps; or
c) if the applicable MCPTT group information entry was not found in step 3), shall determine that the MCPTT user at the MCPTT client is not affiliated to the targeted MCPTT group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.12 Affiliation status change by implicit affiliation | This clause is referenced from other procedures.
Upon receiving a SIP request that requires implicit affiliation of the sending MCPTT client to an MCPTT group, the participating MCPTT function:
1) shall determine the served MCPTT client ID from the <mcptt-client-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP request;
2) shall determine the MCPTT group ID from the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP request;
3) shall determine the served MCPTT ID by using the public user identity in the P-Asserted-Identity header field of the SIP 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.
4) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
5) shall consider an MCPTT client information entry such that:
a) the MCPTT client information entry is in the list of MCPTT client information entries of the served MCPTT user information entry; and
b) the MCPTT client ID of the MCPTT client information entry is equal to the served MCPTT client ID;
as the served MCPTT client information entry;
6) shall consider a copy of the list of the MCPTT group information entries of the served MCPTT client information entry as the served list of the MCPTT group information entries;
7) shall construct the candidate list of the MCPTT group information entries as follows:
a) for each MCPTT group ID which has an MCPTT group information entry in the served list of the MCPTT group information entries shall copy the MCPTT group information entry into a new MCPTT group information entry of the candidate list of the MCPTT group information entries; and
b) if the determined MCPTT group ID does not have an MCPTT group information entry in the served list of the MCPTT group information entries or has an MCPTT group information entry in the served list of the MCPTT group information entries, such that the expiration time of the MCPTT group information entry has already expired:
i) shall add a new MCPTT group information entry in the candidate list of the MCPTT group information list for the determined MCPTT group ID;
ii) shall set the affiliation status of the new MCPTT group information entry to the "affiliating" state; and
iii) shall set the expiration time of the new MCPTT group information entry to the current time increased with the candidate expiration interval;
8) determine the candidate number of MCPTT group IDs as the number of different MCPTT group IDs which have an MCPTT group information entry:
a) in the candidate list of the MCPTT group information entries; or
b) in the list of the MCPTT group information entries of an MCPTT client information entry such that:
i) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry; and
ii) the MCPTT client ID of the MCPTT client information entry is not equal to the served MCPTT client ID;
with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and
9) if the candidate number of MCPTT group IDs is bigger than the N2 value of the served MCPTT ID (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile), shall based on MCPTT service provider policy reduce the candidate MCPTT group IDs to that equal to N2;
NOTE 2: The MCPTT service provider policy can determine to remove an MCPTT group ID based on the importance or priority of other MCPTT groups, received SIP requests containing an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1 or other policy to determine which MCPTT groups are preferred.
10) if the determined MCPTT group ID cannot be added to the the candidate list of the MCPTT group information entries due to exceeding the MCPTT user's N2 limit (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile of the served MCPTT ID), shall discard the candidate list of the MCPTT group information entries and skip the remaining steps of the current procedure; and
11) shall replace the list of the MCPTT group information entries stored in the served MCPTT client information entry with the candidate list of the MCPTT group information entries. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.13 Implicit affiliation status change completion | This clause is referenced from other procedures.
If the participating MCPTT function has received a SIP 2xx response from the controlling MCPTT function to a SIP request that had triggered performing the procedures of clause 9.2.2.2.12, the participating MCPTT function:
1) shall set the affiliation status of the MCPTT group information entry added to the candidate list of the MCPTT group information entries by the procedures of clause 9.2.2.2.12 to "affiliated"; and
2) shall perform the procedures specified in clause 9.2.2.2.5 for the served MCPTT ID. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.14 Implicit affiliation status change cancellation | This clause is referenced from other procedures.
If the participating MCPTT function determines that a received SIP request that had triggered performing the procedures of clause 9.2.2.2.12 needs to be rejected or if the participating MCPTT function receives a SIP 4xx, 5xx or 6xx response from the controlling MCPTT function for the received SIP request, the participating MCPTT function:
1) shall remove the MCPTT group ID entry added by the procedures of clause 9.2.2.2.12 such that:
a) the MCPTT group information entry has the MCPTT group ID set to the MCPTT group ID of the MCPTT group targeted by the received SIP request;
b) the MCPTT group information entry is in the list of the MCPTT group information entries of an MCPTT client information entry containing the MCPTT client ID included in the received SIP request; and
c) the MCPTT client information entry is in the list of the MCPTT client information entries of the MCPTT user information entry containing the MCPTT ID of the sender of the received SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.15 Implicit affiliation to configured groups procedure | This clause is referenced from other procedures.
If the participating MCPTT function has successfully performed service authorization for the MCPTT ID identified in the service authorisation procedure as described in 3GPP TS 33.180 [78], the participating MCPTT function:
1) shall identify the MCPTT ID included in the SIP request received for service authorisation procedure as the served MCPTT ID;
2) shall identify the MCPTT client ID from the <mcptt-client-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the SIP request received for service authorisation as the served MCPTT client ID;
3) shall download the MCPTT user profile from the MCPTT user database as defined in 3GPP TS 29.283 [73] if not already stored at the participating MCPTT function;
4) if no <ImplicitAffiliations> element is contained in the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) for the served MCPTT ID or the <ImplicitAffiliations> element contains no <entry> elements containing an MCPTT group ID, shall skip the remaining steps;
5) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
6) shall consider an MCPTT client information entry such that:
a) the MCPTT client information entry is in the list of MCPTT client information entries of the served MCPTT user information entry; and
b) the MCPTT client ID of the MCPTT client information entry is equal to the served MCPTT client ID;
as the served MCPTT client information entry;
7) shall consider a copy of the list of the MCPTT group information entries of the served MCPTT client information entry as the served list of the MCPTT group information entries;
8) shall construct the candidate list of the MCPTT group information entries as follows:
a) for each MCPTT group ID which has an MCPTT group information entry in the served list of the MCPTT group information entries shall copy the MCPTT group information entry into a new MCPTT group information entry of the candidate list of the MCPTT group information entries;
b) for each MCPTT group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) for the served MCPTT ID that does not have an MCPTT group information entry in the served list of the MCPTT group information entries or has an MCPTT group information entry in the served list of the MCPTT group information entries such that the expiration time of the MCPTT group information entry has already expired:
i) shall add a new MCPTT group information entry in the candidate list of the MCPTT group information list for the MCPTT group ID;
ii) shall set the affiliation status of the new MCPTT group information entry to the "affiliating" state; and
iii) shall set the expiration time of the new MCPTT group information entry to the current time increased with the candidate expiration interval;
c) if in step b) above, no new MCPTT group information entries were added to the candidate list of the MCPTT group information list for the MCPTT group ID:
i) shall discard the candidate list; and
ii) shall skip the remaining steps;
9) determine the candidate number of MCPTT group IDs as the number of different MCPTT group IDs which have an MCPTT group information entry:
a) in the candidate list of the MCPTT group information entries; or
b) in the list of the MCPTT group information entries of an MCPTT client information entry such that:
i) the MCPTT client information entry is in the list of the MCPTT client information entries of the served MCPTT user information entry; and
ii) the MCPTT client ID of the MCPTT client information entry is not equal to the served MCPTT client ID;
with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and
c) if the candidate number of MCPTT group IDs is bigger than the N2 value of the served MCPTT ID (specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile), shall based on MCPTT service provider policy reduce the candidate MCPTT group IDs to that equal to N2;
NOTE 1: The MCPTT service provider policy can determine to remove an MCPTT group ID based on the importance or priority of other MCPTT groups, received SIP requests containing an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1 or other policy to determine which MCPTT groups are preferred.
10) shall replace the list of the MCPTT group information entries stored in the served MCPTT client information entry with the candidate list of the MCPTT group information entries; and
11) for each MCPTT group ID contained in an <entry> element of the <ImplicitAffiliations> element in the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) for the served MCPTT ID and which has an MCPTT group information entry in the candidate list of the MCPTT group information entries with an affiliation status of "affiliating", shall perform the procedures specified in clause 9.2.2.2.6 for the served MCPTT ID and each MCPTT group ID.
NOTE 2: To learn of the MCPTT groups successfully affiliated to, the MCPTT client can subscribe to that information by the procedures specified in clause 9.2.1.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.2.16 Forwarding subscription to group dynamic data towards the controlling MCPTT server procedure | Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-uri> element which identifies an MCPTT group ID not served by the MCPTT server;
3) 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]; and
4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
then the MCPTT server:
1) shall identify the target MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info MIME body of the SIP SUBSCRIBE request;
2) shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) shall if the originating MCPTT ID is not authorized for this subscription reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
4) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCPTT server:
a) shall set the Request-URI to the public service identity identifying the controlling MCPTT function serving the target MCPTT group ID;
NOTE 1: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: 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 3: 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 4: How the participating MCPTT function determines the public service identity of the controlling MCPTT function serving he target MCPTT group ID 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.
b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
A) shall include the <mcptt-request-uri> element set to the target MCPTT group ID; and
B) shall include the <mcptt-calling-user-id> element set to the originating MCPTT ID; and
d) shall include other signalling elements from the received SIP SUBSCRIBE request; and
4) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [4].
The MCPTT server shall forward any received SIP responses to the SIP SUBSCRIBE request, any received SIP NOTIFY requests and any received SIP responses to the SIP NOTIFY request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3 Procedures of MCPTT server owning the MCPTT group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.1 General | The procedures of MCPTT server owning the MCPTT group consist of:
- receiving group affiliation status change procedure;
- receiving subscription to affiliation status procedure;
- sending notification of change of affiliation status procedure;
- affiliation eligibility check procedure;
- implicit affiliation eligibility check procedure;
- affiliation status change by implicit affiliation procedure;
- receiving subscription to group dynamic data procedure and;
- sending notification of change of group dynamic data procedure.
NOTE: Usage of CSC-3 part of MCPTT group affiliation procedure and of CSC-3 part of MCPTT group de-affiliation procedure is not specified in this version of the specification. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.2 Stored information | The MCPTT server shall maintain a list of MCPTT group information entries.
In each MCPTT group information entry, the MCPTT server shall maintain:
1) an MCPTT group ID. This field uniquely identifies the MCPTT group information entry in the list of the MCPTT group information entries;
2) the status of the MCPTT group as defined in clause 10.1.5.5 of 3GPP TS 23.280 [82], along with the MCPTT ID of the user that last changed the status; and
3) a list of MCPTT user information entries.
In each MCPTT user information entry, the MCPTT server shall maintain:
1) an MCPTT ID. This field uniquely identifies the MCPTT user information entry in the list of the MCPTT user information entries;
2) a list of MCPTT client information entries; and
3) an expiration time.
In each MCPTT client information entry, the MCPTT server shall maintain:
1) an MCPTT client ID. This field uniquely identifies the MCPTT client information entry in the list of the MCPTT client information entries. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.3 Receiving group affiliation status change procedure | Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains the public service identity of the controlling MCPTT function associated with the served MCPTT group;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to clause 9.3.1.2;
then the MCPTT server:
1) shall identify the served MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
3) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
4) if an MCPTT group for the served MCPTT group ID does not exist in the group management server according to 3GPP TS 24.481 [31], shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
5) if the handled MCPTT ID is not a member of the MCPTT group identified by the served MCPTT group ID, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
6) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37]. In the SIP 200 (OK) response, the MCPTT server:
a) shall set the Expires header field according to IETF RFC 3903 [37], to the selected expiration time;
7) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCPTT group ID, shall not continue with the rest of the steps;
8) if the handled MCPTT ID is different from the MCPTT ID in the "id" attribute of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request, shall not continue with the rest of the steps;
9) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries described in clause 9.2.2.3.2; and
b) the MCPTT group ID of the MCPTT group information entry is equal to the served MCPTT group ID;
as the served MCPTT group information entry;
10) if the selected expiration time is zero:
a0) if the MCPTT group identity configuration for the served MCPTT group ID found in the group management server according to 3GPP TS 24.481 [31] contains:
i) a <forbidden-deaffiliation-FAs> element and the handled MCPTT ID has activated a functional alias that matches with one of the <entry> elements of the <forbidden-deaffiliation-FAs> element; or
ii) a <forbidden-deaffiliation-if-last-FAs> element and the handled MCPTT ID has activated a functional alias that matches with one of the <entry> elements of the <forbidden-deaffiliation-if-last-FAs> element and corresponds to the last user that has bound the functional alias to the served MCPTT group ID;
shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
NOTE: The MCPTT server learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.2.2.7.
a) shall remove the MCPTT user information entry such that:
i) the MCPTT user information entry is in the list of the MCPTT user information entries of the served MCPTT group information entry; and
ii) the MCPTT user information entry has the MCPTT ID set to the served MCPTT ID;
11) if the selected expiration time is not zero:
a) shall consider an MCPTT user information entry such that:
i) the MCPTT user information entry is in the list of the MCPTT user information entries of the served MCPTT group information entry; and
ii) the MCPTT ID of the MCPTT user information entry is equal to the handled MCPTT ID;
as the served MCPTT user information entry;
b) if the MCPTT user information entry does not exist:
i) shall insert an MCPTT user information entry with the MCPTT ID set to the handled MCPTT ID into the list of the MCPTT user information entries of the served MCPTT group information entry; and
ii) shall consider the inserted MCPTT user information entry as the served MCPTT user information entry; and
c) shall set the following information in the served MCPTT user information entry:
i) set the MCPTT client ID list according to the "client" attributes of the <affiliation> elements of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
ii) set the expiration time according to the selected expiration time;
12) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request;
13) shall perform the procedures specified in clause 9.2.2.3.5 for the served MCPTT group ID;
14) if there is an outstanding MCPTT emergency alert on the MCPTT group to which the user affiliated, shall perform the procedures specified in clause 12.1.3.4; and
15) if MCPTT group to which the client affiliated is already regrouped, shall notify the client about the regroup condition of the group by performing the procedures specified in clause 16.2.4.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.4 Receiving subscription to affiliation status procedure | NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCPTT function associated with the served MCPTT group;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and
5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to clause 9.3.2 indicating the same MCPTT ID as in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
then the MCPTT server:
1) shall identify the served MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
4) if an MCPTT group for the served MCPTT group ID does not exist in the group management server according to 3GPP TS 24.481 [31], shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
5) if the handled MCPTT ID is not a member of the MCPTT group identified by the served MCPTT group ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and
6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify subscriber about changes of the information of the served MCPTT ID, as described in clause 9.2.2.3.5. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.5 Sending notification of change of affiliation status procedure | In order to notify the subscriber identified by the handled MCPTT ID about changes of the affiliation status of the served MCPTT group ID, the MCPTT server:
1) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries described in clause 9.2.2.3.2; and
b) the MCPTT group ID of the MCPTT group information entry is equal to the served MCPTT group ID;
2) shall consider an MCPTT user information entry such:
a) the MCPTT user information entry is in the list of the MCPTT user information entries of the served MCPTT group information entry; and
b) the MCPTT ID of the MCPTT user information entry is equal to the handled MCPTT ID;
as the served MCPTT user information entry;
3) shall generate an application/pidf+xml MIME body indicating per-group affiliation information according to clause 9.3.1 and the served list of the served MCPTT user information entry of the MCPTT group information entry with following clarifications:
a) the MCPTT server shall include the "expires" attribute in the <affiliation> element; and
b) if this procedures is invoked by procedure in clause 9.2.2.3.3 where the handled p-id was identified, the MCPTT server shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and
4) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9.2.2.3.4. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-group affiliation information. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.6 Implicit affiliation eligibility check procedure | This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to check on the eligibility of the MCPTT user to be implicitly affiliated to the MCPTT group, the controlling MCPTT function:
1) shall perform the procedures of clause 9.2.2.3.8 to determine if the MCPTT user is eligible to be affiliated to the MCPTT group; and
2) if the MCPTT user was determined eligible to be affiliated to the MCPTT group by the procedures of clause 9.2.2.3.8, shall consider the MCPTT user to be eligible for implicit affiliation to the MCPTT group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.7 Affiliation status change by implicit affiliation procedure | This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to perform an implicit affiliation to, the controlling MCPTT function:
1) shall identify the served MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP request;
3) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries described in clause 9.2.2.3.2; and
b) the MCPTT group ID of the MCPTT group information entry is equal to the served MCPTT group ID;
as the served MCPTT group information entry;
4) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of the MCPTT user information entries of the served MCPTT group information entry; and
b) the MCPTT ID of the MCPTT user information entry is equal to the handled MCPTT ID;
as the served MCPTT user information entry;
c) if the MCPTT user information entry does not exist:
i) shall insert an MCPTT user information entry with the MCPTT ID set to the handled MCPTT ID into the list of the MCPTT user information entries of the served MCPTT group information entry; and
ii) shall consider the inserted MCPTT user information entry as the served MCPTT user information entry; and
d) shall make the following modifications in the served MCPTT user information entry:
i) add the MCPTT client ID derived from the received SIP request to the MCPTT client ID list if not already present; and
ii) set the expiration time as determined by local policy;
5) shall perform the procedures specified in clause 9.2.2.3.5 for the served MCPTT group ID. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.8 Affiliation eligibility check procedure | This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to check on the eligibility of the MCPTT user to be affiliated to the MCPTT group, the controlling MCPTT function shall:
1) shall identify the served MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP request;
3) if an MCPTT group for the served MCPTT group ID does not exist in the group management server according to 3GPP TS 24.481 [31], shall consider the MCPTT user to be ineligible for affiliation and skip the rest of the steps;
4) if the handled MCPTT ID is not a member of the MCPTT group identified by the served MCPTT group ID, shall consider the MCPTT user to be ineligible for affiliation and skip the rest of the steps;
5) if there is no MCPTT group information entry in the list of MCPTT group information entries described in clause 9.2.2.3.2 with an MCPTT group identity matching the served MCPTT group ID, then shall consider the MCPTT user to be ineligible for affiliation and skip the rest of the steps; or
6) shall consider the MCPTT user to be eligible for affiliation. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.9 Receiving subscription to group dynamic data procedure | Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCPTT function associated with the served MCPTT group;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and
5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-group dynamic data of presence event package notification information according to clause 9.3.2 indicating the same MCPTT group ID as in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
then the MCPTT server:
1) shall identify the served MCPTT group ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
4) if an MCPTT group for the served MCPTT group ID does not exist in the group management server according to 3GPP TS 24.481 [31], shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
5) if the handled MCPTT ID is not authorized to subscribe to group dynamic data of the MCPTT group identified by the served MCPTT group ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and
6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify subscriber about changes of the information of the served MCPTT ID, as described in clause 9.2.2.3.10. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.10 Sending notification of change of group dynamic data procedure | In order to notify the subscriber identified by the handled MCPTT ID about changes of the per-group dynamic data of the served MCPTT group ID, the MCPTT server:
1) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries described in clause 9.2.2.3.2; and
b) the MCPTT group ID of the MCPTT group information entry is equal to the served MCPTT group ID;
2) shall generate an application/pidf+xml MIME body indicating per-group dynamic data according to clause 9.3.1 with the following clarifications:
a) the MCPTT server shall include the "expires" attribute in the <affiliation> element; and
3) shall send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9.2.2.3.8. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-group dynamic data. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.2.2.3.11 Implicit affiliation status change cancellation | This clause is referenced from other procedures.
The participating MCPTT function:
1) shall remove the MCPTT user information entry added by the procedures of clause 9.2.2.3.7 such that:
a) the MCPTT client information entry has the MCPTT client ID set to the MCPTT client ID of the MCPTT user whose affiliation status is to be cancelled;
b) the MCPTT client information entry is in the list of the MCPTT client information entries of the MCPTT user information entry containing the MCPTT ID of the MCPTT user whose affiliation status to be cancelled; and
c) the MCPTT user information entry is in the list of the MCPTT user information entries of an MCPTT group information entry containing the MCPTT group ID set to the MCPTT group ID of the MCPTT group from which the affiliation of the MCPTT user is to be cancelled. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3 Coding | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.1 Extension of application/pidf+xml MIME type | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.1.1 Introduction | The clauses of the parent clause describe an extension of the application/pidf+xml MIME body specified in IETF RFC 3863 [52]. The extension is used to indicate:
- per-user affiliation information;
- per-group affiliation information; and
- per-group dynamic data information. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.1.2 Syntax | The application/pidf+xml MIME body indicating per-user affiliation information is constructed according to IETF RFC 3863 [52] and:
1) contains a <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the MCPTT ID of the MCPTT user;
3) contains one <tuple> child element according to IETF RFC 3863 [52] per each MCPTT client of the <presence> element;
4) can contain a <p-id> child element defined in the XML schema defined in table 9.3.1.2-1, of the <presence> element set to an identifier of a SIP PUBLISH request;
5) contains an "id" attribute of the <tuple> element set to the MCPTT client ID;
6) contains one <status> child element of each <tuple> element;
7) contains one <affiliation> child element defined in the XML schema defined in table 9.3.1.2-1, of the <status> element, for each MCPTT group in which the MCPTT user is interested at the MCPTT client;
8) contains a "group" attribute of each <affiliation> element set to the MCPTT group ID of the MCPTT group in which the MCPTT user is interested at the MCPTT client;
9) can contain a "status" attribute of each <affiliation> element indicating the affiliation status of the MCPTT user to MCPTT group at the MCPTT client; and
10) can contain an "expires" attribute of each <affiliation> element indicating expiration of affiliation of the MCPTT user to MCPTT group at the MCPTT client.
The application/pidf+xml MIME body indicating per-group affiliation information is constructed according to IETF RFC 3856 [51] and:
1) contains the <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the MCPTT group ID of the MCPTT group;
3) contains one <tuple> child element according to IETF RFC 3863 [52] of the <presence> element;
4) can contain a <p-id> child element defined in the XML schema defined in table 9.3.1.2-1, of the <presence> element set to an identifier of a SIP PUBLISH request;
5) contains an "id" attribute of the <tuple> element set to the MCPTT ID of the MCPTT user;
6) contains one <status> child element of each <tuple> element;
7) contains one <affiliation> child element defined in the XML schema defined in table 9.3.1.2-1, of the <status> element, for each MCPTT client at which the MCPTT user is interested in the MCPTT group;
8) contains one "client" attribute defined in the XML schema defined in table 9.3.1.2-1, of the <affiliation> element set to the MCPTT client ID;
9) can contain an "expires" attribute defined in the XML schema defined in table 9.3.1.2-1, of the <affiliation> element indicating expiration of affiliation of the MCPTT user to MCPTT group at the MCPTT client; and
10) can contain one <functionalAlias> child element defined in the XML schema defined in table 9.3.1.2-1, of the <status> element, for each functional alias that the group member identified by the "id" attribute of the <tuple> element has activated with the "functionalAliasID" attribute set to the corresponding functional alias ID.
The application/pidf+xml MIME body indicating per-group dynamic data information is constructed according to IETF RFC 3856 [51] and:
1) contains the <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the MCPTT group ID of the MCPTT group;
3) can contain a <groupStatus> child element defined in the XML schema, of the <presence> element set to an appropriate value specified in Table 9.3.1.2-3;
4) can contain a "ModifiedBy" attribute of the <groupStatus> element;
5) can contain an <additionalData> child element definied in the XML schema defined in table 9.3.1.2-1, of the <presence> element;
6) can contain a <groupBroadcastAlias> attribute defined in the XML schema defined in table 9.3.1.2-1 of the <additionalData> element;
7) can contain a <groupRegroupAlias> attribute defined in the XML schema defined in table 9.3.1.2-1 of the <additionalData> element;
8) can contain a <groupCallOnoing> attribute defined in the XML schema defined in table 9.3.1.2-1 of the <additionalData> element;
9) contains one <tuple> child element per affiliated MCPTT ID of the MCPTT group, according to IETF RFC 3863 [52] of the <presence> element;
10) contains an "id" attribute of the <tuple> element set to the MCPTT ID of the group member;
11) contains one <status> child element of each <tuple> element;
12) contains one <affiliation> child element defined in the XML schema defined in table 9.3.1.2-1, of the <status> element, for each MCPTT client at which the MCPTT user is interested in the MCPTT group;
13) contains one "client" attribute defined in the XML schema defined in table 9.3.1.2-1, of the <affiliation> element set to the MCPTT client ID;
14) can contain an "expires" attribute defined in the XML schema defined in table 9.3.1.2-1, of the <affiliation> element indicating expiration of affiliation of the MCPTT user to MCPTT group at the MCPTT client; and
15) can contain one <functionalAlias> child element defined in the XML schema defined in table 9.3.1.2-1, of the <status> element, for each functional alias that the group member identified by the "id" attribute of the <tuple> element has activated with the "functionalAliasID" attribute set to the corresponding functional alias ID.
Table 9.3.1.2-1: XML schema with elements and attributes extending the application/pidf+xml MIME body
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttPresInfo:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttPI10="urn:3gpp:ns:mcpttPresInfo:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCPTT specific child elements of presence element -->
<xs:element name="p-id" type="xs:string"/>
<xs:element name="groupStatus" type="mcpttPI10:groupStatusType"/>
<xs:element name="additionalData" type="mcpttPI10:additionalDataType"/>
<!-- MCPTT specific child elements of tuple element -->
<xs:element name="affiliation" type="mcpttPI10:affiliationType"/>
<xs:complexType name="affiliationType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="group" type="xs:anyURI" use="optional"/>
<xs:attribute name="client" type="xs:anyURI" use="optional"/>
<xs:attribute name="status" type="mcpttPI10:statusType" use="optional"/>
<xs:attribute name="expires" type="xs:dateTime" use="optional"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="functionalAlias" type="mcpttPI10:functionalAliasType"/>
<xs:complexType name="functionalAliasType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="functionalAliasID" type="xs:anyURI" use="optional"/>
<xs:attribute name="expires" type="xs:dateTime" use="optional"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="statusType">
<xs:restriction base="xs:string">
<xs:enumeration value="affiliating"/>
<xs:enumeration value="affiliated"/>
<xs:enumeration value="deaffiliating"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="groupStatusType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="ModifiedBy" type="xs:anyURI" use="optional"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="emptyType"/>
<xs:complexType name="additionalDataType">
<xs:complexContent>
<xs:extension base="mcpttPI10:emptyType">
<xs:attribute name="groupBroadcastAlias" type="xs:anyURI" use="optional"/>
<xs:attribute name="groupRegroupAlias" type="xs:anyURI" use="optional"/>
<xs:attribute name="groupCallOngoing" type="xs:boolean" use="optional"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
The application/pidf+xml MIME body refers to namespaces using prefixes specified in table 9.3.1.2-2.
Table 9.3.1.2-2: Assignment of prefixes to namespace names in the application/pidf+xml MIME body
Prefix
Namespace
mcpttPI10
urn:3gpp:ns:mcpttPresInfo:1.0
NOTE: The "urn:ietf:params:xml:ns:pidf" namespace is the default namespace so no prefix is used for it in the application/pidf+xml MIME body.
Table 9.3.1.2-3 ABNF syntax of values of the <groupStatus> element
in-peril-value = %x69.6E.2D.70.65.72.69.6C ; "in-peril"
emergency-value = %x65.6D.65.72.67.65.6E.63.79 ; "emergency" |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.2 Extension of application/simple-filter+xml MIME type | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.2.1 Introduction | The clauses of the parent clause describe an extension of the application/simple-filter+xml MIME body specified in IETF RFC 4661 [63].
The extension is used to indicate per-client restrictions of presence event package notification information, per-user restrictions of presence event package notification information and per-group dynamic data restrictions of presence event package notification information. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 9.3.2.2 Syntax | The application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains a <ns-bindings> child element according to IETF RFC 4661 [63], of the <filter-set> element;
3) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63] set to "pidf"; and
B) contains a "urn" attribute set to the "urn:ietf:params:xml:ns:pidf" value;
4) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63], set to "mcpttPI10"; and
B) contains an "urn" attribute according to IETF RFC 4661 [63], set to the "urn:3gpp:ns:mcpttPresInfo:1.0" value;
5) contains a <filter> child element according to IETF RFC 4661 [63], of the <filter-set> element where the <filter> element;
A) contains an "id" attribute set to a value constructed according to IETF RFC 4661 [63];
B) does not contain an "uri" attribute of the <filter> child element according to IETF RFC 4661 [63]; and
C) does not contain an "domain" attribute according to IETF RFC 4661 [63];
6) contains a <what> child element according to IETF RFC 4661 [63], of the <filter> element; and
7) contains an <include> child element according to IETF RFC 4661 [63], of the <what> element where the <include> element;
A) does not contain a "type" attribute according to IETF RFC 4661 [63]; and
B) contains the value, according to IETF RFC 4661 [63], set to concatenation of the '//pidf:presence/pidf:tuple[@id="' string, the MCPTT client ID, and the '"]' string.
The application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains a <ns-bindings> child element according to IETF RFC 4661 [63], of the <filter-set> element;
3) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63] set to "pidf"; and
B) contains a "urn" attribute set to the "urn:ietf:params:xml:ns:pidf" value;
4) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63], set to "mcpttPI10"; and
B) contains an "urn" attribute according to IETF RFC 4661 [63], set to the "urn:3gpp:ns:mcpttPresInfo:1.0" value;
5) contains a <filter> child element according to IETF RFC 4661 [63], of the <filter-set> element where the <filter> element;
A) contains an "id" attribute set to a value constructed according to IETF RFC 4661 [63];
B) does not contain an "uri" attribute of the <filter> child element according to IETF RFC 4661 [63]; and
C) does not contain an "domain" attribute according to IETF RFC 4661 [63];
6) contains a <what> child element according to IETF RFC 4661 [63], of the <filter> element; and
7) contains an <include> child element according to IETF RFC 4661 [63], of the <what> element where the <include> element;
A) does not contain a "type" attribute according to IETF RFC 4661 [63]; and
B) contains the value, according to IETF RFC 4661 [63], set to concatenation of the '//pidf:presence/pidf:tuple[@id="' string, the MCPTT ID, and the '"]' string.
The application/simple-filter+xml MIME body indicating per-group dynamic data restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains an <ns-bindings> child element according to IETF RFC 4661 [63], of the <filter-set> element;
3) contains an <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63] set to "pidf"; and
B) contains a "urn" attribute set to the "urn:ietf:params:xml:ns:pidf" value;
4) contains an <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63], set to "mcpttPI10"; and
B) contains a "urn" attribute according to IETF RFC 4661 [63], set to the "urn:3gpp:ns:mcpttPresInfo:1.0" value;
5) contains a <filter> child element according to IETF RFC 4661 [63], of the <filter-set> element where the <filter> element;
A) contains an "id" attribute set to a value constructed according to IETF RFC 4661 [63];
B) does not contain a "uri" attribute of the <filter> child element according to IETF RFC 4661 [63]; and
C) does not contain a "domain" attribute according to IETF RFC 4661 [63];
6) contains a <what> child element according to IETF RFC 4661 [63], of the <filter> element; and
7) contains one or more <include> child elements according to IETF RFC 4661 [63], of the <what> element where the <include> element(s);
A) does not contain a "type" attribute according to IETF RFC 4661 [63]; and
B) can contain one of the values, according to IETF RFC 4661 [63], needed to retrieve the dynamic group data the UE is interested in:
a) "//pidf:presence/pidf:groupStatus/@pidf:ModifiedBy" if the group status is requested;
b) "//pidf:presence/pidf:additionalData/@pidf:groupBroadcastAlias" if the group broadcast alias is requested;
c) "//pidf:presence/pidf:additionalData/@pidf:groupRegroupAlias" if the group regroup alias is requested;
d) "//pidf:presence/pidf:additionalData/@pidf:groupCallOngoing" if the group call ongoing information is requested; or
e) "//pidf:presence/pidf:tuple/pidf:status/pidf:affiliation/@pidf:client [@pidf:status="affiliated"]" if the Contact address for all affiliated users are requested.
9A Functional Alias
9A.1 General
Clause 9A.2 contains the procedures for management of Functional Alias at the MCPTT client, the MCPTT server serving the MCPTT user and the MCPTT server owning the Functional Alias.
Clause 9A.3 describes the coding used for management of Functional Aliases.
9A.2 Procedures
9A.2.1 MCPTT client procedures
9A.2.1.1 General
The MCPTT client procedures consist of:
- a functional alias status change procedure;
- a functional alias status determination procedure; and
- a location based functional alias status change procedure.
In order to obtain information about success or rejection of changes triggered by the functional alias status change procedure for an MCPTT user, the MCPTT client needs to initiate the functional alias status determination procedure for the MCPTT user before starting the functional alias status change procedure for the MCPTT user.
9A.2.1.2 Functional alias status change procedure
In order:
- to indicate that an MCPTT user requests to activate or to take-over one or more functional aliases;
- to indicate that the MCPTT user requests to deactivate one or more functional aliases;
- to indicate that the MCPTT user continues to have interest in one or more functional aliases due to near expiration of the expiration time of a functional alias with the status set to the "activated" state received in a SIP NOTIFY request in clause 9A.2.1.3;
- to indicate that the MCPTT client entering into or exiting from a location area triggers one or more functional aliases to be activated;
- to indicate that the MCPTT client entering into or exiting from a location area triggers one or more functional aliases to be deactivated; or
- any combination of the above;
the MCPTT client shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37], and IETF RFC 3856 [51].
When the MCPTT user requests to deactivate a functional alias, the MCPTT client shall first check the <manual-deactivation-not-allowed-if-location-criteria-met> element within the <anyExt> element of the <entry> element corresponding to the functional alias within the <FunctionalAliasList> list element of the <anyExt> element of the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]). If the functional alias has been activated due to a location area trigger and the <manual-deactivation-not-allowed-if-location-criteria-met> element is set to a value of "true", the MCPTT client shall suppress the MCPTT user's request.
NOTE 1: If the request is suppressed, a notification message can be displayed to the user.
In the SIP PUBLISH request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include the <mcptt-request-uri> element set to the MCPTT ID of the MCPTT user;
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) if the MCPTT client requests to activate one or more functional aliases, shall set the Expires header field according to IETF RFC 3903 [37], 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].
5) if the MCPTT client requests to deactivate any functional alias, shall set the Expires header field according to IETF RFC 3903 [37], to zero; and
NOTE 3: Activation of one or more functional alias and deactivation of any functional alias cannot be performed with the same PUBLISH request.
6) shall include an application/pidf+xml MIME body indicating per-user functional alias information according to clause 9A.3.1. In the MIME body, the MCPTT client:
a) shall include all functional aliases where the MCPTT user requests activation for the MCPTT ID;
b) shall include the MCPTT client ID of the targeted MCPTT client;
c) shall not include the "status" attribute and the "expires" attribute in the <>functionalAlias element;
d) if the MCPTT client has received an indication that take over of a functional alias is possible and intends to take over a functional alias, shall include a <take-over> child element in the <status> element set to "true"; and
NOTE 4: The MCPTT client learns that take over of a functional alias is possible from procedures specified in clause 9A.2.1.3 (i.e., when status attribute is set to "take-over-possible"). The take-over indication applies to all functional aliases.
e) shall set the <p-id-fa> child element of the <presence> root element to a globally unique value.
NOTE 5: This procedure deviates from IETF RFC 3903 [37] by possibly including an application/pidf+xml MIME body when refreshing the expiration time for one or more functional aliases. The use of this MIME body provides the ability to refresh activation or to deactivate of multiple functional aliases in a single message.
The MCPTT client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
9A.2.1.3 Functional alias status determination procedure
NOTE 1: The MCPTT UE also uses this procedure to determine which functional alias have been successfully activated for the MCPTT ID and which MCPTT IDs have successfully activated a specific functional alias.
In order to discover functional aliases:
1) which are activated for the MCPTT user or which the MCPTT user is allowed to take-over; or
2) which another MCPTT user has activated;
Or in order to discover MCPTT IDs:
1) which have activated a functional alias;
the MCPTT client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) In order to discover functional aliases that are activated for the MCPTT user shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include:
a) the <mcptt-request-uri> element set to the MCPTT ID of the targeted MCPTT user; and
b) the <request-type> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element set to the value "functional-alias-status-determination";
2a) In order to discover MCPTT IDs that have activated a certain functional alias shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT client shall include:
a) the <mcptt-request-uri> element set to the functional alias; and
b) the <req-type> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element set to the value "fa-user-status-determination";
2b) shall include an application/simple-filter+xml MIME body indicating per-functional alias restrictions of presence event package notification information according to clause 9.3.2;
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) 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 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) 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;
6) shall include an Events header field set to "presence"; and
7) shall include an Accept header field containing the application/pidf+xml MIME type.
In order to re-subscribe or de-subscribe, the MCPTT client shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT client:
1) 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 3: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
2) if the MCPTT client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
3) shall include an Events header field set to "presence"; and
4) shall include an Accept header field containing the application/pidf+xml MIME type.
Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-user functional alias information constructed according to clause 9A.3.1, then the MCPTT client shall determine the status of each functional alias for the MCPTT user in the MIME body. If the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request is included, the <p-id-fa> element value indicates the SIP PUBLISH request which triggered sending of the SIP NOTIFY request.
If the MCPTT client detected a functional alias activation or deactivation, it shall perform the procedure specified in clause 9.2.1.7.
9A.2.1.4 Location based functional alias status change procedure
If a location criterion for functional alias activation or de-activation is met, the MCPTT client shall initiate the functional alias status change procedure as specified in clause 9A.2.1.2.
9A.2.2 MCPTT server procedures
9A.2.2.1 General
The MCPTT server procedures consist of:
- procedures of MCPTT server serving the MCPTT user; and
- procedures of MCPTT server owning the functional alias.
9A.2.2.2 Procedures of MCPTT server serving the MCPTT user
9A.2.2.2.1 General
The procedures of MCPTT server serving the MCPTT user consist of:
- a receiving functional alias status change from MCPTT client procedure;
- a receiving subscription to functional alias status procedure;
- a sending notification of change of functional alias status procedure;
- a sending functional alias status change towards MCPTT server owning the functional procedure;
- a functional alias status determination from MCPTT server owning the functional alias procedure;
- a functional alias resolution from MCPTT server owning the functional alias procedure; and
- a forwarding subscription to functional alias status towards another MCPTT server procedure, which is used to identify the status of functional aliases activated by a target user who is served by another MCPTT server.
9A.2.2.2.2 Stored information
The MCPTT server shall maintain a list of MCPTT user information entries. The list of the MCPTT user information entries contains one MCPTT user information entry for each served MCPTT ID.
In each MCPTT user information entry, the MCPTT server shall maintain:
1) an MCPTT ID. This field uniquely identifies the MCPTT user information entry in the list of the MCPTT user information entries; and
2) a list of functional alias information entries.
In each functional alias information, the MCPTT server shall maintain:
1) a functional alias ID. This field uniquely identifies the functional alias information entry in the list of the functional alias information entries;
2) a functional alias status;
3) an expiration time;
4) a functional alias p-id-fa; and
5) a next publishing time.
9A.2.2.2.3 Receiving functional alias status change from MCPTT client procedure
Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID served by the MCPTT server;
3) 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) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-user functional alias information according to clause 9A.3.1;
then the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
2) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP PUBLISH request;
3) if the Request-URI of the SIP PUBLISH request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
4) if the originating MCPTT ID is different than the served MCPTT ID or the originating MCPTT ID is not authorized to modify functional alias status of the served MCPTT ID, shall send a SIP 403 (Forbidden) response and shall not continue with the rest of the steps;
5) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
6) if the Expires header field of the SIP PUBLISH request has nonzero value, shall determine the candidate expiration interval to according to IETF RFC 3903 [37];
7) if the Expires header field of the SIP PUBLISH request has zero value, shall set the candidate expiration interval to zero;
8) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37]. In the SIP 200 (OK) response, the MCPTT server:
a) shall set the Expires header field according to IETF RFC 3903 [37], to the candidate expiration time;
9) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCPTT ID, shall not continue with the rest of the steps;
10) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
11) shall consider a copy of the list of the MCPTT functional alias entries of the served MCPTT user information entry as the served list of the MCPTT functional alias information entries;
12) if the candidate expiration interval is nonzero, shall construct the candidate list of the MCPTT functional alias entries as follows:
a) for each functional alias ID which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has not expired yet, and which is indicated in a "functionalAliasID" attribute of a <functionalAlias> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
i) shall copy the functional alias information entry into a new functional alias information entry of the candidate list of the functional alias information entries;
ii) if the functional alias status of the functional alias information entry is "deactivating" or "deactivated", shall set the functional alias status of the new functional alias information entry to the "activating" state and shall set the activating p-id-fa of the new functional alias information entry to the value of the <p-id-fa> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
iii) shall set the expiration time of the new functional alias information entry to the current time increased with the candidate expiration interval;
b) for each functional alias ID which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has not expired yet, and which is not indicated in any "functionalAliasID" attribute of the <functionalAlias> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
i) shall copy the functional alias information entry into a new functional alias information entry of the candidate list of the functional alias information entries; and
ii) if the functional alias status of the functional alias information entry is "activated" or "activating":
- shall set the functional alias status of the new functional alias entry to the "deactivating" state; and
- shall set the expiration time of the new functional alias information entry to the current time increased with twice the value of timer F; and
c) for each functional alias ID:
i) which does not have a functional alias information entry in the served list of the functional alias entries; or
ii) which has a functional alias information entry in the served list of the functional alias information entries, such that the expiration time of the functional alias information entry has already expired;
and which is indicated in a "functionalAliasID" attribute of the <functionalAlias> element of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request:
i) shall add a new functional alias information entry in the candidate list of the functional alias information list for the functional alias ID;
ii) shall set the functional alias status of the new functional alias information entry to the "activating" state;
iii) shall set the expiration time of the new functional alias information entry to the current time increased with the candidate expiration interval; and
iv) shall set the activating p-id-fa of the new functional alias information entry to the value of the <p-id-fa> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request;
13) if the candidate expiration interval is zero, constructs the candidate list of the functional alias information entries as follows:
a) for each functional alias ID which has an entry in the served list of the functional alias information entries:
i) shall copy the functional alias entry of the served list of the functional alias information into a new functional alias information entry of the candidate list of the functional alias information entries;
ii) shall set the functional alias status of the new functional alias information entry to the "deactivating" state; and
iii) shall set the expiration time of the new functional alias information entry to the current time increased with twice the value of timer F;
14) shall replace the list of the functional alias information entries stored in the served MCPTT user information entry with the candidate list of the functional alias information entries;
15) shall perform the procedures specified in clause 9A.2.2.2.6 for the served MCPTT ID and each functional alias:
a) which does not have a functional alias information entry in the served list of the functional alias information entries and which has a functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state;
b) which has a functional alias information entry in the served list of the functional alias information entries with the expiration time already expired, and which has a functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state;
c) which has a functional alias information entry in the served list of the functional alias information entries with the functional alias status set to the "deactivating" state or the "deactivated" state and with the expiration time not expired yet, and which has an functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "activating" state; or
d) which has a functional alias information entry in the served list of the functional alias information entries with the functional alias status set to the "activated" state and with the expiration time not expired yet, and which has an functional alias information entry in the candidate list of the functional alias information entries with the functional alias status set to the "deactivating" state;
16) shall identify the handled p-id-fa in the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
17) shall perform the procedures specified in clause 9A.2.2.2.5 for the served MCPTT ID.
9A.2.2.2.4 Receiving subscription to functional alias status procedure
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing:
a) the<mcptt-request-uri> element which identifies an MCPTT ID served by the MCPTT server; and
b) the <mcpttinfo> element with the <mcptt-Params> element containing an <anyExt> element with the <request-type> element set to a value of "functional-alias-status-determination";
3) 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]; and
4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
the MCPTT server:
1) shall identify the served MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) if the Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user, shall identify the originating MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
4) if the originating MCPTT ID is different than the served MCPTT ID and the originating MCPTT ID is not authorized to modify functional alias status of the served MCPTT ID, shall send a SIP 403 (Forbidden) response and shall not continue with the rest of the steps; and
5) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify the subscriber about changes of the information of the served MCPTT ID, as described in clause 9A.2.2.2.5.
9A.2.2.2.5 Sending notification of change of functional alias status procedure
In order to notify the subscriber about changes of functional aliases of the served MCPTT ID, the MCPTT server:
1) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
2) shall generate an application/pidf+xml MIME body indicating per-user functional alias information according to clause 9A.3.1 and the served list of the MCPTT user information entries with the following clarifications:
a) the MCPTT server shall not include information from functional alias information entry with the expiration time already expired;
b) the MCPTT server shall not include information from a functional alias information entry with the functional alias status set to the "deactivated" state;
c) if this procedures is invoked by procedure in clause 9A.2.2.2.3 where the handled p-id-fa value was identified, the MCPTT server shall set the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id-fa value; and
3) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9A.2.2.2.4. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-user functional alias information.
9A.2.2.2.6 Sending functional alias status change towards MCPTT server owning the functional alias procedure
NOTE 1: Usage of one SIP PUBLISH request to carry information about change of functional alias state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order:
- to send an activation request of a served MCPTT ID for a handled functional alias ID;
- to send a deactivation request of a served MCPTT ID for a handled functional alias ID;
- to send a take over request of a served MCPTT ID for a handled functional alias ID due to take over; or
- to send an activation request of a served MCPTT ID for a handled functional alias ID due to near expiration of the previously published information;
the MCPTT server shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51]. In the SIP PUBLISH request, the MCPTT server:
1) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled functional alias ID;
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 MCPTT function serving the MCPTT user determines the public service identity of the controlling MCPTT function associated with the handled functional alias 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.
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
a) shall include the <mcptt-request-uri> element set to the handled functional alias ID; and
b) shall include the <mcptt-calling-user-id> element set to the served MCPTT ID;
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) if sending an activation request, shall set the Expires header field according to IETF RFC 3903 [37], to 4294967295;
NOTE 7: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) if sending a deactivation request, shall set the Expires header field according to IETF RFC 3903 [37], to zero;
6) shall include a P-Asserted-Identity header field set to the public service identity of the MCPTT server according to 3GPP TS 24.229 [4];
7) shall set the current p-id-fa to a globally unique value;
8) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information entry is equal to the served MCPTT ID;
as the served MCPTT user information entry;
9) for each functional alias information entry such that:
a) the functional alias information entry has the "activating" functional alias status, the functional alias ID set to the handled functional alias ID, the expiration time has not expired yet and the activating p-id-fa is not set; and
b) the functional alias information entry is in the list of the functional alias information entries of the served MCPTT user information entry;
shall set the activating p-id-fa of the functional alias information entry to the current p-id-fa; and
10) shall include an application/pidf+xml MIME body indicating per-functional alias status information constructed according to clause 9A.3.1.2. The MCPTT server shall indicate all served MCPTT user IDs, such that:
a) the functional alias status is set to "activating" with or without "take-over" element or "activated", and the expiration time has not expired yet in a functional alias information entry with the functional alias ID set to the handled functional alias;
b) the functional alias information entry is in the list of the functional alias information entries of an MCPTT user information entry; and
c) the MCPTT user information entry is a served MCPTT user information entry.
The MCPTT server shall set the <p-id-fa> child element of the <presence> root element to the current p-id-fa.
The MCPTT server shall not include the "expires" attribute in the <functionalAlias> element.
NOTE 8: The MCPTT server sets the "status" attribute in the <functionalAlias> element to indicate whether the request is for functional alias take over.
The MCPTT server shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
If timer F expires for the SIP PUBLISH request sent for a (de)activation request of served MCPTT ID for the functional alias ID or upon receiving a SIP 3xx, 4xx, 5xx or 6xx response to the SIP PUBLISH request, the MCPTT server:
1) shall remove each functional alias ID entry such that:
a) the functional alias information entry has the functional alias ID set to the handled functional alias ID; and
b) the functional alias information entry is in the list of the functional alias information entries of the served MCPTT user information entry.
9A.2.2.2.7 Functional alias status determination from MCPTT server owning functional alias procedure
NOTE 1: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of functional alias state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order to discover whether a served MCPTT user successfully activated a handled functional alias in the MCPTT server owning the functional alias, the MCPTT server shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT server:
1) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled functional alias;
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 MCPTT function serving the MCPTT user determines the public service identity of the controlling MCPTT function associated with the handled functional alias 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.
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
a) shall include the <mcptt-request-uri> element set to the handled functional alias ID; and
b) shall include the <mcptt-calling-user-id> element set to the served MCPTT ID;
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) if the MCPTT server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 7: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) if the MCPTT server wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
6) shall include an Accept header field containing the application/pidf+xml MIME type;
7) shall include an Events header field set to "presence"; and
8) shall include an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to clause 9A.3.2, indicating the served MCPTT ID.
In order to re-subscribe or de-subscribe, the MCPTT server shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the MCPTT server:
1) if the MCPTT server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 8: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
2) if the MCPTT server wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
3) shall include an Events header field set to "presence"; and
4) shall include an Accept header field containing the application/pidf+xml MIME type.
Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-functional alias information constructed according to clause 9A.3.1, then the MCPTT server:
1) for each served MCPTT ID such that the application/pidf+xml MIME body of SIP NOTIFY request contains:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID;
c) an <functionalAlias> child element of the <status> element of the <tuple> element; and
d) the "expires" attribute of the <functionalAlias> element indicating expiration of activation of functional alias;
perform the following:
a) if a functional alias information entry exists such that:
i) the functional alias information entry has the "activating" functional alias status, the functional alias ID set to the handled functional alias ID, and the expiration time has not expired yet;
ii) the functional alias information entry is in the list of the functional alias information entries of an MCPTT user information entry with the MCPTT ID set to the served MCPTT ID; and
iii) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2;
shall set the functional alias status of the functional alias information entry to "activated"; and
shall set the next publishing time of the functional alias information entry to the current time and half of the time between the current time and the expiration of the functional alias; and
2) for each functional alias information entry such that:
a) the functional alias information entry has the "activated" functional alias status or the "deactivating" functional alias status, the functional alias ID set to the handled functional alias ID, and the expiration time has not expired yet;
b) the functional alias information entry is in the list of the functional alias information entries of an MCPTT user information entry with the MCPTT ID set to a served MCPTT ID; and
c) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2; and
for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID; and
c) an <functionalAlias> child element of the <status> child element of the <tuple> element.
perform the following:
a) shall set the functional alias status of the functional alias information entry to "deactivated"; and
b) shall set the expiration time of the functional alias information entry to the current time; and
3) if a <p-id-fa> element is included in the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request, then for each functional alias information entry such that:
a) the functional alias information entry has the "activating" functional alias status, the functional alias ID set to the handled functional alias ID, the expiration time has not expired yet and with the activating p-id-fa set to the value of the <p-id-fa> element;
b) the functional alias information entry is in the list of the functional alias information entries of an MCPTT user information entry with the MCPTT ID set to a served MCPTT ID; and
d) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9A.2.2.2.2; and
for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
a) a <tuple> element of the root <presence> element;
b) the "id" attribute of the <tuple> element indicating the served MCPTT ID; and
c) an <functionalAlias> child element of the <status> child element of the <tuple> element;
perform the following:
a) shall set the functional alias status of the functional alias information entry to "deactivated"; and
b) shall set the expiration time of the functional alias information entry to the current time.
9A.2.2.2.8 Functional alias resolution from MCPTT server owning the functional alias procedure
In order to discover the MCPTT users that have successfully activated a handled functional alias in the MCPTT server owning the functional alias, the MCPTT server shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT server:
1) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled functional alias;
NOTE 1: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: 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 3: 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 4: How the MCPTT function serving the MCPTT user determines the public service identity of the controlling MCPTT function associated with the handled functional alias 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.
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server shall include the <mcptt-request-uri> element set to the handled functional alias ID;
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 set the Expires header field according to IETF RFC 6665 [26] to zero;
NOTE 6: if the MCPTT server wants to receive the current status and later notification, can set the Expires header field according to IETF RFC 6665 [26], to 4294967295, which is the highest value defined for Expires header field in IETF RFC 3261 [24].
5) shall include an Accept header field containing the application/pidf+xml MIME type;
6) shall include an Events header field set to "presence"; and
7) shall include an application/simple-filter+xml MIME body indicating per-functional alias restrictions of presence event package notification information indicating the served functional alias.
9A.2.2.2.9 Forwarding subscription to functional alias status towards another MCPTT server procedure
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-uri> element which identifies an MCPTT ID not served by MCPTT server;
3) 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]; and
4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
then the MCPTT server:
1) shall identify the target MCPTT ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info MIME body of the SIP SUBSCRIBE request;
2) shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
3) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCPTT server:
a) shall set the Request-URI to the public service identity identifying the terminating participating MCPTT function serving the target MCPTT ID;
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 MCPTT function serving the MCPTT user determines the public service identity of the terminating participating MCPTT function of the target MCPTT ID 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.
b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
A) shall include the <mcptt-request-uri> element set to the target MCPTT ID; and
B) shall include the <mcptt-calling-user-id> element set to the originating MCPTT ID; and
d) shall include other signalling elements from the received SIP SUBSCRIBE request; and
4) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [4].
The MCPTT server shall forward to the originating MCPTT ID any received SIP responses to the SIP SUBSCRIBE request, and for the duration of the subscription any received SIP NOTIFY requests and any received SIP responses to the SIP NOTIFY request according to 3GPP TS 24.229 [4].
9A.2.2.2.10 Forwarding subscription to functional alias status towards MCPTT server owning the functional alias procedure
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-uri> element which identifies a functional alias;
3) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with: the <mcpttinfo> element containing the <mcptt-Params> element containing an <anyExt> element with the <req-type> element present and set to a value of "fa-user-status-determination";
4) 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]; and
5) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type;
then the MCPTT server:
1) if the <allow-query-functional-alias-other-user> element of the <ruleset> element is not present in the 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 SUBSCRIBE request with a SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
2) shall identify the target functional alias in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info MIME body of the SIP SUBSCRIBE request;
3) shall identify the originating MCPTT ID from public user identity in the P-Asserted-Identity header field of the SIP SUBSCRIBE request;
4) shall generate a SIP SUBSCRIBE request from the received SIP SUBSCRIBE request. In the generated SIP SUBSCRIBE request, the MCPTT server:
a) shall set the Request-URI to the public service identity of the controlling MCPTT function associated with the handled functional alias ID;
NOTE 1: The public service identity can identify of the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: 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 3: 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 4: How the MCPTT function serving the MCPTT user determines the public service identity of the controlling MCPTT function associated with the handled functional alias 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.
b) shall include a P-Asserted-Identity header field containing the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body. In the application/vnd.3gpp.mcptt-info+xml MIME body, the MCPTT server:
A) shall include the <mcptt-request-uri> element set to the target functional alias; and
B) shall include the <mcptt-calling-user-id> element set to the originating MCPTT ID; and
d) shall include other signalling elements from the received SIP SUBSCRIBE request; and
5) shall send the generated SIP SUBSCRIBE request according to 3GPP TS 24.229 [4].
The MCPTT server shall forward to the originating MCPTT ID any received SIP responses to the SIP SUBSCRIBE request, and for the duration of the subscription any received SIP NOTIFY requests according to 3GPP TS 24.229 [4].
9A.2.2.3 Procedures of MCPTT server owning the Functional alias
9A.2.2.3.1 General
The procedures of MCPTT server owning the functional alias consist of:
- receiving functional alias status change procedure;
- receiving subscription to functional alias status procedure;
- sending notification of change of functional alias status procedure;
- modification of functional alias eligibility check procedure; and
- receiving subscription to functional alias resolution procedure; and
- sending notification of functional alias resolution procedure.
9A.2.2.3.2 Stored information
The MCPTT server shall maintain a list of functional alias information entries.
In each functional alias information entry, the MCPTT server shall maintain:
1) a functional alias ID. This field uniquely identifies the functional alias information entry in the list of the functional alias information entries; and
2) a list of MCPTT user information entries.
In each MCPTT user information entry, the MCPTT server shall maintain:
1) an MCPTT ID. This field uniquely identifies the MCPTT user information entry in the list of the MCPTT user information entries;
2) a take-over possible indication; and
3) an expiration time.
9A.2.2.3.3 Receiving functional alias status change procedure
Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains the public service identity of the controlling MCPTT function associated with the served functional alias;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-functional alias information constructed according to clause 9A.3.1.2;
then the MCPTT server:
1) shall identify the served functional alias in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP PUBLISH request;
3) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
4) if the functional alias does not exist in the MCPTT server, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
4a) if SIP PUBLISH request is for activation of a functional alias then:
a) if handled MCPTT ID does not match with any of the entries in the <mcptt-user-list> which contains the MCPTT IDs of MCPTT users which are allowed to activate the functional alias; and
b) if no local policy exists that authorizes the request by the handled MCPTT ID;
shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
5) if SIP PUBLISH request is for activation of a functional alias and the number of activations for the handled functional alias is equal <max-simultaneous-activations>, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
6) if SIP PUBLISH request is for take over of a functional alias, the MCPTT server shall use the <allow-takeover> element of the MCPTT service configuration document and the <allow-takeover-functional-alias-other-user> element of the MCPTT user profile document (see 3GPP TS 24.484 [50]) to determine if take over is possible. If take over is not possible, the MCPTT server shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
7) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37]. In the SIP 200 (OK) response, the MCPTT server:
a) shall set the Expires header field according to IETF RFC 3903 [37], to the selected expiration time;
8) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served functional alias ID, shall not continue with the rest of the steps;
9) if the handled MCPTT ID is different from the MCPTT ID in the "id" attribute of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request, shall not continue with the rest of the steps;
10) shall consider a functional alias information entry such that:
a) the functional alias information entry is in the list of functional alias information entries described in clause 9A.2.2.3.2; and
b) the functional alias ID of the functional alias information entry is equal to the served functional alias ID;
as the served functional alias information entry;
11) if the selected expiration time is zero:
a) shall remove the MCPTT user information entry such that:
i) the MCPTT user information entry is in the list of the MCPTT user information entries of the served functional alias information entry; and
ii) the MCPTT user information entry has the MCPTT ID set to the served MCPTT ID;
12) if the selected expiration time is not zero:
a) shall consider an MCPTT user information entry such that:
i) the MCPTT user information entry is in the list of the MCPTT user information entries of the served functional alias information entry; and
ii) the MCPTT ID of the MCPTT user information entry is equal to the handled MCPTT ID;
as the served MCPTT user information entry;
b) if the MCPTT user information entry does not exist:
i) shall insert an MCPTT user information entry with the MCPTT ID set to the handled MCPTT ID into the list of the MCPTT user information entries of the served functional alias information entry; and
ii) shall consider the inserted MCPTT user information entry as the served MCPTT user information entry; and
c) shall set the expiration time according to the selected expiration time in the served MCPTT user information entry;
13) shall identify the handled p-id-fa in the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
14) shall perform the procedures specified in clause 9A.2.2.3.5 for the served functional alias ID.
9A.2.2.3.4 Receiving subscription to functional alias status procedure
NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of functional alias state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCPTT function associated with the served functional alias;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-uri> element and the <mcptt-calling-user-id> element;
3) 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) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and
5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to clause 9A.3.2 indicating the same MCPTT ID as in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
then the MCPTT server:
1) shall identify the served functional alias ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) shall identify the handled MCPTT ID in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
4) if a functional alias does not exist in the MCPTT server, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
5) if the handled MCPTT ID based on local policy is not authorized for notifications of the functional alias identified by the served functional alias ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and
6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify subscriber about changes of the information of the served MCPTT ID, as described in clause 9A.2.2.3.5.
9A.2.2.3.5 Sending notification of change of functional alias status procedure
In order to notify the subscriber identified by the handled MCPTT ID about changes of the functional alias status of the served functional alias ID, the MCPTT server:
1) shall consider a functional alias information entry such that:
a) the functional alias information entry is in the list of functional alias information entries described in clause 9A.2.2.3.2; and
b) the functional alias ID of the functional alias information entry is equal to the served functional alias ID;
2) shall consider an MCPTT user information entry such:
a) the MCPTT user information entry is in the list of the MCPTT user information entries of the served functional alias information entry; and
b) the MCPTT ID of the MCPTT user information entry is equal to the handled MCPTT ID;
as the served MCPTT user information entry;
3) shall generate an application/pidf+xml MIME body indicating per-functional alias information according to clause 9A.3.1 and the served list of the served MCPTT user information entry of the functional alias information entry with following clarifications:
a) the MCPTT server shall include the "expires" attribute in the <functionalAlias> element; and
b) if this procedures is invoked by procedure in clause 9A.2.2.3.3 where the handled p-id-fa was identified, the MCPTT server shall set the <p-id-fa> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id-fa value; and
4) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9A.2.2.3.4. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-functional alias information.
9A.2.2.3.6 Functional alias status automatic deactivation procedure
In order to deactivate a functional alias associated with a target MCPTT ID:
1) externally triggered by an MCPTT administrator by a mechanism outside of the scope of the standard; or
2) directly by the MCPTT function owning the functional alias as a result of an internal trigger like the expiration of the functional alias association;
the MCPTT server
1) shall consider a functional alias information entry such that:
a) the functional alias information entry is in the list of functional alias information entries described in clause 9A.2.2.3.2; and
b) the functional alias ID of the functional alias information entry is equal to the served functional alias ID;
as the served functional alias information entry;
2) shall remove the MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of the MCPTT user information entries of the served functional alias information entry; and
b) the MCPTT user information entry has the MCPTT ID set to the target MCPTT ID; and
3) shall perform the procedures specified in clause 9A.2.2.3.5 for the served functional alias ID.
9A.2.2.3.7 Receiving subscription to functional alias resolution procedure
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCPTT function associated with the requested functional alias;
2) 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) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and
4) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-functional alias restrictions of presence event package notification information according to clause 9A.3.2;
then the MCPTT server:
1) shall identify the requested functional alias ID in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP SUBSCRIBE request;
2) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
3) if the requested functional alias does not exist in the MCPTT server, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and
4) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
For the duration of the subscription, the MCPTT server shall notify subscriber about changes of the information of the requested functional alias, as described in clause 9A.2.2.3.8.
9A.2.2.3.8 Sending notification to functional alias resolution procedure
In order to notify the subscriber about the MCPTT users that have successfully activated the functional alias corresponding to the requested functional alias ID, the MCPTT server:
1) shall consider a functional alias information entry such that:
a) the functional alias information entry is in the list of functional alias information entries described in clause 9A.2.2.3.2; and
b) the functional alias ID of the functional alias information entry is equal to the requested functional alias ID;
2) shall consider any MCPTT user information entry such that the MCPTT user information entry is in the list of the MCPTT user information entries of the served functional alias information entry, as the served MCPTT user information entry;
3) shall generate an application/pidf+xml MIME body indicating per-functional alias information according to clause 9A.3.1 and the served list of the served MCPTT user information entry of the functional alias information entry
4) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 9A.2.2.3.7. In the SIP NOTIFY request, the MCPTT server shall include the generated application/pidf+xml MIME body indicating per-functional alias information.
9A.3 Coding
9A.3.1 Extension of application/pidf+xml MIME type
9A.3.1.1 Introduction
The clauses of the parent clause describe an extension of the application/pidf+xml MIME body specified in IETF RFC 3863 [52]. The extension is used to indicate:
- per-user functional alias information; and
- per-functional alias status information.
9A.3.1.2 Syntax
The application/pidf+xml MIME body indicating per-user functional alias information is constructed according to IETF RFC 3863 [52] and:
1) contains a <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the MCPTT ID of the MCPTT user;
3) contains one <tuple> child element according to IETF RFC 3863 [52] per <presence> element;
4) can contain a <p-id-fa> child element defined in the XML schema defined in table 9A.3.1.2-1, of the <presence> element set to an identifier of a SIP PUBLISH request;
5) contains an "id" attribute of the <tuple> element set to the MCPTT client ID;
6) contains one <status> child element of each <tuple> element;
7) contains one <functionalAlias> child element defined in the XML schema defined in table 9A.3.1.2-1, of the <status> element, for each functional alias in which the MCPTT user is interested;
8) contains a "functionalAliasID" attribute of each <functionalAlias> element set to the functional alias ID of the functional alias in which the MCPTT user is interested;
9) can contain a "status" attribute of each <functionalAlias> element indicating the activation status of functional alias for the MCPTT user;
10) can contain an "expires" attribute of each <functionalAlias> element indicating expiration of activation of the functional alias for the MCPTT user; and
11) can contain one <take-over> child element of the <status> element set to "true" indicating that the MCPTT user is interested to take over the functional aliases.
The application/pidf+xml MIME body indicating per-functional alias status information is constructed according to IETF RFC 3856 [51] and:
1) contains the <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the functional alias ID of the functional alias;
3) contains one <tuple> child element according to IETF RFC 3863 [52] of the <presence> element;
4) can contain a <p-id-fa> child element defined in the XML schema defined in table 9A.3.1.2-1, of the <presence> element set to an identifier of a SIP PUBLISH request;
5) contains an "id" attribute of the <tuple> element set to the functional alias ID;
6) contains one <status> child element of each <tuple> element;
7) contains one <functionalAlias> child element defined in the XML schema defined in table 9A.3.1.2-1, of the <status> element, for each MCPTT ID for which functional alias information is provided;
8) contains one "user" attribute defined in the XML schema defined in table 9A.3.1.2-1, of the <functionalAlias> element set to the MCPTT client ID; and
9) can contain an "expires" attribute defined in the XML schema defined in table 9A.3.1.2-1, of the <functionalAlias> element indicating expiration of activation of the functional alias for the MCPTT user.
Table 9A.3.1.2-1: XML schema with elements and attributes extending the application/pidf+xml MIME body
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttPresInfoFA:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttPIFA10="urn:3gpp:ns:mcpttPresInfoFA:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCPTT functional alias specific child elements of presence element -->
<xs:element name="p-id-fa" type="xs:string"/>
<!-- MCPTT functional alias specific child elements of status element -->
<xs:element name="functionalAlias" type="mcpttPIFA10:functionalAliasType"/>
<xs:complexType name="functionalAliasType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="functionalAliasID" type="xs:anyURI" use="optional"/>
<xs:attribute name="user" type="xs:anyURI" use="optional"/>
<xs:attribute name="status" type="mcpttPIFA10:statusType" use="optional"/>
<xs:attribute name="expires" type="xs:dateTime" use="optional"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="take-over" type="xs:boolean"/>
<xs:simpleType name="statusType">
<xs:restriction base="xs:string">
<xs:enumeration value="activating"/>
<xs:enumeration value="activated"/>
<xs:enumeration value="deactivating"/>
<xs:enumeration value="take-over-possible"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
The application/pidf+xml MIME body refers to namespaces using prefixes specified in table 9A.3.1.2-2.
Table 9A.3.1.2-2: Assignment of prefixes to namespace names in the application/pidf+xml MIME body
Prefix
Namespace
mcpttPIFA10
urn:3gpp:ns:mcpttPresInfoFA:1.0
NOTE: The "urn:ietf:params:xml:ns:pidf" namespace is the default namespace so no prefix is used for it in the application/pidf+xml MIME body.
9A.3.2 Extension of application/simple-filter+xml MIME type
9A.3.2.1 Introduction
The clauses of the parent clause describe an extension of the application/simple-filter+xml MIME body specified in IETF RFC 4661 [63].
The extension is used to indicate per-user restrictions of presence event package notification information for functional alias information and per-functional alias restrictions of presence event package notification information.
9A.3.2.2 Syntax
The application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains a <ns-bindings> child element according to IETF RFC 4661 [63], of the <filter-set> element;
3) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63] set to "pidf"; and
B) contains a "urn" attribute set to the "urn:ietf:params:xml:ns:pidf" value;
4) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63], set to "mcpttPIFA10"; and
B) contains an "urn" attribute according to IETF RFC 4661 [63], set to the "urn:3gpp:ns:mcpttPresInfoFA:1.0" value;
5) contains a <filter> child element according to IETF RFC 4661 [63], of the <filter-set> element where the <filter> element;
A) contains an "id" attribute set to a value constructed according to IETF RFC 4661 [63];
B) does not contain an "uri" attribute of the <filter> child element according to IETF RFC 4661 [63]; and
C) does not contain an "domain" attribute according to IETF RFC 4661 [63];
6) contains a <what> child element according to IETF RFC 4661 [63], of the <filter> element; and
7) contains an <include> child element according to IETF RFC 4661 [63], of the <what> element where the <include> element;
A) does not contain a "type" attribute according to IETF RFC 4661 [63]; and
B) contains the value, according to IETF RFC 4661 [63], set to concatenation of the '//pidf:presence/pidf:tuple[@id="' string, the MCPTT ID, and the '"]' string.
The application/simple-filter+xml MIME body indicating per-functional alias restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains a <ns-bindings> child element according to IETF RFC 4661 [63], of the <filter-set> element;
3) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63] set to "pidf"; and
B) contains a "urn" attribute set to the "urn:ietf:params:xml:ns:pidf" value;
4) contains a <ns-binding> child element according to IETF RFC 4661 [63], of the <ns-bindings> element where the <ns-binding> element:
A) contains a "prefix" attribute according to IETF RFC 4661 [63], set to "mcpttPIFA10"; and
B) contains a "urn" attribute according to IETF RFC 4661 [63], set to the "urn:3gpp:ns:mcpttPresInfoFA:1.0" value;
5) contains a <filter> child element according to IETF RFC 4661 [63], of the <filter-set> element where the <filter> element;
A) contains an "id" attribute set to a value constructed according to IETF RFC 4661 [63];
B) does not contain an "uri" attribute of the <filter> child element according to IETF RFC 4661 [63]; and
C) does not contain a "domain" attribute according to IETF RFC 4661 [63];
6) contains a <what> child element according to IETF RFC 4661 [63], of the <filter> element; and
7) contains an <include> child element according to IETF RFC 4661 [63], of the <what> element where the <include> element;
A) does not contain a "type" attribute according to IETF RFC 4661 [63]; and
B) contains the value, according to IETF RFC 4661 [63], set to concatenation of the '//pidf:presence/pidf:tuple[@id="' string, the functional alias ID, and the '"]' string.
9A.4 Functional alias to group binding for the MCPTT user procedures
9A.4.1 General
This clause describes the functional alias to group binding for the MCPTT user procedures for on-network.
For on-network functional alias to group binding for the MCPTT user, the procedures for originating MCPTT clients, participating MCPTT functions and controlling MCPTT function are specified in clause 9A.2.
An MCPTT user can bind the same functional alias with multiple MCPTT groups but an MCPTT user cannot bind multiple functional aliases to the same MCPTT group.
Only the activated functional aliases are used for creating a binding with a MCPTT group or list of MCPTT groups.
9A.4.2 On-network functional alias to group binding
9A.4.2.1 Client procedures
9A.4.2.1.1 General
On request from an MCPTT user at MCPTT client, a request to create binding of a functional alias with group for the MCPTT user is initiated by the MCPTT client towards the participating MCPTT function.
9A.4.2.1.2 Functional alias to group binding
Upon receiving a request from an MCPTT user to bind a functional alias with an MCPTT group or a list of MCPTT groups for the MCPTT user, if the <allow-functional-alias-binding-with-group> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from an MCPTT user to bind a functional alias with an MCPTT group or a list of MCPTT groups for the MCPTT user, if the requested functional alias is not activated by MCPTT user at MCPTT client, the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from an MCPTT user to bind a functional alias with an MCPTT group or a list of MCPTT groups for the MCPTT user, 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.
The MCPTT client:
1) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
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];
3) 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];
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according IETF RFC 3841 [6];
5) 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];
6) 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 <request-type> element set to a value of "fa-group-binding-req";
b) the <binding-ind> element set to a value of "true";
c) the <binding-fa-uri> element set to the URI of an activated functional alias that shall be bound with the specified list of MCPTT groups in "uri" attributes of <entry> elements of a <list> element of the <resource-lists> element in an application/resource-lists+xml MIME body;
d) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
e) 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;
7) shall include an application/resource-lists+xml MIME body containing a <resource-lists> element containing a <list> element containing one or more <entry> elements each containing a "uri" attribute set to an MCPTT group ID; 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 inform the MCPTT user of success in binding of a functional alias with the MCPTT group or list of MCPTT groups for the MCPTT user.
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall inform the MCPTT user of unsuccess in binding of a functional alias with the MCPTT group or list of MCPTT groups for the MCPTT user, possibly taking into account Warning header information for the failure reason.
9A.4.2.1.3 Functional alias to group unbinding
Upon receiving a request from an MCPTT user to unbind a functional alias with an MCPTT group or a list of MCPTT groups for the MCPTT user, if the <allow-functional-alias-binding-with-group> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from an MCPTT user to unbind a functional alias with an MCPTT group or a list of MCPTT groups for the MCPTT user, 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.
The MCPTT client:
1) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
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];
3) 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];
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according IETF RFC 3841 [6];
5) 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];
6) 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 <request-type> element set to a value of "fa-group-binding-req";
b) the <binding-ind> element set to a value of "false";
c) the <unbinding-fa-uri> element set to the URI of a functional alias that shall be unbound from the specified list of MCPTT groups in "uri" attributes of <entry> elements of a <list> element of the <resource-lists> element in an application/resource-lists+xml MIME body;
d) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
e) 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;
7) shall include an application/resource-lists+xml MIME body containing a <resource-lists> element containing a <list> element containing one or more <entry> elements each containing a "uri" attribute set to an MCPTT group ID; 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 inform the MCPTT user of success in unbinding the functional alias with the MCPTT group or list of MCPTT groups for the MCPTT user.
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall inform the MCPTT user of unsuccess in unbinding of a functional alias with the MCPTT group or list of MCPTT groups for the MCPTT user, possibly taking into account Warning header information for the failure reason.
9A.4.2.2 Participating MCPTT function procedures
9A.4.2.2.1 General
The participating MCPTT function has procedures to:
- receive a request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user from the MCPTT Client.
9A.4.2.2.2 Receipt of a SIP MESSAGE request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user
Upon receipt of a "SIP MESSAGE request for binding of a functional alias with the MCPTT group(s) for the MCPTT user 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 <request-type> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request is set to a value of "fa-group-binding-req" and:
a) the <allow-functional-alias-binding-with-group> element of the <ruleset> element is not present in the 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 "176 user not authorized to request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user" in a Warning header field, and shall not continue with the rest of the steps in this clause;
b) the SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or the <binding-ind> element and the <binding-fa-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "unable to determine target functional alias or group for creating/removing a binding information for the MCPTT user" in a Warning header field, and shall not continue with the rest of the steps in this clause; and
c) the SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or the <binding-ind> element and the <unbinding-fa-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "177 unable to determine target functional alias or group for creating/removing a binding information for the MCPTT user" in a Warning header field, and shall not continue with the rest of the steps in this clause;
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 for the binding of a functional alias with the MCPTT group(s) for the MCPTT user service associated with the originating user's MCPTT ID identity;
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) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID. If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise it shall not include a <functional-alias-URI> element;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) shall copy the contents of the application/resource-lists+xml MIME body in the received SIP MESSAGE request into an application/resource-lists+xml MIME body in the outgoing SIP MESSAGE request;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
12) 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];
13) 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];
14) 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
15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 15):
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the following 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.
9A.4.2.3 Controlling MCPTT function procedures
9A.4.2.3.1 General
The participating MCPTT function has procedures to:
- receive a request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user from the MCPTT Client.
9A.4.2.3.2 Receipt of a SIP MESSAGE request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user
Upon receiving a:
- "SIP MESSAGE request for binding of a functional alias with the MCPTT group(s) for the MCPTT user 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";
3) the SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or the <binding-ind> element and the <binding-fa-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "177 unable to determine target functional alias or group for creating/removing a binding information for the MCPTT user" in a Warning header field, and shall not continue with the rest of the steps in this clause;
4) the SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or the <binding-ind> element and the <unbinding-fa-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "177 unable to determine target functional alias or group for creating/removing a binding information for the MCPTT user" in a Warning header field, and shall not continue with the rest of the steps in this clause;
5) if any of the <entry> elements of a <list> element of the <resource-lists> element in the application/resource-lists+xml MIME body of the incoming SIP MESSAGE request contains a "uri" attribute set to an MCPTT group ID where the indicated MCPTT group has an existing binding with any other functional alias from same MCPTT user, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "178 MCPTT group binding already exists with other functional alias" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
6) if the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request contains the <request-type> element set to a value of "fa-group-binding-req" and:
a) if the <binding-ind> element is set to a value of "true", shall update or store the record for the MCPTT client, and create a binding information for the functional alias specified in the <binding-fa-uri> element with the list of the MCPTT group(s) included in an application/resource-lists+xml MIME body; or
b) if the <binding-ind> element is set to a value of "false", shall update or store the record for the MCPTT client, and remove a binding information of the functional alias specified in the <unbinding-fa-uri> element from the list of the MCPTT group(s) included in an application/resource-lists+xml MIME body;
7) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the following clarifications:
a) shall include a P-Asserted-Identity header field set to the public service identity of the controlling MCPTT function; and
8) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10 Group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.0 General | This clause describes the group call procedures for on-network and off-network.
For on-network, prearranged group call including emergency group call for each functional entity are specified in clause 10.1.1 and chat group (restricted) call including emergency group call for each functional entity are specified in clause 10.1.2.
Off-network group call and off-network broadcast group call are specified in clause 10.2 and clause 10.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1 On-network group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1 Prearranged group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.2 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.2.1 On-demand prearranged group call | 10.1.1.2.1.1 Client originating procedures
Upon receiving a request from an MCPTT user to establish an MCPTT prearranged group 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 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 prearranged 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, the MCPTT client shall comply with the procedures in clause 6.2.8.1.9;
3) if the MCPTT user has requested the origination of a broadcast group call, the MCPTT client shall comply with the procedures in clause 6.2.8.2;
4) 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];
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 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;
7) 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];
8) should include the "timer" option tag in the Supported header field;
9) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
10) 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.
11) 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];
12) 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 include the Resource-Priority header field and comply with the procedures in clause 6.2.8.1.2;
13) 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;
14) shall contain in 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 "prearranged";
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;
NOTE 2: The MCPTT client does not include the MCPTT ID of the originating MCPTT user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCPTT function.
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;
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;
NOTE 3: 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 of the present document.
NOTE 4: 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.
NOTE 5: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
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; and
g) if the call request is a result of receiving a remotely initiated call request, shall include the <anyExt> element with the <remotely-initiated-call-request-ind> element set to "true";
15) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1;
16) 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
17) shall send the SIP INVITE request towards the MCPTT server 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;
2A) may notify the answer state to the user (i.e. "Unconfirmed" or "Confirmed") if received in the P-Answer-State header field; and
3) may subscribe to the conference event package as specified in clause 10.1.3.1.
On receiving 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 the SIP INVITE request was sent with <remotely-initiated-call-request-ind> element set to "true", then the MCPTT client:
1) shall invoke the procedures of clause 9.2.1.2 to affiliate the MCPTT user to the targeted MCPTT group;
2) if the procedures of clause 9.2.1.2 were not successful:
A) shall skip the rest of the steps of the present clause;
3) upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]:
A) if the SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-user affiliation information constructed according to clause 9.3.1, shall determine if the per user affiliation information indicates that the MCPTT user is affiliated; and
B) if per user affiliation information in the received SIP NOTIFY request indicates that the MCPTT user is not affiliated to the targeted MCPTT group, shall skip the rest of the steps of the present clause; and
4) shall re-initiate the establishing of the session using the procedure defined in the present clause.
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.1.2.1.2 Client terminating procedures
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 shall follow the procedures for termination of multimedia sessions in the IM CN subsystem as specified in 3GPP TS 24.229 [4] with the clarifications below.
The MCPTT client:
1) may reject the SIP INVITE request if any of the following conditions are met:
a) the 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;
1A) should reject the SIP INVITE and include a warning text set to "196 user participates under another constituent group" if the SIP INVITE is for a temporary group or a group based on a preconfigured group where the MCPTT client is an affiliated member of more than one constituent group and the MCPTT client chooses to accept another SIP INVITE for the same temporary group or regroup based on a preconfigured group received for a different constituent group;
NOTE 1: The MCPTT client learns from the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body to which constituent group the received SIP INVITE is associated
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 2: 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) 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];
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 <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
5) 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";
6) may display to the MCPTT user the MCPTT ID of the inviting MCPTT user;
6A) may display to the MCPTT user the functional alias of the inviting MCPTT user;
6B) if the <remotely-initiated-call-request-ind> element is included in the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request, may indicate to the MCPTT user that the received call request is a result of receiving a remotely initiated call request;
7) shall perform the automatic commencement procedures specified in clause 6.2.3.1.2 if one of the following conditions are met:
a) SIP INVITE request contains an Answer-Mode header field with the value "Auto" and the MCPTT service setting at the invited MCPTT client for answering the call is set to automatic commencement mode; or
b) SIP INVITE request contains an Answer-Mode header field with the value "Auto" and the MCPTT service setting at the invited MCPTT client for answering the call is set to manual commencement mode, yet the invited MCPTT client allows the call to be answered with automatic commencement mode;
8) shall perform the manual commencement procedures specified in clause 6.2.3.2.2 if one of the following conditions are met:
a) SIP INVITE request contains an Answer-Mode header field with the value "Manual" and the MCPTT service setting at the invited MCPTT client for answering the call is to use manual commencement mode; or
b) SIP INVITE request contains an Answer-Mode header field with the value "Manual" and the MCPTT service setting at the invited MCPTT client for answering the call is set to automatic commencement mode, yet the invited MCPTT client allows the call to be answered with manual commencement mode; and
9) when the SIP 200 (OK) response to the SIP INVITE request is sent, may subscribe to the conference event package as specified in clause 10.1.3.1.
10.1.1.2.1.3 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 an MCPTT prearranged 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 this is an unauthorised request for an MCPTT emergency call 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 call to an in-progress imminent peril state and this is an unauthorised request for an MCPTT imminent peril group call 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. 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", 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 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 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.
On receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP re-INVITE request the MCPTT client shall perform the actions specified in clause 6.2.8.1.5.
10.1.1.2.1.4 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 prearranged MCPTT group, the MCPTT client shall generate a SIP re-INVITE request while in an ongoing prearranged group call by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below, otherwise generate a SIP MESSAGE request by following client procedure of clause 12.1.1.5 of present document.
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 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 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 "prearranged"; 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 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;
NOTE 2: The SIP re-INVITE request can be sent within an on-demand session or a pre-established session. 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 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];
2) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency";
3) shall set the MCPTT emergency group call state of the group to "MEGC 1: emergency-gc-capable"; and
4) 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 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.
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.
10.1.1.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 prearranged MCPTT group, the MCPTT client shall generate a SIP re-INVITE request while in an ongoing prearranged group call by following the procedures specified in 3GPP TS 24.229 [4], with the clarifications given below, otherwise generate a SIP MESSAGE request by following client procedure of clause 10.1.6.2.1 of present document.
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; and
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 "prearranged"; 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. 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, 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 3: This is the case where the MCPTT client requested the cancellation of the MCPTT imminent peril in-progress state and was rejected.
10.1.1.2.1.6 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) 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];
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;
NOTE: The SIP re-INVITE request can be received within an on-demand session or a pre-established session. 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]; and
12) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.2.2 Prearranged group call using pre-established session | 10.1.1.2.2.1 Client originating procedures
Upon receiving a request from an MCPTT user to establish an MCPTT group session using an MCPTT group identity identifying a prearranged 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 shall follow the procedures specified in clause 10.1.2.2.2.1 with the clarification in step 3) of clause 10.1.2.2.2.1 that:
1) an <entry> element of a <list> element of the <resource-lists> element in the application/resource-lists+xml MIME body shall contain a "uri" attribute set to the prearranged MCPTT group identity;
2) the <session-type> element of the application/vnd.3gpp.mcptt-info MIME body in the hname "body" parameter in the headers portion of the SIP URI shall be set to a value of "prearranged"; and
3) if the MCPTT user has requested the origination of a broadcast group call, the MCPTT client shall comply with the procedures in clause 6.2.8.2.
NOTE: The MCPTT user re-initiate session after affiliating to the target MCPTT group if the session established failed due to user not affiliated to the target MCPTT group and the SIP REFER request was sent with <remotely-initiated-call-request-ind> element set to "true".
10.1.1.2.2.2 Client terminating procedures
Upon receiving a SIP re-INVITE request within a pre-established session without an associated MCPTT call or when generating SIP responses to the SIP re-INVITE request, the MCPTT client shall follow the procedures in clause 10.1.1.2.1.2.
NOTE: In clause 10.1.1.2.1.2, the reader is assumed to replace occurrences of SIP INVITE request with SIP re-INVITE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.2.3 End group call | 10.1.1.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.1.2.3.2 Client originating procedures using pre-established session
When an MCPTT client wants to leave the MCPTT call 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.1.2.3.3 Client terminating procedures
Upon receiving a SIP BYE request for releasing the prearranged MCPTT group call, 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.1.2.4 Rejoin procedure | 10.1.1.2.4.1 On demand session establishment
Upon receiving a request from an MCPTT user to rejoin an ongoing MCPTT session or triggered by coming back from out of coverage, 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.
NOTE: How an MCPTT client is informed whether it comes back from out of coverage is out of scope of present document.
The MCPTT client shall follow the procedures specified in clause 10.1.1.2.1.1 with the clarification in step 10) of clause 10.1.1.2.1.1 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity to rejoin.
10.1.1.2.4.2 Pre-established session
Upon receiving a request from an MCPTT user to rejoin an ongoing MCPTT call within the pre-established session or triggered by coming back from out of coverage, the MCPTT client shall generate a SIP REFER request 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 shall follow the procedures specified in clause 10.1.1.2.2.1 with the clarification in step 3) of clause 10.1.2.2.2.1 that the Refer-To header field of the SIP REFER request:
1) shall contain a URI of the MCPTT session identity to rejoin; and
2) shall contain a Content-Type header field in the headers portion of the SIP URI containing an application/vnd.3gpp.mcptt-info+xml MIME type of the hname "body" parameter in the headers portion of the SIP URI and the hname "body" parameter in the headers portion of the SIP URI containing the <mcpttinfo> element with the <mcptt-Params> element and with the <session-type> element set to a value of "prearranged". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.1 Originating procedures | 10.1.1.3.1.1 On demand prearranged group call
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" 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:
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 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 participating MCPTT function, the user identified by the MCPTT ID is not authorised to initiate prearranged 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 "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4;
4) shall validate the media parameters and if the MCPTT speech codec is not offered in the SIP INVITE request shall 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 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. 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) shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation;
a) 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 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1; or
b) if the received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <remotely-initiated-call-request-ind> element set to a value of "true";
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 8;
4) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request:
a) Answer-Mode header field as specified in IETF RFC 5373 [18]; and
b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [18];
5) shall set the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user;
6) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCPTT client as specified in clause 6.3.2.1.1.1;
6a) 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.
7) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3 and 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;
8) 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 3GPP TS 24.229 [4] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCPTT client;
NOTE 12: The participating MCPTT function will leave verification of the Resource-Priority header field to the controlling MCPTT function.
9) 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 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
10) 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 in response to the above SIP INVITE request, the participating MCPTT function:
1) void;
2) shall generate a SIP 200 (OK) response as in 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 13: 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;
6A) shall include the answer state into the P-Answer-State header field of the outgoing SIP 200 (OK) response, if received in the P-Answer-State header field of the incoming 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 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 this procedure, shall perform the procedures of clause 9.2.2.2.14.
10.1.1.3.1.2 Prearranged group call using pre-established session
Upon receipt of a "SIP REFER request for a pre-established session", with:
1) the Refer-To header field 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 an <entry> element with a "uri" attribute containing a SIP URI set to a pre-arranged 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 "prearranged"; 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.4, and 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 initiate prearranged group calls, shall reject the "SIP REFER request for pre-established session" with a SIP 403 (Forbidden) response to the SIP REFER request, with warning text set to "109 user not authorised to make prearranged group calls" in a Warning header field as specified in clause 4.4;
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 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.
6) if the "SIP REFER request for a pre-established session" contained a Refer-Sub header field containing "false" value and a Supported header field containing "norefersub" value, shall handle the SIP REFER request as specified in 3GPP TS 24.229 [4], IETF RFC 3515 [25] as updated by IETF RFC 6665 [26], and IETF RFC 4488 [22] without establishing an implicit subscription;
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) shall retrieve the group identity within the "uri" attribute of the <entry> element of a <list> element of 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;
10) shall determine the public service identity of the controlling MCPTT function associated with the group identity within the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element in the application/resource-lists+xml MIME body referenced by the Refer-To header 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 any of the remaining steps;
NOTE 4: The public service identity can identify the controlling function in the primary MCPTT system or a part in ner MCPTT system.
NOTE 5: 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 6: 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 7: 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 8: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
11) shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation;
a) if the user identified by the MCPTT ID is not affiliated to the group identified in the SIP REFER request as determined by clause 9.2.2.2.11 and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.1; or
b) if the received SIP REFER request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <remotely-initiated-call-request-ind> element set to a value of "true";
12) if the actions for implicit affiliation specified in step 11) 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 9: 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 10: 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.
13) 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];
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.
14) shall send the response to the "SIP REFER request for a pre-established session" towards the MCPTT client according to 3GPP TS 24.229 [4];
15) shall generate a SIP INVITE request as specified in clause 6.3.2.1.4;
16) shall set the Request-URI of the SIP INVITE request to the public service identity determined in step 10;
17) shall copy the group identity from the "uri" attribute of the <entry> element of a <list> element of 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;
18) if the received SIP REFER request contained a Resource-Priority header field, shall include in the outgoing SIP INVITE request 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;
NOTE 12: The participating MCPTT function will leave verification of the Resource-Priority header field to the controlling MCPTT function.
18a) 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
19) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receiving SIP provisional responses for the SIP INVITE request the participating MCPTT function:
1) shall discard the received SIP responses without forwarding them.
Upon receipt of a SIP 302 (Moved Temporarily) response to the SIP INVITE request the participating MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.2.1.10;
2) 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 a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field in the incoming SIP REFER request from the MCPTT client; and
3) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the participating MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13; and
3) 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 towards the MCPTT client according to 3GPP TS 24.229 [4].
NOTE 13: 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 14: 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 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 in step 19) the participating MCPTT function:
1) 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; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
10.1.1.3.1.3 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 an MCPTT session identifying an on-demand prearranged MCPTT group session or pre-established session, 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 re-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] 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 participating MCPTT function can 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 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.
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;
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) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
3) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response;
4) 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;
5) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4]; and
6) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
Upon receipt of a SIP 403 (Forbidden) response to the above SIP INVITE request in step 7) 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;
4) shall forward the SIP 403 (Forbidden) response to the MCPTT client according to 3GPP TS 24.229 [4]; and
5) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.2 Terminating Procedures | 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.
This clause covers both on-demand session and pre-established sessions.
Upon receipt of a "SIP INVITE request 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 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], and shall not 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", the terminating participating MCPTT function can according to local policy 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, and shall not continue with the rest of the steps;
3) if the Answer-Mode Indication in the application/poc-settings+xml MIME body has not yet been received from the invited MCPTT client as defined in clause 7.3.3 or clause 7.3.4, shall reject the request with a SIP 480 (Temporarily Unavailable) response with the warning text set to "146 T-PF unable to determine the service settings for the called user" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
4) 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 INVITE request to retrieve the binding between the MCPTT ID and public user identity;
5) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
6) 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.
7) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [18] if the "SIP INVITE request for terminating participating MCPTT function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as per clause 7.3.3 or clause 7.3.4 is set to "auto-answer"; and
8) shall perform the manual commencement procedures specified in clause 6.3.2.2.6.1 and according to IETF RFC 5373 [18] if the "SIP INVITE request for terminating participating MCPTT function" does not contain an Answer-Mode header field and the Answer-Mode Indication received in the application/poc-settings+xml MIME body received from the invited MCPTT client as per clause 7.3.3 or clause 7.3.4 is set to "manual-answer". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 10.1.1.3.3 End group call at the originating participating MCPTT function | 10.1.1.3.3.1 Receipt of SIP BYE request for ending group call on-demand
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.
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.3.2 Receipt of SIP REFER "BYE" request for ending group call using pre-established session
Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.