hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.5.3.1 Originating procedures | Upon receiving a "SIP MESSAGE request for private call call-back for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the "SIP MESSAGE request for private call call-back for originating participating MCPTT function" contains the <request-type> element set to a value of "private-call-call-back-request", and the <allow-request-private-call-call-back> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "151 user not authorised to make a private call call-back request" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps in this clause;
4) if the "SIP MESSAGE request for private call call-back for originating participating MCPTT function" contains the <request-type> element set to a value of "private-call-call-back-cancel-request", and the <allow-cancel-private-call-call-back> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "152 user not authorised to make a private call call-back cancel request" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps in this clause;
5) shall determine the public service identity of the controlling MCPTT function for the private call call-back service for the MCPTT user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function for the private call call-back service for the MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5);
8) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) shall copy the contents of the application/resource-lists+xml MIME body in the received SIP MESSAGE request into an application/resource-lists+xml MIME body in the outgoing SIP MESSAGE request;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
12) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
13) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
14) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 13), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, the participating MCPTT function shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.5.3.2 Terminating procedures | Upon receiving a "SIP MESSAGE request for private call call-back for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.5.4 Controlling MCPTT function procedures | Upon receiving a:
- "SIP MESSAGE request for private call call-back request for controlling MCPTT function";
- "SIP MESSAGE request for private call call-back cancel request for controlling MCPTT function"; or
- "SIP MESSAGE request for private call call-back responses for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or contains an application/resource-lists+xml MIME body with more than one total <entry> element in all <list> elements of the <resource-lists> element, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
8) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP MESSAGE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
9) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the MCPTT user to be invited or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
10) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6 Ambient listening call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.1 General | Clause 11.1.6 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for on-network ambient listening calls. The procedures as specified are applicable to both locally initiated and remotely initiated ambient listening call.
The procedures for originating an ambient listening call are initiated by the MCPTT user at the MCPTT client in the following circumstances:
- an authorised MCPTT user initiates an ambient listening call in order to listen to the terminating user; or
- an authorised MCPTT user initiates an ambient listening call in order to be listened to by the terminating user.
The procedures for releasing an ambient listening call are initiated by the MCPTT user at the MCPTT client in the following circumstances:
- a listening MCPTT user initiates the ambient listening call release; or
- a listened-to MCPTT user who was the originator of the ambient listening call initiates the ambient listening call release.
The procedures for releasing an ambient listening call by the controlling MCPTT function are initiated in the following circumstances:
- can be triggered by the MCPTT administrator by a mechanism outside of the scope of the standard; or
- can be triggered by a call terminating event occurring at the controlling MCPTT function such as a timer expiration. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.2 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.2.0 Ambient listening handling at the MCPTT client | The MCPTT client takes the actions needed to avoid letting the user detect that an ambient listening call is active. This includes:
- avoiding that the user is aware of the beginning of an ambient listening call, except an ambient listening call initiated by the user;
- avoiding that the user is aware of the end of an ambient listening call, except an ambient listening call initiated by the user;
- avoiding that the user is aware of the ongoing progress of an ambient listening call, even an ambient listening call initiated by the user; and
- avoiding changes in the display of information, visual, audible, or haptic, that might occur or might be absent if the ambient call was not active. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.2.1 On-demand ambient listening call | 11.1.6.2.1.1 Client originating procedures
Upon receiving a request from the MCPTT user to originate a remote initiated ambient listening call, if the <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from the MCPTT user to originate a locally initiated ambient listening call, if the <allow-request-locally-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from an MCPTT user to establish an MCPTT ambient listening call that has been authorised successfully by the requesting MCPTT client, the MCPTT client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) shall set the Request-URI of the SIP INVITE request to a public service identity of the participating MCPTT function serving the MCPTT user;
2) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4];
3) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16];
4) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP INVITE request;
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref contain with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "ambient-listening";
8) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <ambient-listening-type> element set to a value of:
a) "local-init", if the MCPTT user has requested a locally initiated ambient listening call; or
b) "remote-init", if the MCPTT user has requested a remotely initiated ambient listening call;
9) shall insert in the SIP INVITE request an application/resource-lists+xml MIME body with the MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20];
NOTE 1: the targeted MCPTT user is the listened-to MCPTT user in the case of a remotely initiated ambient listening call or the listening MCPTT user in the case of a locally initiated listening call.
10) if an end-to-end security context needs to be established then:
a) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [78];
b) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78];
c) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];
d) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID and KMS URI of the invited user and a time related parameter as described in 3GPP TS 33.180 [78];
e) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];
f) shall add the MCPTT ID of the originating MCPTT user to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; and
g) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user's signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78];
11) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarification given in clause 6.2.1 and with a media stream of the offered media-floor control entity;
12) if this is a locally initiated ambient listening call, shall comply with the conditions for implicit floor control as specified in clause 6.4;
13) if this is a remotely initiated ambient listening call, shall comply with the conditions for an implicit request to grant the floor to the terminating MCPTT client as specified in clause 6.4;
14) shall include in the SIP INVITE request a Priv-Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [18]; and
15) shall send the SIP INVITE request towards the participating MCPTT function according to 3GPP TS 24.229 [4].
Upon receiving a SIP 183(Session Progress) response to the SIP INVITE request the MCPTT client:
1) if the SIP 183(Session Progress) response includes an alert-info header field as specified in IETF RFC 3261 [24] and as updated by IETF RFC 7462 [77] set to a value of "<file:///dev/null>" shall not give any indication of the progress of the call setup to the MCPTT user; and
NOTE 2: The alert-info header field having the value of "<file:///dev/null>" is intended to result in having a "null" alert, i.e. an alert with no content or physical manifestation of any kind.
2) if this is a remotely initiated ambient listening call, may indicate the progress of the session establishment to the inviting MCPTT user.
Upon receiving a SIP 200 (OK) response to the SIP INVITE request the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) if this is a remotely initiated ambient listening call, shall notify the user that the call has been successfully established;
3) if this is a locally initiated ambient listening call, shall not provide any indication to the user that the call has been successfully established;
4) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the sent SIP INVITE request was set to a value of "local-init":
a) shall cache the value of "listened-to MCPTT user" as the ambient listening client role for this call; or
b) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body was set to a value of "remote-init" shall cache the value of "listening MCPTT user" as the ambient listening client role for this call; and
5) shall cache the value contained in the <ambient-listening-type> element of the application/vnd.3gpp.mcptt-info+xml MIME body set in step 8) as the ambient listening type of this call.
11.1.6.2.1.2 Client terminating procedures
Upon receipt of an initial SIP INVITE request, the MCPTT client shall follow the procedures for termination of multimedia sessions in the IM CN subsystem as specified in 3GPP TS 24.229 [4] with the clarifications below.
The MCPTT client:
1) may reject the SIP INVITE request if either of the conditions in step a) or b) are met:
a) MCPTT client is already occupied in another session and the number of simultaneous sessions exceeds <MaxCall>, the maximum simultaneous MCPTT session for private call, as specified in TS 24.484 [50]; or
b) MCPTT client does not have enough resources to handle the call;
c) if neither condition a) nor b) are met, continue with the rest of the steps;
2) if the SIP INVITE request is rejected in step 1):
a) shall respond towards the participating MCPTT function either with:
i) an appropriate reject code as specified in 3GPP TS 24.229 [4] and warning texts as specified in clause 4.4.2; or
ii) with a SIP 480 (Temporarily unavailable) response not including warning texts if the user is authorised to restrict the reason for failure according to <allow-failure-restriction> as specified in 3GPP TS 24.484 [50]; and
b) skip the rest of the steps of this clause;
3) if the SDP offer of the SIP INVITE request contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:
a) shall extract the MCPTT ID of the originating MCPTT user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
b) shall convert the MCPTT ID to a UID as described in 3GPP TS 33.180 [78];
c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if authentication verification of the MIKEY-SAKKE I_MESSAGE fails, shall reject the SIP INVITE 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
e) if the signature of the MIKEY-SAKKE I_MESSAGE was successfully validated:
i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78]; and
ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
NOTE 1: With the PCK successfully shared between the originating MCPTT client and the terminating MCPTT client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.
4) may check if a Resource-Priority header field is included in the incoming SIP INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
5) shall perform the automatic commencement procedures specified in clause 6.2.3.1.1;
NOTE 2: Auto-answer is the commencement mode for both participants in locally initiated and remotely initiated ambient listening calls.
6) if the received SIP INVITE request includes an alert-info header field as specified in IETF RFC 3261 [24] and as updated by IETF RFC 7462 [77] set to a value of "<file:///dev/null>" shall not give any indication of the progress of the call to the MCPTT user;
NOTE 3: The alert-info header field having the value of "<file:///dev/null>" is intended to result in having a "null" alert, i.e. an alert with no content or physical manifestation of any kind.
7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request was set to a value of "remote-init":
a) shall cache the value of "listened-to MCPTT user" as the ambient listening client role for this call;
NOTE 4: The terminating user in a remotely initiated ambient listening is the listened-to MCPTT user and is intended to be totally unaware that their microphone is activated and a call is in progress.
8) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request was set to a value of "local-init":
a) shall cache the value of "listening MCPTT user" as the ambient listening client role for this call;
b) should provide an indication to the MCPTT user that the ambient listening call is in progress; and
c) may display to the MCPTT user the MCPTT ID of the inviting MCPTT user; and
9) shall cache as the ambient listening type for the call the value contained in the <ambient-listening-type> element of the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP INVITE request.
11.1.6.2.1.3 Client release origination procedure
Upon receiving a request from an MCPTT user to release an MCPTT ambient listening call:
The MCPTT client:
1) if the MCPTT client has not received a g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93] in:
a) a received SIP INVITE request for the ambient listening call; or
b) a received SIP 200 (OK) response to a sent SIP INVITE request for the ambient listening call;
then shall skip the rest of the steps;
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
3) shall generate a SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4] and IETF RFC 6086 [64]; and
4) shall send the SIP BYE request within the dialog of the MCPTT ambient call session as specified in 3GPP TS 24.229 [4].
Upon receipt of the SIP 200 (OK) response to the SIP BYE request the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call has been terminated;
3) if the cached ambient listening client role is equal to "listening MCPTT user", may provide an indication to the MCPTT user that the ambient listening call has been terminated; and
4) shall clear the cache of the data stored as:
a) ambient listening client role; and
b) ambient listening type.
11.1.6.2.1.4 Client session release termination procedure
This clause is referenced from other procedures.
Upon receipt of a SIP BYE request in the dialog of an ambient listening session, the MCPTT client:
1) shall comply with the procedures of clause 6.2.6;
2) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call has been terminated;
3) if the cached ambient listening client role is equal to "listening MCPTT user", may provide an indication to the MCPTT user that the ambient listening call has been terminated; and
4) shall clear the cache of the data stored as:
a) ambient listening client role; and
b) ambient listening type. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.2.2 Ambient listening call using pre-established session | 11.1.6.2.2.1 Client originating procedures
Upon receiving a request from the MCPTT user to originate a remote initiated ambient listening call, if the <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from the MCPTT user to originate a locally initiated ambient listening call, if the <allow-request-locally-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT client shall inform the MCPTT user and shall exit this procedure.
Upon receiving a request from an MCPTT user to establish an MCPTT ambient listening call that has been authorised successfully by the requesting MCPTT client within a pre-established session, the MCPTT client shall generate a SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27], with the clarifications given below.
If an end-to-end security context needs to be established the MCPTT client:
1) if necessary, shall instruct the key management client to request keying material from the key management server as described in 3GPP TS 33.180 [78];
2) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78];
3) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];
4) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID of the invited user and a time related parameter as described in 3GPP TS 33.180 [78];
5) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];
6) shall add the MCPTT ID of the originating MCPTT user to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]; and
7) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user's signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78].
The MCPTT client populates the SIP REFER request as follows:
1) shall include the Request-URI set to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
2) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
3) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
4) shall include the option tag "multiple-refer" in the Require header field;
5) may include a P-Preferred-Identity header field in the SIP REFER request containing a public user identity as specified in 3GPP TS 24.229 [4];
6) shall include a P-Preferred-Service header field set to the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), according to IETF RFC 6050 [9];
7) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20], and with the Content-ID header field set to this "cid" URL;
8) shall include in the application/resource-lists+xml MIME body a single <entry> element in a <list> element of the <resource-lists> element where the single <entry> element contains a "uri" attribute set to the MCPTT ID of the targeted user, extended with hname "body" parameter containing:
a) an application/vnd.3gpp.mcptt-info MIME body containing:
i) a <session-type> element set to "ambient-listening";
ii) if the MCPTT user has requested a locally initiated ambient listening call, an <ambient-listening-type> element set to a value of "local-init"; or
iii) if the MCPTT user has requested a remotely initiated ambient listening call, an <ambient-listening-type> element set to a value of "remote-init";
b) a Priv-Answer-Mode header field with the value "Auto" according to the rules and procedures of IETF RFC 5373 [18];
c) if the SDP parameters of the pre-established session do not contain a media-level section of a media-floor control entity or if end-to-end security is required for the ambient listening call, an application/sdp MIME body containing the SDP parameters of the pre-established session according to 3GPP TS 24.229 [4] with the clarification given in clause 6.2.1;
d) if this is a locally initiated ambient listening call, shall comply with the conditions for implicit floor control as specified in clause 6.4;
e) if this is a remotely initiated ambient listening call, shall comply with the conditions for an implicit request to grant the floor to the terminating MCPTT client as specified in clause 6.4; and
f) if implicit floor control is to be requested per clause 6.4, then:
i) the application/sdp MIME body shall contain an implicit floor request as specified in clause 6.4; and
ii) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
9) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session.
The MCPTT client shall send the SIP REFER request towards the MCPTT server according to 3GPP TS 24.229 [4].
Upon receiving a final SIP 2xx response to the SIP REFER request the MCPTT client:
1) shall interact with media plane as specified in 3GPP TS 24.380 [5]; and
2) if this is a locally initiated ambient listening call, shall not provide any indication to the user that the call setup is in progress.
On call establishment by interaction with the media plane as specified in clause 9.2.2 of 3GPP TS 24.380 [5] if the sent SIP REFER request the MCPTT client:
1) if the MCPTT user has requested a locally initiated ambient listening call shall provide no indication to the MCPTT user that the ambient listening call has been successfully established; and
2) if the MCPTT user has requested a remotely initiated ambient listening call shall provide an indication to the MCPTT user that the ambient listening call has been successfully established.
3) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the sent SIP REFER request was set to a value of "local-init":
a) shall cache the value of "listened-to MCPTT user" as the ambient listening client role for this call; or
b) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body was set to a value of "remote-init" shall cache the value of "listening MCPTT user" as the ambient listening client role for this call; and
4) shall cache the value contained in the <ambient-listening-type> element of the application/vnd.3gpp.mcptt-info+xml MIME body set in step 8) as the ambient listening type of this call.
11.1.6.2.2.2 Client terminating procedures
The MCPTT client shall follow the procedures for termination of multimedia sessions for ambient listening calls as specified in clause 11.1.6.2.1.2.
NOTE: The terminating MCPTT client in an ambient listening call receives a SIP INVITE request with Replaces header field when using a pre-established session.
11.1.6.2.2.3 Client release origination procedure
Upon receiving a request from an MCPTT user to release an MCPTT ambient listening call when using a pre-established MCPTT session:
The MCPTT client:
1) if the MCPTT client has not received a g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93] in:
a) a received SIP INVITE request for the ambient listening call; or
b) a received SIP 200 (OK) response to a sent SIP INVITE request or SIP REFER request for the ambient listening call;
then shall skip the rest of the steps; and
2) shall perform the actions specified in clause 6.2.5.2.
If the procedures of clause 6.2.5.2 were successful:
1) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call has been terminated;
2) if the cached ambient listening client role is equal to "listening MCPTT user", may provide an indication to the MCPTT user that the ambient listening call has been terminated; and
3) shall clear the cache of the data stored as:
a) ambient listening client role; and
b) ambient listening type.
11.1.6.2.2.4 Reception of SIP INFO request with release-reason
Upon receiving a SIP INFO request containing an application/vnd.3gpp.mcptt-info+xml MIME body containing a <release-reason> element, the MCPTT client:
1) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call is being terminated;
2) if the cached ambient listening client role is equal to "listening MCPTT user", should provide an indication to the MCPTT user that an ambient listening call is being terminated;
3) shall generate and send a SIP 200 OK response to the SIP INFO request according to 3GPP TS 24.229 [4]; and
4) shall comply with the procedures of clause 11.1.6.2.2.5.
11.1.6.2.2.5 Client session release termination procedure
This clause is referenced from other procedures.
Upon receiving an interaction with the media plane indicating release of the ambient listening call but preservation of the pre-established session as specified in clause 9.2 of 3GPP TS 24.380 [5], the MCPTT client:
1) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call has been terminated;
2) if the cached ambient listening client role is equal to "listening MCPTT user", may provide an indication to the MCPTT user that the ambient listening call has been terminated; and
3) shall clear the cache of the data stored as:
a) ambient listening client role; and
b) ambient listening type. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.3.1 Originating procedures | 11.1.6.3.1.1 On-demand ambient listening call
Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "ambient-listening", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall not continue with the rest of the steps;
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the <ambient-listening-type> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of:
a) "remote-init" and an <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false"; or
b) "local-init" and an <allow-request-locally-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response, with warning text set to "user not authorised to make an ambient listening call" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
5) shall determine the public service identity of the controlling MCPTT function for the ambient listening call service associated with the originating user's MCPTT ID identity. If the participating MCPTT function is unable to identify the controlling MCPTT function for the ambient listening call service associated with the originating user's MCPTT ID identity, it shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text "142 unable to determine the controlling function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function for the ambient listening call service associated with the originating user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) if the incoming SIP INVITE request does not contain an application/resource-lists+xml MIME body or contains an application/resource-lists+xml MIME body with more than one <entry> element in all <list> elements of the <resource-lists> element, shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
7) if the <allow-private-call> element of the <ruleset> element is not present in the MCPTT user profile document on the participating MCPTT function or is present with the value "false" (see the MCPTT user profile document in 3GPP TS 24.484 [50]), indicating that the user identified by the MCPTT ID is not authorised to initiate private calls, shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response, with warning text set to "107 user not authorised to make private calls" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
8) if the <PrivateCall> element exists in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]) and:
a) if the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body does not match with the "uri" attribute of one of the <entry> elements of the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); and
b) if configuration is not set in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) that allows the MCPTT user to make a private call to users not contained within the <entry> elements of the <PrivateCall> element;
then:
a) shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "144 user not authorised to call this particular user" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
9) shall validate the media parameters and if the MCPTT speech codec is not offered in the "SIP INVITE request for originating participating MCPTT function" shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
10) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3;
11) shall set the Request-URI to the public service identity of the controlling MCPTT function determined in step 5);
12) shall set the <mcptt-calling-user-id> element in an application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user;
13) if the Priv-Answer-Mode header field specified in IETF RFC 5373 [18] was received in the incoming SIP INVITE request with a value of "Auto" or if no Priv-Answer-Mode header field was received in the incoming SIP INVITE request or a Priv-Answer-Mode header field was received containing a value other than "Auto", shall include the Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request;
14) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received "SIP INVITE request for originating participating MCPTT function", as specified in clause 6.3.2.1.1.1;
15) if, according to clause 6.4, the SIP INVITE request is regarded as being received with an implicit request to grant the floor to the originating MCPTT client:
if:
a) the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP INVITE request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has available the location of the originating MCPTT client; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
16) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP INVITE request, the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2;
2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
3) shall include Warning header field(s) received in the incoming SIP 200 (OK) response;
4) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
5) shall include an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response;
6) shall include the answer state into the P-Answer-State header field of the outgoing SIP 200 (OK) response, if received in the P-Answer-State header field of the incoming SIP 200 (OK) response;
7) shall send the SIP 200 (OK) response to the inviting MCPTT client according to 3GPP TS 24.229 [4]; and
8) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
11.1.6.3.1.2 Receipt of SIP BYE request for on-demand ambient listening call
Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function:
1) shall follow the procedures as specified in clause 11.1.3.2.1.1.
11.1.6.3.1.3 Receipt of REFER "BYE" request for private call using pre-established session
Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
11.1.6.3.1.4 Ambient listening call initiation using pre-established session
Upon receipt of a "SIP REFER request for a pre-established session", with:
1) the Refer-To header field containing a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20] containing one <entry> element in a <list> element of the <resource-lists> element with a "uri" attribute containing a SIP URI set to the MCPTT ID of the called user(s);
2) a "body" parameter of the SIP URI specified above containing an application/vnd.3gpp.mcptt-info MIME body with the <session-type> element set to "ambient-listening"; and
3) a Content-ID header field set to the "cid" URL;
the participating function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall not continue with the rest of the steps;
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP REFER request;
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP REFER request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the received SIP REFER request does not contain an application/resource-lists+xml MIME body referenced by a "cid" URL in the Refer-To header field, shall reject the "SIP REFER request for pre-established session" with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
5) if the received SIP REFER request contains an application/resource-lists+xml MIME body referenced by a "cid" URL in the Refer-To header field with more than one total <entry> element in all <lists> elements of the <resource-lists> element where each <entry> element contains an application/vnd.3gpp.mcptt-info MIME body with the <session-type> element, shall reject the "SIP REFER request for pre-established session" with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
6) if the received SIP REFER request contains an application/resource-lists+xml MIME body referenced by a "cid" URL in the Refer-To header field with only one <entry> element in all <list> elements of the <resource-lists> element where the <entry> element contains an application/vnd.3gpp.mcptt-info MIME body with the <session-type> element not set to "ambient-listening", shall reject the "SIP REFER request for pre-established session" with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
7) if the <ambient-listening-type> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP REFER request is set to a value of:
a) "remote-init" and an <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false"; or
b) "local-init" and an <allow-request-locally-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then shall reject the "SIP REFER request for a pre-established session" with a SIP 403 (Forbidden) response, with warning text set to "154 The MCPTT user is not authorised to make an ambient listening call" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
8) shall determine the public service identity of the controlling MCPTT function for the ambient listening call service associated with the originating user's MCPTT ID;
NOTE 1: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the participating MCPTT function determines the public service identity of the controlling MCPTT function for the ambient listening call serviceassociated with the originating user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
9) if the participating MCPTT function is unable to identify the controlling MCPTT function for the ambient listening call service associated with the originating user's MCPTT ID, it shall reject the REFER request with a SIP 404 (Not Found) response with the warning text "142 unable to determine the controlling function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
10) if the <allow-private-call> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) on the participating MCPTT function or is present with the value "false", indicating that the user identified by the MCPTT ID is not authorised to initiate private calls, shall reject the "SIP REFER request for pre-established session" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "107 user not authorised to make private calls" in a Warning header field as specified in clause 4.4;
11) if the <PrivateCall> element exists in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]) and:
a) the "uri" attribute of each and every <entry> element of all the <list> elements of the <resource-lists> element of the application/resource-lists+xml MIME body referenced by a "cid" URL in the Refer-To header field do not match with any of the <entry> elements of the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); and
b) if configuration is not set in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) that allows the MCPTT user to make a private call to users not contained within the <entry> elements of the <PrivateCall> element;
then:
a) shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "144 user not authorised to call this particular user" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
12) if the "SIP REFER request for a pre-established session" contained a Refer-Sub header field containing "false" value and a Supported header field containing "norefersub" value, shall handle the SIP REFER request as specified in 3GPP TS 24.229 [4], IETF RFC 3515 [25] as updated by IETF RFC 6665 [26], and IETF RFC 4488 [22] without establishing an implicit subscription;
13) shall generate a final SIP 200 (OK) response to the "SIP REFER request for a pre-established session" according to 3GPP TS 24.229 [4];
NOTE 6: In accordance with IETF RFC 4488 [22], the participating MCPTT function inserts the Refer-Sub header field containing the value "false" in the SIP 200 (OK) response to the SIP REFER request to indicate that it has not created an implicit subscription.
14) shall include in the SIP 200 (OK) response the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93];
NOTE 7: The originator of the ambient listening call is either the initiator of a "remote-init" ambient listening type call or the originator of a "local-init" ambient listening type call. In either case, the originating user is allowed to release the ambient listening call.
15) shall send the response to the "SIP REFER request for a pre-established session" towards the MCPTT client according to 3GPP TS 24.229 [4];
16) shall generate a SIP INVITE request as specified in clause 6.3.2.1.4;
17) shall include a Priv-Answer-Mode header field set to a value of "Auto" in the outgoing SIP INVITE request;
18) shall set the Request-URI of the SIP INVITE request to the public service identity of the controlling MCPTT function as determined above in step 7);
NOTE 8: The participating MCPTT function will leave verification of the Resource-Priority header field to the controlling MCPTT function.
18a) if, according to clause 6.4, the SIP REFER request is regarded as being received with an implicit request to grant the floor to the initiating MCPTT client:
if:
a) the incoming SIP REFER request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP REFER request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has available the location of the initiating MCPTT client; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
19) shall forward the SIP INVITE request according to 3GPP TS 24.229 [4].
Upon receiving SIP provisional responses for the SIP INVITE request the participating MCPTT function:
1) shall discard the received SIP responses without forwarding them.
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the participating MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request in step 21) the participating MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.3.2 Terminating procedures | 11.1.6.3.2.1 Terminating procedures for ambient listening call
Upon receipt of a "SIP INVITE request for terminating participating MCPTT function", the participating MCPTT function:
NOTE: The procedures in the present clause are applicable for both on-demand and pre-established sessions.
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24], and shall not continue with the rest of the steps;
2) shall check the presence of the isfocus media feature tag in the Contact header field and if it is not present then the participating MCPTT function shall reject the request with a SIP 403 (Forbidden) response with the warning text set to "104 isfocus not assigned" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
3) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request to retrieve the binding between the MCPTT ID and public user identity;
4) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP INVITE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
5) when the called user identified by the MCPTT ID is unable to participate in private calls as identified in the called user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) on the terminating participating MCPTT function, shall reject the "SIP INVITE request for terminating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "127 user not authorised to be called in private call" in a Warning header field as specified in clause 4.4; and
6) shall perform the automatic commencement procedures specified in clause 6.3.2.2.5.1 and according to IETF RFC 5373 [18].
11.1.6.3.2.2 Receipt of SIP BYE request for on-demand ambient listening call
Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 11.1.3.2.2.1.
11.1.6.3.2.3 Receipt of SIP BYE request for an ongoing pre-established session
Upon receiving a SIP BYE request from the controlling MCPTT function for an ambient listening call and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function:
1) if the SIP BYE request contains an application/vnd.3gpp.mcptt-info+xml MIME body:
a) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [4] and IETF RFC 6086 [64];
b) shall include the Info-Package header field set to g.3gpp.mcptt-info in the SIP INFO request;
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP BYE request to the SIP INFO request; and
d) shall send the SIP INFO request towards the targeted MCPTT client in the dialog of the pre-established session according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response for the sent SIP INFO request, shall perform the procedures specified in clause 11.1.3.2.2.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.4 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.4.1 Originating procedures | This clause describes the procedures for inviting an MCPTT user to an MCPTT ambient listening session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 11.1.6.4.2
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
NOTE 1: As a result of calling clause 6.3.3.1.2, the <mcptt-calling-user-id> containing the calling user's MCPTT ID is copied into the outgoing SIP INVITE.
2) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP INVITE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request;
3) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited;
NOTE 2: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: 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 4: 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 5: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the MCPTT user to be invited or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
4) shall include a P-Asserted-Identity header field in the outgoing SIP INVITE request set to 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;
6) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "local-init", shall include the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93];
NOTE 7: The only case where the terminating user can release the ambient listening call is when the terminating client is the "listening MCPTT user";
7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init", shall include in the outgoing SIP INVITE request an alert-info header field set to a value of "<file:///dev/null>" according to IETF RFC 3261 [24];
8) shall send the SIP INVITE request towards the core network according to 3GPP TS 24.229 [4]; and
9) shall start a private call timer with a value set to the configured max private call duration for the user.
Upon receiving SIP 200 (OK) response for the SIP INVITE request, the controlling MCPTT function:
1) shall cache the contact received in the Contact header field; and
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
Upon expiry of the private call timer, the controlling MCPTT function shall follow the procedure for releasing the ambient listening call session as specified in clause 11.1.6.4.3, with the clarification that the <release-reason> element included in the SIP BYE request shall be set to "private-call-timer-expiry". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.4.2 Terminating procedures | Upon receiving of a "SIP INVITE request for controlling MCPTT function of an ambient listening call" the controlling MCPTT function:
1) shall check whether the public service identity contained in the Request-URI is allocated for ambient listening call and perform the actions specified in clause 6.3.7.1 if it is not allocated and skip the rest of the steps;
2) shall perform actions to verify the MCPTT ID of the inviting MCPTT user in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request, and authorise the request according to local policy; and
3) if the request is not authorised as determined by step 2) above, the controlling MCPTT function shall return a SIP 403 (Forbidden) response with the warning text as specified in "Warning header field" and skip the rest of the steps;
4) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec or media format is acceptable by the controlling MCPTT function and if not, reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps;
5) shall perform actions as described in clause 6.3.3.2.2;
6) shall allocate an MCPTT session identity for the MCPTT ambient listening call session; and
7) shall invite the MCPTT user listed in the application/resource-lists+xml MIME body of received SIP INVITE request as specified in clause 11.1.6.4.1.
Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 11.1.6.4.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], the controlling MCPTT function supports media buffering and the SIP final response is not yet sent to the inviting MCPTT client, the controlling MCPTT function:
1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2;
2) shall include 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;
3) shall include a P-Answer-State header field with the value "Unconfirmed";
4) shall include in the SIP 200 (OK) response the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93];
NOTE 1: The originator of the ambient listening call is either the initiator of a "remote-init" ambient listening type call or the originator of a "local-init" ambient listening type call. In either case, the originating user is allowed to release the ambient listening call.
5) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
6) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4];
7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init":
a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listening MCPTT user of the ambient listening call and cache the MCPTT ID contained in the application/resource-lists+xml MIME body of the received SIP INVITE request as the listened-to MCPTT user; and
b) shall cache the ambient listening type of the ambient listening call as "remote-init"; and
8) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "local-init":
a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listened-to MCPTT user of the ambient listening call and cache the MCPTT ID contained in the application/resource-lists+xml MIME body of received SIP INVITE request as the listening MCPTT user; and
b) shall cache the ambient listening type of the ambient listening call as "local-init".
If the procedures of clause 11.1.6.4.1 were successful in inviting the MCPTT user listed in the application/resource-lists+xml MIME body of received SIP INVITE request and the SIP final response is not yet sent to the inviting MCPTT client, the controlling MCPTT function:
1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps;
2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.2;
3) shall include in the SIP 200 (OK) response the g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93];
NOTE 2: The originator of the ambient listening call is either the initiator of a "remote-init" ambient listening type call or the originator of a "local-init" ambient listening type call. In either case, the originating user is allowed to release the ambient listening call.
4) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
5) shall send a SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4];
6) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "remote-init":
a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listening MCPTT user of the ambient listening call and cache the MCPTT ID contained in the application/resource-lists+xml MIME body of the received SIP INVITE request as the listened-to MCPTT user; and
b) shall cache the ambient listening type of the ambient listening call as "remote-init"; and
7) if the <ambient-listening-type> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP INVITE request is set to a value of "local-init":
a) shall cache the MCPTT ID contained in the <mcptt-calling-user-id> element of the received SIP INVITE request as the listened-to MCPTT user of the ambient listening call and cache the MCPTT ID contained in the application/resource-lists+xml MIME body of received SIP INVITE request as the listening MCPTT user; and
b) shall cache the ambient listening type of the ambient listening call as "local-init".
If the procedures of clause 11.1.6.4.1 were not successful in inviting the MCPTT user listed in the application/resource-lists+xml MIME body of received SIP INVITE request, the controlling MCPTT function shall reject the received SIP INVITE request with a SIP 480 (Temporarily Unavailable) response and skip the remaining procedures of the present clause.
The controlling MCPTT function shall forward any other SIP response that does not contain SDP, including any MIME bodies contained therein, along the signalling path to the originating network according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.4.3 Server initiated ambient call release | The ambient listening call release is triggered by an MCPTT administrator by a mechanism outside of the scope of the standard, or directly by the controlling MCPTT function as a result of an event as specified in clause 10.14.3.3 of 3GPP TS 23.379 [3].
This clause is referenced from other procedures.
Upon receipt of a trigger to release an ongoing ambient listening call identified by the MCPTT ID of the listening MCPTT user, the MCPTT ID of the listened-to MCPTT user and the ambient listening type of the call, the controlling MCPTT function:
1) shall identify the MCPTT sessions of the listening MCPTT user and the MCPTT ID of the listened-to MCPTT user for the ambient listening call to be released;
2) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for the MCPTT session release;
3) shall generate a SIP BYE request according to rules and procedures of 3GPP TS 24.229 [4] to be sent in the dialog for the ambient listening call with the MCPTT client of the listened-to MCPTT user; and
4) shall send the SIP BYE request in the dialog for the ambient listening call with the MCPTT client of the listened-to MCPTT user.
Upon receipt of a SIP 200 (OK) response to the SIP BYE request the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] for the MCPTT session release;
2) shall generate a SIP BYE requests according to 3GPP TS 24.229 [4];
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body in the SIP BYE request including a <release-reason> element set to a value of:
a) "administrator-action" if triggered by an MCPTT administrator;
b) "private-call-expiry" if the ambient listening call is released due to the expiry of the private call timer;
c) "call-request-for-listened-to-client" if there is a call request targeted to the listened-to client; or
d) "call-request-initiated-by-listened-to-client" if there is a call request initiated by the listened-to client; and
4) shall send the SIP BYE requests in the dialog for the ambient listening call with the MCPTT client of the listening MCPTT user according to3GPP TS 24.229 [4].
Upon receipt of a SIP 200 (OK) response to the SIP BYE request sent to MCPTT client of the listening MCPTT user the controlling MCPTT function:
1) shall delete the following cached data for the ambient listening call:
a) the MCPTT ID of the listened-to MCPTT user
b) the MCPTT ID of the listening MCPTT user; and
c) the ambient listening type.
Upon receipt of a SIP 200 (OK) response to the 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 media plane resources associated with the SIP sessions with the MCPTT clients;
2) shall delete the following cached data for the ambient listening call:
a) the MCPTT ID of the listened-to MCPTT user;
b) the MCPTT ID of the listening MCPTT user; and
c) the value of the ambient listening type. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.6.4.4 Reception of a SIP BYE request | Upon receipt of a SIP BYE request for an ambient listening session 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;
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
3) shall send the SIP BYE request in the dialog of the other participant in the ambient listening call according to3GPP TS 24.229 [4];
4) shall generate a SIP BYE request according to 3GPP TS 24.229 [4]; and
5) shall send the SIP BYE request in the dialog of the participant in the ambient listening call according to3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the sent 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 media plane resources associated with the SIP session with the MCPTT ambient listening call participant;
2) shall generate a SIP 200 (OK) response to the received SIP BYE request and send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4]; and
3) shall delete the following cached data for the ambient listening call:
a) the MCPTT ID of the listened-to MCPTT user;
b) the MCPTT ID of the listening MCPTT user; and
c) the value of the ambient listening type. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7 Remotely initiated private call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.1 General | Clause 11.1.7 describes the MCPTT client procedures, the participating MCPTT function procedures and the controlling MCPTT function procedures for the on-network remotely initiated private call functionality.
In the procedures of clause 11.1.7.2, clause 11.1.7.3, and clause 11.1.7.4:
- the term "requesting MCPTT user" is used to refer to the MCPTT user who sent a request to initiate a remotely initiated private call;
- the term "remote MCPTT user" is used to refer to the MCPTT user who is sent a request to initiate a remotely initiated private call; and
- the term "identified MCPTT user" is used to refer to the MCPTT user to be invited to the remotely initiated private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.2.1 Remotely initiated private call initiation request procedures | Upon receiving a request from the requesting MCPTT user to send a remotely initiated private call request to the remote MCPTT user to originate a private call to an identified MCPTT user, the MCPTT client:
1) if:
a) the <allow-request-remote-init-private-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) should indicate to the requesting MCPTT user that the requesting MCPTT user is not authorised to initiate a remotely initiated private call request to the remote MCPTT user; and
b) shall skip the rest of the steps of the present clause;
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-called-party-id> element set to the MCPTT ID of the identified MCPTT user of the remotely initiated private call; and
ii) an <anyExt> element containing:
A) the <request-type> element set to a value of "remotely-initiated-private-call-request";
B) the <notify-remote-user> element set to a value of "true" if the requesting MCPTT user has indicated that the remote MCPTT user be notified of the remotely initiated private call request;
C) the <notify-remote-user> element set to a value of "false" if the requesting MCPTT user has indicated that the remote MCPTT user not be notified of the remotely initiated private call request;
D) may include <ric-app-level-priority> element set to a value of the namespace and priority values as specified in IETF RFC 8101 [48] and MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) to be used by the remote MCPTT user to request an application level priority while initiating a call as a result of received remotely initiated call request; and
E) may include <ric-commencement-mode> element set to:
I) a value of "force-auto-mode", if the requesting MCPTT user has indicated that the remote MCPTT user to request the force of automatic commencement mode at the invited MCPTT client while initiating a call as a result of received remotely initiated call request;
II) a value of "auto-mode", if the requesting MCPTT user has indicated that the remote MCPTT user to request the automatic commencement mode at the invited MCPTT client while initiating a call as a result of received remotely initiated call request; or
III) a value of "manual-mode", if the requesting MCPTT user has indicated that the remote MCPTT user to request the manual commencement mode at the invited MCPTT client while initiating a call as a result of received remotely initiated call request;
e) shall insert in the SIP MESSAGE request a application/resource-lists+xml MIME body with the MCPTT ID of the remote MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and
f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
3) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the requesting MCPTT user the failure of the sent remotely initiated private call request and not continue with the rest of the steps.
Upon receiving a "SIP MESSAGE request for remotely initiated private call response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent remotely initiated private call request from the value of the <remotely-initiated-call-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
2) should indicate to the requesting MCPTT user the success or failure of the sent remotely initiated private call request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.2.2 Remote client procedures for handling remotely initiated private call request | Upon receiving a "SIP MESSAGE request for remotely initiated private call request for terminating client", the MCPTT client:
1) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "true", may indicate to the remote MCPTT user that a remotely initiated private call request to call the identified MCPTT user has been received;
2) shall extract the MCPTT ID of the identified MCPTT user from the <mcptt-called-party-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;
3) if according to local policy on-demand sessions are to be used for remotely initiated private calls, shall invoke the procedures of clause 11.1.1.2.1.1 to originate an MCPTT private call to the identified MCPTT user with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated private call request to call the identified MCPTT user has been received; and
ii) if a SIP 180 (Ringing) response or SIP 183 (Session Progress) response is received to the to the sent SIP INVITE request, shall not give any indication to the remote MCPTT user that the remotely initiated private call origination is in progress;
b) if the <ric-app-level-priority> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP INVITE request with the value received in the <ric-app-level-priority> element; and
c) if the <ric-commencement-mode> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to:
i) a value of "force-auto-mode", may include in the initial SIP INVITE request a privileged answer mode with auto commencement mode (i.e. a Priv-Answer-Mode header field with the value "Auto") to force of automatic commencement mode at the invited MCPTT client;
ii) a value of "auto-mode", may include in the initial SIP INVITE request a answer mode with auto commencement mode (i.e. a Answer-Mode header field with the value "Auto") to request automatic commencement mode at the invited MCPTT client; or
iii) a value of "manual-mode", may include in the initial SIP INVITE request a answer mode with manual commencement mode (i.e. a Answer-Mode header field with the value "Manual") to request manual commencement mode at the invited MCPTT client; and
4) if according to local policy pre-established sessions are to be used for remotely initiated private calls and a pre-established session is available, shall invoke the procedures of clause 11.1.1.2.2.1 to originate an MCPTT private call to the identified MCPTT user with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated private call request to call the identified MCPTT user has been received; and
ii) shall not give any indication to the remote MCPTT user that the remotely initiated private call origination is in progress.
b) if the <ric-app-level-priority> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP REFER request with the value received in the <ric-application-level-priority> element; and
c) if the <ric-commencement-mode> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set:
i) to value of "force-auto-mode", may include in the initial SIP REFER request a privileged answer mode with auto commencement mode (i.e. a Priv-Answer-Mode header field with the value "Auto") to force of automatic commencement mode at the invited MCPTT client;
ii) to value of "auto-mode", may include in the initial SIP REFER request a answer mode with auto commencement mode (i.e. a Answer-Mode header field with the value "Auto") to request automatic commencement mode at the invited MCPTT client; or
iii) to value of "manual-mode", may include in the initial SIP REFER request to answer mode with manual commencement mode (i.e. a Answer-Mode header field with the value "Manual") to request manual commencement mode at the invited MCPTT client.
Upon completion of the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1, the MCPTT client:
1) if:
a) the MCPTT ID of the identified MCPTT user is identical to the <mcptt-calling-user-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request: and
b) the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user;
then:
a) shall skip the remaining steps of the current clause;
NOTE: In this case, it is not necessary to send a response to the sender of the remotely initiated private call request as the sender and the terminating party of the successful private call origination are the same user and will be aware of the request's outcome.
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and
e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-called-party-id> set to the MCPTT ID of the identified MCPTT user called by the remote MCPTT user; and
ii) an <anyExt> element containing:
A) the <response-type> element set to a value of "remotely-initiated-private-call-response";
B) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user, a <remotely-initiated-call-outcome> element set to a value of "success"; and
C) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were not successful in originating an MCPTT private call to the identified MCPTT user, a <remotely-initiated-call-outcome> element set to a value of "fail";
3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.3.1 Originating procedures | Upon receiving a "SIP MESSAGE request for remotely initiated private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if:
a) the "SIP MESSAGE request for remotely initiated private call for originating participating MCPTT function" contains the <request-type> element set to a value of "remotely-initiated-private-call-request; and
b) if the <allow-request-remote-init-private-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "158 user not authorised to request a remotely initiated private call" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
4) shall determine the public service identity of the controlling MCPTT function for the remotely initiated private call service for the requesting MCPTT user;
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function associated with the remotely initiated private call service for the requesting MCPTT user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the remotely initiated private call service for the requesting MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body the MCPTT ID determined in step 2) above;
9) shall copy the contents of the application/resource-lists+xml MIME body in the received SIP MESSAGE request into an application/resource-lists+xml MIME body in the outgoing SIP MESSAGE request;
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
11) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 13), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.3.2 Terminating procedures | Upon receiving a "SIP MESSAGE request for remotely initiated private call for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response and skip the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.7.4 Controlling MCPTT function procedures | Upon receiving a:
- "SIP MESSAGE request for remotely initiated private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for remotely initiated private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or contains an application/resource-lists+xml MIME body with more than one <entry> element in all <list> elements of the <resource-lists> element, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
8) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP MESSAGE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
9) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user identified by the MCPTT ID contained in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
10) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8 Private call transfer | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.1 General | In the procedures of clause 11.1.8:
- the term "requesting MCPTT user" is used to refer to the MCPTT user who sent a request to initiate a private call transfer;
- the term "transferred MCPTT user" is used to refer to the MCPTT user who is being transferred to the new target MCPPT user; and
- the term "target MCPTT user" is used to refer to the MCPTT user that is the new target of the private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.2.1 Private call transfer request procedures | Upon receiving a request from an MCPTT user to transfer an ongoing MCPTT private call to a target MCPTT user, the MCPTT client:
1) if:
a) the <allow-call-transfer> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) should indicate to the requesting MCPTT user that the requesting MCPTT user is not authorised to initiate a private call transfer request; and
b) shall skip the rest of the steps of the present clause;
2) if the request from the MCPTT user is for an announced transfer of an ongoing MCPTT private call to a target MCPTT user, shall follow the procedure of clause 11.1.8.2.3;
3) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-called-party-id> element set to MCPTT ID of the target MCPTT user; and
ii) an <anyExt> element containing:
A) the <request-type> element set to a value of "transfer-private-call-request"; and
B) if the call is requested to be transferred to a functional alias and the MCPTT client is aware of active functional aliases, then the <call-to-functional-alias-ind> element set to "true"; otherwise, the <call-to-functional-alias-ind> element set to "false";
C) if the request from the MCPTT user is for an announced transfer, and the incoming SIP INVITE request contained a Supported header field containing an option tag "replaces", and, if present, the <replaces-header-value> element set to content copied from the call to the target MCPTT user provided in step 2; and
D) if the target ot the call tranfer is a functional alias, then the <called-functional-alias-URI> element set to the value of the target functional alias;
NOTE 1: For a call transfer to a MCPTT ID the value is the MCPTT ID of the target user, while for call transfer to a functional alias the value is the functional alias of the target user.
NOTE 2: For an announced call transfer to a functional alias, the target MCPTT ID is already known and can therefore be used directly in the <mcptt-called-party-id> element together with the <call-to-functional-alias-ind> element set to "false". Additionally, the <called-functional-alias-URI> element is set to the value of the target functional alias.
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the transferred MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and
f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
4) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the requesting MCPTT user the failure of the sent private call transfer request and skip the rest of the steps.
Upon receiving a "SIP MESSAGE request for transfer private call response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent transfer private call request from the value of the <transfer-call-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request and generate and send a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) if the outcome of the private call transfer is a success, the MCPTT client shall invoke the procedures of clause 11.1.3.1 to end the MCPTT private call with the transferred MCPTT user; and
a) if the request from the MCPTT user is for an announced private call transfer, shall invoke the procedures of clause 11.1.3.1 to end the MCPTT private call with the target MCPTT user; and
3) should indicate to the requesting MCPTT user the success or failure of the sent private call transfer request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.2.2 Client procedures for handling incoming private call transfer request | Upon receiving a "SIP MESSAGE request for transfer private call request for terminating client", the MCPTT client:
1) should indicate to the transferred MCPTT user that a request to transfer the previously ongoing call to a new target MCPTT user has been received;
2) shall extract the MCPTT ID of the target MCPTT user from the <mcptt-called-party-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;
3) if present in the received SIP MESSAGE request, shall extract the content of the <replaces-header-value> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;
4) if according to local policy on-demand sessions are to be used for transfer of private calls, shall invoke the procedures of clause 11.1.1.2.1.1 to originate an MCPTT private call to the target MCPTT user; and
5) if according to local policy pre-established sessions are to be used for transfer of private calls and a pre-established session is available, shall invoke the procedures of clause 11.1.1.2.2.1 to originate an MCPTT private call to the target MCPTT user;
Upon completion of the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1, the MCPTT client:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and
e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-called-party-id> set to the MCPTT ID of the target MCPTT user called by the transferred MCPTT user; and
ii) an <anyExt> element containing:
A) the <response-type> element set to a value of "transfer-private-call-response";
B) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user, a <transfer-call-outcome> element set to a value of "success"; and
C) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were not successful in originating an MCPTT private call to the identified MCPTT user, a <transfer-call-outcome> element set to a value of "fail";
2) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the transferred MCPTT user; and
3) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.2.3 Announced private call transfer | This clause describes the procedures for transferring an MCPTT private call for both cases if a call to the target MCPTT user is already established or not.
When the MCPTT user requests an announced private call transfer of an ongoing private MCPTT call, the MCPTT client:
1) shall put the ongoing MCPTT private call with the transferred MCPTT user on hold following the procedures as described in RFC 5359, clause 2.1;
2) If the requesting MCPTT user does not have a call to the target MCPTT user established:
a) shall initiate an on-demand private call as specified in clause 11.1.1.2.1, or a private call using pre-established session as specified in clause 11.1.1.2.2 to the target MCPTT user with the following clarification:
i) shall include a <transfer-announced-ind> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if present in the the 200 (OK) response received for the MCPTT call in step 2a, shall provide the content of the <replaces-header-value> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body to the procedure in clause 11.1.8.2.1;
c) once the call to the target MCPPT user is established, the MCPTT client should notify the requesting MCPTT user to announce the call transfer to the target MCPTT user;
d) if no <replaces-header-value> element was received in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the 200 (OK) response message in step 2a, shall terminate the MCPTT private call with the target user as specified in clause 11.1.3; and
e) should offer the MCPTT user the option to retrieve the ongoing call with the transferred MCPTT user, to announce the transfer to the calling MCPTT user.
3) If the requesting MCPTT user already has a call to the target MCPTT user established:
a) shall generate a SIP re-INVITE request to be sent towards the target MCPTT user as specified in 3GPP TS 24.229 [4], with the following clarification:
i) shall include a <transfer-announced-ind> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true": and
ii) shall include an SDP offer with the media parameters as currently established according to 3GPP TS 24.229 [4];
b) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4];
c) if present in the the 200 (OK) response received for the SIP re-INVITE request in step 3a, shall provide the content of the <replaces-header-value> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body to the procedure in clause 11.1.8.2.1; and
d) if no <replaces-header-value> element was received in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the 200 (OK) response message of the SIP re-INVITE request in step 3a, should indicate to the requesting MCPTT user failure of invoking the private call transfer request and shall not continue with the rest of the steps. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.3.1 Originating procedures | Upon receiving a "SIP MESSAGE request for transfer private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
4) if:
a) the "SIP MESSAGE request for transfer private call for originating participating MCPTT function" contains the <request-type> element set to a value of "transfer-private-call-request"; and
b) if the <allow-call-transfer> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "170 user not authorised to make a private call transfer request" in a Warning header field as specified in clause 4.4, and skip the rest of the steps;
5) if the "SIP MESSAGE request for transfer private call for originating participating MCPTT function" contains the <request-type> element set to a value of "transfer-private-call-request" and:
a) if the <allow-call-transfer-to-any-user> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false"; and
i) if the call is transferred to an MCPTT ID and the <mcptt-called-party-id> element does not match the <uri-entry> element of one of the <entry> elements of the <AllowedMCPTTIdsForCallTransfer> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
ii) if the call is transferred to a functional alias and the <mcptt-called-party-id> element does not match the <uri-entry> element of one of the <entry> elements of the <AllowedFunctionalAliasesForCallTransfer> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
a) shall reject the "SIP MESSAGE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response including warning text set to "170 user not authorised to make a private call transfer request" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
6) shall determine the public service identity of the controlling MCPTT function for the private call transfer service for the requesting MCPTT user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the private call transfer service for the requesting MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
7) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
8) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 6);
9) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
10) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
11) shall copy the contents of the application/resource-lists+xml MIME body in the received SIP MESSAGE request into an application/resource-lists+xml MIME body in the outgoing SIP MESSAGE request;
12) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
13) 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];
14) 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];
15) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
16) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 16), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, the participating MCPTT function shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.3.2 Terminating procedures | Upon receiving a
- "SIP MESSAGE request for transfer private call request for terminating participating MCPTT function"; or
- "SIP MESSAGE request for transfer private call response for terminating participating MCPTT function";
the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response and skip the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) if the "SIP MESSAGE request for transfer private call for originating participating MCPTT function" contains the <request-type> element set to a value of "transfer-private-call-request"
a) shall extract the MCPTT ID of the target MCPTT user from the <mcptt-called-party-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;
b) shall cache the mapping of the MCPTT ID used in step 2) and target MCPTT ID extracted in step a);
NOTE 1: If multiple private calls transfers are in progress at the same time for the same user, multiple mappings have to be stored.
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.8.4 Controlling MCPTT function procedures | Upon receiving a:
- "SIP MESSAGE request for transfer private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for transfer private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or contains an application/resource-lists+xml MIME body with a total of more than one <entry> element in all <list> elements of the <resource-lists> element, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
8) if the incoming SIP MESSAGE request contains in the application/vnd.3gpp. mcptt-info+xml MIME body <call-to-functional-alias-ind> set to "true" shall identify the MCPTT ID(s) of the MCPTT user(s) that have activated the received functional alias by performing the actions specified in clause 9A.2.2.2.8:
a) if the functional alias is not activated by any MCPTT user, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
b) if the functional alias is activated by one MCPTT user, shall use the MCPTT ID of that user as new target MCPTT ID;
c) if the functional alias is simultaneously activated by multiple MCPTT users, shall select an appropriate MCPTT ID based on local policy. The selection of an appropriate MCPTT ID is left to implementation. The outcome of the selection includes rejection. Upon completion of the selection process,:
i) if the controlling MCPTT function was unable to select an MCPTT ID, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps; or
ii) if the selection process concluded by selecting an appropriate MCPTT ID, this MCPTT ID shall be used as new target MCPTT ID;
d) shall copy the new target MCPTT ID into the <mcptt-called-party-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request.
e) shall set <call-to-functional-alias-ind> to "false" in the application/vnd.3gpp. mcptt-info+xml MIME body of the outgoing SIP message;
9) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP MESSAGE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
10) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user identified by the MCPTT ID contained in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
11) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
12) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controling MCPTT function; and
13) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9 Private call forwarding | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.1 General | In the procedures of clause 11.1.9:
- the term "forwarded-calling-client" is used to refer to the originating MCPTT client who has made a private call attempt that is being forwarded;
- the term "forwarded-by-client" is used to refer to the MCPTT client to whom a private call has been placed and who has requested that the private call be forwarded either through settings at its participating MCPTT function or through manual user input; and
- the term "forwarded-to-client" is used to refer to the terminating MCPTT client to whom a private call attempt is being forwarded |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.2 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.2.1 Private call forwarding request based on manual user input procedure | The following procedure covers the case when an MCPTT user decides to forward an incoming MCPTT private call to a new target MCPTT ID or functional alias based on manual user input instead of accepting the incoming MCPTT private call. If the MCPTT user decides to forward an incoming MCPTT private call to a new target MCPTT ID or functional alias based on manual user input, the MCPTT client:
NOTE 1: Forwarding an MCPTT private call based on manual user input is only possible for manual commencement mode.
1) if:
a) the <allow-call-fwd-manual-any> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) should indicate to the requesting MCPTT user that the requesting MCPTT user is not authorised to initiate a private call forwarding request; and
b) shall skip the rest of the steps of the present clause;
1A) if the incoming SIP INVITE request contains a <forwarding-other-list> element with one or more <entry> elements should indicate to the requesting MCPTT user that the maximum number of allowed forwardings is exceeded and shall skip the rest of the steps of the present clause;
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) an <anyExt> element containing:
A) the <request-type> element set to a value of "forward-private-call-request";
B) if the call is requested to be forwarded to a functional alias and the MCPTT client is aware of active functional aliases, then the <call-to-functional-alias-ind> element set to "true"; otherwise, the <call-to-functional-alias-ind> element set to "false";
NOTE 2: For call forwarding to an MCPTT ID the value of the <forwarding-target-orig-id> is the MCPTT ID of the target user, while for call forwarding to a functional alias the value is the functional alias of the target user.
C) the <forwarding-reason> element set to a value of "manual-input";
D) the <forwarded-by-functional-alias> set to the <called-functional-alias-URI> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request, if present;
E) the <forwarded-by-mcptt-id> element set to the MCPTT ID present in the <mcptt-request-uri> received in the SIP application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request; and
F) the <forwarding-target-orig-id> element set to the MCPTT ID or the functional alias to be used of the target MCPTT user;
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the forwarded-calling-client MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and
f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
4) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
NOTE 3: The SIP MESSAGE is sent towards the client of the forwarded MCPTT user. The procedure how to process this incoming SIP MESSAGE is descibed in clause 11.1.9.2.2. Clause 11.1.9.2.2 also contains references to clause 11.1.1.2.1.1 and clause 11.1.1.2.2.1 describing how to originate an MCPTT private call from the forwarded MCPTT user to the target MCPTT.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the requesting MCPTT user the failure of the sent private call forwarding request and skip the rest of the steps.
Upon receiving a "SIP MESSAGE request for forwarding private call response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent forwarding private call request from the value of the <forwarding-call-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request and generate and send a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
2) should indicate to the requesting MCPTT user the success or failure of the sent private call forwarding request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.2.2 Client procedures for handling incoming private call forwarding request | Upon receiving a "SIP MESSAGE request for forwarding private call request for terminating client", the MCPTT client:
1) should indicate to the forwarded MCPTT user that a request to forward the previously initiated call to a new target MCPTT user has been received;
2) shall extract the MCPTT ID of the target MCPTT user from the <forwarding-target-id> element contained in the in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request;
3) if according to local policy on-demand sessions are to be used for forwarding of private calls, shall invoke the procedures of clause 11.1.1.2.1.1 to originate an MCPTT private call to the target MCPTT user; and
4) if according to local policy pre-established sessions are to be used for forwarding of private calls and a pre-established session is available, shall invoke the procedures of clause 11.1.1.2.2.1 to originate an MCPTT private call to the target MCPTT user.
Once the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 resulted in receiving a SIP 180 (Ringing) response or a SIP final response the MCPTT client:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the forwarded-by-mcptt-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and
e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-called-party-id> set to the MCPTT ID of the forwarded-to-client called by theforwarded-calling-client; and
ii) an <anyExt> element containing:
A) the <response-type> element set to a value of "forwarding-private-call-response";
B) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were successful in originating an MCPTT private call to the identified MCPTT user, a <forwarding-call-outcome> element set to a value of "success"; and
C) if the procedures of clause 11.1.1.2.1.1 or clause 11.1.1.2.2.1 were not successful in originating an MCPTT private call to the identified MCPTT user, a <forwarding-call-outcome> element set to a value of "fail";
2) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the forwarded-by-client; and
3) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.3.1 Originating procedures | Upon receiving a "SIP MESSAGE request for forwarding private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
4) if:
a) the "SIP MESSAGE request for forwarding private call for originating participating MCPTT function" contains the <request-type> element set to a value of "forward-private-call-request"; and
b) if the <allow-call-forward-manual-input> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false";
then:
a) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "173 user not authorised to make a private call forwarding request" in a Warning header field as specified in clause 4.4, and skip the rest of the steps;
5) shall determine the public service identity of the controlling MCPTT function for the forwarding private call service for the requesting MCPTT user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the private call forwarding service for the requesting MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5);
8) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) shall copy the contents of the application/resource-lists+xml MIME body in the received SIP MESSAGE request into an application/resource-lists+xml MIME body in the outgoing SIP MESSAGE request;
10a) shall set the <forwarded-by-mcptt-id> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request to the MCPTT ID determined in step 2:
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
12) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
13) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
14) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 15), the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.3.2 Terminating procedures | Upon receiving a
- "SIP MESSAGE request for forwarding private call request for terminating participating MCPTT function"; or
- "SIP MESSAGE request for forwarding private call response for terminating participating MCPTT function";
the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response and skip the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) if the "SIP MESSAGE request for forwarding private call for terminating participating MCPTT function" contains the <request-type> element set to a value of "forward-private-call-request":
a) shall extract the MCPTT ID of the target MCPTT user from the <mcptt-called-party-id> element contained in the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request; and
b) shall cache the mapping of the MCPTT ID used in step 2) and target MCPTT ID extracted in step a);
NOTE: If multiple private call forwardings are in progress at the same time for the same user, multiple mappings have to be stored.
6) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.1.9.4 Controlling MCPTT function procedures | Upon receiving a:
- "SIP MESSAGE request for forwarding private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for forwarding private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body or contains an application/resource-lists+xml MIME body with a total of more than one <entry> element in all <list> elements in the <resource-lists> element, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
8) if the incoming SIP MESSAGE is a SIP MESSAGE request for forwarding private call request for controlling MCPTT function:
a) shall copy the value of the <forwarding-target-orig-id> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request into the <forwarding-target-id> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
b) if the incoming SIP MESSAGE request contains in the application/vnd.3gpp. mcptt-info+xml MIME body <call-to-functional-alias-ind> set to "true" shall identify the MCPTT ID(s) of the MCPTT user(s) that have activated the received functional alias by performing the actions specified in clause 9A.2.2.2.8:
i) if the functional alias is not activated by any MCPTT user, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
ii) if the functional alias is activated by one MCPTT user, shall use the MCPTT ID of that user as the new target MCPTT ID;
iii) if the functional alias is simultaneously activated by multiple MCPTT users, shall select an appropriate MCPTT ID based on local policy. The selection of an appropriate MCPTT ID is left to implementation. The outcome of the selection includes rejection. Upon completion of the selection process:
A) if the controlling MCPTT function was unable to select an MCPTT ID, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps; and
B) if the selection process concluded by selecting an appropriate MCPTT ID, this MCPTT ID shall be used as new target MCPTT ID;
iv) shall copy the new target MCPTT ID into the < forwarding-target-id > element in the <mcptt-Params> element of the <mcpttinfo> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
v) shall set <call-to-functional-alias-ind> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp. mcptt-info+xml MIME body of the outgoing SIP message to "false"; and
vi) shall include a <forwarding-target-is-functional-alias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request with a value set to "true";
c) if the incoming SIP MESSAGE request does not contain a <call-to-functional-alias-ind> element in the application/vnd.3gpp. mcptt-info+xml MIME body, or if it is present and set to "false" shall set the <forwarding-target-is-functional-alias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request with a value set to “false”;
9) shall copy the MCPTT ID of the MCPTT user listed in the MIME resources body of the incoming SIP MESSAGE request, into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
10) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user identified by the MCPTT ID contained in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system.
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
11) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
12) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
13) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2 Off-network private call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.1.1 Common procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.1.1.1 Sending/Receiving a message | In order to participate in a private call, the MCPTT client:
1) shall send the MONP message as a UDP message to the local IP address of the MCPTT user, to UDP port 8809, with an IP time-to-live set to 255; and
2) shall treat UDP messages received on the port TBD as received 8809 messages.
NOTE: An MCPTT client that supports IPv6 shall listen to the IPv6 addresses. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.1.1.2 Session description | For an off-network MCPTT session, only MCPTT speech is used.
One off-network MCPTT session includes one media-floor control entity.
The MCPTT client shall generate an SDP body for a private call in accordance with rules and procedures of IETF RFC 4566 [12] and IETF RFC 3264 [44].
The MCPTT client:
1) shall include in the session-level section:
a) the "o=" field with the <username> portion set to a dash;
b) the "s=" field with the <session name> portion set to a dash; and
c) the "c=" field with the <nettype> portion set to "IN", the <addrtype> portion set to the IP version of the unicast IP address of the MCPTT client and the <connection-address> portion set to the unicast IP address of the MCPTT client;
2) shall include the media-level section for MCPTT speech consisting of:
a) the "m=" field with the <media> portion set to "audio", the <port> portion set to a port number for MCPTT speech of the MCPTT group, the <proto> field set to "RTP/AVP" and <fmt> portion set indicating RTP payload type numbers;
b) the "i=" field with the <session description> portion set to "speech";
c) the "a=fmtp:" attribute(s), the "a=rtpmap:" attribute(s) or both, indicating the codec(s) and media parameters of the MCPTT speech; and
d) the "a=rtcp:" attribute indicating port number to be used for RTCP at the MCPTT client selected according to the rules and procedures of IETF RFC 3605 [13], if the media steam uses other than the default IP address;
3) shall include the media-level section for media-floor control entity consisting of:
a) an "m=" line, with the <media> portion set to "application", the <port> portion set to a port number for media-floor control entity of the MCPTT group, the <proto> field set to "udp" and <fmt> portion set to "MCPTT"; and
b) the "a=fmtp:MCPTT" attribute indicating the parameters of the media-floor control entity as specified 3GPP TS 24.380 [5]; and
4) shall include the MIKEY-SAKKE I_MESSAGE, if generated by the MCPTT client, in an "a=key-mgmt" attribute as a "mikey" attribute value in the SDP offer as specified in IETF RFC 4567 [47]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2 Basic call control | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.1 General | The maximum number of simultaneous off-network private calls is limited by the value of "/<x>/Common/PrivateCall/MaxCallN10" leaf node present in the UE configuration as specified in 3GPP TS 24.483 [45]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.2 Private call control state machine | The figure 11.2.2.2-1 gives an overview of the main states and transitions on the UE for private call control.
Each private call control state machine is per MCPTT user ID.
Figure 11.2.2.2-1: Private call control state machine |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3 Private call control states | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.1 P0: start-stop | In this state, no private call control entity exists. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.2 P1: ignoring same call id | This state exists for UE, when the UE is not part of an ongoing private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.3 P2: waiting for call response | This state exists for UE, when the UE has sent a PRIVATE CALL SETUP REQUEST message and is waiting for a response, PRIVATE CALL ACCEPT or PRIVATE CALL REJECT message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.4 P3: waiting for release response | This state exists for UE, when the UE has sent a PRIVATE CALL RELEASE message and is waiting for a PRIVATE CALL RELEASE ACK message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.5 P4: part of ongoing call | This state exists for UE, when the UE is part of an ongoing private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.3.6 P5: pending | This state exists for UE, when the UE has presented a notification to the user for the received PRIVATE CALL SETUP REQUEST message and is waiting for a user indication. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4 Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.2 Private call setup | 11.2.2.4.2.1 Initiating a private call
When in the "P0: start-stop" state or "P1: ignoring same call id", upon an indication from MCPTT User to initiate a private call and the value of "/<x>/<x>/Common/PrivateCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", the MCPTT client:
1) shall generate and store the call identifier as a random number uniformly distributed between (0, 65536);
2) shall store own MCPTT user ID as caller ID;
3) shall store MCPTT user ID of the callee as callee ID;
4) shall store "AUTOMATIC COMMENCEMENT MODE" as commencement mode, if requested and the value of "/<x>/<x>/Common/PrivateCall/AutoCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise if the value of "/<x>/<x>/Common/PrivateCall/ManualCommence" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", store "MANUAL COMMENCEMENT MODE" as commencement mode;
5) shall create a call type control state machine as described in clause 11.2.3.2;
6) if an end-to-end security context needs to be established then:
a) shall use keying material provided by the key management server to generate a PCK as described in 3GPP TS 33.180 [78];
b) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect private call communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];
c) shall encrypt the PCK to a UID associated to the MCPTT client using the MCPTT ID and KMS URI of the invited user as determined by the procedures of clause 6.2.8.3.9 and a time related parameter as described in 3GPP TS 33.180 [78];
d) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];
e) shall add the MCPTT ID of the originating MCPTT user to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
f) shall sign the MIKEY-SAKKE I_MESSAGE using the originating MCPTT user's signing key provided in the keying material together with a time related parameter, and add this to the MIKEY-SAKKE payload, as described in 3GPP TS 33.180 [78] and;
g) shall store the MIKEY-SAKKE I_MESSAGE for later inclusion in an SDP body;
7) may store current user location as user location;
8) shall generate and store offer SDP, as defined in clause 11.2.1.1.2;
9) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE with the stored commencement mode;
e) shall set the Call type IE with the stored current call type associated with the call type control state machine;
f) shall set the SDP offer IE with the stored offer SDP; and
g) may set the User location IE with the stored user location if the stored current call type associated with the call type control state machine is "EMERGENCY PRIVATE CALL".
10) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
11) shall initialize the counter CFP1 (private call request retransmission) with the value set to 1;
12) shall start timer TFP1 (private call request retransmission);
13) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
14) shall enter the "P2: waiting for call response" state.
11.2.2.4.2.2 Private call setup request retransmission
When in the "P2: waiting for call response" state, upon expiry of timer TFP1 (private call request retransmission) and the value of the counter CFP1 (private call request retransmission) is less than the upper limit, the MCPTT client:
1) may update the stored user location with current user location;
2) shall increment the value of counter CFP1 (private call request retransmission) by 1;
3) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE with the stored commencement mode;
e) shall set the Call type IE with the stored current call type associated with the call type control state machine;
f) shall set the SDP offer IE with the stored offer SDP; and
g) may set the User location IE with stored user location if the stored current call type is "EMERGENCY PRIVATE CALL" associated with the call type control state machine.
4) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
5) shall start timer TFP1 (private call request retransmission); and
6) shall remain in the "P2: waiting for call response" state.
11.2.2.4.2.3 Ringing notification to the user
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL RINGING message, the MCPTT client:
1) shall remain in the "P2: waiting for call response" state.
11.2.2.4.2.4 No response to private call setup request with automatic commencement mode
In the "P2: waiting for call response" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit and the stored commencement mode is "AUTOMATIC COMMENCEMENT MODE", the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
11.2.2.4.2.5 No response to private call setup request with manual commencement mode
When in the "P2: waiting for call response" state when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit and the stored commencement mode is "MANUAL COMMENCEMENT MODE", the MCPTT client:
1) shall start timer TFP9 (waiting for call response message); and
2) shall remain in the "P2: waiting for call response" state.
11.2.2.4.2.6 No response to private call setup request after waiting for user acknowledgement
When in the "P2: waiting for call response" state, upon expiry of timer TFP9 (waiting for call response message), the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
11.2.2.4.2.7 Private call setup request rejected
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as the stored call identifier, the MCPTT client:
1) shall stop timer TFP1 (private call request retransmission), if running;
2) shall stop timer TFP9 (waiting for call response message), if running;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
11.2.2.4.2.8 Private call setup request accepted
When in the "P2: waiting for call response" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall store the SDP answer IE received in the PRIVATE CALL ACCEPT message as answer SDP;
2) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
3) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
4) shall stop timer TFP1 (private call request retransmission), if running;
5) shall stop timer TFP9 (waiting for call response message), if running;
6) shall establish a media session based on the SDP body of the stored answer SDP;
7) shall start floor control as originating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
8) shall start timer TFP5 (max duration); and
9) shall enter the "P4: part of ongoing call" state.
11.2.2.4.2.9 User cancels the private call setup request
When in the "P2: waiting for call response" state, upon an indication from MCPTT User to cancel the private call request, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP1 (private call request retransmission);
4) shall stop timer TFP9 (waiting for call response message);
5) shall start timer TFP3 (private call release retransmission);
6) shall initialize the counter CFP3 with value set to 1; and
7) shall enter the "P3: waiting for release response" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.3 Private call setup in automatic commencement mode | 11.2.2.4.3.1 Unable to establish media
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Call identifier IE different than stored call identifier and media session declared in SDP body of PRIVATE CALL SETUP REQUEST message cannot be established, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall store the MCPTT user ID of the caller IE in the received PRIVATE CALL SETUP message as caller ID;
3) shall store own MCPTT user ID as callee ID;
4) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
a) shall set the Call identifier IE to the cached call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID; and
d) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the Reason IE as "MEDIA FAILURE".
5) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
6) shall start timer TFP7 (waiting for any message with same call identifier); and
7) shall enter the "P1: ignoring same call id" state if current state is the "P0: start-stop" state.
11.2.2.4.3.2 Responding to private call setup request when not participating in the ongoing call
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Commencement mode IE set to "AUTOMATIC COMMENCEMENT MODE" and Call identifier IE different than stored call identifier and media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall create the call type control state machine as described in clause 11.2.3.2;
3) shall store the MCPTT user ID of the caller IE in the received PRIVATE CALL SETUP REQUEST message as caller ID;
4) shall store own MCPTT user ID as callee ID;
5) if the SDP offer contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:
a) shall extract the MCPTT ID of the originating MCPTT user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
b) shall convert the MCPTT ID to a UID as described in 3GPP TS 33.180 [78];
c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if the validation of the signature failed, shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
i) shall set the call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID;
iv) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "E2E SECURITY CONTEXT FAILURE";
v) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall release call type control state machine; and
vii) shall remain in the current state;
e) if the validation of the signature was successful:
i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78];
ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
iii) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
iv) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier; and
B) shall set the MCPTT user ID of the caller IE with stored caller ID.
C) shall set the MCPTT user ID of the callee IE with stored callee ID; and
D) shall set the SDP answer IE with the stored answer SDP;
v) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall establish a media session based on the SDP body of the stored answer SDP;
vii) shall initialize the counter CFP4 with value set to 1;
viii) shall start timer TFP4 (private call accept retransmission);
ix) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
x) shall enter the "P5: pending" state; and
NOTE: With the PCK successfully shared between the originating MCPTT client and the terminating MCPTT client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.
6) if the SDP offer does not contain an "a=key-mgmt" attribute, the MCPTT client:
a) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with stored caller ID.
iii) shall set the MCPTT user ID of the callee IE with stored callee ID; and
iv) shall set the SDP answer IE with the stored answer SDP;
c) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
d) shall establish a media session based on the SDP body of the stored answer SDP;
e) shall initialize the counter CFP4 with value set to 1;
f) shall start timer TFP4 (private call accept retransmission);
g) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier); and
h) shall enter the "P5: pending" state.
11.2.2.4.3.3 Private call accept retransmission
When in the "P5: pending" state, upon expiry of timer TFP4 (private call accept retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the SDP answer IE with the stored answer SDP;
2) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the counter CFP4 (private call accept retransmission) by 1;
4) shall start timer TFP4 (private call accept retransmission); and
5) shall remain in the "P5: pending" state.
11.2.2.4.3.4 Establishing the call
When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCPTT client:
1) shall stop timer TFP4(private call accept retransmission);
2) shall start floor control as terminating MCPTT client as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall start timer TFP5 (max duration); and
4) shall enter the "P4: part of ongoing call" state.
11.2.2.4.3.5 Call failure
In the "P5: pending" state, when timer TFP4 (private call accept retransmission) expires and the value of the counter CFP4 (private call accept retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.4 Private call setup in manual commencement mode | 11.2.2.4.4.1 Incoming private call
When in the "P0: start-stop" or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL SETUP REQUEST message with Commencement mode IE set to "MANUAL COMMENCEMENT MODE" and Call identifier IE different from stored call identifier, the MCPTT client:
1) shall store the Call identifier IE in the received message as call identifier;
2) shall create the call type control state machine as described in clause 11.2.3.2;
3) shall store the MCPTT user ID of the caller IE as received in the PRIVATE CALL SETUP REQUEST as caller ID;
4) shall store own MCPTT user ID as callee ID;
5) shall generate a PRIVATE CALL RINGING message as specified in clause 15.1.6;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
6) shall send PRIVATE CALL RINGING message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
7) if in "P1: ignoring same call id" state, shall stop timer TFP7 (waiting for any message with same call identifier);
8) shall start timer TFP2 (waiting for user to respond); and
9) shall enter the "P5: pending" state.
11.2.2.4.4.2 No response from the user
When in the "P5: pending" state, upon expiry of timer TFP2 (waiting for user to respond), the MCPTT client:
1) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the Reason IE as "FAILED".
2) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
11.2.2.4.4.3 User accepts the private call setup request
When in the "P5: pending" state, upon an indication from MCPTT User to accept the incoming private call, the MCPTT client:
1) if the SDP offer contains an "a=key-mgmt" attribute field with a "mikey" attribute value containing a MIKEY-SAKKE I_MESSAGE:
a) shall extract the MCPTT ID of the originating MCPTT user from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
b) shall convert the MCPTT ID to a UID as described in 3GPP TS 33.180 [78];
c) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
d) if the validation of the signature failed, shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8. In the PRIVATE CALL REJECT message, the MCPTT client:
i) shall set the call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID;
iv) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "E2E SECURITY CONTEXT FAILURE";
v) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall stop timer TFP2 (waiting for user to respond);
vii) if timer TFP 7 is not running, shall start timer TFP7 (waiting for any message with same call identifier);
viii) shall release the call type control state machine; and
ix) shall enter the "P1: ignoring same call id" state;
e) if the validation of the signature was successful:
i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78];
ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
iii) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
iv) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier;
B) shall set the MCPTT user ID of the caller IE with the stored caller ID;
C) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
D) shall set the SDP answer IE with the stored answer SDP;
v) shall send the PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
vi) shall establish a media session based on the SDP body of the private call;
vii) shall stop timer TFP2 (waiting for user to respond);
viii) shall initialize the counter CFP4 with value set to 1;
ix) shall start timer TFP4 (private call accept retransmission); and
x) shall remain in the "P5: pending" state; and
NOTE: With the PCK successfully shared between the originating MCPTT client and the terminating MCPTT client, both clients are able to use SRTP/SRTCP to create an end-to-end secure session.
2) if the SDP offer does not contain an "a=key-mgmt" attribute, the MCPTT client:
a) shall generate and store answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the caller IE with the stored caller ID;
iii) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
iv) shall set the SDP answer IE with the stored answer SDP;
c) shall send the PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
d) shall establish a media session based on the SDP body of the private call;
e) shall stop timer TFP2 (waiting for user to respond);
f) shall initialize the counter CFP4 with value set to 1;
g) shall start timer TFP4 (private call accept retransmission); and
h) shall remain in the "P5: pending" state.
11.2.2.4.4.4 Private call accept retransmission
When in the "P5: pending" state, upon expiry of timer TFP4 (private call accept retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7. In the PRIVATE CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID; and
d) shall set the SDP answer IE with the stored answer SDP;
2) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the (counter CFP4 private call accept retransmission) by 1;
4) shall start timer TFP4 (private call accept retransmission); and
5) shall remain in the "P5: pending" state.
11.2.2.4.4.5 Establishing the call
When in the "P5: pending" state, upon receiving a PRIVATE CALL ACCEPT ACK message or RTP media from originating user, the MCPTT client:
1) shall stop timer TFP4 (private call accept retransmission);
2) shall start floor control as terminating MCPTT client as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall start timer TFP5 (max duration); and
4) shall enter the "P4: part of ongoing call" state.
11.2.2.4.4.6 Call failure
In the "P5: pending" state, when timer TFP4 (private call accept retransmission) expires and the value of the counter CFP4 (private call accept retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall release the call type control state machine; and
3) shall enter the "P1: ignoring same call id" state.
11.2.2.4.4.7 User rejects the private call setup request
When in the "P5: pending" state, upon an indication from MCPTT User to reject the incoming private call, the MCPTT client:
1) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID; and
d) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the Reason IE as "REJECT";
2) shall send the PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP2 (waiting for user to respond);
4) shall start timer TFP7 (waiting for any message with same call identifier);
5) shall release the call type control state machine; and
6) shall enter the "P1: ignoring same call id" state.
11.2.2.4.4.8 Caller cancels the private call setup request before call establishment
When in the "P5: pending" state or "P1: ignoring same call id" state, upon receiving a PRIVATE CALL RELEASE message, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE ACK message as specified in clause 15.1.10. In the PRIVATE CALL RELEASE ACK message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and.
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) if in the "P5: pending" state and timer TFP7 (waiting for any message with same call identifier) is not running, shall start timer TFP7 (waiting for any message with same call identifier);
4) shall stop timer TFP2 (waiting for user to respond), if running;
5) shall stop timer TFP4 (private call accept retransmission) if running;
6) shall release the call type control state machine, if the current state is "P5: pending" state; and
7) shall enter the "P1: ignoring same call id" state, if the current state is "P5: pending" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.5 Private call release | 11.2.2.4.5.1 Releasing a private call
When in the "P4: part of ongoing call" state, upon an indication from MCPTT User to release a private call, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9. In the PRIVATE CALL RELEASE message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with stored callee ID.
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop timer TFP5 (max duration);
4) shall initialize the counter CFP3 (private call release retransmission) with the value set to 1;
5) shall start timer TFP3 (private call release retransmission); and
6) shall enter the "P3: waiting for release response" state.
11.2.2.4.5.2 Private call release retransmission
When in the "P3: waiting for release response" state, upon expiry of timer TFP3 (private call release retransmission), the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE message as specified in clause 15.1.9. In the PRIVATE CALL RELEASE message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of timer CFP3 by 1;
4) shall start timer TFP3 (private call release retransmission); and
5) shall remain in the "P3: waiting for release response" state.
11.2.2.4.5.3 No response to private call release
In the "P3: waiting for release response" state, when timer TFP3 (private call request retransmission) expires and the value of the counter CFP3 (private call release retransmission) is equal to the upper limit, the MCPTT client:
1) shall terminate the media session;
2) shall start timer TFP7 (waiting for any message with same call identifier);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
11.2.2.4.5.4 Acknowledging private call release after call establishment
When in the "P4: part of ongoing call" state, upon receiving a PRIVATE CALL RELEASE message, the MCPTT client:
1) shall generate a PRIVATE CALL RELEASE ACK message as specified in clause 15.1.10;
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID.
2) shall send the PRIVATE CALL RELEASE ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall terminate the media session for private call;
4) shall stop timer TFP5 (max duration);
5) shall start timer TFP7 (waiting for any message with same call identifier);
6) shall release the call type control state machine; and
7) shall enter the "P1: ignoring same call id" state.
11.2.2.4.5.5 Private call release acknowledged
When in the "P3: waiting for release response" state, upon receiving a PRIVATE CALL RELEASE ACK to PRIVATE CALL RELEASE message, the MCPTT client:
1) shall stop timer TFP3 (private call release retransmission), if running;
2) shall terminate the media session;
3) shall start timer TFP7 (waiting for any message with same call identifier);
4) shall release the call type control state machine; and
5) shall enter the "P1: ignoring same call id" state.
11.2.2.4.5.6 Max duration reached
When in the "P4: part of ongoing call" state, upon expiry of timer TFP5 (max duration), the MCPTT client:
1) shall terminate the media session;
2) shall start timer TFP7 (waiting for any message with same call identifier);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
11.2.2.4.5.7 Stop ignoring same call id
When in the "P1: ignoring same call id" state, upon expiry of timer TFP7 (waiting for any message with same call identifier) the MCPTT client:
1) shall clear the stored call identifier; and
2) shall enter the "P0: start-stop" state.
11.2.2.4.5.8 No response to emergency private call setup request
In the "P4: part of ongoing call" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall stop timer TFP5 (max duration);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state.
11.2.2.4.5.9 No response to emergency private call cancel
In the "P4: part of ongoing call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:
1) shall start timer TFP7 (waiting for any message with same call identifier);
2) shall stop timer TFP5 (max duration);
3) shall release the call type control state machine; and
4) shall enter the "P1: ignoring same call id" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.2.4.6 Error handling | 11.2.2.4.6.1 Unexpected MONP message received
Upon receiving a MONP message in a state where there is no handling specified for the MONP message, the MCPTT client shall discard the MONP message.
11.2.2.4.6.2 Unexpected indication from MCPTT user
Upon receiving an indication from the MCPTT user in a state where there is no handling specified for the indication, the MCPTT client shall ignore the indication.
11.2.2.4.6.3 Unexpected expiration of a timer
Upon expiration of a timer in a state where there is no handling specified for expiration of the timer, the MCPTT client shall ignore the expiration of the timer. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3 Call type control | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.1 General | This state machine exists in parallel with the call control state machine for off-network private call as specified in clause 11.2.2.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.2 Call type control state machine | The Figure 11.2.3.2-1 gives an overview of the states and transitions of the state machine.
Figure 11.2.3.2-1: Call type control state machine
When sending the message, MCPTT client indicates the stored current ProSe per-packet priority associated with the call type control state machine to the lower layers. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.3 Call type control states | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.3.1 Q0: waiting for the call to be established | This state is the start state of this state machine. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.3.2 Q1: in-progress private call | This state exists for UE, when the UE is part of an in-progress private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.3.3 Q2: in-progress emergency private call | This state exists for UE, when the UE is part of an in-progress emergency private call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4 Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.2 Outgoing call initiated | When in "Q0: waiting for the call to be established" state, upon an indication from the MCPTT user to initiate a call, the MCPTT client:
1) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "true" and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true":
a) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45]; or
2) if the stored emergency state associated with emergency alert state machine described in 12.2.2.2 is set to "false":
a) if the user initiates an MCPTT emergency private call and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true":
i) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45]; or
b) if the user initiates an MCPTT private call:
i) shall set the stored current call type to "PRIVATE CALL"; and
ii) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.3 Received incoming call | When in "Q0: waiting for the call to be established" state, upon receipt of a PRIVATE CALL SETUP REQUEST message by an idle MCPTT client, the MCPTT client:
1) if the Call type IE of the received PRIVATE CALL SETUP REQUEST message is set to "EMERGENCY PRIVATE CALL":
a) shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
2) if the Call type IE of the received PRIVATE CALL SETUP REQUEST message is set to "PRIVATE CALL":
a) shall set the stored current call type to "PRIVATE CALL"; and
b) shall set the stored current ProSe per-packet priority to value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.4 Establishing the private call | When in "Q0: waiting for the call to be established" state, upon receiving PRIVATE CALL ACCEPT message or PRIVATE CALL ACCEPT ACK message, the MCPTT client:
1) if the stored current call type is set to "EMERGENCY PRIVATE CALL":
a) shall start TFP8 (implicit downgrade) timer; and
b) shall enter "Q2: in-progress emergency private call" state; or
2) if the stored current call type is set to "PRIVATE CALL":
a) shall enter "Q1: in-progress private call" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.5 Upgrade call | 11.2.3.4.5.1 User upgrades private call to emergency private call
When in the "Q1: in-progress private call" state, upon an indication from MCPTT User to upgrade the call to emergency and the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/Authorised" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true", the MCPTT client:
1) shall generate and store emergency offer SDP as defined in clause 11.2.1.1.2;
2) shall update stored caller ID as own MCPTT user ID;
3) shall update stored callee ID as MCPTT user ID of the other user;
4) shall store current user location as user location;
5) shall set the stored current call type to "EMERGENCY PRIVATE CALL";
6) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID;
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
d) shall set the Commencement mode IE as "AUTOMATIC COMMENCEMENT MODE";
e) shall set the Call type IE to the stored current call type;
f) shall set the SDP offer IE with emergency offer SDP; and
g) may set the User location IE with user location.
7) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
8) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
9) shall initialize the counter CFP1 (private call request retransmission) with value set to 1;
10) shall start timer TFP1 (private call request retransmission);
11) shall stop timer TFP6 (emergency private call cancel retransmission), if running; and
12) shall enter the "Q2: in-progress emergency private call" state.
11.2.3.4.5.2 Emergency private call setup request retransmission
When in the "Q2: in-progress emergency private call" state, upon expiry of timer TFP1 (private call request retransmission) and the value of CFP1 is less than the limit for CFP1, the MCPTT client:
1) may update the stored user location with current user location;
2) shall increment the value of the counter CFP1 (private call request retransmission) by 1;
3) shall generate a PRIVATE CALL SETUP REQUEST message as specified in clause 15.1.5. In the PRIVATE CALL SETUP REQUEST message, the MCPTT client:
a) shall set the Call identifier IE with the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID;
c) shall set the MCPTT user ID of the callee IE with stored callee ID;
d) shall set the Commencement mode IE as "AUTOMATIC COMMENCEMENT MODE";
e) shall set the Call type IE to the stored current call type;
f) shall set the SDP offer IE with the stored emergency offer SDP; and
g) may set the User location IE with stored user location;
4) shall send the PRIVATE CALL SETUP REQUEST message towards other MCPTT client according to rules and procedures as specified in clause 11.2.1.1.1;
5) shall start timer TFP1 (private call request retransmission); and
6) shall remain in the "Q2: in-progress emergency private call" state.
11.2.3.4.5.3 Emergency private call setup request accepted
When in the "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall store the SDP answer IE received in the PRIVATE CALL ACCEPT message as emergency answer SDP;
2) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
3) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
4) shall stop timer TFP1 (private call request retransmission), if running;
5) if timer TFP8 is not running, shall start TFP8 (implicit downgrade) timer;
6) shall establish a media session based on the SDP body of the stored emergency answer SDP, if not already established based on the received SDP body of the stored emergency answer SDP; and
7) shall remain in the current state.
NOTE: PRIVATE CALL ACCEPT ACK message is retransmitted, as described in this clause, every time a PRIVATE CALL ACCEPT message is received.
11.2.3.4.5.4 Emergency private call setup request rejected
When in the "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL REJECT message in response to PRIVATE CALL SETUP REQUEST message with Call identifier IE same as stored call identifier, the MCPTT client:
1) shall stop timer TFP1 (private call request retransmission), if running;
2) shall set the ProSe per-packet priority to the value corresponding to the MCPTT off-network private call as described in 3GPP TS 24.483 [45];
3) shall set the stored current call type to "PRIVATE CALL"; and
4) shall enter the "Q1: in-progress private call" state.
11.2.3.4.5.5 No response to emergency private call setup request
In the "Q2: in-progress emergency private call" state, when timer TFP1 (private call request retransmission) expires and the value of the counter CFP1 (private call request retransmission) is equal to the upper, the MCPTT client:
1) shall release the stored current call type;
2) shall release the stored Prose per-packet priority; and
3) shall enter "Q0: waiting for the call to be established".
11.2.3.4.5.6 Responding to emergency private call setup request when participating in the ongoing call
When in the "Q1: in-progress private call" state or "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL SETUP REQUEST message with the Call identifier IE same as the stored call identifier of the call, the Call type IE set as "EMERGENCY PRIVATE CALL", the MCPTT client:
1) if the media session declared in SDP body of PRIVATE CALL SETUP REQUEST message can be established:
a) shall generate and store emergency answer SDP based on received SDP offer IE in PRIVATE CALL SETUP REQUEST message, as defined in clause 11.2.1.1.2;
b) shall update the stored caller ID with the MCPTT user ID of the caller IE as received in the PRIVATE CALL SETUP REQUEST message;
c) shall update the stored callee ID with own MCPTT user ID;
d) shall generate a PRIVATE CALL ACCEPT message as specified in clause 15.1.7:
i) shall set the Call identifier IE to the stored call identifier;
ii) shall set the MCPTT user ID of the callee IE with stored callee ID;
iii) shall set the MCPTT user ID of the caller IE with stored caller ID; and
iv) shall set the SDP answer IE with the stored emergency answer SDP;
e) if in the "Q1: in-progress private call" state, shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network emergency private call as described in 3GPP TS 24.483 [45];
f) if in the "Q1: in-progress private call" state, shall stop timer TFP6 (emergency private call cancel retransmission), if running;
g) if in the "Q1: in-progress private call" state, shall start timer TFP8 (implicit downgrade);
h) shall send PRIVATE CALL ACCEPT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1;
i) if in the "Q1: in-progress private call" state, shall set the stored current call type to "EMERGENCY PRIVATE CALL"; and
j) if in the "Q1: in-progress private call" state, shall enter the "Q2: in-progress emergency private call" state; otherwise remain in the "Q2: in-progress emergency private call" state;
2) if the media session declared in SDP body of PRIVATE CALL SETUP REQUEST message cannot be established:
a) shall generate a PRIVATE CALL REJECT message as specified in clause 15.1.8;
b) shall set the call identifier IE with the call identifier in the received message;
c) shall set the MCPTT user ID of the caller IE with the caller ID in the received message;
d) shall set the MCPTT user ID of the callee IE with the callee ID in the received message;
e) shall set the Reason IE as "FAILED", if requested to restrict notification of call failure and the value of "/<x>/<x>/Common/PrivateCall/FailRestrict" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] is set to "true". Otherwise, shall set the reason IE as "MEDIA FAILURE";
f) shall send a PRIVATE CALL REJECT message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1; and
g) shall remain in the current state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.6 Downgrade call | 11.2.3.4.6.1 User cancels the emergency private call
When in the "Q2: in-progress emergency private call" state, upon an indication from:
1) the caller of the emergency private call; or
2) the recipient of the emergency private call with the value of "/<x>/<x>/Common/PrivateCall/EmergencyCall/CancelPriority" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] set to "true",
to cancel the emergency private call, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in clause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller; and
c) shall set the MCPTT user ID of the callee IE with the stored callee.
2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall stop TFP1 (private call request retransmission), if running;
4) shall stop TFP8 (implicit downgrade) timer;
5) shall initialize the counter CFP6 (emergency private call cancel retransmission) with the value set to 1;
6) shall start timer TFP6 (emergency private call cancel retransmission);
7) shall set the stored current call type to "PRIVATE CALL"; and
8) shall enter the "Q1: in-progress private call" state.
11.2.3.4.6.2 Emergency private call cancel retransmission
When in the "Q1: in-progress private call" state, upon expiry of timer TFP6 (emergency private call cancel retransmission) and the value of the counter CFP6 (emergency private call cancel retransmission) is less than upper limit, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL message as specified in clause 15.1.12. In the PRIVATE CALL EMERGENCY CANCEL message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with the stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with store callee ID.
2) shall send the PRIVATE CALL EMERGENCY CANCEL message according to rules and procedures as specified in clause 11.2.1.1.1;
3) shall increment the value of the timer CFP6 (emergency private call cancel retransmission) by 1;
4) shall start timer TFP6 (emergency private call cancel retransmission); and
5) shall remain in the "Q1: in-progress private call" state.
11.2.3.4.6.3 Emergency private call cancel accepted
When in the "Q1: in-progress private call" state, upon receiving a PRIVATE CALL EMERGENCY CANCEL ACK message response to PRIVATE CALL EMERGENCY CANCEL message with the same "call identifier", the MCPTT client:
1) shall stop timer TFP6 (emergency private call cancel retransmission), if running;
2) shall establish a media session based on the SDP body of the stored answer SDP;
3) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]; and
4) shall remain in the "Q1: in-progress private call" state.
11.2.3.4.6.4 No response to emergency private call cancel
In the "Q1: in-progress private call" state, when timer TFP6 (emergency private call cancel retransmission) expires and the value of the counter CFP6 (emergency private call cancel retransmission) is equal to the upper limit, the MCPTT client:
1) shall release the stored current call type;
2) shall release the stored Prose per-packet priority; and
3) shall enter "Q0: waiting for the call to be established".
11.2.3.4.6.5 Responding to emergency private call cancel
When in the "Q1: in-progress private call" state or "Q2: in-progress emergency private call" state, upon receiving a PRIVATE CALL EMERGENCY CANCEL message with the same "call identifier" IE, the MCPTT client:
1) shall generate a PRIVATE CALL EMERGENCY CANCEL ACK as specified in clause 15.1.13:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the callee IE with own MCPTT user ID; and
c) shall set the MCPTT user ID of the caller IE with MCPTT user ID of the caller IE in received message;
2) shall send PRIVATE CALL EMERGENCY CANCEL ACK message according to rules and procedures as specified in clause 11.2.1.1.1;
3) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP8 (implicit downgrade);
4) shall establish a media session based on the SDP body of the stored answer SDP;
5) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45]; and
6) shall enter the "Q1: in-progress private call" state and set the stored current call type to "PRIVATE CALL", if current state is the "Q2: in-progress emergency private call" state.
11.2.3.4.6A Implicit downgrade
When in the "Q2: in-progress emergency private call" state, upon expiry of TFP8 (implicit downgrade) timer, the MCPTT client:
1) shall establish a media session based on the SDP body of the stored answer SDP;
2) shall set the ProSe per-packet priority to the value corresponding to MCPTT off-network private call as described in 3GPP TS 24.483 [45];
3) shall set the stored current call type to "PRIVATE CALL"; and
4) shall enter the "Q1: in-progress private call" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.7 Call Release | When in state "Q1: in-progress private call" or "Q2: in-progress emergency private call", upon receiving an indication from MCPTT user to release the call or upon receiving PRIVATE CALL RELEASE message, the MCPTT client:
1) shall release the stored current call type;
2) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP1 (private call request retransmission), if running;
3) if in the "Q1: in-progress private call" state, shall stop timer TFP6 (emergency private call cancel retransmission), if running;
4) if in the "Q2: in-progress emergency private call" state, shall stop timer TFP8 (implicit downgrade);
5) shall release the stored Prose per-packet priority; and
6) shall enter "Q0: waiting for the call to be established".
11.2.3.4.7A Private call setup request accepted
When in the "Q1: in-progress private call" state, upon receiving a PRIVATE CALL ACCEPT message response to PRIVATE CALL SETUP REQUEST message with the same call identifier, the MCPTT client:
1) shall generate a PRIVATE CALL ACCEPT ACK message as specified in clause 15.1.11:
a) shall set the Call identifier IE to the stored call identifier;
b) shall set the MCPTT user ID of the caller IE with stored caller ID; and
c) shall set the MCPTT user ID of the callee IE with the stored callee ID;
2) shall send the PRIVATE CALL ACCEPT ACK message in response to the request message according to rules and procedures as specified in clause 11.2.1.1.1; and
3) shall remain in the current state.
NOTE: PRIVATE CALL ACCEPT ACK message is retransmitted, as described in this clause, every time a PRIVATE CALL ACCEPT message is received. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 11.2.3.4.8 Error handling | 11.2.3.4.8.1 Unexpected MONP message received
Upon receiving a MONP message in a state where there is no handling specified for the MONP message, the MCPTT client shall discard the MONP message.
11.2.3.4.8.2 Unexpected indication from MCPTT user
Upon receiving an indication from the MCPTT user in a state where there is no handling specified for the indication, the MCPTT client shall ignore the indication.
11.2.3.4.8.3 Unexpected expiration of a timer
Upon expiration of a timer in a state where there is no handling specified for expiration of the timer, the MCPTT client shall ignore the expiration of the timer. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12 Emergency alert | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.0 General | This clause describes the emergency alert procedures for on-network and off-network.
For on-network emergency alert, the procedures for originating and terminating MCPTT clients, participating MCPTT functions and controlling MCPTT function are specified in clause 12.1. MCPTT emergency call procedures that have emergency alerts as an optional capability shall be performed as defined in clause 10.1 for on-network group call and defined in clause 11.1 for on-network private call.
For off-network emergency alert, the procedures for each functional entity is specified in clause 12.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1 On-network emergency alert | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.1 Emergency alert origination | Upon receiving a request from the MCPTT user to send an MCPTT emergency alert to the indicated MCPTT group shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
1) should indicate to the MCPTT user that alerts are not allowed on the indicated group; and
2) shall skip the remainder of this procedure.
If this is an authorised request for an MCPTT emergency alert as determined by clause 6.2.8.1.6, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to:
i) if the <EmergencyAlert> element of the MCPTT user profile exists, then:
A) if the <entry-info> attribute of the <entry> element of the <EmergencyAlert> element is set to the value 'DedicatedGroup', the value in the <uri-entry> element of the <entry> element of the <EmergencyAlert> element; and
B) if the <entry-info> attribute of the <entry> element of the <EmergencyAlert> element is set to the value 'UseCurrentlySelectedGroup' and there is no currently selected group, the value in the <uri-entry> element of the <entry> element of the <EmergencyAlert> element; and
ii) if the <EmergencyAlert> element of the MCPTT user profile does not exist, the group identity selected by the MCPTT user;
b) the <alert-ind> element set to a value of "true";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
NOTE 2: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
5) shall include in the SIP MESSAGE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
6) shall set the MCPTT emergency state if not already set;
7) shall set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending";
8) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
9) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated".
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT emergency alert state to "MEA 1: no-alert".
NOTE 3: The MCPTT emergency state is left set in this case as the MCPTT user presumably is in the best position to determine whether or not they are in a life-threatening condition. The assumption is that the MCPTT user can clear the MCPTT emergency state manually if need be.
NOTE 4: Based on implementation the MCPTT client can subsequently automatically originate an MCPTT emergency group call as specified in clause 10.1.1.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.2 Emergency alert cancellation | Upon receiving a request from the MCPTT user to send an MCPTT emergency alert cancellation to the indicated MCPTT group and this is an authorised request for an MCPTT emergency alert cancellation as determined by clause 6.2.8.1.6, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
2) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
3) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity;
b) the <alert-ind> element set to a value of "false";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
NOTE 1A: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
e) if the MCPTT user is cancelling an MCPTT emergency alert originated by another MCPTT user, include the <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT emergency alert;
5) if the MCPTT user has additionally requested the cancellation of the in-progress emergency state of the MCPTT group and this is an authorised request for an in-progress emergency group state cancellation as determined by clause 6.2.8.1.7, shall include an <emergency-ind> element set to a value of "false" in the <mcpttinfo> element containing the <mcptt-Params> element;
6) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
7) if the generated SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind-rcvd> element set to true and an <mcptt-client-id> matching the MCPTT client ID included in the sent SIP MESSAGE request:
1) if the <alert-ind> element is set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall:
a) set the MCPTT emergency alert state to "MEA 1: no-alert"; and
b) clear the MCPTT emergency state if not already cleared;
2) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT emergency alerts but not have the authority to clear them. Hence, the case is covered here.
3) if an <emergency-ind> element is present in the application/vnd.3gpp.mcptt-info+xml MIME body of received SIP MESSAGE request is set to a value of "false" and the sent SIP MESSAGE request contains an <emergency-ind> element set to a value of "false":
a) shall set the MCPTT emergency group call state of the group to "MEGC 1: emergency-gc-capable"; and
b) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency".
NOTE 3: The case where an <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:
1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true", the sent SIP MESSAGE request did not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 4: In this case, an <emergency-ind> element would either not be present or would be set to true. In either case, no change in state would result. Hence, this case is not specified above.
2) if the received SIP 4xx response, SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request does not contain an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element, the sent SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.3 MCPTT client receives an MCPTT emergency alert or call notification | Upon receipt of a "SIP MESSAGE request for emergency notification", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true", may display to the MCPTT user the functional alias of the originating MCPTT user, if provided, and should display to the MCPTT user an indication of the MCPTT emergency alert and associated information, including:
a) the MCPTT group identity contained in <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
b) the originator of the MCPTT emergency alert contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
c) the mission critical organization of the MCPTT emergency alert originator contained in the <mc-org> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE 1: This is the case of the MCPTT client receiving the notification of another MCPTT user's emergency alert.
2) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the MCPTT emergency alert cancellation and associated information, including:
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body;
ii) the originator of the MCPTT emergency alert contained in:
A) if present, the <originated-by> element of the application/vnd.3gpp.mcptt-info+xml MIME body; or
B) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) if the MCPTT ID contained in the <originated-by> element is the MCPTT ID of the receiving MCPTT user, shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
c) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element is set to a value of "false":
i) shall set the MCPTT emergency group state to "MEG 1: no-emergency"; and
ii) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
NOTE 2: This is the case of the MCPTT client receiving the notification of the cancellation by a third party of an MCPTT emergency alert. This can be the MCPTT emergency alert of another MCPTT user or the MCPTT emergency alert of the recipient, as determined by the contents of the <originated-by> element. Optionally, notification of the cancellation of the in-progress emergency state of the MCPTT group can be included.
3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "true":
a) should display to the MCPTT user an indication of the additional emergency MCPTT user participating in the MCPTT emergency group call including the following if not already displayed as part of step 1):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT emergency group state to "MEG 2: in-progress" if not already set to that value;
NOTE 3: This is the case of the MCPTT client receiving notification of an additional MCPTT user in an MCPTT emergency state (i.e., not the MCPTT user that originally triggered the in-progress emergency state of the group) joining the in-progress emergency group call or in the case of MCPTT client not participating in an in-progress emergency group call but affiliated to group to receive notification of an MCPTT users having MCPTT outstanding emergency call. An emergency alert indication, if included, is handled in step 1).
4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress emergency state of the MCPTT group call including the following if not already displayed as part of step 2):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT emergency group state to "MEG 1: no-emergency"; and
c) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
NOTE 4: This is the case of the MCPTT client receiving the notification of the cancellation of the in-progress emergency state of the MCPTT group. In this case, the receiving MCPTT client is affiliated with the MCPTT group but not participating or participating in the session. An emergency alert cancellation, if included, is handled in step 2).
5) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true":
a) should display to the MCPTT user an indication of the MCPTT user participating in the MCPTT imminent peril group call including the following if not already displayed as part of step 1):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall set the MCPTT imminent peril group state to "MIG 2: in-progress" if not already set to that value;
NOTE 5: This is the case of the MCPTT client receiving notification of an additional MCPTT user initiating an imminent peril group call when there is already an in-progress imminent peril state in effect on the group.
6) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress imminent peril state of the MCPTT group including the following if not already displayed as part of step 2):
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
b) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
c) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
NOTE 6: This is the case of the MCPTT client receiving notification of the cancellation of the in-progress imminent peril state of the group.
7) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
8) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.4 MCPTT client receives notification of entry into or exit from a group geographic area | Upon receipt of a "SIP MESSAGE request for notification of entry into or exit from a group geographic area", the MCPTT client;
1) shall send a SIP 200 (OK) to the participating MCPTT function that sent the SIP MESSAGE request; and
2) if the <group-geo-area-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is:
a) set to "true":
i) may display to the MCPTT user an indication that a group geographic area has been entered; and
ii) shall execute the procedure in clause 9.2.1.2 to affiliate to the group indicated by the participating MCPTT function; or
b) set to "false":
i) may display to the MCPTT user an indication that a group geographic area has been exited; and
ii) shall execute the procedure in clause 9.2.1.2 to de-affiliate from the group indicated by the participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.5 MCPTT group in-progress emergency group state cancel | Upon receiving a request from an MCPTT user to cancel the in-progress emergency condition on a prearranged MCPTT group on which there is no call ongoing, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress emergency group state of the MCPTT group as determined by the procedures of clause 6.2.8.1.7, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress emergency group state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity; and
b) the <emergency-ind> element set to a value of "false";
6) if the MCPTT user has additionally requested the cancellation of an MCPTT emergency alert originated by MCPTT user, shall include an <alert-ind> element set to a value of "false" in the <mcpttinfo> element containing the <mcptt-Params> element;
7) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
8) if the generated SIP MESSAGE request contain an <alert -ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
9) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receipt of a SIP MESSAGE request containing an application/vnd.3gpp.mcptt-info+xml MIME body with an <emergency-ind-rcvd> element set to a value of "true" and an <mcptt-client-id> matching the MCPTT client ID included in the sent SIP MESSAGE request:
1) if an <emergency-ind> element is present in the application/vnd.3gpp.mcptt-info+xml MIME body of received SIP MESSAGE request and is set to a value of "false":
a) shall set the MCPTT emergency group state of the group to "MEG 1: no-emergency".
NOTE 3: The case where an <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes.
2) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "true" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT emergency alerts but not have the authority to clear them. Hence, the case is covered here.
3) if the <alert-ind> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request is set to a value of "false" and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body, shall:
a) set the MCPTT emergency alert state to "MEA 1: no-alert"; and
b) clear the MCPTT emergency state if not already cleared;
On receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to the sent SIP MESSAGE request:
1) if the received SIP 4xx response, SIP 5xx response or SIP 6xx response contains an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true" and the sent SIP MESSAGE request contain an <alert-ind> element set to value "false" in the application/vnd.3gpp.mcptt-info+xml MIME body and the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
NOTE 4: In this case, <emergency-ind> element is set to true is possible but not handled specifically above as it results in no state changes. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.1.6 MCPTT client receives notification of entry into or exit from an emergency alert area | Upon receipt of a "SIP MESSAGE request for notification of entry into or exit from an emergency alert area", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-alert-area-ind> element value:
a) set to "true":
i) may display to the MCPTT user an indication that MCPTT client has entered a pre-defined emergency alert area; and
ii) if the MCPTT user is not in emergency state, shall initiate the emergency alert origination procedure as specified in clause 12.1.1.1; or
b) set to "false":
i) may display to the MCPTT user an indication that MCPTT client has exited a pre-defined emergency alert area;
NOTE: In this case, the MCPTT emergency state remains set, as the MCPTT user is in the best position to determine whether or not they are in a life-threatening condition. The MCPTT user can clear the MCPTT emergency state manually, if needed.
2) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
3) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.2 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.2.1 Receipt of a SIP MESSAGE request for emergency notification from the served MCPTT client | Upon receipt of a "SIP MESSAGE request for emergency notification for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can, according to local policy, choose to accept the request.
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the MCPTT user is not affiliated with the MCPTT group as determined by clause 9.2.2.2.11, shall perform the actions specified in clause 9.2.2.2.12 for implicit affiliation;
4) if the actions for implicit affiliation specified in step 3) above were performed but not successful in affiliating the MCPTT user due to the MCPTT user already having N2 simultaneous affiliations(specified in the <MaxAffiliationsN2> element of the <Common> element of the corresponding MCPTT user profile of the served MCPTT ID), shall reject the "SIP MESSAGE request for emergency notification for originating participating MCPTT function" with a SIP 486 (Busy Here) response with the warning text set to "102 too many simultaneous affiliations" in a Warning header field as specified in clause 4.4. and skip the rest of the steps.
NOTE 3: N2 is the total number of MCPTT groups that an MCPTT user can be affiliated to simultaneously as specified in 3GPP TS 23.379 [3].
NOTE 4: As this is a request for MCPTT emergency services, the participating MCPTT function can choose to accept the request.
5) shall determine the public service identity of the controlling MCPTT function associated with the group identity in the received SIP MESSAGE request;
NOTE 5: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 6: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 7: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 8: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 9: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5) above;
8) shall copy the contents of the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8a) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID. If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise it shall not include a <functional-alias-URI> element;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3 shall copy the contents of the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-location-info+xml MIME body included in the outgoing SIP MESSAGE request;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
12) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent in step 10):
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
2) if the procedures of clause 9.2.2.2.12 for implicit affiliation were performed in the present clause, shall complete the implicit affiliation by performing the procedures of clause 9.2.2.2.13; and
3) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the sent SIP MESSAGE request and if the implicit affiliation procedures of clause 9.2.2.2.12 were invoked in the present clause, the participating MCPTT function shall perform the procedures of clause 9.2.2.2.14. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.2.2 Receipt of a SIP MESSAGE request for emergency notification for terminating MCPTT client | In the procedures in this clause:
1) emergency indication in an incoming SIP MESSAGE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) alert indication in an incoming SIP MESSAGE request refers to the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP MESSAGE request for emergency notification for terminating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
NOTE 1: if the SIP MESSAGE request contains an emergency indication set to a value of "true" or an alert indication set to a value of "true", the participating MCPTT function can by means beyond the scope of this specification choose to accept the request.
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.2.3 Receipt of a SIP MESSAGE request indicating successful delivery of emergency notification | Upon receipt of a SIP MESSAGE request routed to the terminating participating MCPTT function with the Request-URI set to the public service identity of the terminating participating MCPTT function and the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind-rcvd> or <emergency-ind-rcvd> element present, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated to the MCPTT ID of the MCPTT user that was in the Request-URI of the incoming SIP MESSAGE request;
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; and
d) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.3 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.3.1 Handling of a SIP MESSAGE request for emergency notification | Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE: If the SIP MESSAGE request contains an alert indication set to a value of "true", the controlling MCPTT function can, according to local policy, choose to accept the request.
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "168 alert is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false", the <emergency-ind> element present or not and call is ongoing on associated group on which outstanding alert exists, shall perform the procedures specified in clause 12.1.3.2 and skip the rest of the steps;
3a) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false", the <alert-ind> element present or not and no call is ongoing on the group on which in-progress emergency state cancelation request is recieved, shall perform the procedures specified in clause 12.1.3.3 and skip the rest of the steps;
4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "true":
a) if the received SIP MESSAGE request is an unauthorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1 shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "false"; and
ii) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps; and
b) if the received SIP MESSAGE request is an authorised request for an MCPTT emergency alert as specified in clause 6.3.3.1.13.1:
i) if the sending MCPTT user identified by the <mcptt-calling-user-id> element included in the application/vnd.3gpp.mcptt-info+xml MIME body is not affiliated with the MCPTT group identified by the <mcptt-request-uri> element of the MIME body as determined by the procedures of clause 6.3.6:
I) shall check if the MCPTT user is eligible to be implicitly affiliated with the MCPTT group as determined by clause 9.2.2.3.6;
II) if the MCPTT user is determined not to be eligible to be implicitly affiliated to the MCPTT group shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below; or
III) if the procedures of clause 9.2.2.3.6 determined the MCPTT user to be eligible to be implicitly affiliated to the MCPTT group shall, perform the implicit affiliation as specified in clause 9.2.2.3.7;
ii) for each of the other affiliated members of the group:
A) generate an outgoing SIP MESSAGE request notification of the MCPTT user's emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.12;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request; and
C) send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4];
iii) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
A) shall cache the information that the MCPTT user has initiated an MCPTT emergency alert;
iv) shall send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4].
v) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an emergency alert, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body:
A) the <alert-ind> element set to a value of "true";
B) the <alert-ind-rcvd> element set to a value of true; and
C) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
vi) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.3.2 Handling of a SIP MESSAGE request for emergency alert cancellation | Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false", the controlling MCPTT function:
1) if the received SIP MESSAGE request is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.1:
a) and if the received SIP MESSAGE request does not contain an <emergency-ind> element set to a value of "false" or is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4] with the following clarifications:
i) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <alert-ind> element set to a value of "true";
ii) if the received SIP MESSAGE request contains an <emergency-ind> element of the <mcpttinfo> element set to a value of "false" and if the in-progress emergency state of the group is set to a value of "true" and this is an unauthorised request for an MCPTT emergency call cancellation as determined in step i) above, shall include an <emergency-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP 403 (Forbidden) response; and
iii) shall send the SIP 403 (Forbidden) response according to rules and procedures of 3GPP TS 24.229 [4] and skip the rest of the steps; and
b) and if the received SIP MESSAGE request contains an <emergency-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the MCPTT group is set to a value of "true":
i) shall set the in-progress emergency state of the group to a value of "false";
ii) shall clear the cache of the MCPTT ID of the MCPTT user that triggered the setting of the in-progress emergency state of the MCPTT group to "true";
iii) shall generate SIP re-INVITE requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5];
iv) for each of the affiliated but not joined members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
B) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request; and
C) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
v) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
vi) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
vii) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation
viii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request:
A) the <alert-ind> element set to a value of "true";
B) the <alert-ind-rcvd> element set to a value of true;
C) the <emergency-ind> element set to a value of "false"; and
D) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
ix) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4]; and
2) if the received SIP MESSAGE request is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3:
a) if the received SIP MESSAGE request contains an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, shall clear the cache of the MCPTT ID of the MCPTT user identified by the <originated-by> element as having an outstanding MCPTT emergency alert;
b) if the received SIP MESSAGE request does not contain an <originated-by> element in the application/vnd.3gpp.mcptt-info+xml MIME body, clear the cache of the MCPTT ID of the sender of the SIP MESSAGE request as having an outstanding MCPTT emergency alert;
c) if the received SIP MESSAGE request does not contain an <emergency-ind> element set to a value of "false" or is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, for each of the affiliated members of the group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency alert as specified in clause 6.3.3.1.11;
ii) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
iii) if the received SIP MESSAGE 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 MESSAGE request;
iv) shall include an <alert-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
v) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
d) if the received SIP MESSAGE request contains an <emergency-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4 and the in-progress emergency state of the MCPTT group is set to a value of "true":
i) shall set the in-progress emergency state of the group to a value of "false";
ii) cache the information that the MCPTT user has cancelled the outstanding in-progress emergency state of the group;
iii) shall generate SIP re-INVITES requests to the other affiliated and joined members of the MCPTT group as specified in clause 6.3.3.1.6. The MCPTT controlling function:
A) for each affiliated and joined member shall send the SIP re-INVITE request towards the MCPTT client as specified in 3GPP TS 24.229 [4]; and
B) Upon receiving a SIP 200 (OK) response to the SIP re-INVITE request the controlling MCPTT function shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
iv) for each of the affiliated but not joined members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency call as specified in clause 6.3.3.1.11;
B) include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <mcptt-calling-user-id> element set to the value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
C) if the received SIP MESSAGE 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 MESSAGE request;
D) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to a value of "false"; and
E) shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
e) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
f) shall send the SIP 200 (OK) response to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4].
g) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of the request for emergency alert cancellation;
h) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body, the <alert-ind> element set to a value of "false" and the <alert-ind-rcvd> set to "true";
i) shall populate the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
j) if the received SIP MESSAGE request contains an <emergency-ind> element of the <mcpttinfo> element set to a value of "false":
i) if this is an authorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, shall include an <emergency-ind> element set to a value of "false" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
ii) otherwise, if this is an unauthorised request for an MCPTT emergency call cancellation as specified in clause 6.3.3.1.13.4, and the in-progress emergency state of the group is set to a value of "true", shall include an <emergency-ind> element set to a value of "true" in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
k) shall send the SIP MESSAGE request according to according to the rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.