hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.4.2 Sending notifications to the conference event package
|
The procedures in this clause is triggered by:
1) the receipt of a SIP SUBSCRIBE request as specified in clause 10.1.3.4.1;
2) the receipt of a SIP BYE request from one of the participants in a pre-arranged, a chat, or an adhoc group session; or
3) when a new participant is added in a pre-arranged, chat, or adhoc group session.
When sending a conference event notification, the controlling MCPTT function:
1) shall generate a notification package as specified in clause 6.3.3.4 to all MCPTT clients which have subscribed to the conference event package; and
NOTE: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
2) shall send a SIP NOTIFY request to all participants which have subscribed to the conference event package as specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.4.3 Sending subscriptions to the conference event package
|
The procedure in this clause is triggered by:
1) the receipt of a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCPTT function of an MCPTT group and if at least one participant already has subscribed to the conference event package in the controlling MCPTT function as specified in clause 10.1.3.4.1; or
2) the receipt of the first SIP SUBSCRIBE request as specified in clause 10.1.3.4.1 and one or more participant in the group session is a non-controlling MCPTT function;
then, for each non-controlling MCPTT function from where a SIP 200 (OK) response to a SIP INVITE request for non-controlling MCPTT function of an MCPTT group has been received and where a SIP SUBSCRIBE request is not already sent, the controlling MCPTT function:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the public service identity of the non-controlling MCPTT function serving the group identity of the MCPTT group owned by the partner MCPTT system;
3) shall include a P-Asserted-Identity header field in the outgoing SIP SUBSCRIBE request set to the public service identity of the controlling MCPTT function;
4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9];
5) shall include an Accept-Contact header with the g.3gpp.mcptt along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
7) shall include an Accept header field containing the application/conference-info+xml MIME type;
8) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-request-uri> element set to the constituent MCPTT group ID; and
b) the <mcptt-calling-group-id> set to the temporary MCPTT group ID; and
9) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The responses to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving an incoming SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request, the controlling MCPTT function:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
2) shall modify the SIP NOTIFY request as specified in clause 6.3.3.4; and
3) shall forward the modified SIP NOTIFY request according to 3GPP TS 24.229 [4] to all other participants with a subscription to the conference event package.
NOTE: A non-controlling MCPTT function of an MCPTT group is regarded as a participant in a temporary group session.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.4.4 Terminating a subscription
|
Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" that terminates the subscription of the conference event package as specified in IETF RFC 6665 [26], the controlling MCPTT function:
1) shall send a SIP 200 (OK) response as specified in IETF RFC 6665 [26]; and
2) if there are no remaining subscriptions to the event package in the ongoing MCPTT call in a temporary group session, shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [26] in all non-controlling MCPTT functions in the temporary group session.
Upon expiry of the subscription timer and if there are no remaining subscriptions to the event package in the ongoing MCPTT call in a temporary group session, the controlling MCPTT function shall terminate the subscriptions to the conference event package as specified in IETF RFC 6665 [26] in all non-controlling MCPTT functions in the temporary group session.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.5 Non-controlling MCPTT function
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.5.1 Receiving subscriptions to the conference event package
|
Upon receipt of "SIP SUBSCRIBE request for conference event status subscription in the non-controlling MCPTT function" and the SIP SUBSCRIBE request:
1) contains an application/vnd.3gpp.mcptt-info+xml MIME body with
a) the <mcptt-request-uri> element set to the constituent MCPTT group ID; and
b) the <mcptt-calling-user-id> element is set to:
i) a participant in the group session; or
ii) the temporary MCPTT group ID;
2) contains the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
3) contains an Accept header field containing the application/conference-info+xml MIME type; and
4) is not received in a group call initiated as a broadcast group call;
then the non-controlling MCPTT function:
1) shall check if the <on-network-allow-conference-state> element in the group document in 3GPP TS 24.481 [31] of the constituent group allows the MCPTT ID in the <mcptt-calling-user-id> element to subscribe to the conference event package and if not allowed:
a) shall reject the "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" with a SIP 403 (Forbidden) response to the SIP SUBSCRIBE request, with warning text set to "138 subscription of conference events not allowed" as specified in clause 4.4; and
b) shall not continue with the remaining steps;
2) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
3) shall cache information about the subscription;
4) shall generate a notification package as specified in clause 6.3.4.3 and send a SIP NOTIFY request according to 3GPP TS 24.229 [4] to the MCPTT client which have subscribed to the conference event package; and
5) if the SIP SUBSCRIBE request is the first SIP SUBSCRIBE request from a MCPTT client, shall subscribe to the conference event package from the controlling MCPTT functions in the group session as specified in clause 10.1.3.5.3.
Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the controlling MCPTT function" in a group call initiated as a broadcast group call, the controlling MCPTT function:
1) shall generate a SIP 480 (Temporarily Unavailable) response to the SIP SUBSCRIBE request as specified in 3GPP TS 24.229 [4];
2) shall include a Warning header field with the warning text set to "105 subscription not allowed in a broadcast group call" as specified in clause 4.4; and
3) send the SIP 480 (Temporarily Unavailable) response according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.5.2 Sending notifications to the conference event package
|
The procedures in this clause is triggered by:
1) the receipt of a receipt of a SIP BYE request from one of the participants in a pre-arranged or a chat group session; or
2) when a new participant is added in a pre-arranged or chat group session.
When sending a conference event notification, the non-controlling MCPTT function:
1) shall generate a notification package as specified in clause 6.3.4.3 to all participants which have subscribed to the conference event package; and
NOTE: As a group document can potentially have a large content, the controlling MCPTT function can notify using content-indirection as defined in IETF RFC 4483 [32].
2) shall send a SIP NOTIFY request to all participants which have subscribed to the conference event package as specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.5.3 Sending a subscription to the conference event package
|
Upon receipt of the first subscription to the conference event package from an MCPTT client, the non-controlling MCPTT function:
1) shall generate a SIP SUBSCRIBE request and use a new SIP-dialog according to IETF RFC 6665 [26], IETF RFC 4575 [30] and 3GPP TS 24.229 [4];
2) shall set the Request-URI of the SIP SUBSCRIBE request to the temporary MCPTT session identity;
NOTE: The SIP URI received in the Contact header field of the SIP INVITE request for non-controlling MCPTT function of an MCPTT group is the temporary MCPTT session identity. Towards MCPTT clients the non-controlling MCPTT function uses an internal generated MCPTT session identity.
3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
4) shall include an Accept-Contact header with the media feature tag g.3gpp.icsi-ref with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
NOTE 2: 4294967295, which is equal to 232-1, is the highest value defined for Expires header field in IETF RFC 3261 [24].
6) shall include an Accept header field containing the application/conference-info+xml MIME type;
7) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with:
a) the <mcptt-request-uri> element set to the temporary MCPTT group ID: and
b) the <mcptt-calling-group-id> set to the constituent MCPTT group ID; and
8) shall send the SIP SUBSCRIBE request using a new SIP dialog according to 3GPP TS 24.229 [4].
The 2xx response to the SIP SUBSCRIBE request shall be handled according to IETF RFC 6665 [26], IETF RFC 4575 [30] and TS 24.229 [4].
Upon receiving an incoming SIP NOTIFY requests to the previously sent SIP SUBSCRIBE request the non-controlling MCPTT function:
1) shall handle the request according to IETF RFC 6665 [26] and IETF RFC 4575 [30];
2) shall store conference information based on the SIP NOTIFY request content;
3) shall modify the SIP NOTIFY request as specified in clause 6.3.4.3; and
4) forward the modified SIP NOTIFY request according to 3GPP TS 24.229 [4] to all MCPTT clients with a subscription to the conference event package.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.5.4 Terminating a subscription
|
Upon receipt of a "SIP SUBSCRIBE request for conference event status subscription in the non-controlling MCPTT function" that terminates the subscription of the conference event package as specified in IETF RFC 6665 [26], the non-controlling MCPTT function:
1) shall send a SIP 200 (OK) response as specified in IETF RFC 6665 [26]; and
2) if there are no remaining subscriptions to the event package (excluding any subscriptions to the event package made by the controlling MCPTT function), shall terminate the subscriptions to the conference event package in the controlling MCPTT function as specified in IETF RFC 6665 [26].
Upon expiry of the subscription timer and if there are no remaining subscriptions to the event package (excluding any subscriptions to the event package made by the controlling MCPTT function), the non-controlling MCPTT function shall terminate the subscriptions to the conference event package in the controlling MCPTT function as specified in IETF RFC 6665 [26].
NOTE: The subscription to the event package made by the controlling MCPTT function will be terminated by the controlling MCPTT function when the last subscription to the event package is terminated in the controlling MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.6 Coding
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.6.1 Extension of application/conference-info+xml MIME type
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.6.1.1 Introduction
|
The present clause describes an extensions of the application/conference-info+xml MIME body specified in IETF RFC 4575 [30].
The functional alias extension is used to indicate per-user functional alias association with MCPTT group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.3.6.1.2 Schema
|
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttConfInfo:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttConfInfo="urn:3gpp:ns:mcpttConfInfo:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCPTT specific child element of endpoint element -->
<xs:element name="functional-alias" type="xs:anyURI" use="optional"/>
</xs:schema>
The application/conference-info MIME body refers to namespaces using prefixes specified in table 10.1.3.6.1.2-1.
Table 10.1.3.6.1.2-1: Assignment of prefixes to namespace names in the application/pidf+xml MIME body
Prefix
Namespace
mcpttConfInfo
urn:3gpp:ns:mcpttConfInfo:1.0
NOTE: The "urn:ietf:params:xml:ns:conference-info" namespace is the default namespace so no prefix is used for it in the application/conference-info MIME body.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4 Remote change of an MCPTT user's selected group
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.1 General
|
Clause 10.1.4 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for the on-network remote change of an MCPTT user's selected group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.2 Client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.2.1 Remote selected group change initiation
|
Upon receiving a request from the MCPTT user to send a group selection change request to change the selected group of a targeted MCPTT user to a specific MCPTT group, the MCPTT client:
1) if:
a) the <RemoteGroupSelectionURIList> element does not exist in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
b) the <RemoteGroupSelectionURIList> element exists in the MCPTT user profile document and the MCPTT ID of the targeted MCPTT user does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
a) should indicate to the requesting MCPTT user that they are not authorised to change the selected MCPTT group of the targeted MCPTT user; and
b) shall skip the rest of the steps of the present clause;
1A) shall determine whether the group document associated with the specific MCPTT group contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
a) should indicate to the MCPTT user that calls are not allowed on the specific MCPTT group; and
b) shall skip the remainder of this procedure;
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-request-uri> set to the MCPTT group identity to be selected by the targeted MCPTT user; and
ii) the <request-type> element set to a value of "group-selection-change-request"; and
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the targeted MCPTT user, according to rules and procedures of IETF RFC 5366 [20];
3) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
4) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the MCPTT user the failure of the sent group selection change request and not continue with the rest of the steps.
Upon receiving a "SIP MESSAGE request for group selection change response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent group selection change request from the value of the <selected-group-change-outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
2) should indicate to the MCPTT user the success or failure of the sent group selection change request.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.2.2 Target client procedures for handling remote selected group change request
|
Upon receiving a "SIP MESSAGE request for group selection change request for terminating client", the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing an <affiliation-required> element set to a value of "true":
a) shall invoke the procedures of clause 9.2.1.2 to affiliate to the MCPTT group identified by the contents of the <mcptt-calling-group-id> included in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) if the MCPTT client has not already invoked the procedures of clause 9.2.1.3, shall invoke the procedures of clause 9.2.1.3; and
c) upon receiving a SIP NOTIFY request including a <p-id> element set to a value matching the <p-id> value included in the SIP PUBLISH request sent in step 1) a) above as specified in clause 9.2.1.3, shall determine if the affiliation procedure to the MCPTT group identified by the contents of the <mcptt-calling-group-id> in the received SIP MESSAGE request was successful;
2) if the received SIP MESSAGE request contained an application/vnd.3gpp.mcptt-info+xml MIME body containing an <affiliation-required> element set to a value of "true" and the affiliation was successful as determined in step 1) c) above, or if the <affiliation-required> element was not present in the received SIP MESSAGE request:
a) shall change the MCPTT client's selected group to the MCPTT group identified by the contents of the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall determine the success or failure of the change of selected group action;
3) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request;
e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-request-uri> set to the MCPTT group identity to be selected by the MCPTT user; and
ii) the <anyExt> element containing:
A) the <response-type> element set to a value of "group-selection-change-response";
B) if the MCPTT client was able to successfully change the selected group as determined in step 2) b) above, then a <selected-group-change-outcome> element set to a value of "success"; and
C) if the MCPTT client:
I) was required to affiliate to the MCPTT group identified by the contents of the <mcptt-calling-group-id> in the received SIP MESSAGE request and the affiliation failed as determined in step 1) c); or
II) failed to change the selected group as determined in step 2) b);
then a <selected-group-change-outcome> element set to a value of "fail";
4) should indicate to the MCPTT user the success or failure of the requested change of selected group action;
5) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user; and
6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.3 Participating MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.3.1 Originating procedures
|
Upon receiving a "SIP MESSAGE request for group-selection-change for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the "SIP MESSAGE request for group selection change for originating participating MCPTT function" contains the <request-type> element set to a value of "group-selection-change-request":
a) if:
i) the <RemoteGroupSelectionURIList> element does not exist in the MCPTT user profile document with one or more <entry> elements (see the MCPTT user profile document in 3GPP TS 24.484 [50]); or
ii) if the MCPTT ID contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received "SIP MESSAGE request for group selection change for originating participating MCPTT function" does not match with one of the <entry> elements of the <RemoteGroupSelectionURIList> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
then:
i) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "155 user not authorised to change user's selected group" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
4) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4);
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8) shall copy the contents of the application/resource-lists+xml MIME body into the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
11) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the sent SIP MESSAGE request, the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.3.2 Terminating procedures
|
Upon receiving a "SIP MESSAGE request for group-selection-change for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.4.4 Controlling MCPTT function procedures
|
Upon receiving:
- a "SIP MESSAGE request for group selection change request for controlling MCPTT function"; or
- a "SIP MESSAGE request for group selection change response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if there is a <request-type> element set to a value of "group-selection-change-request" contained in the <anyExt> element in the <mcptt-Params> element contained in the <mcpttinfo> root element contained in the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request:
a) if the MCPTT user identified by the MCPTT ID in the "uri" attribute of an <entry> element in a <list> element in the <resource-lists> element of the application/resource-lists+xml MIME body contained in the SIP MESSAGE request is not affiliated with the MCPTT group identified by the <mcptt-request-uri> in the application/vnd.3gpp. mcptt-info+xml MIME body as determined by the procedures of clause 6.3.6:
i) shall determine if the MCPTT user is eligible to be affiliated with the MCPTT group as determined by clause 9.2.2.3.8; and
ii) if the MCPTT user is not eligible for affiliation, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request with the following clarifications:
a) shall set the <mcptt-calling-group-id> to the MCPTT group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall set the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the MCPTT ID of the targeted MCPTT user contained in the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the received SIP MESSAGE request;
8) if the received SIP MESSAGE request is a "SIP MESSAGE request for group selection change request for controlling MCPTT function":
a) if the targeted MCPTT user is not affiliated to the identified MCPTT group and was determined to be eligible to be affiliated with the MCPTT group in step 3) a) i) above, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <anyExt> element an <affiliation-required> element set to a value of "true";
9) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
10) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
12) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, controlling MCPTT function shall forward the error response to the originating participating MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5 Remotely initiated group call
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.1 General
|
Clause 10.1.5 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for on-network remotely initiated group call.
In the procedures clause 10.1.5.2:
- the term "requesting MCPTT user" is used to refer to the user who sent a request to initiate a remotely initiated group call;
- the term "remote MCPTT user" is used to refer to the user who is sent a request to initiate a remotely initiated group call; and
- the term "targeted MCPTT group" is used to refer to the group that is to be called in the requested remotely initiated group call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.2 Client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.2.1 Remotely initiated group call initiation request procedures
|
Upon receiving a request from the requesting MCPTT user to send a remotely initiated group call request to the remote MCPTT user for a targeted MCPTT group, the MCPTT client:
1) if:
a) the <allow-request-remote-init-group-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false":
then:
a) should indicate to the requesting MCPTT user that the requesting MCPTT user is not authorised to initiate a remotely initiated group call request to the remote MCPTT user; and
b) shall skip the rest of the steps of the present clause;
1A) shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "true", then the MCPTT client:
a) should indicate to the MCPTT user that calls are not allowed on the indicated group; and
b) shall skip the remainder of this procedure;
2) void; and
3) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
d) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-request-uri> set to the MCPTT group identity of the targeted MCPTT group for the remotely initiated call; and
ii) an <anyExt> element containing:
A) the <request-type> element set to a value of "remotely-initiated-group-call-request";
B) the <notify-remote-user> element set to a value of "true" if the requesting MCPTT user has indicated that the remote MCPTT user be notified of the remotely initiated group call request;
C) the <notify-remote-user> element set to a value of "false" if the requesting MCPTT user has indicated that the remote MCPTT user not be notified of the remotely initiated group call request; and
D) may include <ric-app-level-priority> element set to a value of the namespace and priority values as specified in IETF RFC 8101 [48], and MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) to be used by the remote MCPTT user to request an application level priority while initiating a call as a result of received remotely initiated call request;
e) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the remote MCPTT user, according to rules and procedures of IETF RFC 5366 [20]; and
f) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the remote MCPTT user; and
4) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, should indicate to the requesting MCPTT user the failure of the sent remotely initiated group call request and not continue with the rest of the steps.
Upon receiving a "SIP MESSAGE request for remotely initiated group call response for terminating client", the MCPTT client:
1) shall determine the success or failure of the sent remotely initiated group call request from the value of the <remotely-initiated-call -outcome> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
2) should indicate to the requesting MCPTT user the success or failure of the sent remotely initiated group call request.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.2.2 Remote client procedures for handling remotely initiated group call request
|
Upon receiving a "SIP MESSAGE request for remotely initiated group call request for terminating client", the MCPTT client:
1) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "true", may indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
2) if according to local policy on-demand sessions are to be used for remotely initiated group calls, shall invoke the procedures of clause 10.1.1.2.1.1 to originate an MCPTT group call to the targeted MCPTT group with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
ii) shall not give any indication to the remote MCPTT user that the remotely initiated call origination is in progress; and
b) if the <ric-app-level-priority> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP INVITE request with the value received in the <ric-app-level-priority> element; and
3) if according to local policy pre-established sessions are to be used for remotely initiated group calls and a pre-established session is available, shall invoke the procedures of clause 10.1.1.2.2.1 to originate an MCPTT group call to the targeted MCPTT group with the following clarifications:
a) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "false":
i) shall not indicate to the remote MCPTT user that a remotely initiated call request to call the targeted MCPTT group has been received; and
ii) shall not give any indication to the remote MCPTT user that the remotely initiated call origination is in progress; and
b) if the <ric-app-level-priority> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of the namespace and priority value, may include Resource-Priority header field in the initial SIP REFER request with the value received in the <ric-app-level-priority> element.
Editor's note: It is FFS that how the client will handle the request if according to local policy pre-established sessions are to be used for remotely initiated group calls and a pre-established session is not available.
Upon completion of the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1, the MCPTT client:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
b) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
d) shall include in a "uri" attribute of <entry> element of a <list> element of the <resource-lists> element of an application/resource-lists+xml MIME body the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/ vnd.3gpp.mcptt-info+xml MIME body of the received SIP MESSAGE request; and
e) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element containing:
i) the <mcptt-request-uri> set to the MCPTT group identity called by the remote MCPTT user; and
ii) an <anyExt> element containing:
A) the <response-type> element set to a value of "remotely-initiated-group-call-response";
B) if the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1 were successful in originating an MCPTT group call to the targeted MCPTT group, a <remotely-initiated-call-outcome> element set to a value of "success"; and
C) if the procedures of clause 10.1.1.2.1.1 or clause 10.1.1.2.2.1 were not successful in originating an MCPTT group call to the targeted MCPTT group, a <remotely-initiated-call-outcome> element set to a value of "fail";
2) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the requesting MCPTT user; and
3) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.3 Participating MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.3.1 Originating procedures
|
In the procedures of this clause:
- the term "requesting MCPTT user" is used to refer to the user who sent a request to initiate a remotely initiated group call; and
- the term "remote MCPTT user" is used to refer to the user who is sent a request to initiate a remotely initiated group call.
Upon receiving a "SIP MESSAGE request for remotely initiated group call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1 The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
2a) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
3) if the "SIP MESSAGE request for remotely initiated group call for originating participating MCPTT function" contains the <request-type> element set to a value of "remotely-initiated-group-call-request":
a) if the <allow-request-remote-init-group-call> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "157 user not authorised to request a remotely initiated group call" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
4) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4);
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
8) shall copy the contents of the application/resource-lists+xml MIME body into the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> element of the <mcptt-Params> element of the <mcpttinfo> element to the MCPTT ID determined in step 2) above;
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
11) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
14) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the sent SIP MESSAGE request, the participating MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the MCPTT client.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.3.2 Terminating procedures
|
Upon receiving a "SIP MESSAGE request for remotely initiated group call for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response and skip the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP INVITE request; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall forward the SIP 2xx response to the controlling MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.5.4 Controlling MCPTT function procedures
|
Upon receiving:
- a "SIP MESSAGE request for remotely initiated group call request for controlling MCPTT function"; or
- a "SIP MESSAGE request for remotely initiated group call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2A) if the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element that is set to the value "true", shall shall reject the SIP request with a SIP 403 (Forbidden) response with the warning text set to "167 call is not allowed on the preconfigured group" as specified in clause 4.4 "Warning header field" and skip the rest of the steps;
3) if:
a) there is a <request-type> element set to a value of "remotely-initiated-group-call-request" contained in the <anyExt> element in the <mcptt-Params> element contained in the <mcpttinfo> root element contained in the application/vnd.3gpp. mcptt-info+xml MIME body in the received SIP MESSAGE request; and
b) if the MCPTT user identified by the MCPTT ID in the "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the SIP MESSAGE request is not affiliated with the MCPTT group identified by the <mcptt-request-uri> in the application/vnd.3gpp. mcptt-info+xml MIME body as determined by the procedures of clause 6.3.6;
then:
a) shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
4) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
7) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request with the following clarifications:
a) shall set the <mcptt-calling-group-id> to the MCPTT group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request; and
b) shall set the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request to the MCPTT ID contained in the "uri" attribute of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body contained in the received SIP MESSAGE request;
8) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated with the MCPTT user identified by the MCPTT ID contained in the <mcptt-request-uri> element of the application/vnd.3gpp. mcptt-info+xml MIME body in the outgoing SIP MESSAGE request;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the targeted MCPTT user or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
9) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
11) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall generate a SIP 200 (OK) response and forward the SIP 200 (OK) response to the originating participating MCPTT function.
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, the controlling MCPTT function shall forward the error response to the originating participating MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6 Change of in-progress imminent peril state of the MCPTT group
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.1 General
|
Clause 10.1.6 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for the on-network canceling of in-progress imminent peril state of the MCPTT group while there is no MCPTT session is ongoing on the MCPTT group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.2 Client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.2.1 MCPTT group in-progress imminent peril state cancel initiation
|
Upon receiving a request from an MCPTT user to cancel the in-progress imminent peril state on a prearranged MCPTT group on which there is no call ongoing, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
NOTE 1: This SIP MESSAGE request is assumed to be sent out-of-dialog.
The MCPTT client:
1) if the MCPTT user is not authorised to cancel the in-progress imminent peril state of the MCPTT group as determined by the procedures of clause 6.2.8.1.A and clause 6.2.8.1.10, the MCPTT client:
a) should indicate to the MCPTT user that they are not authorised to cancel the in-progress imminent peril state of the MCPTT group; and
b) shall skip the remaining steps of the current clause;
2) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
3) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing the public user identity of the originator as specified in 3GPP TS 24.229 [4];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT group identity;
b) the <imminentperil-ind> element set to a value of "false";
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
d) if the MCPTT client needs to include an active functional alias in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 2: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
6) shall set the Request-URI to the public service identity identifying the participating MCPTT function serving the MCPTT user;
7) shall set MCPTT imminent peril group state to "MIG 3: cancel-pending"; and
8) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT imminent peril group state to "MIG 1: no-imminent peril".
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the MCPTT client shall set the MCPTT imminent peril group state to "MIG 2: in-progress".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.2.2 Reception of MCPTT group in-progress imminent peril state cancel notification
|
Upon receiving a "SIP MESSAGE request for imminent peril state change notification for terminating MCPTT client" for the cancellation of the in-progress imminent peril state of the MCPTT group, the MCPTT client:
1) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "false":
a) should display to the MCPTT user an indication of the cancellation of the in-progress imminent peril state of the MCPTT group including the following:
i) the MCPTT group identity contained in the <mcptt-calling-group-id> element application/vnd.3gpp.mcptt-info+xml MIME body; and
ii) the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
b) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril";
2) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4]; and
3) shall send the SIP 200 (OK) response towards the participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.3 Participating MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.3.1 Originating procedures
|
a) 10.1.6.3.1.1 Reception of MCPTT group in-progress imminent peril state cancel initiation
Upon receipt of a "SIP MESSAGE request for imminent peril state change request for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall determine the MCPTT ID of the calling user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
NOTE 1: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the MCPTT user is not affiliated with the MCPTT group as determined by clause 9.2.2.2.11, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
5) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the group identity or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
6) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
7) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 5);
8) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body in the received SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 included in the outgoing SIP MESSAGE request;
9) shall set the <mcptt-calling-user-id> contained in <mcptt-Params> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the MCPTT ID determined in step 2) above;
10) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
11) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
12) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
13) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
14) shall send the SIP MESSAGE request towards the controlling MCPTT function as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent above:
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4] with the follow clarifications:
a) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function; and
2) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the error response to the MCPTT client.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.3.2 Terminating Procedures
|
b) 10.1.6.3.2.1 Reception of MCPTT group in-progress imminent peril state cancel notification
Upon receipt of a "SIP MESSAGE request for imminent peril state change notification for terminating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
2) shall use the MCPTT ID present in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to retrieve the binding between the MCPTT ID and public user identity;
3) if the binding between the MCPTT ID and public user identity does not exist, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps;
4) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
6) shall send the SIP MESSAGE request towards MCPTT client as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the SIP MESSAGE request sent above:
1) shall generate a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4]; and
2) shall send the SIP 200 (OK) response to the controlling MCPTT function according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, shall forward the response to the controlling MCPTT function.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.4 Controlling MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.1.6.4.1 Terminating Procedures
|
c) 10.1.6.4.1.1 Reception of MCPTT group in-progress imminent peril state cancel initiation
Upon receipt of a "SIP MESSAGE request for imminent peril state change request for controlling MCPTT function", the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
3) if the received SIP MESSAGE request is an unauthorised request for an MCPTT in-progress imminent peril state of group cancellation as specified in clause 6.3.3.1.13.B and clause 6.3.3.1.13.6, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
4) set the in-progress imminent peril state of the MCPTT group to a value of "false";
5) cache the information that the MCPTT user has cancelled the outstanding in-progress imminent peril state of the group and clear the cache of the all MCPTT ID of the MCPTT users that triggered the setting of the in-progress imminent peril state of the MCPTT group to "true";
6) for each of the affiliated members of the group shall:
a) generate a SIP MESSAGE request notification of the cancellation of the MCPTT user's imminent peril call as specified in clause 6.3.3.1.11;
b) set the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of the <mcptt-calling-user-id> element in the received SIP MESSAGE request;
c) set the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to a value of "false"; and
d) send the SIP MESSAGE request towards the terminating participating MCPTT function according to 3GPP TS 24.229 [4];
7) shall generate a SIP 200 (OK) response to the received SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
8) shall send the SIP 200 (OK) response towards the originating participating MCPTT function to the received SIP MESSAGE as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx, SIP 4xx, 5xx or 6xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2 Off-network group call
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.1 General
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.1.1 Common Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.1.1.1 MONP message transport
|
In order to participate in a call of an MCPTT group, the MCPTT client:
1) shall send the MONP message as a UDP message to the multicast IP address of the MCPTT group, to UDP port 8809, with an IP time-to-live set to 255; and
2) shall treat UDP messages received on the multicast IP address of the MCPTT group and on port 8809 as received MONP messages.
The MONP message is the entire payload of the UDP message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.1.1.2 Session description
|
For an off-network MCPTT session, only MCPTT speech is used.
One off-network MCPTT session includes one media-floor control entity.
The MCPTT client shall generate an SDP body for a group call in accordance with rules and procedures of RFC4566 [12].
The MCPTT client:
1) shall include in the session-level section:
a) the "o=" field with the <username> portion set to a dash;
b) the "s=" field with the <session name> portion set to a dash; and
c) the "c=" field with the <nettype> portion set to "IN", the <addrtype> portion set to the IP version of a multicast IP address of the MCPTT group and the <connection-address> portions set to the multicast IP address of the MCPTT group;
2) shall include the media-level section for MCPTT speech consisting of:
a) the "m=" field with the <media> portion set to "audio", the <port> portion set to a port number for MCPTT speech of the MCPTT group, the <proto> field set to "RTP/AVP" and <fmt> portion set indicating RTP payload type numbers;
b) the "i=" field with the <session description> portion set to "speech";
c) the "a=fmtp:" attribute(s), the "a=rtpmap:" attribute(s) or both, indicating the codec(s) and media parameters of the MCPTT speech with the following clarification:
i) if the "/<x>/<x>/Common/PreferredVoiceCodec" leaf node is present in the group document configured on the group management client as specified in 3GPP TS 24.483 [45] containing an RTP payload format name as specified in IETF RFC 4566 [12], indicating a preferred voice codec for an MCPTT group; and
ii) if the MCPTT client supports the encoding name indicated in the value of the "name" attribute;
then the MCPTT client:
i) shall insert the value of the "/<x>/<x>/Common/PreferredVoiceCodec" leaf node in the <encoding name> field of the "a=rtpmap" attribute as defined in IETF RFC 4566 [12]; and
d) the "a=rtcp:" attribute indicating port number to be used for RTCP at the MCPTT client selected according to the rules and procedures of IETF RFC 3605 [13], if the media steam uses other than the default IP address; and
3) shall include the media-level section for media-floor control entity consisting of:
a) an "m=" line, with the <media> portion set to "application", the <port> portion set to a port number for media-floor control entity of the MCPTT group, the <proto> field set to "udp" and <fmt> portion set to "MCPTT"; and
b) the "a=fmtp:MCPTT" attribute indicating the parameters of the media-floor control entity as specified 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2 Basic call control
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.1 General
|
In this release of specification, media streams of off-network group call cannot be modified and the SDP is the same for the entire duration of the call.
The maximum number of simultaneous off-network group calls is limited by the value of "/<x>/Common/MCPTTGroupCall/MaxCallN4" leaf node present in the UE configuration as specified in 3GPP TS 24.483 [45].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.2 Basic call control state machine
|
The Figure 10.2.2.2-1 gives an overview of the main states and transitions on the UE for call control.
Each call control state machine is per MCPTT group ID.
Figure 10.2.2.2-1: Basic call control state machine
The following pieces of information are associated with the basic call control state machine:
a) the stored call identifier of the call;
b) the probe response value of the call;
c) the stored refresh interval of the call;
d) the stored SDP body of the call;
e) the stored originating MCPTT user ID of the call;
f) the stored MCPTT group ID of the call; and
g) the stored call start time of the call.
The basic call control state machine has a related call type control state machine described in clause 10.2.3.2.
When sending the message, MCPTT client indicates the stored current ProSe per-packet priority associated with the call type control state machine to the lower layers.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3 Call Control states
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.1 S1: start-stop
|
This state exists for UE, when the UE is not part of an ongoing call.
This state is the start state of this state machine.
This state is the stop state of this state machine.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.2 S2: waiting for call announcement
|
This state exists for UE, when the UE has sent a GROUP CALL PROBE message and is waiting for a GROUP CALL ANNOUNCEMENT message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.3 S3: part of ongoing call
|
This state exists for UE, when the UE is part of an ongoing group call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.4 S4: pending user action without confirm indication
|
This state exists for UE, when the UE has presented a notification to the MCPTT user for the received GROUP CALL ANNOUNCEMENT message, is waiting for a response and is not expected to send confirm indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.5 S5: pending user action with confirm indication
|
This state exists for UE, when the UE has presented a notification to the MCPTT user for the received GROUP CALL ANNOUNCEMENT message, is waiting for a response and is expected to send confirm indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.6 S6: ignoring incoming call announcements
|
This state exists for UE, when the group call was rejected or released, GROUP CALL ANNOUNCEMENT message was sent or received and GROUP CALL ANNOUNCEMENT messages continue being received.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.3.7 S7: waiting for call announcement after call release
|
This state exists for UE, when the group call was released, GROUP CALL ANNOUNCEMENT message was neither sent nor received and GROUP CALL PROBE was sent.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4 Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.1 General
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.1.1 Call announcement timer calculation
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.1.1.1 Periodic call announcement timer calculation
|
The MCPTT client:
1) shall generate a random number, X, with uniform distribution between 0 and 1; and
2) shall set the TFG2 (periodic announcement) timer as follows:
- TFG2 (periodic announcement) = the refresh interval of the call * (2/3 + 2/3*X) seconds.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.1.1.2 Call announcement timer calculation after CALL PROBE
|
The MCPTT client:
1) shall generate a random number, X, with uniform distribution between 0 and 1; and
2) shall set the TFG2 (periodic announcement) timer as follows:
- TFG2 (periodic announcement) = 1/12*X seconds.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.1.2 Max duration timer calculation
|
The MCPTT client shall set the TFG6 (max duration) timer as follows:
- TFG6 (max duration) = X – (Y – Z) seconds, where:
- X = value of "/<x>/<x>/OffNetwork/MaxDuration" leaf node present in group configuration as specified in 3GPP TS 24.483 [45];
- Y = current UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds);
- Z = Call start time IE of the GROUP CALL ANNOUNCEMENT message or the stored call start time, if a GROUP CALL ANNOUNCEMENT message was not received that caused this max duration timer calculation to be invoked.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.2 Call Probe
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.2.1 Call probe initiation
|
When in the "S1: start-stop" state, upon an indication from an MCPTT user to initiate a group call for an MCPTT group ID, the MCPTT client:
1) shall store the MCPTT group ID as the MCPTT group ID of the call;
2) shall create a call type control state machine as described in clause 10.2.3.2;
3) shall generate a GROUP CALL PROBE message as specified in clause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
4) shall send the GROUP CALL PROBE message as specified in clause 10.2.1.1.1;
5) shall start timer TFG3 (call probe retransmission);
6) shall start timer TFG1 (wait for call announcement); and
7) shall enter the "S2: waiting for call announcement" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.2.2 Call probe retransmission
|
When in the "S2: waiting for call announcement" state, upon expiration of TFG3 (call probe retransmission), the MCPTT client:
1) shall generate a GROUP CALL PROBE message as specified in clause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
2) shall send the GROUP CALL PROBE message as specified in clause 10.2.1.1.1;
3) shall start timer TFG3 (call probe retransmission); and
4) shall remain in the "S2: waiting for call announcement" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.2.3 Receiving GROUP CALL PROBE message when participating in the ongoing call
|
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL PROBE message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) if the stored probe response value of the call is set to "false":
a) shall stop timer TFG2 (call announcement);
b) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.2; and
c) shall set the stored probe response of the call to "true"; and
2) shall remain in the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3 Call setup
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.1 Not receiving any response to GROUP CALL PROBE message
|
When in the "S2: waiting for call announcement" state, upon expiry of timer TFG1 (wait for call announcement), the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission), if running;
2) shall generate an SDP body as specified in clause 10.2.1.1.2 and store it as the SDP body of the call;
3) shall generate a random number with uniform distribution between 0 and 65535 and store it as the call identifier of the call;
4) shall select refresh interval value and store it as the refresh interval of the call;
5) shall store own MCPTT user ID as the originating MCPTT user ID of the call;
6) shall store the current UTC time as the call start time of the call;
7) shall generate a GROUP CALL ANNOUNCEMENT message as specified in clause 15.1.3. In the GROUP CALL ANNOUNCEMENT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Call type IE to the stored current call type associated with the call type control state machine;
c) shall set the Refresh interval IE to the stored refresh interval of the call;
d) shall set the SDP IE to the stored SDP body of the call;
e) shall set the Originating MCPTT user ID IE to the stored originating MCPTT user ID of the call;
f) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
g) shall set the Call start time IE to the stored call start time of the call;
h) shall set the Last call type change time IE to the stored last call type change time of the call associated with call type control state machine;
i) shall set the Last user to change call type IE to last user to change call type associated with call type control state machine; and
j) may include the Confirm mode indication IE;
8) shall send the GROUP CALL ANNOUNCEMENT message as specified in clause 10.2.1.1.1;
9) shall establish a media session based on the stored SDP body of the call;
10) shall start floor control as originating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
11) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
12) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
13) shall enter the "S3: part of ongoing call" state.
Note: In this release of the specification, the refresh interval of the call is fixed to 10 seconds.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.2 Receiving a GROUP CALL ANNOUNCEMENT message
|
When in the "S2: waiting for call announcement" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission);
2) shall stop timer TFG1 (wait for call announcement);
3) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
4) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
5) shall store the value of the originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the Originating MCPTT user ID of the call;
6) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
7) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
8) shall establish a media session based on the stored SDP body of the call;
9) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
10) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2;
11) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
12) shall enter the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.3 Receiving a GROUP CALL ANNOUNCEMENT message when not participating in the ongoing call
|
When in the "S1: start-stop" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE not matching MCPTT group ID of the call stored for other state machines, the MCPTT client:
1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;
4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
5) shall store the value of the MCPTT group ID IE of the GROUP CALL ANNOUNCEMENT message as the MCPTT group ID of the call;
6) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
7) shall create a call type control state machine as described in clause 10.2.3.2;
8) if the terminating UE is configured that the terminating MCPTT user acknowledgement is required upon a terminating call request reception:
a) shall start timer TFG4 (waiting for the user);
b) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE, shall enter the "S5: pending user action with confirm indication" state; and
c) if the GROUP CALL ANNOUNCEMENT message does not contains the Confirm mode indication IE, shall enter the "S4: pending user action without confirm indication" state; and
9) if the terminating UE is configured that the terminating MCPTT user acknowledgement is not required upon a terminating call request reception:
a) shall establish a media session based on the stored SDP body of the call;
b) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
c) if the GROUP CALL ANNOUNCEMENT message contains the Confirm mode indication IE:
i) shall generate a GROUP CALL ACCEPT message as specified in clause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:
A) shall set the Call identifier IE to the stored call identifier of the call;
B) shall set the Sending MCPTT user ID IE to own MCPTT user id;
C) shall set the Call type IE to the stored current call type associated with the call type control state machine; and
D) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
ii) shall send the GROUP CALL ACCEPT message as specified in clause 10.2.1.1.1;
d) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2;
e) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
f) shall enter the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.4 MCPTT user accepts the terminating call with confirm indication
|
When in the "S5: pending user action with confirm indication" state, upon indication from the MCPTT user to accept the incoming group call, the MCPTT client:
1) shall establish a media session based on the stored SDP body of the call;
2) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall generate a GROUP CALL ACCEPT message as specified in clause 15.1.4. In the GROUP CALL ACCEPT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Sending MCPTT user ID IE to own MCPTT user id;
c) shall set the Call type IE to the stored current call type associated with the call type control state machine; and
d) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
4) shall send the GROUP CALL ACCEPT message as specified in clause 10.2.1.1.1;
5) shall stop timer TFG4;
6) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
7) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
8) shall enter the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.5 MCPTT user accepts the terminating call without confirm indication
|
When in the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to accept the incoming group call, the MCPTT client:
1) shall establish a media session based on the stored SDP body of the call;
2) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
3) shall stop timer TFG4;
4) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
5) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
6) shall enter the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.6 Receiving GROUP CALL ACCEPT message
|
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ACCEPT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) can inform the MCPTT user about the call acceptance; and
2) shall remain in the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.7 MCPTT user rejects the terminating call
|
When in the "S5: pending user action with confirm indication" state or the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to reject the incoming group call, the MCPTT client:
1) shall stop timer TFG4 (waiting for the user);
2) shall start timer TFG5 (not present incoming call announcements); and
3) shall enter the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.3.8 MCPTT user does not act on terminating call
|
When in the "S5: pending user action with confirm indication" state or the "S4: pending user action without confirm indication" state, upon expiration of timer TFG4 (waiting for the user), the MCPTT client:
1) shall start timer TFG5 (not present incoming call announcements); and
2) shall enter the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.4 Periodic group call announcement
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.4.1 Sending periodic call announcement
|
When in the "S3: part of ongoing call" state, upon expiry of timer TFG2 (call announcement), the MCPTT client:
1) shall generate a GROUP CALL ANNOUNCEMENT message as specified in clause 15.1.3. In the GROUP CALL ANNOUNCEMENT message, the MCPTT client:
a) shall set the Call identifier IE to the stored call identifier of the call;
b) shall set the Call type IE to the stored current call type associated with the call type control state machine;
c) shall set the Refresh interval IE to the stored refresh interval of the call;
d) shall set the SDP IE to the stored SDP body of the call;
e) shall set the Originating MCPTT user ID IE to the stored originating MCPTT user ID of the call;
f) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call;
g) shall set the Last call type change time IE to the stored last call type change time of the call associated with call type control state machine;
h) shall set the Last user to change call type IE to last user to change call type associated with call type control state machine;
i) shall set the Call start time IE to the stored call start time of the call;
j) if the stored probe response value of the call is set to "true", shall include Probe response IE;
2) shall send the GROUP CALL ANNOUNCEMENT message as specified in clause 10.2.2.1.1.1;
3) if the stored probe response value of the call is set to "true", shall set the stored probe response value of the call to "false";
4) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
5) shall remain in the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.4.2 Receiving periodic call announcement
|
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the Call start time IE being the same as the stored call start time of the call, the Last call type change time IE being the same as the stored last call type change time of the call associated with the call type control state machine, the Last user to change call type IE being the same as the stored last user to change call type of the call associated with the call type control state machine and the Call identifier IE being the same as the stored call identifier of the call and Call type IE same as the stored current call type associated with the call type control state machine and:
1) if the stored probe response value of the call is set to "true" and GROUP CALL ANNOUNCEMENT message contains Probe response IE; or
2) if the stored probe response value of the call is set to "false":
the MCPTT client,
1) shall stop timer TFG2 (call announcement);
2) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1;
3) shall set the stored probe response of the call to "false", if set to "true"; and
4) shall remain in the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5 Call release
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.1 MCPTT user leaves the call when GROUP CALL ANNOUNCEMENT was sent or received
|
When in the "S3: part of ongoing call" state, the "S5: pending user action with confirm indication" state, or the "S4: pending user action without confirm indication" state, upon an indication from the MCPTT user to release the group call, the MCPTT client:
1) shall release the media session, if established;
2) shall stop floor control as specified in clause 7.2.3.9.2 in 3GPP TS 24.380 [5];
3) shall stop timer TFG4 (waiting for the user), if running;
4) shall stop timer TFG2 (call announcement), if running;
5) shall start timer TFG5 (not present incoming call announcements);
6) shall stop timer TFG6 (max duration), if running; and
7) shall enter the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.2 Receiving GROUP CALL ANNOUNCEMENT message for rejected or released call
|
When in the "S6: ignoring incoming call announcements" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;
4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
5) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
6) shall stop timer TFG5 (not present incoming call announcements);
7) shall start timer TFG5 (not present incoming call announcements); and
8) shall remain in the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.3 MCPTT user initiates originating call for rejected or released call
|
When in the "S6: ignoring incoming call announcements" state, upon an indication from the MCPTT user to initiate a group call for an MCPTT group ID matching the stored MCPTT group ID of the call, the MCPTT client:
1) stop timer TFG5 (not present incoming call announcements);
2) shall establish a media session based on the stored SDP body of the call;
3) shall start floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
4) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2 (using stored call start time);
5) shall start timer TFG2 (call announcement) with value as specified in clause 10.2.2.4.1.1.1; and
6) shall enter the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.4 No GROUP CALL ANNOUNCEMENT messages for rejected or released call
|
When in the "S6: ignoring incoming call announcements" state, upon expiration of timer TFG5 (not present incoming call announcements), the MCPTT client:
1) shall release the stored SDP body of the call;
2) shall release the stored call identifier of the call;
3) shall release the stored originating MCPTT user ID of the call;
4) shall release the stored refresh interval of the call;
5) shall release the stored MCPTT group ID of the call;
6) shall release the stored call start time of the call;
7) shall destroy the call type control state machine as specified in clause 10.2.3.4.10 or 10.2.3.4.11; and
8) shall enter the "S1: start-stop" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.5 MCPTT user leaves the call when GROUP CALL PROBE was sent
|
When in the "S2: waiting for call announcement" state, upon an indication from the MCPTT user to release the group call, the MCPTT client:
1) shall stop timer TFG3 (call probe retransmission); and
2) shall enter the "S7: Waiting for call announcement after call release" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.6 MCPTT user initiates originating call for released call
|
When in the "S7: Waiting for call announcement after call release" state, upon an indication from the MCPTT user to initiate a group call for an MCPTT group ID matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall stop timer TFG1 (wait for call announcement);
2) shall generate a GROUP CALL PROBE message as specified in clause 15.1.2. In the GROUP CALL PROBE message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID of the call; and
3) shall send the GROUP CALL PROBE message as specified in clause 10.2.1.1.1;
4) shall start timer TFG3 (call probe retransmission);
5) shall start timer TFG1 (wait for call announcement); and
6) shall enter the "S2: waiting for call announcement" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.7 Receiving GROUP CALL ANNOUNCEMENT message for released call
|
When in the "S7: Waiting for call announcement after call release" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call, the MCPTT client:
1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;
4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
5) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
6) shall stop timer TFG1 (wait for call announcement);
7) shall start timer TFG5 (not present incoming call announcements); and
8) shall enter the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.8 No GROUP CALL ANNOUNCEMENT messages for released call
|
When in the "S7: Waiting for call announcement after call release" state, upon expiration of timer TFG1 (wait for call announcement), the MCPTT client:
1) shall release the stored MCPTT group ID of the call;
2) shall destroy the call type control state machine as specified in clause 10.2.3.4.11; and
3) shall enter the "S1: start-stop" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.5.9 Max duration reached
|
When in the "S3: part of ongoing call" state, upon expiration of timer TFG6 (max duration), the MCPTT client:
1) shall release the media session;
2) shall stop floor control as specified in clause 7.2.3.9.2 in 3GPP TS 24.380 [5];
3) shall stop timer TFG2 (call announcement), if running;
4) shall start timer TFG5 (not present incoming call announcements); and
5) shall enter the "S6: ignoring incoming call announcements" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.6 Merge of calls
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.6.1 Merge of two calls
|
When in the "S3: part of ongoing call" state, upon receiving a GROUP CALL ANNOUNCEMENT message with the MCPTT group ID IE matching the stored MCPTT group ID of the call and:
1) the Originating MCPTT user ID IE is different from the stored originating MCPTT user ID of the call; or
2) the Call identifier IE is different from the stored call identifier of the call;
then:
1) if the stored current call type associated with the call type control state machine is "BASIC GROUP CALL" and the value of the Call type IE of GROUP CALL ANNOUNCEMENT message is either "IMMINENT PERIL GROUP CALL" or "EMERGENCY GROUP CALL";
2) if the stored current call type associated with the call type control state machine is "IMMINENT PERIL GROUP CALL" and the value of the Call type IE of GROUP CALL ANNOUNCEMENT message is "EMERGENCY GROUP CALL";
3) if the stored current call type associated with the call type control state machine being equal to the Call type IE of the GROUP CALL ANNOUNCEMENT message and the Call start time IE of the GROUP CALL ANNOUNCEMENT message being lower than the stored call start time of the call; or
4) if the stored current call type associated with the call type control state machine being equal to the Call type IE of the GROUP CALL ANNOUNCEMENT message and the Call start time IE of the GROUP CALL ANNOUNCEMENT message being equal to the stored call start time of the call and the Call identifier IE of the GROUP CALL ANNOUNCEMENT message being lower than the stored call identifier of the call;
the MCPTT client:
1) shall store the value of the SDP IE of the GROUP CALL ANNOUNCEMENT message as the SDP body of the call;
2) shall store the value of the Call identifier IE of the GROUP CALL ANNOUNCEMENT message as the call identifier of the call;
3) shall store the value of the Originating MCPTT user ID IE of the GROUP CALL ANNOUNCEMENT message as the originating MCPTT user ID of the call;
4) shall store the value of the Refresh interval IE of the GROUP CALL ANNOUNCEMENT message as the refresh interval of the call;
5) shall store the value of the Call start time IE of the GROUP CALL ANNOUNCEMENT message as the call start time of the call;
6) shall adjust the media session based on the stored SDP body of the call and restart floor control as terminating floor participant as specified in clause 7.2 in 3GPP TS 24.380 [5];
7) shall stop timer TFG6 (max duration);
8) shall start timer TFG6 (max duration) with value as specified in clause 10.2.2.4.1.2;
9) shall stop timer TFG2 (call announcement); and
10) shall start timer TFG2 (call announcement) with value according to rules and procedures as specified in clause 10.2.2.4.1.1.1; and
11) shall remain in the "S3: part of ongoing call" state.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.7 Error handling
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.7.1 Unexpected MONP message received
|
Upon receiving a MONP message in a state where there is no handling specified for the MONP message, the MCPTT client shall discard the MONP message.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.7.2 Unexpected indication from MCPTT user
|
Upon receiving an indication from the MCPTT user in a state where there is no handling specified for the indication, the MCPTT client shall ignore the indication.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.2.4.7.3 Unexpected expiration of a timer
|
Upon expiration of a timer in a state where there is no handling specified for expiration of the timer, the MCPTT client shall ignore the expiration of the timer.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3 Call type control
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3.1 General
|
This state machine exists in parallel with the basic call control state machine for off-network group call as specified in clause 10.2.2.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3.2 Call type control state machine
|
The Figure 10.2.3.2-1 gives an overview of the states and transitions of the state machine.
Figure 10.2.3.2-1: Call type control state machine
The following pieces of information are associated with the call type control state machine:
a) the stored current call type;
b) the stored current ProSe per-packet priority;
c) the stored last call type change time of the call; and
d) the stored last user to change call type of the call.
When sending the message, MCPTT client indicates the stored current ProSe per-packet priority (as described in 3GPP TS 24.483 [45]) associated with the call type control state machine to the lower layers.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3.3 Call type control states
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3.3.1 T0: waiting for call to establish
|
This state is the start state of this state machine.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
10.2.3.3.2 T1: in-progress emergency group call
|
This state exists for UE, when the UE is part of an in-progress emergency group call.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.