hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.6 Sending a SIP re-INVITE request for MCPTT emergency group call | This clause is referenced from other procedures.
The controlling MCPTT function shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4].
The controlling MCPTT function:
1) shall include an SDP offer with the media parameters as currently established with the terminating MCPTT client according to 3GPP TS 24.229 [4];
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-calling-user-id> element set to the MCPTT ID of the initiating MCPTT user;
3) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCPTT function:
a) shall include a Resource-Priority header field with the namespace populated with the values for an MCPTT emergency group call as specified in clause 6.3.3.1.19;
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body the <emergency-ind> element set to a value of "true";
c) if the <alert-ind> element is set to "true" in the received SIP re-INVITE request and MCPTT emergency alerts are authorised for this group and MCPTT user as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcptt-info+xml MIME body and application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body; and
d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <imminentperil-ind> element set to a value of "false"; and
NOTE: If the imminent peril state of the group is true at this point, the controlling function will be setting it to false as part of the calling procedure. This is in effect an upgrade of an MCPTT imminent peril group call to an MCPTT emergency group call.
4) if the in-progress emergency group state of the group is set to a value of "false":
a) shall include a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.3.3.1.19; and
b) if the received SIP re-INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and this is an authorised request to cancel an MCPTT emergency group call as determined by the procedures of clause 6.3.3.1.13.4:
i) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false"; and
ii) if the received SIP re-INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false" and this is an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.3.3.1.15, shall:
A) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "false"; and
B) if the received SIP request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, copy the contents of the received <originated-by> element to an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP re-INVITE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.7 Sending a SIP INVITE request for MCPTT emergency group call | This clause is referenced from other procedures.
This clause describes the procedures for inviting an MCPTT user to an MCPTT session associated with an MCPTT emergency group call or MCPTT imminent peril group call. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 10.1.2.4.1.1.
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated with the MCPTT ID of the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element populated as follows:
a) the <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user;
b) the <mcptt-calling-user-id> element set to the value of the MCPTT ID of the calling MCPTT user; and
c) the <mcptt-calling-group-id> element set to the value of the MCPTT group ID of the emergency group call.
4) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCPTT function;
5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1; and
6) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCPTT function:
a) shall include a Resource-Priority header field populated with the values for an MCPTT emergency group call as specified in clause 6.3.3.1.19;
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <emergency-ind> element set to a value of "true";
c) if the <alert-ind> element is set to "true" in the received SIP INVITE request and the requesting MCPTT user and MCPTT group are authorised for the initiation of MCPTT emergency alerts as determined by the procedures of clause 6.3.3.1.13.1, shall populate the application/vnd.3gpp.mcptt-info+xml MIME body and the application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause 6.3.3.1.12. Otherwise, shall set the <alert-ind> element to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body; and
d) if the in-progress imminent peril state of the group is set to a value of "true" shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <imminentperil-ind> element set to a value of "false";
NOTE 6: If the imminent peril state of the group is true at this point, the controlling function will set it to false as part of the calling procedure.
7) if the in-progress emergency state of the group is set to a value of "false" and the in-progress imminent peril state of the group is set to a value of "true", the controlling MCPTT function:
a) shall include a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.3.3.1.19; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.8 Sending a SIP UPDATE request for Resource-Priority header field correction | This clause is referenced from other procedures.
This clause describes the procedures for updating an MCPTT session associated with an MCPTT emergency group call or MCPTT imminent peril group call when the received SIP INVITE request did not include a correctly populated Resource-Priority header field. The procedure is initiated by the controlling MCPTT function for the purpose of providing the correct Resource-Priority header field.
1) shall generate a SIP 183 (Session Progress) response according to 3GPP TS 24.229 [4] with the clarifications provided specified in clause 6.3.3.2.3.1;
2) shall include the option tag "100rel" in a Require header field in the SIP 183 (Session Progress) response;
3) shall include in the SIP 183 (Session Progress) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1; and
4) shall send the SIP 183 (Session Progress) response towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP PRACK request to the SIP 183 (Session Progress) response the controlling MCPTT function:
1) shall send the SIP 200 (OK) response to the SIP PRACK request according to 3GPP TS 24.229 [4].
2) shall generate a SIP UPDATE request according to 3GPP TS 24.229 [4] with the following clarifications:
3) shall include in the SIP UPDATE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1;
4) if the in-progress emergency group state of the group is set to a value of "true" the controlling MCPTT function shall include a Resource-Priority header field populated for an MCPTT emergency group call as specified in clause 6.3.3.1.19; and
NOTE 1: This is the case when the sending MCPTT client did not send a Resource-Priority header field populated appropriately to receive emergency-level priority. In this case, the Resource-Priority header field is populated appropriately to provide emergency-level priority.
5) if the in-progress emergency group state of the group is set to a value of "false" the controlling MCPTT function:
a) if the in-progress imminent peril state of the group is set to a value of "false", shall include a Resource-Priority header field populated for a normal priority MCPTT group call as specified in clause 6.3.3.1.19; and
b) if the in-progress imminent peril state of the group is set to a value of "true", shall include a Resource-Priority header field populated for an MCPTT imminent peril group call as specified in clause 6.3.3.1.19.
NOTE 2: This is the case when the sending MCPTT client incorrectly populated a Resource-Priority header field for emergency-level or imminent peril-level priority and the controlling MCPTT function re-populates it as appropriate to an imminent peril level priority or normal priority level. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.9 Generating a SIP re-INVITE request | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP re-INVITE request to be sent by the controlling MCPTT function.
The controlling MCPTT function:
1) shall generate an SIP re-INVITE request according to 3GPP TS 24.229 [4]; and
2) shall include an SDP offer with the media parameters as currently established with the terminating MCPTT client according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.1.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.10 Generating a SIP re-INVITE request to cancel an in-progress emergency | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP re-INVITE request to cancel the in-progress emergency state of an MCPTT group. The procedure is initiated by the controlling MCPTT function when it determines the cancellation of the in-progress emergency state of an MCPTT group is required.
The controlling MCPTT function:
1) shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.1.9;
2) shall include a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.3.3.1.19; and
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.11 Generating a SIP MESSAGE request for notification of in-progress emergency or imminent peril status | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify affiliated but not participating members of an MCPTT group the status of the in-progress emergency state, imminent peril state, emergency alert status of an MCPTT adhoc group or emergency alert status of an MCPTT group. The procedure is initiated by the controlling MCPTT function when there has been a change of state, or to notify of a current outstanding in-progress imminent peril state, in-progress emergency state, emergency alert status of an MCPTT group or the emergency alert status of an MCPTT group.
The controlling MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall set the Request-URI to the public service identity of the terminating participating function associated with the MCPTT ID of the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall include a P-Asserted-Identity header field set to the public service identity of controlling MCPTT function;
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [9];
7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user; and
8) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <mcptt-calling-group-id> element set to the MCPTT group ID of the MCPTT group on which the MCPTT emergency call, imminent peril call or the emergency alert state has changed or already exists. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.12 Populate mcptt-info and location-info MIME bodies for emergency alert | This clause is referenced from other procedures.
This clause describes the procedures for populating the application/vnd.3gpp.mcptt-info+xml and application/vnd.3gpp.mcptt-location-info+xml MIME bodies for an MCPTT emergency alert. The procedure is initiated by the controlling MCPTT function when it has received a SIP request initiating an MCPTT emergency alert, or to notify an outstanding MCPTT emergency alert of the MCPTT user, and generates a message containing the MCPTT emergency alert information required by 3GPP TS 23.379 [3].
The controlling MCPTT function:
1) shall include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <alert-ind> element to a value of "true";
2) shall determine the value of the MCPTT user's Mission Critical Organization from the <MissionCriticalOrganization> element, of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
3) shall include in the <mcpttinfo> element containing the <mcptt-Params> element containing an <mc-org> element set to the value of the MCPTT user's Mission Critical Organization; and
4) if the incoming SIP request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body, shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.13 Authorisations | 6.3.3.1.13.1 Determining authorisation for initiating an MCPTT emergency alert
If the controlling MCPTT function has received a SIP request targeted to an MCPTT group with the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true", the controlling MCPTT function shall check the following conditions:
1) if the <allow-activate-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
a) if the "entry-info" attribute of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and:
i) if the MCPTT group identity targeted for the emergency alert is contained in the <uri-entry> element of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); and
ii) if the <allow-MCPTT-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the <list-service> element of the group document identified by the MCPTT group identity is set to a value of "true" as specified in 3GPP TS 24.481 [31]; or
b) if the "entry-info" attribute of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup" and the <allow-MCPTT-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the <list-service> element of the group document identified by the MCPTT group identity targeted for the emergency alert is set to a value of "true" as specified in 3GPP TS 24.481 [31].
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert targeted to a MCPTT group. In all other cases, the MCPTT emergency alert request shall be considered to be an unauthorised request for an MCPTT emergency alert targeted to an MCPTT group.
If the controlling MCPTT function has received a SIP request targeted to an MCPTT user with the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true", the controlling MCPTT function shall check the following conditions:
1) if the <allow-activate-emergency-alert> element of the <actions> element of the <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
a) if the "entry-info" attribute of the <entry> element of the <PrivateEmergencyAlert> element contained within the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UsePreConfigured" and the MCPTT ID of the MCPTT user targeted for the call is contained in the <uri-entry> element of the <entry> element of the <PrivateEmergencyAlert> element contained within the <OnNetwork> element (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
b) if the "entry-info" attribute of the <entry> element of the <PrivateEmergencyAlert> element contained within the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "LocallyDetermined";
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert targeted to an MCPTT user. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert targeted to an MCPTT user.
6.3.3.1.13.2 Determining authorisation for initiating an MCPTT emergency group or private call
If the controlling MCPTT function has received a SIP request for an MCPTT group call with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" and:
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and:
i) if the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the identity of the MCPTT group targeted by the calling MCPTT user; and
ii) if the <allow-MCPTT-emergency-call> element of the <list-service> element of the group document identified by the targeted MCPTT group identity is set to a value of "true" as specified in 3GPP TS 24.481 [31];
then the controlling MCPTT function shall consider the MCPTT emergency group call request to be an authorised request for an MCPTT emergency group call and skip the remaining steps; or;
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup" and if the <allow-MCPTT-emergency-call> element of the <list-service> element of the group document identified by the targeted MCPTT group identity is set to a value of "true" as specified in 3GPP TS 24.481 [31];
then the controlling MCPTT function shall consider the MCPTT emergency group call request to be an authorised request for an MCPTT emergency group call and skip the remaining steps; or
2) if the controlling MCPTT function does not consider the MCPTT emergency group call request to be an authorised request for an MCPTT emergency group call by step 1) above, then the controlling MCPTT function shall consider the MCPTT emergency group call request to be an unauthorised request for an MCPTT emergency group call.
If the controlling MCPTT function has received a SIP request for an MCPTT private call with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
a) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UsePreConfigured" and if the MCPTT ID targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "LocallyDetermined";
then the controlling MCPTT function shall consider the MCPTT emergency private call request to be an authorised request for an MCPTT emergency private call and skip step 2) below; or
2) if the controlling MCPTT function does not consider the MCPTT emergency private call request to be an authorised request for an MCPTT emergency private call by step 1) above, then the controlling MCPTT function shall consider the MCPTT emergency private call request to be an unauthorised request for an MCPTT emergency private call.
6.3.3.1.13.3 Determining authorisation for cancelling an MCPTT emergency alert
If the controlling MCPTT function has received a SIP request with the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false" and:
1) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request for an MCPTT emergency alert cancellation; and
2) if the <allow-cancel-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", then the MCPTT emergency alert cancellation request shall be considered to be an unauthorised request for an MCPTT emergency alert cancellation.
6.3.3.1.13.4 Determining authorisation for cancelling an MCPTT emergency call
If the controlling MCPTT function has received a SIP request for an MCPTT group call with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false", the controlling MCPTT function determines, based on local policy (e.g if the requester is dispatcher or not, initiator of the MCPTT emergency group call, if other participants exist in the MCPTT session who are in emergency state etc), whether the emergency group state cancel request is authorised or not.
If the controlling MCPTT function has received a SIP request for an MCPTT private call with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false" and:
1) if the <allow-cancel-private-emergency-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency private call cancellation request shall be considered to be an authorised request for an MCPTT emergency private call cancellation; and
2) if the <allow-cancel-private-emergency-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false" or not present, then the MCPTT emergency private call cancellation request shall be considered to be an unauthorised request for an MCPTT emergency private call cancellation.
Editor's Note: [MCProtoc17, CR 0654] Whether the controlling MCPTT function examines the <allow-cancel-private-emergency-call> element or uses local policy to determine whether the calling user is authorised to cancel a private emergency call is FFS.
6.3.3.1.13.5 Determining authorisation for initiating an MCPTT imminent peril call
If the controlling MCPTT function has received a SIP request with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-imminent-peril-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value other than "true" the request for initiating an MCPTT imminent peril call shall be considered to be an unauthorised request for an MCPTT imminent peril call and skip the remaining steps;
2) if the <allow-imminent-peril-call> element of the <list-service> element of the group document identified by the targeted MCPTT group identity is set to a value other than "true" as specified in 3GPP TS 24.481 [31], the request for initiating an MCPTT imminent peril call shall be considered to be an unauthorised request for an MCPTT imminent peril call and skip the remaining steps;
3) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the MCPTT group identity targeted for the call is contained in the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
4) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup".
then the MCPTT imminent peril call request shall be considered to be an authorised request for an MCPTT imminent peril call. In all other cases, it shall be considered to be an unauthorised request for an MCPTT imminent peril call.
6.3.3.1.13.6 Determining authorisation for cancelling an MCPTT imminent peril call
If the controlling MCPTT function has received a SIP request with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false" and:
1) if the <allow-cancel-imminent-peril> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency call cancellation request shall be considered to be an authorised request for an MCPTT imminent peril call cancellation; and
2) if the <allow-cancel-imminent-peril> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false" or not present, then the MCPTT emergency call cancellation request shall be considered to be an unauthorised request for an MCPTT imminent peril call cancellation.
6.3.3.1.13.7 void
6.3.3.1.13.8 Determining authorisation for initiating an MCPTT adhoc group emergency alert
If the controlling MCPTT function has received a SIP request for initiating an MCPTT adhoc group emergency alert with the <adhoc-alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true", the controlling MCPTT function shall check the following conditions:
1) if the <allow-activate-adhoc-group-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; then the MCPTT adhoc group emergency alert request shall be considered to be an authorised request for an MCPTT adhoc group emergency alert targeted to a MCPTT group.
2) if the <allow-activate-adhoc-group-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", or is not present; then the MCPTT adhoc group emergency alert request shall be considered to be an unauthorised request for an MCPTT adhoc group emergency alert targeted to a MCPTT group.
6.3.3.1.13.9 Determining authorisation for cancelling an MCPTT adhoc group emergency alert
If the controlling MCPTT function has received a SIP request with the <adhoc-alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false" and:
1) if the <allow-cancel-adhoc-group-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT adhoc group emergency alert cancellation request shall be considered to be an authorised request for an MCPTT adhoc group emergency alert cancellation; and
2) if the <allow-cancel-adhoc-group-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", or is not present, then the MCPTT adhoc group emergency alert cancellation request shall be considered to be an unauthorised request for an MCPTT adhoc group emergency alert cancellation.
6.3.3.1.13.10 Determining MCPTT users that are authorized for receiving MCPTT adhoc group emergency alert participant information
If the controlling MCPTT function has received a SIP request with the <adhoc-alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-to-recv-adhoc-group-emergency-alert-participants-info> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the handled MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT user shall be considered to be authorised for MCPTT adhoc group emergency alert participant information; and
2) if the <allow-to-recv-adhoc-group-emergency-alert-participants-info> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the handled MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", or is not present, then the MCPTT user shall be considered to be unauthorised for MCPTT adhoc group emergency alert participant information.
6.3.3.1.13.11 Determining authorisation for initiating an MCPTT emergency adhoc group call
If the controlling MCPTT function has received a SIP request for an MCPTT emergency adhoc group call with the <adhoc-emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-emergency-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", shall consider the MCPTT emergency adhoc group call request to be an authorised request for an MCPTT emergency adhoc group call and skip the remaining steps; and
In all other cases, the controlling MCPTT function shall consider the request to originate an MCPTT emergency adhoc group call to be an unauthorised request to originate an MCPTT emergency adhoc group call.
6.3.3.1.13.12 Determining authorisation for initiating an MCPTT imminent peril adhoc group call
If the controlling MCPTT function has received a SIP request with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-imminent-peril-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value "true", shall consider the MCPTT imminent peril adhoc group call request to be authorised request for an MCPTT imminent peril adhoc group call and skip the remaining steps;
In all other cases, the controlling MCPTT function shall consider the request to originate an MCPTT imminent peril adhoc group call to be an unauthorised request to originate an MCPTT imminent peril adhoc group call.
6.3.3.1.13.13 Determining authorisation for cancelling the in-progress imminent peril state of an MCPTT group
If the controlling MCPTT function has received a SIP request for an MCPTT group with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false", the controlling MCPTT function determines, based on local policy (e.g if the requester is dispatcher or not, initiator of the MCPTT imminent peril group call that has set in-progress imminent peril state of a group etc), whether the in-progress imminent peril state of a group cancel request is authorised or not. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.14 Generating a SIP 403 response for priority call request rejection | If the controlling MCPTT function has received a SIP request with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is set to "true" and this is an unauthorised request for an MCPTT emergency call as determined by the procedures of clause 6.3.3.1.13.2, the controlling MCPTT function shall:
1) include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <emergency-ind> element set to a value of "false" and the <alert-ind> element set to a value of "false". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.15 Sending a SIP re-INVITE request for MCPTT imminent peril group call | This clause is referenced from other procedures.
The controlling MCPTT function shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4].
The controlling MCPTT function:
1) shall include in the Contact header field an MCPTT session identity for the MCPTT session with the g.3gpp.mcptt media feature tag and the isfocus media feature tag according to IETF RFC 3840 [16];
2) shall include an SDP offer with the media parameters as currently established with the terminating MCPTT client according to 3GPP TS 24.229 [4];
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-calling-user-id> element set to the MCPTT ID of the initiating MCPTT user;
4) if the in-progress imminent peril state of the group is set to a value of "true" the controlling MCPTT function:
a) shall include a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.3.3.1.19; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <imminentperil-ind> element set to a value of "true"; and
5) if the in-progress imminent peril state of the group is set to a value of "false":
a) shall include a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.3.3.1.19; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <emergency-ind> element set to a value of "false" and the <imminentperil-ind> element set to a value of "false". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.16 Handling the expiry of timer TNG2 (in-progress emergency group call timer) | Upon expiry of timer TNG2 (in-progress emergency group call timer) for an MCPTT group, the controlling MCPTT function:
1) shall set the in-progress emergency state of the group to a value of "false";
2) shall, if an MCPTT group call or MCPTT group session is in progress on the indicated group, for each of the participating members:
a) generate a SIP re-INVITE request as specified in clause 6.3.3.1.10; and
b) send the SIP re-INVITE request towards the MCPTT client according to 3GPP TS 24.229 [4]; and
3) shall for each affiliated but non-participating member of the group:
a) generate a SIP MESSAGE request according to clause 6.3.3.1.11 and include in the application/vnd.3gpp.mcptt-info+xml MIME body an <emergency-ind> element set to a value of "false";
b) shall include in the P-Asserted-Identity header field the public service identity of the controlling MCPTT function;
c) include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [9]; and
d) send the SIP MESSAGE request towards the MCPTT client according to rules and procedures of 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to a re-SIP INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.17 Validate priority request parameters | This clause is referenced from other procedures. This procedure validates the combinations of <emergency-ind>, <imminentperil-ind> and <alert-ind> in the application/vnd.3gpp.mcptt-info+xml MIME body included in:
1) a SIP INVITE request or SIP re-INVITE request; or
2) the body "URI" header field of the SIP URI included in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body which is pointed to by a "cid" URL located in the Refer-To header of a SIP REFER request;
Upon receiving a SIP request as specified above with the <emergency-ind> element set to a value of "true", the controlling MCPTT function shall only consider the following as valid combinations:
1) <imminentperil-ind> not included and <alert-ind> included.
Upon receiving a SIP request as specified above with the <emergency-ind> element set to a value of "false", the controlling MCPTT function shall only consider the following as valid combinations:
1) <imminentperil-ind> not included and <alert-ind> not included; or
2) <imminentperil-ind> not included and <alert-ind> included.
Upon receiving a SIP request as specified above with the <imminentperil-ind> element included the controlling MCPTT function shall only consider the request as valid if both the <emergency-ind> and <alert-ind> are not included.
If the combination of the <emergency-ind>, <imminentperil-ind> or <alert-ind> indicators is invalid, the controlling MCPTT function shall send a SIP 403 (Forbidden) response with the warning text set to "150 invalid combinations of data received in MIME body" in a Warning header field as specified in clause 4.4. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.18 Sending a SIP INFO request in the dialog of a SIP request for a priority call | This clause is referenced from other procedures and describes how the controlling MCPTT function generates a SIP INFO request due to the receipt of a SIP request for a priority call.
The controlling MCPTT function:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [4] and IETF RFC 6086 [64];
2) shall include the Info-Package header field set to g.3gpp.mcptt-info in the SIP INFO request;
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INFO request and:
a) if the received SIP request contained application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1, shall set the <emergency-ind> element to a value of "true" and the <alert-ind> element to a value of "false";
b) if the received SIP request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false" and if this is an unauthorised request for an MCPTT emergency alert cancellation, shall set <alert-ind> element to a value of "true"; and
c) if the received SIP request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true", this is an authorised request for an MCPTT imminent peril group call and the in-progress emergency state of the group is set to a value of "true", shall set the <imminentperil-ind> element to a value of "false" and the <emergency-ind> element set to a value of "true"; and
4) shall send the SIP INFO request towards the inviting MCPTT client in the dialog created by the SIP request from the inviting MCPTT client, as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.19 Retrieving Resource-Priority header field values | This clause is referenced from other procedures.
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT emergency group call or MCPTT emergency private call or MCPTT emergency adhoc group call, the controlling MCPTT function:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT imminent peril group call or MCPTT imminent peril adhoc group call, the controlling MCPTT function:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50])
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for a normal MCPTT group or private call or normal MCPTT adhoc group call, the controlling MCPTT function:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
NOTE: The "normal" Resource-Priority header field value is needed to return to a normal priority value from a priority value adjusted for an MCPTT emergency group or private call or an MCPTT imminent peril group call. The "normal" priority received from the EPS by use of the "normal" Resource-Priority header field value is expected to be the same as the "normal" priority received from the EPS when initiating a call with no Resource-Priority header field included. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.20 Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or emergency cancellation | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify the originator of an emergency alert or emergency cancellation that the request was successfully received.
The controlling MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall set the Request-URI to the public service identity of the terminating participating function associated with the MCPTT ID of the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall include a P-Asserted-Identity header field set to the public service identity of controlling MCPTT function; and
6) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.21 void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.22 void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.23 Populate mcptt-info MIME bodies for adhoc group emergency alert | This clause is referenced from other procedures.
This clause describes the procedures for populating the application/vnd.3gpp.mcptt-info+xml and application/vnd.3gpp.mcptt-location-info+xml MIME bodies for an MCPTT adhoc group emergency alert. The procedure is initiated by the controlling MCPTT function when it has received a SIP request initiating an MCPTT adhoc group emergency alert and generates a message containing the MCPTT adhoc group emergency alert information required by 3GPP TS 23.379 [3].
The controlling MCPTT function:
1) shall include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <adhoc-alert-ind> element to a value of "true";
2) b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the MCPTT ID of the user that has initiated the ongoing adhoc group emergency alert;
3) shall determine the value of the MCPTT user's Mission Critical Organization from the <MissionCriticalOrganization> element, of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
4) shall include in the <mcpttinfo> element containing the <mcptt-Params> element containing an <mc-org> element set to the value of the MCPTT user's Mission Critical Organization; and
5) shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.24 Generating a SIP MESSAGE request to containing the participant lists of an MCPTT adhoc group emergency alert | This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify the authorized users of an MCPTT adhoc group emergency alert with the list of users participating in the MCPTT adhoc group emergency alert.
The controlling MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall set the Request-URI to the public service identity of the terminating participating function associated with the MCPTT ID of the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
a) the <mcptt-request-uri> element set to the value of the MCPTT ID of the targeted MCPTT user;
b) the <mcptt-calling-group-id> element set to the adhoc group identity; and
c) an <anyExt> element containing:
i) the <adhoc-alert-participant-list> containing the total list of MC service users who belong to the ad hoc group irrespective if they have acknowledged the ad hoc group emergency alert or not; and
ii) the <adhoc-alert-participant-not-ack-list> containing the list of MC service users who belong to the ad hoc group but have not acknowledged the ad hoc group emergency alert;
NOTE 6: These lists are populated with data cached clause 12.1A.3.1 and clause 12.1A.3.3.
6) shall include a P-Asserted-Identity header field set to the public service identity of controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.1.25 Validate adhoc group priority request parameters | This clause is referenced from other procedures. This procedure validates the combinations of <adhoc-emergency-ind>, and <imminentperil-ind> in the application/vnd.3gpp.mcptt-info+xml MIME body included in:
1) a SIP INVITE request or SIP re-INVITE request; or
2) the body "URI" header field of the SIP URI included in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body which is pointed to by a "cid" URL located in the Refer-To header of a SIP REFER request;
Upon receiving a SIP request as specified above with the <adhoc-emergency-ind> element set to a value of "true", the controlling MCPTT function shall only consider the <imminentperil-ind> element not included.
Upon receiving a SIP request as specified above with the <adhoc-emergency-ind> element set to a value of "false", the controlling MCPTT function shall only consider the <imminentperil-ind> element not included.
Upon receiving a SIP request as specified above with the <imminentperil-ind> element included the controlling MCPTT function shall only consider the request as valid if the <adhoc-emergency-ind> not included.
If the combination of the <adhoc-emergency-ind>, or <imminentperil-ind> indicators is invalid, the controlling MCPTT function shall send a SIP 403 (Forbidden) response with the warning text set to "150 invalid combinations of data received in MIME body" in a Warning header field as specified in clause 4.4. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.2 Requests terminated by the controlling MCPTT function | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.2.1 SDP answer generation | When composing the SDP answer according to 3GPP TS 24.229 [4], the controlling MCPTT function:
1) for the accepted media stream in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the media distribution function of the controlling MCPTT function; and
Editor’s Note: Text needs to be added for the case of a private call without floor control : the controlling MCPTT function assigns unique RTP SSRCs to be used by each participant and include the SSRC to be used in the sent media stream in an mc-ssrc fmtp attribute and the SSRC to expect in the received media stream in an a=ssrc attribute.
2) for the accepted media plane control channel, if present in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the floor control server of the controlling MCPTT function;
b) shall include an mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14 for the selected media plane control channel with the RTCP SSRC that the controlling MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the offerer in the floor control messages sent to the controlling MCPTT function for this session; and
NOTE: The controlling MCPTT function has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the offerer in this session.
c) shall include any other necessary 'fmtp' attributes a specified in 3GPP TS 24.380 clause 14. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.2.2 Receipt of a SIP INVITE request | On receipt of an initial SIP INVITE request the controlling MCPTT function shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.2.3 Sending a SIP response to a SIP INVITE request | 6.3.3.2.3.1 Provisional response
When sending SIP provisional responses with the exception of the SIP 100 (Trying) response to the SIP INVITE request the controlling MCPTT function:
1) shall generate the SIP provisional response;
2) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCPTT function;
3) shall include an MCPTT session identity in the Contact header field; and
4) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
c) the isfocus media feature tag.
6.3.3.2.3.2 Final response
When sending a SIP 200 (OK) response to the initial SIP INVITE request, the controlling MCPTT function:
1) shall generate the SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of IETF RFC 4028 [7], "UAS Behavior". The "refresher" parameter in the Session-Expires header field shall be set to "uac";
3) shall include the option tag "timer" in a Require header field;
4) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCPTT function;
5) shall include a SIP URI for the MCPTT session identity in the Contact header field identifying the MCPTT session at the controlling MCPTT function;
6) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
c) the isfocus media feature tag;
7) shall include Warning header field(s) received in incoming responses to the SIP INVITE request;
8) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23];
9) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [22];
10) shall include the "explicitsub" and "nosub" option tags in a Supported header field according to IETF RFC 7614 [35]; and
11) void
12) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.2.4 Receiving a SIP BYE request | Upon receiving a SIP BYE request the controlling MCPTT function:
1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.380 [5] for releasing the media plane resource associated with the SIP session towards the MCPTT client;
NOTE: The non-controlling MCPTT function is also regarded as a MCPTT client in a temporary MCPTT group session.
2) shall generate a SIP 200 (OK) response and send the SIP response towards the MCPTT client according to 3GPP TS 24.229 [4];
3) shall check the MCPTT session release policy as specified in clause 6.3.8.1 and clause 6.3.8.2 whether the MCPTT session needs to be released for each participant of the MCPTT session;
4) if release of the MCPTT session is required:
a) shall perform the procedures as specified in the clause 6.3.3.1.5 with the clarification that if the received SIP BYE request contains an application/vnd.3gpp.mcptt-info+xml MIME body, copy the application/vnd.3gpp.mcptt-info+xml MIME body into the outgoing SIP BYE request; and
5) if a release of the MCPTT session is not required, shall send a SIP NOTIFY request to all remaining MCPTT clients in the MCPTT session with a subscription to the conference event package as specified in clause 10.1.3.4.2.
Upon receiving a SIP 200 (OK) response to the SIP BYE request the controlling MCPTT function shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.380 [5] for releasing media plane resources associated with the SIP session with the MCPTT participant. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.3 Handling of the acknowledged call setup timer (TNG1) | When the controlling MCPTT function receives a SIP INVITE request to initiate a group session and there are members of the group document retrieved from the group management server that are affiliated and are marked as <on-network-required> as specified in 3GPP TS 24.481 [31], then the controlling MCPTT function shall start timer TNG1 (acknowledged call setup timer) with a timer value as described in Annex B.2.1, prior to sending out SIP INVITE requests inviting group members to the group session.
When the controlling MCPTT function receives all SIP 200 (OK) responses to the SIP INVITE requests, from all affiliated and <on-network-required> members then the controlling MCPTT function shall stop timer TNG1 (acknowledged call setup timer) and if the local counter of the number of SIP 200 (OK) responses received from invited members is greater than or equal to the value of the <on-network-minimum-number-to-start> element of the group document, the controlling MCPTT function shall send a SIP 200 (OK) response to the initiating MCPTT client.
NOTE 1: MCPTT clients that are affiliated but are not <on-network-required> members that have not yet responded will be considered as joining an ongoing session when the controlling MCPTT function receives SIP 200 (OK) responses from these MCPTT clients.
After expiry of timer TNG1 (acknowledged call setup timer) and the local counter of the number of SIP 200 (OK) responses received from invited members is less than the value of the <on-network-minimum-number-to-start> element of the group document, then the controlling MCPTT function shall wait until further responses have been received from invited clients and the value of the local counter of the number of SIP 200 (OK) responses received from invited members is equal to the <on-network-minimum-number-to-start>, before continuing with the timer TNG1 expiry procedures in this clause.
After expiry of timer TNG1 (acknowledged call setup timer) and the local counter of the number of SIP 200 (OK) responses received from invited members is greater or equal to the value of the <on-network-minimum-number-to-start> element of the group document, the controlling MCPTT function shall execute the steps described below:
1) if the <on-network-action-upon-expiration-of-timeout-for-acknowledgement-of-required-members> element configured in the group document for the action on expiry of the timer is set to "proceed" indicating that the controlling MCPTT function should proceed with the setup of the group call, then the controlling MCPTT function:
a) shall perform the following actions:
i) generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2 before continuing with the rest of the steps;
ii) include in the SIP 200 (OK) response the warning text set to "111 group call proceeded without all required group members" in a Warning header field as specified in clause 4.4;
iii) include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
iv) interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 2: Resulting media plane processing is completed before the next step is performed.
v) send a SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4];
b) when a SIP 200 (OK) response to a SIP INVITE request is received from an invited MCPTT client the controlling MCPTT function may send an in-dialog SIP MESSAGE request to the MCPTT client that originated the group session with the text "group call proceeded without all required group members";
c) when the controlling MCPTT function receives a SIP BYE request from an invited MCPTT client, shall take the actions specified in clause 6.3.3.2.4 and may send an in-dialog SIP MESSAGE request to the MCPTT client that originated the group session with the text "group call proceeded without all required group members"; and
d) shall generate a notification package as specified in clause 6.3.3.4 and send a SIP NOTIFY request according to 3GPP TS 24.229 [4] to the MCPTT clients which have subscribed to the conference event package; and
2) if the <on-network-action-upon-expiration-of-timeout-for-acknowledgement-of-required-members> element configured in the group document for the action on expiry of the timer is set to "abandon" indicating that the controlling MCPTT function should abandon the setup of the group call, then the controlling MCPTT function shall:
a) send a SIP 480 (Temporarily Unavailable) response to the MCPTT client that originated the group session with the warning text set to "112 group call abandoned due to required group members not part of the group session" in a Warning header field as specified in clause 4.4;
b) for each confirmed dialog at the controlling MCPTT function, send a SIP BYE request towards the MCPTT clients invited to the group session in accordance with 3GPP TS 24.229 [4] and interact with the media plane as specified in 3GPP TS 24.380 [5]; and
c) for each non-confirmed dialog at the controlling MCPTT function, send a SIP CANCEL request towards the MCPTT clients invited to the group session in accordance with 3GPP TS 24.229 [4].
If the controlling MCPTT function receives a final SIP 4xx, 5xx or 6xx response from an affiliated and <on-network-required> group member prior to expiry of timer TNG1 (acknowledged call setup timer) and based on policy, the controlling MCPTT function decides not to continue with the establishment of the group call without the affiliated and <on-network-required> group member, then the controlling MCPTT function:
NOTE 3: It is expected that this action is taken if the policy is to abandon the call on expiry of timer TNG1 (acknowledged call setup timer).
1) shall stop timer TNG1 (acknowledged call setup timer); and
2) shall forward the final SIP 4xx, 5xx or 6xx response towards the inviting MCPTT client with the warning text set to "112 group call abandoned due to required group member not part of the group session" in a Warning header field as specified in clause 4.4.
If:
1) the controlling MCPTT function receives a final SIP 4xx, 5xx or 6xx response from an affiliated and <on-network-required> group member prior to expiry of timer TNG1 (acknowledged call setup timer);
2) the local counter of the number of SIP 200 (OK) responses received from invited members is greater than or equal to the value of the <on-network-minimum-number-to-start> element of the group document; and
3) based on policy, the controlling MCPTT function decides to continue with the establishment of the group call without the affiliated and <on-network-required> group member;
then the controlling MCPTT function:
NOTE 4: It is expected that this action is taken if the policy is to proceed with the call on expiry of timer TNG1 (acknowledged call setup timer).
1) if all other invited clients have not yet responded, shall continue running timer TNG1 (acknowledged call setup timer); and
2) if all other invited clients have responded with SIP 200 (OK) responses, shall
a) stop timer TNG1 (acknowledged call setup timer);
b) generate SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.2 before continuing with the rest of the steps;
c) include in the SIP 200 (OK) response the warning text set to "111 group call proceeded without all required group members" in a Warning header field as specified in clause 4.4;
d) include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
e) interact with the media plane as specified in 3GPP TS 24.380 [5]; and
NOTE 5: Resulting media plane processing is completed before the next step is performed.
f) send a SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP ACK to the above SIP 200 (OK) response and
1) the SIP 200 (OK) response contained the warning text set to "111 group call proceeded without all required group members" in a Warning header field and
2) the user profile of MCPTT client that originated the group session contains the element <allow-to-receive-non-acknowledged-users-information> and is set to a value of "true",
then the controlling MCPTT function may:
1) generate a SIP INFO request according to rules and procedures of 3GPP TS 24229 [4] and IETF RFC 6086 [64];
2) include the Info-Package header field set to g.3gpp.mcptt-info in the SIP INFO request;
3) include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with a <non-acknowledged-user> element containing the MCPTT ID of each of the invited members that have not sent a SIP 200 (OK) response; and
4) send the SIP INFO request towards the inviting MCPTT client in the dialog created by the SIP request from the inviting MCPTT client, as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.4 Generating a SIP NOTIFY request | The controlling MCPTT function shall generate a SIP NOTIFY request according to 3GPP TS 24.229 [4] with the clarification in this clause.
In the SIP NOTIFY request, the controlling MCPTT function:
1) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCPTT function;
2) shall include an Event header field set to "conference";
3) shall include an Expires header field set to 3600 seconds according to IETF RFC 4575 [30], as default value;
4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9]; and
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-calling-group-id> set to the value of the MCPTT group ID;
b) if the target is a MCPTT user, the value of <mcptt-request-uri> element set to the value of MCPTT ID of the targeted MCPTT user; and
c) if the target is the non-controlling MCPTT function, the value of <mcptt-request-uri> element set to the constituent MCPTT group ID.
In the SIP NOTIFY request, the controlling MCPTT function shall include an application/conference-info+xml MIME body according to IETF RFC 4575 [30] with the following limitations:
1) the controlling MCPTT function shall include the MCPTT group ID of the MCPTT group in the "entity" attribute of the <conference-info> element;
2) for each participant in the MCPTT session with the exception of non-controlling MCPTT functions, the controlling MCPTT function shall include a <user> element. The <user> element shall:
NOTE: Non-controlling MCPTT functions will appear as a participant in temporary group sessions.
a) include the "entity" attribute. The "entity" attribute:
i) shall for the MCPTT client, which initiated, joined or rejoined an MCPTT session, include the MCPTT ID of the MCPTT user which originates SIP INVITE request; and
ii) shall for an invited MCPTT client include the MCPTT ID of the invited MCPTT user in case of a prearranged group call or chat group call;
b) shall include a single <endpoint> element. The <endpoint> element:
i) shall include the "entity" attribute;
ii) shall include the <status> element indicating the status of the MCPTT session according to IETF RFC 4575 [30]; and
iii) may include one <functional-alias> element indicating the functional alias bound by the MCPTT user with the MCPTT group for which the notification is being sent as defined in the XML schema of clause 10.1.3.6.1; and
NOTE 1: The functional alias binding by the MCPTT user with the MCPTT group is done through either using an explicit procedure or as a part of call setup procedure.
c) may include <roles> element.
NOTE 2: The usage of <roles> is only applicable for human consumption. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.5 Handling of the group call timer (TNG3) | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.5.1 General | When the controlling MCPTT function receives a SIP INVITE request to initiate a group session, then after an MCPTT session identity has been allocated for the group session and if the <on-network-maximum-duration> element is present in the group document as specified in 3GPP TS 24.481 [31], the controlling MCPTT function: shall start timer TNG3 (group call timer) with the value obtained from the <on-network-maximum-duration> element of the group document as specified in 3GPP TS 24.481 [31].
If the <on-network-maximum-duration> element is not present in the group document as specified in 3GPP TS 24.481 [31], then the controlling MCPTT function shall not start timer TNG3 (group call timer).
NOTE 1: The configuration of <on-network-maximum-duration> element in 3GPP TS 24.481 [31] is mandated for a pre-arranged group and is optional for a chat group.
When merging two or more active group calls into a temporary group call, the controlling MCPTT function(s) hosting the active group calls shall stop timer TNG3 (group call timer) for each group call, and the controlling MCPTT function hosting the temporary group call shall start timer TNG3 (group call timer) for the temporary group call.
NOTE 2: If the MCPTT server(s) hosting the independent active group calls are different to the MCPTT server that will host the temporary group call, then the MCPTT server(s) hosting the independent active group calls become non-controlling MCPTT function(s) of an MCPTT group, for the temporary group call.
When splitting a temporary group call into independent group calls, the controlling MCPTT function hosting the temporary group call shall stop timer TNG3 (group call timer) and the controlling MCPTT function(s) hosting the independent group calls shall start TNG3 (group call timer) for each group call.
When the last MCPTT client leaves the MCPTT session, the controlling MCPTT function shall stop timer TNG3 (group call timer).
On expiry of timer (group call timer), the controlling MCPTT function shall release the MCPTT session by following the procedures in clause 6.3.3.1.5; |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.5.2 Interaction with the in-progress emergency group call timer (TNG2) | If the controlling MCPTT function starts timer TNG2 (in-progress emergency group call timer), it shall not start timer TNG3 (group call timer).
If timer TNG3 (group call timer) is running and the MCPTT group call is upgraded to an MCPTT emergency group call, then the controlling MCPTT function shall stop timer TNG3 (group call timer) and shall start timer TNG2 (in-progress emergency group call timer) with the value obtained from the <group-time-limit> element of the <emergency-call> element of the <on-network> element of the service configuration document as specified in 3GPP TS 24.484 [50].If timer TNG2 (in-progress emergency group call timer) is running and the MCPTT emergency group call is cancelled, then the controlling MCPTT function shall stop timer TNG2 (in-progress emergency group call timer) and shall start timer TNG3 (group call timer) with the value obtained from the <on-network-maximum-duration> element of the group document as specified in 3GPP TS 24.481 [31].
If timer TNG2 (in-progress emergency group call timer) is running and subsequently expires, then the controlling MCPTT function shall start timer TNG3 (group call timer) with the value obtained from the <on-network-maximum-duration> element of the group document as specified in 3GPP TS 24.481 [31].
NOTE: The above conditions for starting timer TNG2 (in-progress emergency group call timer) and timer TNG3 (group call timer) also apply in the case that these timers are re-started. For example: the case where the timer TNG3 was initially running, the MCPTT group call is upgraded to an MCPTT emergency group call and then the MCPTT emergency group call is cancelled. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.3.6 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4 Non-controlling MCPTT function of an MCPTT group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.1 Request initiated by the non-controlling MCPTT function of an MCPTT group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.1.1 SDP offer generation | The SDP offer is generated based on the received SDP offer. The SDP offer generated by the non-controlling MCPTT function of an MCPTT group:
1) shall include only one SDP media-level section for MCPTT speech as contained in the received SDP offer; and
2) shall include one SDP media-level section for media plane control messages, if present in the received SDP offer.
When composing the SDP offer according to 3GPP TS 24.229 [4], the non-controlling MCPTT function of an MCPTT group:
1) shall replace the IP address and port number for the offered media stream in the received SDP offer with the IP address and port number of the non-controlling MCPTT function;
2) shall include all media-level attributes from the received SDP offer;
3) shall replace the IP address and port number for the offered media plane control channel, if any, in the received SDP offer with the IP address and port number of the non-controlling MCPTT function; and
4) shall replace the mc_floor_ssrc 'fmtp' attribute for the offered media plane control channel, if any, in the received SDP offer with the RTCP SSRC that the non-controlling MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the answerer in the floor control messages sent to the non-controlling MCPTT function for this session; and
NOTE: The non-controlling MCPTT function will receive in the SDP answer the RTP SSRC it will have to use in the floor control message it will send to the answerer in this session.
5) shall include any other necessary 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.1.2 Sending an INVITE request towards the MCPTT client | This clause is referenced from other procedures.
The non-controlling MCPTT function of an MCPTT group shall generate initial SIP INVITE requests according to 3GPP TS 24.229 [4].
For each SIP INVITE request, the non-controlling MCPTT function of an MCPTT group:
1) shall generate a new MCPTT session identity for the MCPTT session with the invited MCPTT client and include it in the Contact header field together with the g.3gpp.mcptt media feature tag, the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt", and the isfocus media feature tag according to IETF RFC 3840 [16];
2) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [9] in the SIP INVITE request;
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
5) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT ID of the MCPTT user to be invited;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the non-controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the MCPTT ID of the MCPTT user to be invited or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall copy the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request to the outgoing SIP INVITE request;
6a) shall update the application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-calling-group-id> element set to the TGI or to the identity of the group regroup based on a preconfigured group;
6b) shall update the application/vnd.3gpp.mcptt-info+xml MIME body with an <associated-group-id> element set to the identity of the constituent group;
7) shall update the application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element set to the MCPTT ID of the invited MCPTT user;
8) shall include the public service identity of the non-controlling MCPTT function in the P-Asserted-Identity header field;
9) void;
10) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7]. The refresher parameter shall be omitted;
11) shall include the Supported header field set to "timer";
12) void.
13) shall include an unmodified Answer-Mode header field, if present in the incoming SIP INVITE request;and
14) void. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.1.3 Sending a SIP INFO request | This clause is referenced from other procedures.
The non-controlling MCPTT function shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [4] and IETF RFC 6086 [64].
The non-controlling MCPTT function:
1) shall include the Info-Package header field set to g.3gpp.mcptt-floor-request;
2) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> set to the temporary MCPTT group ID and the <mcptt-calling-group-id> element with the constituent MCPTT group ID;
3) shall include an application/vnd.3gpp.mcptt-floor-request+xml MIME body with the Content-Disposition header field set to "Info-Package". For each current speaker the application/vnd.3gpp.mcptt-floor-request+xml MIME body shall be populated as follows:
a) the <floor-type> element set to "general" or "dual" as described in clause F.5.3;
b) the SSRC of the MCPTT client with the permission to send media in the <ssrc> element;
c) the actual floor priority in the <floor-priority> element;
d) the MCPTT ID of the MCPTT user with the permission to send media in the <user-id> element;
e) the queueing capability in the <queueing-capability> element of the <track-info> element;
f) the participant type in the <participant-type> in the <track-info> element;
g) one or more <floor-participant-reference> elements in the <track-info> element in the same order as the would appear in the Track Info field as specified in 3GPP TS 24.380 [5] clause 8.2.3.13; and
h) if available, additional information in the <floor-indicator> element; and
4) if:
a) the non-controlling MCPTT function has location information (see clause 13.2.4) for the MCPTT client; and
b) the location information for the MCPTT client either has not been sent to the controlling MCPTT function or has changed since last sent to the MCPTT controlling function; and
c) 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. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.1.4 Sending an INVITE request towards the controlling MCPTT function | This clause is referenced from other procedures.
The non-controlling MCPTT function shall generate a SIP INVITE request according to rules and procedures of 3GPP TS 24.229 [4].
The non-controlling MCPTT function:
1) shall include in the Contact header field the g.3gpp.mcptt media feature tag, the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt", and the isfocus media feature tag according to IETF RFC 3840 [16];
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-Asserted-Service-Id header field according to IETF RFC 6050 [9] in the SIP INVITE request;
3) shall set the Request-URI to the public service identity of the controlling MCPTT function based on the <mcptt-request-uri> element received in the "SIP INVITE request from participating MCPT function for non-controlling MCPTT function of an MCPTT group";
NOTE 1: The public service identity can identify the controlling MCPTT function in the local MCPTT system or in an interconnected MCPTT system.
NOTE 2: If the controlling MCPTT function is in an interconnected MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the interconnected MCPTT system from the local MCPTT system.
NOTE 3: If the controlling MCPTT function is in an interconnected MCPTT system in a different trust domain, then the local MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the local MCPTT system to the interconnected MCPTT system
NOTE 4: How the non-controlling MCPTT function determines the public service identity of the controlling MCPTT function based on the <mcptt-request-uri> element received in the "SIP INVITE request from participating MCPTT function for non-controlling MCPTT function of an MCPTT group" or of the MCPTT gateway server in the interconnected MCPTT system is out of the scope of the present document.
NOTE 5: How the local MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <session-type> element set to "prearranged" or "chat" depending on the type of the group identified by the TGI or of the group regroup based on a preconfigured group;
b) the <mcptt-request-uri> element set to the TGI or to the identity of the group regroup based on a preconfigured group received in the <mcptt-request-uri> element of the received SIP INVITE;
c) the <mcptt-calling-group-id> element set to the identity of the constituent group received in the <associated-group-id> element of the received SIP INVITE;
d) the <mcptt-calling-user-id> element set to the identity of the calling user received in the <mcptt-calling-user-id> element of the received SIP INVITE; and
e) the <required> element set to "true", if the group document retrieved from the group management server contains <on-network-required> group members as specified in 3GPP TS 24.481 [31];
5) shall include the public service identity of the non-controlling MCPTT function in the P-Asserted-Identity header field;
6) should include the Session-Expires header field according to rules and procedures of IETF RFC 4028 [7]. The refresher parameter shall be omitted; and
7) shall include the Supported header field set to "timer". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.2 Requests terminated by the non-controlling MCPTT function of an MCPTT group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.2.1 SDP answer generation | When composing the SDP answer according to 3GPP TS 24.229 [4], the non-controlling MCPTT function of an MCPTT group:
1) for the accepted media stream in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the non-controlling MCPTT function; and
2) for the accepted media plane control channel, if present in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the non-controlling MCPTT function; and
b) shall replace the mc_floor_ssrc 'fmtp' attribute in the received SDP offer with the RTCP SSRC that the non-controlling MCPTT function has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the offerer in the floor control messages sent to the non-controlling MCPTT function for this session; and
NOTE: The non-controlling MCPTT function has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the offerer in this session.
c) shall include any other necessary 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.2.2 Sending a SIP response to the SIP INVITE request | 6.3.4.2.2.1 Sending a SIP 183 (Session Progress) response
When sending a SIP 183 (Session Progress) the non-controlling MCPTT function of an MCPTT group:
1) shall generate a SIP 183 (Session Progress) response according to 3GPP TS 24.229 [4];
2) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag; and
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) shall include the public service identity of the non-controlling MCPTT function in the P-Asserted-Identity header field; and
4) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23];
6.3.4.2.2.2 Sending a SIP 200 (OK) response
When sending a SIP 200 (OK) response, the non-controlling MCPTT function of an MCPTT group:
1) shall generate the SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of IETF RFC 4028 [7], "UAS Behavior". The "refresher" parameter in the Session-Expires header field shall be set to "uac";
3) shall include the option tag "timer" in a Require header field;
4) shall include the public service identity of the non-controlling MCPTT function in the P-Asserted-Identity header field;
5) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag; and
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
6) if allowed by local policy and if Warning header field(s) were received in incoming responses to SIP INVITE requests that were sent as a result of following the procedures of clause 6.3.4.1.2, shall include those Warning header field(s);
7) shall include the option tag "tdialog" in a Supported header field according to rules and procedures of IETF RFC 4538 [23]; and
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-called-party-id> element set to the constituent MCPTT group ID and the <floor-state> element set to the state of the floor. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.3 Generating a SIP NOTIFY request | The non-controlling MCPTT function shall generate a SIP NOTIFY request according to 3GPP TS 24.229 [4] with the clarification in this clause.
In the SIP NOTIFY request, the non-controlling MCPTT function:
1) shall set the P-Asserted-Identity header field to the public service identity of the non-controlling MCPTT function;
2) shall include an Event header field set to "conference";
3) shall include an Expires header field set to 3600 seconds according to IETF RFC 4575 [30], as default value;
4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9]; and
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-calling-group-id> set to the value of the constituent MCPTT group ID;
b) if the target is a MCPTT user, the value of <mcptt-request-uri> element set to the MCPTT ID of the targeted MCPTT user; and
c) if the target is the controlling MCPTT function the value of <mcptt-request-uri> element set to the temporary MCPTT group ID.
In the SIP NOTIFY request, the non-controlling MCPTT function shall include application/conference-info+xml MIME body according to IETF RFC 4575 [30] as specified in clause 6.3.3.4 with the following exceptions:
1) the non-controlling MCPTT function shall not regard the controlling MCPTT function as a participant and not include the controlling MCPTT function in a <user> element; and
NOTE: The controlling MCPTT function initiated the temporary group call and will appear as a participant in the group session.
2) the non-controlling MCPTT function shall include stored conference status information received in SIP NOTIFY requests from the controlling MCPTT function in clause 10.1.3.5.3 and status information about own participants. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.4.4 Void | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5 Retrieving and processing a group document | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5.1 General | This clause describes how an MCPTT server accesses a group document from a group management server. The MCPTT server which accesses a group document performs the role of a controlling MCPTT function or performs the role of a non-controlling MCPTT function of an MCPTT group when accessing a group document. In such cases, for a group call:
- the controlling MCPTT function and group management server are both located in the primary MCPTT system;
- the controlling MCPTT function and group management server are both located in a partner MCPTT system;
- the controlling MCPTT function is located in the primary MCPTT system and accesses a group management server in the primary MCPTT system and a non-controlling MCPTT function of an MCPTT group is located in a partner MCPTT system and accesses a group management server in the partner MCPTT system; or
- the controlling MCPTT function and non-controlling MCPTT function(s) of an MCPTT group are located in the primary MCPTT system and access group management servers in the primary MCPTT system.
When the MCPTT server receives a SIP INVITE request that requires it to access a group document, it uses an MCPTT group ID or a temporary MCPTT group identity (TGI) which was created by the group regrouping operation as specified in 3GPP TS 24.481 [31].
The MCPTT server can cache the group document associated with an MCPTT group or temporary group, and can subscribe to be notified of changes to the group document associated with an MCPTT group or temporary group as specified in 3GPP TS 24.481 [31].
NOTE 1: During the group regrouping operation as specified in 3GPP TS 24.481 [31], the controlling MCPTT function is notified of the constituent MCPTT group identities associated with the TGI.
If the group data associated with an MCPTT group ID or TGI cached in the MCPTT server is removed, the MCPTT server re-subscribes for changes in the group information associated with the MCPTT group ID or TGI.
NOTE 2: Re-subscription can occur prior to the receipt of an SIP INVITE request containing an MCPTT group ID or TGI of a group document which is no longer cached on the MCPTT server. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5.2 Rules for retrieving Group Document(s) | NOTE 1: In this clause, "MCPTT server" can refer to either the controlling MCPTT function of an MCPTT group or the non-controlling MCPTT function of an MCPTT group.
When the group document is retrieved for the controlling MCPTT function procedures or for the non-controlling MCPTT function terminating procedures (clauses 10.1.1.5.2), the requested group identity refers to the group identity in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request.
When the group document is retrieved for the non-controlling MCPTT function to initiate a temporary group session (clause 10.1.1.5.5), the requested group identity refers to the group identity of the constituent group contained in the <associated-group-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request.
Upon receipt of a SIP INVITE request:
1) if the MCPTT server is not yet subscribed to the group document for the requested group, the MCPTT server shall subscribe to the "xcap-diff" event-package for the group document of this group identity as specified in 3GPP TS 24.481 [31];
NOTE 2: The requested group identity is either an MCPTT group ID or a temporary MCPTT group identity (TGI).
NOTE 3: As a group document can potentially have a large content, the controlling MCPTT function of an MCPTT group can subscribe to the group document indicating support of content-indirection as defined in IETF RFC 4483 [32], by following the procedures in 3GPP TS 24.481 [31].
2) upon receipt of a SIP 404 (Not Found) response as a result of attempting to subscribe to the "xcap-diff" event-package for the group document of the requested group as specified in 3GPP TS 24.481 [31], the MCPTT server shall send the SIP 404 (Not Found) response with the warning text set to "113 group document does not exist" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps;
3) upon receipt of any other SIP 4xx, SIP 5xx or SIP 6xx response as a result of attempting to subscribe to the "xcap-diff" event-package for the group document of the requested group identity as specified in 3GPP TS 24.481 [31], the MCPTT server shall send the SIP final response with the warning text set to "114 unable to retrieve group document" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
4) upon receipt of a notification from the group management server containing the group document for the requested group identity, or if the group document is already cached:
a) if the MCPTT server is a non-controlling function of an MCPTT group, then the MCPTT server shall exit this clause; and
b) if the MCPTT server is a controlling function of an MCPTT group, then the MCPTT server shall determine if the group document is for a TGI or an MCPTT group ID as follows:
i) if the group document includes an <on-network-temporary> element, then the group document is associated with a TGI;
ii) if the group document does not include an <on-network-temporary> element or an <on-network-regrouped> element, then the group document is associated with an MCPTT group ID that has not been regrouped; and
iii) if the group document does not include an <on-network-temporary> element but includes an <on-network-regrouped> element, then the group document is associated with an MCPTT group ID that has been regrouped;
5) if the requested group identity is an MCPTT group ID that has not been re-grouped, then:
a) if the <on-network-disabled> element is present in the group document, shall send a SIP 403 (Forbidden) response with the warning text set to "115 group is disabled" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
b) if the <list> element of the <list-service> element does not contain an entry matching the MCPTT ID of the user in the SIP INVITE request, shall send a SIP 403 (Forbidden) response with the warning text set to "116 user is not part of the MCPTT group" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
c) if the <on-network-invite-members> element is set to "true" and if the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element containing a value not set to "prearranged", shall return a SIP 404 (Not Found) response with the warning text set to "117 the group identity indicated in the request is a prearranged group" as specified in clause 4.4 "Warning header field" and shall not continue with the rest of the steps; and
d) if the <on-network-invite-members> element is set to "false" and if the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element containing a value not set to "chat" shall return a SIP 404 (Not Found) response with the warning text set to "118 the group identity indicated in the request is a chat group" as specified in clause 4.4 "Warning header field" and shall not continue with the rest of the steps; and
6) if the requested group identity is an MCPTT group ID that has been regrouped then the MCPTT server:
a) shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the warning text set to "148 group is regrouped" as specified in clause 4.4 "Warning header field" and shall not continue with the rest of the steps. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5.3 Rules for joining a group session | The following conditions shall be met for the controlling MCPTT function to allow an MCPTT user to join an existing group session:
1) an <entry> element exists in the <list> element of the group document for the MCPTT user;
2) a <rule> exists in the group document with:
a) the <is-list-member> element of the <conditions> element present and with the <join-handling> element of the corresponding <actions> element set to "true"; or
b) the <identity> element of the <conditions> element containing an entry matching the MCPTT ID in the SIP INVITE request, with the <join-handling> element of the <actions> element set to "true"; and
3) if the <supported-services> element is present, it contains:
a) a <service> element containing an "enabler" attribute which is set to the MCPTT ICSI; and
b) if a <group-media> element is present, an entry set to "MCPTT speech".
If all of the above conditions are not met, then the MCPTT user shall not be authorised to join the group session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5.4 Rules for initiating a prearranged group session | When the non-controlling MCPTT function of an MCPTT group receives a request to intiate a group session for the calling MCPTT user, if:
1) one of the following conditions is met:
a) the <on-network-regrouped> element in the <list-service> element is present in the group document associated with the MCPTT group ID identified in the <associated-group-id> element of the incoming SIP INVITE and if the MCPTT group ID indicated in the <mcptt-request-uri> element of the incoming INVITE request is the same as the MCPTT group ID in the "temporary-MCPTT-group-ID" attribute of the <on-network-regrouped> element; or
b) according to the information stored per procedures of clause 16, the group identified in the <mcptt-request-uri> of the incoming SIP INVITE is a group regroup based on a preconfigured group and if the group identified in the <associated-group-id> of the incoming SIP INVITE is a constituent group of that group regroup based on a preconfigured group according;
NOTE 1: In this step 1), the non-controlling MCPTT function checks the consistency of the constituent group with the called group regroup.
2) an <entry> element set to the MCPTT IDof the calling MCPTT user exists in the <list> element of the group document associated with the MCPTT group ID identified in the <associated-group-id> element of the incoming SIP INVITE;
NOTE 2: In this step 2), the non-controlling MCPTT function checks that the calling MCPTT user is a member of the constituent group.
3) a <rule> exists in the group document with:
a) the <is-list-member> element of the <conditions> element present and with the <allow-initiate-conference> element of the corresponding <actions> element set to "true"; or
b) the <identity> element of the <conditions> element containing an entry matching the MCPTT ID of the calling MCPTT user identified in the <mcptt-calling-user-id> element of the SIP INVITE request, with the <allow-initiate-conference> element of the <actions> element is set to "true"; and
4) the <supported-services> element exists in the group document with:
a) a <service> element containing an "enabler" attribute which is set to the MCPTT ICSI; and
b) a <group-media> element containing an entry set to "MCPTT speech".
NOTE 3: In these steps 3) and 4) the non-controlling MCPTT function checks that the calling MCPTT user is allowed to initiate the group call per the rules in the group document, and that the group is supporting MCPTT services.
then the calling MCPTT user shall be authorised by the non-controlling MCPTT function to initiate the group session. Otherwise, the calling MCPTT user shall not be authorised by the non-controlling MCPTT function to initiate the group session.
When the controlling MCPTT function of an MCPTT group receives a request to intiate a group session for the calling MCPTT user, if:
NOTE 4: The check that the MCPTT group has not been regrouped (is not a constituent group) is done in the parent procedure and in clause 6.3.5.2.
1) the MCPTT group ID identified in the <mcptt-request-uri> element of the incoming SIP INVITE is a temporary group or a group regroup based on preconfigured group, then the calling MCPTT user shall be authorised by the controlling MCPTT function to initiate the group session and the rest of the steps in this clause shall be skipped;
NOTE 5: The consistency of the constituent group with the called regroup has been checked at the non-controlling MCPTT function.
NOTE 6: The check that the requesting user is authorised to initiate the group call has been done at the non-controlling MCPTT function of the constituent group.
2) one of the following conditions is met:
a) an <entry> element set to the MCPTT ID of the calling MCPTT user exists in the <list> element of the group document associated with the MCPTT group ID identified in the <mcptt-request-uri> element of the incoming SIP INVITE; or
b) the group is a user regroup based on a preconfigured group and the MCPTT ID contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request is included in the list of users that was stored during successful processing of the creation of the user regroup per clause 16;
NOTE 7: In this step 2), the controlling MCPTT function checks that the calling MCPTT user is a member of the normal group (i.e., not a constituent group nor a regroup) or a user regroup.
3) a <rule> exists in the group document with:
a) the <is-list-member> element of the <conditions> element present and with the <allow-initiate-conference> element of the corresponding <actions> element set to "true"; or
b) the <identity> element of the <conditions> element containing an entry matching the MCPTT ID of the calling MCPTT user identified in the <mcptt-calling-user-id> element of the SIP INVITE request, with the <allow-initiate-conference> element of the <actions> element is set to "true"; and
4) the <supported-services> element exists in the group document with:
a) a <service> element containing an "enabler" attribute which is set to the MCPTT ICSI; and
b) a <group-media> element containing an entry set to "MCPTT speech".
NOTE 8: In these steps 3) and 4), the controlling MCPTT function checks that the calling MCPTT user is allowed to initiate the group call per the rules in the group document, and that the group is supporting MCPTT services.
then the calling MCPTT user shall be authorised by the controlling MCPTT function to initiate the group session. Otherwise, the calling MCPTT user shall not be authorised by the controlling MCPTT function to initiate the group session. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.5.5 Determining the group members to invite | The MCPTT server shall only invite affiliated group members to a group session.
If the group is not a regroup based on a preconfigured group, the MCPTT server determines the affiliated members from the entries contained in the <list> element of the group document by following the procedures specified in clause 6.3.6.
If the group is a regroup based on a preconfigured group, the MCPTT server determines the affiliated members from the list of users that was stored during successful processing of the creation of the regroup per clause 16 by following the procedures specified in clause 6.3.6.
NOTE 1: The term "affiliated group members" used above also includes those members that are implicitly affiliated by the controlling MCPTT function.
If the number of members of the MCPTT group exceeds the value contained in the <on-network-max-participant-count> element the MCPTT server shall invite only <on-network-max-participant-count> members from the list, but shall prioritise inviting those group members to the group session that have an <entry> element in the <list> element with a <on-network-required> element present.
NOTE 2: The <on-network-max-participant-count> element indicates the maximum number of participants allowed in the group session. The <on-network-required> element is used to determine which group members need to acknowledge the group call before audio transmission can proceed.
NOTE 3: Other requirements for how the controlling MCPTT function selects which of the <on-network-max-participant-count> members to invite is outside the scope of this specification.
NOTE 4: It is assumed that validation checks are performed at the group management server to ensure that the <on-network-max-participant-count> cannot be less than the number of <on-network-required> users. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.6 Affiliation check | The MCPTT server checks if an MCPTT user is affiliated to an MCPTT group at an MCPTT client by following the procedures specified below:
1. the MCPTT server shall find the applicable MCPTT group information entry as an MCPTT group information entry of the list of MCPTT group information entries described in clause 9.2.2.3.2, such that the MCPTT group ID of the MCPTT group information entry is equal to the MCPTT group identity of the MCPTT group. If the applicable MCPTT group information entry cannot be found, then the MCPTT server shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the MCPTT server shall not continue with rest of the steps;
2. the MCPTT server shall find the applicable MCPTT user information entry as an MCPTT user information entry of the list of MCPTT user information entries of the applicable MCPTT group information entry, such that the MCPTT ID of the MCPTT user information entry is equal to the MCPTT ID of the MCPTT user. If the applicable MCPTT user information entry cannot be found, then the MCPTT server shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the MCPTT server shall not continue with rest of the steps;
3. if the MCPTT client ID of the MCPTT client cannot be found in the list of MCPTT client information entries of the applicable MCPTT user information entry, then the MCPTT server shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the MCPTT server shall not continue with rest of the steps;
NOTE: the MCPTT client ID of the originating MCPTT client can be found in the <mcptt-client-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of a SIP INVITE request, SIP REFER request or SIP MESSAGE request originated by the MCPTT client.
4. if the expiration time of the applicable MCPTT user information entry has been reached, then the MCPTT server shall determine that the MCPTT user is not affiliated to the MCPTT group at the MCPTT client and the MCPTT server shall not continue with rest of the steps; and
5. the MCPTT server shall determine that the MCPTT user is affiliated to the MCPTT group at the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.7 Error handling | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.7.1 Public service identity does not exist | Upon receiving a request that includes the Request-URI set to a public service identity that is not allocated in the participating or the controlling MCPTT function, the participating or the controlling MCPTT function shall return a SIP 404 (Not Found) response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.8 Session release policy | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.8.1 Session release policy for group call | If:
1) the call is a pre-arranged group call, or a broadcast group call, or an adhoc group call and if the controlling MCPTT function receives an indication from the media plane that the T4 (Inactivity) timer specified in 3GPP TS 24.380 [5] expired;
2) there are only one or no participants in the MCPTT session;
3) the call is a pre-arranged group call or an adhoc group call and if it is according to local policy, the initiator of the group call leaves the MCPTT session;
4) the minimum number of affiliated MCPTT group members is not present;
NOTE: Not applicable for adhoc group calls.
5) timer TNG3 (group call timer) expires; or
6) the call is an adhoc group call and if it is according to local policy, one or multiple specific user(s) of the group call leave the MCPTT session;
the controlling MCPTT function shall release the MCPTT session for the group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.3.8.2 Session release policy for private call | If:
1) the controlling MCPTT function receives an indication from the media plane that the T4 (Inactivity) timer specified in 3GPP TS 24.380 [5] expired;
2) the MCPTT session has lasted longer than the maximum of duration of private call; or
3) there are only one or no participants in the MCPTT session;
the controlling MCPTT function shall release the MCPTT session for a private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.4 Implicit floor request | An initial SIP INVITE request fulfilling the following criteria shall be regarded by the MCPTT server as an implicit floor request by the originating MCPTT client when the MCPTT client:
1) initiates an MCPTT speech session or initiates a pre-established session that is not used for a remotely initiated MCPTT ambient listening call; and
2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the floor control in the SDP offer/answer as specified in 3GPP TS 24.380 [5] clause 12.
An initial SIP INVITE request fulfilling the following criteria shall be regarded by the MCPTT server as an implicit request to grant the floor to the terminating MCPTT client when the originating MCPTT client:
1) initiates a remotely initiated MCPTT ambient listening call; and
2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the floor control in the SDP offer/answer as specified in 3GPP TS 24.380 [5] clause 12.
A SIP re-INVITE request fulfilling the following criteria shall be regarded by the MCPTT server as an implicit floor request when the MCPTT client:
1) performs an upgrade of:
a) an MCPTT group call to an emergency MCPTT group call;
b) an MCPTT private call to an emergency MCPTT private call; or
c) an MCPTT group call to an imminent peril MCPTT group call; and
2) includes the "mc_implicit_request" 'fmtp' attribute in the associated UDP stream for the floor control in the SDP offer/answer as specified in 3GPP TS 24.380 [5] clause 12.
In all other cases the SIP (re-)INVITE request shall be regarded as received without an implicit floor request.
When using a pre-established session the MCPTT server shall regard the SIP REFER request as an implicit floor request:
1) if the pre-established session was established with an implicit floor request and if an SDP offer is not included in a "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field;
2) if the pre-established session was established with an implicit floor request, an SDP offer is included in a "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field, and this SDP includes the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer; or
3) if the pre-established session was established without an implicit floor request and the SDP offer in a "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, referenced by the "cid" URL in the Refer-To header field includes the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer.
In all other cases the SIP REFER request shall be regarded as received without an implicit floor request.
When using a pre-established session the MCPTT server shall regard the SIP REFER request as an implicit request to grant the floor to the terminating MCPTT client:
1) if the pre-established session was established with an SDP offer included in a "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists MIME+xml body, referenced by the "cid" URL in the Refer-To header field, and this SDP includes the "mc_implicit_request" media level attribute in the associated UDP stream for the floor control in the SDP offer; and
2) the pre-established session is being used for a remotely initiated ambient listening call.
In all other cases the SIP REFER request shall be regarded as received without an implicit request to grant the floor to the terminating MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.5 Handling of MIME bodies in a SIP message | The MCPTT client and the MCPTT server shall support several MIME bodies in SIP request and SIP responses.
When the MCPTT client or the MCPTT server sends a SIP message and the SIP message contains more than one MIME body, the MCPTT client or the MCPTT server:
1) shall, as specified in IETF RFC 2046 [21], include one Content-Type header field with the value set to multipart/mixed and with a boundary delimiter parameter set to any chosen value;
2) for each MIME body:
a) shall insert the boundary delimiter;
b) shall insert the Content-Type header field with the MIME type of the MIME body; and
c) shall insert the content of the MIME body;
3) shall insert a final boundary delimiter; and
4) if an SDP offer or an SDP answer is one of the MIME bodies, shall insert the application/sdp MIME body as the first MIME body.
NOTE: The reason for inserting the application/sdp MIME body as the first body is that if a functional entity in the underlying SIP core does not understand multiple MIME bodies, the functional entity will ignore all MIME bodies with the exception of the first MIME body. The order of multiple MCPTT application MIME bodies in a SIP message is irrelevant.
When the MCPTT client or the MCPTT server sends a SIP message and the SIP message contains only one MIME body, the MCPTT client or the MCPTT server:
1) shall include a Content-Type header field set to the MIME type of the MIME body; and
2) shall insert the content of the MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6 Confidentiality and Integrity Protection | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.1.1 Applicability and exclusions | The procedures in clauses 6.6 apply in general to all procedures described in clause 9, clause 10, clause 11 and clause 12 with the exception that the confidentiality and integrity protection procedures for the registration and service authorisation procedures are described in clause 7. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.1.2 Performing XML content encryption | Whenever the MCPTT UE includes XML elements or attributes pertaining to the data specified in clause 4.8 in SIP requests or SIP responses, the MCPTT UE shall perform the procedures in clause 6.6.2.3.1.
Whenever the MCPTT server includes XML elements or attributes pertaining to the data specified in clause 4.8 in SIP requests or SIP responses, the MCPTT server shall perform the procedures in clause 6.6.2.3.2, with the exception that when the MCPTT server receives a SIP request with XML elements or attributes in an MIME body that need to be copied from the incoming SIP request to an outgoing SIP request without modification, the MCPTT server shall perform the procedures specified in clause 6.6.2.5.
NOTE: The procedures in clause 6.6.2.3.1 and clause 6.6.2.3.2 first determine (by referring to configuration) if confidentiality protection is enabled and then call the necessary procedures to encrypt the contents of the XML elements if confidentiality protection is enabled. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.1.3 Performing integrity protection on an XML body | The functional entity shall perform the procedures in the clause just prior to sending a SIP request or SIP response.
1) The MCPTT UE shall perform the procedures in clause 6.6.3.3.1; and
2) The MCPTT server shall perform the procedures in clause 6.6.3.3.2.
NOTE: The procedures in clause 6.6.3.3.1 and clause 6.6.3.3.2 first determine if integrity protection of XML MIME bodies is required and then calls the necessary procedures to integrity protect each XML MIME body if integrity protection is required. Each XML MIME body has its own signature. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.1.4 Verifying integrity of an XML body and decrypting XML elements | Whenever the functional entity (i.e. MCPTT UE or MCPTT server) receives a SIP request or a SIP response, the functional entity shall perform the following procedures before performing any other procedures.
1) The functional entity shall determine if integrity protection has been applied to an XML MIME body by following the procedures in clause 6.6.3.4.1 and if integrity protection has been applied:
a) shall use the keying information described in clause 6.6.3.2 and the procedures described in clause 6.6.3.4.2 to verify the integrity of the XML MIME body; and
b) if the integrity protection checks fail shall not perform any further procedures in this clause;
2) The functional entity shall determine whether confidentiality protection has been applied to XML elements in XML MIME bodies in a SIP request or SIP response, pertaining to the data specified in clause 4.8, by following the procedures in clause 6.6.2.4.1, and if confidentiality protection has been applied:
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 decrypt the received values; and
b) if any decryption procedures fail, shall not perform any further procedures in this clause. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2 Confidentiality Protection | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.1 General | In general, confidentiality protection is applied to specific XML elements and attributes in XML MIME bodies in SIP requests and responses as specified in clause 4.8. However in the case of SIP REFER requests used for pre-established sessions, confidentiality protection is required for:
the targeted MCPTT ID or MCPTT Group ID in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body that is pointed to by a "cid" URL located in the Refer-To header field of the SIP REFER request; and
- sensitive XML data included in MIME bodies which are placed in the hname "body" parameter in the headers portion of the SIP URI in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body.
Configuration for applying confidentiality protection is not selective to a specific XML element or attribute of the data described in clause 4.8. If configuration for confidentiality protection is turned on, then all XML elements and attributes described in clause 4.8 are confidentiality protected. If configuration for confidentiality protection is turned off, then no XML content in SIP requests and SIP responses are confidentiality protected. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.2 Keys used in confidentiality protection procedures | Confidentiality protection uses an XPK to encrypt the data which (depending on who is the sender and who is the receiver of the encrypted information) can be a CSK or an SPK as specified in clause 4.8. An XPK-ID (CSK-ID/SPK-ID) is used to key the XPK (CSK/SPK). It is assumed that before the procedures in this clause are called, the CSK/CSK-ID and/or SPK/SPK-ID are available on the sender and recipient of the encrypted content as described in clause 4.8.
The procedures in clause 6.6.2.3 and clause 6.6.2.4 are used with a XPK equal to the CSK and a XPK-ID equal to the CSK-ID in the following circumstances as described in 3GPP TS 33.180 [78]:
1) MCPTT client sends confidentiality protected content to an MCPTT server; and
2) MCPTT server sends confidentiality protected content to an MCPTT client.
The procedure in clause 6.6.2.3 and clause 6.6.2.4 are used with a XPK equal to the SPK and a XPK-ID equal to the SPK-ID in the following circumstances as described in 3GPP TS 33.180 [78]:
1) MCPTT server sends confidentiality protected content to an MCPTT server in the same domain; and
2) MCPTT server sends confidentiality protected content to an MCPTT server in another domain. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.3 Procedures for sending confidentiality protected content | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.3.1 MCPTT client | If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <confidentiality-protection> element is present in the Service Configuration document, then sending confidentiality protected content from the MCPTT client to the MCPTT server is enabled, and the MCPTT client:
1) shall use the appropriate keying information specified in clause 6.6.2.2;
2) shall perform the procedures in clause 6.6.2.3.3 to confidentiality protect XML elements containing the content described in clause 4.8; and
3) shall perform the procedures in clause 6.6.2.3.4 to confidentiality protect URIs in XML attributes for URIs described in clause 4.8.
If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending confidentiality protected content from the MCPTT client to the MCPTT server is disabled, and content is included in XML elements and attributes without encryption. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.3.2 MCPTT server | If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <confidentiality-protection> element is present in the Service Configuration document, then sending confidentiality protected content from the MCPTT server to the MCPTT client is enabled. If the <allow-signalling-protection> element of the <protection-between-mcptt-servers> element is set to "true" in the Service Configuration document as specified in 3GPP TS 24.484 [50] or no <allow-signalling-protection> element is present in the Service Configuration document, then sending confidentiality protected content between MCPTT servers is enabled.
When sending confidentiality protected content, the MCPTT server:
1) shall use the appropriate keying information specified in clause 6.6.2.2;
2) shall perform the procedures in clause 6.6.2.3.3 to confidentiality protect XML elements containing the content described in clause 4.8, and
3) shall perform the procedures in clause 6.6.2.3.4 to confidentiality protect URIs in XML attributes for URIs described in clause 4.8.
If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending confidentiality protected content from the MCPTT server to the MCPTT client is disabled, and then content is included in XML elements and attributes without encryption.
If the <allow-signalling-protection> element of the <protection-between-mcptt-servers> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending confidentiality protected content between MCPTT servers is disabled, and content is included in XML elements and attributes without encryption. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.3.3 Content Encryption in XML elements | The following procedures shall be performed by an MCPTT client or an MCPTT server:
1) perform encryption as specified in W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-core1/ [60] clause 4.3, using the "AES-128-GCM algorithm HMAC" as the encryption algorithm and the XPK as the key; and
2) follow the semantic for the element of the MIME body as described in Annex F of the present document, to include the encrypted content in the MIME body ensuring that the necessary XML elements required for confidentiality protection are included as specified in 3GPP TS 33.180 [78]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.3.4 Attribute URI Encryption | The following procedures shall be performed by an MCPTT client or an MCPTT server:
1) perform encryption as specified in IETF RFC 5288 [83], using the "AES-128-GCM algorithm HMAC" as the encryption algorithm and the XPK as the key, with a 96 bit randomly selected IV; and
2) replace the URI to be protected in the attribute by a URI constructed as follows:
a) the URI schema is "sip:";
b) the first part of the userinfo part is the base64 encoded result of the encryption of the original attribute value;
c) the string ";iv=" is appended to the result of step b);
d) the base64 encoding of the IV (section 5 of IETF RFC 4648 [71]) is appended to the result of step c);
e) the string ";key-id=" is appended to the result of step d);
f) the base64 encoding of the XPK-ID according to 3GPP 33.180 [78] is appended to the result of step e);
g) the string ";alg=128-aes-gcm" is appended to the result of step f); and
h) the string "@" followed by the domain name for MCPTT confidentiality protection as specified in 3GPP TS 23.203 [41] is appended to the result of step g). |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.4 Procedures for receiving confidentiality protected content | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.4.1 Determination of confidentiality protected content | The following procedure is used by the MCPTT client or MCPTT server to determine if an XML element is confidentiality protected.
1) if an XML element contains the <EncryptedData> XML element, then the content of the XML element is confidentiality protected; and
2) if an XML element does not contain the <EncryptedData> XML element, then the content of the XML element is.not confidentiality protected.
The following procedure is used by the MCPTT client or MCPTT server to determine if a URI in the XML attribute is confidentiality protected.
1) if an XML attribute is a URI with the domain name for MCPTT confidentiality protection as specified in the 3GPP TS 23.003 [40], then the URI is confidentiality protected; and
2) if an XML attribute is a URI without the domain name for MCPTT confidentiality protection as specified in the 3GPP TS 23.003 [40], then the URI is not confidentiality protected. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.4.2 Decrypting confidentiality protected content in XML elements | The following procedure shall be performed by an MCPTT client or an MCPTT server to decrypt an individual XML element that has a type of "encrypted" within an XML MIME body:
1) if the <EncryptedData> XML element or any of its sub-elements as described in 3GPP TS 33.180 [78] are not present in the MIME body then send a SIP 403 (Forbidden) response with the warning text set to "140 unable to decrypt XML content" in a Warning header field as specified in clause 4.4, and exit this procedure. Otherwise continue with the rest of the steps;
2) perform decryption on the <EncryptedData> element as specified in W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-core1/ [60] clause 4.4 to decrypt the contents of the <CipherValue> element contained within the <CipherData> element;
3) if the decryption procedure fails, then send a SIP 403 (Forbidden) response with the warning text set to "140 unable to decrypt XML content" in a Warning header field as specified in clause 4.4. Otherwise continue with the rest of the steps; and
4) return success of this procedure together with the decrypted XML element. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.4.3 Decrypting confidentiality protected URIs in XML attributes | The following procedure shall be performed by an MCPTT client or an MCPTT server to decrypt a URI in an attribute in a XML document:
1) the value between ";iv=" and the next ";" provides the base64 encoded value of the 96 bit IV and the value between ";=key-id" and the next ";" defines the key which has been used for encryption, i.e. "CSK" or "SPK"; and
2) the original URI is obtained by decrypting the base64 encoded string between the "sip:" URI prefix and the next ";" using the "AES-128-GCM algorithm HMAC" as the decryption algorithm with IV and key as determined in step 1). This value replaces the encrypted URI as the value of the XML attribute. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.2.5 MCPTT server copying received XML content | The following procedure is executed when an MCPTT server receives a SIP request containing XML MIME bodies, where the content needs to be copied from the incoming SIP request to the outgoing SIP request.
The MCPTT server:
1) shall copy the XML elements from the XML MIME body of the incoming SIP request that do not contain a <EncryptedData> XML element, to the same XML body in the outgoing SIP request;
2) for each encrypted XML element in the XML MIME body of the incoming SIP request as determined by clause 6.6.2.4.1:
a) shall use the keying information described in clause 6.6.2.2 to decrypt the content within the XML element by following the procedures specified in clause 6.6.2.4.2, and shall continue with the steps below if the encrypted XML element was successfully decrypted;
b) if confidentiality protection is enabled as specified in clause 6.6.2.3.2, then for each decrypted XML element:
i) shall re-encrypt the content within the XML element using the keying information described in clause 6.6.2.2 and by following the procedures specified in clause 6.6.2.3.3; and
ii) shall include the re-encrypted content into the same XML MIME body of the outgoing SIP request; and
c) if confidentiality protection is disabled as specified in clause 6.6.2.3.2, shall include the decrypted content in the same XML MIME body of the outgoing SIP request.
3) for each encrypted XML URI attribute in the XML MIME body of the incoming SIP request as determined by clause 6.6.2.4.1:
a) shall use the keying information described in clause 6.6.2.2 to decrypt the URI value of the XML attribute by following the procedures specified in clause 6.6.2.4.3, and shall continue with the steps below if the encrypted XML attribute value was successfully decrypted;
b) if confidentiality protection is enabled as specified in clause 6.6.2.3.2, then for each decrypted XML element:
i) shall re-encrypt the URI value of the XML attribute using the keying information described in clause 6.6.2.2 and by following the procedures specified in clause 6.6.2.3.4; and
ii) shall include the re-encrypted attribute value into the same XML MIME body of the outgoing SIP request; and
c) if confidentiality protection is disabled as specified in clause 6.6.2.3.2, shall include the decrypted value in the same XML MIME body of the outgoing SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3 Integrity Protection of XML documents | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.1 General | Integrity protection can be applied to a whole XML MIME body. When integrity protection is enabled, all XML MIME bodies transported in SIP requests and responses are integrity protected. The following XML MIME bodies used in the present specification in SIP signalling can be integrity protected:
- application/vnd.3gpp.mcptt-info+xml;
- application/poc-settings+xml;
- application/resource-lists+xml;
- application/vnd.3gpp.mcptt-mbms-usage-info+xml;
- application/vnd.3gpp.mcptt-mbs-usage-info+xml;
- application/vnd.3gpp.mcptt-location-info+xml;
- application/vnd.3gpp.mcptt-affiliation-command+xml;
- application/vnd.3gpp.mcptt-floor-request+xml;
- application/conference-info+xml;
- application/pidf+xml;
- application/xcap-diff+xml;
- application/simple-filter+xml; and
- application/vnd.3gpp.mcptt-regroup+xml.
If integrity protection is enabled, and one or more of the XML MIME bodies complying to the types listed above are included in a SIP request or SIP response, then a MIME body of type application/vnd.3gpp.mcptt-signed+xml is included in the SIP request or SIP response containing one or more signatures pointing to those XML MIME bodies as illustrated in Figure 6.6.3.3-1.
In order to integrity protect the XML MIME bodies listed above in this clause in SIP requests and SIP responses, the MCPTT client and MCPTT server shall for each MIME body, include the Content-ID header field as specified in IETF RFC 2045 [68] containing a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62].
Figure 6.6.3.1-1: Integrity Protection of XML MIME bodies in SIP requests and SIP responses
Each MIME body that is integrity protected is assigned a unique signature.
When integrity protecting the XML content in SIP REFER request used for pre-established sessions, the application/vnd.3gpp.mcptt-signed+xml MIME type can appear twice in the SIP REFER request as illustrated in Figure 6.6.3.1-2.
Figure 6.6.3.1-2: Integrity Protection of XML MIME bodies in SIP REFER requests
- an application/vnd.3gpp.mcptt-signed+xml MIME body is included in the SIP REFER request with a signature pointing to the application/resource-lists+xml MIME body; and
NOTE 1: Sensitive XML content placed in the application/resource-lists+xml MIME body can be encrypted.
- an application/vnd.3gpp.mcptt-signed+xml MIME is included in the hname "body" parameter in the headers portion of the SIP URI in the "uri" attribute of the <entry> element of the application/resource-lists+xml MIME body in the SIP REFER request, containing signatures pointing to the XML MIME bodies included in the hname "body" parameter in the headers portion of the SIP URI.
NOTE 2: Sensitive XML content placed in the hname "body" parameter in the headers portion of the SIP URI can be encrypted.
Configuration for applying integrity protection is not selective to a specific MIME body. If configuration for integrity protection is turned on, then all XML MIME bodies in SIP requests and responses are integrity protected. If configuration for integrity protection is turned off, then no XML MIME bodies in SIP requests and SIP responses are integrity protected. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.2 Keys used in integrity protection procedures | Integrity protection uses an XPK to sign the data which (depending on who is the sender and who is the receiver of the signed information) can be a CSK or an SPK as specified in clause 4.8. An XPK-ID (CSK-ID/SPK-ID) is used to key the XPK (CSK/SPK). It is assumed that before the procedures in clause 6.6.3.3 and clause 6.6.3.4 are called, the CSK/CSK-ID and/or SPK/SPK-ID are available on the sender and recipient of the integrity protected content, as described in clause 4.8.
The procedures in clause 6.6.3.3 and clause 6.6.3.4 shall be used with a XPK equal to the CSK and a XPK-ID equal to the CSK-ID in the following circumstances as described in 3GPP TS 33.180 [78]:
1) MCPTT client sends integrity protected content to an MCPTT server; and
2) MCPTT server sends integrity protected content to an MCPTT client.
The procedure in clause 6.6.3.3 and clause 6.6.3.4 shall be used with a XPK equal to the SPK and a XPK-ID equal to the SPK-ID in the following circumstances as described in 3GPP TS 33.180 [78]:
1) MCPTT server sends integrity protected content to an MCPTT server in the same domain; and
2) MCPTT server sends integrity protected content to an MCPTT server in another domain. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.3 Sending integrity protected content | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.3.1 MCPTT client | If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <integrity-protection> element is present in the Service Configuration document, then sending integrity protected content from the MCPTT client to the MCPTT server is enabled, and the MCPTT client shall use the appropriate keying information specified in clause 6.6.3.2 and shall perform the procedures in clause 6.6.3.3.3 to integrity protect XML MIME bodies.
NOTE: Each XML MIME body is integrity protected separately.
If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending integrity protected content from the MCPTT client to the MCPTT server is disabled, and all XML MIME bodies are sent without integrity protection. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.3.2 MCPTT server | If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true", or no <integrity-protection> element is present in the Service Configuration document, then sending integrity protected content from the MCPTT server to the MCPTT client is enabled. If the <allow-signalling-protection> element of the <protection-between-mcptt-servers> element is set to "true" in the Service Configuration document as specified in 3GPP TS 24.484 [50] or no <allow-signalling-protection> element is present in the Service Configuration document, then sending integrity protected content between MCPTT servers is enabled.
When sending integrity protected content, the MCPTT server shall use the appropriate keying information specified in clause 6.6.3.2 and shall perform the procedures in clause 6.6.3.3.3 to integrity protect XML MIME bodies.
NOTE: Each XML MIME body is integrity protected separately.
If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending integrity protected content from the MCPTT server to the MCPTT client is disabled, and all XML MIME bodies are sent without integrity protection.
If the <allow-signalling-protection> element of the <protection-between-mcptt-servers> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "false", then sending integrity protected content between MCPTT servers is disabled, and content is included in XML elements without encryption. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.3.3 Integrity protection procedure | The following procedure shall be performed by the MCPTT client and MCPTT server to integrity protect the XML bodies defined by the MIME types listed in clause 6.6.3.1:
1) include a Content-Type header field set to "application/vnd.3gpp.mcptt-signed+xml";
2) for each of the MIME types defined in clause 6.6.3.1 where the content defined by these MIME types is to be integrity protected:
a) perform reference generation as specified in W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core [61] clause 3.1.1 using the SHA256 algorithm to produce a hash of the MIME body and continue with the procedures below if reference generation is successful;
b) perform signature generation as specified in W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core [61] clause 3.1.2 using the HMAC-SHA256 signature method and the XPK as the key and continue with the procedures below if signature generation is successful; and
3) follow the schema defined in Annex F.6.2 and the semantic described in Annex F.6.3 to create the application/vnd.3gpp.mcptt-signed+xml MIME body containing signatures referring to the XML MIME bodies included in the SIP request or SIP response. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.4 Receiving integrity protected content | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.4.1 Determination of integrity protected content | The following procedure is used by the MCPTT client or MCPTT server to determine if an XML MIME body is integrity protected.
1) if the <Signature> XML element is not present in the XML MIME body, then the content is not integrity protected; and
2) if the <Signature> XML element is present in the XML MIME body, then the content is integrity protected. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.6.3.4.2 Verification of integrity protected content | The following procedure is used by the MCPTT client or MCPTT server to verify the integrity of an XML MIME body:
1) if the required sub-elements of the <Signature> as described in 3GPP TS 33.180 [78] are not present in the MIME body and if not present, are not known to the sender and recipient by other means, then the integrity protection procedure fails and exit this procedure. Otherwise continue with the rest of the steps;
2) perform reference validation on the <Reference> element as specified in W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core [61] clause 3.2.1;
3) if reference validation fails, then send a SIP 403 (Forbidden) response towards the functional entity with the warning text set to: "139 integrity protection check failed" in a Warning header field as specified in clause 4.4, and do not continue with the rest of the steps in this clause;
4) obtain the XPK using the XPK-ID in the received XML body and use it to perform signature validation of the value of the <SignatureValue> element as specified in W3C: "XML Signature Syntax and Processing (Second Edition)", http://www.w3.org/TR/xmldsig-core [61] clause 3.2.2;
5) if signature validation fails, then send a SIP 403 (Forbidden) response towards the functional entity with the warning text set to: "139 integrity protection check failed" in a Warning header field as specified in clause 4.4, and do not continue with the rest of the steps in this clause; and
6) return success of the integrity protection of the XML document passes the integrity protection procedure. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.7 Priority sharing | The participating MCPTT function shall enable or disable priority sharing as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.8 Procedures at the MCPTT gateway | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.8.1 General | As described in clause 5.5, the MCPTT gateway servers are inserted in the path between MCPTT functions that reside in MCPTT systems from different trust domains.
This clause specifies the behavior of an MCPTT gateway server that acts as an exit point from an MCPTT system or as an entry point in an MCPTT system.
Local policies enforcement covers a wide variety of actions that are left to implementation. An example of local policies enforcement is given in clause 6.8.4. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.8.2 MCPTT gateway server acting as an exit point from an MCPTT system | When acting as an exit point from a local MCPTT system to an interconnected MCPTT system, the MCPTT gateway server receives SIP requests and SIP responses intended for the controlling, non-controlling or participating function in the interconnected MCPTT system.
When receiving an outgoing SIP message, the MCPTT gateway server acting as an exit point:
1) shall identify the MCPTT system identity of the interconnected MCPTT system from the Request-URI of the outgoing SIP messages or other information elements from the outgoing SIP message;
2) may enforce local policy, and if local policy enforcement results in rejecting a SIP request (e.g. not having a mutual aid relationship), the MCPTT gateway shall reject the request by sending back a SIP 403 (Forbidden) response including a warning text "179 service not authorized with the interconnected system", and the MCPTT gateway server shall not continue with the rest of the steps;
3) may replace in the outgoing SIP message any addressing information linked to the local MCPTT system topology with its own addressing information. This includes:
a) the P-Asserted-Identity header field may be set to the MCPTT gateway server's own URI; and
b) the Request-URI may be set to the public service identity of the targeted function in the interconnected MCPTT system, or to the URI of the MCPTT gateway server that acts as an entry point in the interconnected MCPTT system; and
NOTE: How the MCPTT gateway server determines the public service identity of the targeted MCPTT function in the interconnected MCPTT system or the URI of the MCPTT gateway server in the interconnected MCPTT system is out of the scope of the present document.
4) shall forward the outgoing SIP message according to 3GPP TS 24.229 [4] |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.8.3 MCPTT gateway server acting as an entry point in an MCPTT system | When acting as an entry point in an MCPTT system from an interconnected MCPTT system, the MCPTT gateway receives SIP requests and SIP responses intended for the controlling, non-controlling or participating function in the local MCPTT system.
When receiving an incoming SIP message, the MCPTT gateway server acting as an entry point:
1) shall identify the MCPTT system identity of the interconnected MCPTT system from the P-Asserted-Identity header field of the incoming SIP messages;
2) may enforce local policy, and if local policy enforcement results in rejecting a SIP request (e.g. not having a mutual aid relationship), the MCPTT gateway shall reject the request by sending back a SIP 403 (Forbidden) response including a warning text "180 service not authorized by the interconnected system", and the MCPTT gateway server shall not continue with the rest of the steps;
3) should replace in the incoming SIP message its own addressing information with the addressing information of the targeted MCPTT function in the local MCPTT system:
a) the Request-URI should be set to the public service identity of the targeted MCPTT function in the local MCPTT system; and
NOTE: How the MCPTT gateway server determines the public service identity of the targeted MCPTT function in the local MCPTT system is out of the scope of the present document.
4) shall forward the incoming SIP message according to 3GPP TS 24.229 [4] |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 6.8.4 Local policies enforcement | Below is one example of local policy enforcement that can be handled by an MCPTT gateway server.
If an MCPTT gateway server acting as an exit point receives a SIP request or a SIP response that contains sensitive information that cannot be exposed to the targeted partner system based on local policies but does not prevent the service from being delivered (e.g. a functional alias), the MCPTT gateway server can remove that information from the outgoing SIP message before forwarding it. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7 Registration and service authorisation | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.1 General | This clause describes the procedures for SIP registration and MCPTT service authorization for the MCPTT client and the MCPTT service. The MCPTT UE can use SIP REGISTER or SIP PUBLISH for MCPTT service settings to perform service authorization for MCPTT. The decision which method to use is based on implementation and on availability of an access-token received as outcome of the user authentication procedure as described in 3GPP TS 24.482 [49].
If another MC service client (e.g. MCVideo, MCData) is operating at the same time on the same MC UE as the MCPTT client, then the MCPTT client shares the same SIP registration as the other MC service clients. The SIP REGISTER procedures in this clause are combined with the SIP REGISTER procedures for the other operating MC service clients to create a single SIP REGISTER request. If other MC service clients are already operating when the MCPTT client registers, then a re-registration is performed containing the parameters for the other operating MC services.
Although the access-token can be the same for the MCPTT service as for other MC services when performing service authorization for MCPTT along with other MC services using SIP REGISTER multipart MIME bodies for each MC service are included in the SIP REGISTER request. The MCPTT server can therefore receive multipart MIME bodies in the SIP REGISTER request. Multiple contact addresses (one per MC service client) can be included in a SIP REGISTER request provided they all contain the same IP address and port number (see 3GPP TS 24.229 [4] for further details of including multiple contact addresses in a single SIP REGISTER request).
If the MCPTT client logs off from the MCPTT service but other MC service clients are to remain registered the MC UE performs a re-registration as specified in 3GPP TS 24.229 [4] without the g.3gpp.mcptt media feature tag and 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 REGISTER request but with the parameters for the remaining operating MC service clients. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2.1 SIP REGISTER request for service authorisation | When the MCPTT client performs SIP registration for service authorisation 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".
NOTE 1: If the MCPTT client logs off from the MCPTT service but the MCPTT UE remains registered the MCPTT UE performs a re-registration as specified in 3GPP TS 24.229 [4] without both the g.3gpp.mcptt media feature tag and 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 REGISTER request.
If the MCPTT client supports MCPTT service continuity, then the MCPTT client shall follow the IMS registration procedures for PS to PS service continuity as specified in clause 6.2.2 of 3GPP TS 24.237 [58].
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;
3) based on implementation decides to use SIP REGISTER for service authorization;
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 during the user authentication procedures;
2) the <mcptt-client-id> element set to the value of the MCPTT client ID of the originating MCPTT client; and
NOTE 2: The access-token contains the MCPTT ID of the user.
3) if the MCPTT client uses a MCPTT gateway UE to access the MCPTT system, the MCPTT client shall set the <gw-mcptt-usage> element to true.
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;
3) based on implementation decides to use SIP REGISTER for service authorization; and
4) 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 client ID of the originating MCPTT client and include the <mcptt-client-id> element set to the encrypted MCPTT client ID; and
c) if the MCPTT client uses a MCPTT gateway UE to access the MCPTT system, the MCPTT client shall set the <gw-mcptt-usage> element to true.
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 value of the access token received during the user authentication procedures;
b) the <mcptt-client-id> element set to the value of the MCPTT client ID of the originating MCPTT client; and
c) if the MCPTT client uses a MCPTT gateway UE to access the MCPTT system, the MCPTT client shall set the <gw-mcptt-usage> element to true; 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.
7.2.1AA SIP REGISTER request without service authorisation
When the MCPTT client performs SIP registration without service authorisation 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".
NOTE: If the MCPTT client logs off from the MCPTT service but the MCPTT UE remains registered the MCPTT UE performs a re-registration as specified in 3GPP TS 24.229 [4] without both the g.3gpp.mcptt media feature tag and 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 REGISTER request.
If the MCPTT client supports MCPTT service continuity, then the MCPTT client shall follow the IMS registration procedures for PS to PS service continuity as specified in clause 6.2.2 of 3GPP TS 24.237 [58].
7.2.1A Common SIP PUBLISH procedure
This procedure is only referenced from other procedures.
When populating the SIP PUBLISH request, the MCPTT client shall:
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 set the Event header field to the "poc-settings" value; and
4) shall set the Expires header field according to IETF RFC 3903 [37], to 4294967295, if the MCPTT user is not removing the MCPTT service settings, otherwise to remove the MCPTT service settings the MCPTT client shall set the Expires header field to zero.
NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
NOTE 2: The expiration timer of the MCPTT client service settings is only applicable for the MCPTT client service settings from the MCPTT client that matches the Instance Identifier URN. The expiration timer of MCPTT user service settings is also updated in the MCPTT server if expiration timer of MCPTT client service settings is updated in the MCPTT server.
NOTE 3: Removing the MCPTT service settings by setting the Expires header field to zero, logs off the MCPTT client from the MCPTT service. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2.2 SIP PUBLISH request for service authorisation and MCPTT service settings | If based on implementation the MCPTT client decides to use SIP PUBLISH for MCPTT server settings to also perform service authorization and
1) has successfully finished the user authentication procedure as described in 3GPP TS 24.482 [49]; and
2) has available an access-token;
then the MCPTT client:
1) shall perform the procedures in clause 7.2.1A;
2) if confidentiality protection is disabled as specified in clause 6.6.2.3.1 and integrity protection is disabled, shall include in the body of the SIP PUBLISH request, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with the <mcptt-access-token> element set to the value of the access token received during the user authentication procedures;
3) if 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 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 PUBLISH request;
4) if confidentiality protection is enabled as specified in clause 6.6.2.3.1, shall include in the body of the SIP PUBLISH request an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-access-token> element set to the received access-token encrypted using the CSK, as specified in clause 6.6.2.3.3;
b) the <mcptt-client-id> element set to the encrypted MCPTT client ID of the originating MCPTT client, as specified in clause 6.6.2.3.3; and
c) if the MCPTT client uses a MCPTT gateway UE to access the MCPTT system, the MCPTT client shall set the <gw-mcptt-usage> element to true.
5) if confidentiality protection is disabled as specified in clause 6.6.2.3.1, shall include in the body of the SIP PUBLISH request, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1 with:
a) the <mcptt-access-token> element set to the value of the access token received during the user authentication procedures in the body of the SIP PUBLISH request;
b) the <mcptt-client-id> element set to the value of the MCPTT client ID of the originating MCPTT client; and
c) if the MCPTT client uses a MCPTT gateway UE to access the MCPTT system, the MCPTT client shall set the <gw-mcptt-usage> element to true.
6) shall include an application/poc-settings+xml MIME body containing:
a) the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package set to the current answer mode setting ("auto-answer" or "manual-answer") of the MCPTT client according to IETF RFC 4354 [55];
b) the <selected-user-profile-index> element as defined in clause 7.4.1.2.2 set to the value contained in the "user-profile-index" attribute of the selected MCPTT user profile as defined in 3GPP TS 24.484 [50]; and
c) the <multiplex-support> element as defined in clause 7.4.1.2.2; and
7) 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 and application/poc-settings+xml MIME body by following the procedures in clause 6.6.3.3.3.
The MCPTT client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the above SIP PUBLISH request, the MCPTT client:
1) may notify the MCPTT user of the successful MCPTT service authorisation and service settings.
Upon receiving a SIP 3xx, SIP 4xx, or SIP 5xx response to the above SIP PUBLISH request, the MCPTT client:
1) should notify the MCPTT user of the unsuccessful MCPTT service authorisation and service setting, possibly taking into account Warning header information for the failure reason; and
2) shall consider that the MCPTT client is not authorised. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2.3 Sending SIP PUBLISH for MCPTT service settings only | To set, update, remove or refresh the MCPTT service settings, the MCPTT client shall generate a SIP PUBLISH request according 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 4354 [55]. In the SIP PUBLISH request, the MCPTT client:
1) shall perform the procedures in clause 7.2.1A;
2) if confidentiality protection is enabled as specified in clause 6.6.2.3.1, shall include in the body of the SIP PUBLISH request, an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-request-uri> element set to the targeted MCPTT ID encrypted using the CSK, as specified in clause 6.6.2.3.3; and
b) the <mcptt-client-id> element set to the encrypted MCPTT client ID of the originating MCPTT client, as specified in clause 6.6.2.3.3;
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 specified in Annex F.1 with:
a) the <mcptt-request-uri> set to the cleartext targeted MCPTT ID; and
b) the <mcptt-client-id> element set to the value of the MCPTT client ID of the originating MCPTT client;
4) shall include an application/poc-settings+xml MIME body containing:
a) the Answer-Mode Indication setting in the <am-settings> element of the poc-settings event package set to the current answer mode setting ("auto-answer" or "manual-answer") of the MCPTT client according to IETF RFC 4354 [55];
b) the <selected-user-profile-index> element as defined in clause 7.4.1.2.2 set to the value contained in the "user-profile-index" attribute of the selected MCPTT user profile as defined in 3GPP TS 24.484 [50]; and
c) the <multiplex-support> element as defined in clause 7.4.1.2.2; and
5) 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 and application/poc-settings+xml MIME body by following the procedures in clause 6.6.3.3.3.
The MCPTT client shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
Upon receiving the SIP 200 (OK) response to the SIP PUBLISH request the MCPTT client may indicate to the MCPTT User the successful communication of the MCPTT service settings to the MCPTT server.
Upon receiving a SIP 3xx, SIP 4xx, or SIP 5xx response to the above SIP PUBLISH request, the MCPTT client:
1) should notify the MCPTT user of the unsuccessful communication of the MCPTT service settings to the MCPTT server, possibly taking into account Warning header information for the failure reason; and
2) shall consider that the MCPTT service settings attempted in the SIP PUBLISH request has not been successful. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2.4 Determination of MCPTT service settings | In order to discover MCPTT service settings of another MCPTT client of the same MCPTT user or to verify the currently active MCPTT service settings of this MCPTT client, the MCPTT client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26], and IETF RFC 4354 [55].
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 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) shall set the Event header field to the 'poc-settings' value;
5) shall include an Accept header field containing the "application/poc-settings+xml" MIME type;
6) 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; and
NOTE 1: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
7) 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.
In order to re-subscribe or de-subscribe, the MCPTT client shall generate and send an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26], IETF RFC 4354 [55]. In the SIP SUBSCRIBE request, the MCPTT client with the following clarifications:
1) shall set the Event header field to the 'poc-settings' value;
2) shall include an Accept header field containing the "application/poc-settings+xml" MIME type;
3) 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; and
NOTE 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
4) if the MCPTT client wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero.
Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26] and IETF RFC 4354 [55], that contains an application/poc-settings+xml MIME body the MCPTT client shall cache:
1) the <am-settings> element of the poc-settings+xml MIME body for each MCPTT client identified by the "id" attribute according to IETF RFC 4354 [55] as the current Answer-mode indication of that MPCTT client; and
2) the <selected-user-profile-index> element of the poc-settings+xml MIME body for each MCPTT client identified by the "id" attribute according to IETF RFC 4354 [55] as the active MCPTT service user profile of that MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.2.5 Receiving a CSK key download message | When the MCPTT client receives a SIP MESSAGE request containing:
1) a P-Asserted-Service header field containing the "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
2) an application/mikey MIME body;
Then, if the key identifier within the CSB-ID of the MIKEY payload is a CSK-ID (4 most-significant bits have the value '2'), the MCPTT client:
1) shall follow the security procedures in clause 9.2.1 of 3GPP TS 33.180 [78] to extract the CSK. The client:
a) if the initiator field (IDRi) has type 'URI' (identity hiding is not used), the client:
i) shall extract the initiator URI from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]. If the initiator URI deviates from the public service identity of the participating MCPTT function serving the MCPTT user, shall reject the SIP MESSAGE request with a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and include warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
ii) shall convert the initiator URI to a UID as described in 3GPP TS 33.180 [78];
b) if the initiator field (IDRi) has type 'UID' (identity hiding in use), the client:
ii) shall convert the public service identity of participating MCPTT function serving the MCPTT user to a UID as described in 3GPP TS 33.180 [78];
i) shall compare the generated UID with the UID in the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]. If the two initiator UIDs deviate from each other, shall reject the SIP MESSAGE request with a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and include warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
c) shall use the UID to validate the signature of the I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if authentication verification of the I_MESSAGE fails, shall reject the SIP MESSAGE request with a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and include warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
e) shall extract and decrypt the encapsulated CSK using the participating MCPTT function's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78]; and
f) shall extract the CSK-ID, from the payload as specified in 3GPP TS 33.180 [78];
2) Upon successful extraction, the client shall replace the existing CSK and CSK-ID associated with the participating MCPTT function, with the extracted CSK and CSK-ID in the 'key download' message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 7.3 MCPTT server procedures |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.