hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.3.3 Handling of a SIP MESSAGE request for in-progress emergency group state 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 <emergency-ind> element set to a value of "false" and no call is ongoing on the group on which in-progress emergency cancellation request is made, the controlling MCPTT function:
1) if the received SIP MESSAGE request is an unauthorised request for an MCPTT in-progress emergency group state cancellation as specified in clause 6.3.3.1.13.4:
a) and if the received SIP MESSAGE request does not contain an <alert-ind> element or is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, 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 <emergency-ind> element set to a value of "true";
ii) if the received SIP MESSAGE request contains an <alert-ind> element of the <mcpttinfo> element set to a value of "false" and this is an unauthorised request for an MCPTT emergency alert cancellation as determined in step a) above and the emergency state of the MCPTT user has outstanding emergency state, shall include an <alert-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 <alert-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and the MCPTT user has outstanding emergency state:
i) shall clear the cache of the MCPTT ID of the MCPTT user that has the outstanding emergency alert state;
ii) for each of the affiliated members of the group shall:
A) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's emergency alert 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 <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;
D) 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];
iv) 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;
v) 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
vi) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP MESSAGE request:
A) the <emergency-ind> element set to a value of "true";
B) the <emergency-ind-rcvd> element set to a value of "true";
C) the <alert-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
vii) 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 in-progress emergency group state cancellation as specified in clause 6.3.3.1.13.4:
a) shall set the in-progress emergency state of the group to a value of "false";
b) cache the information that the MCPTT user has cancelled the outstanding in-progress emergency state of the group and clear the cache of the all MCPTT ID of the MCPTT users that triggered the setting of the in-progress emergency state of the MCPTT group to "true";
c) if the received SIP MESSAGE request contains an <alert-ind> element set to a value of "false" and is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3 and the MCPTT user has outstanding emergency state, clear the cache of the MCPTT ID of the sender of the SIP MESSAGE request as having an outstanding MCPTT emergency alert;
d) 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/group emergency state as specified in clause 6.3.3.1.11;
ii) 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;
iii) 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;
iv) if the received SIP MESSAGE request contains an <alert-ind> element of the <mcpttinfo> element set to a value of "false" and this is an authorised request for an MCPTT emergency alert cancellation as determined in step c) above, 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 according to according to rules and procedures of 3GPP TS 24.229 [4];
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 in-progress emergency group cancellation;
h) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body, the <emergency-ind> element set to a value of "false" and the <emergency-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 <alert-ind> element of the <mcpttinfo> element set to a value of "false":
i) if this is an authorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, 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
B) otherwise, if this is an unauthorised request for an MCPTT emergency alert cancellation as specified in clause 6.3.3.1.13.3, shall include an <alert-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]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.1.3.4 Late emergency alert initiated by controlling MCPTT function | When controlling MCPTT function is notified that an MCPTT client is newly affiliated or comes back from out of coverage, the controlling MCPTT function:
NOTE: How the MCPTT function is informed when an MCPTT client is coming back from out of coverage is out of scope of present document.
1) if there is an outstanding MCPTT emergency alert for the MCPTT group to which the user affiliated, and the call is not ongoing on associated group on which outstanding alert exists, for the MCPTT client:
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 MCPTT ID of the MCPTT user who has initiated an MCPTT emergency alert; and
c) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
12.1A On-network MCPTT adhoc group emergency alert
12.1A.1 Client procedures
12.1A.1.1 Ad hoc group emergency alert origination
Upon receiving a request from the MCPTT user to send an MCPTT adhoc group emergency alert, the MCPTT client shall determine if this is an authorised request for the origination of an MCPTT adhoc group emergency alert as specified in the clause 6.2.8.1.19.
If this is an unauthorised request for an MCPTT adhoc group emergency alert, the MCPTT client:
1) should indicate to the MCPTT user that adhoc group emergency alerts are not allowed; and
2) shall skip the remainder of this procedure.
If this is an authorised request, 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) if the MCPTT client needs to include an identity of adhoc group, the <mcptt-request-uri> element set to the identity of the adhoc group;
NOTE 2: The MCPTT client can optionally include an identity of adhoc group if it learns by any means or generated by the MCPTT client using required parameters.
b) the <anyExt> element with the <adhoc-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;
NOTE 3: 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;
f) if the MCPTT user has requested to include additional information related to the MCPTT adhoc emergency alter, the <anyExt> element with the <adhoc-additional-information> element set to the user provided value; and
g) a <call-participants-criterias> with one or more criteria as a comma separated list into <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request;
5) shall include in the SIP MESSAGE request the specific location information for MCPTT adhoc group emergency alert as specified in clause 6.2.9.1;
6) may set the MCPTT emergency state if not already set;
7) may set the MCPTT adhoc group emergency alert state to "AH-MEA 2: adhoc-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 adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated", if the current MCPTT adhoc group emergency alert state is "AH-MEA 2: adhoc-emergency-alert-confirm-pending".
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 adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert".
NOTE 4: 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 5: Based on implementation the MCPTT client can subsequently automatically originate an MCPTT emergency group call as specified in clause 17.2.2.1.1.
12.1A.1.2 Ad hoc group emergency alert cancellation
Upon receiving a request from the MCPTT user to send an MCPTT adhoc group emergency alert cancellation, the MCPTT client shall determine if this is an authorised request for an MCPTT adhoc group emergency alert cancellation as specified in the clause 6.2.8.1.19.
If this is an unauthorised request for an MCPTT adhoc group emergency alert cancellation, the MCPTT client:
1) should indicate to the MCPTT user that adhoc group emergency alert cancellations are not allowed; and
2) shall skip the remainder of this procedure.
If this is an authorised request, 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 adhoc group identity;
b) the <anyExt> element with the <adhoc-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;
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 adhoc group 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 adhoc group emergency alert; and
f) set the MCPTT adhoc group emergency alert state to "AH-MEA 4: adhoc-emergency-alert-cancel-pending";
5) void
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 adhoc group emergency alert state to "AH-MEA 4: adhoc-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 <adhoc-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 <adhoc-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 adhoc group 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 adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert"; and
b) clear the MCPTT emergency state if not already cleared;
2) if the <adhoc-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 adhoc group emergency alert state is set to "AH-MEA 4: adhoc-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 adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated"; and
NOTE 2: It would appear to be an unusual situation for the initiator of an MCPTT adhoc group emergency alert to not be able to clear their own alert. Nevertheless, an MCPTT user can be configured to be authorised to initiate MCPTT adhoc group emergency alerts but not have the authority to clear them. Hence, the case is covered here.
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 containing the <anyExt> element with the <adhoc-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 adhoc group emergency alert state is set to "AH-MEA 4: adhoc-emergency-alert-cancel-pending", shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated"; and
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 <adhoc-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 adhoc group emergency alert state is set to "AH-MEA 4: adhoc-emergency-alert-cancel-pending", shall set the MCPTT adhoc group emergency alert state to "AH-MEA 3: adhoc-emergency-alert-initiated".
12.1A.1.3 MCPTT client receives an MCPTT adhoc group emergency alert notification
Upon receipt of a "SIP MESSAGE request for adhoc group emergency alert notification", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-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 adhoc group 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 adhoc group emergency alert contained in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
c) the mission critical organization of the MCPTT adhoc group emergency alert originator contained in the <mc-org> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
d) the additional information related to the MCPTT adhoc group emergency alert contained in the <anyExt> element with the <adhoc-additional-information> element of the application/vnd.3gpp.mcptt-info+xml MIME body, if present;
NOTE 1: This is the case of the MCPTT client receiving the notification of another MCPTT user’s adhoc group emergency alert.
2) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the MCPTT adhoc group 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 adhoc group 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 adhoc group emergency alert state to "AH-MEA 1: no-adhoc-alert";
NOTE 2: This is the case of the MCPTT client receiving the notification of the cancellation by an MCPTT authorized user of an MCPTT adhoc group emergency alert. This can be the MCPTT adhoc group emergency alert of another MCPTT user or the MCPTT adhoc group emergency alert of the recipient, as determined by the contents of the <originated-by> element.
3) void;
4) void;
5) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
6) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
12.1A.1.4 Void
12.1A.2 Participating MCPTT function procedures
12.1A.2.1 Receipt of a SIP MESSAGE request for adhoc group emergency notification from the served MCPTT client
Upon receipt of a "SIP MESSAGE request for adhoc 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.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) shall determine the public service identity of the controlling MCPTT function for the adhoc group emergency alert service associated with the originating user's identity i.e. MCPTT ID;
NOTE 3: How the participating MCPTT function determines the public service identity of the controlling MCPTT function for the adhoc group emergency alert service associated with the originating user's identity is out of the scope of the present document.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4) above;
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;
7A) may modify based on local policy the content of the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
8) if the received SIP MESSAGE request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall check the status of the functional alias for the MCPTT ID. If the functional alias status is activated, then the participating MCPTT function shall set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the received value, otherwise it shall not include a <functional-alias-URI> element;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) 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) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
12.1A.2.2 Receipt of a SIP MESSAGE request for adhoc group emergency notification for terminating MCPTT client
In the procedures in this clause:
1) alert indication in an incoming SIP MESSAGE request refers to the <adhoc-alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP MESSAGE request for adhoc 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 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;
5) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11; 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 follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.2.3 Receipt of a SIP MESSAGE request indicating successful delivery of adhoc group emergency notification of originating MCPTT client
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 <adhoc-alert-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] towards the originating MCPTT client of the adhoc group emergency alert.
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].
12.1A.2.4 Adhoc group emergency alert participants determination procedure
The participating MCPTT function shall follow the procedures as specified in the clause 17.3.6.1.
12.1A.2.5 Adhoc group emergency alert participants determination stop procedure
The participating MCPTT function shall follow the procedures as specified in the clause 17.3.6.2.
12.1A.2.6 Adhoc group emergency alert participants modify procedure initiated by participating MCPTT function
When the participating MCPTT function determines that new MCPTT users are meeting the specified criteria or the MCPTT users who were meeting the specified criteria are no longer meeting the specified criteria, the participating MCPTT function shall follow the procedures as specified in the clause 17.3.5.2.1.
12.1A.3 Controlling MCPTT function procedures
12.1A.3.1 Handling of adhoc group emergency alert notification
Upon receipt of a "SIP MESSAGE request for adhoc 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 1: 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 received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false", shall perform the procedures specified in clause 12.1A.3.2 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 <adhoc-alert-ind> element set to a value of "true":
a) if the received SIP MESSAGE request is an unauthorised request for an adhoc group emergency alert as specified in clause 6.3.3.1.13.8, 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 containing the <anyExt> element with the < adhoc-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;
b) if the received SIP MESSAGE request is an authorised request for an adhoc group emergency alert as specified in clause 6.3.3.1.13.8, shall determine the MCPTT users that meet the criteria contained in the <call-participants-criterias> contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP MESSAGE request:
NOTE 2: The determination of meeting the criteria is left to implementation and can use additional predefined data stored on the controlling MCPTT function.
i) shall create the adhoc group and generate the group identity to be associated with the adhoc group if the identity of adhoc group included in the <mcptt-request-uri> element of the <mcptt-Params> element of the <mcpttinfo> element containing in an application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP INVITE request is not acceptable or not included;
ii) shall determine the participants of the adhoc group emergency alert and send the adhoc group emergency alert, as specified in clause 12.1A.3.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:
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 cache the information that the MCPTT user has initiated an adhoc group emergency alert;
vi) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.20 to indicate successful receipt of an adhoc group emergency alert to the initiator, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing:
A) the <anyExt> element with the <adhoc-alert-ind> element set to a value of "true";
B) the <anyExt> element with the <adhoc-alert-ind-rcvd> element set to a value of "true";
C) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request;
D) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in this clause; and
E) the <anyExt> element with the <call-participants-criterias> element as determined in step 5) b) in clause 12.1A.3.4; and
vii) shall send the SIP MESSAGE request towards the originating participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]; and
4) shall continue to include the MCPTT users meeting or to remove MCPTT users no longer meeting the criteria as specified in the clause 12.1A.3.3.
12.1A.3.2 Handling of adhoc group emergency alert cancellation
Upon receipt of a "SIP MESSAGE request for adhoc emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-alert-ind> element set to a value of "false", 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 "false", 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";
3) if the received SIP MESSAGE request is an unauthorised request for an adhoc group emergency alert cancellation as specified in clause 6.3.3.1.13.9, 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:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing the anyExt> element with the <adhoc-alert-ind> element set to a value of "true"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
4) if the received SIP MESSAGE request is an authorised request for an adhoc group emergency alert cancellation as specified in clause 6.3.3.1.13.9:
a) shall stop determining the participants of the adhoc group emergency alert, as specified in clause 12.1A.3.5;
b) 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 adhoc group emergency alert;
c) 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 adhoc group emergency alert;
d) for each members of the adhoc group shall:
i) generate a SIP MESSAGE request notification of the cancellation of the adhoc group 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 <adhoc-alert-ind> element set to a value of "false" in an <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request; and
v) send the SIP MESSAGE request towards the terminating MCPTT clients as specified in 3GPP TS 24.229 [4];
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 request towards the originating MCPTT client as specified in 3GPP TS 24.229 [4];
g) to indicate successful receipt of an adhoc group emergency alert cancellation shall:
i) generate a SIP MESSAGE request as described in clause 6.3.3.1.20, and shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing:
A) the <anyExt> element with the <adhoc-alert-ind> element set to a value of "false";
B) the <anyExt> element with the <adhoc-alert-ind-rcvd> element set to a value of true;
C) the <mcptt-client-id> element with the MCPTT client ID that was included in the incoming SIP MESSAGE request; and
D) the <mcptt-calling-group-id> element set to the adhoc group identity received in the incoming SIP MESSAGE request; and
ii) shall send the SIP MESSAGE request towards the originating participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4]; and
h) if no call is in-progress on ad hoc group or once the ongoing adhoc group call is terminated, the cached information about adhoc group is cleared.
12.1A.3.3 Handling of ongoing adhoc group emergency alert
When the controlling MCPTT function is notified that a new MCPTT client is meeting the criteria, or that an MCPTT client does not meet the criteria any more, the controlling MCPTT function:
1) shall for each new user determined to meet the criteria:
a) generate an outgoing SIP MESSAGE request notification of the MCPTT user's adhoc group emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.23;
b) include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <adhoc-alert-ind> element to a value of "true"; and
c) include the <call-participants-criterias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5)/b) in clause 12.1A.3.4; and
d) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4];
2) shall for each new user determined to not meet the criteria anymore:
a) generate an outgoing SIP MESSAGE request notification of the MCPTT user's adhoc group emergency alert indication as specified in clause 6.3.3.1.11 with the clarifications of clause 6.3.3.1.23;
b) include, if not already present, an application/vnd.3gpp.mcptt-info+xml MIME body as specified in Annex F.1, and set the <adhoc-alert-ind> element to a value of "false"; and
c) include the <call-participants-criterias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5)/b) in clause 12.1A.3.4; and
d) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4];
3) shall cache the information of the adhoc group identity and the list of MCPTT users that meet the criteria for the duration of the adhoc group emergency alert.
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests shall:
1) cache the information of the adhoc group identity and a separate list of MCPTT users that meet the criteria but did not respond with a SIP 2xx response to the above SIP MESSAGE request for notification of the MCPTT user's adhoc group emergency alert indication, for the duration of the adhoc group emergency alert;
2) determine the users that are authorized to receive adhoc group emergency alert participant information as described in clause 6.3.3.1.13.10;
3) for each new user determined to be authorized to receive adhoc group emergency alert participant information:
a) shall generate a SIP MESSAGE request as described in clause 6.3.3.1.24; and
b) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
2) follow the procedures specified in 3GPP TS 24.229 [4].
12.1A.3.4 Adhoc group emergency alert participants determination procedures
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.6.1.
12.1A.3.5 Adhoc group emergency alert participants determination stop procedures
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.6.2.
12.1A.3.6 Handling of adhoc group emergency alert participants modify procedure initiated by participating MCPTT function
The controlling MCPTT function shall follow the procedures as specified in the clause 17.4.5.2.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2 Off-network emergency alert | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2 Basic state machine | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2.1 General | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2.2 Emergency alert state machine | The figure 12.2.2.2-1 gives an overview of the main states and transitions on the UE for emergency alert.
Each emergency alert state machine is per MCPTT group.
Figure 12.2.2.2-1: Emergency alert state machine
The following pieces of information are associated with the emergency alert state machine:
a) the stored emergency state of the MCPTT group; and
b) the stored organization name of the MCPPT client.
NOTE: The emergency alert state machine is referred by the MCPTT off-network group call and MCPTT off-network private call procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2.3 Emergency alert states | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2.3.1 E1: Not in emergency state | This state is the start state of this state machine.
The UE stays in this state while not in emergency state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.2.3.2 E2: Emergency state | This state exists for UE, when the UE has sent a GROUP EMERGENCY ALERT message. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3 Procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.1 Originating user sending emergency alert | When in state "E1: Not in emergency state", upon receiving an indication from the MCPTT user to transmit an emergency alert for an MCPTT group ID, and the values of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Authorised" leaf node present in the user profile and "/<x>/<x>/Common/AllowedEmergencyAlert" present in group configuration as specified in 3GPP TS 24.483 [45] are set to "true", the MCPTT client:
1) shall set the stored emergency state as "true";
2) shall set the stored MCPTT group ID to the indicated MCPTT group ID;
3) shall generate a GROUP EMERGENCY ALERT message as specified in clause 15.1.16. In the GROUP EMERGENCY ALERT message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID;
b) shall set the Originating MCPTT user ID IE to own MCPTT user ID;
c) shall set the Organization name IE to own organization name; and
d) may set the User location IE with client's current location, if requested;
4) shall send the GROUP EMERGENCY ALERT message as specified in clause 10.2.1.1.1;
5) shall start timer TFE2 (emergency alert retransmission); and
6) shall enter "E2: Emergency state" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.2 Emergency alert retransmission | When in state "E2: Emergency state", upon expiry of timer TFE2 (emergency alert retransmission), the MCPTT client:
1) shall generate a GROUP EMERGENCY ALERT message as specified in clause 15.1.16. In the GROUP EMERGENCY ALERT message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID;
b) shall set the originating MCPTT user ID IE to own MCPTT user ID;
c) shall set the Organization name IE to own organization name; and
d) may set the Location IE with client's current location, if requested; and
2) shall send the GROUP EMERGENCY ALERT message as specified in clause 10.2.1.1.1;
3) shall start the timer TFE2 (emergency alert retransmission); and
4) shall remain in the current state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.3 Terminating user receiving emergency alert | When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE not stored in the list of users in emergency, the MCPTT client:
1) shall store the Originating MCPTT user ID IE and location IE in the list of users in emergency;
2) shall generate a GROUP EMERGENCY ALERT ACK message as specified in clause 15.1.17. In the GROUP EMERGENCY ALERT ACK message, the MCPTT client:
a) shall set the MCPTT group ID IE to the MCPTT group ID IE of the received GROUP EMERGENCY ALERT message;
b) shall set the Sending MCPTT user ID IE to own MCPTT user ID; and
c) shall set the Originating MCPTT user ID IE to the Originating MCPTT user ID IE of the received GROUP EMERGENCY ALERT message; and
3) shall send the GROUP EMERGENCY ALERT ACK message as specified in clause 10.2.1.1.1;
4) shall start timer TFE1 (emergency alert); and
5) shall remain in the current state.
NOTE: Each instance of timer TFE1 is per MCPTT user ID. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.4 Terminating user receiving retransmitted emergency alert | When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:
1) may update the stored location of the user with the received Location IE;
2) shall restart the associated timer TFE1 (emergency alert); and
3) shall remain in the current state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.5 Originating user cancels emergency alert | When in "E2: Emergency state", upon receiving an indication from the MCPTT user to cancel an emergency alert and the value of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Cancel" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] set to "true", the MCPTT client:
1) shall set the stored emergency state as "false";
2) shall generate a GROUP EMERGENCY ALERT CANCEL message as specified in clause 15.1.18. In the GROUP EMERGENCY ALERT CANCEL message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID;
b) shall set the Originating MCPTT user ID IE to own MCPTT user ID; and
c) shall set the Sending MCPTT user ID IE to own MCPTT user ID;
3) shall send the GROUP EMERGENCY ALERT CANCEL message as specified in clause 10.2.1.1.1;
4) shall stop timer TFE2 (emergency alert retransmission); and
5) shall enter "E1: Not in emergency state" state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.6 Terminating user receives GROUP EMERGENCY ALERT CANCEL message | When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT CANCEL message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:
1) shall remove the MCPTT user ID and associated location information from the stored list of users in emergency;
2) shall generate a GROUP EMERGENCY ALERT CANCEL ACK message as specified in clause 15.1.19. In the GROUP EMERGENCY ALERT CANCEL ACK message, the MCPTT client:
a) shall set the MCPTT group ID IE to the MCPTT group ID IE of the received GROUP EMERGENCY ALERT CANCEL message; and
b) shall set the Sending MCPTT user ID IE to own MCPTT user ID; and
c) shall set the Originating MCPTT user ID IE to the Originating MCPTT user ID IE of the received GROUP EMERGENCY ALERT message;
3) shall send the GROUP EMERGENCY ALERT CANCEL ACK message as specified in clause 10.2.1.1.1;
4) shall stop the associated timer TFE1 (emergency alert); and5) shall remain in the current state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 12.2.3.7 Implicit emergency alert cancel | When in state "E1: Not in emergency state" or in "E2: Emergency state", upon expiry of timer TFE1 (emergency alert) associated with a stored MCPTT user ID, the MCPTT client:
1) shall remove the MCPTT user ID and associated location information from the stored list of users in emergency; and
2) shall remain in the current state. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13 Location procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.1 General | If the participating MCPTT function needs to obtain location information, the participating MCPTT function configures the MCPTT client upon successful service authorization. The configuration contains information the MCPTT client uses to set up filter criteria for when the MCPTT client shall send location reports to the participating MCPTT function.
The participating MCPTT function can also explicitly request the MCPTT client to send a location report.
The MCPTT client will, based on the received configuration or when explicitly requested, send location reports.
The location information is used by the participating MCPTT function to determine whether to use MBMS bearers or not as described in clause 14.
In case of LTE MBMS and 5G MBS co-existence, the inter-RAT information contained in the location information is used by the participating MCPTT function to determine how to receive MCPTT services after inter-RAT change. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2 Participating MCPTT function location procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.1 General | The participating MCPTT function has procedures to:
- configure the location reporting at the UE;
- request the UE to report the location of the UE; and
- receive a location information report from the UE. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.2 Location reporting configuration | The participating MCPTT function may configure the location reporting in the MCPTT client by generating a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function:
1) shall include a Request-URI set to the public user identity corresponding to the identity of the MCPTT client;
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6];
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element containing the MCPTT ID of the MCPTT user to receive the configuration;
4) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with the <Configuration> element contained in the <location-info> root element set to the desired configuration;
5) shall include the TriggerId attribute, with its already assigned value, if existent and valid, or with a newly generated unique value, if not, where defined for the sub-elements defining the trigger criterion;
6) shall include the public service identity of the participating MCPTT function in the P-Asserted-Identity header field;
7) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
8) may include an 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 identity of the user requesting the location information configuration;
9) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
10) shall store the location reporting configuration for the MCPTT client.
NOTE: The participating MCPTT function can first identify the users that have activated a functional alias. It can learn the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.2.2.8.
13.2.2A Location reporting configuration requested by authorized MCPTT client
Upon receiving a SIP MESSAGE containing a location reporting configuration replacement or modification request from an MCPTT client, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall skip the rest of the steps;
2) shall determine the MCPTT ID of the requesting user from public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the requesting user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "192 invalid location request target client list" in a Warning header field, as specified in clause 4.4, and shall not continue with the rest of the steps;
5) shall check if the MC user is authorized to send a location reporting configuration request and if the MC user is not authorized, reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including a warning text set to "194 user not authorized to request location configuration changes" in a Warning header field, as specified in clause 4.4, and shall not continue with the rest of the steps;
NOTE 2: How the participating function determine if the MC user is authorized to send location reporting configuration requests is out of scope of the current specification.
6) shall generate and send a SIP 200 OK response to the SIP MESSAGE request according to 3GPP TS 24.229 [4]; and
7) for each requested MCPTT client identified by the "uri" attribute of each <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body, shall perform the following:
a) if the requested MCPTT client location reporting configuration contains trigger criteria without assigned values for the respective TriggerId attribute, set the same value for the respective TriggerId for all MCPTT clients, different for each individual trigger criterion;
b) if the requested MCPTT client location reporting configuration is not managed by the current participating function, determine the public service identity of the participating MCPTT function managing the requested MCPTT client location reporting configuration and send a copy of the received SIP MESSAGE request with the following modifications; or
NOTE 3: How to determine the public service identity of the participating function is out of scope of the current specification.
i) set the Request-URI to the public service identity of the participating MCPTT function managing the requested MC user location reporting configuration;
ii) update the application/resource-lists+xml MIME body to only include the requested MC user;
iii) 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 identity of the requesting user as determined in step 2; and
iv) send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4]; and
c) if the requested MCPTT client location reporting configuration is managed by the current participating MCPTT function, perform the following:
i) evaluate if the requested MC user has authorized providing the requested MC user's location information to requesting MC user, and if the authorization is not successful, silently ignore the request and not continue with the remaining steps in this clause for this requested MCPTT client; and
NOTE 4: How the requested MCPTT client authorizes sharing of location information with the requesting MC user is out of scope of the current specification.
ii) proceed further as specified in clause 13.2.2, for the requested MCPTT client.
13.2.2B Location reporting configuration request from another MCPTT server
Upon receiving a SIP MESSAGE containing a location reporting configuration request from another MCPTT server, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to determine the MCPTT ID of the requesting user;
3) shall generate and send a SIP 200 OK response to the SIP MESSAGE request according to 3GPP TS 24.229 [4]; and
4) for each requested MCPTT client identified by the "uri" attribute of each <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body, shall perform the following:
i) evaluate if the requested MC user has authorized the requesting MC user to replace or modify the location reporting configuration, and if the authorization was not successful, silently ignore the request and not continue with the remaining steps in this sub clause for this requested MCPTT client; and
NOTE: How the requested MCPTT client authorizes the requesting MC user to replace or modify the location reporting configuration is out of scope of the current specification.
ii) proceed further as specified in clause 13.2.2, for the requested MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.3 Location information request | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.3.1 Location information request to MCPTT client | If the participating MCPTT function needs to request the MCPTT client to report its location, the participating MCPTT functions shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function:
1) shall include a Request-URI set to the URI corresponding to the identity of the MCPTT client;
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6];
3) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with an <mcptt-request-uri> element containing the MCPTT ID of the MCPTT user;
4) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element contained in the <location-info> root element;
5) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
NOTE: The participating MCPTT function can first identify the users that have activated a functional alias. It can learn the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.2.2.8. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.3.2 Location information request from authorized MCPTT client | Upon receiving a SIP MESSAGE containing a location information request from an MCPTT client, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall skip the rest of the steps;
2) shall determine the MCPTT ID of the requesting user from public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the requesting user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "192 invalid location request target client list" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
5) shall check if the MC user is authorized to send a location information request and if the MC user is not authorized, reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including a warning text set to "193 user not authorized to request location information" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
NOTE 2: How the participating function determine if the MC user is authorized to send location information request is out of scope of the current specification.
6) shall generate and send a SIP 200 OK response to the SIP MESSAGE request according to 3GPP TS 24.229 [4]; and
7) shall determine the lists of MCPTT clients for which location information is being requested by the following:
a) determine as being requested each MCPTT client identified by the "uri" attributes of each <entry> element of the <list> element of the <resource-list> element of the application/resource-lists+xml MIME body; or
b) determine as being requested each MCPTT client that has activated the functional alias provided by the <location-of-functional-alias-URI> element into the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body and utilize the functional alias status determination from MCPTT server owning functional alias procedure in clause 9A.2.2.2.7.
7A) for each requested MCPTT client determined in the step 7 perform the following:
a) if the requested MCPTT client location information is not managed by the current participating function, determine the public service identity of the participating MCPTT function serving the requested MCPTT client location information and send a copy of the received SIP MESSAGE request with the following modifications; or
NOTE 3: How to determine the public service identity of the participating function is out of scope of the current specification.
i) set the Request-URI to the public service identity of the participating MCPTT function handling the requested MC user location information;
ii) update the application/resource-lists+xml MIME body to only include the requested MC user;
iii) send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4];
iv) skip the remaining steps in this procedure; and
b) if the requested MCPTT client location information is managed by the current participating MCPTT function, perform the following:
i) evaluate if the requested MC user has authorized providing the requested MC user's location information to requesting MC user, and if the authorization is not successful silently ignore the request and not continue with the remaining steps in this clause for this requested MCPTT client;
NOTE 4: How the requested MCPTT client authorizes sharing of location information with the requesting MCPTT user is out of scope of the current specification.
ii) if the participating MCPTT function does not have any location information stored about the requested MCPTT client or if the "refresh" attribute is set to "true" in the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body then the participating MCPTT function shall request an immediate update of the location information from the requested MCPTT client by sending a location information request according to clause 13.2.3.1, wait for the location information report from the MCPTT client for an implementation dependent period of time, and when received, store/update the reported location information.
iii) if the participating MCPTT function have location information stored but the information is older than an implementation dependent value then the participating MCPTT function shall request an immediate update of the location information from the requested MCPTT client by sending a location information request according to clause 13.2.3.1, wait for the location information report from the MCPTT client for an implementation dependent period of time, and, when received, store/update the reported location information.
iv) if the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE contains a <LocationFilter> element of the <anyExt> element of "location‑info", then the participating MCPTT function:
A) if the <AreaIn> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info" is set to "true" and the requested MCPTT client is outside the geographical area identified by the TriggerId content of the <AreaIdentifier> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info", skip the remaining steps in this procedure; or
B) if the <AreaIn> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info" is set to "false" and the requested MCPTT client is inside the geographical area identified by the TriggerId content of the <AreaIdentifier> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info", skip the remaining steps in this procedure; and
v) generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33], according to the following.
A) set the Request-URI of the SIP MESSAGE to the public user identity bound to the MCPTT ID of the requesting user;
B) include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include a <Report> element and include the <ReportID> attribute set to the value of the <RequestID> attribute in the received request;
C) in the application/vnd.3gpp.mcptt-location-info+xml MIME body include current location information of the requested MCPTT client in the <CurrentLocation> element in the <Report> element;
NOTE 5: The type of location information reported (e.g., cell id, geographical coordinates) is based on location information configuration and implementation.
D) in the application/vnd.3gpp.mcptt-location-info+xml MIME body include the MCPTT ID of the requested MCPTT client in the <mcptt-reporting-uri> element in the <Report> element; and
E) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.3.3 Location information request from another MCPTT server | Upon receiving a SIP MESSAGE containing a location information request from an another MCPTT server, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall skip the rest of the steps;
2) shall determine the MCPTT ID of the requesting user from public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the requesting user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) shall generate and send a SIP 200 OK response to the SIP MESSAGE request according to 3GPP TS 24.229 [4]; and
4) for each requested MCPTT client identified by the "uri" attribute of each <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body shall perform the following:
i) evaluate if the requested MC user has authorized providing the requested MC user's location information to requesting MC user, and if the authorization is not successful, silently ignore the request and not continue with the remaining steps in this clause for this requested MCPTT client; and
NOTE 2: How the requested MCPTT client authorizes sharing of location information with the requesting MC user is out of scope of the current specification.
ii) if the participating MCPTT function does not have any location information stored about the requested MCPTT client or if the "refresh" attribute is set to "true" in the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body then the participating MCPTT function shall request an immediate update of the location information from the requested MCPTT client by sending a location information request according to clause 13.2.3.1, wait for the location information report from the MCPTT client for an implementation dependent period of time, and, when received, store/update the reported location information.
iii) if the participating MCPTT function have location information stored but the information is older than an implementation dependent value then the participating MCPTT function shall request an immediate update of the location information from the requested MCPTT client by sending a location information request according to clause 13.2.3.1, wait for the location information report from the MCPTT client for an implementation dependent period of time, and, when received, store/update the reported location information.
iv) if the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body in the received SIP MESSAGE contains a <LocationFilter> element of the <anyExt> element of "location‑info", then the participating MCPTT function:
A) if the <AreaIn> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info" is set to "true" and the requested MCPTT client is outside the geographical area identified by the TriggerId content of the <AreaIdentifier> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info", skip the remaining steps in this procedure; or
B) if the <AreaIn> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info" is set to "false" and the requested MCPTT client is inside the geographical area identified by the TriggerId content of the <AreaIdentifier> sub-element of the <LocationFilter> element of the <anyExt> element of "location‑info", skip the remaining steps in this procedure; and
v) generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33], according to the following:
A) set the Request-URI of the SIP MESSAGE to the public service identity of the participating MCPTT function associated to the requesting MCPTT user;
B) include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include a <Report> element and include the <ReportID> attribute set to the value of the <RequestID> attribute in the received request;
C) in the application/vnd.3gpp.mcptt-location-info+xml MIME body include current location information of the requested MCPTT client in the <CurrentLocation> element in the <Report> element;
NOTE 3: The type of location information reported (e.g., cell id, geographical coordinates) is based on location information configuration and implementation.
D) in the application/vnd.3gpp.mcptt-location-info+xml MIME body include the MCPTT ID of the requested MCPTT client in the <mcptt-reporting-uri> element in the <Report> element; and
E) send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.4 Location information report | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.4.1 Location information report from an MCPTT client | If the participating MCPTT function receives a SIP request containing:
1) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
2) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
then the participating MCPTT function shall authorise the location report based on the MCPTT ID received. If the MCPTT user is authorised to send a location report the participating MCPTT function:
1) shall use the location information as needed; and
2) shall follow the procedure of clause 6.3.2.4.1, if the MCPTT client has entered into or exited from an emergency alert area ;and
3) shall follow the procedure of clause 6.3.2.4.2, if the MCPTT client has entered into or exited from a group geographic area.
NOTE: The <Report> element contains the event triggering identity in the location information report from the UE, and can contain location information. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.4.2 Location information report from another MCPTT server | If the participating function receives a location information report from another server containing:
1) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
2) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element including a <ReportID> attribute and a <mcptt-reporting-uri> element included in the <location-info> root element;
then the participating function shall update the Request-URI and forward the report to the requesting MCPTT client.
NOTE: this case occurs when another MCPTT participating function forwards a location information report, as described in clause 13.2.3.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.2.5 Abnormal cases | Upon receipt of a SIP request:
1) where the P-Asserted-Identity identifies a public user identity not associated with an MCPTT user served by the participating MCPTT function; or
2) with a MIME body with Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and with a <mcptt-request-URI> element containing an MCPTT ID that identifies an MCPTT user served by the participating MCPTT function;
then, when the SIP request contains:
1) an Accept-Contact header field with the g.3gpp.mcptt media feature tag;
2) an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
3) an application/vnd.3gpp.mcptt-location-info+xml MIME body containing a <Request> element or a <Configuration> element;
the participating MCPTT function shall remove the application/vnd.3gpp.mcptt-location-info+xml MIME body from the outgoing SIP request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3 MCPTT client location procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.1 General | The MCPTT client sends a location report when one of the trigger criteria is fulfilled or when it receives a request from the participating MCPTT function to send a location report. To send the location report the MCPTT client can use an appropriate SIP message that it needs to send for other reasons, or it can include the location report in a SIP MESSAGE request.
To send a location report, the MCPTT client includes in the SIP MESSAGE request an application/vnd.3gpp.mcptt-location-info+xml MIME body as specified in clause F.3. The MCPTT client populates the elements in accordance with its reporting configuration. Further location information may also be included in the P-Access-Network-Info header field. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.2 Location reporting configuration | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.2.1 MCPTT client receiving location reporting configuration | Upon receiving a SIP MESSAGE request containing:
1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Configuration> root element included in the <location-info> root element;
then the MCPTT client:
1) shall replace or modify the stored contents of the <Configuration> elements, consistent with the <ConfigScope> value, and then store the location configuration;
NOTE: The MCPTT client only needs to store the latest received location reporting configuration.
2) shall set the location reporting triggers accordingly; and
3) shall start the minimumReportInterval timer. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.2.2 Authorized MCPTT client sending location reporting configuration | To request replacement or modification of the location reporting configuration for one or several MCPTT clients, an authorized MC user’s MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33], as follows:
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 set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
5) shall include in the "uri" attribute of each <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body set to the MCPTT ID of the requested MCPTT users for which replacement or modification of location reporting configuration is being requested, according to rules and procedures of IETF RFC 5366 [20];
6) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Configuration> element contained in the <location-info> root element; and
7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.3 Location information request | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.3.1 Location information request to MCPTT client | Upon receiving a SIP MESSAGE request containing
1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
3) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element included in the <location-info> root element;
then the MCPTT client:
1) shall send a location report as specified in clause 13.3.4; and
2) shall reset the minimumReportInterval timer. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.3.2 Location information request from authorized MCPTT client | If a MC user needs to request the location information for one or several MCPTT clients, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33].
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 set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
5) shall include either a list of MCPTT IDs of the MCPTT users for which location information is being requested or one activated functional alias that is used to identify the MCPTT clients for which location information is being requested according to the following:
i) include in the "uri" attribute of each <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body set to the MCPTT ID of the requested MCPTT users for which location information is being requested, according to rules and procedures of IETF RFC 5366 [20]; or
ii) include a <location-of-functional-alias-URI> element into the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body with the requested functional alias URI used to identify the MCPTT clients for which location information is being requested.
6) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Request> element identified with the <RequestId> attribute contained in the <location-info> root element;
NOTE: The value of the <RequestId> attribute is returned in the corresponding <ReportId> attribute in order to correlate the request and the reports.
7) may include the "refresh" attribute set to "true" in the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body;
8) may include a <LocationFilter> element of the <anyExt> element of "location‑info" together with the <Request> element in the application/vnd.3gpp.mcptt-location-info+xml MIME body, with the sub-elements of the <LocationFilter> element of the <anyExt> element of "location‑info" set as follows:
i) the sub-element <AreaIdentifier> set to the TriggerId associated to the specific geographical area; and
ii) the <AreaIn> sub-element set to "true", for restricting the request to the requested MCPTT user being inside the geographical area, or to "false", for restricting the request to the requested MCPTT user being outside the geographical area; and
9) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.4 Location information report | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.4.1 Report triggering | If a location reporting trigger fires the MCPTT client checks if the minimumReportInterval timer is running. If the timer is running the MCPTT client waits until the timer expires. When the minimumReportInterval timer fires, the MCPTT client:
1) shall, if any of the reporting triggers are still true, send a location information report as specified in clause 13.3.4.2.
If the MCPTT client receives a location information request as specified in clause 13.3.3, the MCPTT client shall send a location report as specified in clause 13.3.4.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 13.3.4.2 Sending location information report | If the MCPTT client needs to send a SIP request for other reasons (e.g. a SIP MESSAGE request containing an MBMS listening report as described in clause 14), the MCPTT client:
1) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element the MCPTT client shall include:
a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request;
b) <TriggerId> child elements, where each element is set to the value of the <Trigger-Id> attribute associated with the trigger that have fired; and
c) the location reporting elements corresponding to the triggers that have fired;
2) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer; and
3) shall reset all triggers.
If the MCPTT client does not need to send a SIP request for other reasons, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The MCPTT client;
1) shall include in the Request-URI, the SIP URI received in the P-Asserted-Identity header field in the received SIP MESSAGE request for location report configuration;
2) shall include a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml";
3) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element include:
a) a <Report> element and if the Report was triggered by a location request include the <ReportID> attribute set to the value of the <RequestID> attribute in the received Request;
b) a <TriggerId> child element set to the value of each <Trigger-Id> value of the triggers that have fired; and
c) the location reporting elements corresponding to the triggers that have fired;
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.mcptt along with parameters "require" and "explicit" in accordance with IETF RFC 3841 [6];
5) shall set the minimumReportInterval timer to the minimumReportInterval time and start the timer;
6) shall reset all triggers; and
7) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14 MBMS transmission usage procedure | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.1 General | This clause describes the participating MCPTT function and the MCPTT client procedure for:
1) MBMS bearer announcements;
2) MBMS bearer listening status; and
3) MBMS bearer suspension status. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2 Participating MCPTT function MBMS usage procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.1 General | This clause describes the procedures in the participating MCPTT function for:
1) sending an MBMS bearer announcements to the MCPTT client;
2) receiving an MBMS bearer listening status from the MCPTT client; and
3) receiving an MBMS bearer suspension status from the MCPTT client. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2 Sending MBMS bearer announcement procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2.1 General | The availability of a MBMS bearer is announced to MCPTT clients by means of an MBMS bearer announcement message. One or more MBMS bearer announcement elements are included in an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body.
An MBMS bearer announcement message can contain new MBMS bearer announcements, updated MBMS bearer announcements or cancelled MBMS bearer announcements or a mix of all of them at the same time in an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body. Each initial MBMS bearer announcement message announces one MBMS bearer intended to carry a general purpose MBMS subchannel used for application level multicast signalling in a specified MBMS service area and additionally, the message could also announce zero or more extra MBMS bearers intended to carry media and media control.
NOTE: A new MBMS bearer announcement does not implicitly remove previously sent MBMS bearer announcements if the previously sent MBMS bearer announcement is not included in an MBMS bearer announcement message. However, the application/sdp MIME body, if included in the new MBMS bearer announcement message, fully replaces the existing application/sdp MIME body (which includes the MSCCK security key used to protect the general purpose MBMS subchannel).
When and to whom the participating MCPTT function sends the MBMS bearer announcement is based on local policy in the participating MCPTT function.
The following clauses describe how the participating MCPTT function:
1. sends an initial MBMS bearer announcement message;
2. updates a previously sent announcement of MBMS bearer(s);
3. cancels a previously sent announcement of MBMS bearer(s); and
4. keys, re-keys or un-keys MCPTT groups using Multicast Signalling Key (MuSiK) via a key download procedure.
Prior to the participating MCPTT function transmitting on an MBMS bearer, the participating MCPTT function:
1. if necessary, shall instruct the local key management client to request keying material from the key management server as described in 3GPP TS 33.180 [78];
2. shall generate MSCCK(s) with the corresponding MSCCK-ID(s) and MuSiK(s) with the corresponding MuSiK‑ID(s) as necessary; and
3. shall distribute MSCCKs, MSCCK-IDs, MuSiKs and MuSiK-IDs to the MCPTT clients, as needed, using the keying material received from the key management server for security protection, as described in 3GPP TS 33.180 [78]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2.2 Sending an initial MBMS bearer announcement procedure | For each MCPTT client that the participating MCPTT function is sending an MBMS bearer announcement to, the participating MCPTT function:
1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
5) shall include one application/sdp MIME body conforming to 3GPP TS 24.229 [4], where the application/sdp MIME body:
a) shall include the Content-Disposition header field with the value "render";
b) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio and media control. Additionally, the participating MCPTT function:
i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6;
ii) shall set port number of the media line to 9;
ii) shall include the "a=rtcp-mux" attribute as specified in IETF RFC 5761 [39]; and
iii) shall include the "a=rtcp:9" as specified in IETF RFC 5761 [39].
c) should include one or more "m=audio" media lines and media line attributes as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for audio only. Additionally, the participating MCPTT function:
i) shall set the c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and
ii) shall set the port number of the media line to 9;
NOTE 1: If an MBMS subchannel for audio only is included, the "a=rtcp-mux" and "a=rtcp:" attributes are not included in the media line.
d) shall include one "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the general purpose MBMS subchannel. The media line shall include a valid multicast IP address and a valid port number. If the protection of MBMS subchannel control messages sent over the general purpose MBMS subchannel of the MBMS bearer is required, the participating MCPTT function also includes an "a=key-mgmt" media-level attribute. The participating MCPTT function:
i) shall encrypt the MSCCK to a UID associated to the targeted MCPTT ID and a time related parameter as described in 3GPP TS 33.180 [78];
ii) shall generate a MIKEY-SAKKE I_MESSAGE using the encapsulated MSCCK and MSCCK-ID as specified in 3GPP TS 33.180 [78];
iii) shall add the public service identity of the participating MCPTT function to the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78];
iv) shall sign the MIKEY-SAKKE I_MESSAGE using the public service identity of the participating MCPTT function 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
v) shall include the "mikey" key management and protocol identifier and the signed MIKEY-SAKKE I_MESSAGE in the value of the a=key-mgmt" media-level attribute according to IETF RFC 4567 [47]; and
NOTE 2: The media parameters to be used by the MBMS subchannel for media is included in the Map Group To Bearer message defined in 3GPP TS 24.380 [5] and not included in this application/sdp MIME body.
e) if "m=audio" media lines to be used in an MBMS subchannel for audio only are included above, shall include one or more "m=application" media line as defined in 3GPP TS 24.380 [5] to be used as the MBMS subchannel for floor control messages. The media line:
i) shall set c-line to the unspecified address (0.0.0.0), if IPv4, or to a domain name within the ".invalid" DNS top-level domain, if IPv6; and
ii) shall set the port number of the media line to 9;
NOTE 3: The use of a separate MBMS subchannel for floor control is optional. When a separate MBMS subchannel for floor control is not used, floor control messages are sent in the MBMS subchannel for media.
NOTE 4: The port number 9 used in this clause indicates that the final address and port has not yet been determined. The final address and port information will be sent in the Map Group To Bearer message and MapGroupToSessionStream message.
6) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1" and one or more <announcement> elements associated with the pre-activated MBMS bearers. Each set of an <announcement> element:
a) shall include a TMGI value in the <TMGI> element;
NOTE 5: The same TMGI value can only appear in one <announcement> element. The TMGI value is also used to identify the <announcement> when updating or cancelling the <announcement> element.
NOTE 6: The security key active for the general purpose MBMS subchannel on which the mapping (i.e. the Map Group To Bearer message) of media or media control to this MBMS bearer was indicated, is used for MBMS subchannels on this MBMS bearer, unless a different key or an indication of not using encryption is in place.
b) shall include the QCI value in the <QCI> element;
c) if multiple carriers are supported, shall include the frequency to be used in the <frequency> element;
NOTE 7: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast.
d) shall include one or more MBMS service area IDs in <mbms-service-area-id> elements in the <mbms-service-areas> element;
NOTE 8: Initial mappings of groups to MBMS subchannels on an MBMS bearer for the purpose of carrying media or media control can occur only where the MBMS service area for this bearer and the MBMS service area for the bearer carrying the general purpose MBMS subchannel on which the Map Group To Bearer message is sent intersect. However, once media or media control were successfully mapped to this bearer, the reception by the MCPTT client can continue (until Unmap Group To Bearer is received or until timeout) throughout the entire MBMS service area of this bearer.
e) may include the <report-suspension> element and set it to "true" value or the "false" value;
NOTE 9: The participating function can choose to direct some clients not to send an MBMS bearer suspension report when notified by RAN, by including the <report-suspension> element set to "false". The purpose is to prevent an avalanche of identical reports sent by clients roughly at the same time, to report the suspension of the same MBMS bearer. The way the participation function determines which clients are to send or not to send the report is outside the scope of the present document.
f) if the MBMS bearer is carrying the general purpose MBMS subchannel, shall include one <GPMS>element, giving the number of the "m=application" media line in the application/sdp MIME body generated in step 5 above to be used for the general purpose MBMS subchannel; and
g) if the packet headers are compressed with ROHC specified in RFC 5795 [80] in this MBMS bearer, the <anyExt> element in the <announcement> element in the <mcptt-mbms-usage-info> element shall include the <mcptt-mbms-rohc> element defined in clause F.2.3.
7) shall include the MBMS public service identity of the participating MCPTT function in the P-Asserted-Identity header field;
8) shall include in a MIME body with Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml", the <mcptt-request-uri> element set to the MCPTT ID of the user; and
9) shall send the SIP MESSAGE request towards the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2.3 Updating an announcement | When the participating MCPTT function wants to update a previously sent announcement, the participating MCPTT function sends an MBMS bearer announcement in an SIP MESSAGE request as specified in clause 14.2.2.2 where the participating MCPTT function in the <announcement> element to be updated:
1) shall include the same TMGI value as in the MBMS bearer announcement to be updated in the <TMGI> element;
NOTE 1: TMGI value is used to identify the <announcement> when updating or cancelling the <announcement> element and can't be changed.
2) shall include the same or an updated value of the QCI in the <QCI> element;
3) if a frequency was included in the previously sent announcement, shall include the same value in the <frequency> element;
NOTE 2: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast.
4) shall include the same list of MBMS service area IDs or an updated list of MBMS service area IDs in the <mbms-service-areas> element;
5) may include the same or an updated value in the <report-suspension> element;
6) shall include the <GPMS> element with the same value as in the initial <announcement> element; and
7) shall include the same application/sdp MIME body as included in the initial MBMS announcement. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2.4 Cancelling an MBMS bearer announcement | When the participating MCPTT function wants to cancel an MBMS bearer announcement associated with an <announcement> element, the participating MCPTT function sends an MBMS bearer announcement as specified in clause 14.2.2.2 where the participating MCPTT function in the <announcement> element to be cancelled:
1) shall include the same TMGI value as in the <announcement> element to be cancelled in the <TMGI> element;
2) shall not include an <mbms-service-areas> element;
3) if the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body only contains <announcement> elements that are to be cancelled, shall not include an <GPMS> element; and
4) if the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body only contains <announcement> elements that are to be cancelled, shall not include an application/sdp MIME body. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.2.5 Sending a MuSiK download message | For each MCPTT client that the participating MCPTT function is intending to use an MBMS bearer to transmit confidentiality protected floor control signalling (SRTCP) to the client, the participating MCPTT function shall perform a key download procedure for each Multicast Signalling Key (MuSiK). Two kinds of MuSiK download are possible: default MuSiK download and explicit MuSiK download. The default MuSiK download is used to set, reset or unset a MuSiK and its corresponding MuSiK-ID and is applicable to all groups supported by the MCPTT client, except for certain identified groups for which MuSiKs and MUSiK-IDs are assigned, reassigned or unassigned separately via explicit MuSiK download. The default MuSiK and MUSiK-ID can apply to all the MCPTT clients supported by the participating MCPTT function and can be overridden by the explicit MuSiK download which is selectively applied only to the MCPTT clients using the explicitly identified groups. A group subject to explicit MuSiK download, can be switched to the default MuSiK protection via a default MuSiK download identifying that group. The participating MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI to the URI received in the To header field in a third-party SIP REGISTER request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
4) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
5) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body defined in clause F.2 with the <version> element set to "1", and either
a) containing an <mbms-explicitMuSiK-download> element with at least one <group> element associated with the MuSiK being downloaded; or
b) containing an <mbms-defaultMuSiK-download> element with zero or more <group> elements associated with the MuSiK being downloaded;
6) if the floor control signaling for the group(s) in the specified list is to be protected using the MuSiK, shall include an application/mikey MIME body with the MIKEY message containing the encrypted MuSiK and the corresponding MuSiK-ID, constructed as described in clauses 5.8.1 and 5.2.2 of 3GPP TS 33.180 [78];
NOTE: Clause 9.2.1.3 of 3GPP TS 33.180 [78] shows an example on how to include an application/mikey MIME body in a SIP message.
7) shall send the SIP MESSAGE request towards the MCPTT client according to 3GPP TS 24.229 [4].
The participating MCPTT function shall consider the key download successful on receipt of a 200 OK message in response to the SIP MESSAGE request sent in step 7).
A participating MCPTT function that does not receive a 200 OK message from a specific MCPTT client shall use unicast signalling for floor control towards that MCPTT client for the groups for which the MuSiK was intended. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.3 Receiving an MBMS bearer listening status from an MCPTT client | Upon receiving a "SIP MESSAGE request for an MBMS listening status update", the participating MCPTT function shall handle the request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33].
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with an <mbms-listening-status> element; and
2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function;
then the participating MCPTT function:
1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case:
a) if the <mbms-listening-status> element is set to "listening":
i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the session identified by the <session-id> element is now listening to the MBMS subchannel; and
ii) if <general-purpose> element is included with the value "true", shall indicate to the media plane that the MCPTT client is now listening to the general purpose MBMS subchannel; and
NOTE 1: The <mbms-listening-status> element can contain an <anyExt> element containing an <mbms-reception-quality> element. The use of this element is implementation specific.
b) if the <mbms-listening-status> element is set to "not-listening":
i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the sessions identified by the <session-id> elements is not listening to the MBMS subchannel;
ii) if <general-purpose> element is included with the value "false", shall indicate to the media plane that the MCPTT client is no longer listening to the general purpose MBMS bearer; and
iii) shall interact with the media plane as specified in 3GPP TS 24.380 [5].
NOTE 2: If the MCPTT client reports that the MCPTT client is no longer listening to the general purpose MBMS subchannel it is implicitly understood that the MCPTT client no longer listens to any MBMS subchannel in ongoing conversations that the MCPTT client previously reported status "listening".
NOTE 3: The <mbms-listening-status> element can contain an <anyExt> element containing an <mbms-reception-quality> element. The use of this element is implementation specific.
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with an <mbms-suspension-status> element; and
2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function;
then the participating MCPTT function:
1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case:
a) if the <mbms-suspension-status> element is set to "suspending":
i) shall consider that the bearer identified by the <suspended-TMGI> element is about to be suspended and that the reduction or elimination of traffic on that bearer and/or on some of the bearers indicated in the <other-TMGI> elements can potentially avoid the suspension; and
NOTE 4: An MBMS bearer is about to be suspended when RAN has notified the clients of the decision to suspend the bearer, but the actual suspension, which would occur at the end of the MCCH modification period, has not taken place yet because the MCCH modification period has not yet expired.
ii) may take implementation/configuration specific immediate action for the MCPTT client that reports the suspension as well as other MCPTT clients that listen to the same bearer (e.g. moving traffic to unicast bearer(s)), reducing transmission rate, eliminating traffic, modifying pre-emption priority); or
b) if the <mbms-suspension-status> element is set to "not-suspending":
i) shall consider that the bearer identified by the <suspended-TMGI> element is no longer about to be suspended; and
NOTE 5: An MBMS bearer is no longer about to be suspended when RAN has notified the clients of the decision to no longer suspend the bearer after having previously notified the clients that the bearer would be suspended at the end of the MCCH modification period. The RAN notifications to first suspend and subsequently not to suspend the same MBMS bearer would have to come within the same MCCH modification period.
ii) may take implementation/configuration specific immediate action for the MCPTT client that reports the suspension as well as other MCPTT clients that listen to the same bearer (e.g. restoring traffic previously reduced or eliminated from MBMS bearers upon reception of suspension information).
NOTE 6: If the MCPTT client reports that the MCPTT client is no longer listening to MBMS subchannels associated with the MBMS bearer indicated in the suspension information, it is implicitly understood that the suspension of that MBMS bearer has actually occurred. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.2.4 Abnormal cases | Upon receipt of a SIP MESSAGE request with an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
1) where the P-Asserted-Identity identifies a public user identity not associated with MCPTT user served by the participating MCPTT function; or
2) with an application/vnd.3gpp.mcptt-info+xml MIME body and with a <mcptt-request-uri> element containing an MCPTT ID that identifies an MCPTT user served by the participating MCPTT function and an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body containing one or more <announcement> elements;
then the participating MCPTT function shall send a SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3 MCPTT client MBMS usage procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.1 General | This clause describes the procedures in the MCPTT client for:
1) receiving an MBMS bearer announcement from the participating MCPTT function;
2) sending an MBMS bearer listening status report to the participating MCPTT function; and
3) sending an MBMS bearer suspension status report to the participating MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.2 Receiving an MBMS bearer announcement | The MCPTT client associates each received application/sdp MIME body and each received security key with a general purpose MBMS subchannel announced in the same MBMS Bearer Announcement message. When receiving a Map Group To Bearer message, the MCPTT client interprets its content (e.g. the m= line number) in the context of the application/sdp MIME body associated with the general purpose MBMS subchannel on which the Map Group To Bearer was received.
When the MCPTT client receives a SIP MESSAGE request containing:
1) a P-Asserted-Service header field containing the "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
2) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body containing one or more an <announcement> element(s);
then the MCPTT client for each <announcement> element in the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
1) if the <mbms-service-areas> element is present:
a) if an <announcement> element with the same value of the <TMGI> element is already stored:
i) shall replace the old <announcement> element with the <announcement> element received in the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body;
b) if there is no <announcement> element with the same value of the <TMGI> element stored:
i) shall store the received <announcement> element;
c) shall associate the received announcement with the received application/sdp MIME body;
d) shall associate the received announcement with the received <GPMS> element;
e) shall store the MBMS public service identity of the participating MCPTT function received in the P-Asserted-Identity header field and associate the MBMS public service identity with the new <announcement> element;
f) if a "a=key-mgmt" media-level attribute with the "mikey" key management and protocol identifier and a MIKEY-SAKKE I_MESSAGE is included for the general purpose MBMS subchannel defined in the "m=application" media line in the application/sdp MIME body in the received SIP MESSAGE request,
i) shall extract the initiator URI from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]. If the initiator URI deviates from the public service identity of the participating MCPTT function serving the MCPTT user, shall reject the SIP MESSAGE request with a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and include warning text set to "136 authentication of the MIKEY-SAKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
ii) shall convert the initiator URI to a UID as described in 3GPP TS 33.180 [78];
iii) shall use the UID to validate the signature of the MIKEY-SAKKE I_MESSAGE as described in 3GPP TS 33.180 [78];
iv) if authentication verification of the MIKEY-SAKKE I_MESSAGE fails, shall reject the SIP MESSAGE request with a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and include warning text set to "136 authentication of the MIKEY-SAKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
v) shall extract and decrypt the encapsulated MSCCK using the participating MCPTT function's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78]; and
vi) shall extract the MSCCK-ID, from the payload as specified in 3GPP TS 33.180 [78];
NOTE: With the MSCCK successfully shared between the participating MCPTT function and the served UEs, the participating MCPTT function is able to securely send MBMS subchannel control messages to the MCPTT clients.
g) shall listen to the general purpose MBMS subchannel defined in the "m=application" media line in the application/sdp MIME body in the received SIP MESSAGE request when entering an MBMS service area where the announced MBMS bearer is available; and
h) shall check the condition for sending a listening status report as specified in the clause 14.3.3; and
2) if no <mbms-service-areas> element is present:
a) shall discard a previously stored <announcement> element identified by the value of the <TMGI>;
b) shall remove the association with the stored application/sdp MIME body and stop listening to the general purpose MBMS subchannel;
c) if no more <announcement> elements associated with the stored application/sdp MIME body are stored in the MCPTT client, shall remove the stored application/sdp MIME body; and
d) check the condition for sending a listening status report as specified in the clause 14.3.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.3 The MBMS bearer listening status and suspension report procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.3.1 Conditions for sending an MBMS listening status report | If one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives a Map Group To Bearer message over the general purpose MBMS channel;
b) participates in a group session identified by the Map Group To Bearer message; and
c) the status "listening" is not already reported; or
2) if the MCPTT client:
a) receives an announcement as described in clause 14.3.2;
b) enters an MBMS service area where a general purpose MBMS is available; and
c) experiences good MBMS bearer radio condition;
then the MCPTT client shall report that the MCPTT client is listening to the MBMS bearer as specified in clause 14.3.3.2.
If one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives an MBMS bearer announcement as described in the clause 14.3.2;
b) the MBMS bearer announcement contains a cancellation of an <announcement> element identified by the same TGMI value as received in a Map Group To Bearer message in an ongoing conversation; and
c) the status "not-listening" is not already reported;
2) if the MCPTT client:
a) receives an MBMS bearer announcement as described in the clause 14.3.2;
b) the MBMS bearer announcement contains a cancellation of an <announcement> element;
c) does not participate in an ongoing conversation;
d) the MCPTT client has reported the "listening" status due to the availability of the general purpose MBMS subchannel in the <announcement> element; and
e) the status "not-listening" is not already reported; or
3. if the MCPTT client:
a) suffers from bad MBMS bearer radio condition,
then the MCPTT client shall report that the MCPTT client is not listening to the MBMS subchannels as specified in clause 14.3.3.2.
If all the following conditions are fulfilled:
1) the MCPTT client has reported "listening" as the most recent listening status relative to an MBMS bearer;
2) the MCPTT client is notified that the MBMS bearer is about to be suspended by the RAN; and
3) the MCPTT client has not received a MBMS bearer announcement containing a <report-suspension> element set to "false",
then the MCPTT client shall report that the MBMS bearer is about to be suspended, as specified in clause 14.3.3.2.
If all the following conditions are fulfilled:
1) the MCPTT client has reported "listening" as the most recent listening status relative to an MBMS bearer;
2) the MCPTT client has reported that the MBMS bearer is about to be suspended, but the suspension of the bearer has not been detected yet by the MCPTT client;
3) the MCPTT client is notified that the MBMS bearer is no longer to be suspended by the RAN; and
4) the MCPTT client has not received a MBMS bearer announcement containing a <report-suspension> element set to "false",
then the MCPTT client shall report that the MBMS bearer is no longer to be suspended, as specified in clause 14.3.3.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.3.2 Sending the MBMS bearer listening or suspension status report | When the MCPTT client wants to report the MBMS bearer listening status, the MCPTT client:
NOTE 1: The application/vnd.3gpp.mcptt-mbms-usage-info+xml can contain both the listening status "listening" and "not listening" at the same time.
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and
a) shall include in the Request-URI the MBMS public service identity of the participating MCPTT function received in the P-Asserted-Identity header field of the announcement message;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
c) should include a public user identity in the P-Preferred-Identity header field as specified in 3GPP TS 24.229 [4];
d) shall include a P-Preferred-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
e) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with the <version> element set to "1";
f) if the MCPTT client is listening to the MBMS bearer, the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
i) shall include an <mbms-listening-status> element set to "listening";
ii) if the intention is to report that the MCPTT client is listening to the MBMS subchannel for an ongoing conversation in a session (e.g. as the response to the Map Group To Bearer message), shall include the MCPTT session identity of the ongoing conversation in a <session-id> element;
iii) shall include one or more <TGMI> elements for which the listening status applies;
iv) if the intention is to report that the MCPTT client is listening to the general purpose MBMS subchannel, shall include the <general-purpose> element set to "true"; and
v) may include an anyExt element containing:
A) an <mbms-reception-quality> element indicating the received satisfactory quality level;
g) if the MCPTT client is not listening, the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
i) shall include an <mbms-listening-status> element set to "not-listening";
iii) shall include one or more <TGMI> elements for which the listening status applies;
iii) if the intention is to report that the MCPTT client is no longer listening to the MBMS subchannel in an ongoing session (e.g. as the response to Unmap Group to Bearer message), shall include the MCPTT session identity in a <session-id> element;
iv) if the intention is to report that the MCPTT client is no longer listening to general purpose MBMS subchannel, shall include the <general-purpose> element set to "false"; and
v) may include an anyExt element containing:
A) an <mbms-reception-quality> element indicating the received not satisfactory quality level; andNOTE 2: If the MCPTT client reports that the MCPTT client is no longer listening to the general purpose MBMS subchannel, it is implicitly understood that the MCPTT client no longer listens to any MBMS subchannel in ongoing conversations that the MCPTT client previously reported status "listening".
h) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> set to the MCPTT ID; and
2) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4].
When the MCPTT client meets all the conditions specified in clause 14.3.3.1 for reporting a change in an MBMS bearer suspension status, the MCPTT client:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and
a) shall include in the Request-URI the MBMS public service identity of the participating MCPTT function received in the P-Asserted-Identity header field of the announcement message;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
c) should include a public user identity in the P-Preferred-Identity header field as specified in 3GPP TS 24.229 [4];
d) shall include a P-Preferred-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
e) shall include an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with the <version> element set to "1";
f) if at least one MBMS bearer is about to be suspended, the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
i) shall include an <mbms-suspension-status> element set to "suspending";
ii) shall set the <number-of-reported-bearers> element to the total number of the included <suspended-TMGI> elements and <other-TMGI> elements;
iii) shall include <suspended-TMGI> element(s) set to the TMGI value for each of the MTCHs on the same MCH corresponding to the MBMS bearers about to be suspended; and
iv) may include <other-TMGI> elements, if available, corresponding to the TMGI values for other MTCHs on the same MCH as the MBMS bearers to be suspended;
NOTE 3: To report the suspension of MTCHs on different MCHs, the MCPTT client sends a separate message for each of the involved MCHs.
g) if the MBMS bearer is no longer about to be suspended, the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
i) shall include an <mbms-suspension-status> element set to "not-suspending";
ii) shall set the <number-of-reported-bearers> element to the number of included <suspended-TMGI> elements; and
iii) shall include a <suspended-TMGI> element set to the corresponding TMGI value for each of the MTCHs of the MBMS bearers that are no longer about to be suspended; and
h) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> set to the MCPTT ID; and
2) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4].
NOTE 4: The MCPTT client reports in separate messages the MBMS bearers that are about to be suspended and the MBMS bearers that are no longer about to be suspended. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 14.3.4 Receiving a MuSiK download message | When the MCPTT client receives a SIP MESSAGE request containing:
1) a P-Asserted-Service header field containing the "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
2) with one of the following:
a) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body containing an <mbms-explicitMuSiK-download> element with at least one <group> subelement; or
b) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body containing an <mbms-defaultMuSiK-download> element with zero or more <group> subelements;
the MCPTT client shall:
1) if the received message contains an <mbms-explicitMuSiK-download> element, set the impacted groups to be those groups identified by the <group> subelements;
2) if the received message contains an <mbms-defaultMuSiK-download> element without <group> subelements, set the impacted groups to be all groups not associated with currently valid explicit MuSiK downloads; and
3) if the received message contains an <mbms-defaultMuSiK-download> element with <group> subelements, first dissociate those groups identified by the <group> subelements from currently valid associations with explicit MuSiK downloads and then set the impacted groups to be all groups not associated with currently valid explicit MuSiK downloads.
If the key identifier within the CSB-ID of the MIKEY payload is a MuSiK-ID (4 most-significant bits have the value '6'), the MCPTT client:
1) shall process the MIKEY payload according to 3GPP TS 33.180 [78], as follows:
a) if the initiator field (IDRi) has type 'URI' (identity hiding is not used), the client:
i) shall extract the initiator URI from the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]. If the initiator URI deviates from the public service identity of the participating MCPTT function serving the MCPTT client, shall reject the SIP MESSAGE request by sending a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and including warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps; and
ii) shall convert the initiator URI to a UID as described in 3GPP TS 33.180 [78];
b) otherwise, if the initiator field (IDRi) has type 'UID' (identity hiding in use), the client:
i) shall convert the public service identity of participating MCPTT function serving the MCPTT user to a UID as described in 3GPP TS 33.180 [78]; and
ii) shall compare the generated UID with the UID in the initiator field (IDRi) of the I_MESSAGE as described in 3GPP TS 33.180 [78]. If the two initiator UIDs deviate from each other, shall reject the SIP MESSAGE request by sending a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and including warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
c) otherwise, shall reject the SIP MESSAGE request by sending a SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and including warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps;
d) shall use the UID to validate the signature of the I_MESSAGE as described in 3GPP TS 33.180 [78];
e) if authentication verification of the I_MESSAGE fails or the I_MESSAGE does not contain a Status attribute, shall reject the SIP MESSAGE request by sending SIP 488 (Not Acceptable Here) response as specified in IETF RFC 4567 [47], and including warning text set to "136 authentication of the MIKEY-SAKKE I_MESSAGE failed" in a Warning header field as specified in clause 4.4 and shall not continue with the rest of the steps; and
f) shall examine the Status attribute and shall either mark the associated security functions as "not in use" or shall extract and store the encapsulated MuSiK and the corresponding MuSiK-ID from the payload as specified in 3GPP TS 33.180 [78]; and
2) for each of the impacted groups, shall either associate the status 'security not in use' or shall add/replace in the storage associated with the group the MuSiK‑ID and the MuSiK, for use (decrypted) as security key for floor control.
NOTE: It is expected that the MCPTT client is capable of storing a different MuSiK for each MCPTT group of interest.
The MCPTT client shall respond with SIP 200 OK only if it finds the message syntactically correct and recognizes it as a valid and error-free MuSiK download (default or explicit) message.
14A MCPTT Service Continuity
14A.1 General
This clause describes the procedures for service continuity of an ongoing SIP session supporting an MCPTT private call or MCPTT group call when:
- the MCPTT UE (referred to as the remote UE) is connected to the network via E-UTRAN and decides to connect to a UE-to-network relay, e.g. because it realises that it is losing connection to the network and wants to ensure seamless service; and
- the remote UE is connected to the network via the UE-to-network-relay and decides to disconnect from the UE-to-network relay, e.g. because the remote UE realises that it is losing connection to UE-to-network relay or because the LTE-Uu link quality goes above a certain threshold, and decides to connect to the network via E-UTRAN for seamless service.
MCPTT service continuity follows the principles of 3GPP TS 24.237 [58] for PS-PS service continuity. In particular:
1) the SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) before and after the handover. This requires that initial filter criteria is configured to ensure that the SCC AS is in the registration path, is the first application server in the path of an originating session, and the last AS in the path of a terminating session;
2) the remote UE is an SC UE that supports PS-PS access transfer as per 3GPP TS 24.237 [58]; and
3) the remote UE is either configured with a static PS to PS STI as specified in 3GPP TS 24.216 [66] that it uses when initiating the session transfer request, or it uses a dynamic PS to PS STI which is the URI contained in the Contact header field returned at the creation of the dialog over the Source Access Leg, as specified in 3GPP TS 24.237 [58].
14A.2 Service continuity from on-network MCPTT service to UE-to-network relay MCPTT service
14A.2.1 Remote UE
When performing service continuity from on-network MCPTT service to UE-to-network relay MCPTT service, the remote UE:
1) shall perform ProSe UE-to-network relay discovery over PC5 as specified in clause 10A of 3GPP TS 24.334 [28];
NOTE 1: Depending on the model (A or B) used for discovery as specified in 3GPP TS 24.334 [28], the remote UE can perform UE-to-network relay discovery while still in coverage (when model A is used), or while still in coverage if the LTE-Uu link quality drops below a certain threshold (when model B is used).
NOTE 2: As part of the discovery process, service authorisation is performed as specified in 3GPP TS 24.334 [28]. The UE-to-network relay is provisioned with relay service code(s) associated with allowed MCPTT group(s) as specified in 3GPP TS 24.483 [45] and 3GPP TS 24.484 [50]. To find a permitted UE-to-network relay for group communications, a remote UE is provisioned with the relay service code(s) associated with the MCPTT group(s) which the MCPTT user is part of, in the MCPTT group configuration MO as specified in 3GPP TS 24.483 [45].
2) shall select a suitable UE-to-network relay by performing the UE-to-network relay selection procedure specified in clause 10A.2.12 of 3GPP TS 24.334 [28];
3) shall establish a direct link to the relay as specified in clause 10.4.2 of 3GPP TS 24.334 [28];
NOTE 3: As part of this process the remote UE is assigned a /64 IPv6 Prefix by the relay.
4) shall initiate IMS registration over the UE-to-network relay target access leg by following the procedures in clause 10.2.0 of 3GPP TS 24.237 [58];
NOTE 4: As part of this process the remote UE needs to discover the P-CSCF address to connect to via the UE-to-network relay. The remote UE either uses mechanism I or mechanism III of clause 9.2.1 in 3GPP TS 24.229 [4] to discover the P-CSCF address. The details of how mechanism I or mechanism III are used to discover the P-CSCF address are not covered by the present document.
5) shall initiate session transfer by following the procedures specified in clause 10.2.1 of 3GPP TS 24.237 [58];
6) after successful session transfer if MCPTT content is being distributed on the target side using MBMS bearers, shall send a MBMS bearer listening status report procedure to the participating MCPTT function by performing the procedures in clause 14.3.3; and
NOTE 5: Upon receiving the MBMS bearer listening status from an MCPTT client indicating that the MCPTT UE is now listening to a MBMS subchannel, the participating MCPTT function performs the procedures in clause 14.2.3 to switch to MBMS bearer.
7) after successful session transfer if the remote UE still has an connection in the source access, may perform IMS de-registration of the contact address of the IMS public user identity registered on the source access leg by following the procedures in 3GPP TS 24.229 [4];
14A.2.2 SCC AS
The SCC AS follows the procedures in clause 10.3.2 of 3GPP TS 24.237 [58].
14A.3 Service continuity from UE-to-network relay MCPTT service to on-network MCPTT service
14A.3.1 Remote UE
When performing access transfer between UE-to-network relay MCPTT service and on-network MCPTT service, the remote UE:
1) shall initiate IMS registration over the on-network target access leg by following the procedures in clause 10.2.0 of 3GPP TS 24.237 [58]; and
NOTE: The remote UE uses option II procedures for P-CSCF discovery as defined in clause L.2.2.1 of 3GPP TS 24.229 [4] to discover the P-CSCF address when connecting to EPC.
2) follows the procedures in steps 5), 6) and 7) of clause 14A.2.1.
14A.3.2 SCC AS
The SCC AS follows the procedures in clause 14A.2.2.
14B 5G MBS transmission usage procedure
14B.1 General
This clause describes the participating MCPTT function and the MCPTT client procedure for:
1) MBS session announcement;
2) UE session join notification;
3) MBS session listening status; and
4) MBS session de-announcement.
14B.2 Participating MCPTT function MBS usage procedures
14B.2.1 General
This clause describes the procedures in the participating MCPTT function for:
1) sending an MBS session announcement to the MCPTT client;
2) receiving a UE session join notification from the MCPTT client;
3) receiving an MBS session listening status from the MCPTT client; and
4) receiving an MBS session de-announcement acknowledgement from the MCPTT client.
14B.2.2 Sending MBS session announcement procedures
14B.2.2.1 General
The participating MCPTT function follows the procedure in clause 14.2.2.1 with the terminology mapping specified in clause L.3.4.
14B.2.2.2 Sending an initial MBS session announcement procedure
Shall generate a SIP MESSAGE request as specified in clause 14.2.2.2 with the following clarifications/exceptions.
All steps of clause 14.2.2.2 apply also for MBS except step 6), with the clarification that terminology mapping specified in clause L.3.4 applies.
In place of step 6) of clause 14.2.2.2, the following step 6) shall be used:
6) shall include an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body defined in clause F.2A with the <version> element set to "1" and one or more <announcement> elements associated with the pre-activated MBS sessions. Each set of an <announcement> element:
a) in case of the MCPTT server is able to provide the MC services to the client over 5G MBS sessions (either broadcast or multicast), shall include <mbs-session-infoType> providing the MBS session related information:
i) shall include an MBS session ID value in the <mbs-session-id> element;
NOTE 1: The identity of the MBS session used to deliver MC service group communication data. It is either TMGI for broadcast MBS and multicast MBS sessions, or source specific IP multicast address for multicast MBS session.
ii) shall include the <mbs-session-mode> element and set it to "multicast" value or the "broadcast" value;
iii) shall include a MC service group ID value in the <mc-service-group-id> element;
iv) if the MBS sessions is carrying the general purpose MBS subchannel, shall include one <GPMS>element, giving the number of the "m=application" media line in the application/sdp MIME body generated in above to be used for the general purpose MBS subchannel;
v) may include one or more MBS service area IDs in <mbs-service-area-id> elements in the <mbs-service-areas> element;
vi) for multicast MBS session, may include the <report-ue-session-join-notification> element and set it to "true" value or the "false" value;
vii) may include <multicast-mbs-session-related-info>, additional information to be used by the MC service client to join the multicast MBS session such as PLMN ID of the default PLMN service provider in case of source specific IP multicast address, DNN, and SNSSAI of the PDU session associated with the multicast MBS session;
NOTE 2: Such information may be pre-configured in the MC service UE, or provided in any other implementation specific way.
viii) for broadcast MBS session, shall include an MBS Frequency Selection Area ID value in the <mbs-fsa-id> element;
ix) if multiple carriers are supported, shall include the frequency to be used in the <frequency> element; and
NOTE 3: In the current release if the <frequency> element is included, the frequency in the <frequency> element is the same as the frequency used for unicast.
x) may include the <mbs-session-de-announcement-acknowledgement> element and set it to "true" value or the "false" value;
b) in case of LTE eMBMS and 5G MBS co-existence, shall include <eMBMS-bearer-infoType> providing the 4G eMBMS bearer related information:
i) may include a list of additional alternative TMGI which may be used in roaming scenarios in the <Alternative-TMGI> element; and
ii) the remaining elements are generated as specified in step 6) of clause 14.2.2.2.
14B.2.2.3 Updating an MBS session announcement
When the participating MCPTT function wants to update a previously sent announcement, the participating MCPTT function sends an MBS session announcement in a SIP MESSAGE request as specified in clause 14B.2.2.2 where the participating MCPTT function in the <announcement> element to be updated:
1) <mbs-session-infoType> to be updated as specified in clause 14.2.2.3 with the terminology mapping specified in clause L.3.4; and
2) <eMBMS-bearer-infoType> to be updated as specified in clause 14.2.2.3.
14B.2.2.4 Cancelling an MBS session announcement
When the participating MCPTT function wants to cancel an MBS session announcement associated with an <announcement> element, the participating MCPTT function sends an MBS session announcement as specified in clause 14B.2.2.2 where the participating MCPTT function in the <announcement> element to be cancelled:
1) <mbs-session-infoType> to be cancelled as specified in clause 14.2.2.4 with the terminology mapping specified in clause L.3.4; and
2) <eMBMS-bearer-infoType> to be cancelled as specified in clause 14.2.2.4.
14B.2.2.5 Sending a MuSiK download message
The participating MCPTT function follows the procedure in clause 14.2.2.5 with the terminology mapping specified in clause L.3.4.
14B.2.3 Receiving an MBS session listening status or MBS session de-announcement acknowledgement from an MCPTT client
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body with an <mbs-listening-status> element; and
2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function;
then the participating MCPTT function follows the procedure "MBMS bearer listening status" in clause 14.2.3 with the terminology mapping specified in clause L.3.4.
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body with an <mbs-session-de-announcement-status> element; and
2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function;
then the participating MCPTT function:
1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case:
a) if the <mbs-session-de-announcement-status> element is set to "deleting":
i) shall consider that the MBS session identified by the <de-announcement-mbs-session-id> element is about to be deleted and that the reduction or elimination of traffic on that MBS session and/or on some of the MBS sessions indicated in the <other-mbs-session-id> elements can potentially avoid the deletion; and
ii) may take implementation/configuration specific immediate action for the MCPTT client that reports the deletion as well as other MCPTT clients that listen to the same MBS session(e.g. moving traffic to unicast delivery), reducing transmission rate, eliminating traffic, modifying pre-emption priority); or
b) if the <mbs-session-de-announcement-status> element is set to "not-deleting":
i) shall consider that the MBS session identified by the <de-announcement-mbs-session-id> element is no longer about to be deleted; and
ii) may take implementation/configuration specific immediate action for the MCPTT client that reports the deletion as well as other MCPTT clients that listen to the same MBS session(e.g. restoring traffic previously reduced or eliminated from MBS session upon reception of deletion information).
14B.2.4 Abnormal cases
Upon receipt of a SIP MESSAGE request with an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body, then the participating MCPTT function follows the procedure in clause 14.2.4 with the terminology mapping specified in clause L.3.4.
14B.2.5 Receiving a UE session join notification from an MCPTT client
Upon receiving a "SIP MESSAGE request for a UE session join notification", the participating MCPTT function shall handle the request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33].
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body with an <mbs-multicast-joining-status> element; and
2) an application/vnd.3gpp.mcptt-info+xml MIME body containing an MCPTT ID in the <mcptt-request-uri> served by the participating MCPTT function;
then the participating MCPTT function:
1) shall verify that the public user identity in the P-Asserted-Identity header field is bound to the MCPTT ID in the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body, and if that is the case:
a) if the <mbs-multicast-joining-status> element is set to "ue-session-join":
i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the session identified by the <session-id> element wants to receive multicast data identified by a specific MBS session ID; and
b) if the <mbs-multicast-joining-status> element is set to "ue-session-leave":
i) if a <session-id> element is included, shall indicate to the media plane that the MCPTT client in the sessions identified by the <session-id> elements no longer wants to receive multicast data identified by a specific MBS session ID;
14B.3 MCPTT client MBS usage procedures
14B.3.1 General
This clause describes the procedures in the MCPTT client for:
1) receiving an MBS session announcement from the participating MCPTT function;
2) sending a UE session join notification to the participating MCPTT function;
3) sending an MBS session listening status report to the participating MCPTT function; and
4) sending an MBS session de-announcement acknowledgement to the participating MCPTT function.
14B.3.2 Receiving an MBS session announcement
The participating MCPTT client follows the procedure in clause 14.3.2 with the terminology mapping specified in clause L.3.4.
When the MCPTT client for each <announcement> element in the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body:
1) if the <mbs-service-areas> element is present:
a) if an <announcement> element with the same value of the <mbs-session-id> element is already stored:
i) shall replace the old <announcement> element with the <announcement> element received in the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body;
b) if there is no <announcement> element with the same value of the <mbs-session-id> element stored:
i) shall store the received <announcement> element;
c) the remaining parts in step 1) of clause 14.3.2 applies also for MBS, with the clarification that terminology mapping specified in clause L.3.4 applies.
2) if no <mbs-service-areas> element is present:
a) shall discard a previously stored <announcement> element identified by the value of the <mbs-session-id>; and
b) the remaining parts in step 2) of clause 14.3.2 applies also for MBS, with the clarification that terminology mapping specified in clause L.3.4 applies;
3) for 5G MBS and 4G MBMS co-existence, the <eMBMS-bearer-infoType> is performed as specified in clause 14.3.2.
14B.3.3 The MBS session listening status and de-announcement acknowledgement procedures
14B.3.3.1 Conditions for sending an MBS listening status report or de-announcement acknowledgement
If one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives a Map Group To Session Stream message over the general purpose MBS channel;
b) participates in a group session identified by the Map Group To Session Stream message; and
c) the status "listening" is not already reported; or
2) if the MCPTT client:
a) receives an announcement as described in clause 14B.3.2;
b) for multicast MBS session, sends a UE session join notification as described in clause 14B.3.5;
c) enters an MBS service area where a specific MBS session stream is available; and
d) experiences good MBS session radio condition;
then the MCPTT client shall report that the MCPTT client is listening to the MBS session as specified in clause 14B.3.3.2.
If one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives an MBS session announcement as described in the clause 14B.3.2;
b) the MBS session announcement contains a cancellation of an <announcement> element identified by the same MBS session ID value as received in a Map Group To Session Stream message in an ongoing conversation; and
c) the status "not-listening" is not already reported;
2) if the MCPTT client:
a) receives an MBS session announcement as described in the clause 14B.3.2;
b) the MBS session announcement contains a cancellation of an <announcement> element;
c) does not participate in an ongoing conversation;
d) the MCPTT client has reported the "listening" status due to the availability of the general purpose MBS subchannel in the <announcement> element; and
e) the status "not-listening" is not already reported; or
3) if the MCPTT client:
a) suffers from bad MBS session radio condition,
then the MCPTT client shall report that the MCPTT client is not listening to the MBS session stream as specified in clause 14B.3.3.2.
If all the following conditions are fulfilled:
1) the MCPTT client has reported "listening" as the most recent listening status relative to an MBS session; and
2) the MCPTT client has not received a MBS session announcement containing a <mbs-session-de-announcement-acknowledgement> element set to "false",
then the MCPTT client shall report that the MBS session is about to be deleted, as specified in clause 14B.3.3.2.
If all the following conditions are fulfilled:
1) the MCPTT client has reported "listening" as the most recent listening status relative to an MBS session;
2) the MCPTT client has reported that the MBS session is about to be deleted, but the deletion of the MBS session has not been detected yet by the MCPTT client; and
3) the MCPTT client has not received a MBS session announcement containing a <mbs-session-de-announcement-acknowledgement> element set to "false",
then the MCPTT client shall report that the MBS session is no longer to be deleted, as specified in clause 14B.3.3.2.
14B.3.3.2 Sending the MBS session listening or MBS session de-announcement acknowledgement
When the MCPTT client wants to report the MBS session listening status, the MCPTT client shall generate a SIP MESSAGE request as specified "MBMS bearer listening status" in clause 14.3.3.2 with the terminology mapping specified in clause L.3.4 applise;
When the MCPTT client meets all the conditions specified in clause 14B.3.3.1 for reporting a change in an MBS session de-announcement status, the MCPTT client shall generate a SIP MESSAGE request as specified "MBMS bearer suspension status" in clause 14.3.3.2 with the terminology mapping specified in clause L.3.4 applise with the following clarifications/exceptions:
1) in step f) of clause 14.2.2.2 1) with the exception that if at least one MBS session is about to be deleted, the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body:
i) shall include an <mbs-session-de-announcement-status> element set to "deleting";
ii) shall set the <number-of-reported-sessions> element to the total number of the included <deleted-mbs-session-id> elements and <other-mbs-session-id> elements;
iii) shall include <deleted-mbs-session-id> element(s) set to the MBS session ID value for each of the MBS sessions about to be deleted; and
iv) may include <other-mbs-session-id> elements, if available, corresponding to the MBS session ID values for other MBS sessions to be deleted;
2) in step g) of clause 14.2.2.2 1) with the exception that if the MBS session is no longer about to be deleted, the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body:
i) shall include an <mbs-session-de-announcement-status> element set to "not-deleting";
ii) shall set the <number-of-reported-sessions> element to the number of included <deleted-mbs-session-id> elements; and
iii) shall include a <deleted-mbs-session-id> element set to the corresponding MBS session ID value for each of the MBS sessions that are no longer about to be deleted.
14B.3.4 Receiving a MuSiK download message
The MCPTT client follows the procedure in clause 14.3.4 with the terminology mapping specified in clause L.3.4.
14B.3.5 The UE session join notification
14B.3.5.1 Conditions for sending the UE session join notification
For multicast MBS sessions, if one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives a Map Group To Session Stream message over the general purpose MBS channel;
b) participates in a group session identified by the Map Group To Session Stream message; and
c) the status "ue-session-join" is not already reported; or
2) if the MCPTT client:
a) receives an announcement as described in clause 14B.3.2;
b) enters an MBS service area where a specific MBS session stream is available; and
c) experiences good MBS session radio condition;
then the MCPTT client shall report that the MCPTT client indicates to MCPTT server that such MCPTT client wants to receive multicast data identified by a specific MBS session ID, as specified in clause 14B.3.5.2.
For multicast MBS sessions, if one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives an MBS session announcement as described in the clause 14B.3.2;
b) the MBS session announcement contains a cancellation of an <announcement> element identified by the same MBS session ID value as received in a Map Group To Session Stream message in an ongoing conversation; and
c) the status "ue-session-leave" is not already reported;
2) if the MCPTT client:
a) receives an MBS session announcement as described in the clause 14B.3.2;
b) the MBS session announcement contains a cancellation of an <announcement> element;
c) does not participate in an ongoing conversation;
d) the MCPTT client has reported the "ue-session-join" status due to the availability of the general purpose MBS subchannel in the <announcement> element; and
e) the status "ue-session-leave" is not already reported; or
3) if the MCPTT client:
a) suffers from bad MBS session radio condition,
then the MCPTT client shall report that the MCPTT client no longer wants to receive multicast data identified by a specific MBS session ID, as specified in clause 14B.3.3.2.
14B.3.5.2 Sending the UE session join notification
When the MCPTT client wants to send the UE session join notification, the MCPTT client:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and
a) shall include in the Request-URI the MBS public service identity of the participating MCPTT function received in the P-Asserted-Identity header field of the announcement message;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media-feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
c) should include a public user identity in the P-Preferred-Identity header field as specified in 3GPP TS 24.229 [4];
d) shall include a P-Preferred-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
e) shall include an application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body with the <version> element set to "1";
f) if the MCPTT client is successfully joining a certain multicast MBS session procedure, the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body:
i) shall include an <mbs-multicast-joining-status> element set to "ue-session-join";
ii) if the intention is to report that the MCPTT client is joining a certain multicast MBS session procedure, shall include the MCPTT session identity of the ongoing conversation in a <session-id> element; and
iii) shall include one or more <mbs-session-id> elements for which the listening status applies;
g) if the MCPTT client is not joining a certain multicast MBS session procedure, the application/vnd.3gpp.mcptt-mbs-usage-info+xml MIME body:
i) shall include an <mbs-multicast-joining-status> element set to "ue-session-leave";
ii) if the intention is to report that the MCPTT client is not joining a certain multicast MBS session procedure, shall include the MCPTT session identity in a <session-id> element; and
iii) shall include one or more <mbs-session-id> elements for which the listening status applies;
h) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> set to the MCPTT ID; and
2) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15 Off-network message formats | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1 MONP message functional definitions and contents | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.1 General | The following clauses describe the MONP message functional definitions and contents. Each message consist of a series of information elements. Annex I describes the standard format of a MONP message and the encoding rules for each type of information element. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.2 GROUP CALL PROBE message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.2.1 Message definition | This message is sent by the UE to other UEs to check for an ongoing group call. For contents of the message see Table 15.1.2.1-1.
Message type: GROUP CALL PROBE
Direction: UE to other UEs
Table 15.1.2.1-1: GROUP CALL PROBE message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call probe message identity
Message type
15.2.2
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.3 GROUP CALL ANNOUNCEMENT message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.3.1 Message definition | This message is sent by the UE to other UEs to announce an ongoing group call to other UEs. For contents of the message see Table 15.1.3.1-1.
Message type: GROUP CALL ANNOUNCEMENT
Direction: UE to other UEs
Table 15.1.3.1-1: GROUP CALL ANNOUNCEMENT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call announcement message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Call type
Call type
15.2.11
M
V
1
Refresh interval
Refresh interval
15.2.4
M
V
2
Call start time
Call start time
15.2.14
M
V
5
Last call type change time
Last call type change time
15.2.15
M
V
5
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
SDP
SDP
15.2.6
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x
Last user to change call type
MCPTT User ID
15.2.10
M
LV-E
3-x
80
Confirm mode indication
Confirm mode indication
15.2.9
O
T
1
81
Probe response
Probe response
15.2.16
O
T
1 |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.4 GROUP CALL ACCEPT message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.4.1 Message definition | This message is sent by the UE to other UEs to indicate acceptance of a group call. For contents of the message see Table 15.1.4.1-1.
Message type: GROUP CALL ACCEPT
Direction: UE to other UEs
Table 15.1.4.1-1: GROUP CALL ACCEPT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call accept message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Call type
Call type
15.2.11
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Sending MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.5 PRIVATE CALL SETUP REQUEST message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.5.1 Message definition | This message is sent by a UE to another UE to request setup of a private call. For contents of the message see Table 15.1.5.1-1.
Message type: PRIVATE CALL SETUP REQUEST
Direction: UE to another UE
Table 15.1.5.1-1: PRIVATE CALL SETUP REQUEST message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call setup request message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Commencement mode
Commencement mode
15.2.7
M
V
1
Call type
Call type
15.2.11
M
V
1
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x
SDP offer
SDP
15.2.6
M
LV-E
3-x
78
User location
User location
15.2.12
O
TLV-E
4-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.6 PRIVATE CALL RINGING message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.6.1 Message definition | This message is automatically sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message. This message indicates that the UE has presented the incoming call notification to the user and is awaiting user response. For contents of the message see Table 15.1.6.1-1.
Message type: PRIVATE CALL RINGING
Direction: UE to another UE
Table 15.1.6.1-1: PRIVATE CALL RINGING message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call ringing message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.7 PRIVATE CALL ACCEPT message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.7.1 Message definition | This message is sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message when user accepts the call. This message indicates that the UE accepts the call setup request. For contents of the message see Table 15.1.7.1-1.
Message type: PRIVATE CALL ACCEPT
Direction: UE to another UE
Table 15.1.7.1-1: PRIVATE CALL ACCEPT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call accept message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x
SDP answer
SDP
15.2.6
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.8 PRIVATE CALL REJECT message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.8.1 Message definition | This message is sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message when user rejects the call. This message indicates that the UE rejects the call setup request. For contents of the message see Table 15.1.8.1-1.
Message type: PRIVATE CALL REJECT
Direction: UE to another UE
Table 15.1.8.1-1: PRIVATE CALL REJECT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call reject message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Reason
Reason
15.2.8
M
V
1
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.9 PRIVATE CALL RELEASE message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.9.1 Message definition | This message is sent by a UE to another UE to terminate an ongoing private call. For contents of the message see Table 15.1.9.1-1.
Message type: PRIVATE CALL RELEASE
Direction: UE to another UE
Table 15.1.9.1-1: PRIVATE CALL RELEASE message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call release message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user id
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user id
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.10 PRIVATE CALL RELEASE ACK message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.10.1 Message definition | This message is sent by a UE to another UE in response to a PRIVATE CALL RELEASE message. This message indicates that the UE has terminated the call. For contents of the message see Table 15.1.10.1-1.
Message type: PRIVATE CALL RELEASE ACK
Direction: UE to another UE
Table 15.1.10.1-1: PRIVATE CALL RELEASE ACK message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call release ack message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user id
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.11 PRIVATE CALL ACCEPT ACK message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.11.1 Message definition | This message is sent by a UE to another UE in response to a PRIVATE CALL ACCEPT message. This message acknowledges the receipt of PRIVATE CALL ACCEPT message. For contents of the message see Table 15.1.11.1-1.
Message type: PRIVATE CALL ACCEPT ACK
Direction: UE to another UE
Table 15.1.11.1-1: PRIVATE CALL ACCEPT ACK message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call accept ack message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.12 PRIVATE CALL EMERGENCY CANCEL message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.12.1 Message definition | This message is sent by a UE to another UE to indicate termination of emergency mode in private call. For contents of the message see Table 15.1.12.1-1.
Message type: PRIVATE CALL EMERGENCY CANCEL
Direction: UE to another UE
Table 15.1.12.1-1: PRIVATE CALL EMERGENCY CANCEL message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call emergency cancel message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.13 PRIVATE CALL EMERGENCY CANCEL ACK message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.13.1 Message definition | This message is sent by a UE to another UE to indicate receipt of PRIVATE CALL EMERGENCY CANCEL message. For contents of the message see Table 15.1.13.1-1.
Message type: PRIVATE CALL EMERGENCY CANCEL ACK
Direction: UE to another UE
Table 15.1.13.1-1: PRIVATE CALL EMERGENCY CANCEL ACK message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Private call emergency cancel ack message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT user ID of the caller
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT user ID of the callee
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.14 GROUP CALL IMMINENT PERIL END message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.14.1 Message definition | This message is sent by the UE to other UEs to indicate termination of imminent peril mode in the group call. For contents of the message see Table 15.1.14.1-1.
Message type: GROUP CALL IMMINENT PERIL END
Direction: UE to other UEs
Table 15.1.14.1-1: GROUP CALL IMMINENT PERIL END message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call imminent peril end message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Last call type change time
Last call type change time
15.2.16
M
V
5
Last user to change call type
MCPTT User ID
15.2.10
M
LV-E
3-x
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.15 GROUP CALL EMERGENCY END message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.15.1 Message definition | This message is sent by the UE to other UEs to indicate termination of emergency mode in the group call. For contents of the message see Table 15.1.15.1-1.
Message type: GROUP CALL EMERGENCY END
Direction: UE to other UEs
Table 15.1.15.1-1: GROUP CALL EMERGENCY END message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call emergency end message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Last call type change time
Last call type change time
15.2.16
M
V
5
Last user to change call type
MCPTT User ID
15.2.10
M
LV-E
3-x
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.16 GROUP EMERGENCY ALERT message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.16.1 Message definition | This message is sent by the UE to other UEs to indicate an emergency situation. For contents of the message see Table 15.1.16.1-1.
Message type: GROUP EMERGENCY ALERT
Direction: UE to other UEs
Table 15.1.16.1-1: GROUP EMERGENCY ALERT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group emergency alert message identity
Message type
15.2.2
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x
Organization name
Organization name
15.2.13
M
LV-E
3-x
78
User location
User location
15.2.12
O
TLV-E
4-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.17 GROUP EMERGENCY ALERT ACK message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.17.1 Message definition | This message is sent by the UE to other UEs to indicate receipt of emergency alert. For contents of the message see Table 15.1.17.1-1.
Message type: GROUP EMERGENCY ALERT ACK
Direction: UE to other UEs
Table 15.1.17.1-1: GROUP EMERGENCY ALERT ACK message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group emergency alert ack message identity
Message type
15.2.2
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x
Sending MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.18 GROUP EMERGENCY ALERT CANCEL message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.18.1 Message definition | This message is sent by the UE to other UEs to indicate end of emergency situation. For contents of the message see Table 15.1.18.1-1.
Message type: GROUP EMERGENCY ALERT CANCEL
Direction: UE to other UEs
Table 15.1.18.1-1: GROUP EMERGENCY ALERT CANCEL message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group emergency alert cancel 0message identity
Message type
15.2.2
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT User ID
15.2.10
M
LV-E
3-x
Sending MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.19 GROUP EMERGENCY ALERT CANCEL ACK message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.19.1 Message definition | This message is sent by the UE to other UEs to indicate receipt of emergency alert cancel. For contents of the message see Table 15.1.19.1-1.
Message type: GROUP EMERGENCY ALERT CANCEL ACK
Direction: UE to other UEs
Table 15.1.19.1-1: GROUP EMERGENCY ALERT CANCEL ACK message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group emergency alert cancel ack message identity
Message type
15.2.2
M
V
1
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT User ID
15.2.10
M
LV-E
3-x
Sending MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.