hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3 Adhoc group call release
|
This clause describes the originating, and terminating call release participating MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.1 Call release procedures using on-demand session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.1.1 Originating procedures
|
Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.1.2 Terminating procedures
|
Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.2 Call release procedures using pre-established session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.2.1 Originating procedures
|
Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.3.2.2 Terminating procedures
|
Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.4 Adhoc group call rejoin
|
This clause describes the originating, and terminating call rejoin participating MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.4.1 Call rejoin procedures using on-demand session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.4.1.1 Originating procedures
|
Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "adhoc", the participating MCPTT function shall follow the procedures specified in clause 17.3.2.1.1 with the clarification in step 10) of clause 17.3.2.1.1 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity which mapped to the MCPTT session identity provided in Request-URI of the "SIP INVITE request for originating participating MCPTT function".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.4.2 Call rejoin procedures using pre-established session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.4.2.1 Originating procedures
|
Upon receipt of a "SIP REFER request for a pre-established session", with the Refer-To header containing an application/vnd.3gpp.mcptt-info+xml MIME type content in an hname "body" parameter in the headers portion of the SIP URI and with the <session-type> element set to "adhoc", the participating MCPTT function shall follow the procedures specified in clause 17.3.2.2.1 with the clarification in step 13) of clause 17.3.2.2.1 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity which mapped to the MCPTT session identity provided in the Refer-To header field of the "SIP REFER request for a pre-established session".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.5 Adhoc group call participants modify
|
This clause describes the originating adhoc group call participants modify participating MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.5.1 Call participants modify procedures using on-demand session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.5.1.1 Originating procedures
|
Upon receipt of a SIP re-INVITE request for an MCPTT session identifying an on-demand MCPTT adhoc group session, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP re-INVITE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP re-INVITE request;
NOTE: 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 re-INVITE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) shall validate the media parameters and if the MCPTT speech codec is not offered in the SIP re-INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
5) shall generate an outgoing SIP re-INVITE request according to 3GPP TS 24.229 [4];
6) shall copy the application/vnd.3gpp.mcptt-info+xml MIME body from the received SIP re-INVITE request into the outgoing SIP re-INVITE request;
7) shall include the MCPTT ID of the originating user in <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP re-INVITE request;
8) shall include in the SIP re-INVITE request an SDP offer based on the SDP offer in the received SIP re-INVITE request as specified in clause 6.3.2.1.1;
9) shall copy the application/resource-lists+xml MIME body from the received SIP re-INVITE request into the outgoing SIP re-INVITE request; and
10) shall forward the SIP re-INVITE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the above SIP re-INVITE request, the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2;
2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
3) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response;
4) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function; and
5) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 403 (Forbidden) response to the above SIP re-INVITE request, the participating MCPTT function:
1) shall generate a SIP 403 (Forbidden) response according to 3GPP TS 24.229 [4];
2) shall copy, if included in the received SIP 403 (Forbidden) response, the application/vnd.3gpp.mcptt-info+xml MIME body MIME body to the outgoing SIP 403 (Forbidden) response;
3) shall include Warning header field(s) that were received in the incoming SIP 403 (Forbidden) response; and
4) shall forward the SIP 403 (Forbidden) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP re-INVITE request, the participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response; and
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.5.2 Call participants modify procedures initiated by participating MCPTT function
|
This clause describes the procedure to notify the controlling MCPTT function about user meeting or no longer meeting the criteria to be added to or removed from the ongoing adhoc group session.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.5.2.1 Originating procedures
|
When the participating MCPTT function determines that new MCPTT users are meeting the specified criteria or the MCPTT users who are meeting the specified criteria are no longer meeting the specified criteria, the participating MCPTT function:
1) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function;
NOTE 1: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system.
NOTE 4: How the participating MCPTT function determines the public service identity of the controlling MCPTT function 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 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
4) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the adhoc group identity from the stored information;
b) an <anyExt> element containing:
i) the <req-type> element set to a value of "adhoc-group-call-add-participants-request", if the application/resource-lists+xml MIME body contains the list of MCPTT users meeting the specified criteria; or
ii) the <req-type> element set to a value of "adhoc-group-call-remove-participants-request" if the application/resource-lists+xml MIME body contains the list of MCPTT users who are meeting the specified criteria are no longer meeting the specified criteria;
c) shall include an application/resource-lists+xml MIME body with the MCPTT ID and, if applicable and based on local policy the corresponding functional aliases through which the MCPTT users to be added or to be removed have been determined, according to rules and procedures of IETF RFC 5366 [20]; and
NOTE 6: If the criteria together with the local policy contain functional alias related aspects, the participating MCPTT function can use them to determine the functional alias used to address the MCPTT user.
d) shall update the stored information by adding newly determined MCPTT users or by removing MCPTT users; and
5) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.6 Adhoc group call participants determination
|
This clause describes the procedure to provide the user list from the participating MCPTT function serving users based on the criteria for determining the participants to be invited for adhoc group sessions, and handling the notification from the controlling MCPTT function about the release of an adhoc group session to stop determining the users based on the specified criteria.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.6.1 Call participants determination procedures
|
Upon receipt of a "SIP MESSAGE request to get userlist for adhoc group call request for 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 criteria present in the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP MESSAGE request to determine MCPTT users meeting the specified criteria and also based on the local policy to be invited to adhoc group session;
3) if unable to determine the MCPTT users meeting the specified criteria, shall send a SIP 403 (Forbidden) response including warning text set to "187 can't determine the adhoc group participants" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
4) shall generate and send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4];
5) shall, based on local policy, determine and store the list of the MCPTT IDs of the MCPTT users meeting the specified criteria together with, if applicable, the functional aliases through which those MCPTT users are meeting the specified criteria;
NOTE 1: If the criteria together with the local policy contain functional alias related aspects, the the participating MCPTT function can use them to determine the functional alias used to address the MCPTT user.
6) shall store the adhoc group ID and the specified criteria to be used for continuously determining the MCPTT users meeting the criteria and no longer meeting the criteria;
7) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function;
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.
b) 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;
c) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
i) the <mcptt-request-uri> element set to the adhoc group identity;
ii) shall copy the criteria for determining the list of MCPTT users to be called exists in the incoming SIP MESSAGE request included in the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body, into the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP MESSAGE request; and
iii) an <anyExt> element containing:
A) the <resp-type> element set to a value of "get-userlist-adhoc-group-call-response"; and
d) shall include in the newly generated SIP MESSAGE request an application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users in the "uri" attribute, and, if available the corresponding functional aliases in the <functional-alias> element as determined in step 5) in the <entry> element of the <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body, according to rules and procedures of IETF RFC 5366 [20]; and
8) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the participating MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.6.2 Call participants determination stop procedures
|
Upon receipt of a "SIP MESSAGE request to stop determining the participant list for participating MCPTT function", the participating MCPTT function:
1) shall stop determining the MCPTT users meeting and no longer meeting the specified criteria;
2) shall remove all the stored information about the adhoc group ID, the specified criteria and the list of MCPTT IDs of the MCPTT users determined; and
3) shall generate and send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.3.7 Notification of ad hoc group call redirection
|
When receiving a "SIP MESSAGE request to the terminating participating MCPTT function to send notification of adhoc group call redirection", the terminating 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 terminating 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]. The terminating participating MCPTT function shall skip the rest of the steps;
2) shall generate a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and shall send the SIP 200 (OK) response as specified in 3GPP TS 24.229 [4];
3) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
4) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
5) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated with the MCPTT ID of the calling MCPTT user;
6) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
7) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP MESSAGE request to the P-Asserted-Identity header field of the outgoing SIP MESSAGE request; and
8) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4 Controlling MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.1 General
|
This clause describes the adhoc group calls controlling MCPTT function procedures using on-demand and pre-established sessions to setup adhoc group calls, release the ongoing adhoc group calls, and modify (criteria for) the participant list of the ongoing adhoc group calls.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.2 Adhoc group call setup
|
This clause describes the originating, and terminating call setup controlling MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.2.1 Originating Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.2.1.1 INVITE targeted to an MCPTT client
|
This clause describes the procedures for inviting an MCPTT user to an MCPTT session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 17.4.2.2.
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Request-URI to the public service identity of the terminating participating MCPTT function associated to the MCPTT user to be invited;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system.
NOTE 4: How the controlling MCPTT function determines the public service identity of the terminating MCPTT participating function 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.
Editor's Note: [MC_AHGC, CR 0927] The MCPTT user to be invited in the partner MCPTT system by primary MCPTT system while establishing a call using the get user list procedure is need to be specified.
3) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCPTT function;
4) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the MCPTT ID of the terminating user;
b) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in the clause 17.4.2.2;
c) if the ad hoc group call was initiated using call-participants-criterias, the <call-participants-criterias> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5)/b) in clause 17.4.6.1;
NOTE 6: The <mcptt-calling-user-id> is already included in the MIME body as a result of calling clause 6.3.3.1.2 in step 1).
d) if end-to-end security is requested for the call, the <anyExt> element with the <preconfigured-group-id> element set to the preconfigured group identity as determined in the clause 17.4.2.2; and
e) the <called-functional-alias-URI> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body as determined in step 5) in clause 17.3.6.1 of the MCPTT ID of the terminating user, if available;
5) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the originating network according to the procedures specified in clause 6.3.3.1.1;
6) if the in-progress emergency state of the adhoc group is set to a value of "true":
a) shall include a Resource-Priority header field populated with the values for an MCPTT emergency adhoc group call as specified in clause 6.3.3.1.19;
b) if the received SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <adhoc-emergency-ind> element set to a value of "true":
i) shall include in the outgoing SIP INVITE request in the application/vnd.3gpp.mcptt-info+xml MIME body an <adhoc-emergency-ind> element set to a value of "true"; and
c) if the in-progress imminent peril adhoc group state is set to a value of "true" shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <imminentperil-ind> element set to a value of "false";
7) if the in-progress emergency adhoc group state is set to a value of "false" and the in-progress imminent peril adhoc group state is set to a value of "true":
a) shall include a Resource-Priority header field populated with the values for an MCPTT imminent peril adhoc group call as specified in clause 6.3.3.1.19; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body with the <imminentperil-ind> element set to a value of "true";
8) shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP INVITE request into the outgoing SIP INVITE request; and
9) shall send the SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [4].
Upon receiving a SIP 183 (Session Progress) response containing a Require header field with the option tag "100rel" to the SIP INVITE request the controlling MCPTT function:
1) shall send a SIP PRACK request towards the MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response for the SIP INVITE request the controlling MCPTT function:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
2) shall increment the local counter of the number of SIP 200 (OK) responses received from invited members, by 1; and
3) shall send a SIP NOTIFY request to all participants with a subscription to the conference event package as specified in clause 10.1.3.4.
NOTE 7: The procedures executed by the controlling MCPTT function prior to sending a response to the inviting MCPTT client are specified in clause 17.4.2.2.
Upon receiving a SIP 302 (Moved Temporarily) response for the SIP INVITE request and the warning header includes the warning text "191 call forwarding due to migration" the the controlling MCPTT function:
1) shall perform again the procedure in this clause with the only difference to use the MCPTT ID from the <mcptt-request-uri> element in the body of the SIP 302 (Moved Temporarily) response as the target MC user to be invited;
2) may send a SIP MESSAGE to the inviting MCPTT user according to the following steps:
a) generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) 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];
c) 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];
d) shall set the Request-URI to the public service identity of the terminating participating function associated with the MCPTT ID of the calling MCPTT user;
NOTE 8: How the controlling MCPTT function determines the public service identity of the terminating participating MCPTT function associated with the calling MCPTT user is out of the scope of the present document.
e) shall include a P-Asserted-Identity header field set to the public service identity of controlling MCPTT function.
f) shall include in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body:
i) a <forwarding-reason> element set to a value of "migrated";
ii) a <forwarding-target-id> element set to the MCPTT ID in the partner system bound to the primary MCPTT ID at the migration authorization;
iii) a <mcptt-request-uri> element set to the MCPTT ID of the terminating user from its primary MC system before migration; and
iv) a <mcptt-calling-user-id> element set to the MCPTT ID of the initator of the adhoc group call; and
g) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4];
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.2.2 Terminating Procedures
|
In the procedures in this clause:
1) MCPTT ID in an incoming SIP INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) adhoc group identity in an incoming SIP INVITE request if included refers to the adhoc group identity from the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
3) MCPTT ID in an outgoing SIP INVITE request refers to the MCPTT ID of the called user in the <mcptt-request-uri> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request;
4) emergency indication in an incoming SIP INVITE request refers to the <adhoc-emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
5) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP INVITE request for controlling MCPTT function of a MCPTT adhoc group call", 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 INVITE 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;
NOTE 1: If the SIP INVITE request contains an adhoc emergency indication or an adhoc imminent peril indication set to a value of "true" and this is an authorised request for originating an MCPTT emergency adhoc group call as determined by clause 6.3.3.1.13.11, or for originating an MCPTT imminent peril adhoc group call as determined by clause 6.3.3.1.13.12, the controlling MCPTT function can according to local policy choose to accept the request.
2) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps;
3) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) 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";
3a) if received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.3.1.25;
3b) if the SIP INVITE request contains an unauthorised request for an MCPTT emergency adhoc group call as determined by clause 6.3.3.1.13.11:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <adhoc-emergency-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
3c) if the SIP INVITE request contains an unauthorised request for an MCPTT imminent peril adhoc group call as determined by clause 6.3.3.1.13.12, shall reject the SIP INVITE request with a SIP 403 (Forbidden) response with the following clarifications:
a) shall include in the SIP 403 (Forbidden) response an application/vnd.3gpp.mcptt-info+xml MIME body as specified in clause F.1 with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "false"; and
b) shall send the SIP 403 (Forbidden) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
3d) if a Resource-Priority header field is included in the SIP INVITE request:
a) if the Resource-Priority header field is set to the value indicated for adhoc group emergency calls and the SIP INVITE request does not contain an adhoc emergency indication and the in-progress emergency adhoc group state is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps; or
b) if the Resource-Priority header field is set to the value indicated for adhoc group imminent peril calls and the SIP INVITE request does not contain an adhoc imminent peril indication and the in-progress imminent peril adhoc group state is set to a value of "false", shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps;
4) if the originating user identified by the MCPTT ID is not authorised to initiate the adhoc group session if the <allow-adhoc-group-call> element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the originating MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", shall send a SIP 403 (Forbidden) response with the warning text set to: "185 user is not authorised to initiate the adhoc group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
5) if the MCPTT service does not support the adhoc group call, if the <allow-adhoc-group-call-support> element of the <adhoc-group-call> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]) is set to a value of "false" or does not exists, shall send a SIP 403 (Forbidden) response with the warning text set to: "186 the MCPTT system do not support adhoc group call" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
6) if the application/resource-lists+xml MIME body with the MCPTT ID of the invited MCPTT users to be called exists in the incoming SIP INVITE request, shall check if the number of invited participants is within the configured limit as specified in the <max-no-participants> element of the <adhoc-group-call> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]). If not within the configured limit, shall send a SIP 403 (Forbidden) response including warning text set to "189 maximum number of allowed adhoc group participants exceeded" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
7) if the application/resource-lists+xml MIME body with the MCPTT ID of the invited MCPTT users to be called exists in the incoming SIP INVITE request and the <call-participants-criterias> element with one or more criteria as a comma separated into <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request exists, shall send a SIP 403 (Forbidden) response including warning text set to "187 can't determine the adhoc group participants" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
7a) if the <adhoc-grp-emg-alert-grp-ind> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP INVITE request exists with the value set to "true" and adhoc group identified using adhoc group identity does not exist, shall send a SIP 403 (Forbidden) response including warning text set to "187 cant determine the adhoc group participants" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
8) shall perform the actions as described in clause 6.3.3.2.2;
9) shall maintain a local counter of the number of SIP 200 (OK) responses received from invited members and shall initialise this local counter to zero;
9a) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may apply any preferential treatment to the SIP request as specified in 3GPP TS 24.229 [4];
10) if the <adhoc-grp-emg-alert-grp-ind> element set to a value of "false" or does not exists, shall create the adhoc group and generate the adhoc group identity to be associated with the adhoc group if the identity of adhoc group included in the <mcptt-request-uri> element of the <mcptt-Params> element of the <mcpttinfo> element containing in an application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP INVITE request is not acceptable or not included;
11) if originating MCPTT user has requested for end-to-end security by including the <end-to-end-security> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element containing in an application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP INVITE request with the value set to "true", shall determine the preconfigured group from which security related materials can be used by the adhoc group call participants to communicate securely in the adhoc group session;
12) shall determine the members to invite to the adhoc group session:
i) if the application/resource-lists+xml MIME body with the MCPTT ID of the invited MCPTT users to be called exists in the incoming SIP INVITE request, shall consider each entry of the MCPTT users to be invited to the adhoc group session;
ii) if the application/vnd.3gpp.mcptt-info+xml MIME body with the criteria for determining the list of MCPTT users to be called exists in the incoming SIP INVITE request included in the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body, shall determine the users as specified in the clause 17.4.6 and consider each of the determined MCPTT users meeting the specified criteria and also based on the local policy to be invited to the adhoc group session. If unable to determine any users meeting the specified criteria within the call setup duration, shall send a SIP 403 (Forbidden) response including warning text set to "187 can't determine the adhoc group participants" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps; or
iii) if the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-request-uri> element set to an identity of the adhoc group and <adhoc-grp-emg-alert-grp-ind> element with the value set to "true" exists in the incoming SIP INVITE request, shall consider each member of the adhoc group to be invited to the adhoc group session;
13) shall create an adhoc group session and allocate an MCPTT session identity for the adhoc group call. If the request is not for originating a priority adhoc group call, shall start timer TNG3 (group call timer) with the value obtained from the <max-duration-of-call> element of the <adhoc-group-call> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]). When the last MCPTT client leaves the MCPTT session, shall stop timer TNG3 and on expiry of timer TNG3, shall release the MCPTT session;
14) if the received SIP INVITE request contains an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element, the controlling MCPTT function can remember the location information contained in the <location-info> root element;
14A) if the received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-emergency-ind> element set to a value of "true":
i) shall cache the information that the MCPTT user has initiated an MCPTT emergency adhoc group call; and
ii) if the in-progress emergency adhoc group state is set to a value of "false":
A) shall set the value of the in-progress emergency adhoc group state to "true"; and
B) shall start timer TNG2 (in-progress emergency group call timer) with the value obtained from the <group-time-limit> element of the <emergency-call> element of the <on-network> element of the service configuration document as specified in 3GPP TS 24.484 [50] and shall release the MCPTT session on expiry of timer TNG2;
14B) if the in-progress emergency adhoc group state is set to a value of "false" and if the received SIP INVITE request contains <imminentperil-ind> element set to a value of "true", the controlling MCPTT function shall:
i) shall cache the information that the MCPTT user has initiated an MCPTT imminent peril adhoc group call; and
ii) if the in-progress imminent peril adhoc group state is set to a value of "false", shall set the in-progress imminent peril adhoc group state to a value of "true";
15) shall invite each adhoc group member determined in step 12) above, to the adhoc group session, as specified in clause 17.4.2.1.1;
16) shall consider all the invited members as implicitly affiliated to the adhoc group; and
17) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3.
Upon receiving a SIP 183 (Session Progress) response to the SIP INVITE request specified in clause 17.4.2.1.1 containing a P-Answer-State header field with the value "Unconfirmed" as specified in IETF RFC 4964 [34], the controlling MCPTT function supports media buffering and the SIP final response is not yet sent to the inviting MCPTT client:
1) shall generate a SIP 200 (OK) response to SIP INVITE request as specified in the clause 6.3.3.2.3.2;
2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
3) shall include a P-Answer-State header field with the value "Unconfirmed";
4) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE 1: Resulting user plane processing is completed before the next step is performed.
5) shall include the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in this clause;
b) if end-to-end security is requested for the call, the <anyExt> element with the <preconfigured-group-id> element set to the preconfigured group identity as determined in this clause; and
c) the <call-participants-criterias> element in the <anyExt> element as determined in step 5)/b) in clause 17.4.6.1; and
6) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response for the SIP INVITE request, and the SIP final response has not yet been sent to the inviting MCPTT client the controlling MCPTT function:
1) shall generate a SIP 200 (OK) response to the SIP INVITE request as specified in the clause 6.3.3.2.3.2 before continuing with the rest of the steps;
2) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
3) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
NOTE 2: Resulting media plane processing is completed before the next step is performed.
4) shall include the application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-calling-group-id> element set to the adhoc group identity as determined in this clause;
b) if end-to-end security requested for the call, the <anyExt> element with the <preconfigured-group-id> element set to the preconfigured group identity as determined in this clause; and
c) the <call-participants-criterias> element in the <anyExt> element as determined in step 5)/b) in clause 17.4.6.1; and
5) shall send a SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3 Adhoc group call release
|
This clause describes the originating, and terminating call release controlling MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.1 Originating Procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.1.1 Adhoc group call release initiated by the controlling MCPTT function
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.1.1.1 SIP BYE request for releasing MCPTT session
|
When the MCPTT session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCPTT function shall execute the procedures in clause 17.4.6.2 and then follow the procedures in clause 6.3.3.1.5 with the clarifications given below for the clause 6.3.8.1 that:
1) the condition "minimum number of affiliated MCPTT group members is not present" is not applicable;
If there is no outstanding MCPTT adhoc group emergency alert exist on this adhoc group, the controlling MCPTT function shall delete the adhoc group and its associated information.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.1.2 Adhoc group call leave initiated by the controlling MCPTT function
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.1.2.1 SIP BYE request for releasing MCPTT client from MCPTT session
|
When an MCPTT client needs to be removed from the MCPTT session (e.g. user no longer meeting the criteria), the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
After successful in removing the MCPTT client from the MCPTT session, the controlling MCPTT function may generate a notification to the MCPTT clients, which have subscribed to the conference event package that an MCPTT user has been removed from the MCPTT session, as specified in clause 6.3.3.4 and send the SIP NOTIFY request to the MCPTT client according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.3.2 Terminating Procedures
|
Upon receiving a SIP BYE request the controlling MCPTT function:
1) if the adhoc group call is to be released based on the release policies as specified in clause 6.3.8.1, shall follow the procedures as specified in clause 17.4.6.2;
2) if the adhoc group call is release based on user migration, may inform the remaining participants by generating a SIP MESSAGE for notification of redirection according clase 6.3.3.1.x, and send the SIP MESSAGE accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]; and
3) shall follow the procedures as specified in clause 6.3.3.2.4.
If the MCPTT session for group call needs to be released as per the procedures specified in clause 6.3.3.2.4 and if there is no outstanding MCPTT adhoc group emergency alert exist on this adhoc group, the controlling MCPTT function shall delete the adhoc group and its associated information.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.4 Adhoc group call rejoin
|
This clause describes the originating, and terminating call rejoin controlling MCPTT function procedures.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.4.1 Call rejoin procedures using on-demand session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.4.1.1 Terminating procedures
|
Upon receipt of a SIP INVITE request that includes an MCPTT session identity of an ongoing MCPTT session in the Request-URI 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 INVITE 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 404 (Not Found) response if the MCPTT adhoc group call represented by the MCPTT session identity in Request-URI is not present;
3) shall determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not, reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
4) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if:
a) an Accept-Contact header field does not include the g.3gpp.mcptt media feature tag; or
b) 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";
5) shall determine the MCPTT ID of the calling user;
6) shall perform the actions on receipt of an initial SIP INVITE request as described in clause 6.3.3.2.2;
7) if the user identified by the MCPTT ID is no longer meeting the criteria if the adhoc group participants are determined using criteria while establishing adhoc group call, shall return a SIP 403 (Forbidden) response with the warning text set to "188 user is not allowed to participate in adhoc group call" in a Warning header field as specified in clause 4.4;
8) if the user identified by the MCPTT ID is not affiliated to the MCPTT adhoc group ID associated with the MCPTT session identity as specified in clause 6.3.6, shall return 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;
9) shall generate a SIP 200 (OK) response as specified in the clause 6.3.3.2.3.2;
10) shall include in the SIP 200 (OK) response an SDP answer to the SDP offer in the incoming SIP INVITE request as specified in the clause 6.3.3.2.1;
11) shall interact with media plane as specified in 3GPP TS 24.380 [5] clause 6.3;
NOTE : Resulting media plane processing is completed before the next step is performed.
12) shall send the SIP 200 (OK) response towards the inviting MCPTT client according to 3GPP TS 24.229 [4];
13) shall generate a notification to the MCPTT clients, which have subscribed to the conference event package that the inviting MCPTT User has joined in the MCPTT group call, as specified in clause 6.3.3.4; and
14) shall send a SIP NOTIFY request to each MCPTT client according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5 Adhoc group call participants modify
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5.0 General
|
This clause describes the terminating ad hoc group call modification procedures in terms of (criteria for) the participant list.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5.1 Modification of the participant list or criteria for the participant list procedures using on-demand session
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5.1.1 Terminating procedures
|
In the procedures in this clause:
1) MCPTT ID in an incoming SIP re-INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) MCPTT ID in an incoming SIP re-INVITE request refers to the MCPTT ID of the MCPTT user to be invited to a call from the "uri" attribute with the "method" SIP URI parameter set to the value "INVITE" of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body of the incoming SIP re-INVITE request, if any; and
3) MCPTT ID in an incoming SIP re-INVITE request refers to the MCPTT ID of the MCPTT user to be removed from a call from the "uri" attribute with the "method" SIP URI parameter set to the value "BYE" of the <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body of the incoming SIP re-INVITE request, if any.
Upon receipt of a SIP re-INVITE request for an MCPTT session identifying an on-demand MCPTT adhoc group session, 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 re-INVITE 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 determine if the media parameters are acceptable and the MCPTT speech codec is offered in the SDP offer and if not reject the request with a SIP 488 (Not Acceptable Here) response and skip the rest of the steps;
3) if the originating user identified by the MCPTT ID is not authorised to modify (criteria for) the participant list of adhoc group session if the <allow-to-modify-adhoc-group-call-participants-info > element of the <actions> element of a <rule> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the originating MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "false", shall send a SIP 403 (Forbidden) response with the warning text set to: "190 user is not authorised to initiate modify adhoc group call participants" in a Warning header field as specified in clause 4.4 and skip the rest of the steps below;
4) if:
a) the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users to be invited to a call or the MCPTT ID of the MCPTT users to be removed from a call exists in the incoming SIP re-INVITE request:
i) shall check if the number of existing call participants and newly inviting MCPTT users is within the configured limit as specified in the <max-no-participants> element of the <adhoc-group-call> element of the <anyExt> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]). If not within the configured limit, shall send a SIP 403 (Forbidden) response including warning text set to "189 maximum number of allowed adhoc group participants exceeded" in a Warning header field as specified in clause 4.4 and shall skip the rest of the steps;
ii) shall determine the members to invite to the adhoc group session or remove from the adhoc group session based on the local policy and:
A) if the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users to be invited to a call exists in the incoming SIP re-INVITE request, shall consider each entry of the MCPTT users to be invited to the adhoc group session; or
B) if the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT user to be removed from a call exists in the incoming SIP re-INVITE request, shall consider the each entry of the MCPTT users to be removed from the adhoc group session;
iii) if the determined members in step ii) above are to be invited to the adhoc group session, shall be invited to the adhoc group session, as specified in clause 17.4.2.1.1;
iv) if the determined members in step ii) above are to be removed from the adhoc group session, shall be removed from the adhoc group session, as specified in clause 17.4.3.1;
v) shall consider all the invited members as implicitly affiliated to the adhoc group and remove the affiliation of the user who are removed from the adhoc group session;
b) the <call-participants-criterias> element in <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body exists in the incoming SIP re-INVITE request, shall perform the operations described in clause 17.4.6.1 using the <call-participants-criterias> element;
5) shall generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
6) shall include in the SIP 200 (OK) response an SDP answer according to 3GPP TS 24.229 [4] with the clarifications specified in clause 6.3.3.2.1;
7) shall include the "norefersub" option tag in a Supported header field according to IETF RFC 4488 [22];
8) shall include the "tdialog" option tag in a Supported header field according to IETF RFC 4538 [23];
9) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the controlling MCPTT function;
10) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag;
b) the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
c) the isfocus media feature tag; and
11) shall send the SIP 200 (OK) response towards the MCPTT client according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5.2 Call participants modify procedures initiated by participating MCPTT function
|
This clause describes the procedure to handle the notification from the participating MCPTT function about user meeting or no longer meeting the criteria to be added to or removed from the ongoing adhoc group session.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.5.2.1 Terminating procedures
|
Upon receiving a:
- "SIP MESSAGE request to add user to adhoc group call notification for controlling MCPTT function"; or
- "SIP MESSAGE request to remove user from adhoc group call notification for controlling MCPTT function";
the controlling MCPTT function:
1) if the incoming SIP MESSAGE request does not contain an application/resource-lists+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "187 can't determine the adhoc group participants" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
2) shall identify the adhoc group on which the session is ongoing matching the identity of the adhoc group with the value of the <mcptt-request-uri> element set to the adhoc group identity. If unable to determine, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "195 can't determine the adhoc group" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
3) shall generate and send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4];
4) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the <resp-type> element set to a value of "adhoc-group-call-add-participants-request":
a) if the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users meeting the specified criteria exists in the incoming SIP MESSAGE request, shall consider each entry of the MCPTT users meeting the specified criteria to be invited to the ongoing adhoc group session if not already invited and:
i) the user with the MCPTT ID was not manually removed from the adhoc group session as described in clause 17.2.6; or
ii) the user with the MCPTT ID has not left the adhoc group session as described in clause 17.2.4:
b) shall include the users to be invited to the ongoing adhoc group session into the adhoc group;
c) if the adhoc group session is ongoing, shall invite each of the MCPTT users determined above to the adhoc group session, as specified in clause 17.4.2.1.1; and
d) shall consider all the invited members as implicitly affiliated to the adhoc group; and
5) if the received SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the <resp-type> element set to a value of "adhoc-group-call-remove-participants-request":
a) if the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users who are meeting the specified criteria are no longer meeting the specified criteria exists in the incoming SIP MESSAGE request, shall consider each entry of the MCPTT users to be removed from the ongoing adhoc group session if the MCPTT ID was not manually invited to the adhoc group session as described in clause 17.2.6;
b) shall remove the users to be released from the ongoing adhoc group session from the adhoc group; and
c) if the adhoc group session is ongoing, shall remove each of the MCPTT users determined above from the adhoc group session, as specified in clause 17.4.3.1.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.6 Adhoc group call participants determination
|
This clause describes the procedure to determine the participants to be invited to the adhoc group session. Based on local policy, the participants to be invited to the adhoc group session may be determined on the controlling MCPTT function or by means of getting the user lists from the participating MCPTT functions serving users based on the criteria for determining the participants to be invited for adhoc group sessions, and notifying the participating MCPTT function about the release of an adhoc group session to stop determining the users based on criteria.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.6.1 Call participants determination procedures
|
When the controlling MCPTT function needs to determine the MCPTT users meeting the specified criteria, it may determine them, based on local policy on the controlling MCPTT function. Additionally, the controlling MCPTT function may create a list of terminating participating MCPTT functions from which users are to be determined to be involved in an adhoc group session. For each terminating participating MCPTT function in the list, the controlling MCPTT function:
1) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
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 targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include a P-Asserted-Identity header field set to the public service identity of 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-Asserted-Service header field according to IETF RFC 6050 [9];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the adhoc group identity; and
b) an <anyExt> element containing:
i) a <call-participants-criterias> element containing the value as received in the incoming SIP INVITE request, or modified based on local policy; and
ii) a <req-type> element set to a value of "get-userlist-adhoc-group-call-request"; and
6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
On receiving a SIP 4xx response a SIP 5xx response or a SIP 6xx response to the SIP MESSAGE request, the controlling MCPTT function shall consider the user served by the terminating participating MCPTT function are not available and remove from the created list of terminating participating MCPTT functions.
NOTE 6: Based on implementation the controlling MCPTT function can reattempt again before removing from the created list of terminating participating MCPTT functions.
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
On receipt of a "SIP MESSAGE request to get userlist for adhoc group call response for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the <resp-type> element set to a value of "get-userlist-adhoc-group-call-response" and an <mcptt-request-uri> matching the adhoc group identity included in the sent SIP MESSAGE request the MCPTT controlling function:
1) if the application/resource-lists+xml MIME body with the MCPTT ID of the MCPTT users meeting the specified criteria exists in any of the incoming SIP MESSAGE requests shall consider each entry of the MCPTT users meeting the specified criteria to be invited to the adhoc group session. If an MCPTT ID appears multiple times the controlling MCPTT function shall only send one SIP INVITE request for this MCPTT ID;
1a) shall consider MCPTT users participating in the adhoc group session to be removed from the adhoc group session, if their MCPTT ID is not included in the application/resource-lists+xml MIME body of the MCPTT users meeting the specified criteria in any of the incoming SIP MESSAGE requests;
1b) store the MCPTT ID, and if present the functional alias of the users participating in the adhoc group session; and
2) shall generate and send the SIP 200 (OK) response to the received SIP MESSAGE according to rules and procedures of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.4.6.2 Call participants determination stop procedures
|
When the controlling MCPTT function needs to stop determining the MCPTT users meeting the specified criteria, then for each terminating participating MCPTT function in the created list, the controlling MCPTT function:
1) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
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 targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
3) shall include a P-Asserted-Identity header field set to the public service identity of 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-Asserted-Service header field according to IETF RFC 6050 [9];
5) shall include an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-request-uri> element set to the adhoc group identity; and
b) an <anyExt> element containing:
i) the <req-type> element set to a value of "adhoc-group-call-release-notification-request";
6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4]; and
7) shall delete the list of terminating participating MCPTT functions from which users are to be determined to be involved in an adhoc group session.
Upon receipt of SIP 2xx responses to the outgoing SIP MESSAGE requests, the controlling MCPTT function shall follow the procedures specified in 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.5 Extension of application/resource-lists +xml MIME type
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.5.1 Introduction
|
The present clause describes an extension of the application/resource-lists+xml MIME body specified in IETF RFC 4826 [99].
The functional alias extension is used to indicate per-user functional alias association for the enties in the resource list.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
17.5.2 Schema
|
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttResLists:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttResLists="urn:3gpp:ns:mcpttResLists: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/resource-lists MIME body refers to namespaces using prefixes specified in table 17.5.2-1.
Table 17.5.2-1: Assignment of prefixes to namespace names in the application/pidf+xml MIME body
Prefix
Namespace
mcpttResLists
urn:3gpp:ns:mcpttResLists:1.0
NOTE: The "urn:ietf:params:xml:ns:resource-lists" namespace is the default namespace so no prefix is used for it in the application/resource-lists MIME body.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18 Remote emergency floor request trigger
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1 General
|
Clause X specifies the MCPTT client, participating MCPTT function and controlling MCPTT function procedures for a remote emergency floor request trigger.
In the procedures clause X:
- the term "requesting MCPTT user" is used to refer to the user who sends a trigger for a remote emergency floor request;
- the term "remote MCPTT user" is used to refer to the user who is sent a trigger for a remote emergency floor request; and
- the term "targeted call" is used to refer to the emergency group call or to the emergency private call in which the remote emergency floor request is triggered.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1.1 Client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1.1.1 Client originating procedure
|
Upon receiving a request from the requesting MCPTT user to send a remote emergency floor request trigger to the MCPTT user who has initiated an ongoing emergency group call or emergency private call, the MCPTT client:
1) if the <allow-trigger-remote-floor-request> 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 trigger a remote emergency floor request; and
b) shall skip the rest of the steps of the present clause;
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the following clarifications:
a) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9];
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> element set to the MCPTT group identity of the targeted MCPTT group, if the requesting clients triggers an emergency remote floor resquest on the remote client for an ongoing emergency group call; and
ii) an <anyExt> element containing:
A) the <req-type> element set to a value of "emergency-remote-floor-request-trigger"; and
B) the <functional-alias-URI> element set to the URI of the selected functional alias for the requesting user, if the MCPTT originating client has activated functional aliases and an active functional alias is to be included in the request;
e) shall include 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 requesting MCPTT user; and
3) shall send the SIP MESSAGE request towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Upon receipt of a SIP 200 (OK) response to the sent SIP MESSAGE request, should indicate to the requesting MCPTT user the success of the transmission of the emergency remote floor request trigger.
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 transmission of the emergency remote floor request trigger.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1.1.2 Client terminating procedure
|
Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger for terminating client", the MCPTT client:
1) shall determine that the targeted communication is a group call if the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request contains an <mcptt-calling-group-id> element set to an MCPTT group identity, otherwise shall determine that the targeted communication is a private call;
2) if the targeted communication is a group call and if there no ongoing emergency group call for the MCPTT group identified by the MCPTT group ID contained in the <mcptt-calling-group-id> element of the received application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "197 targeted emergency group call is not ongoing" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
3) if the targeted communication is a private call and if there is no ongoing emergency private call between the MCPTT client and the MCPTT user identified by the MCPTT user ID contained in the <mcptt-calling-user-id> element of the received application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "198 targeted emergency private call is not ongoing" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
4) if the MCPTT emergency state of the MCPTT client is not set, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "199 remote user is not in emergency state" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
5) shall generate a SIP 200 (OK) response and send the SIP 200 (OK) response to the terminating participating MCPTT function; and
6) shall trigger a floor resquest for the targeted communication, according to the procedures in 3GPP TS 24.380.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1.2 Participating MCPTT function procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
18.1.2.1 Originating procedures
|
Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger 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 requesting 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 requesting user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if the <allow-trigger-remote-floor-request> 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) with the warning text set to "200 user not authorised to trigger an emergency remote floor request" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
5) shall determine the public service identity of the controlling MCPTT function associated with the group identity contained in the <mcptt-request-uri> element of the received application/vnd.3gpp.mcptt-info+xml MIME body if that element contains an MCPTT group ID, or the public service identity of the controlling MCPTT function associated with the emergency private call for the targeted MCPTT user;
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the 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 of 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 copy the contents of the application/resource-lists+xml MIME body of the received SIP MESSAGE request into the outgoing SIP MESSAGE request;
10) shall set the <mcptt-calling-user-id> element of the <mcptt-Params> element of the <mcpttinfo> element to the MCPTT ID of the requesting user determined in step 2) above;
11) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
12) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
13) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
14) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request; and
15) shall send the SIP MESSAGE request as specified to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response 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
|
18.1.2.2 Terminating procedures
|
Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger 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, 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 determine that the targeted communication is a group call if the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request contains an <mcptt-calling-group-id > element set to an MCPTT group identity, otherwise shall determine that the targeted communication is a private call;
5) if the targeted communication is a group call and if there no ongoing emergency group call for the MCPTT group identified by the MCPTT group ID contained in the <mcptt-calling-group-id> element of the received application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "197 targeted emergency group call is not ongoing" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
6) if the targeted communication is a private call and if there is no ongoing emergency private call between the MCPTT client and the MCPTT user identified by the MCPTT user ID contained in the <mcptt-calling-user-id> element of the received application/vnd.3gpp.mcptt-info+xml MIME body, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "198 targeted emergency private call is not ongoing" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
7) if the MCPTT emergency state of the MCPTT client is not set, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response with the warning text set to "199 remote user is not in emergency state" in a Warning header field as specified in clause 4.4 and shall skip the remaining steps;
8) if according to local policy the received emergency remote floor request trigger shall not be accepted by the MCPTT client, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) and shall skip the remaining steps;
9) shall generate an outgoing SIP MESSAGE request as specified in clause 6.3.2.2.11;
10) 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;
11) 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: and
12) 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
|
18.1.3 Controlling MCPTT function procedures
|
Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger 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) if according to local policy the emergency remote floor request trigger is not authorized for the remote user or for the targeted call, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) with the warning text set to "200 user not authorised to trigger an emergency remote floor request" in a Warning header field as specified in clause 4.4, and not continue with the rest of the steps in this clause;
3) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
4) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
5) shall include 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];
6) 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) if the <mcptt-request-uri> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body included in the received SIP MESSAGE request contains an MCPTT group identity, shall set the <mcptt-calling-group-id> to that MCPTT group identity; 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;
7) 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.
8) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
9) 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
10) 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.
Annex A (informative):
Signalling flows
A.0 General
The flows in this Annex are only for the purposes of illustration and are not guaranteed to be up-to-date.
A.1 Group regrouping flow
A.1.1 General
This clause describes how a temporary group call as the result of a group regroup operation is established.
A.1.2 Use case description
The police and a private security company cooperate during a fair. A temporary prearranged group is created as specified in TS 24.481 [31] to allow the policemen and security personal to communicate.
The temporary group consists of two groups of policemen and a group of security personal from the private security company. One of the groups of policemen is called in from another town. A dispatcher from the police creates the temporary group. The dispatcher is added to the group of policemen hosted by the controlling MCPTT function A.
Table A.1.2-1 shows the group coding details.
Table A.1.2-1: Group coding details
MCPTT group identity
Hosted by
Group type
MCPTT group members
mcptt-group-A-B@mcptt-op.gov
controlling MCPTT function A
Temporary group
mcptt-group-A1@mcptt-op.gov
mcptt-group-B@mcptt-city1.net
mcptt-group-A2@mcptt-op.gov
mcptt-group-A1@mcptt-op.gov
controlling MCPTT function A
Prearranged group
mcptt-id-A2@mcptt-op.gov
mcptt-group-B@mcptt-city1.net
non-controlling MCPTT function B
Prearranged group
mcptt-id-B@mcptt-city1.net
mcptt-group-A2@mcptt-op.gov
non-controlling MCPTT function A
Prearranged group
mcptt-id-A3@mcptt-op.gov
For readability reasons all prearranged groups have only one member. Table A.1.2-1 shows the group member coding details.
Table A.1.2-2: Group member coding details
MCPTT ID of group member
Registered public user identity
MCPTT client name
IP address
audio / floor control port number
(NOTE 2)
mcptt-id-A1@mcptt-op.gov
sip:userA1@ims-op.net
MCPTT client A1
5555::aaa:bbb:ccc:eee
3456 / 3457
mcptt-id-A2@mcptt-op.gov
sip:userA2@ims-op.net
MCPTT client A2
5555::aaa:ccc:aaa:bbb
26456 / 26457
(NOTE 1)
mcptt-id-A3@mcptt-op.gov
sip:userA3@ims-op.net
MCPTT client A3
5555::bbb:aaa:ccc:aaa
25644 / 25645
mcptt-id-B@mcptt-city1.net
sip:userB@ims-op.net
MCPTT client B
5555::baa:abb:ddd:ccc
62122 / 62122
NOTE 1: A pre-established session is used and the IP address and port numbers of the participating MCPTT function A2 is used.
NOTE 2: The IP address is the same as for the registered contact.
Each MCPTT user is served by a different MCPTT function. Table A.1.2-3 shows the Participating MCPTT functions coding details.
Table A.1.2-3: Participating MCPTT functions coding details
Functional entity
Public service identity
IP address
audio / floor control
port number
participating MCPTT function A1
sip:pf-A1.ims-op.net
5555::aaa:bbb:ccc:eef
7890 / 7891
participating MCPTT function A2
sip:pf-A2.ims-op.net
5555::aaa:ccc:aaa:bbb
26456 / 26457
participating MCPTT function A3
sip:pf-A3.ims-op.net
5555::aaa:ccc:aaa:ccc
18412 / 18413
participating MCPTT function B
sip:pf-B.ims-op.net
5555::aaa:bbb:ccc:eef
16412 / 16413
Each group is hosted by a different MCPTT server. Table A.1.2-4 shows the Controlling and non-controlling MCPTT functions coding details.
Table A.1.2-4: Controlling and non-controlling MCPTT functions coding details
Functional entity
Public service identity
MCPTT session identifier
IP address
audio / floor control
port number
controlling MCPTT function A
sip:cf-A.ims-op.net
session@cf-A@ims-op.net
5555::aaa:bbb:ddd:aaa
23124 / 23125
non-controlling MCPTT function A
sip:cf-A2.ims-op.net
sessionA@cf-A2@ims-op.net
5555::aaa:bbb:ddd:eee
12344 / 12345
non-controlling MCPTT function B
sip:cf-B.ims-op.net
sessionB@cf-B@ims-op.net
5555::aaa:bbb:ddd:ddd
34456 / 34457
A.1.3 Signalling flow
The temporary group consists of a group A1 (police), group A2 (police in other town) and a group B (security company in a partner system).
For the mcptt-id-B@mcptt-city1.net the controlling MCPTT function is using the connection model in figure 5.3.2-5.
For the mcptt-id-A3@mcptt-op.gov the controlling MCPTT function is using the connection model in figure 5.3.2-2.
Preconditions:
1) the temporary group mcptt-group-A-B is already created and all members are affiliated to the group;
2) this is not an emergency or imminent peril call;
3) MCPTT client A2 has a pre-established session and the MCPTT services setting for the commencement mode is auto-answer;
4) MCPTT client A3 has no pre-established session and the MCPTT services setting for the commencement mode is manual-answer;
5) MCPTT client has no pre-established session and the MCPTT services setting for queueing the commencement mode is auto-answer;
6) the IMS service provider (ims-op.net) is the same for all groups;
7) the flow does not consider confidentiality and integrity protection; and
8) non-controlling model used between the Primary and the partner is the "untrusted" model.
Figure A.1.3-1 shows the signalling flow when the controlling MCPTT function invites the prearranged groups consisting in the temporary group.
Figure A.1.3-1: Temporary prearranged group call setup
The steps of the flow are as follows:
NOTE 1: The parameters in the coding parts are only those specified in the normative part of the present document. For information about other parameters, see 3GPP TS 24.229 [4].
1) SIP INVITE request (MCPTT client A1 to participating MCPTT function A1) - see example in table A.1.3-1
Upon receiving a request from an MCPTT user A1 to establish an MCPTT temporary group session the MCPTT client A1 sends a SIP INVITE request towards the participating MCPTT function A1 according to 3GPP TS 24.229 [4].
Table A.1.3-1: SIP INVITE request (MCPTT client A1 to participating MCPTT function A1)
INVITE sip: pf-A1.ims-op.net SIP/2.0
Accept-Contact: *;+g.3gpp.mcptt;require;explicit,+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt;require;explicit
P-Preferred-Service:urn:urn-7:3gpp-service.ims.icsi.mcptt
Supported: timer
Session-Expires: 3600;refresher=uac
Contact: <sip:[5555::aaa:bbb:ccc:eee]>;g.3gpp.mcptt;g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Preferred-Identity:<sip:userA1@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ccc:eee
m=audio 3456 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2
a=maxptime:20
i=speech
m=application 3457 udp mcptt
a=fmtp:MCPTT mc_queueing;mc_implicit_request
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1—
Request-URI: Contains the public service identity of the participating MCPTT function serving the MCPTT user.
Accept-Contact: Contains the g.3gpp.mcptt feature tag.
P-Preferred-Service: Contains the ICSI for MCPTT.
Contact: Contains the registered contact and the g.3gpp.mcptt feature tag.
P-preferred-Identity: Contains the public user identity of the MCPTT user.
mcptt-info: The application/vnd.3gpp.mcptt-info+xml contains the <mcptt-Params> element with the <session-type> element set to "prearranged" and the <mcptt-request-uri> element set to "mcptt-group-T@mcptt-op.gov".
SDP offer: Contains a media-level section for the MCPTT speech media stream and a media-level section for the media-floor control entity indicating that of floor requests is supported ("mc:queueing") and that the SIP INVITE request is an implicit floor request ("mc_implicit_request").
2) SIP INVITE request (participating MCPTT function A1 to controlling MCPTT function A) - see example in table A.1.3-2
Upon receiving of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "prearranged", the participating MCPTT function authorizes the MCPTT user to initiate the prearranged group call and since the MCPTT user is authorized, the participating MCPTT function A1 forwards the SIP INVITE request according to 3GPP TS 24.229 [4].
Table A.1.3-2: SIP INVITE request (participating MCPTT function A to controlling MCPTT function A)
INVITE sip: cf-A.ims-op.net SIP/2.0
Accept-Contact:
P-Asserted-Service:
Supported:
Session-Expires:
Contact:
P-Asserted-Identity:<sip:userA1@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ccc:eef
m=audio 7890 RTP/AVP 97
a=
a=
i=
m=application 7891 udp mcptt
a=
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-group-T@mcptt-city1.gov</>
<mcptt-calling-user-id>mcptt-id-A1@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Updated to include the public service identifier of the MCPTT server owning the mcptt-group-T@mcptt-city1.gov.
mcptt-info: The application/vnd.3gpp.mcptt-info+xml is updated to include the MCPTT ID of the MCPTT user in the <mcptt-calling-user-id> element. The participating MCPTT function A1 determines the MCPTT-ID using the public user identity to locate the binding formed during service authorisation.
SDP offer: The SDP offer is updated to include the IP address and port numbers of the participating MCPTT function.
3) HTTP GET request (controlling MCPTT function A to GMS A)
Upon receipt of the "SIP INVITE request for controlling MCPTT function of an MCPTT group" the controlling MCPTT functions fetches the group document mcptt-group-T@mcptt-op.gov from the GMS A.
4) HTTP 200 response (GMS A to controlling MCPTT function A)
The GMS A returns the mcptt-group-T@mcptt-op.gov group document and the document indicates that this is a temporary group consisting of mcptt-group-A1@mcptt-op.gov, mcptt-group-B@mcptt-city1.net and mcptt-group-A2@mcptt-op.gov.
5) HTTP GET request (controlling MCPTT function A to GMS A)
Since the mcptt-id-A1@mcptt-op.gov is affiliated to the mcptt-group-A1@mcptt-op.gov the controlling MCPTT function fetches the group document from GMS A by means of a HTPP GET request as described in 3GPP TS 24.481 [31].
6) HTTP 200 response (GMS A to controlling MCPTT function B)
The GMS A returns the mcptt-group-A1@mcptt-op.gov group document with the list of group members in a HTTP 200 response as described in 3GPP TS 24.481 [31].
The controlling MCPTT function verifies that the mcptt-id-A1@mcptt-op.gov is authorized to initiate a prearranged group call.
The following steps describe the invitation of the group member mcptt-id-A@mcptt-op.gov using a pre-established session between the participating MCPTT function A2 and MCPTT client A2. Other members can be invited using the same method or using on-demand session signalling.
7) SIP INVITE request (controlling MCPTT function A to participating MCPTT function A2) - see example in table A.1.3-7
The controlling MCPTT function sends an initial SIP INVITE request towards the participating MCPTT function A2 according to 3GPP TS 24.229 [4].
Table A.1.3-7: SIP INVITE request (controlling MCPTT function A to participating MCPTT function A2)
INVITE sip: pf-A2.ims-op.net SIP/2.0
Accept-Contact: *;+g.3gpp.mcptt;require;explicit,+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt;require;explicit
P-Asserted-Service: urn:urn-7:3gpp-service.ims.icsi.mcptt
Supported:timer
Session-Expires:3600
Contact: <sip:session@cf-A@ims-op.net:66350>;g.3gpp.mcptt;isfocus;g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Asserted-Identity:<sip:cf-a@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:aaa
m=audio 23124 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2
a=maxptime:20
i=speech
m=application 23125 udp mcptt
a=fmtp:MCPTT mc_queueing;
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-id-A2@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
<mcptt-calling-user-id>userA1@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Contains the public service identity of the participating MCPTT function A2 associated to the MCPTT user mcptt-id-A2@mcptt-op.gov.
Contact: Contains the MCPTT session identity.
P-Asserted-Identity: Contains the public service identity of the controlling MCPTT function A.
mcptt-info Is copied from the received INVITE request and updated to include the "mcptt-id-A2@mcptt-op.gov" in the <mcptt-request-uri> element and mcptt-group-T@mcptt-op.gov in the <mcptt-calling-group-id> element.
SDP offer: The SDP offer is based on the received SDP offer where the IP address and port numbers are replaced with the IP address and port numbers of the controlling MCPTT function. The media-level section for the media-floor control entity is indicating that queueing of floor requests is supported ("mc:queueing").
8) SIP 200 (OK) response (participating MCPTT function A2 to controlling MCPTT function A) - see example in table A.1.3-8
The participating MCPTT function detects that there is a pre-established session to the MCPTT client A2 where negotiated MCPTT speech media stream parameters and media-floor control entity 'fmtp' attributes matches the incoming SIP INVITE request and that the MCPTT service setting for commencement mode is set to "auto-answer".
The participating MCPTT function A2 sends a SIP 200 (OK) response to the controlling MCPTT function A according to 3GPP TS 24.229 [4].
Table A.1.3-8: SIP 200 (OK) response (participating MCPTT function A2 to controlling MCPTT function A)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uac
Require: timer
P-Asserted-Identity:<sip:userA2@ims-op.net>
Contact: <sip:[5555::aaa:ccc:aaa:bbbb]>; g.3gpp.mcptt;
Supported: tdialog, norefersub, explicitsub, nosub
P-Answer-State:Unconfirmed
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:ccc:aaa:bbbb
m=audio 26456 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=maxptime:20
i=speech
m=application 26457 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-called-party-id>mcptt-id-A2@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1—
P-Asserted-Identity: Contains a public user identity of the sip: userA2@ims-op.net.
Contact: Contains a URI that identifies the session in the participating MCPTT function A2.
P-Answer-State: Contains the value "Unconfirmed" to indicate that the participating MCPTT function A2 sent this on behalf of the MCPTT A2.
SDP answer: The SDP answer is based on the received SDP offer and is updated to IP address and port numbers of the participating MCPTT function A2. The media-floor control entity 'fmtp' attributes includes the "mc_queueing" to indicate that queueing is supported.
9) SIP ACK request (controlling MCPTT function A to participating MCPTT function A2)
The controlling MCPTT function A acknowledge the SIP 200 (OK) response by means of the SIP ACK request.
10) MCPC Connect message (participating MCPTT function to MCPTT client B)
Since the MCPTT client B has a pre-established session the participating MCPTT function B uses the pre-established session to invite the MCPTT client B by means of a MCPC Connect messages as described in 3GPP TS 24.380 [5] annex A.
11) MCPC Acknowledgement message (MCPTT client B to participating MCPTT B)
The MCPTT client B acceptes the invitation and sends an MCPC Acknowledge message as as described in 3GPP TS 24.380 [5] annex A.
12) SIP 200 (OK) response (controlling MCPTT function A to participating MCPTT function A1) - see example in table A.1.3-12
Upon receiving the SIP 200 (OK) response from the participating MCPTT function A2, the controlling MCPTT function A interacts with the media plane as specified in 3GPP TS 24.380 [5] clause 6.3 and sends the SIP 200 (OK) towards the participating MCPTT function A1 according to 3GPP TS 24.229 [4].
NOTE 2: When more than one MCPTT user is invited (not done in this example) then when receiving additional SIP 200 (OK) responses from other participating MCPTT functions, the controlling MCPTT function sends the SIP ACK request towards the other participating MCPTT functions and interacts with the media plane as specified in clause 6.3 i.e. there is no SIP signalling sent towards the MCPTT client A1.
NOTE 3: If there more than one user in the group, the 200 (OK) response is not sent if the acknowledged timeout value for the group is running if some members of the group are marked as <on-network-required> as specified in 3GPP TS 24.481 [31], and responses are not received from those members.
Table A.1.3-12: SIP 200 (OK) response (controlling MCPTT function A to participating MCPTT function A1)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uac
Require: timer
P-Asserted-Identity:<sip:cf-A.ims-op.net>
Contact: <sip:[5555::aaa:bbb:ddd:bbbb]>; +g.3gpp.mcptt;+g.3gpp.icsi-ref; isfocus
Supported: tdialog, norefersub, explicitsub, nosub
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:bbbb
m=audio 23124 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2
a=maxptime:20
i=speech
m=application 23125 udp mcptt
a=fmtp:MCPTT mc_queueing;mc_implicit_request
P-Asserted-Identity: Contains the public user identifier identifying the controlling MCPTT function.
Contact: Contains the MCPTT session identifier and the g.3gpp.icsi-ref and isfocus media feature tags.
SDP answer: Contains the SDP answer to the SDP offer received from the participating MCPTT function A2 updated with the IP address and port numbers of the controlling MCPTT function. The media-level section for the media-floor control entity acknowledges that queueing is supported ("mc_queueing") and that the SIP INVITE request is accepted as an implicit floor request.
13) SIP 200 (OK) response (participating MCPTT function A to MCPTT client A) - see example in table A.1.3-13
The participating MCPTT function A1 interacts with the media plane as specified in 3GPP TS 24.380 [5] clause 6.4 and sends the SIP 200 (OK) response towards the MCPTT client A1.
Table A.1.3-13: SIP 200 (OK) response (participating MCPTT function A to MCPTT client A1)
SIP/2.0 200 OK
Session-Expires:
Require:
P-Asserted-Identity:
Contact:
Resouce-Share: media-sharing; session-initiator; rules="k1::UL"; timestamp=55688
Priority-Share:allowed
Supported: tdialog
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:ccc:aaa:bbb
m=audio 7890 RTP/AVP 97
a=
a=
a=
m=application 7891 udp mcptt
a=
Resource-Share: Contains a new sharing key along with indication that MCPTT speech media can be shared in the uplink (UL) direction. The value "k1" is the key that P-CSCF can use to identify media streams towards MCPTT client A1 that can share media.
Priority-Share: The Priority-Share header field is set to "allowed" indicating that priority sharing can be applied by IMS.
SDP answer: Contains the SDP answer received from the controlling MCPTT function updated with the IP address and port numbers of the participating MCPTT function.
14)-15) SIP ACK request (MCPTT client A1 to controlling MCPTT function A via participating MCPTT function A1)
The MCPTT client A1 acknowledges the receipt of the SIP 200 (OK) response by means of a SIP ACK request. The ACK request is forwarded by the participating MCPTT function A1 to the controlling MCPTT function A.
16) SIP INVITE request (controlling MCPTT function A to non-Controlling MCPTT function C) - see example in table A.1.3-16
Since the GMS storing the group document of the "mcptt-group-B@mcptt-city1.net" is not available to the controlling MCPTT function A, the controlling MCPTT function A decides to use the non-controlling MCPTT function connectivity model (see figure 5.3.2-5) and sends a SIP INVITE request towards the MCPTT server hosting "mcptt-group-B@mcptt-city1.net" according to 3GPP TS 24.229 [4].
Table A.1.3-16: SIP INVITE request (controlling MCPTT function A to non-Controlling MCPTT function B)
INVITE sip:cf-B.ims-op.net SIP/2.0
Accept-Contact: *;+g.3gpp.mcptt;require;explicit,+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt;require;explicit
P-Asserted-Service:urn:urn-7:3gpp-service.ims.icsi.mcptt
Supported:timer
Session-Expires:3600
Contact: <sip:session@cf-A@ims-op.net:66350>;g.3gpp.mcptt;isfocus;g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Asserted-Identity:<sip:cf-a@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:aaa
m=audio 23124 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2
a=maxptime:20
i=speech
m=application 23125 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-group-B@mcptt-city1.net</>
<mcptt-calling-user-id>userA1@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Contains the public service identity of the MCPTT server hosting the "mcptt-group-B@mcptt-city1.net".
Contact: Contains the MCPTT session identity.
mcptt-info: Is copied from the received INVITE request and updated to include the "mcptt-group-B@mcptt-city1.net" in the <mcptt-request-uri> element and mcptt-group-T@mcptt-op.gov in the <mcptt-calling-group-id> element.
SDP offer: Is based on the received SDP offer where the IP address and port numbers are replaced with the IP address and port numbers of the controlling MCPTT function. The media-level section for the media-floor control entity is indicating that queueing is supported ("mc:queueing").
17) HTTP GET request (controlling MCPTT function A to GMS B)
Since mcptt-group-B@mcptt-city1.net is hosted by the non-controlling MCPTT function B the group document is fetched from GMS B.
The group document are fetched by means of a HTPP GET request as described in 3GPP TS 24.481 [31].
18) HTTP 200 response (GMS B to controlling MCPTT function B)
The GMS B returns the mcptt-group-B@mcptt-city1.net group document with the list of group members in a HTTP 200 response as described in 3GPP TS 24.481 [31].
The following steps describes the invitation of one group member, mcptt-id-B@mcptt-city1.net, using an on-demand session between the participating MCPTT function B and MCPTT client B. Other members can be invited using the same method or using pre-established session.
19) SIP INVITE request (non-controlling MCPTT function B to participating MCPTT function B) - see example in table A.1.3-19
The non-controlling MCPTT function B invites the MCPTT user "mcptt-id-B@mcptt-city1.net" to the session by sending and SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [4].
Table A.1.3-19: SIP INVITE request (non-Controlling MCPTT function B to participating MCPTT function B)
INVITE sip: pf-B.ims-op.net SIP/2.0
Accept-Contact:
P-Asserted-Service:
Supported:
Session-Expires:
Contact: <sip:sessionB@cf-B@ims-op.net:45678>;g.3gpp.mcptt; isfocus; g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Asserted-Identity:<sip:cf-b@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:ddd
m=audio 34456 RTP/AVP 97
a=
a=
a=
i=
m=application 34457 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-id-B@mcptt-city1.net</>
<mcptt-calling-user-id>mcptt-id-A@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Contact: Contains a new MCPTT session identity and can be used by the members to rejoin the session.
NOTE 4: The MCPTT session identity received from the controlling MCPTT function A cannot be used since when a member of group mcptt-group-B@mcptt-city1.net rejoins the session, the member shall rejoin the session in the non-controlling MCPTT function B and not the session in the controlling MCPTT function A.
P-Asserted-Identity: Contains the public service identity of the non-controlling MCPTT function B.
mcptt-info: The identity of the invited MCPTT user mcptt-id-B@mcptt-city1.net is added.
SDP offer: The SDP offer is a copy of the received SDP offer updated with the IP address and port numbers of the non-controlling MCPTT function B.
20) SIP 183 (Session Progress) response (participating MCPTT function B to non-Controlling MCPTT function B) - see example in table A.1.3-20
The participating MCPTT function B sends a SIP 183 (Session Progress) response towards the non-controlling MCPTT function B according to 3GPP TS 24.229 [4].
Table A.1.3-20: SIP 183 (Session Progress) response (participating MCPTT function B non-Controlling MCPTT function B)
SIP/2.0 183 Session Progress
P-Asserted-Identity:
Contact: <sip:[5555::aaa:bbb:ccc:eef]>;+g.3gpp.mcptt;,+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Answer-State:Unconfirmed
P-Answer-State: Contains the "Unconfirmed" indication acknowledging the automatic commencement mode.
21) SIP INVITE request (participating MCPTT function B to MCPTT client B) - see example in table A.1.3-21
The participating MCPTT function B sends the SIP INVITE request towards the MCPTT client B according to 3GPP TS 24.229 [4].
Table A.1.3-21: SIP INVITE request (participating MCPTT function B to MCPTT client B)
INVITE sip: userB@ims-op.net SIP/2.0
Accept-Contact:
P-Asserted-Service:
Supported:timer;tdialog
Session-Expires:refresher;uac
Contact:
Resouce-Share: media-sharing; session-receiver; rules="k2::UL"; timestamp=55750
Priority-Share:allowed
P-Asserted-Identity:<sip:cf-b@ims-op.net>
Answer-Mode:Auto
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ccc:eef
m=audio 16412 RTP/AVP 97
a=
a=
a=
i=
m=application 16413 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-id-B@mcptt-city1.net</>
<mcptt-calling-user-id>userA1@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Contains the public user identity of the mcptt-id-B@mcptt-city1.net.
Resource-Share: Contains a new sharing key along with indication that MCPTT speech media can be shared in the uplink (UL) direction. The value "k2" is the key that P-CSCF can use to identify media streams towards MCPTT client A2 that can share media.
Priority-Share: The Priority-Share header field is set to "allowed" indicating that priority sharing can be applied by IMS.
Answer-Mode: The MCPTT service setting is "auto-answer" so the participating MCPTT function includes the value "auto" in the Answer-Mode header field.
SDP offer: The SDP offer is a copy of the received SDP offer updated with the IP address and port numbers of the participating MCPTT function B.
22) SIP 200 (OK) response (non-controlling MCPTT function B to controlling MCPTT function A) - see example in table A.1.3-22
Upon receipt of the first SIP 200 (OK) response from the participating MCPTT function B serving the invited MCPTT user B in the prearranged group mcptt-group-C@mcptt-city1.net, the non-controlling MCPTT function interact with the media plane as specified in 3GPP TS 24.380 [5] and sends the SIP 200 (OK) response towards the controlling MCPTT function A in accordance with 3GPP TS 24.229 [4].
NOTE 6: The non-controlling function translates the SIP 183 (Session Progress) response with a P-Answer-State header field set to "Auto" to a SIP 200 (OK) response only if the non-controlling function supports media-buffering otherwise a SIP 183 (Session Progress) response is sent.
Table A.1.3-22: SIP 200 (OK) response (non-controlling MCPTT function B to controlling MCPTT function A)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uac
Require: timer
P-Asserted-Identity:<sip:cf-B.op.net>
Contact: <sip:[5555::aaa:bbb:ddd:ddd]>; g.3gpp.mcptt;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
Supported: tdialog, norefersub, explicitsub, nosub
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:ddd
m=audio 34456 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=maxptime:20
i=speech
m=application 34457 udp mcptt
a=fmtp:MCPTT mc_queueing
P-Asserted-Identity Contains a public service identity identifying the non-controlling MCPTT function B.
Contact Contains a contact address and the media feature tags g.3gpp.mcptt and g.3gpp.icsi-ref.
SDP Contains the SDP answer to the SDP offer received from the controlling MCPTT function A. The media-level section for the media-floor control entity acknowledges that queueing is supported ("mc_queueing").
NOTE 5: The SDP answer is based on the capabilities of the non-controlling MCPTT function and not based on the SIP 200 (OK) response received from the participating MCPTT function.
23) SIP ACK request (controlling MCPTT function A to MCPTT client B via non-controlling MCPTT function B and participating MCPTT function B)
The controlling MCPTT function acknowledges the receipt of the SIP 200 (OK) response by means of a SIP ACK request.
24)-25) SIP 200 (OK) response (MCPTT client B to non-controlling MCPTT function B via participating MCPTT function B) - see example in table A.1.3-24
Upon receiving the SIP INVITE request the MCPTT client B accepts the invitation, interacts with the media plane as specified in 3GPP TS 24.380 clause 6.2 and sends the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Table A.1.3-24: SIP 200 (OK) response (MCPTT client B to non-controlling MCPTT function B via participating MCPTT function B)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uas
Require: timer
Contact:<sip:[5555::baa:abb:ddd:cccc]>;+g.3gpp.mcptt;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt"
P-Asserted-Identity:<sip:userB@ims-op.net>
Supported: tdialog, norefersub, explicitsub, nosub
P-Answer-State:Confirmed
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::baa:abb:ddd:cccc
m=audio 62122 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=maxptime:20
i=speech
m=application 62123 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-called-party-id>mcptt-id-B@mcptt-city1.net</>
</mcptt-Params>
</mcpttinfo>
--boundary1—
Contact: Contains the registered contact and the g.3gpp.mcptt feature tag.
P-Answer-State: Contains the value "Confirmed" to indicate that the MCPTT client B sent the response.
SDP answer: The received SDP offer is accepted and updated with the IP address and port numbers of the MCPTT client B. The MCPTT client B confirms that queueing of floor requests are supported in the 'fmtp' attribute "mc_queueing".
The participating MCPTT function B updates the IP address and port numbers with the IP address and port numbers of the participating MCPTT function B.
26)-27) SIP ACK request (non-controlling MCPTT function B to MCPTT client B via participating MCPTT function B)
The non-controlling MCPTT function acknowledges the receipt of the SIP 200 (OK) response by means of a SIP ACK request.
28) SIP INVITE request (controlling MCPTT function A to non-controlling MCPTT function A) – see example in table A.1.3-28
Since the GMS storing the group document of the "mcptt-group-A2@mcptt-op.gov" is not available to the controlling MCPTT function A, the controlling MCPTT function A decides to use the non-controlling MCPTT function connectivity model (see figure 5.3.2-2) and sends a SIP INVITE request towards the MCPTT server hosting "mcptt-group-A2@mcptt-op.gov" in accordance with 3GPP TS 24.229 [4].
Table A.1.3-28: SIP INVITE request (controlling MCPTT function A to non-Controlling MCPTT function A)
INVITE sip: cf-A2.ims-op.net SIP/2.0
Accept-Contact: *;+g.3gpp.mcptt;require;explicit,+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt;require;explicit
P-Asserted-Service:urn:urn-7:3gpp-service.ims.icsi.mcptt
Supported:timer
Session-Expires:3600
Contact: <sip:session@cf-A@ims-op.net:66350>;g.3gpp.mcptt;isfocus;g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Asserted-Identity:<sipcf-a@ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:aaa
m=audio 23124 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2
a=maxptime:20
i=speech
m=application 23125 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-group-A2@mcptt-op.gov</>
<mcptt-calling-user-id>userA1@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Contains the public service identity of the MCPTT server hosting the "mcptt-group-A2@mcptt-op.gov".
Contact: Contains the MCPTT session identity.
mcptt-info: Is copied from the received INVITE request and updated to include the "mcptt-group-A2@mcptt-op.gov" in the <mcptt-request-uri> element and mcptt-group-T@mcptt-op.gov in the <mcptt-calling-group-id> element.
SDP offer: Is based on the received SDP offer where the IP address and port numbers are replaced with the IP address and port numbers of the controlling MCPTT function. The media-level section for the media-floor control entity is indicating that queueing is supported ("mc:queueing").
29) HTTP GET request (controlling MCPTT function A to GMS B)
Since mcptt-group-A@mcptt-city1.net is hosted by the non-controlling MCPTT function A the group document is fetched from GMS A2.
The group document is fetched by means of a HTPP GET request as described in 3GPP TS 24.481 [31].
30) HTTP 200 response (GMS B to controlling MCPTT function B)
The GMS B returns the mcptt-group-A2@mcptt-op.gov group document with the list of group members in a HTTP 200 response as described in 3GPP TS 24.481 [31].
The following steps describes the invitation of one group member, mcptt-id-A@mcptt-op.gov, using an on-demand session between the participating MCPTT function B and MCPTT client B. Other members can be invited using the same method or using pre-established session.
31) SIP INVITE request (non-controlling MCPTT function A to participating MCPTT function A3) – see example in table A.1.3-31
The non-controlling MCPTT function A invites the MCPTT user mcptt-id-A3@mcptt-op.gov to the session by sending and SIP INVITE request towards the terminating network in accordance with 3GPP TS 24.229 [4].
Table A.1.3-31: SIP INVITE request (non-Controlling MCPTT function A to participating MCPTT function A3)
INVITE sip: pf-A3.ims-op.net SIP/2.0
Accept-Contact:
P-Asserted-Service:
Supported:
Session-Expires:
Contact: <sessionA@cf-A2@ims-op.net61234>;g.3gpp.mcptt; isfocus; g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
P-Asserted-Identity:<sip:cf-A2.ims-op.net>
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:eee
m=audio 12344 RTP/AVP 97
a=
a=
a=
i=
m=application 12345 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-id-A3@mcptt-op.gov</>
<mcptt-calling-user-id>mcptt-id-A@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Contact: Contains a new MCPTT session identity and can be used by the members to rejoin the session.
NOTE 7: The MCPTT session identity received from the controlling MCPTT function A cannot be used since when a member of group mcptt-group-A2@mcptt-op.gov rejoins the session, the member shall rejoin the session in the non-controlling MCPTT function A and not the session in the controlling MCPTT function A.
P-Asserted-Identity: Contains the public service identity of the non-controlling MCPTT function A.
mcptt-info: The identity of the invited MCPTT user mcptt-id-A3@mcptt-op.gov is added.
SDP offer: The SDP offer is a copy of the received SDP offer updated with the IP address and port numbers of the non-controlling MCPTT function A.
32) SIP INVITE request (participating MCPTT function A3 to MCPTT client A3) – see example in table A.1.3-32
The participating MCPTT function A3 sends the SIP INVITE request towards the MCPTT client A3 according to 3GPP TS 24.229 [4].
Table A.1.3-32: SIP INVITE request (participating MCPTT function A3 to MCPTT client A3)
INVITE sip: userA3@ims-op.net SIP/2.0
Accept-Contact:
P-Asserted-Service:
Supported:timer;tdialog
Session-Expires:refresher;uac
Contact:
Resouce-Share: media-sharing; session-receiver; rules="k3::UL"; timestamp=32651
Priority-Share:allowed
P-Asserted-Identity:<sip:cf-A2.ims-op.net>
Answer-Mode:Manual
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:ccc:aaa:ccc
m=audio 18412 RTP/AVP 97
a=
a=
a=
i=
m=application 18413 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-request-uri>mcptt-id-A3@mcptt-op.gov</>
<mcptt-calling-user-id>mcptt-id-A@mcptt-op.gov</>
<mcptt-calling-group-id>mcptt-group-T@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1--
Request-URI: Contains the public user identity of the userA3@ims-op.net.
Resource-Share: Contains a new sharing key along with indication that MCPTT speech media can be shared in the uplink (UL) direction. The value "k3" is the key that P-CSCF can use to identify media streams towards MCPTT client A3 that can share media.
Priority-Share: The Priority-Share header field is set to "allowed" indicating that priority sharing can be applied by IMS.
Answer-Mode: The MCPTT service setting is "manual-answer" so the participating MCPTT function includes the value "Manual" in the Answer-Mode header field.
SDP offer: The SDP offer is a copy of the received SDP offer updated with the IP address and port numbers of the participating MCPTT function B.
33)-34) SIP 200 (OK) response to the SIP INVITE request (MCPTT client A3 to non-controlling MCPTT function A) – see example in table A.1.3-33
Upon receiving the SIP INVITE request the MCPTT client A3 accepts the invitation, interacts with the media plane as specified in 3GPP TS 24.380 clause 6.2 and sends the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4].
Table A.1.3-33: SIP 200 (OK) response (MCPTT client A3 to non-controlling MCPTT function via participating MCPTT function A3)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uas
Require: timer
Contact:<sip:[5555::bbb:aaa:ccc:aaa]>;+g.3gpp.mcptt;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt"
P-Asserted-Identity:<sip:userA3@ims-op.net>
Supported: tdialog, norefersub, explicitsub, nosub
P-Answer-State:Confirmed
Content-Type: multipart/mixed;boundary="boundary1"
--boundary1
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::baa:abb:ddd:cccc
m=audio 25644 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=maxptime:20
i=speech
m=application 25644 udp mcptt
a=fmtp:MCPTT mc_queueing
--boundary1
Content-Type: application/vnd.3gpp.mcptt-info+xml
Content-Length: (…)
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</>
<mcptt-called-party-id>mcptt-id-A3@mcptt-op.gov</>
</mcptt-Params>
</mcpttinfo>
--boundary1—
Contact: Contains the registered contact, the g.3gpp.mcptt feature tag and the g.3gpp.icsi-ref media feature tag with the IMS communication service MCPTT.
P-Answer-State: Contains the value "Confirmed" to indicate that the MCPTT client sent the response.
SDP answer: The received SDP offer is accepted and updated with the IP address and port numbers of the MCPTT client A3. The MCPTT client A3 confirms that queueing of floor requests are supported in the 'fmtp' attribute "mc_queueing".
The participating MCPTT function A3 updates the IP address and port numbers with the IP address and port numbers of the participating MCPTT function A3.
35)-36) SIP ACK request (non-controlling MCPTT function A to MCPTT client A3 via participating MCPTT function A3.
The non-controlling MCPTT function A acknowledges the receipt of the SIP 200 (OK) response to the INVITE request by means of a SIP ACK request.
37) SIP 200 (OK) response to the SIP INVITE request (non-controlling MCPTT function A to controlling MCPTT function A) – see example in table A.1.3-37
Upon receipt of the first SIP 200 (OK) response from the participating MCPTT function A3 serving the invited MCPTT user A3 in the prearranged group mcptt-id-A3@mcptt-op.gov, the non-controlling MCPTT function A interact with the media plane as specified in 3GPP TS 24.380 [5] and sends the SIP 200 (OK) towards the controlling MCPTT function A in accordance with 3GPP TS 24.229 [4].
Table A.1.3-37: SIP 200 (OK) response (non-controlling MCPTT function A to controlling MCPTT function A)
SIP/2.0 200 OK
Session-Expires:3600;refresher=uac
Require: timer
P-Asserted-Identity:<sip:cf-B.ims-op.net>
Contact: <sip:[5555::aaa:bbb:ddd:eee]>;+g.3gpp.mcptt;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mcptt
Supported: tdialog, norefersub, explicitsub, nosub
Content-Type: application/sdp
Content-Length: (…)
c=IN IP6 5555::aaa:bbb:ddd:eee
m=audio 12344 RTP/AVP 97
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes=2
a=maxptime:20
i=speech
m=application 12345 udp mcptt
a=fmtp:MCPTT mc_queueing
P-Asserted-Identity Contains a public service identity identifying the non-controlling MCPTT function A3.
Contact Contains a contact address and the media feature tags g.3gpp.mcptt and g.3gpp.icsi-ref.
SDP Contains the SDP answer to the SDP offer received from the controlling MCPTT function A. The media-level section for the media-floor control entity acknowledged that queueing is supported ("mc_queueing").
NOTE 8: The SDP answer is based on the capabilities of the non-controlling MCPTT function and not based on the SIP 200 (OK) response received from the participating MCPTT function.
38) SIP ACK request (controlling MCPTT function A to non-controlling MCPTT function A.
The controlling MCPTT function A acknowledges the receipt of the SIP 200 (OK) response to the INVITE request by means of a SIP ACK request.
Annex B (normative):
Timers
B.1 General
The following tables give a brief description of the timers used in the present document.
For the on-network timers described in the present document, the following timer families are used:
- TNGx: Timer oN-network Group call x
For the off-network timers described in the present document, the following timer families are used:
- TFGx: Timer oFf-network Group call x
- TFPy: Timer oFf-network Private call y
- TFBz: Timer oFf-network Broadcast group call z
where x, y and z represent numbers.
B.2 On-network timers
B.2.1 Timers in the controlling MCPTT function
The table B.2.1-1 provides a description of the timers used by the controlling MCPTT function, specifies the timer values, describes the reason for starting of the timer, normal stop and the action on expiry.
Table B.2.1-1: controlling MCPTT function timers
Timer
Timer value
Cause of start
Normal stop
On expiry
TNG1 (acknowledged call setup timer)
(NOTE 1)
Obtained from the group document in the <on-network-timeout-for-acknowledgement-of-required-members> element as specified in 3GPP TS 24.481 [31].
On reception of a SIP INVITE request to start a group session where the group document contains <on-network-required> group members as specified in 3GPP TS 24.481 [31].
On receipt of all SIP 200 (OK) responses to all SIP INVITE requests for <on-network-required> group members as specified in 3GPP TS 24.481 [31].
Either proceed with the set-up of the call or abandon the call.
TNG2
(in-progress emergency group call timer)
(NOTE 2)
Obtained from the <group-time-limit> element of the <emergency-call> element of the <on-network> element of the service configuration document as specified in 3GPP TS 24.484 [50].
On reception of a SIP INVITE request or SIP re-INVITE request that initiates an MCPTT emergency group call.
On acceptance of a request to cancel the in-progress emergency state of a group.
Cancels the in-progress emergency state of the group and return the session and/or call to normal priority level.
TNG3 (group call timer).
(NOTE 1).
Set to the value of the <on-network-maximum-duration> element from the group document.
On reception of a SIP INVITE request to start a group session after retrieval of the group document from the group management server.
For a temporary group call, when merging active group calls into a temporary group call.
When splitting a temporary group all into independent active calls
When the last MCPTT client has left the session.
When a temporary group call is split into independent active calls.
For active group calls, when merging them into a temporary group call.
Release the group call.
NOTE 1: More than one instance of this timer can be running in the controlling MCPTT function, each instance associated with a specific group call.
NOTE 2: More than one instance of this timer can be running in the controlling MCPTT function, each instance associated with a specific in-progress emergency state of a single group
B.2.2 Timers in the terminating participating MCPTT function
The table B.2.2-1 provides a description of the timers used by the terminating participating MCPTT function, specifies the timer values, describes the reason for starting of the timer, normal stop and the action on expiry.
Table B.2.2-1: controlling MCPTT function timers
Timer
Timer value
Cause of start
Normal stop
On expiry
TNP1 (call forwarding no answer timer)
(NOTE 1)
Obtained from the user profile document in the <call-forwarding-no-answer-timeout> element as specified in 3GPP TS 24.484 [50]. If the <call-forwarding-no-answer-timeout> element does not exist in the user profile document, the terminating participating MCPTT function shall use a default value of 20 seconds for the timer TNP1.
On reception of a SIP INVITE request to start a private call with the terminating MCPTT user having private call forwarding turned on with the <call-forwarding-condition> "no-answer" as specified in 3GPP TS 24.484 [50].
On receipt of a SIP 200 (OK) response to the SIP INVITE request for the private call to an MCPTT user having private call forwarding turned on with the <call-forwarding-condition> "no-answer" as specified in 3GPP TS 24.484 [50].
Retrieve new target from the <call-forwarding-target> element as specified in 3GPP TS 24.484 [50], and proceed according to 6.3.2.5
NOTE 1: More than one instance of this timer can be running in the controlling MCPTT function, each instance is associated with a specific private call.
B.3 Off-network timers
B.3.1 Timers in off-network group call
B.3.1.1 Basic call control
The table B.3.1.1-1 lists the timers used in basic call control, their start values, their limits, describes the cause of the start, and the action to take on normal stop and on expiry.
Table B.3.1.1-1: Timers in basic call control
Timer
Timer value
Cause of start
Normal stop
On expiry
TFG1 (wait for call announcement)
Default value: 150 millisecond
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a CALL PROBE message.
Reception of a CALL ANNOUNCEMENT message.
Send a CALL ANNOUNCEMENT message.
TFG2 (call announcement)
Calculated. Refer to section 10.2.2.4.1.1.
Commencement of group call.
Restarted every time a CALL PROBE message is received OR CALL ANNOUNCEMENT message is sent or received.
Termination of group call.
When the client Receives a CALL PROBE message or CALL ANNOUNCEMENT message, Re-calculate timer value and restart.
Send a CALL ANNOUNCEMENT message. Re-calculate timer value and restart.
TFG3 (call probe retransmission)
Default value: 40 millisecond
Depends on the characteristic of the D2D (D2D Sidelink period)
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG3" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a CALL PROBE message.
Reception of a CALL ANNOUNCEMENT message.
Or TFG1 Expires.
Or User releases the call.
Send a CALL PROBE message.
TFG4 (waiting for the user)
Default value: 30 seconds
Maximum value: 60 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG4" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Reception of CALL ANNOUNCEMENT message when not participating in the ongoing call.
Reception of User action (Accept or Reject).
Stop incoming call notification.
TFG5 (not present incoming call announcements)
Default value: 30 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG5" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Expiration of TFG4
Or User rejects the call.
Or User releases the call.
-
Reset group call state machine.
TFG6 (Max duration)
Calculated. Refer to section 10.2.2.4.1.2.
Commencement of group call
Termination of group call
Release the group call
B.3.1.2 Call type control
The table B.3.1.2-1 lists the timers used in call type control, their star values, describes the cause of start, and the action to take on normal stop and on expiry.
Table B.3.1.2-1: Call type control
Timer
Timer value
Cause of start
Normal stop
On expiry
TFG11 (emergency end retransmission)
Default value: 1 second
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG11" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a GROUP CALL EMERGENCY END message.
-
Send a GROUP CALL EMERGENCY END message Increment associated counter by 1.
If counter has reached limit, stop the timer.
TFG12 (imminent peril end retransmission)
Default value: 1 second
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFG12" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a GROUP CALL IMMINENT PERIL END message.
-
Send a GROUP CALL IMMINENT PERIL END message Increment associated counter by 1.
If counter has reached limit, stop the timer.
TFG13 (implicit downgrade emergency)
Calculated.
Refer to clause 10.2.3.4.1.1.
Upgrade of the call to emergency group call.
Downgrade of the call.
Downgrade the call.
TFG14 (implicit downgrade imminent peril)
Calculated.
Refer to clause 10.2.3.4.1.2.
Upgrade of the call to imminent peril call.
Downgrade of the call.
Downgrade the call.
B.3.2 Timers in off-network private call
The table B.3.2-1 lists the timers used in off-network private call, their start values, their limits, describes the cause of start, and the action to take on normal stop and on expiry.
Table B.3.2-1: Timers in off-network private call
Timer
Timer value
Cause of start
Normal stop
On expiry
TFP1 (private call request retransmission)
Default value: 40 millisecond
Depends on the characteristic of the D2D (D2D Sidelink period)
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a PRIVATE CALL SETUP REQUEST message.
Reception of a PRIVATE CALL ACCEPT or PRIVATE CALL REJECT message.
Resend PRIVATE CALL SETUP REQUEST message. Increment associated counter by 1.
If counter has reached limit, assume the called client is not available. Terminate call setup.
TFP2 (waiting for user to respond )
Default value: 30 seconds
Maximum value: 60 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP2" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Reception of a PRIVATE CALL SETUP REQUEST message.
User responds to the incoming call notification.
Start TFP7 timer.
Send a PRIVATE CALL REJECT message
TFP3 (private call release retransmission)
Default value: 40 millisecond
Depends on the characteristic of the D2D (D2D Sidelink period)
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP3" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a PRIVATE CALL RELEASE message.
Reception of PRIVATE CALL RELEASE ACK message.
Resend PRIVATE CALL RELEASE message. Increment associated counter by 1.
If counter has reached limit, assume the receiving client is not available anymore. Release the call.
TFP4 (private call accept retransmission)
Default value: 40 millisecond
Depends on the characteristic of the D2D (D2D Sidelink period)
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP4" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a PRIVATE CALL ACCEPT message.
Reception of a PRIVATE CALL ACCEPT ACK message or RTP media.
Resend PRIVATE CALL ACCEPT message. Increment associated counter by 1.
If counter has reached limit, assume the receiving client is not available anymore
Notify call setup failure.
TFP5 (max duration)
Configurable.
Set to the value of "/<x>/OffNetwork/PrivateCall/MaxDuration" leaf node present in the service configuration as specified in 3GPP TS 24.483 [45].
Call establishment.
Call termination.
Terminate the call.
TFP6 (private emergency call cancel retransmission)
Default value: 40 millisecond
Depends on the characteristic of the D2D. (D2D Sidelink period)
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP6" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
When the client sends a PRIVATE EMERGENCY CALL CANCEL message.
Reception of a PRIVATE EMERGENCY CALL CANCEL ACK message.
Resend PRIVATE EMERGENCY CALL CANCEL message. Increment associated counter by 1.
If counter has reached limit, assume the receiving client is not available anymore
Notify call setup failure.
TFP7 (waiting for any message with same call identifier)
Default value: 1 second
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP7" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Rejection of a call OR
Termination of a call OR
Call Failure.
-
Reset the call control state machine.
TFP8 (implicit downgrade)
Configurable.
Default value: 180 seconds
Set to the value of "/<x>/OffNetwork/PrivateCall/CancelTimeout" leaf node present in the service configuration as specified in 3GPP TS 24.483 [45].
TFP9 (waiting for call response message)
Default value: 30 seconds
Maximum value: 60 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFP9" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Expiry of timer TFP1 and CFP1 = upper limit and manual commencement mode.
Reception of PRIVATE CALL ACCEPT or PRIVATE CALL REJECT message.
Start TFP7 timer.
B.3.3 Timers in off-network broadcast call
The table B.3.3-1 lists the timers used in off-network broadcast call, their start values, their limits, describes the cause of start, and the action to take on normal stop and on expiry.
Table B.3.3-1: Timers in off-network broadcast call
Timer
Timer value
Cause of start
Normal stop
On expiry
TFB1 (max duration)
Default value: 300 seconds
Maximum value: 600 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFB1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Start of the broadcast call (terminating UE).
Receive GROUP CALL BROADCAST END message.
Terminate participation in the broadcast call.
TFB2 (broadcast retransmission)
Default value: 3 seconds
Maximum value: 10 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFB2" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Start of the broadcast call (originating UE).
Broadcast call termination.
Send GROUP CALL BROADCAST message.
TFB3 (waiting for the user)
Default value: 30 seconds
Maximum value: 60 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFB3" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Receipt of GROUP CALL BROADCAST message when user response is required.
Response from user.
Terminate incoming call notification.
B.3.4 Timers in off-network emergency alert
The table B.3.4-1 lists the timers used in off-network emergency alert, their start values, their limits, describes the cause of start, and the action to take on normal stop and on expiry.
Table B.3.4-1: Timers in off-network emergency alert
Timer
Timer value
Cause of start
Normal stop
On expiry
TFE1 (emergency alert)
Default value: 30 seconds
Maximum value: 60 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFE1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Receipt of GROUP EMERGENCY ALERT.
Receipt of GROUP EMERGENCY ALERT CANCEL.
Assume end of emergency state, remove associated user from the list.
TFE2 (emergency alert retransmission)
Default value: 5 seconds
Maximum value: 10 seconds
Configurable.
Set to the value of "/<x>/OffNetwork/Timers/TFE2" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
Transmission of GROUP EMERGENCY ALERT.
Transmission of GROUP EMERGENCY ALERT CANCEL.
Transmit GROUP EMERGENCY ALERT.
Annex C (normative):
Counters
C.1 General
The following tables give a brief description of the counters used in the present document.
C.2 Off-network counters
C.2.1 Counters in off-network group call
The table C.2.1-1 lists the counters used in off-network group call, their default upper limits and the action to take upon reaching the upper limit. The counters start at 1.
Table C.2.1-1: Counters in off-network group call
Counter
Upper Limit
Associated timer
Upon reaching the upper limit
CFG11
(emergency end retransmission)
Default value: 5
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFG11" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFG11
Stop timer TFG11.
CFG12 (imminent peril end retransmission)
Default value: 5
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFG12" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFG12
Stop timer TFG12.
C.2.2 Counters in off-network private call
The table C.2.2-1 lists the counters used in off-network private call, their default upper limits and the action to take upon reaching the upper limit. The counters start at 1.
Table C.2.2-1: Counters in off-network private call
Counter
Upper Limit
Associated timer
Upon reaching the upper limit
CFP1
(private call request retransmission)
Default value: 3
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFP1" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFP1
Assume the called client is not available. Terminate call setup.
CFP3 (private call release retransmission)
Default value: 3
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFP3" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFP3
Assume the receiving client is not available anymore. Release the call.
CFP4 (private call accept retransmission)
Default value: 3
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFP4" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFP4
Notify call setup failure.
CFP6 (emergency private call cancel retransmission)
Default value: 3
Configurable.
Set to the value of "/<x>/OffNetwork/Counters/CFP6" leaf node present in the UE initial configuration as specified in 3GPP TS 24.483 [45].
TFP6
Notify emergency call release failure.
Annex D (normative):
Media feature tags and feature-capability indicators used within the current document
D.1 General
This clause describes the media feature tag definitions that are applicable for the 3GPP IM CN Subsystem for the realisation of the Mission Critical Push To Talk (MCPTT) service.
D.2 Definition of media feature tag g.3gpp.mcptt
Media feature tag name: g.3gpp.mcptt
ASN.1 Identifier: 1.3.6.1.8.2.28
Summary of the media feature indicated by this media feature tag: This media feature tag when used in a SIP request or a SIP response indicates that the function sending the SIP message supports Mission Critical Push To Talk (MCPTT) communication.
Values appropriate for use with this media feature tag: Boolean
The media feature tag is intended primarily for use in the following applications, protocols, services, or negotiation mechanisms: This media feature tag is most useful in a communications application, for describing the capabilities of a device, such as a phone or PDA.
Examples of typical use: Indicating that a mobile phone supports the Mission Critical Push To Talk (MCPTT) communication.
Related standards or documents: 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification"
Security Considerations: Security considerations for this media feature tag are discussed in clause 11.1 of IETF RFC 3840 [16].
D.3 Definition of feature-capability indicator g.3gpp.mcptt.ambient-listening-call-release
Feature-capability indicator name: g.3gpp.mcptt.ambient-listening-call-release
Summary of the feature indicated by this feature-capability indicator:
This feature-capability indicator when included in a Feature-Caps header field as specified in IETF RFC 6809 [93] in a SIP INVITE request or a SIP 200 (OK) response to a SIP INVITE request indicates that the MCPTT server is capable of receiving a SIP BYE from an MCPTT client to release an ambient-listening call.
Feature-capability indicator specification reference:
3GPP TS 24.379, http://www.3gpp.org/ftp/Specs/archive/24_series/24.379/
Values appropriate for use with this feature-capability indicator: None
Examples of typical use: Indicating that the MCPTT server can support receiving a SIP BYE from an MCPTT client to release an ambient listening call.
Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of IETF RFC 6809 [93].
Annex E (normative):
ICSI values defined within the current document
E.1 General
This clause describes the IMS communications service identifier definitions that are applicable for the 3GPP IM CN Subsystem for the realisation of the Mission Critical Push To Talk (MCPTT) service.
NOTE: The template has been created using the headers of the table in http://www.3gpp.org/specifications-groups/34-uniform-resource-name-urn-list
E.2 Definition of ICSI value for MCPTT service
E.2.1 URN
urn:urn-7:3gpp-service.ims.icsi.mcptt
E.2.2 Description
This URN indicates that the device has the capabilities to support the mission critical push to talk (MCPTT) service.
E.2.3 Reference
3GPP TS 24 379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification"
E.2.3 Contact
Name: <MCC name>
Email: <MCC email address>
E.2.4 Registration of subtype
Yes
E.2.5 Remarks
None
Annex F (normative):
XML schemas
F.1 XML schema for MCPTT Information
F.1.1 General
This clause defines XML schema and MIME type for MCPTT information.
F.1.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:mcpttInfo:1.0"
xmlns:mcpttinfo="urn:3gpp:ns:mcpttInfo:1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
xmlns:mgktp="urn:3gpp:ns:mcpttGKTP:1.0">
<xs:import namespace="http://www.w3.org/2001/04/xmlenc#"/>
<xs:import namespace="urn:3gpp:ns:mcpttGKTP:1.0"/>
<!-- root XML element -->
<xs:element name="mcpttinfo" type="mcpttinfo:mcpttinfo-Type" id="info"/>
<xs:complexType name="mcpttinfo-Type">
<xs:sequence>
<xs:element name="mcptt-Params" type="mcpttinfo:mcptt-ParamsType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mcptt-ParamsType">
<xs:sequence>
<xs:element name="mcptt-access-token" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="session-type" type="xs:string" minOccurs="0"/>
<xs:element name="mcptt-request-uri" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="mcptt-calling-user-id" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="mcptt-called-party-id" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="mcptt-calling-group-id" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="required" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="emergency-ind" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="alert-ind" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="imminentperil-ind" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="broadcast-ind" type="xs:boolean" minOccurs="0"/>
<xs:element name="mc-org" type="xs:string" minOccurs="0"/>
<xs:element name="floor-state" type="xs:string" minOccurs="0"/>
<xs:element name="associated-group-id" type="xs:string" minOccurs="0"/>
<xs:element name="originated-by" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="MKFC-GKTPs" type="mgktp:singleTypeGKTPsType" minOccurs="0"/>
<xs:element name="mcptt-client-id" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="alert-ind-rcvd" type="mcpttinfo:contentType" minOccurs="0"/>
<xs:element name="gw-mcptt-usage" type="xs:boolean" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="protectionType">
<xs:restriction base="xs:string">
<xs:enumeration value="Normal"/>
<xs:enumeration value="Encrypted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="contentType">
<xs:choice>
<xs:element name="mcpttURI" type="xs:anyURI"/>
<xs:element name="mcpttString" type="xs:string"/>
<xs:element name="mcpttBoolean" type="xs:boolean"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:attribute name="type" type="mcpttinfo:protectionType"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<!-- anyEXT elements – begin -->
<xs:element name="ambient-listening-type" type="mcpttinfo:ambientListeningType"/>
<xs:simpleType name="ambientListeningType">
<xs:restriction base="xs:string">
<xs:enumeration value="remote-init"/>
<xs:enumeration value="local-init"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="release-reason" type="mcpttinfo:releaseReasonType"/>
<xs:simpleType name="releaseReasonType">
<xs:restriction base="xs:string">
<xs:enumeration value="private-call-expiry"/>
<xs:enumeration value="administrator-action"/>
<xs:enumeration value="not selected for call"/>
<xs:enumeration value="call-request-for-listened-to-client"/>
<xs:enumeration value="call-request-initiated-by-listened-to-client"/>
<xs:enumeration value="authentication of the MIKEY-SAKE I_MESSAGE failed"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="request-type" type="mcpttinfo:requestTypeType"/>
<xs:simpleType name="requestTypeType">
<xs:restriction base="xs:string">
<xs:enumeration value="private-call-call-back-request"/>
<xs:enumeration value="private-call-call-back-cancel-request"/>
<xs:enumeration value="group-selection-change-request"/>
<xs:enumeration value="remotely-initiated-group-call-request"/>
<xs:enumeration value="remotely-initiated-private-call-request"/>
<xs:enumeration value="transfer-private-call-request"/>
<xs:enumeration value="functional-alias-status-determination"/>
<xs:enumeration value="forward-private-call-request"/>
<xs:enumeration value="forward-private-call-settings-request"/>
<xs:enumeration value="forward-private-call-settings-response"/>
<xs:enumeration value="fa-group-binding-req"/>
</xs:restriction>
</xs:simpleType>
<!-- The request-type and response-type elements uses the enumeration as values, which cant be extended for new values to be added. Hence the new req-type and resp-type elements are defined and going forward all the new values are added to these element -->
<xs:element name="req-type" type="mcpttinfo:contentType"/>
<xs:element name="resp-type" type="mcpttinfo:contentType"/>
<xs:element name="response-type" type="mcpttinfo:responseTypeType"/>
<xs:simpleType name="responseTypeType">
<xs:restriction base="xs:string">
<xs:enumeration value="private-call-call-back-response"/>
<xs:enumeration value="private-call-call-back-cancel-response"/>
<xs:enumeration value="group-selection-change-response"/>
<xs:enumeration value="remotely-initiated-group-call-response"/>
<xs:enumeration value="remotely-initiated-private-call-response"/>
<xs:enumeration value="transfer-private-call-response"/>
<xs:enumeration value="forward-private-call-response"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="urgency-ind">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="low"/>
<xs:enumeration value="normal"/>
<xs:enumeration value="high"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="time-of-request" type="xs:dateTime"/>
<xs:element name="selected-group-change-outcome" type="mcpttinfo:selectedGroupChangeOutcomeType"/>
<xs:simpleType name="selectedGroupChangeOutcomeType">
<xs:restriction base="xs:string">
<xs:enumeration value="success"/>
<xs:enumeration value="fail"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="affiliation-required" type="xs:boolean"/>
<xs:element name="remotely-initiated-call-outcome" type="mcpttinfo:remotelyInitiatedCallOutcomeType"/>
<xs:simpleType name="remotelyInitiatedCallOutcomeType">
<xs:restriction base="xs:string">
<xs:enumeration value="success"/>
<xs:enumeration value="fail"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="notify-remote-user" type="xs:boolean"/>
<xs:element name="functional-alias-URI" type="mcpttinfo:contentType"/>
<xs:element name="user-requested-priority" type="xs:nonNegativeInteger"/>
<xs:element name="emergency-alert-area-ind" type="xs:boolean"/>
<xs:element name="group-geo-area-ind" type="xs:boolean"/>
<xs:element name="non-acknowledged-user" type="mcpttinfo:contentType"/>
<xs:element name="call-to-functional-alias-ind" type="xs:boolean"/>
<xs:element name="emergency-ind-rcvd" type="mcpttinfo:contentType"/>
<xs:element name="call-transfer-ind" type="xs:boolean"/>
<xs:element name="multiple-devices-ind" type="mcpttinfo:contentType"/>
<xs:element name="transfer-call-outcome" type="mcpttinfo:transferCallOutcomeType"/>
<xs:simpleType name="transferCallOutcomeType">
<xs:restriction base="xs:string">
<xs:enumeration value="success"/>
<xs:enumeration value="fail"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="called-functional-alias-URI" type="mcpttinfo:contentType"/>
<xs:element name="call-forwarding-ind" type="xs:boolean"/>
<xs:element name="forwarding-call-outcome" type="mcpttinfo:forwardingCallOutcomeType"/>
<xs:simpleType name="forwardingCallOutcomeType">
<xs:restriction base="xs:string">
<xs:enumeration value="success"/>
<xs:enumeration value="fail"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="forwarding-immediate-list" type="mcpttinfo:mcpttIdListType"/>
<xs:complexType name="mcpttIdListType">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="entry" type="mcpttinfo:EntryType"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="forwarding-other-list" type="mcpttinfo:mcpttIdListType"/>
<xs:complexType name="EntryType">
<xs:sequence>
<xs:element name="uri-entry" type="xs:anyURI"/>
<xs:element name="display-name" type="xs:string" minOccurs="0"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="forwarding-reason" type="mcpttinfo:forwardingReasonType"/>
<xs:simpleType name="forwardingReasonType">
<xs:restriction base="xs:string">
<xs:enumeration value="immediate"/>
<xs:enumeration value="no-answer"/>
<xs:enumeration value="manual-input"/>
<xs:enumeration value="migrated"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="PrivateCallKMSURI" type="mcpttinfo:PrivateCallKMSURIEntryType"/>
<xs:complexType name="PrivateCallKMSURIEntryType">
<xs:sequence>
<xs:element name="PrivateCallKMSURI" type="mcpttinfo:EntryType"/>
<xs:element name="anyExt" type="mcpttinfo:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="binding-ind" type="xs:boolean"/>
<xs:element name="binding-fa-uri" type="xs:anyURI"/>
<xs:element name="unbinding-fa-uri" type="xs:anyURI"/>
<xs:element name="replaces-header-value" type="xs:string"/>
<xs:element name="transfer-announced-ind" type="xs:boolean"/>
<xs:element name="forwarding-sequence-number" type="xs:nonNegativeInteger"/>
<xs:element name="forwarded-by-mcptt-id" type="xs:anyURI"/>
<xs:element name="forwarded-by-functional-alias" type="xs:anyURI"/>
<xs:element name="forwarding-target-id" type="xs:anyURI"/>
<xs:element name="forwarding-target-is-functional-alias" type="xs:boolean"/>
<!-- These elements can be added under the anyExt element of the mcpttinfo element -->
<xs:element name="ric-app-level-priority" type="xs:string"/>
<xs:element name="ric-commencement-mode" type="xs:string"/>
<xs:element name="remotely-initiated-call-request-ind" type="mcpttinfo:contentType"/>
<xs:element name="forwarding-target-orig-id" type="xs:anyURI"/>
<xs:element name="end-to-end-security" type="xs:boolean"/>
<xs:element name="call-participants-criterias" type="xs:string"/>
<xs:element name="preconfigured-group-id" type="xs:anyURI"/>
<xs:element name="adhoc-grp-emg-alert-grp-ind" type="xs:boolean"/>
<xs:element name="migration-auth-result" type="mcpttinfo:contentType"/>
<xs:element name="partner-mcptt-id" type="mcpttinfo:contentType"/>
<xs:element name="selected-user-profile-index" type="mcpttinfo:selected-user-profile-indexType"/>
<xs:element name="primary-mcptt-id" type="mcpttinfo:contentType"/>
<xs:element name="adhoc-emergency-ind" type="xs:boolean"/>
<xs:element name="adhoc-alert-ind" type="xs:boolean"/>
<xs:element name="adhoc-additional-information" type="xs:string"/>
<xs:element name="adhoc-emergency-ind-rcvd" type="xs:boolean"/>
<xs:element name="adhoc-alert-ind-rcvd" type="xs:boolean"/>
<xs:element name="adhoc-alert-participant-list" type="mcpttinfo:mcpttIdListType"/><xs:element name="adhoc-alert-participant-not-ack-list" type="mcpttinfo:mcpttIdListType"/>
<xs:element name="location-of-functional-alias-URI" type="mcpttinfo:contentType"/>
<xs:element name="connected-functional-alias-URI" type="mcpttinfo:contentType"/>
<!-- anyEXT elements – end -->
<xs:complexType name="selected-user-profile-indexType">
<xs:sequence>
<xs:element name="user-profile-index" type="xs:nonNegativeInteger"/>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:schema>
F.1.3 Semantic
The <mcpttinfo> element is the root element of the XML document. The <mcpttinfo> element can contain subelements.
NOTE 1: The subelements of the <mcpttinfo> are validated by the <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <mcpttinfo> element
If the <mcpttinfo> contains the <mcptt-Params> element then:
1) the <mcptt-access-token>, <mcptt-request-uri>, <mcptt-calling-user-id>, <mcptt-called-party-id>, <mcptt-calling-group-id>, <emergency-ind>, <alert-ind>, <imminentperil-ind>, <originated-by>, <mcptt-client-id>, <functional-alias-URI>, <called-functional-alias-URI>, <non-acknowledged-user>, <multiple-devices-ind>, <associated-group-id>, <group-geo-area-ind>, <migration-auth-result> , <partner-mcptt-id>, <primary-mcptt-id>, <selected-user-profile-index>, <req-type>, <resp-type> and <connected-functional-alias-URI> elements can be included with encrypted content;
2) for each element in 1) that is included with content that is not encrypted:
a) the element has the "type" attribute set to "Normal";
b) if the element is one of the following elements: <mcptt-request-uri>, <mcptt-calling-user-id>, <mcptt-called-party-id>, <mcptt-calling-group-id>, <originated-by>, <functional-alias-URI>, <called-functional-alias-URI>, <non-acknowledged-user>, <associated-group-id>, <partner-mcptt-id>, <primary-mcptt-id>, or <connected-functional-alias-URI>, then the <mcpttURI> element is included;
c) if the element is one of the following elements:<mcptt-access-token>, <mcptt-client-id>, <req-type>, or <resp-type> then the <mcpttString> element is included;
d) if the element is one of the following elements: <emergency-ind>, <alert-ind>, <alert-ind-rcvd>, <imminentperil-ind>, <emergency-ind-rcvd>, <multiple-devices-ind>, or <remotely-initiated-call-request-ind>, or <migration-auth-result>, then the <mcpttBoolean> element is included; and
e) if the element is <selected-user-profile-index>, then the <user-profile-index> element is included; and
3) for each element in 1) that is included with content that is encrypted:
a) the element has the "type" attribute set to "Encrypted";
b) the <xenc:EncryptedData> element from the "http://www.w3.org/2001/04/xmlenc#" namespace is included and:
i) can have a "Type" attribute can be included with a value of "http://www.w3.org/2001/04/xmlenc#Content";
ii) can include an <EncryptionMethod> element with the "Algorithm" attribute set to value of "http://www.w3.org/2009/xmlenc11#aes128-gcm";
iii) can include a <KeyInfo> element with a <KeyName> element containing the base 64 encoded XPK-ID; and
iv) includes a <CipherData> element with a <CipherValue> element containing the encrypted data.
NOTE 2: When the optional attributes and elements are not included within the <xenc:EncryptedData> element, the information they contain is known to sender and the receiver by other means.
If the <mcpttinfo> contains the <mcptt-Params> element then:
1) the <mcptt-access-token> can be included with the access token received during authentication procedure as described in 3GPP TS 24.482 [49];
2) the <session-type> can be included with:
a) a value of "chat" to indicate that the MCPTT client wants to join a chat group call
b) a value of "prearranged" to indicate the MCPTT client wants to make a prearranged group call;
c) a value of "private" to indicate the MCPTT client wants to make a private call;
d) a value of "first-to-answer" to indicate that the MCPTT client wants to make a first-to-answer call;
e) a value of "ambient-listening" to indicate the MCPTT client wants to make an ambient listening call; or
f) a value of "adhoc" to indicate the MCPTT client wants to make an adhoc group call;
3) the <mcptt-request-uri> can be included with:
a) a value set to an MCPTT group ID or temporary MCPTT group ID when the <session-type> is set to a value of "prearranged" or "chat";
b) a value set to the MCPTT ID of the called MCPTT user when the <session-type> is set to a value of "private"; and
c) a value set to the MCPTT ID of the called MCPTT user or MCPTT group ID of adhoc group when the <session-type> is set to a value of "adhoc";
4) the <mcptt-calling-user-id> can be included, set to MCPTT ID of the originating user;
5) the <mcptt-called-party-id> can be included, set to the MCPTT ID of the terminating user;
6) the <mcptt-calling-group-id> can be included to indicate the MCPTT group identity or MCPTT adhoc group identity to the terminating user;
7) the <required> can be included in a SIP 183 (Session Progress) from a non-controlling MCPTT function of an MCPTT group to inform the controlling MCPTT function that the group on the non-controlling MCPTT function has group members in the group document which are marked as <on-network-required>, as specified in 3GPP TS 24.481 [31];
8) the <emergency-ind> can be:
a) set to "true" to indicate that the call that the MCPTT client is initiating is an emergency MCPTT call; or
b) set to "false" to indicate that the MCPTT client is cancelling an emergency MCPTT call (i.e. converting it back to a non-emergency call)
9) the <alert-ind> can be:
a) set to "true" in an emergency call initiation to indicate that an alert to be sent; or
b) set to "false" when cancelling an emergency call which requires an alert to be cancelled also
10) if the <session-type> is set to "chat" or "prearranged":
a) the <imminentperil-ind> can be set to "true" to indicate that the call that the MCPTT client is initiating is an imminent peril group MCPTT call;
11) the <broadcast-ind> can be:
a) set to "true" to indicate that the MCPTT client is initiating a broadcast group call; or
b) set to "false" to indicate that the MCPTT client is initiating a non-broadcast group call;
12) the <mc-org> can be:
a) set to the MCPTT user's Mission Critical Organization in an emergency alert sent by the MCPTT server to terminating MCPTT clients;
13) the <floor-state> can be:
a) set to "floor-idle" if the floor is idle in a non-controlling MCPTT function; or
b) set to "floor-taken" if the floor state in a non-controlling MCPTT function is taken;
14) the <associated-group-id>:
a) if the <mcptt-request-uri> element contains a group identity then this element can include an MCPTT group ID associated with the group identity in the <mcptt-request-uri> element. E.g. if the <mcptt-request-uri> element contains a temporary group identity (TGI), then the <associated-group-id> element can contain the constituent MCPTT group ID;
15) the <originated-by>:
a) can be included, set to the MCPTT ID of the originating user of an MCPTT emergency alert when being cancelled by another authorised MCPTT user;
16) the <MKFC-GKTPs>:
a) contains a group key transport payload carrying one or more MKFC(s) and MKFC-ID(s) as described in3GPP TS 24.481 [31] clause 7.4, to be used for protection of multicast floor control signalling when the UE operates on the network;
17) the <mcptt-client-id>:
a) can be included, set to the MCPTT client ID of the MCPTT client that originated a SIP INVITE request, SIP REFER request, SIP REGISTER request, SIP PUBLISH request or SIP MESSAGE request;
18) the <alert-ind-rcvd>:
a) can be set to "true" and included in a SIP MESSAGE to indicate that the emergency alert or cancellation was received successfully;
18a) void;
18b) void
18a) the <gw-mcptt-usage>
a) can be set to true in a SIP REGISTER or a SIP PUBLISH to indicate to the MCPTT server that the MCPTT client uses a MCPTT gateway UE, which requires that network resources are allocated over Rx, N5 or N33; and
19) the <anyExt> can be included with the following elements:
a) an <ambient-listening-type> element set to:
i) "remote-init" when the listening MCPTT user of an ambient listening call initiates the call; or
ii) "local-init" when the listened-to MCPTT user of an ambient listening call initiates the call;
b) a <release-reason> element set to:
i) "private-call-expiry" when the ambient listening call is release due to the expiry of the private call timer;
ii) "administrator-action" when the ambient listening call is released by an MCPTT administrator;
iii) "not selected for call" when the when a dialog is released with an MCPTT client that was not selected as the terminating client of a first-to-answer call;
iv) "call-request-for-listened-to-client" when there is a call request targeted to the listened-to client;
v) "call-request-initiated-by-listened-to-client" when there is a call request initiated by the listened-to client; or
vi) "authentication of the MIKEY-SAKE I_MESSAGE failed" by a MCPTT client when the signature cannot be verified;
c) a <request-type> element set to:
i) "private-call-call-back-request" when a client initiates a private call call-back request;
ii) "private-call-call-back-cancel-request" when a client initiates a private call call-back cancel request;
iii) "group-selection-change-request" when a client initiates a group selection change request;
iv) "remotely-initiated-group-call-request" when a client initiates a remotely initiated group call request;
v) "remotely-initiated-private-call-request" when a client initiates a remotely initiated private call request;
vi) "transfer-private-call-request" when a client initiates a transfer private call request;
vii) "functional-alias-status-determination" when a client initiates a subscription to FA status determination request;
viii) "forward-private-call-request" when a client initiates a forward private call request; or
ix) "fa-group-binding-req" when a client initiates a request for binding of a functional alias with the MCPTT group(s) for the MCPTT user;
d) a <response-type> element set to:
i) "private-call-call-back-response" when a client responds to a private call call-back request;
ii) "private-call-call-back-cancel-response" when a client responds to a private call call-back cancel request;
iii) "group-selection-change-response" when a client responds to a group selection change request;
iv) "remotely-initiated-group-call-response" when a client responds to a remotely initiated call request;
v) "remotely-initiated-private-call-response" when a client responds to a remotely initiated private call request;
vi) "transfer-private-call-response" when a client responds to a transfer private call request;
vii) "forward-private-call-response" when a client responds to a forward private call request; or
e) an <urgency-ind> element:
i) set to a value of "low", "normal" or "high" to indicate the urgency of a private call call-back request;
f) a <time-of-request> element :
i) set to the date and time at which the private call call-back request was initiated, in the form: "YYYY-MM-DDThh:mm:ss" where:
- YYYY indicates the year;
- MM indicates the month;
- DD indicates the day;
- T indicates the start of the required time section;
- hh indicates the hour;
- mm indicates the minute; and
- ss indicates the second;
g) a <selected-group-change-outcome> element set to:
i) "success" when a client reports that it has successfully changed its selected group as requested by a received group selection change request; or
ii) "fail" when a client reports that it has failed to change its selected group as requested by a received group selection change request;
h) an <affiliation-required> element set to:
i) "true" when received by a client in a group-selection-change-request to indicate that the client needs to affiliate to the specified group;
i) a <remotely-initiated-call-outcome> element set to:
i) "success" when a client reports that it has successfully initiated a call requested by a received remotely initiated call request; or
ii) "fail" when a client reports that it has failed to initiate a call triggered as requested by a received group selection change request;
j) a <notify-remote-user> element set to:
i) "true" when the remote user is to be notified of a remotely initiated call request; or
ii) "false" when the remote user is to be notified of a received remotely initiated call request;
k) a <functional-alias-URI> element set to the value of the functional alias that is used together with the "mcptt-calling-user-id";
l) an <emergency-alert-area-ind> element set to:
i) "true" when the MCPTT client has entered an emergency alert area; or
ii) "false" when the MCPTT client has exited an emergency alert area;
m) a <group-geo-area-ind> element set to:
i) "true" when the MCPTT client has entered a group geographic area; or
ii) "false" when the MCPTT client has exited a group geographic area;
n) one or more <non-acknowledged-user> elements set to the MCPTT IDs of invited members to a group call that have not sent a SIP 200 (OK) response;
o) a <call-to-functional-alias-ind> element set to:
i) "true" when the MCPTT client is using a functional alias to identify the MCPTT IDs of the potential target MCPTT users; or
ii) "false" when the MCPTT client is using MCPTT IDs to identify the potential target MCPTT users;
p) the <emergency-ind-rcvd> element set to:
i) "true" and included in a SIP MESSAGE to indicate that the in-progress emergency cancellation request was received successfully;
q) a <call-transfer-ind> element set to:
i) "true" when the MCPTT client is making a private call as a result of a call transfer; or
ii) "false" when the MCPTT client is making a normal private call;
r) a <transfer-call-outcome> element set to:
i) "success" when a client reports that it has successfully initiated a call requested by a received call transfer request; or
ii) "fail" when a client reports that it has failed to initiate a call triggered as requested by a received call transfer request;
s) a <called-functional-alias-URI> element set to the value of the functional alias to be called;
t) a <call-forwarding-ind> element set to:
i) "true" when the MCPTT client is making a private call as a result of a call forwarding; or
ii) "false" when the MCPTT client is making a normal private call;
u) a <forwarding-call-outcome> element set to:
i) "success" when a client reports that it has successfully initiated a call requested by a received call forwarding request; or
ii) "fail" when a client reports that it has failed to initiate a call triggered as requested by a received call forwarding request;
v) a <forwarding- immediate-list> element containing the details of the history of the immediate call forwardings that have occurred in the same MCPTT call;
w) a <forwarding-other-list> element containing the details of the history of the forwardings because of call forwarding on "no-answer" or "manual-input" forthe same MCPTT call;
x) a <forwarding-reason> element set to:
i) "immediate" for call forwarding immediate;
ii) "no-answer" for call forwarding no answer;
iii) "manual-input" for call forwarding based on manual user input; or
iv) "migrated" for call forwarding due to user migration;
y) a <multiple-devices-ind> element set to:
i) "true" to indicate to the client that multiple clients are registered for the MCPTT user; or
ii) "false" to indicate to the client that no other clients are registered for the MCPTT user;
z) a <binding-ind> element set to:
i) "true" when the user wants to create a binding of a particular functional alias with the specified list of MCPTT groups for the MCPTT client; or
ii) "false" when the user wants to remove a binding of a particular functional alias from the specified list of MCPTT groups for the MCPTT client;
aa) a <binding-fa-uri> element set to:
i) a URI of a functional alias that shall be bound with the specified list of MCPTT groups for the MCPTT client;
ab) a <unbinding-fa-uri> element set to:
i) a URI of a functional alias that shall be unbound from the specified list of MCPTT groups for the MCPTT client;
ac) a <transfer-announced-ind> set to:
i) "true" indicating that the call is part of an announced MCPTT call transfer; or
ii) "false" indicating that the call is not part of an announced MCPTT call transfer;
ad) a<replaces-header-value> element set to the Call-ID SIP header field value, the from-tag, and the to-tag of the MCPTT private call to be transferred. The delimiter between the Call-ID, the from-tag, and the to-tag is the semicolon (;);
ae) a <user-requested-priority> element set to the non-negative integer value requested by the user as priorityAbsence of the <emergency-ind>, <alert-ind> and <imminentperil-ind> in a SIP INVITE or a SIP REFER request indicates that the MCPTT client is initiating a non-emergency private call or non-emergency group call;
af) a <forwarding-sequence-number> element set to the total number of forwardings including that forwarding attempt;
ag) a <forwarded-by-mcptt-id> element set to the MCPTT ID of the MCPTT client to whom a private call has been placed and who has requested that the private call be forwarded either through settings at its participating MCPTT function or through manual user input.
ah) a <forwarded-by-functional-alias> element set to the functional alias received by the MCPTT client to whom a private call has been placed and who has requested that the private call be forwarded either through settings at its participating MCPTT function or through manual user input, if a functional alias was used to call the client;
ai) a <forwarding-target-id> element set to the uri of the target of the forwarding;
aj) a<forwarding-target-is-functional-alias> element set to:
i) "true" to indicate that the target of the forwarding is a functional alias; or
ii) "false" to indicate that the target of the forwarding is a MCPTT ID;
ak) a <forwarding-target-orig-id> element set to the target uri of the forwarding as read from the user profile or entered by the MCPTT user requesting the MCPTT private call forwarding.
al) a<end-to-end-security> element set to:
i) "true" to indicate to determine the preconfigured group from which security related information is used for secure adhoc group call; or
ii) "false" to indicate that not to determine the preconfigured group from which security related information is used for secure adhoc group call;
am) a <call-participants-criterias> element set to the criteria for determining the list of MCPTT users to be called in adhoc group call, or to be included in an adhoc group emergency alert. The delimiter between the criteria is the comma (,);
an) a <preconfigured-group-id> element set to the preconfigured group identity of the preconfigured group from which security related materials can be used by the adhoc group call participants to communicate securely in the adhoc group session;
ao) a <adhoc-grp-emg-alert-grp-ind> element set to:
i) "true" to indicate that the identity of adhoc group used in the adhoc group call setup request is learned during an adhoc group emergency alert procedures;
ao1) a <migration-auth-result> element set to:
i) "true" to indicate that the MCPTT client is authorized to migrate; or
ii) "false" to indicate that the MCPTT client is not authorized to migrate;
ao2) a <partner-mcptt-id> element set to the MCPTT ID of a migrating user in the partner MCPTT system;
ap) a <selected-user-profile-index> element set to the value contained in the "user-profile-index" attribute of the MCPTT user profile selected according to clause 4.2.2.1.2.3 of 3GPP TS 24.484 [50];
aq) a <req-type> element set to:
i) "mc-service-authorisation-notify-request" when a participating MCPTT function in the partner MCPTT system initiates a request to notify about the successful completion of MCPTT user service authorization after migrating to the partner MCPTT system;
ii) "get-userlist-adhoc-group-call-request" when a controlling MCPTT function initiates a request to get userlist for adhoc group call from terminating participating MCPTT function;
iii) "adhoc-group-call-add-participants-request" when a terminating participating MCPTT function initiates a request to add user to adhoc group call notification for controlling MCPTT function;
iv) "adhoc-group-call-remove-participants-request" when a terminating participating MCPTT function initiates a request to remove user from adhoc group call notification for controlling MCPTT function;
v) "adhoc-group-call-release-notification-request" when a controlling MCPTT function initiates a request to stop determining the participant list for terminating participating MCPTT function;
vi) "migration-service-deauthorization-notification" when a participating MCPTT function in the primary MCPTT system initiates a request to notify that an MCPTT client that has been authorized for migration service in the partner MCPTT system is to be deauthorized;
vii) "migration-service-authorization-request" when a participating MCPTT function in the partner MCPTT system sends a migration service authorization request;
viii) "fa-user-status-determination" when a client initiates a subscription to functional alias user status determination request;
ix) "ad-hoc-emergency-alert-participant-criteria-modification" when an MCPTT client sends a request to modify participant criteria for an MCPTT ad hoc emergency alert to a participating MCPTT function or the participating MCPTT function forwards the request to a controlling MCPTT function; or
x) "emergency-remote-floor-request-trigger" when a requesting client sends a trigger to a remote user in emergency to request the floor;
ar) void;
as) a <resp-type> element set to:
i) "get-userlist-adhoc-group-call-response" when a terminating participating MCPTT function responds to get userlist for adhoc group call request;
ii) "migration-service-authorization-response" when a participating MCPTT function in the primary MCPTT system sends a migration service authorization response; or
iii) "ad-hoc-emergency-alert-participant-criteria-modification" when a controlling MCPTT function sends a response to a request to modify participant criteria for an MCPTT ad hoc emergency alert to a participating MCPTT function or the participating MCPTT function forwards the response to an MCPTT client;
at) a <primary-mcptt-id> element set to the MCPTT ID of the user in the primary MCPTT system;
au) void
av) a <adhoc-alert-participant-list> element containing the total list of MC service users who belong to the ad hoc group irrespective if they have acknowledged the ad hoc group emergency alert or not;
aw) a <adhoc-alert-participant-not-ack-list> element containing the list of MC service users who belong to the ad hoc group but have not acknowledged the ad hoc group emergency alert;
ax) a <adhoc-emergency-ind> element set to:
i) set to "true" to indicate that the alert or call that the MCPTT client is initiating is an emergency MCPTT alert or call; or
ii) set to "false" to indicate that the MCPTT client is cancelling an emergency MCPTT alert or call (i.e. converting it back to a non-emergency call);
ay) a <adhoc-alert-ind> element set to:
i) "true" in an adhoc group emergency alert initiation to indicate that an alert to be sent; or
ii) "false" in an adhoc group emergency alert cancellation to indicate that an alert to be cancelled;
az) <adhoc-alert-ind-rcvd> element:
i) can be set to "true" and included in a SIP MESSAGE to indicate that the adhoc group emergency alert or cancellation was received successfully;
ba) <adhoc-emergency-ind-rcvd> element set to:
i) "true" and included in a SIP MESSAGE to indicate that the in-progress adhoc emergency cancellation request was received successfully;
bb) an <adhoc-additional-information> element set to text information included with the adhoc group emergency alert.
bc) a <location-of-functional-alias-URI> element set to a URI of a functional alias that is used to identify the MCPTT clients for which location information is being requested; and
bd) a <connected-functional-alias-URI> element set to the value of the functional alias of the final destination returned by the called MCPTT client in an ad hoc group call.
Absence of the <broadcast-ind> in a SIP INVITE or a SIP REFER request indicates that the MCPTT client is initiating a non-broadcast group call.
Absence of the <floor-state> in a SIP 200 (OK) response from the non-controlling MCPTT function indicates that the floor is idle.
Absence of the <call-to-functional-alias-ind> in a SIP INVITE or a SIP REFER request for a first-to-answer call indicates the use of the MCPTT IDs of the potential target MCPTT users.
Absence of the <call-transfer-ind> in a SIP INVITE or a SIP REFER request for a private call indicates that the call is not caused by a request for call transfer.
Absence of the <call-forwarding-ind> in a SIP INVITE or a SIP REFER request for a private call indicates that the call is not caused by a request for call forwarding.
Absence of the <transfer-announced-ind> in a SIP INVITE or a SIP REFER request for a private call indicates that the call is not part of an announced call transfer.
Absence of the <forwarding-target-is-functional-alias> element in a SIP INVITE, a SIP REFER, or a SIP MESSAGE request indicates that the forwarding target contains an MCPTT ID.
The recipient of the XML ignores any unknown element and any unknown attribute.
F.1.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-info+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.2 XML schema for MBMS usage information
F.2A XML schema for MBS usage information
F.2A.1 General
This clause defines XML schema and MIME type for application/vnd.3gpp.mcptt-mbs-usage-info+xml.
F.2A.2 XML schema
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:mcpttMbsUsage:1.0"
xmlns:mcpttmbs="urn:3gpp:ns:mcpttMbsUsage:1.0">
<!-- the root element -->
<xs:element name="mcptt-mbs-usage-info" type="mcpttmbs:mcptt-mbs-usage-info-Type" id="mbs"/>
<xs:complexType name="mcptt-mbs-usage-info-Type">
<xs:sequence>
<xs:element name="mbs-listening-status" type="mcpttmbs:mbs-listening-statusType" minOccurs="0"/>
<xs:element name="mbs-session-de-announcement-status" type="mcpttmbs:mbs-session-de-announcement-statusType" minOccurs="0"/>
<xs:element name="ue-session-join-notification" type="mcpttmbs:ue-session-join-notificationType" minOccurs="0"/>
<xs:element name="announcement" type="mcpttmbs:announcementTypeParams" minOccurs="0"/>
<xs:element name="version" type="xs:integer"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mbs-listening-statusType">
<xs:sequence>
<xs:element name="mbs-listening-status" type="xs:string"/>
<xs:element name="unicast-listening-status" type="xs:string"/>
<xs:element name="session-id" type="xs:anyURI" minOccurs="0"/>
<xs:element name="general-purpose" type="xs:boolean" minOccurs="0"/>
<xs:element name="mbs-session-id" type="xs:hexBinary" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mbs-session-de-announcement-statusType">
<xs:sequence>
<xs:element name="mbs-session-de-announcement-status" type="xs:string" minOccurs="0"/>
<xs:element name="number-of-reported-sessions" type="xs:integer" minOccurs="0"/>
<xs:element name="deleted-mbs-session-id" type="xs:hexBinary" minOccurs="0"/>
<xs:element name="other-mbs-session-id" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="ue-session-join-notificationType">
<xs:sequence>
<xs:element name="mbs-multicast-joining-status" type="xs:string"/>
<xs:element name="mbs-session-id" type="xs:hexBinary"/>
<xs:element name="session-id" type="xs:anyURI" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="announcementTypeParams">
<xs:sequence>
<xs:element name="mbs-session-info" type="mcpttmbs:mbs-session-infoType" minOccurs="0"/>
<xs:element name="eMBMS-bearer-info" type="mcpttmbs:eMBMS-bearer-infoType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mbs-session-infoType">
<xs:sequence>
<xs:element name="mbs-session-id" type="xs:hexBinary"/>
<xs:element name="mbs-session-mode" type="mcpttmbs:sessionType"/>
<xs:element name="mc-service-group-id" type="xs:integer" minOccurs="0"/>
<xs:element name="frequency" type="xs:unsignedLong" minOccurs="0"/>
<xs:element name="GPMS" type="xs:positiveInteger" minOccurs="0"/>
<xs:element name="mbs-service-areas" type="mcpttmbs:mbs-service-areasType" minOccurs="0"/>
<xs:element name="report-ue-session-join-notification" type="xs:boolean" minOccurs="0"/>
<xs:element name="multicast-mbs-session-related-info" type="mcpttmbs:multicast-mbs-session-related-infoType"/>
<xs:element name="mbs-fsa-id" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="mbs-session-de-announcement-acknowledgement" type="xs:boolean" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="eMBMS-bearer-infoType">
<xs:sequence>
<xs:element name="TMGI" type="xs:hexBinary"/>
<xs:element name="Alternative-TMGI" type="mcpttmbs:Alternative-TMGI-Type" minOccurs="0"/>
<xs:element name="QCI" type="xs:integer" minOccurs="0"/>
<xs:element name="frequency" type="xs:unsignedLong" minOccurs="0"/>
<xs:element name="mbms-service-areas" type="mcpttmbs:mbms-service-areasType" minOccurs="0"/>
<xs:element name="GPMS" type="xs:positiveInteger" minOccurs="0"/>
<xs:element name="report-suspension" type="xs:boolean" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyEXT elements for the eMBMS announcement element – begin -->
<xs:element name="mcptt-mbs-rohc" type="mcpttmbs:emptyType"/>
<!-- empty complex type -->
<xs:complexType name="emptyType"/>
<xs:element name="max-cid" type="mcpttmbs:max-cidType"/>
<xs:simpleType name="max-cidType">
<xs:restriction base="xs:integer">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="16383"/>
</xs:restriction>
</xs:simpleType>
<!-- anyEXT elements for the eMBMS announcement element – end -->
<xs:simpleType name="sessionType">
<xs:restriction base="xs:string">
<xs:enumeration value="multicast"/>
<xs:enumeration value="broadcast"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="Alternative-TMGI-Type">
<xs:sequence>
<xs:element name="Alternative-TMGI-id" type="xs:hexBinary" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="mbs-service-areasType">
<xs:sequence>
<xs:element name="mbs-service-area-id" type="xs:hexBinary" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="mbms-service-areasType">
<xs:sequence>
<xs:element name="mbms-service-area-id" type="xs:hexBinary" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="multicast-mbs-session-related-infoType">
<xs:sequence>
<xs:element name="PlmnId" type="mcpttmbs:tPlmnIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="DNN" type="xs:string" minOccurs="0"/>
<xs:element name="IPInformation" type="mcpttmbs:IPInformationType" minOccurs="0"/>
<xs:element name="MC-ID-ref-SNSSAI" type="xs:string" minOccurs="0"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:simpleType name="tPlmnIdentityFormat">
<xs:restriction base="xs:string">
<xs:pattern value="\d{3}\d{3}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tPlmnIdentity">
<xs:simpleContent>
<xs:extension base="mcpttmbs:tPlmnIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="IPInformationType">
<xs:sequence>
<xs:element name="IPInformationListEntry" type="mcpttmbs:IPInformationListEntryType" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="IPInformationListEntryType">
<xs:choice>
<xs:element name="IPv4Address" type="xs:token"/>
<xs:element name="IPv6Address" type="xs:token"/>
<xs:element name="FQDN" type="xs:anyURI"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<!-- anyEXT elements for the mcptt-mbs-usage-info – begin -->
<xs:element name="mbs-defaultMuSiK-download" type="mcpttmbs:mbs-default-ctrlkey-downloadType"/>
<xs:complexType name="mbs-default-ctrlkey-downloadType">
<xs:sequence>
<xs:element name="group" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="mbs-explicitMuSiK-download" type="mcpttmbs:mbs-explicit-ctrlkey-downloadType"/>
<xs:complexType name="mbs-explicit-ctrlkey-downloadType">
<xs:sequence>
<xs:element name="group" type="xs:anyURI" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbs:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyEXT elements for the mcptt-mbs-usage-info – end -->
</xs:schema>
F.2A.3 Semantic
The <mcptt-mbs-usage-info> element is the root element of the XML document. The <mcptt-mbs-usage-info> element contains the subelements:
1) <mbs-listening-status> contains subelements as specified <mbms-listening-status> in clause F.2.3 with the terminology mapping specified in clause L.3.4;
2) <mbs-session-de-announcement-status>: contains the following subelements:
a) <mbs-session-de-announcement-status>: element is a string used to indicate the MBS sessions intended deletion status:
- The value "deleting" indicates that the MC client UE has decided to stop monitoring the broadcast MBS session or leaves the multicast MBS session.
- The value "not-deleting" indicates that the MC client UE has decided to revoke its decision to stop monitoring the broadcast MBS session or leaves the multicast MBS session.
b) <number-of-reported-sessions>: a hex binary number denoting the total number of occurrences of the <deleted-mbs-session-id> and <other-mbs-session-id> elements reported as part of the MBS session de-announcement status;
c) <deleted-mbs-session-id>: contains a MBS session ID that is being reported as about to be deleted or as no longer about to be deleted; and
d) <other-mbs-session-id>: contains a MBS session ID that is not being reported as about to be deleted or as no longer about to be deleted;
3) <ue-session-join-notification> containing the following elements:
a) <mbs-multicast-joining-status> element contains a string used to indicate the MCPTT join MBS session status:
- The value "ue-session-join" indicates that a MCPTT client joins an MBS session, i.e. the MCPTT client indicates to MCPTT server that such MCPTT client wants to receive multicast data identified by a specific MBS session ID.
- The value "ue-session-leave" indicates that a MCPTT client leaves a MBS session, i.e. the MCPTT client no longer wants to receive multicast data identified by a specific MBS session ID.
b) <mbs-session-id>: element is coded as described in 3GPP TS 23.247 [91] clause 6.5.1. The MBS session ID is used to identify a Multicast/Broadcast MBS session by the 5G system on external interface towards AF and between AF and UE, and towards the UE;
c) <session-id> element contains the value of the URI received in the Contact header field received from the controlling MCPTT function when an on-demand session was established, or from the participating MCPTT function in the Connect message when the session was established over a pre-established session. This element is mandatory if the <mbs-multicast-joining-status> element is not present in the application/vnd.3gpp.mcptt-mms-usage-info+xml MIME body.
4) <announcement> element containing <mbs-session-infoType> and <eMBMS-bearer-infoType>.
a) <mbs-session-infoType> element containing the following elements:
i) <mbs-session-id>: element is coded as described in 3GPP TS 23.247 [91] clause 6.5.1. The MBS session ID is used to identify a Multicast/Broadcast MBS Session by the 5G system on external interface towards AF and between AF and UE, and towards the UE;
ii) <mbs-session-mode>: element is a string used to indicate the service type of the MBS session, either a multicast MBS session or a broadcast MBS session:
iii) <mc-service-group-id>: element is a string used to indicate the MC service group ID associated to the MBS session;
iv) <GPMS> element is a positive integer that gives the number of the media line containing the general purpose MBS subchannel in the application/sdp MIME body attached to the SIP MESSAGE request containing the MBS announcement;
v) <mbs-service-areas>: element is a list of MBS service area IDs for the applicable MBS multicast area as specified in 3GPP TS 23.247 [91] for Service Area Identifier (SAI);
vi) <report-ue-session-join-notification>: element is a boolean with the following meaning:
- True indicates that the MC service server requires a notification from the MC service client once it has joined the multicast MBS session.
- False indicates that the MC service server not requires a notification from the MC service client once it has joined the multicast MBS session; and
vii) <multicast-mbs-session-related-info> that can contain:
- shall contain an optional element specifying a PLMN Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
- shall contain an <IPInformation> element containing (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
- shall contain a <DNN> element (see the MCPTT user profile document in 3GPP TS 24.484 [50]); and
- shall containan a <MC-ID-ref-SNSSAI> element (see the MCPTT user profile document in 3GPP TS 24.484 [50]);
viii) <mbs-fsa-id>: contains the MBS Frequency Selection Area ID. The <mbs-fsa-id> element is coded as described in 3GPP TS 23.247 [91] clause 6.5.4. The MBS Frequency Selection Area (FSA) ID is used for broadcast MBS session to guide the frequency selection of the UE.MBS FSA ID identifies a preconfigured area within, and in proximity to, which the cell(s) announces the MBS FSA ID and the associating frequency. MBS FSA ID and their mapping to frequencies are provided to RAN nodes via OAM;
ix) <frequency>: element containing identification of frequency in case of multi carrier support. The <frequency> element is coded as specified in 3GPP TS 29.468 [42]; and
NOTE 1: In the current release the frequency in the <frequency> element is the same as the frequency used for unicast.
x) <mbs-session-de-announcement-acknowledgement>: element is a boolean with the following meaning:
- True indicates that the MCPTT client is instructed to notify the MCPTT server when it becomes aware of an intended change in the de-announcement status of a listened MBS session.
- False indicates that the MCPTT client is instructed not to notify the MCPTT server if it becomes aware of an intended change in the de-announcement status of a listened MBS session.
b) <eMBMS-bearer-infoType> element as specified in clause F.2.3 <announcement> elements with the following clarifications/exceptions:
i) <Alternative-TMGI>: contains a list of additional alternative TMGI which may be included and used in roaming scenarios;
F.2A.4 IANA registration template
Editor’s note: The MIME type "application/vnd.3gpp.mcptt-mbs-usage-info+xml" as defined in this subclause is to be registered in the IANA registry for Application Media Types based upon the following template. The registration is to be started after completion of release 18.
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-mbs-usage-info+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 18.x.x, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.2.1 General
This clause defines XML schema and MIME type for application/vnd.3gpp.mcptt-mbms-usage-info+xml.
F.2.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:mcpttMbmsUsage:1.0"
xmlns:mcpttmbms="urn:3gpp:ns:mcpttMbmsUsage:1.0">
<!-- the root element -->
<xs:element name="mcptt-mbms-usage-info" type="mcpttmbms:mcptt-mbms-usage-info-Type" id="mbms"/>
<xs:complexType name="mcptt-mbms-usage-info-Type">
<xs:sequence>
<xs:element name="mbms-listening-status" type="mcpttmbms:mbms-listening-statusType"
minOccurs="0"/>
<xs:element name="mbms-suspension-status" type="mcpttmbms:mbms-suspension-statusType"
minOccurs="0"/>
<xs:element name="announcement" type="mcpttmbms:announcementTypeParams" minOccurs="0"/>
<xs:element name="version" type="xs:integer"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyEXT elements for the mbms-listening-status element – begin -->
<xs:element name="mbms-reception-quality" type="xs:integer"/>
<!-- anyEXT elements for the mbms-listening-status element – end -->
<xs:complexType name="mbms-listening-statusType">
<xs:sequence>
<xs:element name="mbms-listening-status" type="xs:string"/>
<xs:element name="session-id" type="xs:anyURI" minOccurs="0"/>
<xs:element name="general-purpose" type="xs:boolean" minOccurs="0"/>
<xs:element name="TMGI" type="xs:hexBinary" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mbms-suspension-statusType">
<xs:sequence>
<xs:element name="mbms-suspension-status" type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="number-of-reported-bearers" type="xs:integer" minOccurs="0" maxOccurs="1"/>
<xs:element name="suspended-TMGI" type="xs:hexBinary" minOccurs="0"/>
<xs:element name="other-TMGI" type="xs:hexBinary" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="announcementTypeParams">
<xs:sequence>
<xs:element name="TMGI" type="xs:hexBinary" minOccurs="1"/>
<xs:element name="QCI" type="xs:integer" minOccurs="0"/>
<xs:element name="frequency" type="xs:unsignedLong" minOccurs="0"/>
<xs:element name="mbms-service-areas" type="mcpttmbms:mbms-service-areasType" minOccurs="0"/>
<xs:element name="GPMS" type="xs:positiveInteger" minOccurs="0"/>
<xs:element name="report-suspension" type="xs:boolean" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyEXT elements for the announcement element – begin -->
<xs:element name="mcptt-mbms-rohc" type="mcpttmbms:emptyType"/>
<!-- empty complex type -->
<xs:complexType name="emptyType"/>
<xs:element name="max-cid" type="mcpttmbms:max-cidType"/>
<xs:simpleType name="max-cidType">
<xs:restriction base="xs:integer">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="16383"/>
</xs:restriction>
</xs:simpleType>
<!-- anyEXT elements for the announcement element – end -->
<xs:complexType name="mbms-service-areasType">
<xs:sequence>
<xs:element name="mbms-service-area-id" type="xs:hexBinary"
minOccurs="1" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<!-- anyEXT elements for the mcptt-mbms-usage-info – begin -->
<xs:element name="mbms-defaultMuSiK-download" type="mcpttmbms:mbms-default-ctrlkey-downloadType"/>
<xs:complexType name="mbms-default-ctrlkey-downloadType">
<xs:sequence>
<xs:element name="group" type="xs:anyURI"
minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="mbms-explicitMuSiK-download" type="mcpttmbms:mbms-explicit-ctrlkey-downloadType"/>
<xs:complexType name="mbms-explicit-ctrlkey-downloadType">
<xs:sequence>
<xs:element name="group" type="xs:anyURI"
minOccurs="1" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttmbms:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyEXT elements for the mcptt-mbms-usage-info – end -->
</xs:schema>
F.2.3 Semantic
The <mcptt-mbms-usage-info> element is the root element of the XML document. The <mcptt-mbms-usage-info> element contains the subelements:
1) <mbms-listening-status> containing the following elements:
a) <mbms-listening-status> element contains a string used to indicate the MCPTT listening status:
- The value "listening" indicates that the MCPTT client now is receiving RTP media packets and floor control messages over the MBMS subchannel in the session identified by the <session-id> element or if the <general-purpose> element is set to "true", that the MCPTT client is now listening to the general purpose MBMS subchannel.
- The value "not-listening" indicates that the MCPTT client has stopped listening to the MBMS subchannel in the session identified by the <session-id> element or, if the <general-purpose> element is set to "false", that the MCPTT client no longer listens to the general purpose MBMS subchannel.
Table F.2.3-1 shows the ABNF of the <mbms-listening-status> element.
Table F.2.3-1: ABNF syntax of values of the <mbms-listening-status> element
mbms-listening-status = listening-value / not-listening-value
listening-value = %x6c.69.73.74.65.6e.69.6e.67 ; "listening"
not-listening-value = %x6e.6f.74.2d.6c.69.73.74.65.6e.69.6e.67 ; "not-listening"
b) <session-id> element contains the value of the URI received in the Contact header field received from the controlling MCPTT function when an on-demand session was established, or from the participating MCPTT function in the Connect message when the session was established over a pre-established session. This element is mandatory if the <general-purpose> element is not present in the application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body.
c) <general-purpose> element is a boolean with the following meaning:
- True indicates that the MCPTT client is listening to the general purpose MBMS subchannel associated to the TMGI(s) in the <TMGI> element(s) but have not yet received a Map Group To bearer message for any session that the MCPTT client is involved in.
- False indicates that the MCPTT client is not listening to the general purpose MBMS subchannel any longer.
Absence of the <general-purpose> element requires that the <session-id> element is present in the application/vnd.3gpp.mcptt-mbms-usage-info+xml;
d) <TMGI>: element contains the TMGI. The <TMGI> element is coded as described in 3GPP TS 24.008 [43] clause 10.5.6.13 excluding the Temporary Mobile Group Identity IEI and Length of Temporary Mobile Group Identity contents (octet 1 and octet 2 in 3GPP TS 24.008 [43] clause 10.5.6.13) ; and
e) <anyExt> element containing an <mbms-reception-quality> element. The <mbms-reception-quality> element is an integer in the value range 0-5, 5 indicating the best quality. The value "2" is the lowest value where the UE receives satisfactory voice quality;
2) <mbms-suspension-status>: contains the following subelements:
a) <mbms-suspension-status>: element is a string used to indicate the MBMS bearers intended suspension status:
- The value "suspending" indicates that the RAN has decided to suspend the referenced MBMS bearer(s) at the beginning of the next MCCH modification period.
- The value "not-suspending" indicates that the RAN has decided to revoke its decision to suspend the referenced MBMS bearer(s) before the beginning of the next MCCH modification period.
Table F.2.3-2 shows the ABNF of the <mbms-suspension-status> element.
Table F.2.3-2: ABNF syntax of values of the <mbms-suspension-status> element
mbms-suspension-status = suspending-value / not-suspending-value
suspending-value = %x73.75.73.70.65.6e.64.69.6e.67 ; "suspending"
not-suspending-value = %x6e.6f.74.2d.73.75.73.70.65.6e.64.69.6e.67 ; "not-suspending"
b) <number-of-reported-bearers>: a hex binary number denoting the total number of occurrences of the <suspended-TMGI> and <other-TMGI> elements reported as part of the MBMS bearer suspension status;
c) <suspended-TMGI>: contains a TMGI that is being reported as about to be suspended or as no longer about to be suspended; and
d) <other-TMGI>: contains a TMGI that is not being reported as about to be suspended or as no longer about to be suspended, but which shares the same MCH with MBMS bearers reported in the <suspended-TMGI> elements;
3) <announcement> element containing the following elements:
a) <TMGI>: contains the TMGI. The <TMGI> element is coded as described in 3GPP TS 24.008 [43] clause 10.5.6.13 excluding the Temporary Mobile Group Identity IEI and Length of Temporary Mobile Group Identity contents (octet 1 and octet 2 in 3GPP TS 24.008 [43] clause 10.5.6.13);
b) <QCI>: element contains QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5. QCI values are defined in 3GPP TS 23.203 [41];
c) <frequency>: element containing identification of frequency in case of multi carrier support. The <frequency> element is coded as specified in 3GPP TS 29.468 [42];
NOTE 1: In the current release the frequency in the <frequency> element is the same as the frequency used for unicast.
d) <mbms-service-areas>:element is a list of MBMS service area IDs for the applicable MBMS broadcast area as specified in 3GPP TS 23.003 [40] for Service Area Identifier (SAI), and with the encoding as specified in 3GPP TS 29.061 [74] for the MBMS-Service-Area AVP;
e) <GPMS> element is a positive integer that gives the number of the media line containing the general purpose MBMS subchannel in the application/sdp MIME body attached to the SIP MESSAGE request containing the MBMS announcements;
f) <report-suspension>: element is a boolean with the following meaning:
- True indicates that the MCPTT client is instructed to notify the MCPTT server when it becomes aware of an intended change in the suspension status of a listened MBMS bearer.
- False indicates that the MCPTT client is instructed not to notify the MCPTT server if it becomes aware of an intended change in the suspension status of a listened MBMS bearer ; and
g) <anyExt> element can contain the following elements not shown in the XML schema:
i) <mcptt-mbms-rohc> element: presence of the <mcptt-mbms-rohc> element indicates that the flows delivered by the announced MBMS bearer are header compressed with ROHC as specified in RFC 5795 [80] and RFC 3095 [81]; and
ii) <max-cid> element: of type integer restricted to the range 1 to 16383 indicating the maximum CID value that can be used by the header compressor, see clause 5.1.2 in RFC 5795 [80]). If max-cid > 15 then the header compressor uses the large CID representation. Else, the header compressor uses the small CID representation;
4) <version> is an element of type "xs:integer" indicating the version of the application/vnd.3gpp.mbms-usage-info MIME body. In this version the <version element> indicates "1"; and
5) <anyExt> element can contain the following elements not shown in the XML schema:
a) <mbms-defaultMuSiK-download> that can contain:
i) a <group> element containing the identity, in the form of a URI, of a group for which the MuSiK download is performed; and
b) <mbms-explicitMuSiK-download> that can contain:
i) a <group> element containing the identity, in the form of a URI, of a group for which the MuSiK download is performed.
The recipient of the XML ignores any unknown element and any unknown attribute.
F.2.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-mbms-usage-info+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.3 XML schema for MCPTT location information
F.3.1 General
This clause defines the XML schema and the MIME type for location information.
F.3.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mcpttloc="urn:3gpp:ns:mcpttLocationInfo:1.0" targetNamespace="urn:3gpp:ns:mcpttLocationInfo:1.0" elementFormDefault="qualified" attributeFormDefault="unqualified"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<xs:import namespace="http://www.w3.org/2001/04/xmlenc#"/>
<xs:element name="location-info" id="loc">
<xs:annotation>
<xs:documentation>Root element, contains all information related to location configuration, location request and location reporting for the MCPTT service</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:choice>
<xs:element name="Configuration" type="mcpttloc:tConfigurationType"/>
<xs:element name="Request" type="mcpttloc:tRequestType"/>
<xs:element name="Report" type="mcpttloc:tReportType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:element>
<xs:complexType name="tConfigurationType">
<xs:sequence>
<xs:element name="NonEmergencyLocationInformation" type="mcpttloc:tRequestedLocationType" minOccurs="0"/>
<xs:element name="EmergencyLocationInformation" type="mcpttloc:tRequestedLocationType" minOccurs="0"/>
<xs:element name="TriggeringCriteria" type="mcpttloc:TriggeringCriteriaType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ConfigScope">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Full"/>
<xs:enumeration value="Update"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tLocationFilterType">
<xs:sequence>
<xs:element name="AreaIdentifier" type="xs:string"/>
<xs:element name="AreaIn" type="xs:boolean"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tRequestType">
<xs:complexContent>
<xs:extension base="mcpttloc:tEmptyType">
<xs:attribute name="RequestId" type="xs:string" use="required"/>
<xs:attribute name="refresh" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- Add a new element, conceptually to the "tRequestType" -->
<xs:element name="LocationFilter" type="mcpttloc:tLocationFilterType"/>
<xs:complexType name="tReportType">
<xs:sequence>
<xs:element name="TriggerId" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="mcptt-reporting-uri" type="xs:anyURI" minOccurs="0"/>
<xs:element name="CurrentLocation" type="mcpttloc:tCurrentLocationType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ReportID" type="xs:string" use="optional"/>
<xs:attribute name="ReportType" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Emergency"/>
<xs:enumeration value="NonEmergency"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- BearingAndSpeed includes current azimuth, horizontal and vertical velocities, with speed uncertainties, defined and encoded per TS 23.032 section 8.15 -->
<xs:complexType name="tBearingAndSpeedType">
<xs:sequence>
<xs:element name="BearingAndSpeed" type="mcpttloc:BearingAndSpeedFormat"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/> </xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="BearingAndSpeedFormat">
<xs:restriction base="xs:string">
<xs:pattern value="^[A-Fa-f0-9]{14}$"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="TriggeringCriteriaType">
<xs:sequence>
<xs:element name="CellChange" type="mcpttloc:tCellChange" minOccurs="0"/>
<xs:element name="TrackingAreaChange" type="mcpttloc:tTrackingAreaChangeType" minOccurs="0"/>
<xs:element name="PlmnChange" type="mcpttloc:tPlmnChangeType" minOccurs="0"/>
<xs:element name="MbmsSaChange" type="mcpttloc:tMbmsSaChangeType" minOccurs="0"/>
<xs:element name="MbsfnAreaChange" type="mcpttloc:tMbsfnAreaChangeType" minOccurs="0"/>
<xs:element name="PeriodicReport" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="TravelledDistance" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="McpttSignallingEvent" type="mcpttloc:tSignallingEventType" minOccurs="0"/>
<xs:element name="GeographicalAreaChange" type="mcpttloc:tGeographicalAreaChange"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "TriggeringCriteriaType" including 5G MBS Frequency Selection Area-->
<xs:element name="RatTypeChange" type="mcpttloc:tRatTypeChange"/>
<xs:element name="NR5GMbsfsaAreaChange" type="mcpttloc:t5GMbsfsaAreaChangeType"/>
<xs:element name="NR5GTrackingAreaChange" type="mcpttloc:t5GTrackingAreaChangeType"/>
<xs:element name="AddaptiveTrigger" type="mcpttloc:tAdaptiveTriggerType"/>
<!-- For adaptive behavior based on time & distance combination & the 5G RRC state of the UE -->
<xs:complexType name="tAdaptiveTriggerType">
<xs:sequence>
<xs:element name="MinPeriod" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="MinDistance" type="xs:positiveInteger" minOccurs="0"/>
<xs:element name="PersistencePeriod" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="AdditionalTime" type="xs:positiveInteger" minOccurs="0"/>
<xs:element name="RRC_INACTIVE_MinPeriod" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="RRC_INACTIVE_MinDistance" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name=" RRC_INACTIVE_PersistencePeriod" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:element name="RRC_INACTIVE_AdditionalTime" type="mcpttloc:tIntegerAttributeType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tCellChange">
<xs:sequence>
<xs:element name="AnyCellChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecificCell" type="mcpttloc:tSpecificCellType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ExitSpecificCell" type="mcpttloc:tSpecificCellType" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tCellChange" -->
<xs:element name="EnterSpecificNRCell" type="mcpttloc:tSpecificNRCellType"/>
<xs:element name="ExitSpecificNRCell" type="mcpttloc:tSpecificNRCellType"/>
<xs:complexType name="tEmptyType"/>
<xs:simpleType name="tEcgi">
<xs:restriction base="xs:string">
<xs:pattern value="\d{3}\d{3}[0-1]{28}"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="tNcgi">
<xs:restriction base="xs:string">
<xs:pattern value="\d{3}\d{3}[0-1]{36}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tSpecificCellType">
<xs:simpleContent>
<xs:extension base="mcpttloc:tEcgi">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tSpecificNRCellType">
<xs:simpleContent>
<xs:extension base="mcpttloc:tNcgi">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent> </xs:complexType>
<xs:complexType name="tEmptyTypeAttribute">
<xs:complexContent>
<xs:extension base="mcpttloc:tEmptyType">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="tTrackingAreaChangeType">
<xs:sequence>
<xs:element name="AnyTrackingAreaChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecificTrackingArea" type="mcpttloc:tTrackingAreaIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ExitSpecificTrackingArea" type="mcpttloc:tTrackingAreaIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="t5GTrackingAreaChangeType">
<xs:sequence>
<xs:element name="Any5GTrackingAreaChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecific5GTrackingArea" type="mcpttloc:t5GTrackingAreaIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ExitSpecific5GTrackingArea" type="mcpttloc:t5GTrackingAreaIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="tTrackingAreaIdentityFormat">
<xs:restriction base="xs:string">
<xs:pattern value="\d{3}\d{3}[0-1]{16}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tTrackingAreaIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:tTrackingAreaIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:simpleType name="t5GTrackingAreaIdentityFormat">
<xs:restriction base="xs:string">
<xs:pattern value="(^[A-Fa-f0-9]{4}$)|(^[A-Fa-f0-9]{6}$)"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="t5GTrackingAreaIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:t5GTrackingAreaIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tPlmnChangeType">
<xs:sequence>
<xs:element name="AnyPlmnChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecificPlmn" type="mcpttloc:tPlmnIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ExitSpecificPlmn" type="mcpttloc:tPlmnIdentity" minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="tPlmnIdentityFormat">
<xs:restriction base="xs:string">
<xs:pattern value="\d{3}\d{3}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tPlmnIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:tPlmnIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tMbmsSaChangeType">
<xs:sequence>
<xs:element name="AnyMbmsSaChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecificMbmsSa" type="mcpttloc:tMbmsSaIdentity" minOccurs="0"/>
<xs:element name="ExitSpecificMbmsSa" type="mcpttloc:tMbmsSaIdentity" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="EnterSpecificMbmsSa" type="mcpttloc:tMbmsSaIdentity"/>
<xs:element name="ExitSpecificMbmsSa" type="mcpttloc:tMbmsSaIdentity"/>
<xs:simpleType name="tMbmsSaIdentityFormat">
<xs:restriction base="xs:integer">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="65535"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tMbmsSaIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:tMbmsSaIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tMbsfnAreaChangeType">
<xs:sequence>
<xs:element name="EnterSpecificMbsfnArea" type="mcpttloc:tMbsfnAreaIdentity" minOccurs="0"/>
<xs:element name="ExitSpecificMbsfnArea" type="mcpttloc:tMbsfnAreaIdentity" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="AnyMbsfnAreaChange" type="mcpttloc:tEmptyTypeAttribute"/>
<xs:element name="EnterSpecificMbsfnArea" type="mcpttloc:tMbsfnAreaIdentity"/>
<xs:element name="ExitSpecificMbsfnArea" type="mcpttloc:tMbsfnAreaIdentity"/>
<xs:complexType name="t5GMbsfsaAreaChangeType">
<xs:sequence>
<xs:element name="EnterSpecific5GMbsfsaArea" type="mcpttloc:t5GMbsfsaAreaIdentity" minOccurs="0"/>
<xs:element name="ExitSpecific5GMbsfsaArea" type="mcpttloc:t5GMbsfsaAreaIdentity" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="Any5GMbsfsaAreaChange" type="mcpttloc:tEmptyTypeAttribute"/>
<xs:element name="EnterSpecific5GMbsfsaArea" type="mcpttloc:t5GMbsfsaAreaIdentity"/>
<xs:element name="ExitSpecific5GMbsfsaArea" type="mcpttloc:t5GMbsfsaAreaIdentity"/>
<xs:simpleType name="tMbsfnAreaIdentityFormat">
<xs:restriction base="xs:integer">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="255"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tMbsfnAreaIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:tMbsfnAreaIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:simpleType name="t5GMbsfsaAreaIdentityFormat">
<xs:restriction base="xs:string">
<xs:pattern value="^[A-Fa-f0-9]{6}$"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="t5GMbsfsaAreaIdentity">
<xs:simpleContent>
<xs:extension base="mcpttloc:t5GMbsfsaAreaIdentityFormat">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tIntegerAttributeType">
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="tTravelledDistanceType">
<xs:sequence>
<xs:element name="TravelledDistance" type="xs:positiveInteger"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tSignallingEventType">
<xs:sequence>
<xs:element name="InitialLogOn" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="GroupCallNonEmergency" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="PrivateCallNonEmergency" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="LocationConfigurationReceived" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tSignallingEventType" -->
<xs:element name="FunctionalAliasActivation" type="mcpttloc:tEmptyTypeAttribute"/>
<xs:element name="FunctionalAliasDeactivation" type="mcpttloc:tEmptyTypeAttribute"/>
<xs:complexType name="tEmergencyEventType">
<xs:sequence>
<xs:element name="GroupCallEmergency" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="GroupCallImminentPeril" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="PrivateCallEmergency" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="InitiateEmergencyAlert" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tRequestedLocationType">
<xs:sequence>
<xs:element name="ServingEcgi" type="mcpttloc:tEmptyType" minOccurs="0"/>
<xs:element name="NeighbouringEcgi" type="mcpttloc:tEmptyType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="MbmsSaId" type="mcpttloc:tEmptyType" minOccurs="0"/>
<xs:element name="MbsfnArea" type="mcpttloc:tEmptyType" minOccurs="0"/>
<xs:element name="GeographicalCoordinate" type="mcpttloc:tEmptyType" minOccurs="0"/>
<xs:element name="minimumIntervalLength" type="xs:positiveInteger"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tRequestedLocationType" -->
<xs:element name="ServingNcgi" type="mcpttloc:tEmptyType"/>
<xs:element name="NeighbouringNcgi" type="mcpttloc:tEmptyType"/>
<xs:element name="NR5GMbsfsaArea" type="mcpttloc:tEmptyType"/>
<xs:element name="R_BearingAndSpeed" type="mcpttloc:tEmptyType"/>
<xs:complexType name="tCurrentLocationType">
<xs:sequence>
<xs:element name="CurrentServingEcgi" type="mcpttloc:tLocationType" minOccurs="0"/>
<xs:element name="NeighbouringEcgi" type="mcpttloc:tLocationType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="MbmsSaId" type="mcpttloc:tLocationType" minOccurs="0"/>
<xs:element name="MbsfnArea" type="mcpttloc:tLocationType" minOccurs="0"/>
<xs:element name="CurrentCoordinate" type="mcpttloc:tPointCoordinate" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tCurrentLocationType" -->
<xs:element name="CurrentServingNcgi" type="mcpttloc:tLocationType"/>
<xs:element name="CL_NeighbouringNcgi" type="mcpttloc:tLocationType"/>
<xs:element name="CL_5GMbsfsaArea" type="mcpttloc:tLocationType"/>
<xs:element name="CL_BearingAndSpeed" type="mcpttloc:tBearingAndSpeedType"/>
<xs:element name="locTimestamp" type="xs:dateTime"/>
<xs:element name="FunctionalAlias" type="xs:anyURI"/>
<xs:element name="InterRatType" type="mcpttloc:tInterRatType"/>
<xs:simpleType name="tInterRatType">
<xs:restriction base="xs:string">
<xs:enumeration value="5G-MBS-to-LTE-MBMS"/>
<xs:enumeration value="5G-MBS-to-LTE-unicast"/>
<xs:enumeration value="LTE-MBMS-to-5G-MBS"/>
<xs:enumeration value="LTE-MBMS-to-5G-unicast"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="protectionType">
<xs:restriction base="xs:string">
<xs:enumeration value="Normal"/>
<xs:enumeration value="Encrypted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tLocationType">
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="Ecgi" type="mcpttloc:tEcgi" minOccurs="0"/>
<xs:element name="SaId" type="mcpttloc:tMbmsSaIdentity" minOccurs="0"/>
<xs:element name="MbsfnAreaId" type="mcpttloc:tMbsfnAreaIdentity" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:attribute name="type" type="mcpttloc:protectionType"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tLocationType" -->
<xs:element name="Ncgi" type="mcpttloc:tNcgi"/>
<xs:element name="NR5GMbsfsaAreaId" type="mcpttloc:t5GMbsfsaAreaIdentity"/>
<xs:complexType name="tGeographicalAreaChange">
<xs:sequence>
<xs:element name="AnyAreaChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:element name="EnterSpecificAreaType" type="mcpttloc:tSpecificAreaType" minOccurs="0"/>
<xs:element name="ExitSpecificAreaType" type="mcpttloc:tSpecificAreaType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tSpecificAreaType">
<xs:sequence>
<xs:element name="GeographicalArea" type="mcpttloc:tGeographicalAreaDef"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="TriggerId" type="xs:string" use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tRatTypeChange">
<xs:sequence>
<xs:element name="AnyRatTypeChange" type="mcpttloc:tEmptyTypeAttribute" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tPointCoordinate">
<xs:sequence>
<xs:element name="longitude" type="mcpttloc:tCoordinateType"/>
<xs:element name="latitude" type="mcpttloc:tCoordinateType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tPointCoordinate" -->
<xs:element name="altitude" type="mcpttloc:tCoordinateType2Bytes"/>
<xs:element name="horizontalaccuracy" type="mcpttloc:tCoordinateType1Byte"/>
<xs:element name="verticalaccuracy" type="mcpttloc:tCoordinateType1Byte"/>
<xs:complexType name="tCoordinateType">
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="threebytes" type="mcpttloc:tThreeByteType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:attribute name="type" type="mcpttloc:protectionType"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tCoordinateType2Bytes">
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="twobytes" type="mcpttloc:tTwoByteType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:attribute name="type" type="mcpttloc:protectionType"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tCoordinateType1Byte">
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="onebyteunsignedhalfrange" type="mcpttloc:tOneByteUnsignedHalfRangeType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:choice>
<xs:attribute name="type" type="mcpttloc:protectionType"/>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="tThreeByteType">
<xs:restriction base="xs:integer">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="16777215"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="tTwoByteType">
<xs:restriction base="xs:integer">
<xs:minInclusive value="-32768"/>
<xs:maxInclusive value="32767"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="tOneByteUnsignedHalfRangeType">
<xs:restriction base="xs:integer">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="127"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="tGeographicalAreaDef">
<xs:sequence>
<xs:element name="PolygonArea" type="mcpttloc:tPolygonAreaType" minOccurs="0"/>
<xs:element name="EllipsoidArcArea" type="mcpttloc:tEllipsoidArcType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- anyExt elements for "tGeographicalAreaDef: optional borders widths in meters" -->
<xs:element name="InnerBorderWidth" type="mcpttloc:tOneByteUnsignedHalfRangeType"/>
<xs:element name="OuterBorderWidth" type="mcpttloc:tOneByteUnsignedHalfRangeType"/>
<xs:complexType name="tPolygonAreaType">
<xs:sequence>
<xs:element name="Corner" type="mcpttloc:tPointCoordinate" minOccurs="3" maxOccurs="15"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="tEllipsoidArcType">
<xs:sequence>
<xs:element name="Center" type="mcpttloc:tPointCoordinate"/>
<xs:element name="Radius" type="xs:nonNegativeInteger"/>
<xs:element name="OffsetAngle" type="xs:unsignedByte"/>
<xs:element name="IncludedAngle" type="xs:unsignedByte"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttloc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<!-- anyEXT elements for the Configuration element – begin -->
<xs:element name="EmergencyTriggeringCriteria" type="mcpttloc:TriggeringCriteriaType"/>
<!-- anyEXT elements for the Configuration element – end -->
</xs:schema>
F.3.3 Semantic
The <location-info> element is the root element of the XML document. The <location-info> element contains the <Configuration>, <Request> and <Report> sub-elements, of which only one can be present.
<Configuration> element has a <ConfigScope> attribute that can assume the values "Full" and "Update". The value "Full" means that the Configuration> element contains the full location configuration which replaces any previous location configuration. The value "Update" means that the location configuration is in addition to any previous location configuration. To remove configuration elements a "Full" configuration is needed. The <Configuration> element contains the following child elements:
1) <NonEmergencyLocationInformation>, an optional element that specifies the location information requested in non-emergency situations. The <NonEmergencyLocationInformation> has the sub-elements:
a) <ServingEcgi>, an optional element specifying that the serving E-UTRAN Cell Global Identity (ECGI) needs to be reported;
b) <NeighbouringEcgi>, an optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported;
c) <MbmsSaId>, an optional element specifying that the serving MBMS Service Area Id needs to be reported;
d) <MbsfnArea>, an optional element specifying that the MBSFN area Id needs to be reported;
e) <GeographicalCoordinate>, an optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [54] needs to be reported;
f) <minimumIntervalLength>, a mandatory element specifying the minimum time the MCPTT client needs to wait between sending location reports. The value is given in seconds;
g) <ServingNcgi>, an optional element of the <anyExt> element specifying that the serving NR Cell Global Identity (NCGI) needs to be reported;
h) <NeighbouringNcgi>, an optional element of the <anyExt> element that can occur multiple times, specifying that neighbouring NCGIs need to be reported;
i) <NR5GMbsfsaArea>, an optional element of the <anyExt> element specifying that the 5G MBS Frequency Selection Area Id needs to be reported; and
j) <R_BearingAndSpeed>, an optional element of the <anyExt> element specifying that the BearingAndSpeed needs to be reported;
2) <EmergencyLocationInformation>, an optional element that specifies the location information requested in emergency situations. The <EmergencyLocationInformation> has the sub-elements:
a) <ServingEcgi>, an optional element specifying that the serving ECGI needs to be reported;
b) <NeighbouringEcgi>, an optional element that can occur multiple times, specifying that neighbouring ECGIs need to be reported;
c) <MbmsSaId>, an optional element specifying that the serving MBMS Service Area Id needs to be reported;
d) <MbsfnArea>, an optional element specifying that the MBSFN area Id needs to be reported;
e) <GeographicalCoordinate>, an optional element specifying that the geographical coordinate specified in clause 6.1 in 3GPP TS 23.032 [54] needs to be reported;
f) <minimumIntervalLength>, a mandatory element specifying the minimum time the MCPTT client needs to wait between sending location reports. The value is given in seconds;
g) <ServingNcgi>, an optional element of the <anyExt> element specifying that the serving NCGI needs to be reported;
h) <NeighbouringNcgi>, an optional element of the <anyExt> element that can occur multiple times, specifying that neighbouring NCGIs need to be reported;
i) <NR5GMbsfsaArea>, an optional element of the <anyExt> element specifying that the 5G MBS Frequency Selection Area Id needs to be reported; and
j) <R_BearingAndSpeed>, an optional element of the <anyExt> element specifying that the BearingAndSpeed needs to be reported;
3) <TriggeringCriteria>, a mandatory element specifying the triggers for the MCPTT client to perform reporting in non-emergency status. The <TriggeringCriteria> element contains the following sub-elements:
a) <CellChange>, an optional element specifying what cell changes trigger location reporting. Consists of the following sub-elements:
I) <AnyCellChange>, an optional element. The presence of this element specifies that any cell change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecificCell>, an optional element specifying an ECGI, which when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <ExitSpecificCell>, an optional element specifying an ECGI, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) <EnterSpecificNRCell>, an optional element of the <anyExt> element, specifying an NCGI, which when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) <ExitSpecificNRCell>, an optional element of the <anyExt> element, specifying an NCGI, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
b) <TrackingAreaChange>, an optional element specifying what tracking area changes trigger location reporting. Consists of the following sub-elements:
I) <AnyTrackingAreaChange>, an optional element. The presence of this element specifies that any tracking area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecificTrackingArea>, an optional element specifying a Tracking Area Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
III) <ExitSpecificTrackingArea>, an optional element specifying a Tracking Area Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
c) <PlmnChange>, an optional element specifying what PLMN changes trigger location reporting. Consists of the following sub-elements:
I) <AnyPlmnChange>, an optional element. The presence of this element specifies that any PLMN change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecificPlmn>, an optional element specifying a PLMN Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
III) <ExitSpecificPlmn>, an optional element specifying a PLMN Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
d) <MbmsSaChange>, an optional element specifying what MBMS changes trigger location reporting. Consists of the following sub-elements:
I) <AnyMbmsSaChange>, an optional element. The presence of this element specifies that any MBMS SA change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecificMbmsSa>, an optional element specifying an MBMS Service Area Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <ExitSpecificMbmsSa>, an optional element specifying an MBMS Service Area Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) additional <EnterSpecificMbmsSa> elements may be added in an <anyExt> element specifying MBMS Service Area Ids which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) additional <ExitSpecificMbmsSa> elements may be added in an <anyExt> element specifying MBMS Service Area Ids which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
e) <MbsfnAreaChange>, an optional element specifying what MBSFN changes trigger location reporting. Consists of the following sub-elements:
I) <AnyMbsfnAreaChange>, an optional element in an <anyExt> element. The presence of this element specifies that any MBSFN area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecificMbsfnArea>, an optional element specifying an MBSFN area which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <ExitSpecificMbsfnArea>, an optional element specifying an MBSFN area which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) additional <EnterSpecificMbsfnArea> elements may be added in an <anyExt> element specifying MBSFN areas which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) additional <ExitSpecificMbsfnArea> elements may be added in an <anyExt> element specifying MBSFN areas which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
f) <PeriodicReport>, an optional element specifying that periodic location reports shall be sent. The value in seconds specifies the reporting interval. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
g) <TravelledDistance>, an optional element specifying that the travelled distance shall trigger a report. The value in metres specified the travelled distance. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
h) <McpttSignallingEvent>, an optional element specifying what signalling events triggers a location report. The <McpttSignallingEvent> element has the following sub-elements:
I) <InitialLogOn>, an optional element specifying that an initial log on triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <GroupCallNonEmergency>, an optional element specifying that a non-emergency group call triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <PrivateCallNonEmergency>, an optional element specifying that a non-emergency private call triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) <LocationConfigurationReceived>, an optional element specifying that a received location configuration triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) <anyExt>, an optional element containing:
A) an optional <FunctionalAliasActivation> element specifying that a Functional Alias activation triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
B) an optional element <FunctionalAliasDeactivation> specifying that a Functional Alias deactivation triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
i) <GeographicalAreaChange>, an optional element specifying what geographical area changes trigger location reporting. Consists of the following sub-elements:
I) <AnyAreaChange>, an optional element. The presence of this element specifies that any geographical area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string. At least one <GeographicalArea> element with its sub-elements, as defined in the <EnterSpecificAreaType> element, has to be contained within this trigger or within a different active trigger;
II) <EnterSpecificAreaType>, an optional element specifying a geographical area which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string. The <EnterSpecificAreaType> element has the following sub-elements:
A) <GeographicalArea>, an optional element containing the following sub-elements:
x1) <PolygonArea>, an optional element specifying the area as a polygon specified in clause 5.4 in 3GPP TS 23.032 [54];
x2) <EllipsoidArcArea>, an optional element specifying the area as an Ellipsoid Arc specified in clause 5.7 in 3GPP TS 23.032 [54];
x3) <InnerBorderWidth>, an optional element specifying the width of a band of terrain delimited by an imaginary fence running parallel to the defined contour of the area on the inside, and which, if present and not set to 0, indicates that the area entering trigger will fire if the fence, rather than the defined contour of the area, is crossed due to inward motion, thus avoiding spurious firings of the entering trigger in case of rapid zig-zagging close to the defined contour line of the area; and
x4) <OuterBorderWidth>, an optional element specifying the width of a band of terrain delimited by an imaginary fence running parallel to the defined contour of the area on the outside, and which, if present and not set to 0, indicates that the area exiting trigger will fire if the fence, rather than the defined contour of the area, is crossed due to outward motion, thus avoiding spurious firings of the exiting trigger in case of rapid zig-zagging close to the defined contour line of the area; and
III) <ExitSpecificAreaType>, an optional element specifying a geographical area which, when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string and a <GeographicalArea> element with its sub-elements, as defined in the <EnterSpecificAreaType> element;
j) <RatTypeChange>, an optional element specifying what inter-RAT changes trigger location reporting. Consists of the following sub-elements:
I) <AnyRatTypeChange>, an optional element. The presence of this element specifies that the inter-system RAT changes is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
k) <NR5GMbsfsaAreaChange>, an optional element of the <anyExt> element specifying what 5G MBSFA changes trigger location reporting. Consists of the following sub-elements:
I) <Any5GMbsfsaAreaChange>, an optional element of the <anyExt> element. The presence of this element specifies that any 5G MBSFSA change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecific5GMbsfsaArea>, an optional element specifying a 5G MBSFSA which, when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <ExitSpecific5GMbsfsaArea>, an optional element specifying a 5G MBSFSA, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) additional <EnterSpecific5GMbsfsaArea> elements may be added in an <anyExt> element specifying 5G MBSFSAs which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) additional <ExitSpecific5GMbsfsaArea> elements may be added in an <anyExt> element specifying 5G MBSFSAs which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
l) <NR5GTrackingAreaChange>, an optional element of the <anyExt> element specifying what 5G tracking area changes trigger location reporting. Consists of the following sub-elements:
I) <Any5GTrackingAreaChange>, an optional element. The presence of this element specifies that any 5G tracking area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <EnterSpecific5GTrackingArea>, an optional element specifying a 5G Tracking Area Id, which when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
III) <ExitSpecific5GTrackingArea>, an optional element specifying a 5G Tracking Area Id which, when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
m) <AdaptiveTrigger>, an optional element of the <anyExt> element specifying parameters controlling adaptive combined time and distance triggering. In addition to a mandatory <TriggerId> attribute that shall be set to a unique string, the following sub-elements may be included:
I) <MinPeriod>, an optional element specified as a positive or 0 integer number of seconds and defaulting at 0, if not present. This element specifies the minimum wait period between consecutive location reports, irrespective of changes in the distance between the current location and the location of the most recent sending of a location report;
II) <MinDistance>, an optional element specified as a strictly positive integer number of meters and defaulting at infinity, if not present. This element is used in the decision of sending a location report based on travelled distance, and specifies the minimum required distance, between the current location and the location of the most recent sending of a location report;
III) <PersistencePeriod>, an optional element specified as a positive or 0 integer number of seconds and defaulting at 0, if not present. This element specifies the time between the moment when the MCPTT client detected that the distance between the current location and the location of the most recent sending of a location report exceeded <MinDistance> and the moment when the MCPTT client will check again that the updated current location is still farther away by at least <MinDistance>from the location of the mentioned sending of the location report. If the check is positive, a location report based on travelled distance will be sent;
IV) <AdditionalTime>, an optional element, specified as a strictly positive integer number of seconds and defaulting at 1. If a location report is not sent based on the travelled distance, the MCPTT will send a location report after <MinPeriod> + <PersistencePeriod> + <AdditionalTime> seconds after the previous location report;
NOTE 1: Taking as time origin the moment when the most recent previous location report was sent, the trigger will cause a new location report to be sent, either a travelled distance-based location report after at least <MinPeriod> + <PersistencePeriod> seconds or a time-based report after <MinPeriod> + <PersistencePeriod> + <AdditionalTime> seconds, whichever comes first. The trigger will then be reset and the time of the sending of the new location report will become the time origin for the next firing of the trigger.
V) <RRC_INACTIVE_MinPeriod>, an optional element with the same semantics and behaviour as described above for the corresponding parameter, but applicable when the UE receives MBS traffic in RRC_INACTIVE state;
VI) <RRC_INACTIVE_MinDistance>, an optional element with the same semantics and behaviour as described above for the corresponding parameter, but applicable when the UE receives MBS traffic in RRC_INACTIVE state;
VII) <RRC_INACTIVE_PersistencePeriod>, an optional element with the same semantics and behaviour as described above for the corresponding parameter, but applicable when the UE receives MBS traffic in RRC_INACTIVE state; and
VIII) <RRC_INACTIVE_AdditionalTime>, an optional element with the same semantics and behaviour as described above for the corresponding parameter, but applicable when the UE receives MBS traffic in RRC_INACTIVE state; and
4) the <anyExt> shall be included with the following element not declared in the XML schema:
a) <EmergencyTriggeringCriteria>, a mandatory element specifying the triggers for the MCPTT client to perform reporting in emergency status. The <EmergencyTriggeringCriteria> element contains the following sub-elements:
I) <CellChange>, an optional element specifying what cell changes trigger location reporting. Consists of the following sub-elements:
A) <AnyCellChange>, an optional element. The presence of this element specifies that any cell change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecificCell>, an optional element specifying an ECGI, which when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
C) <ExitSpecificCell>, an optional element specifying an ECGI, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) <EnterSpecificNRCell>, an optional element of the <anyExt> element, specifying an NCGI, which when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
V) <ExitSpecificNRCell>, an optional element of the <anyExt> element, specifying an NCGI, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
II) <TrackingAreaChange>, an optional element specifying what tracking area changes trigger location reporting. Consists of the following sub-elements:
A) <AnyTrackingAreaChange>, an optional element. The presence of this element specifies that any tracking area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecificTrackingArea>, an optional element specifying a Tracking Area Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
C) <ExitSpecificTrackingArea>, an optional element specifying a Tracking Area Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
III) <PlmnChange>, an optional element specifying what PLMN changes trigger location reporting. Consists of the following sub-elements:
A) <AnyPlmnChange>, an optional element. The presence of this element specifies that any PLMN change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecificPlmn>, an optional element specifying a PLMN Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
C) <ExitSpecificPlmn>, an optional element specifying a PLMN Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
IV) <MbmsSaChange>, an optional element specifying what MBMS changes trigger location reporting. Consists of the following sub-elements:
A) <AnyMbmsSaChange>, an optional element. The presence of this element specifies that any MBMS SA change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecificMbmsSa>, an optional element specifying an MBMS Service Area Id which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
C) <ExitSpecificMbmsSa>, an optional element specifying an MBMS Service Area Id which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
D) additional <EnterSpecificMbmsSa> elements may be added in an <anyExt> element specifying MBMS Service Area Ids which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
E) additional <ExitSpecificMbmsSa> elements may be added in an <anyExt> element specifying MBMS Service Area Ids which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
V) <MbsfnAreaChange>, an optional element specifying what MBSFN changes trigger location reporting. Consists of the following sub-elements:
A) <AnyMbsfnAreaChange>, an optional element in an <anyExt> element. The presence of this element specifies that any MBSFN area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecificMbsfnArea>, an optional element specifying an MBSFN area which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
C) <ExitSpecificMbsfnArea>, an optional element specifying an MBSFN area which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
D) additional <EnterSpecificMbsfnSa> elements may be added in an <anyExt> element specifying MBSFN areas which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
E) additional <ExitSpecificMbsfnSa> elements may be added in an <anyExt> element specifying MBSFN areas which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
VI) <PeriodicReport>, an optional element specifying that periodic location reports shall be sent. The value in seconds specifies the reporting interval. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
VII) <TravelledDistance>, an optional element specifying that the travelled distance shall trigger a report. The value in metres specified the travelled distance. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
VIII) <McpttSignallingEvent>, an optional element specifying what signalling events triggers a location report. The <McpttSignallingEvent> element has the following sub-elements:
A) <InitialLogOn>, an optional element specifying that an initial log on triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <GroupCallNonEmergency>, an optional element specifying that a non-emergency group call triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
C) <PrivateCallNonEmergency>, an optional element specifying that a non-emergency private call triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
D) <LocationConfigurationReceived>, an optional element specifying that a received location configuration triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
IX) <GeographicalAreaChange>, an optional element specifying what geographical area changes trigger location reporting. Consists of the following sub-elements:
A) <AnyAreaChange>, an optional element. The presence of this element specifies that any geographical area change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string. At least one <GeographicalArea> element with its sub-elements, as defined in the <EnterSpecificAreaType> element, has to be contained within this trigger or within a different active trigger;
B) <EnterSpecificAreaType>, an optional element specifying a geographical area which, when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string. The <EnterSpecificAreaType> element contains a <GeographicalArea> element, as defined in bullet 3);
C) <ExitSpecificAreaType>, an optional element specifying a geographical area which, when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string and a <GeographicalArea> element with its sub-elements, as defined in the <EnterSpecificAreaType> element;
X) <NR5GMbsfsaAreaChange>, an optional element of the <anyExt> element specifying what 5G MBSFA changes trigger location reporting. Consists of the following sub-elements:
A) <Any5GMbsfsaAreaChange>, an optional element in an <anyExt> element. The presence of this element specifies that any 5G MBSFSA change is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecific5GMbsfsaArea>, an optional element specifying a 5G MBSFSA which, when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
C) <ExitSpecific5GMbsfsaArea>, an optional element specifying a 5G MBSFSA, which when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
D) additional <EnterSpecific5GMbsfsaArea> elements may be added in an <anyExt> element specifying 5G MBSFSAs which when entered triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
E) additional <ExitSpecific5GMbsfsaArea> elements may be added in an <anyExt> element specifying 5G MBSFSAs which when exited triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
XI) <NR5GTrackingAreaChange>, an optional element specifying what tracking area changes trigger location reporting. Consists of the following sub-elements:
A) <Any5GTrackingAreaChange>, an optional element. The presence of this element specifies that any change to or from a 5G tracking area is a trigger. Contains a mandatory <TriggerId> attribute that shall be set to a unique string;
B) <EnterSpecific5GTrackingArea>, an optional element specifying a 5G Tracking Area Id which, when entered, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
C) <ExitSpecific5GTrackingArea>, an optional element specifying a 5G Tracking Area Id which, when exited, triggers a location report. Contains a mandatory <TriggerId> attribute that shall be set to a unique string; and
XII) <AdaptiveTrigger>, an optional element of the <anyExt> element specifying parameters controlling adaptive combined time and distance triggering in emergency situations. The semantics and behaviours are the same as for corresponding elements and sub-elements in non-emergency <TriggeringCriteria>.
<Request> is an element with a <RequestId> attribute, with a "LocationFilter" element as an <anyExt> element of "location‑info" and with an optional "refresh" attribute. The <Request> element is used to request a location report. The "LocationFilter" element requires that only requested MCPTT clients which pass the specified filtering criteria have their location information reported to the requesting MCPTT client. The "refresh" attribute is a Boolean and requires that the location information is immediately updated. The value of the <RequestId> attribute is returned in the corresponding <ReportId> attribute in order to correlate the request and the report.
<Report> is an element used to include the location report. It contains a <ReportId> attribute and a <ReportType> attribute. The <ReportId> attribute is used to return the value in the <RequestId> attribute in the <Request> element. The <ReportType> attribute has two values "Emergency" and "NonEmergency" used to inform whether the client is sending the report in an emergency situation or not. The <Report> element contains the following sub-elements:
1) <TriggerId>, an optional element which can occur multiple times that contain the value of the <TriggerId> attribute associated with a trigger that has fired; and
2) <mcptt-reporting-uri>, an optional element which is used to identify the reporting MCPTT client, this is required when multiple location information responses for different requested MCPTT clients are sent, triggered by one single location information request; and
3) <CurrentLocation>, a mandatory element that contains the location information. The <CurrentLocation> element contains the following sub-elements:
a) <CurrentServingEcgi>, an optional element containing the ECGI of the serving cell;
b) <NeighbouringEcgi>, an optional element that can occur multiple times. It contains the ECGI of any neighbouring cell the MCPTT client can detect;
c) <MbmsSaId>, an optional element containing the MBMS Service Area Id the MCPTT client is using;
d) <MbsfnArea>, an optional element containing the MBSFN area the MCPTT is located in;
e) <CurrentCoordinate>, an optional element containing:
i) the longitude and latitude coded as in clause 6.1 in 3GPP TS 23.032 [54]; and
ii) an optional <anyExt> element containing:
A) an <altitude> element where the <twobytes> sub-element is coded as in clause 6.3 in 3GPP TS 23.032 [54];
B) an optional <horizontalaccuracy> element where the <onebyteunsignedhalfrange> sub-element is coded as in clause 6.2 in 3GPP TS 23.032 [54], which describes the uncertainty for latitude and longitude; and
C) an optional <verticalaccuracy> element where the <onebyteunsignedhalfrange> sub-element is coded as in clause 6.4 in 3GPP TS 23.032 [54], which describes the uncertainty for altitude;
f) <anyExt>, an optional element containing:
i) an optional <locTimestamp> element containing the date and time the location measurement was made;
ii) an optional <FunctionalAlias> element containing the functional alias status change that tiggered the location measurement;
iii) an optional <InterRatType> element containing the inter-RAT change type. The <InterRatType> element set to:
A) "5G-MBS-to-LTE-MBMS" when the inter-system switching from 5G MBS session to LTE MBMS bearer;
B) "5G-MBS-to-LTE-unicast" when the inter-system switching from 5G MBS session to LTE unicast bearer;
C) "LTE-MBMS-to-5G-MBS" when the inter-system switching from LTE MBMS to 5G MBS session; or
D) "LTE-MBMS-to-5G-unicast" when the inter-system switching from LTE MBMS to 5G unicast PDU session.
iv) <CurrentServingNcgi>, an optional element containing the NCGI of the serving cell;
v) <CL_NeighbouringNcgi>, an optional element that can occur multiple times. It contains the NCGI of any neighbouring cell the MCPTT client can detect; and
vi) <CL_5GMbsfsaArea>, an optional element containing the 5G MBSFSA the MCPTT is located in; and
vii) <CL_BearingAndSpeed>, an optional element consisting of a 7 byte‑long string of 14 hexadecimal digits which encode the binary content of the bearing, horizontal velocity and vertical velocity, as well as horizontal and vertical speed uncertainties of the MCPTT UE, according to clause 8.15 of 3GPP TS 23.032 [54], where the spare bits are set to 0.
The contents of the sub-elements in the <CurrentLocation> sub-element of the <Report> element can be encrypted. The following rules are applied when any of these elements are included:
1) if confidentiality protection is not required, then:
a) the "type" attributes associated with the <CurrentServingEcgi>, <NeighbouringEcgi>, <MbmsSaId>, and <MbsfnArea> elements of the <CurrentLocation> element of the <Report> element have the value "Normal"; and
i) the <Ecgi> sub-element of the <CurrentServingEcgi> element contains the unencrypted value of the ECGI of the serving cell;
ii) the <Ecgi> sub-element of the <NeighbouringEcgi> element contains the unencrypted value of the ECGI of any neighbouring cell;
iii) the <SaId> sub-element of the <MbmsSaId> element contains the unencrypted value of the MBMS Service Area Id the MCPTT client is using; and
iv) the <MbsfnAreaId> sub-element of the <MbsfnArea>, element contains the unencrypted value of the MBSFN area the MCPTT is located in;
b) the "type" attribute associated with the <CL_BearingAndSpeed> sub-element has the value “Normal” and the value of the <CL_BearingAndSpeed> sub-element is unencrypted;
c) the "type" attributes associated with the <CurrentServingNcgi>, <CL_NeighbouringNcgi>, <MbmsSaId>, and <CL_5GMbsfsaArea> elements of the <anyExt> element of the <CurrentLocation> element of the <Report> element have the value "Normal"; and
i) the <Ncgi> sub-element of the <CurrentServingNcgi> element contains the unencrypted value of the NCGI of the serving cell;
ii) the <Ncgi> sub-element of the <CL_NeighbouringNcgi> element contains the unencrypted value of the NCGI of any neighbouring cell;
iii) the <SaId> sub-element of the <MbmsSaId> element contains the unencrypted value of the MBMS Service Area Id the MCPTT client is using; and
iv) the <NR5GMbsfsaAreaId> sub-element of the <CL_5GMbsfsaArea>, element contains the unencrypted value of the 5G MBSFSA area the MCPTT is located in; and
d) the "type" attributes associated with the <longitude>, <latitude>, <altitude>, <horizontalaccuracy>, and <verticalaccuracy> sub-elements of the <CurrentCoordinate> element have the value "Normal" and the <three-bytes> sub-elements of <longitude> and <latitude> sub-elements, the <twobytes> sub-element of the <altitude> sub-element, the <onebyteunsignedhalfrange> sub-element of the <horizontalaccuracy>, and the <onebyteunsignedhalfrange> sub-element of the <verticalaccuracy> sub-element contain the unencrypted value of longitude, latitude, altitude, horizontalaccuracy, and verticalaccuracy; and
2) if confidentiality protection is required, then:
a) the "type" attributes associated with the <CurrentServingEcgi>, <NeighbouringEcgi>, <MbmsSaId>, <MbsfnArea>, <CL_5GMbsfsaArea>, <CurrentServingNcgi>, <CL_NeighbouringNcgi> and <CL_BearingAndSpeed> elements have the value "Encrypted";
b) the "type" attributes associated with the <longitude>, <latitude>, <altitude>, <horizontalaccuracy>, and <verticalaccuracy> sub-elements of the <CurrentCoordinate> element have the value "Encrypted"; and
c) for each of the elements described in 2a) and sub-elements described in 2b) above, the <xenc:EncryptedData> element from the "http://www.w3.org/2001/04/xmlenc#" namespace is included and:
i) can have a "Type" attribute can be included with a value of "http://www.w3.org/2001/04/xmlenc#Content";
ii) can include an <EncryptionMethod> element with the "Algorithm" attribute set to value of "http://www.w3.org/2009/xmlenc11#aes128-gcm";
iii) can include a <KeyInfo> element with a <KeyName> element containing the base 64 encoded XPK-ID; and
iv) includes a <CipherData> element with a <CipherValue> element containing the encrypted data.
NOTE 2: When the optional attributes and elements are not included within the <xenc:EncryptedData> element, the information they contain is known to sender and the receiver by other means.
The recipient of the XML ignores any unknown element and any unknown attribute.
F.3.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp. mcptt-location-info+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.4 XML schema for MCPTT (de)-affiliation requests
F.4.1 General
This clause defines XML schema and MIME type for MCPTT (de)-affiliation requests.
F.4.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:affiliationCommand:1.0"
xmlns:mcpttaff="urn:3gpp:ns:affiliationCommand:1.0"
attributeFormDefault="unqualified" elementFormDefault="qualified">
<xs:complexType name="affiliate-command" id="affil">
<xs:sequence>
<xs:element type="xs:anyURI" name="group" minOccurs="1" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttaff:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="de-affiliate-command">
<xs:sequence>
<xs:element type="xs:anyURI" name="group" minOccurs="1" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttaff:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:element name="command-list">
<xs:complexType>
<xs:sequence>
<xs:element name="affiliate" type="mcpttaff:affiliate-command" minOccurs="0" maxOccurs="1"/>
<xs:element name="de-affiliate" type="mcpttaff:de-affiliate-command" minOccurs="0" maxOccurs="1"/>
<xs:element name="anyExt" type="mcpttaff:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
F.4.3 Semantic
The <command-list> element is the root element of the XML document. The <command-list> element may contain <affiliate-command>, or <de-affiliate-command> subelements or both.
If the <command-list> contains the <affiliate-command> element then:
1) the <affiliate-command> element contains a list of <group> subelements having at least one subelement. The recipient shall perform an affiliation for all the MCPTT groups contained in the list for the clients for which the <command-list> applies.
If the <command-list> contains the <de-affiliate-command> element then:
1) the <de-affiliate-command> element contains a list of <group> subelements having at least one subelement. The recipient shall perform a de-affiliation for all the MCPTT groups contained in the list for the clients for which the <command-list> applies.
The recipient of the XML ignores any unknown element and any unknown attribute.
F.4.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-affiliation-command+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.5 XML schema for the floor request
F.5.1 General
This clause defines XML schema and MIME type for application/vnd.3gpp.mcptt-floor-request+xml.
F.5.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:3gpp:ns:mcpttFloorRequest:1.0" xmlns:mcpttfloor="urn:3gpp:ns:mcpttFloorRequest:1.0">
<!-- the root element -->
<xs:element name="mcptt-floor-request" type="mcpttfloor:mcptt-floor-request-Type" minOccurs="1" maxOccurs="2"/>
<xs:complexType name="mcptt-floor-request-Type">
<xs:sequence>
<xs:element name="floor-type" type="xs:string"/>
<xs:element name="ssrc" type="xs:unsignedLong"/>
<xs:element name="floor-priority" type="xs:unsignedByte"/>
<xs:element name="user-id" type="xs:anyURI"/>
<xs:element name="track-info" type="mcpttfloor:track-info-Type"/>
<xs:element name="floor-indicator" type="xs:unsignedLong"/>
<xs:element name="anyExt" type="mcpttfloor:anyExtType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="track-info-Type">
<xs:sequence>
<xs:element name="queueing-capability" type="xs:byte"/>
<xs:element name="participant-type" type="xs:string"/>
<xs:element name="floor-participant-reference" type="xs:unsignedLong" minOccurs="1" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttfloor:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
</xs:schema>
F.5.3 Semantic
This clause describes the elements of the floor request XML Schema.
<floor-type> Contains information about which floor the current speaker was using. The value "general is selected when the current speaker has permission to speak in on the general floor as specified in 3GPP TS 24.380 [5] clause 6.3.4. The value "dual" is selected when the current speaker has permission to speak in on the dual floor as specified in 3GPP TS 24.380 [5] clause 6.3.6.
Table F.5.3-1 shows the ABNF of the <floor-type> element.
Table F.5.3-1: ABNF syntax of values of the <floor-type> element
floor-type-value = general-value / dual-value
general-value = %x67.65.6e.65.72.62.6c ; "general"
dual-value = %x64.75.61.6c ; "dual"
<ssrc>: Contains the SSRC of the floor participant. The content of the SSRC field shall be coded as specified in IETF RFC 3550 [10].
<floor-priority>: Contains the level of priority of the floor request. The <floor-priority> element is coded as specified in 3GPP TS 24.380 [5].
<user-id>: Contains the MCPTT ID of the MCPTT user requesting the permission to send media.
<track-info>: Contains the <queueing-capability> element, the <participant-type> element and the <floor-participant-reference>.
<floor-indicator>: Contains additional information. The <floor-indicator> element is coded as specified in 3GPP TS 24.380 [5].
<participant-type>: Contains the participant type assigned to the MCPTT user identified by the <user-id> element. The <participant-type> element is coded as specified in 3GPP TS 24.380 [5].
NOTE: The reference to the floor participant is a value only understandable by the floor control server interface in the non-Controlling function of an MCPTT group.
<queueing-capability>: Contains the queueing capability of the MCPTT client. The <queueing-capability> element is coded as specified in 3GPP TS 24.380 [5].
The recipient of the XML ignores any unknown element and any unknown attribute.
F.5.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-floor-request+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.0.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.6 XML schema for integrity protection of MIME bodies
F.6.1 General
This clause defines the XML schema and the MIME type vnd.3gpp.mcptt-signed+xml, for integrity protection of MIME bodies used in the present document.
F.6.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:mcpttSignedDoc:1.0"
xmlns:mcpttsigneddoc="urn:3gpp:ns:mcpttSignedDoc:1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
xmlns:xmldsig="http://www.w3.org/2000/09/xmldsig#">
<xs:import namespace="http://www.w3.org/2000/09/xmldsig#"
schemaLocation="http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd"/>
<xs:complexType name="signaturesType">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttsigneddoc:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<!-- root XML element when creating a signed XML document -->
<xs:element name="signatures" type="mcpttsigneddoc:signaturesType"/>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
F.6.3 Semantic
When integrity protection is turned on, the vnd.3gpp.mcptt-signed+xml MIME body is included when sending MIME bodies containing XML content in SIP requests and SIP responses.
The <signatures> element is the root element of the XML document.
NOTE 1: The subelements of the <signatures> element are validated by the <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> particle of the <signatures> element
An instance of the <signatures> element contains one or more instances of the <xmldsig:Signature> element from the http://www.w3.org/2000/09/xmldsig# namespace. The <xmldsig:Signature> element validates against the <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> element.
Each <xmldsig:Signature> element contains the following child elements:
1) a <xmldsig:SignatureValue> element is included with a signature value;
2) a <xmldsig:SignedInfo> element can be included and can contain the following child elements:
a) a <xmldsig:CanonicalizationMethod> element can be included with an "Algorithm" attribute containing an appropriate canonicalisation method to be applied to the signed information;
b) a <xmldsig:SignatureMethod> element can be included with an "Algorithm" attribute containing an appropriate algorithm for the signature; and
NOTE 2: For signatures, it is assumed that HMAC-SHA256 is supported by the sender and the receiver.
c) a <xmldsig:Reference> element can be included and can contain the following child elements:
i) a "URI" attribute can be included with a "cid-URL" referring to an XML MIME body containing a Content-ID set to the "cid-URL"
ii) a <xmldsig:DigestMethod> element can be included referring to an appropriate method for hashing the content; and
NOTE 3: For hashing of the content, it is assumed that SHA-256 is supported by the sender and the receiver.
iii) a <xmldsig:DigestValue> element can be included containing the hashed content; and
3) a <xmldsig:KeyInfo> element can be included with a <xmldsig:KeyName> element containing the base 64 encoded XPK-ID.
NOTE 4: When the optional attributes and elements are not included within the <xmldsig:Signature> element, the information they contain is known to sender and the receiver by other means.
F.6.4 IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-signed+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 13.1.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
F.7 XML schema for regroup using preconfigured group
F.7.1 General
This clause defines the XML schema and MIME type for regroup using preconfigured group.
F.7.2 XML schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:3gpp:ns:preconfiguredRegroup:1.0"
xmlns:mcpttrgrp="urn:3gpp:ns:preconfiguredRegroup:1.0"
attributeFormDefault="unqualified" elementFormDefault="qualified">
<!-- root XML element -->
<xs:element name="mcpttregroup" type="mcpttrgrp:mcpttregroup-Type" id="info"/>
<xs:complexType name="mcpttregroup-Type">
<xs:sequence>
<xs:element name="mcpttregroup-Params" type="mcpttrgrp:mcpttregroup-ParamsType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mcpttregroup-ParamsType">
<xs:sequence>
<xs:element name="preconfig-group-id" type="mcpttrgrp:preconfig-group-Type"/>
<xs:element name="mcptt-regroup-uri" type="mcpttrgrp:mcptt-regroup-uri-Type"/>
<xs:element name="groups-for-regroup" type="mcpttrgrp:groups-for-regroup-Type" minOccurs="0"/>
<xs:element name="users-for-regroup" type="mcpttrgrp:users-for-regroup-Type" minOccurs="0"/>
<xs:element name="regroup-action" type="xs:string"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="preconfig-group-Type">
<xs:sequence>
<xs:element type="xs:anyURI" name="preconfigured-group" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="mcptt-regroup-uri-Type">
<xs:sequence>
<xs:element type="xs:anyURI" name="mcptt-regroup-uri"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="groups-for-regroup-Type">
<xs:sequence>
<xs:element type="xs:anyURI" name="group" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="users-for-regroup-Type">
<xs:sequence>
<xs:element type="xs:anyURI" name="user" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="anyExt" type="mcpttrgrp:anyExtType" minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
<xs:complexType name="anyExtType">
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
F.7.3 Semantic
The <preconfigured-group> element shall contain a URI identifying the preconfigured MCPTT group.
The <mcptt-regroup-uri> element shall contain a URI containing the temporary group identity identifying the regroup.
The <groups-for-regroup> element shall contain one or more <group> elements that shall each contain a URI of a group that is to be a constituent group of the regroup.
The <users-for-regroup> element shall contain one or more <user> elements that shall each contain an MCPTT ID of a user that is to be affiliated to the regroup.
The XML document shall have either one <groups-for-regroup> element or one <users-for-regroup> element, but not both.
If the <regroup-action> element contains the string "create" then:
1) if a <groups-for-regroup> element exists in the received XML, then:
a) if the recipient is the controlling MCPTT function for the MCPTT group identified in the <preconfigured-group> element the recipient shall follow the procedures to create a group regroup with identity equal to the value contained in the <mcptt-regroup-uri> element based on the configuration of the preconfigured MCPTT group identified in the <preconfigured-group> element;
b) if the recipient is a non-controlling MCPTT function, the recipient shall follow the procedures to affiliate users belonging to any constituent groups of the group regroup with identity equal to the value contained in the <mcptt-regroup-uri> element based on the configuration of the preconfigured MCPTT group identified in the <preconfigured-group> element; and
c) if the recipient is the terminating participating MCPTT function for one or more MCPTT users affiliated to a constituent group of the group regroup, the recipient shall follow the procedures to notify each MCPTT user in the list of users in the <users-for-regroup> element that it serves of the group regroup and affiliate those users to the group regroup; and
2) if a <users-for-regroup> element exists in the received XML, then:
a) if the recipient is the controlling MCPTT function for the MCPTT group identified in the <preconfigured-group> element, the recipient shall follow the procedures to create a user regroup with identity equal to the value contained in the <mcptt-regroup-uri> element based on the configuration of the preconfigured MCPTT group identified in the <preconfigured-group> element; and
b) if the recipient is the terminating participating MCPTT function for one or more MCPTT users identified in the <users-for-regroup> element, the recipient shall follow the procedures to notify each MCPTT user in the list of users in the <users-for-regroup> element that it serves of the user regroup and affiliate those users to the user regroup.
If the <regroup-action> element contains the string "remove" then:
1) the recipient shall follow the procedures to remove the regroup identified in the <mcptt-regroup-uri> element.
The recipient of the XML ignores any unknown element and any unknown attribute.
F.7.4 IANA registration template
Editor's Note: [enh2MCPTT-CT, CR 0529] MCC is requested to submit the IANA registration for this media type after the completion of 3GPP release 16.
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
Application
Subtype name:
vnd.3gpp.mcptt-regroup+xml
Required parameters:
None
Optional parameters:
"charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303.
Encoding considerations:
binary.
Security considerations:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.
This media type does not include provisions for directives that institute actions on a recipient's files or other resources.
This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way.
This media type does not employ compression.
Interoperability considerations:
Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.379 "Mission Critical Push To Talk (MCPTT) call control" version 16.2.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the mission critical push to talk as described in the published specification.
Fragment identifier considerations:
The handling in section 5 of IETF RFC 7303 applies.
Restrictions on usage:
None
Provisional registration? (standards tree only):
N/A
Additional information:
1. Deprecated alias names for this type: none
2. Magic number(s): none
3. File extension(s): none
4. Macintosh File Type Code(s): none
5. Object Identifier(s) or OID(s): none
Intended usage:
Common
Person to contact for further information:
- Name: <MCC name>
- Email: <MCC email address>
- Author/Change controller:
i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG
ii) Change controller: <MCC name>/<MCC email address>
Annex G (informative):
States managed by the MCPTT client and MCPTT server
G.1 MCPTT emergency state
The MCPTT emergency state is managed by the MCPTT client and MCPTT user. High-level characteristics of this state are captured in table G-1.1.
Table G.1-1: MCPTT emergency state
MCPTT emergency state
State-setting events
State-clearing events
Comments
Values:
"set": MCPTT user is in a life-threatening situation
"clear": MCPTT user is not in a life-threatening situation
Managed by:
MCPTT client and MCPTT user
MCPTT emergency alert initiated
MCPTT emergency group call initiated
MCPTT emergency private call initiated
MCPTT adhoc emergency alert initiated
MCPTT emergency adhoc group call initiated
MCPTT emergency alert cancelled (by initiator)
MCPTT emergency alert cancelled (by authorised-user)
MCPTT emergency call cancelled by initiator (if there is no outstanding MCPTT emergency alert)
MCPTT user manually clears the state
MCPTT adhoc emergency alert cancelled (by initiator)
MCPTT adhoc emergency alert cancelled (by authorised-user)
MCPTT emergency adhoc group call cancelled by initiator (if there is no outstanding MCPTT adhoc emergency alert)
While the MCPTT client is in the MCPTT emergency state, all group calls it makes will be MCPTT emergency group calls, providing the group is authorised for MCPTT emergency group calls.
While in an emergency group call while in the MCPTT emergency state, the MCPTT user is an "emergency talker" and will have pre-emptive priority over non-emergency talkers in the emergency group call.
G.2 In-progress emergency group state
This state is described in both 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3]. It is managed by the controlling MCPTT function. High-level characteristics of this state are captured in table G.2-1.
Table G.2-1: in-progress emergency group state
In-progress emergency group state values
State-entering events
Comments
"true"
acceptance by the controlling MCPTT function of an MCPTT emergency group call request (as per clause 10.6.2.6.1.1 of 3GPP TS 23.379 [3]).
"false"
initial state prior to any call activity
acceptance by the controlling MCPTT function of an MCPTT emergency group cancel request (as per clause 10.6.2.6.1.3 of 3GPP TS 23.379 [3]).
G.3 MCPTT emergency group state
The MCPTT emergency group state is the MCPTT client's perspective of the in-progress emergency group state which is managed by the controlling MCPTT function. The MCPTT emergency group (MEG) state is managed by the MCPTT client to enable the requesting of MCPTT emergency-level priority as early as possible in the origination of an MCPTT emergency group call. High-level characteristics of this state are captured in table G.3-1.
Table G.3-1: MCPTT emergency group state
MCPTT emergency group state values
State-entering events
Comments
MEG 1: no-emergency
initial state prior to any call activity
Emergency group call cancel request received on behalf of another user from the MCPTT server
Emergency group call cancel response (success) in response to initiator's request
MEG 2: in-progress
Emergency group call response received (confirm) to initiator's emergency group call request
Emergency group call request received (on behalf of another user)
In this state, all participants in calls on this group will receive emergency level priority whether or not they are in the MCPTT emergency state themselves.
MEG 3: cancel-pending
Emergency group call cancel request sent by authorized user
The controlling MCPTT server may not grant the cancel request for various reasons, e.g.if another users in an MCPTT emergency state is transmitting the media or if based on the local policy, the requesting user is not an authorized user to cancel the group emergency state.
MEG 4: confirm-pending
Emergency group call request sent by initiator
The controlling MCPTT server may not grant the call request for various reasons, e.g., the MCPTT group is not configured as being emergency-capable so it can't be assumed that the group will enter the in-progress state.
G.4 MCPTT emergency group call state
Table G.4-1 provides the semantics of the MCPTT emergency group call (MEGC) state values. This internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT emergency group calls and MCPTT emergency alerts and their cancellations.
Table G.4-1: MCPTT emergency group call state
MCPTT emergency group call state values
Semantics
Comments
MEGC 1: emergency-gc-capable
MCPTT client emergency-capable client is not currently in an MCPTT emergency group call that it has originated, nor is it in the process of initiating one.
MCPTT emergency state:
may or may not be set in this state, depending upon the MCPTT client's MEA state
MEGC 2: emergency-call-requested
MCPTT client has initiated an MCPTT emergency group call request.
MCPTT emergency state: is set
MEGC 3: emergency-call-granted
MCPTT client has received an MCPTT emergency group call grant.
If the MCPTT user initiates a call while the MCPTT emergency state is still set, that call will be an MCPTT emergency group call, assuming that group is authorised for the client to initiate emergency group calls on.
MCPTT emergency state: is set
G.5 MCPTT emergency alert state
Table G.5-1provides the semantics of the MCPTT emergency alert (MEA) state values. This is an internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT emergency group calls and MCPTT emergency alerts and their cancellations.
Table G.5-1: MCPTT emergency alert state
MCPTT emergency alert state values
State-entering events
Comments
MEA 1: no-alert
initial state
emergency alert cancelled
emergency alert request denied
emergency alerts can be cancelled in several ways:
MCPTT emergency alert cancel request with <alert-ind> set to "false" (by initiator)
MCPTT emergency alert cancel request with <alert-ind> set to "false" (by authorised user)
MCPTT emergency group call cancel request with <alert-ind> set to "false"
MCPTT emergency state: may be set or clear, depending on MCPTT emergency call status
MEA 2: emergency-alert-confirm-pending
emergency alert request sent
emergency alerts can be requested in several ways:
MCPTT emergency alert request with <alert-ind> set to "true"
MCPTT emergency group call request with <alert-ind> set to "true"
MCPTT emergency state: is set
MEA 3: emergency-alert -initiated
emergency alert response (success) received
MCPTT emergency state: is set
MEA 4: emergency-alert-cancel-pending
emergency alert cancellation request sent by alert originator
MCPTT emergency state: is clear
G.20 MCPTT adhoc group emergency alert state
Table G.20-1provides the semantics of the MCPTT adhoc group emergency alert (AH-MEA) state values. This is an internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT emergency adhoc group calls and MCPTT adhoc group emergency alerts and their cancellations.
Table G.20-1: MCPTT adhoc group emergency alert state
MCPTT adhoc group emergency alert state values
State-entering events
Comments
AH-MEA 1: no-adhoc-alert
initial state
adhoc group emergency alert cancelled
adhoc group emergency alert request denied
emergency alerts can be cancelled in several ways:
MCPTT adhoc group emergency alert cancel request with <adhoc-alert-ind> set to “false” (by initiator)
MCPTT adhoc group emergency alert cancel request with <adhoc-alert-ind> set to “false” (by authorised user)
MCPTT emergency state: may be set or clear, depending on MCPTT emergency call status
AH-MEA 2: adhoc-emergency-alert-confirm-pending
adhoc group emergency alert request sent
emergency alerts can be requested in several ways:
MCPTT adhoc group emergency alert request with < adhoc-alert-ind> set to "true"
MCPTT emergency group call request with <adhoc-alert-ind> set to "true"
MCPTT emergency state: is set
AH-MEA 3: adhoc-emergency-alert-initiated
adhoc group emergency alert response (success) received
MCPTT emergency state: is set
AH-MEA 4: adhoc-emergency-alert-cancel-pending
adhoc group emergency alert cancellation request sent by alert originator
MCPTT emergency state: is clear
G.6 In-progress imminent peril group state
This state is described in both 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3]. It is managed by the controlling MCPTT function. High-level characteristics of this state are captured in table G.6-1.
Table G.6-1: in-progress imminent peril group state
In-progress imminent peril group state values
State-entering events
Comments
"true"
acceptance by the controlling MCPTT function of an MCPTT imminent peril group call request (as per clause 10.6.2.6.2.1 and clause 10.6.2.6.2.2 of 3GPP TS 23.379 [3]).
"false"
initial state prior to any call activity
acceptance by the controlling MCPTT function of an MCPTT imminent peril group cancel request using SIP re-INVITE request while call is ongoing or using SIP MESSAGE request while no call is ongoing on the group (as per clause 10.6.2.6.2.3 of 3GPP TS 23.379 [3]).
G.7 MCPTT imminent peril group state
The MCPTT imminent peril group state is the MCPTT client's perspective of the in-progress imminent peril group state which is managed by the controlling MCPTT function. The MCPTT imminent peril group (MIG) state is managed by the MCPTT client to enable the requesting of MCPTT imminent peril-level priority as early as possible in the origination of an MCPTT imminent peril group call. High-level characteristics of this state are captured in table G.7-1.
Table G.7-1: MCPTT imminent peril group state
MCPTT imminent peril group state values
State-entering events
Comments
MIG 1: no-imminent peril
initial state prior to any call activity
Imminent peril group call cancel request received on behalf of another user from the MCPTT server
Imminent peril group call cancel response (success) in response to initiator's request
MCPTT group in-progress imminent peril state cancel notification received from the MCPTT server
MCPTT group in-progress imminent peril state cancel response (success) in response to initiator’s request
MIG 2: in-progress
Imminent peril group call response received (confirm) to initiator's imminent peril group call request
Imminent peril group call request received (on behalf of another user)
In this state, all participants in calls on this group will receive imminent peril level priority whether or not they initiated an MCPTT imminent peril group call themselves.
MIG 3: cancel-pending
Imminent peril group call cancel request sent by initiator
MCPTT group in-progress imminent peril state cancel request sent by initiator
The controlling MCPTT server may not grant the cancel request for various reasons, e.g., other users in an MCPTT imminent peril state remain in the call.
MIG 4: confirm-pending
Imminent peril group call request sent by initiator
The controlling MCPTT server may not grant the call request for various reasons, e.g., the MCPTT group is not configured as being imminent peril-capable so it can't be assumed that the group will enter the in-progress state.
G.8 MCPTT imminent peril group call state
Table G.8-1 provides the semantics of the MCPTT imminent peril group call (MIGC) state values. This internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT imminent peril group calls and their cancellations.
Table G.8-1: MCPTT imminent peril group call state
MCPTT imminent peril group call state values
Semantics
Comments
MIGC 1: imminent-peril-gc-capable
MCPTT client imminent peril-capable client is not currently in an MCPTT imminent peril group call that it has originated, nor is it in the process of initiating one.
In this state, the MCPTT imminent peril group state will be set to either "MIG 1: no-imminent-peril" or "MIG 2 in-progress" state.
MIGC 2: imminent-peril-call-requested
MCPTT client has initiated an MCPTT imminent peril group call request.
In this state, the MCPTT imminent peril group state will be set to "MIG 4: confirm-pending" if not already in the "MIG 2 in-progress" state.
MIGC 3: imminent-peril-call-granted
MCPTT client has received an MCPTT imminent peril group call grant.
In this state, the MCPTT imminent peril group state will be set to "MIG2 in-progress".
G.9 In-progress emergency private call state
This state is managed by the controlling MCPTT function. All private calls originated between an initiator and the target MCPTT user when they are in an in-progress emergency private call state are MCPTT emergency private calls until this state is cancelled, whether or not the originator of the private call is in an MCPTT emergency state.
Table G.9-1: in-progress emergency private call state
In-progress emergency private call state values
State-entering events
Comments
"true"
acceptance by the controlling MCPTT function of an MCPTT emergency private call request (as per clause 10.7.2.4.1 of 3GPP TS 23.379 [3]).
The in-progress emergency private call state applies to the call and the two MCPTT users in the call.
"false"
initial state prior to any private call activity
acceptance by the controlling MCPTT function of the cancellation of an MCPTT emergency private call (as per clause 10.7.2.4.1 of 3GPP TS 23.379 [3]).
G.10 MCPTT emergency private priority state
The MCPTT emergency private priority state is the MCPTT client's perspective of the in-progress emergency private call state which is managed by the controlling MCPTT function. The MCPTT emergency private priority (MEPP) state is managed by the MCPTT client to enable the requesting of MCPTT emergency-level priority as early as possible in the origination of an MCPTT emergency private call. High-level characteristics of this state are captured in table G.10-1.
Table G.10-1: MCPTT emergency private priority state
MCPTT emergency private priority state values
State-entering events
Comments
MEPP 1: no-emergency
initial state prior to any call activity
Emergency private call cancel request received on behalf of another user from the MCPTT server
Emergency private call cancel response (success) in response to initiator's request
MEPP 2: in-progress
Emergency private call response received (confirm) to initiator's emergency private call request
Emergency private call request received (on behalf of another user)
In this state, both participants in calls to each other will request emergency level priority whether or not they are in the MCPTT emergency state themselves.
MEPP 3: cancel-pending
Emergency private call cancel request sent by initiator
The controlling MCPTT server may not grant the cancel request for various reasons, e.g., the other user in the call is in an MCPTT emergency state.
MEPP 4: confirm-pending
Emergency private call request sent by initiator
The controlling MCPTT server may not grant the call request for various reasons, e.g., the MCPTT user is not configured as being authorised to originate an emergency private call so it can't be assumed that the call (originator and target users) will enter the in-progress state.
G.11 MCPTT emergency private call state
Table G.11-1 provides the semantics of the MCPTT emergency private call (MEPC) state values. This is an internal state of the MCPTT client and is managed by the MCPTT client. This state aids in the managing of the information elements of MCPTT emergency private calls and MCPTT emergency alerts and their cancellations.
Table G.11-1: MCPTT emergency private call state
MCPTT emergency private call state values
Semantics
Comments
MEPC 1: emergency-pc-capable
MCPTT client emergency-capable client is not currently in an MCPTT emergency private call that it has originated, nor is it in the process of initiating one.
MCPTT emergency state:
may or may not be set in this state, depending upon the MCPTT client's MPEA state and the emergency states related to MCPTT emergency group calls.
MEPC 2: emergency-pc-requested
MCPTT client has initiated an MCPTT emergency private call request.
MCPTT emergency state: is set
MEPC 3: emergency-pc-granted
MCPTT client has received an MCPTT emergency private call grant.
If the MCPTT user initiates a call while the MCPTT emergency state is still set, that call will be an MCPTT emergency private call, assuming that the initiating MCPTT user is authorised to initiate an MCPTT emergency private call to the targeted MCPTT user.
MCPTT emergency state: is set
G.12 MCPTT private emergency alert state
Table G.5-1provides the semantics of the MCPTT private emergency alert (MPEA) state values. This is an internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT emergency private calls and MCPTT emergency alerts and their cancellations. MCPTT private emergency alerts are targeted to an MCPTT user.
Table G.12-1: MCPTT private emergency alert state
MCPTT emergency alert state values
State-entering events
Comments
MPEA 1: no-alert
initial state
emergency alert cancelled
emergency alert request denied
emergency alerts targeted to an MCPTT user can be cancelled in several ways:
MCPTT emergency private call cancel request with <alert-ind> set to "false"
timeout of private call inactivity timer
end of call (if system policy)
MCPTT emergency state: may be set or clear, depending on MCPTT emergency call status
MPEA 2: emergency-alert-confirm-pending
emergency alert request sent
emergency alerts can be requested as an optional part of a MCPTT client's request to initiate an MCPTT emergency private call, in which case the request has an <alert-ind> element set to "true".
MCPTT emergency state: is set
MPEA 3: emergency-alert -initiated
emergency alert response (success) received
MCPTT emergency state: is set
MPEA 4: emergency-alert-cancel-pending
emergency alert cancellation request sent by alert originator
MCPTT emergency state: is clear
G.13 Private call call-back state information
Table G.13-1 provides the semantics of the private call call-back state values that are managed by an MCPTT client that initiates a private call call-back request or a private call call-back cancel request. Such a client is known as a requesting MCPTT client.
Table G.13-2 provides the semantics of the private call call-back state values that are managed by an MCPTT client that receives a private call call-back request or a private call call-back cancel request. Such a client is known as a target MCPTT client.
Table G.13-1: MCPTT private call call-back requesting client states
MCPTT private call call-back requesting client states
State-entering events
Comments
PCCB-I1: no-call-back
Moving from "PCCB-I4: cancel-pending" when the requesting MCPTT client receives a private call call-back cancel response from the target MCPTT client
Moving from "PCCB-I3: confirmed" when the requesting MCPTT client sends a response to a private call set-up establishment request from the target MCPTT client.
The information stored on the requesting MCPTT client for the target MCPTT user is deleted.
PCCB-I2: confirm-pending
Moving from "PCCB-I1: no call-back" when the rqeuesting MCPTT client has sent a private call call-back request and is awaiting the response back from the target MCPTT client.
Temporary state of the UE, while the UE awaits the response to the call back request from the target MCPTT client.
PCCB-I3: confirmed
Moving from "PCCB-I2: confirm-pending" when the requesting MCPTT client receives the private call call-back response from the target MCPTT client
The client stores the MCPTT ID of the remote client and the requesting client state. In this state, the client is expecting to receive a private call from the remote client.
PCCB-I4: cancel-pending
Moving from "PCCB-I3: confirmed" when the requesting MCPTT client has initiated a private call cancel request towards the target MCPTT client
Temporary state while the UE awaits the cancel response from the target MCPTT client.
Table G.13-2: MCPTT private call call-back target client states
MCPTT private call call-back target client states
State-entering events
Comments
PCCB-R1: no-call-back
Moving from "PCCB-R2: private-call-call-back-pending" upon initiating a private call to the requesting MCPTT client, and receiving the SIP 200 (OK) to the private call request.
The information stored on the target MCPTT client for the requesting MCPTT user is deleted.
PCCB-R2: private-call-pending
Moving from "PCCB-R1: no call-back" when the target MCPTT client has received a private-call call-back request from the requesting MCPTT client, and has confirmed this by sending a response to this client.
The client stores the MCPTT ID, target client state, urgency and time of request.
G.14 In-progress emergency adhoc group state
This state is described in both 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3]. It is managed by the controlling MCPTT function. High-level characteristics of this state are captured in table G.14-1.
Table G.14-1: in-progress emergency adhoc group state
In-progress emergency adhoc group state values
State-entering events
Comments
"true"
acceptance by the controlling MCPTT function of an MCPTT emergency adhoc group call request.
"false"
initial state prior to any call activity
acceptance by the controlling MCPTT function of an MCPTT emergency adhoc group call release request or MCPTT emergency adhoc group call release request sent by the controlling MCPTT function.
G.15 MCPTT emergency adhoc group state
The MCPTT emergency adhoc group state is the MCPTT client's perspective of the in-progress emergency adhoc group state which is managed by the controlling MCPTT function. The MCPTT emergency adhoc group (MEAG) state is managed by the MCPTT client to enable the requesting of MCPTT emergency-level priority as early as possible in the origination of an MCPTT emergency adhoc group call. High-level characteristics of this state are captured in table G.15-1.
Table G.15-1: MCPTT emergency adhoc group state
MCPTT emergency adhoc group state values
State-entering events
Comments
MEAG 1: no-emergency
initial state prior to any call activity
Emergency adhoc group call release request received from the MCPTT server
Emergency adhoc group call release response (success) in response to initiator's request
MEAG 2: in-progress
Emergency adhoc group call response received (confirm) to initiator's emergency adhoc group call request
Emergency adhoc group call request received (on behalf of another user)
In this state, all participants in calls on this group will receive emergency level priority whether or not they are in the MCPTT emergency state themselves.
MEAG 3: cancel-pending
Emergency adhoc group call release request sent by authorized user
The controlling MCPTT server may not grant the release request for various reasons, e.g.if another users in an MCPTT emergency state is transmitting the media or if based on the local policy, the requesting user is not an authorized user to release the adhoc group emergency call.
MEAG 4: confirm-pending
Emergency adhoc group call request sent by initiator
G.16 MCPTT emergency adhoc group call state
Table G.16-1 provides the semantics of the MCPTT emergency adhoc group call (MEAGC) state values. This internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT emergency adhoc group calls.
Table G.16-1: MCPTT emergency adhoc group call state
MCPTT emergency adhoc group call state values
Semantics
Comments
MEAGC 1: emergency-gc-capable
MCPTT client is not currently in an MCPTT emergency adhoc group call that it has originated, nor is it in the process of initiating one.
MCPTT emergency state:
may or may not be set in this state, depending upon the MCPTT client's MEA state
MEAGC 2: emergency-call-requested
MCPTT client has initiated an MCPTT emergency adhoc group call request.
MCPTT emergency state: is set
MEAGC 3: emergency-call-granted
MCPTT client has received an MCPTT emergency adhoc group call grant.
If the MCPTT user initiates a call while the MCPTT emergency state is still set, that call will be an MCPTT emergency adhoc group call, assuming that group is authorised for the client to initiate emergency adhoc group calls on.
MCPTT emergency state: is set
G.17 In-progress imminent peril adhoc group state
This state is described in both 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3]. It is managed by the controlling MCPTT function. High-level characteristics of this state are captured in table G.17-1.
Table G.17-1: in-progress imminent peril adhoc group state
In-progress imminent peril adhoc group state values
State-entering events
Comments
"true"
acceptance by the controlling MCPTT function of an MCPTT imminent peril adhoc group call request.
"false"
initial state prior to any call activity
acceptance by the controlling MCPTT function of an MCPTT imminent peril adhoc group call release request or MCPTT imminent peril adhoc group call release request sent by the controlling MCPTT function.
G.18 MCPTT imminent peril adhoc group state
The MCPTT imminent peril adhoc group state is the MCPTT client's perspective of the in-progress imminent peril adhoc group state which is managed by the controlling MCPTT function. The MCPTT imminent peril adhoc group (MIAG) state is managed by the MCPTT client to enable the requesting of MCPTT imminent peril-level priority as early as possible in the origination of an MCPTT imminent peril adhoc group call. High-level characteristics of this state are captured in table G.18-1.
Table G.18-1: MCPTT imminent peril adhoc group state
MCPTT imminent peril g adhoc roup state values
State-entering events
Comments
MIAG 1: no-imminent peril
initial state prior to any call activity
Imminent peril adhoc group call release request received from the MCPTT server
Imminent peril adhoc group call release response (success) in response to initiator's request
MIAG 2: in-progress
Imminent peril adhoc group call response received (confirm) to initiator's imminent peril adhoc group call request
Imminent peril adhoc group call request received (on behalf of another user)
In this state, all participants in calls on this group will receive imminent peril level priority whether or not they initiated an MCPTT imminent peril adhoc group call themselves.
MIAG 3: cancel-pending
Imminent peril adhoc group call release request sent by authorized user
The controlling MCPTT server may not grant the release request for various reasons, e.g., if based on the local policy, the requesting user is not an authorized user to release the Imminent peril adhoc group call.
MIAG 4: confirm-pending
Imminent peril adhoc group call request sent by initiator
G.19 MCPTT imminent peril adhoc group call state
Table G.19-1 provides the semantics of the MCPTT imminent peril adhoc group call (MIAGC) state values. This internal state of the MCPTT client and is managed by the MCPTT client. These states aid in the managing of the information elements of MCPTT imminent peril adhoc group calls.
Table G.19-1: MCPTT imminent peril adhoc group call state
MCPTT imminent peril adhoc group call state values
Semantics
Comments
MIAGC 1: imminent-peril-gc-capable
MCPTT client is not currently in an MCPTT imminent peril adhoc group call that it has originated, nor is it in the process of initiating one.
In this state, the MCPTT imminent peril adhoc group state will be set to "MIAG 1: no-imminent-peril".
MIAGC 2: imminent-peril-call-requested
MCPTT client has initiated an MCPTT imminent peril adhoc group call request.
In this state, the MCPTT imminent peril adhoc group state will be set to "MIAG 4: confirm-pending" if not already in the "MIAG 2: in-progress" state.
MIAGC 3: imminent-peril-call-granted
MCPTT client has received an MCPTT imminent peril adhoc group call grant.
In this state, the MCPTT imminent peril adhoc group state will be set to "MIAG 2: in-progress".
Annex H (informative):
On-network routing considerations
H.1 General
The following clauses summarise the identities placed into SIP headers and SIP bodies during session establishment.
H.2 Group Call
Table H.2-1 describes the contents of the SIP headers and SIP bodies inserted by MCPTT clients and MCPTT servers involved in a group call.
Table H.2-1: Routing considerations for group call
Interface
Content of SIP headers
Content of "mcptt-info" MIME body
Notes
originating MCPTT client to originating participating MCPTT function (O-PF).
Request-URI contains PSI of O-PF.
P-Preferred-Identity may contain IMPU of originating user.
"mcptt-request-uri" contains the group identity.
PSI of O-PF configured for each client.
MCPTT-id of each client is never sent in session initiation.
O-PF to controlling MCPTT function (CF).
Request-URI contains PSI of CF.
P-Asserted-Identity contains IMPU of originating user.
"mcptt-request-uri" contains the group identity.
"mcptt-calling-user-id" contains MCPTT ID of originating user.
CF finds the MCPTT ID of the originating user from the stored IMPU-MCPTT ID binding and locates the PSI of the controller that serves the group identity.
O-PF contains configuration of the PSIs of the CFs.
CF to terminating participating MCPTT function (T-PF).
Request-URI contains the address of the T-PF.
P-Asserted-Identity contains the address of the CF.
"mcptt-request-uri" contains the MCPTT ID of the terminating user.
"mcptt-calling-user-id" contains MCPTT ID of originating user.
"mcptt-calling-group-id" contains the group identity.
For each client in the group, CF maps the MCPTT-ID of the terminator to the address of the T-PF.
If the terminator is in another domain, the CF can map the MCPTT ID of the terminator to a PSI identifying a interrogating function in the partner network that is able to find the T-PF using the MCPTT ID.
CF to non-controlling MCPTT function of an MCPTT group (NCF).
Request-URI contains the PSI of the NCF.
P-Asserted-Identity contains the PSI of the CF.
"mcptt-request-uri" contains the group identity.
"mcptt-calling-user-id" contains MCPTT ID of originating user.
-
T-PF to terminating MCPTT client.
Request-URI contains the IMPU of the terminating user.
P-Asserted-Identity contains the address of the CF.
"mcptt-request-uri" contains the MCPTT ID of the terminating user.
"mcptt-calling-user-id" contains MCPTT ID of originating user.
"mcptt-calling-group-id" contains the group identity.
T-PF finds the IMPU of the terminating user from the stored IMPU-MCPTT ID binding at the time of registration.
terminating MCPTT client to T-PF (response).
as in TS 24.229.
"mcptt-called-party-id" contains contacted client's MCPTT ID.
-
T-PF to NCF (response)
as in TS 24.229
"mcptt-called-party-id" contains contacted client's MCPTT ID.
-
T-PF to CF (response).
as in TS 24.229.
"mcptt-called-user" contains contacted client's MCPTT ID.
-
NCF to CF (response)
as in TS 24.229.
-
In the case of trusted mutual aid, the NCF returns the identities of the group in a "resource-lists" MIME body.
CF to O-PF (response)
as in TS 24.229.
-
-
O-PF to originating MCPTT client (response)
as in TS 24.229.
-
-
H.3 Private Call
Table H.3-1 describes the contents of the SIP headers and SIP bodies inserted by MCPTT clients and MCPTT servers involved in a private call.
Table H.3-1: Routing considerations for private call
Interface
Content of SIP headers
Content of SIP bodies (body in brackets)
Notes
Originating MCPTT client (O-C) to originating participating MCPTT function (O-PF).
Request-URI contains the PSI of O-PF.
P-Preferred-Identity may contain IMPU of O-C.
"entry" (resource-lists) contains the MCPTT ID of the called user.
O-C contains configuration of the PSI of O-PF.
MCPTT ID of O-C is never sent in session initiation.
O-PF to controlling MCPTT function (CF).
Request-URI contains the PSI of CF.
P-Asserted-Identity contains the PSI of the O-PF.
"entry" (resource-lists) contains the MCPTT ID of the called user.
"mcptt-calling-user-id" (mcptt-info) contains the MCPTT ID of O-C.
O-PF finds the MCPTT ID of O-C from the stored IMPU-MCPTT ID binding.
O-PF contains configuration of the PSIs of the CFs for private calls.
CF to terminating participating MCPTT function (T-PF).
Request-URI contains the PSI of T-PF.
P-Asserted-Identity contains. The PSI of the CF.
"mcptt-request-uri" (mcptt-info) contains the MCPTT ID of the called user.
"mcptt-calling-user-id" (mcptt-info) contains the MCPTT ID of O-C.
CF maps the MCPTT ID of the called user to the PSI of the T-PF.
T-PF to terminating MCPTT client (T-C).
Request-URI contains the IMPU of T-C.
P-Asserted-Identity contains the PSI of the T-PF
"mcptt-request-uri" (mcptt-info) contains the MCPTT ID of T-C.
"mcptt-calling-user-id" (mcptt-info) contains the MCPTT ID of O-C.
T-PF finds the IMPU of T-C from the stored IMPU-MCPTT ID binding.
T-C to T-PF (response).
as in TS 24.229.
-
-
T-PF to CF (response).
as in TS 24.229.
-
-
CF to O-PF (response).
as in TS 24.229.
-
-
O-PF to O-C (response).
as in TS 24.229.
-
-
Annex I (normative):
MCPTT Off-Network Protocol (MONP) message coding rules
I.1 General
The following clauses describe the message coding rules for the MCPTT Off-Network Protocol (MONP).
I.2 MONP messages
I.2.1 Components of a MONP message
A standard MONP message consists of an imperative part, itself composed of a header and the rest of imperative part, followed by a non-imperative part. Both the non-header part of the imperative part and the non-imperative part are composed of successive parts referred as standard information elements.
I.2.2 Format of standard information elements
A standard IE may have the following parts, in that order:
- an information element identifier (IEI);
- a length indicator (LI);
- a value part.
A standard IE has one of the formats shown in table I.2.2-1:
Table I.2.2-1: Formats of information elements
Format
Meaning
IEI present
LI present
Value part present
T
Type only
yes
no
no
V
Value only
no
no
yes
TV
Type and Value
yes
no
yes
LV
Length and Value
no
yes
yes
TLV
Type, Length and Value
yes
yes
yes
LV-E
Length and Value
no
yes
yes
TLV-E
Type, Length and Value
yes
yes
yes
Some IEs may appear in the structure, but not in all instances of messages. An IE is then said to be present or not present in the message instance. If an IE is not present in a message instance, none of the three parts is present. Otherwise, parts must be present according to the IE format.
In the message structure, an IE that is allowed not to be present in all message instances is said not to be mandatory. Other IEs are said to be mandatory.
I.2.2.1 Information element type and value part
Every standard IE has an information element type which determines the values possible for the value part of the IE, and the basic meaning of the information. The information element type describes only the value part. Standard IEs of the same information element type may appear with different formats. The format used for a given standard IE in a given message is specified within the description of the message.
The value part of a standard IE either consists of a half octet or one or more octets; the value part of a standard IE with format LV or TLV consists of an integral number of octets, between 0 and 255 inclusive; it then may be empty, i.e., consist of zero octets; if it consists of a half octet and has format TV, its IEI consists of a half octet, too. For LV-E and TLV-E, the value part of a standard IE consists of an integral number of octets, between 0 and 65535 inclusive. The value part of a standard IE may be further structured into parts, called fields.
I.2.2.2 Length indicator
For LV or TLV, the length indicator (LI) of a standard IE consists of one octet. For LV-E and TLV-E, the LI of a standard IE consists of two octets where bit 8 of octet n contains the most significant bit and bit 1 of octet n+1 contains the least significant bit (refer to figure I.2.2.4-9 in clause I.2.2.4 for the relative ordering of the 2 octets). The LI contains the binary encoding of the number of octets of the IE value part. The LI of a standard IE with empty value part indicates 0 octets. Standard IE of an information element type such that the possible values may have different values must be formatted with a length field, i.e., LV, TLV, LV-E or TLV-E.
I.2.2.3 Information element identifier
When present, the IEI of a standard IE consists of a half octet or one octet. A standard IE with IEI consisting of a half octet has format TV, and its value part consists of a half octet. The value of the IEI depends on the standard IE, not on its information element type. The IEI, if any, of a given standard IE in a given message is specified within the description of the message. In some protocol specifications, default IEI values can be indicated. They are to be used if not indicated in the message specification. Non mandatory standard IE in a given message, i.e., IE which may be not be present (formally, for which the null string is acceptable in the message), must be formatted with an IEI, i.e., with format T, TV, TLV or TLV-E.
I.2.2.4 Categories of IEs; order of occurrence of IEI, LI, and value part
The following categories of standard information elements are defined:
- information elements of format V or TV with value part consisting of 1/2 octet (type 1);
- information elements of format T with value part consisting of 0 octets (type 2);
- information elements of format V or TV with value part that has fixed length of at least one octet (type 3);
- information elements of format LV or TLV with value part consisting of zero, one or more octets (type 4)
- information elements of format LV-E or TLV-E with value part consisting of zero, one or more octets and a maximum of 65535 octets (type 6).
NOTE: The "types" and "formats" used for MONP match those defined in 3GPP TS 24.007 [56];
Type 1 standard information elements of format V provide the value in bit positions 8, 7, 6, 5 of an octet (see figure I.2.2.4-1) or bits 4, 3, 2, 1 of an octet (see figure I.2.2.4-2).
Figure I.2.2.4-1: Type 1 IE of format V
Figure I.2.2.4-2: Type 1 IE of format V
Type 1 standard information elements of format TV have an IEI of a half octet length; they provide the IEI in bit positions 8, 7, 6, 5 of an octet and the value part in bit positions 4, 3, 2, 1 of the same octet, see figure I.2.2.4-3.
Figure I.2.2.4-3: Type 1 IE of format TV
A type 2 standard IE has format T; its IEI consists of one octet, its value part is empty, see figure I.2.2.3-4.
Figure I.2.2.4-4: Type 2 IE
A type 3 standard information element has format V or TV; if it has format TV, its IEI consists of one octet and proceeds the value part in the IE. The value part consists of at least one octet. See figure I.2.2.4-5 and figure I.2.2.4-6.
Figure I.2.2.4-5: Type 3 IE of format V (k = 0, 1, 2, ...)
Figure I.2.2.4-6: Type 3 IE of format TV (k = 1, 2, ...)
A type 4 standard information element has format LV or TLV. Its LI precedes the value part, which consists of zero, one, or more octets; if present, its IEI has one octet length and precedes the LI. See figure I.2.2.4-7 and figure I.2.2.4-8.
Figure I.2.2.4-7: Type 4 IE of format LV (k = 0, 1, 2, ...)
Figure I.2.2.4-8: Type 4 IE of format TLV (k = 1, 2, ...)
A type 6 standard information element has format TLV-E. The IEI has one octet length and precedes the LI of 2 octets and the value part which consists of zero, one or up to 65535 octets. See figure I.2.2.4-9 and figure I.2.2.4-10.
Figure I.2.2.4-9: Type 6 IE of format LV-E (k = 1, 2, ...)
Figure I.2.2.4-10: Type 6 IE of format TLV-E (k = 1, 2, ...)
I.2.2.5 Method for IE structure
Standard IEs can be further structured in parts called fields and represented in a tabular form.
The IE is presented in its maximum format, i.e., T, TV, TLV or TLV-E, in a picture representing the bits in a table, each line representing an octet. Bits appear in the occidental order, i.e., from left of the page to right of the page, and from top of the page to bottom of the page.
Boxes so delimited contains typically the field name, possibly an indication of which bits in the field are in the box, and possibly a value (e.g., for spare bits).
A specific method can be used in the IE description to describe a branching structure, i.e., a structure variable according to the value of particular fields in the IE. This design is unusual outside type 4 and type 6 IEs, and as, a design rule, should be used only in type 4 and type 6 IEs.
a) The octet number of an octet within the IE is defined typically in the table. It consists of a positive integer, possibly of an additional letter, and possibly of an additional asterisk, see clause f). The positive integer identifies one octet or a group of octets.
b) Each octet group is a self-contained entity. The internal structure of an octet group may be defined in alternative ways.
c) An octet group is formed by using some extension mechanism. The preferred extension mechanism is to extend an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit.
- The bit value "0" indicates that the octet group continues through to the next octet. The bit value "1" indicates that this octet is the last octet of the group. If one octet (Nb) is present, the preceding octets (N and Na) shall also be present.
- In the format descriptions of the individual information elements, bit 8 is marked "0/1 ext" if another octet follows. Bit 8 is marked "1 ext" if this is the last octet in the extension domain.
- Additional octets may be defined in later versions of the protocols ("1 ext" changed to "0/1 ext") and equipments shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in the formal description of the messages and of the individual information elements only takes into account this version of the protocols.
d) In addition to the extension mechanism defined above, an octet (N) may be extended through the next octet(s) (N+1, N+2 etc.) by indications in bits 7-1 (of octet N).
e) The mechanisms in c) and d) may be combined.
f) Optional octets are marked with asterisks (*). As a design rule, the presence or absence of an optional octet should be determinable from information in the IE and preceding the optional octet. Care should be taken not to introduce ambiguities with optional octets.
g) At the end of the IE, additional octets may be added in later versions of the protocols also without using the mechanisms defined in c) and d). Equipments shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in the formal description of the messages and of the individual information elements only takes into account this version of the protocols.
I.2.2.6 Imperative part of a standard MONP message
I.2.2.6.0 General
The imperative part of a standard MONP message is composed of a header possibly followed by mandatory standard IEs having the format V, LV or LV-E.
The header consists of a message type information element as specified in clause 15.2.1.
I.2.2.6.1 Standard information elements of the imperative part
The message type octet of a standard MONP message may be followed by mandatory standard IEs having the format V, LV or LV-E as specified in the message description in the relevant protocol specification.
As a design rule, octet boundaries must be respected. This implies that half-octet standard IEs (i.e., V formatted type 1 standard IEs) must appear by pair.
If message is received as a standard MONP message, and that is too short to contain the complete imperative part as specified in the relevant protocol specification, an imperative message part error is diagnosed. (The same error may be diagnosed at detection of certain contents of the imperative part of a message; this is defined in the relevant protocol specification.) The treatment of an imperative message part error is defined in the relevant protocol specification.
I.2.2.7 Non-imperative part of a standard MONP message
The imperative part of a standard MONP message may be followed by the non-imperative part. The MONP protocol specification defines where the imperative part of a standard MONP message ends. The non-imperative part of a standard MONP message is composed of (zero, one, or several) standard IEs having the format T, TV, TLV or TLV-E. The receiver of a standard MONP message shall analyse the non-imperative part as a succession of standard IEs each containing an IEI, and shall be prepared for the non-imperative part of the message to contain standard IEs that are not specified in the relevant protocol specification.
An IEI may be known in a message or unknown in a message.
An IEI that is known in a message designates the IE type of the IE the first part of which the IEI is, as well as the use of the information. Which IE type it designates is specified in the relevant protocol specification. Within a message, different IEIs may designate the same IE type if that is defined in the relevant protocol specification.
Whether the second part of an IE with IEI known in a message is the length or not (in other words, whether the IEI is the first part of an IE formatted as TLV, TLV-E or not) is specified in the relevant protocol specification.
Unless otherwise specified in the protocol specification, the receiver shall assume that IE with unknown IEI are TV formatted type 1, T formatted type 2, TLV formatted type 4 or TLV-E formatted type 6 standard IEs. The IEI of unknown IEs together with, when applicable, the length indicator, enable the receiver to determine the total length of the IE, and then to skip unknown IEs. The receiver shall assume the following rule for IEs with unknown IEI:
Bit 8 of the IEI octet is set to "1" indicates a TV formatted type 1 standard IE or a T formatted type 2 IEs. Hence, a 1 valued bit 8 indicates that the whole IE is one octet long.
Furthermore:
Bit 8 of the IEI octet set to "0" and bits 7 to 4 set to "1" indicates a TLV-E formatted type 6 IE, i.e. the following two octets are length octets. Bit 8 of the IEI octet set to "0" and bit 7 to 4 set to any other bit combination indicates a TLV formatted type 4 IE, i.e. the following octet is a length octet.
As a design rule, it is recommended that IEIs of any TV formatted type 1, T formatted type 2, TLV formatted type 4 or TLV-E formatted type 6 IE follow the rule, even if assumed to be known by all potential receivers.
A message may contain two or more IEs with equal IEI. Two IEs with the same IEI in a same message must have the same format, and, when of type 3, the same length. More generally, care should be taken not to introduce ambiguities by using an IEI for two purposes. Ambiguities appear in particular when two IEs potentially immediately successive have the same IEI but different meanings and when both are non-mandatory. As a recommended design rule, messages should contain a single IE of a given IEI.
Each protocol specification may put specific rules for the order of IEs in the non-imperative part. An IE known in the message, but at a position non-compliant with these rules is said to be out of sequence. An out of sequence IE is decoded according to the format, and, when of type 3 the length, as defined in the message for its IEI.
I.2.2.8 Presence requirements of information elements
The relevant protocol specification may define three different presence requirements (M, C, or O) for a standard IE within a given standard MONP message:
- M ("Mandatory") means that the IE shall be included by the sending side, and that the receiver diagnoses a "missing mandatory IE" error when detecting that the IE is not present. An IE belonging to the imperative part of a message has presence requirement M. An IE belonging to the non-imperative part of a message may have presence requirement M;
- C ("Conditional") means:
* that inclusion of the IE by the sender depends on conditions specified in the relevant protocol specification;
* that there are conditions for the receiver to expect that the IE is present and/or conditions for the receiver to expect that the IE is not present in a received message of a given message type; these conditions depend only on the content of the message itself, and not for instance on the state in which the message was received, or on the receiver characteristics; they are known as static conditions;
* that the receiver detecting that the IE is not present when sufficient static conditions are fulfilled for its presence, shall diagnose a "missing conditional IE" error;
* that the receiver detecting that the IE is present when sufficient static conditions are fulfilled for its non-presence, shall diagnose an "unexpected conditional IE" error.
- Only IEs belonging to the non-imperative part of a message may have presence requirement C;
- O ("Optional") means that the receiver shall never diagnose a "missing mandatory IE" error, a "missing conditional IE" error, or an "unexpected conditional IE" error because it detects that the IE is present or that the IE is not present. (There may however be conditions depending on the states, resources, etc. of the receiver to diagnose other errors.) Only IEs belonging to the non-imperative part of a message may have presence requirement O.
Unless otherwise specified the presence of an IE of unknown IEI or of an out of sequence IE shall not lead by itself to an error.
I.2.2.9 Description of standard MONP messages
This clause describes a generic description method for MONP messages, the tabular description.
A MONP message is described by a table listing the header elements and the standard IEs in the message. For each element is given:
- if applicable the IEI, in hexadecimal representation (one digit followed by and hyphen for TV formatted type 1, and two digits for the other cases);
- the name of the IE (this is used in particular for the description of conditional presence rules);
- the type of the information element, with a reference of where the internal structure of the value part is specified;
- the format of the standard IE (T, V, TV, LV, TLV, LV-E or TLV-E); and
- the length, or the range of lengths, of the whole standard IE, including when applicable the T and L parts.
The list of elements is given in the table in the order they appear in the resulting bit string, with the exception of half‑octet elements in the imperative part: half octets in a pair are inverted.
Annex J (informative):
INFO packages defined in the present document
J.1 Info package for transfer of floor requests
J.1.1 Scope
This clause contains the information required for the IANA registration of info package g.3gpp.mcptt-floor-request in accordance with IETF RFC 6086 [64].
J.1.2 g.3gpp.mcptt-floor-request info package
J.1.2.1 Overall description
When a temporary group call includes constituent MCPTT groups in partner systems where a MCPTT call is ongoing and if the floor is occupied by a participant with a permission to speak, the non-controlling MCPTT function of a MCPTT group needs to transfer information of the current speaker(s) to the controlling MCPTT function hosting the temporary group. The information is transferred in the form of a floor request.The controlling MCPTT function will then determine if the participant will be permitted to continue to speak or if the permission to speak is revoked.
J.1.2.2 Applicability
This package is used to transport a floor request from the non-controlling MCPTT function of an MCPTT group to the controlling MCPTT function hosting the temporary group.
J.1.2.3 Appropriateness of INFO Package Usage
A number of solutions were discussed for the transportation of the floor request to the controlling MCPTT function hosting the temporary MCPTT group. The solutions were:
1) Use of the session related methods (e.g. SIP 200 (OK) response to the SIP INVITE request).
2) Use of the SIP MESSAGE method.
3) Use of the SIP INFO method as described in IETF RFC 6086, by defining a new info package.
The result of the evaluation of the above solutions were:
1) To include such a large amount of data in a SIP 200 (OK) response to an SIP INVITE request could cause problems with the size of the SIP 200 (OK) response resulting in packet fragmentation.
2) The use of the SIP MESSAGE request would result in that the recommended value of size of the information transferred by the SIP MESSAGE request would be exceeded.
3) The use of SIP INFO request was found as the most appropriate solution since the SIP INFO request could be sent in the existing SIP session.
J.1.2.4 Info package name
g.3gpp.mcptt-floor-request
J.1.2.5 Info package parameters
None defined
J.1.2.6 SIP options tags
None defined
J.1.2.7 INFO message body parts
The MIME type of the message body carrying participant identities is application/vnd.3gpp.floor-request+xml. The application/vnd.3gpp.floor-request+xml MIME type is defined in 3GPP TS 24.379.
When associated with the g.3gpp.mcptt-floor-request info package, the Content-Disposition value of the message body carrying the floor request is "info-package".
J.1.2.8 Info package usage restrictions
None defined.
J.1.2.9 Rate of INFO Requests
Single INFO request generated after session set up.
J.1.2.10 Info package security considerations
The security is based on the generic security mechanism provided for the underlying SIP signalling. No additional security mechanism is defined.
J.1.2.11 Implementation details and examples
UAC generation of INFO requests: See 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
UAS processing of INFO requests: See 3GPP TS 24.379: ""Mission Critical Push To Talk (MCPTT) call control; Protocol specification"
EXAMPLE: A controlling MCPTT function hosting a temporary MCPTT group inviting a constituent MCPTT group hosted by a non-controlling MCPTT function of a MCPTT group in a partner system where an MCPTT call is ongoing with one or two of the participants granted to speak. Then the non-controlling MCPTT function of the an MCPTT group sends a SIP INFO request carrying a floor request in an application/vnd.3gpp.mcptt-floor-request+xml MIME body using the g.3gpp.mcptt-floor-request info package.
J.2 Info package for transfer of MCPTT information
J.2.1 Scope
This clause contains the information required for the IANA registration of info package g.3gpp.mcptt-info in accordance with IETF RFC 6086 [64].
J.2.2 g.3gpp.mcptt-info info package
J.2.2.1 Overall description
The MCPTT client request for MCPTT emergency call origination can also optionally request the origination of an MCPTT emergency alert. Similarly, the MCPTT client request for MCPTT emergency call cancellation can also optionally request the cancellation of an MCPTT emergency alert. A mechanism to inform the MCPTT client that one of the requested actions has been rejected by the controlling MCPTT function is needed to both inform the MCPTT user that one of their requested actions has been rejected and to keep the emergency and imminent peril related state machines maintained by the MCPTT client updated appropriately. Note that a SIP 200 OK has to be sent in the case where the MCPTT emergency call origination request or cancellation request is accepted by the controller to allow the MCPTT user to initiate the MCPTT emergency call and receive updated priority even if the accompanying MCPTT alert request is rejected.
An MCPTT client request for an MCPTT imminent peril call when the targeted MCPTT group is in an in-progress emergency state also needs special handling, as in this case, the call request will be accepted but the MCPTT client needs to be informed that the MCPTT user will be joined to an in-progress MCPTT emergency group call instead of the requested MCPTT imminent peril group call to keep the emergency and imminent peril related state machines maintained by the MCPTT client updated appropriately.
J.2.2.2 Applicability
This package is used to transport emergency call, imminent peril and emergency alert indications from the controlling function to the MCPTT client
J.2.2.3 Appropriateness of INFO Package Usage
A number of solutions were discussed for the transportation of the emergency call, imminent peril and emergency alert indications from the controlling function to the MCPTT client. The solutions were:
1) Use of the session related methods (e.g. SIP 200 (OK) response to the SIP INVITE request).
2) Use of the SIP MESSAGE method.
3) Use of the SIP INFO method as described in IETF RFC 6086, by defining a new info package.
The result of the evaluation of the above solutions were:
1) To include such a large amount of data in a SIP 200 (OK) response to an SIP INVITE request could cause problems with the size of the SIP 200 (OK) response resulting in packet fragmentation.
2) The use of the SIP MESSAGE request would result in that the recommended value of size of the information transferred by the SIP MESSAGE request would be exceeded.
3) The use of SIP INFO request was found as the most appropriate solution since the SIP INFO request could be sent in the existing SIP session.
J.2.2.4 Info package name
g.3gpp.mcptt-info
J.2.2.5 Info package parameters
None defined
J.2.2.6 SIP options tags
None defined
J.2.2.7 INFO message body parts
The MIME type of the message body carrying participant identities is application/vnd.3gpp.mcptt-info+xml. The application/vnd.3gpp.mcptt-info+xml MIME type is defined in 3GPP TS 24.379.
When associated with the g.3gpp.mcptt-info info package, the Content-Disposition value of the message body carrying mcptt information is "info-package".
J.2.2.8 Info package usage restrictions
None defined.
J.2.2.9 Rate of INFO Requests
Single INFO request generated after session set up.
J.2.2.10 Info package security considerations
The security is based on the generic security mechanism provided for the underlying SIP signalling. No additional security mechanism is defined.
J.2.2.11 Implementation details and examples
UAC generation of INFO requests: See 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
UAS processing of INFO requests: See 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification"
EXAMPLE: A controlling MCPTT function will receive a SIP INVITE request or SIP (re-)INVITE request containing a request for an emergency call (with or without an alert) or an imminent peril call. When an emergency call has been authorised but an optional request for an emergency alert has been determined to be unauthorised, the controller will respond with a SIP 200 (OK) response to indicate acceptance of the call request and return an indication of the rejection of the emergency alert request in a SIP INFO request carrying the application/vnd.3gpp.mcptt-info+xml MIME body using the g.3gpp.mcptt-info info package.
Annex K (informative):
IANA UDP port registration form
This annex contains information to be provided to IANA for MCPTT Off-Network Protocol (MONP) UDP port registration. The following information is to be used to register MONP user port number and service name in the "IANA Service Name and Transport Protocol Port Number Registry" and specifically "Service Name and Transport Protocol Port Number Registry". This registration form can be found at: https://www.iana.org/form/ports-services.
Assignee Name
<MCC name>
Assignee E-mail
<MCC email address>
Contact Person
<MCC name>
Contact E-mail
<MCC email address>
Resources required
Port number and service name
Transport Protocols
UDP
Service Code
Service Name
3gpp-monp
Desired Port Number
Description
Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) is a 3GPP control protocol used by a MCPTT client hosted on a User Equipment (UE). MONP facilitates the MCPTT public safety service between MCPTT clients hosted on UEs communicating using IP using a single physical network segment, separated from Internet and any other IP network. The network segment is wireless network segment and UEs are mobile devices. The MCPTT public safety service offers half-duplex voice communication.
Reference
3GPP TS 24.379
Defined TXT keys
N/A
If broadcast/multicast is used, how and what for?
When performing off-network group calls, the MCPTT client initiates the group call to an MCPTT Group by sending a group call announcement message. The group call announcement message is a Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) message which is sent as a UDP message to a multicast IP address of the MCPTT group so that it is ensured that the MONP messages sent for the corresponding MCPTT group are only received by the MCPTT group's members.
If UDP is requested, please explain how traffic is limited, and whether the protocol reacts to congestion.
The number of Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) messages that need to be sent between MCPTT clients depends upon the number of members of the MCPTT group. MONP employs a back-off mechanism to defer transmission of another MONP message once a MONP message is received. MONP controls the number of messages transmitted within a certain, configurable amount of time, thus averting congestion. At maximum a few MONP messages per second are expected in communication between MCPTT clients. MONP does not support any reaction to congestion.
If UDP is requested, please indicate whether the service is solely for the discovery of hosts supporting this protocol.
Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) is not used solely for discovery of hosts supporting this protocol.
Please explain how your protocol supports versioning.
Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) does not support versioning.
If your request is for more than one transport, please explain in detail how the protocol differs over each transport.
N/A
Please describe how your protocol supports security. Note that presently there is no IETF consensus on when it is appropriate to use a second port for an insecure version of a protocol.
Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) does not support security. MONP relies on the security mechanisms of the lower layers.
Please explain why a unique port assignment is necessary as opposed to a port in range (49152-65535) or existing port.
As a general principle, 3GPP protocols use assigned User Ports, e.g. GTP-C uses UDP port number 2123, GTP-U uses UDP port number 2152, S1AP uses SCTP port number 36412, X2AP uses SCTP port number 36422, WLCP uses 36411. A dynamic port number (i.e. 49152 to 65535) cannot be used for the Mission Critical Push To Talk over LTE (MCPTT) Off-Network Protocol (MONP) because of the nature of communication on a single physical network segment, separated from Internet and any other IP network. The requirement of MONP to continuously listen for incoming messages needs an always active listener port. There is no local server that is administering the use of emphemeral ports in the MONP architecture, so there would be no way for one MCPTT client to know that a port is already being used by another MCPTT client. Communication can potentially be long-lived and MCPTT clients could leave and rejoin the calls.
Please explain the state of development of your protocol.
Protocol Standard definition. No implementation exists yet.
If SCTP is requested, is there an existing TCP and/or UDP service name or port number assignment? If yes, provide the existing service name and port number.
N/A
What specific SCTP capability is used by the application such that a user who has the choice of both TCP (and/or UDP) and SCTP ports for this application would choose SCTP? See RFC 4960 section 7.1.
N/A
Please provide any other information that would be helpful in understanding how this protocol differs from existing assigned services
This protocol is between the UEs communicating using IP over a single physical network segment, separated from Internet and any other IP network. An MCPTT public safety service offered by the MCPTT clients hosted by the UEs is for public safety. The MCPTT public safety service offers half-duplex voice communication.
This differs from existing protocols in 3GPP where UDP ports have been requested, as those protocols have been either between the UE and network or between network elements.
Annex L (normative):
MCPTT session control specific concepts for the support of mission critical services over 5GS
L.1 General
The present document applies to both EPS and 5GS. This annex lists the aspects of MCPTT session control protocols which are different in 5GS from EPS. Certain aspects that are only applicable to EPS are described in clause L.2. A mapping of EPS-specific terms to their 5GS equivalents is provided in clause L.3.
L.2 Aspects not applicable to 5GS
The following aspects of EPS mentioned in the present document are not applicable to 5GS:
- Proximity-services (ProSe) and the corresponding procedures are replaced by 5G ProSe and the corresponding procedures in 5GS; and
- Multimedia Broadcast and Multicast Service (MBMS) and the corresponding procedures.
L.3 Mapping of EPS-specific terms to 5GS
L.3.1 Session aspects
In 5GS, the PDU session is the equivalent of a PDN connection in EPS. The requirements and configurations for a PDN connection throughout this document shall also apply to PDU sessions.
L.3.2 Bearer aspects
When using the 5GS, a bearer is provided by a 5GS QoS flow. The requirements, procedures, and configurations for a bearer throughout this document, including those stating EPS explicitly (e.g., EPS bearer priority), shall also apply to QoS flows.
L.3.3 Resource sharing
In 5GS, the exchange of the QoS characteristics of the required resources takes place by means of direct interaction between SIP core and PCF using N5 reference point or Rx reference point or indirectly utilizing N33 reference point between MC service server and NEF. Thus, the requirements for resource sharing of clause 8 apply with the following clarifications:
1) to control resource sharing, interfacing to PCF is using the N5 reference point or the Rx reference point;
2) optionally, QoS characteristics for resources can be exchanged indirectly utilizing N33 reference point between the MC service server and NEF.
L.3.4 Mapping of MBMS terms to MBS
In the EPS, using the MBMS procedures, in the 5GS or eMBMS and 5G MBS co- existence, using the MBS procedures;
- in the MBS procedures, references to 4G "MBMS" is understood to be references to 5G "MBS";
- in the MBS procedures, references to 4G "TMGI" is understood to be references to 5G "MBS session ID";
- in the MBS procedures, references to 4G "application/vnd.3gpp.mcptt-mbms-usage-info+xml" is understood to be references to 5G "application/vnd.3gpp.mcptt-mbs-usage-info+xml";
- in the MBS procedures, references to 4G "MBMS suspension" corresponds to 5G "MBS session de-announcement"; and
- in the MBS procedures, "Map Group To Session Stream" corresponds to the "Map Group To Bearer" in eMBMS, as specified in 3GPP TS 23.289 [92].
L.3.5 Mapping of ProSe terms to 5G ProSe
The procedures defined in this specification are reused for off-network communication and on-network communication (i.e. UE-to-network relay) for MCPTT service over 5G ProSe with the following differences:
- ProSe direct discovery for public safety shall be replaced with 5G ProSe direct discovery, as specified in 3GPP TS 24.554 [94].
- ProSe direct communication shall be replaced with 5G ProSe direct communication, as specified in 3GPP TS 24.554 [94].
- ProSe UE-to-network relay shall be replaced with 5G ProSe UE-to-network relay, as specified in 3GPP TS 24.554 [94].
- One-to-one ProSe direct communication for Public Safety shall be replaced with unicast mode 5G ProSe direct communication for Public Safety, as specified in 3GPP TS 24.554 [94].
- One-to-many ProSe direct communication for Public Safety shall be replaced with groupcast mode 5G ProSe direct communication for Public Safety, as specified in 3GPP TS 24.554 [94].
- PPPP (ProSe Per-Packet Priority) shall be replaced with PQI, as specified in 3GPP TS 24.554 [94].
Annex M (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2015-07
Initial version.
-
0.0.0
2015-08
Implementation of the following P-CRs from CT1#92-bis MCPTT: C1ah-150007; C1ah-150042; C1ah-150046
0.0.0
0.1.0
2015-08
Implementation of the following P-CRs from CT1#93: C1-152952; C1-152956; C1-153125; C1-153177; C1-153178; C1-153179; C1-153180; C1-153220; C1-153229 ;changes by Rapporteur
0.1.0
0.2.0
2015-08
Minor fixes from the rapporteur
0.2.0
0.2.1
2015-09
Modifying the cover sheet to add the TS number and replacing MCPTT TS references with their allocated numbers. Changes by the rapporteur.
0.2.1
0.2.2
2015-10
Implementation of the following P-CRs from CT1#94: C1-153730; C1-153736; C1-153739; C1-153740; C1-154748; C1-153749; C1-153750; C1-153751; C1-153762;C1-153763; C1-153764; C1-153765; C1-153766; C1-153802; C1-153804; C1-153805; C1-153926; C1-153975;
0.2.2
0.3.0
2015-11
Implementation of the following P-CRs from CT1#95: C1-154472; C1-154473; C1-154326; C1-154480; C1-154103; C1-154477; C1-154478; C1-154479; C1-154858; C1-154355; C1-154398; C1-154535; C1-154536; C1-154537; C1-154539; C1-154540; C1-154542; C1-154544; C1-154548; C1-154549; C1-154550; C1-154552; C1-154553; C1-154712; C1-154715; C1-154716; C1-154717; C1-154731; C1-154732;C1-154399; C1-154401; Editorial changes by rapporteur.
0.3.0
0.4.0
2015-11
Minor editorial fixes from the rapporteur
0.4.0
0.4.1
2015-12
CT-70
CP-150733
Version 1.0.0 created for presentation for information
0.4.1
1.0.0
2016-01
Implementation of the following P-CRs from CT1#95-bis: C1-160322; C1-160323; C1-160326; C1-160380; C1-160392; C1-160393; C1-160394; C1-160395; C1-160396, C1-160397; C1-160400; C1-160414; C1-160415; C1-160416; C1-160417; C1-160418; C1-160419; C1-160420; C1-160421; C1-160422; C1-160423; C1-160453, C1-160455; C1-160456; C1-160457; C1-160458; C1-160466; C1-160489; C1-160490; C1-160491; C1-160612; C1-160617; C1-160770; Editorial changes by rapporteur.
1.0.0
1.1.0
2016-02
(1) Implementation of the following P-CRs from CT1 MCPTT-adhoc: C1ah-160039; C1ah-160074; C1ah-160075; C1-ah160080; C1ah-160083; C1ah-160100; C1ah-160101; C1ah-160102; C1ah-160107; C1ah-160108;
(2) Implementation of the following P-CRs from CT1#96: C1-161042; C1-161045; C1-161047; C1-161048; C1-161050; C1-161058; C1-161108; C1-161109; C1-161139; C1-161206; C1-161208; C1-161209; C1-161212; C1-161213; C1-161214; C1-161234; C1-161302; C1-161304; C1-161305; C1-161308; C1-161312; C1-161357; C1-161358; C1-161359; C1-161360; C1-161361; C1-161364; C1-161366; C1-161367; C1-161368; C1-161369; C1-161389; C1-161390; C1-161391; C1-161393; C1-161394; C1-161395; C1-161396; C1-161438; C1-161439; C1-161440; C1-161441; C1-161505; C1-161507; C1-161508; C1-161512; C1-161520; C1-161521.
(3) Editorial changes by rapporteur.
1.1.0
1.2.0
2016-02
Further corrections by rapporteur
1.2.0
1.2.1
2016-03
CT-71
CP-160059
Version 2.0.0 created for presentation for approval
1.2.1
2.0.0
2016-03
CT-71
Version 13.0.0 created after approval
2.0.0
13.0.0
2016-03
Minor editorial changes from TS rapporteur
13.0.0
13.0.1
2016-06
CT-72
CP-160322
0001
1
Subscription to the conference package
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0011
Removing editor's note about MBMS and broadcast group call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0002
1
Triggering conference event subscription – controlling MCPTT function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0003
1
Triggering conference event subscription – non-controlling MCPTT function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0004
1
Triggering conference event subscription – MCPTT client
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0005
1
Rejoin, join or late entry procedures added in non-controlling MCPTT function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0006
1
Clarifying SDP procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0007
1
Cleaning the usage of multipart/mixed content type
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0008
1
URIs in SIP responses clarification
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0010
3
Automatic commencement for On-Demand session clarifications
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0012
1
Automatic commencement for pre-established session clarification
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0013
Removing text about REFER in controlling MCPTT function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0014
3
Manual Commencement Mode corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0015
Correcting the use of <mcptt-calling-group-id>
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0016
Removing isfocus in responses from non-controlling MCPTT function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0017
4
Temporary group flows as a result of group regrouping
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0018
1
Corrections in affiliation procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0019
5
Corrections to call control
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0020
3
24.379 rel-13 Off-network Call Merge
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0021
2
24.379 rel-13 Off-network Emergency alert
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0022
Off-network implicit downgrade timer
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0023
2
24.379 rel-13 Off-network mandatory floor control in private calls
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0024
2
24.379 rel-13 Off-network message format alignment
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0025
3
24.379 rel-13 Off-network editor's notes
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0026
2
Corrections to clauses 4 to 12
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0028
2
Location procedures edits and cross reference fix
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0030
2
MBMS corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0032
2
Annex B corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0035
1
Alignment of XML schema for extensibility
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0034
1
The meaning of the word, see, when used in F.3.3
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0036
1
MIME body corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0037
2
Annex H corrections and modifications
13.0.1
13.1.0
2016-06
CT-72
C1-162029
0038
1
MCPTT Session Identity clarification
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0039
Replace the use of "this document" with "the present document"
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0040
2
Correct the specification of the acknowledged call setup timer
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0041
2
Correct the specification of the in-progress emergency group call timer.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0042
Compliance Statement
13.0.1
13.1.0
2016-06
CT-72
CP-160342
0043
3
Correct authorisation to join a group call or initiate a group call.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0044
Affiliation Check
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0045
2
Modifications to use of non-controlling function
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0046
Private Call Corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0047
1
Setting the P-Asserted-Identity in responses from the terminating participating MCPTT function.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0048
Remove privacy requirements using SIP Privacy header field
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0049
4
Out of dialog REFER and no implicit subscription.
13.0.1
13.1.0
2016-06
CT-72
CP-160343
0050
3
MCPTT identities used in pre-established sessions
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0051
Correct the encoding of the "purpose tag" in the PCK.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0052
Functional description of MONP
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0053
5
General procedure for confidentiality protection of specific XML elements.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0054
4
General procedure for integrity protecting XML documents
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0055
3
Corrections to SIP PUBLISH
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0056
5
Descriptive text on MCPTT emergency alert clause 4.6.3
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0057
5
Emergency alert client procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0058
3
Emergency alert participating and controlling function procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0059
4
Descriptive text on MCPTT imminent peril call Clause 4.6.4
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0060
4
Client originating procedures for on-demand priority calls
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0061
4
Participating MCPTT functions modifications for on-demand priority calls and alerts
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0062
5
Chat controlling function emergency and imminent peril updates
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0063
4
MCPTT prearranged controlling function updates for emergency and imminent peril origination
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0064
4
Terminating MCPTT client receives a SIP INVITE request or SIP re-INVITE for an MCPTT group call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0065
3
Origination MCPTT client SIP REFER updates for MCPTT emergency and imminent peril group calls
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0067
4
Descriptive text on MCPTT emergency private call - clause 4.6.2
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0068
4
Description of imminent peril states
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0070
2
Definition of content for the User location IE and removal of EN
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0071
Removing several editor's note
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0073
4
Alignment of commencement mode determination with answer mode settings delivered by the MCPTT client
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0075
1
Correcting MCPTT address to MCPTT ID
13.0.1
13.1.0
2016-06
CT-72
CP-160359
0076
3
P-Asserted-Identity added in the Referred-By header field
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0077
1
mcptt-group-id changed to mcptt-calling-group-id in annex H
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0078
1
Changing from 2xx to 200 OK when sending a response
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0079
1
Hiding of the MCPTT ID in MBMS listening status report
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0080
1
MBMS usage procedure error corrections
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0082
2
O-PF private call authorisations for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0083
2
Alignment of XML schemas in annex F of 24.379
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0084
1
O-PF group call authorisations commencement mode actions
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0085
1
T-PF private call commencement mode for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0086
1
T-PF group call commencement mode for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0087
1
Originating client private call modifications for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0088
1
Terminating client private call modifications for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0089
1
Terminating client group call modifications for on-demand call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0090
1
Maximum number of simultaneously received group calls (N6)
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0091
Referring to on-network-max-participant-count in TS 24.381
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0092
Correcting names of XML elements "disabled" and "invite-members"
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0093
Correcting name of "required" XML element
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0094
1
Missing procedures of originating PF of authorized MCPTT user
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0095
1
The g.3gpp.icsi-ref media feature tag included in the Contact header field
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0096
2
Clarifications on calling a temporary group
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0097
1
Adding use of "preferred-voice-encodings" to SDP procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0098
Adding use of "on-network-minimum-number-to-start" element to group procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0099
1
Implementing conditions for maximum duration of on-network group call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0100
1
Handling the current speaker during group regrouping
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0101
1
MBSFN Area Id: Alt-1 (Removal from call control specification)
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0103
1
MCPTT client origination procedures for on-demand private emergency call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0104
1
MCPTT client termination procedures for on-demand private emergency call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0105
1
MCPTT participating function procedures for private emergency call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0106
1
MCPTT controlling function procedures for private emergency call
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0107
Correcting subsequent request procedures
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0108
1
Switching from MBMS bearer to unicast bearer based on MBMS listening status
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0110
2
Completion of Pre-established Session General
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0111
2
Completion of Pre-established Session Establishment
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0112
3
Completion of Pre-established Session Modification
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0122
MBMS Service Area ID alignment
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0114
2
Pre-established Session Release
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0115
1
Off-network - Corrections to private call security context
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0116
1
Off-network - Correction to state machines
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0117
1
Off-network - Corrections to timers and counters.
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0118
Removal of unused warning texts from clause 4.4.2
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0119
Description of emergency private call states
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0120
MCPTT server procedures for prearranged priority call re-INVITEs
13.0.1
13.1.0
2016-06
CT-72
CP-160322
0123
Reference number not implemented
13.0.1
13.1.0
2016-06
CT-72
Various corrections
13.1.0
13.1.1
2016-09
CT-73
CP-160439
0125
2
Emergency group call cancel procedure updates for authorised users
13.1.1
13.2.0
2016-09
CT-73
CP-160556
0126
2
MCPTT state management and authorisation corrections for priority calls
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0127
1
Introducing priority sharing in participating MCPTT function
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0128
1
Resolving an editor's note about broadcast group call
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0129
1
Terminating subscription to the event package
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0130
1
Removing errors in re-INVITE and UPDATE procedures
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0131
Authorizing MCPTT clients in constituent groups in non-controllers that do not expose group members, when initiating a temporary group session
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0132
1
Clarifying the sending of SIP NOTIFY request during release of temporary group call
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0133
1
Updating the release policy for chat group
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0134
Moving overriding speaker - call control part
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0135
2
Pre-established session functionality for emergency and imminent peril calls.
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0136
MCPTT client ID
13.1.1
13.2.0
2016-09
CT-73
CP-160498
0137
2
Confidentiality of URIs in XML attributes
13.1.1
13.2.0
2016-09
CT-73
CP-160557
0139
2
Removal of Editor's Notes related to emergency functionality and possible optimizations
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0140
Resolution of Editor's Notes related to priority mechanisms
13.1.1
13.2.0
2016-09
CT-73
CP-160504
0141
2
Assignment of Resource Priority header field values
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0143
EN: Coding of <Configuration> element
13.1.1
13.2.0
2016-09
CT-73
CP-160499
0144
1
EN: Reference regarding mission critical organization.
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0145
1
EN: Resource-Share and INVITE without SDP
13.1.1
13.2.0
2016-09
CT-73
CP-160514
0146
Reference update draft-holmberg-dispatch-mcptt-rp-namespace
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0147
Update the use of configuration for signalling protection
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0148
1
Description of encryption of elements and attributes in pre-established sessions
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0149
Admitting a higher priority user to a call that has reached its max users
13.1.1
13.2.0
2016-09
CT-73
CP-160440
0150
1
Emergency Indications currently in SIP 200 (OK) to SIP INVITE requests need to be in SIP INFO requests
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0151
Corrections for max simultaneous sessions
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0152
1
Solving general editor's notes and removing solved editor's notes
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0153
Removal of editor's notes related to id hiding
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0154
Management of media resource allocation for pre-established sessions
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0155
Remove privacy requirements from Rel-13 MCPTT
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0156
XML schema changes to accommodate confidentiality protection
13.1.1
13.2.0
2016-09
CT-73
CP-160498
0157
2
XML schema changes to accommodate integrity protection
13.1.1
13.2.0
2016-09
CT-73
CP-160542
0158
5
MCPTT Service Continuity
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0160
2
IP address and port number for media stream
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0162
1
Authorization checks
13.1.1
13.2.0
2016-09
CT-73
CP-160496
0163
Removal of editor's note on call probe
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0165
1
Max duration of the calls
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0166
Restrict notification of call failure reason for private call
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0167
1
Timer TFB3
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0168
1
IANA Registration form for UDP Port number for MONP messages
13.1.1
13.2.0
2016-09
CT-73
CP-160497
0169
Error in authorization reference
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0170
2
MCPTT session identity and subscription to conference events
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0171
3
Completion of Pre-established session
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0172
1
Resolution of Editor's Note on NATs
13.1.1
13.2.0
2016-09
CT-73
CP-160500
0176
Downloading MCPTT user profile when receiving the service settings
13.1.1
13.2.0
2016-09
CT-73
CP-160558
0177
Alignment with MCPTT user profile document in TS 24.384
13.1.1
13.2.0
2016-12
CT-74
CP-160731
0178
Addition of MCPTT client id to SIP requests, correction of <originated-by> XML element definition
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0179
Missing user info entry addition
13.2.0
13.3.0
2016-12
CT-74
CP-160756
0180
4
Corrections for missing implicit affiliation functionality
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0181
1
MBMS transmission usage procedure corrections
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0182
Modify emergency authorisations
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0183
1
Broadcast group calls
13.2.0
13.3.0
2016-12
CT-74
CP-160732
0184
Solving Editor's Notes on Priority
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0185
Implicit Floor Request sent in Re-INVITE requests
13.2.0
13.3.0
2016-12
CT-74
CP-160732
0187
4
Transport MKFC from CF to PF in session set-up
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0189
4
SAI and QCI in the MBMS announcement
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0191
Reference update draft-holmberg-dispatch-mcptt-rp-namespace
13.2.0
13.3.0
2016-12
CT-74
CP-160689
0193
2
Corrections to implicit downgrade timers
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0194
1
Handling the ARP of an MBMS bearer in emergency update
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0197
3
Identification of pre-selected MCPTT user profile at the MCPTT server
13.2.0
13.3.0
2016-12
CT-74
CP-160732
0198
1
SIP 403 should not indicate "partial success".
13.2.0
13.3.0
2016-12
CT-74
CP-160190
0199
3
Adding missing implicit affiliation at service authorisation
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0201
Correct Imminent Peril call perfect case state transistion
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0202
1
Corrections to broadcast group call state machine
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0203
Misinterpretations caused by UE roles in titles of clauses in clause 10.2.2.4
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0205
1
Priority call origination using pre-established sessions
13.2.0
13.3.0
2016-12
CT-74
CP-160731
0206
1
PF providing MSCCK and MSCCK-ID to served UEs
13.2.0
13.3.0
2012-09
CT-74
CP-160743
0142
1
Correction to SDP media level parameters for floor control in SIP signalling flows
13.3.0
14.0.0
2016-12
CT-74
CP-160743
0188
Inaccurate representation of application/vnd.3gpp.mcptt-signed+xml MIME body
13.3.0
14.0.0
2016-12
CT-74
CP-160743
0190
Key terminology clarifications
13.3.0
14.0.0
2016-12
CT-74
CP-160743
0196
When to send "not listening to the MBMS subchannels"
13.3.0
14.0.0
2016-12
CT-74
CP-160743
0204
1
Security related definitions
13.3.0
14.0.0
2017-03
CT-75
CP-170114
0208
Corrections in affiliation procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0210
Correction of the tag name used for location
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0211
4
Distinction of requests at the MCPTT client and the MCPTT server for private call call-back
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0212
Request-URI of incoming INVITE should not contain the IMPU
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0213
Removal of redundant procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0215
P-Asserted-Service missing from SIP MESSAGE requests from the controlling MCPTT function.
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0217
1
Contact header field must not be included in SIP MESSAGE or in 2xx response to SIP MESSAGE.
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0219
1
Message body must not be included in a 2xx response to SIP MESSAGE.
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0220
Corrections to Appendix H.3
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0221
1
Corrections to user location
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0223
1
Corrections to SIP NOTIFY
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0224
1
Modifying references in TS 24.379 to cater for rel-14 Stage 1, 2 and Stage 3 mission critical restructure
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0228
1
Reference update draft-holmberg-dispatch-mcptt-rp-namespace
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0229
1
Private Call Call-Back general procedures and client procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0230
1
Private Call Call-Back PF procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0231
1
Private Call Call-Back CF procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0232
1
Private Call Call-Back states in the UE
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0233
1
Private Call Call-Back XML modifications
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0236
First-to-answer call XML modifications
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0237
1
First-to-answer call client procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170070
0238
2
First-to-answer call participating function procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0239
1
First-to-answer call controlling function procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170069
0241
2
Removal of bodies from 200 OK messages sent from the terminating client
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0242
1
SIP 200 (OK) to SIP INFO request not specified
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0243
1
Removal of "hanging paragraphs" and other editorials
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0244
1
The wrong steps are referenced in procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170115
0245
1
Resource-Priority header should not be included in SIP MESSAGE.
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0246
1
Terminology of "join", "initiates", "establishes" and "re-join" needs to be explained
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0247
1
Replace "this MCPTT user" with "the MCPTT user"
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0248
2
Ambient listening call client originating procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0249
2
Ambient listening call client release procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0250
2
Ambient listening call participating function procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0251
2
Ambient listening call controlling function procedures
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0252
1
Ambient listening call definitions
14.0.0
14.1.0
2017-03
CT-75
CP-170125
0253
1
Ambient listening xml changes
14.0.0
14.1.0
2017-03
CT-75
CP-170073
0254
2
Indicating the selected User Profile
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0257
Correction of client usage of RPH
14.0.0
14.1.0
2017-03
CT-75
CP-170114
0259
1
Corrections to off-network emergency alert timers
14.0.0
14.1.0
2017-03
CT-75
CP-170056
0260
Correction of mislabeled states
14.0.0
14.1.0
2017-03
CT-75
CP-170127
0262
Correction of timer name for offnetwork emergency alert
14.0.0
14.1.0
2017-03
CT-75
CP-170240
0267
1
"monp" already used as a service-name in the IANA Service Name and Transport Protocol Port Number Registry
14.0.0
14.1.0
2017-03
CT-75
CP-170210
0269
Issue found with existing IANA XML MIME type registration forms in TS 24.379
14.0.0
14.1.0
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2017-06
CT-76
CP-171066
0272
1
A
Correction for imminent peril cancellation
14.2.0
2017-06
CT-76
CP-171066
0274
1
A
Correction of emergency alert cancellation procedures
14.2.0
2017-06
CT-76
CP-171079
0275
1
F
Correction of FTAC emergency handling for terminating clients
14.2.0
2017-06
CT-76
CP-171066
0277
A
Missing chat session release procedures and corrected release policy
14.2.0
2017-06
CT-76
CP-171079
0278
2
B
Client procedures for ambient listening call using pre-established sessions
14.2.0
2017-06
CT-76
CP-171079
0279
2
B
Participating function procedures for ambient listening call using pre-established sessions
14.2.0
2017-06
CT-76
CP-171079
0280
4
B
Client procedures for remote change of selected group
14.2.0
2017-06
CT-76
CP-171079
0281
3
B
Participating function procedures for remote change of selected group
14.2.0
2017-06
CT-76
CP-171079
0282
3
B
Controlling function procedures for remote change of selected group
14.2.0
2017-06
CT-76
CP-171066
0284
A
Reference update draft-holmberg-dispatch-mcptt-rp-namespace
14.2.0
2017-06
CT-76
CP-171079
0287
1
B
Ambient listening on-demand client authorisation procedures
14.2.0
2017-06
CT-76
CP-171079
0288
1
B
Ambient listening on-demand PF authorisation procedures
14.2.0
2017-06
CT-76
CP-171066
0290
A
Corrections to mcpttinfo schema
14.2.0
2017-06
CT-76
CP-171093
0291
2
B
Response-Source header field handling completion
14.2.0
2017-06
CT-76
CP-171066
0293
1
A
Corrections to off-network private call
14.2.0
2017-06
CT-76
CP-171079
0294
1
B
Floor control updates for ambient listening call
14.2.0
2017-06
CT-76
CP-171066
0296
A
Correction of priority call request validation
14.2.0
2017-06
CT-76
CP-171079
0297
2
B
MBMS bearer suspension
14.2.0
2017-06
CT-76
CP-171079
0298
1
B
Update of AL server-initiated release
14.2.0
2017-06
CT-76
CP-171079
0299
1
B
Addition of authorisation checks for FTAC
14.2.0
2017-06
CT-76
CP-171079
0300
2
F
Implementation of CSK 'key download' procedure
14.2.0
2017-06
CT-76
CP-171079
0302
1
C
Correct and align MCPTT Registration and Service Authorisation procedure with MCVideo and MCData
14.2.0
2017-06
CT-76
CP-171066
0304
3
A
Resource Sharing with pre-established sessions
14.2.0
2017-06
CT-76
CP-171079
0307
1
F
Introduction of KMS URI
14.2.0
2017-06
CT-76
CP-171066
0309
A
Correct (De-)affliation schema
14.2.0
2017-09
CT-77
CP-172093
0311
A
Correction of missing mcptt-client-id in SIP REGISTER
14.3.0
2017-09
CT-77
CP-172101
0312
B
Addition of eMCPTT definitions
14.3.0
2017-09
CT-77
CP-172101
0313
2
F
Key management for first-to-answer call
14.3.0
2017-09
CT-77
CP-172093
0315
A
Terminating procedure for Re-join corrected
14.3.0
2017-09
CT-77
CP-172093
0317
A
Missing procedures and incorrect referencing for private call client procedures
14.3.0
2017-09
CT-77
CP-172093
0320
1
A
Last call type change time
14.3.0
2017-09
CT-77
CP-172093
0322
1
A
Stored call start time of the call
14.3.0
2017-09
CT-77
CP-172093
0324
A
tCoordinateType
14.3.0
2017-09
CT-77
CP-172094
0326
1
A
Timer TFG13
14.3.0
2017-09
CT-77
CP-172093
0328
A
Key-mgmt attribute
14.3.0
2017-09
CT-77
CP-172093
0330
A
SDP for Private call
14.3.0
2017-09
CT-77
CP-172094
0334
3
A
Essential correction to MBMS Bearer Announcement Message
14.3.0
2017-09
CT-77
CP-172101
0335
2
F
Send one MBMS Bearer Announcement Message per TMGI intended for GPMS
14.3.0
2017-09
CT-77
CP-172094
0336
Corrections to off-network call control procedures
14.3.0
2017-09
CT-77
CP-172093
0338
1
A
Coding Error ABNF for the Warning text
14.3.0
2017-09
CT-77
CP-172094
0340
1
A
Correction of state naming for MIG 3, and MIG 4
14.3.0
2017-09
CT-77
CP-172093
0342
A
Correction of identifier mcptt calling user id
14.3.0
2017-09
CT-77
CP-172094
0344
1
A
Correction of identifier for <imminentperil-ind>
14.3.0
2017-09
CT-77
CP-172094
0346
1
A
Correction of cross referenced steps
14.3.0
2017-09
CT-77
CP-172101
0349
1
B
KMS URI update for off network operations
14.3.0
2017-09
CT-77
CP-172094
0351
1
A
Addition of Registration without Auth Token
14.3.0
2017-09
CT-77
CP-172101
0353
1
F
MBMS Bearer Management by the MCPTT participation function
14.3.0
2017-12
CT-78
CP-173063
0358
F
Replace obsolete references to 33.179 with updated references to 33.180
14.4.0
2017-12
CT-78
CP-173063
0359
F
Introduction of MuSiK for alignment with Rel-14 security procedures
14.4.0
2017-12
CT-78
CP-173063
0360
2
F
Removal of MKFC processing as part of replacing MKFC wit h MuSiK
14.4.0
2017-12
CT-78
CP-173053
0361
2
A
Addition of missing warning code 136 for I_MESSAGE authentication failure
14.4.0
2017-12
CT-78
CP-173053
0363
1
A
Correction and clarification of XML integrity protection
14.4.0
2017-12
CT-78
CP-173053
0365
1
A
Location correction for emergency alert
14.4.0
2017-12
CT-78
CP-173053
0367
1
A
Off-network call type control procedures: merge of two calls
14.4.0
2017-12
CT-78
CP-173053
0368
1
A
Off-network Broadcast group call procedures
14.4.0
2017-12
CT-78
CP-173053
0372
A
Four most significant bits of PCK-ID
14.4.0
2017-12
CT-78
CP-173073
0354
3
B
Remotely initiated group call client procedures
15.0.0
2017-12
CT-78
CP-173073
0355
3
B
Remotely initiated group call server procedures
15.0.0
2017-12
CT-78
CP-173073
0356
3
B
Remotely initiated private call client procedures
15.0.0
2017-12
CT-78
CP-173073
0357
3
B
Remotely initiated private call server procedures
15.0.0
2018-03
CT-79
CP-180086
0375
D
Clarification of SIP REFER usage for group calls
15.1.0
2018-03
CT-79
CP-180061
0378
3
A
Correction to TPF procedures for imminent peril calls
15.1.0
2018-03
CT-79
CP-180109
0381
1
A
Removal of editor's notes due to completed IANA registrations
15.1.0
2018-03
CT-79
CP-180086
0383
F
Corrections to mcpttinfo.xsd
15.1.0
2018-03
CT-79
CP-180061
0386
1
A
Correction to CF procedures for Priv-Answer-Mode-handling in private calls
15.1.0
2018-06
CT-80
CP-181071
0387
F
Clarification to URI and address assignments
15.2.0
2018-06
CT-80
CP-181071
0388
2
F
Clarification to SIP REFER "BYE"
15.2.0
2018-06
CT-80
CP-181072
0389
B
Managing functional alias – client procedures
15.2.0
2018-06
CT-80
CP-181072
0390
1
B
Managing functional alias – MCPTT server serving the user
15.2.0
2018-06
CT-80
CP-181072
0391
1
B
Managing functional alias – MCPTT server owning the functional alias
15.2.0
2018-06
CT-80
CP-181072
0392
B
Managing functional alias – coding
15.2.0
2018-06
CT-80
CP-181072
0393
B
Functional alias – definitions and general
15.2.0
2018-06
CT-80
CP-181072
0394
B
Using functional alias in initial SIP INVITE request – client procedures
15.2.0
2018-06
CT-80
CP-181072
0395
B
Using functional alias in initial SIP INVITE request – server procedures
15.2.0
2018-06
CT-80
CP-181048
0398
1
A
<session-id> element confusion
15.2.0
2018-06
CT-80
CP-181048
0400
1
A
RTCP mux correction
15.2.0
2018-09
CT-81
CP-182116
0405
A
Correction of namespace prefix for MC location XML
15.3.0
2018-09
CT-81
CP-182155
0406
1
F
Display of functional alias
15.3.0
2018-09
CT-81
CP-182155
0407
F
Protection of functional alias
15.3.0
2018-09
CT-81
CP-182155
0408
1
F
Functional alias in REFER
15.3.0
2018-09
CT-81
CP-182155
0409
1
F
SUBSCRIBE to contain Event header
15.3.0
2018-09
CT-81
CP-182149
0410
2
B
Location of Talker
15.3.0
2018-09
CT-81
CP-182149
0411
4
B
Enter-Exit emergency alert area
15.3.0
2018-09
CT-81
CP-182155
0412
1
F
FA Take Over
15.3.0
2018-09
CT-81
CP-182149
0413
1
B
De-Affiliation based on Geo-Location
15.3.0
2018-09
CT-81
CP-182153
0417
2
B
Header compression over MBMS - signalling control
15.3.0
2018-12
CT-82
CP-183063
0420
A
Correct root element in presence event package
15.4.0
2018-12
CT-82
CP-183063
0423
A
Correction of the "prefix" attribute handling
15.4.0
2018-12
CT-82
CP-183058
0425
A
Removal of editor's notes
15.4.0
2018-12
CT-82
CP-183058
0428
2
A
Align broadcast group call release with stage 2
15.4.0
2018-12
CT-82
CP-183061
0431
F
Conference event terminology
15.4.0
2018-12
CT-82
CP-183047
0432
3
B
Subscription to group dynamic data
15.4.0
2018-12
CT-82
CP-183063
0433
1
A
Incorrect clause reference
15.4.0
2018-12
CT-82
CP-183061
0434
F
Clean-up of the semantics for MBMS usage information
15.4.0
2018-12
CT-82
CP-183065
0435
1
F
Correction for subscription to FA information
15.4.0
2018-12
CT-82
CP-183058
0439
1
A
Removal of references to a voided clause
15.4.0
2018-12
CT-82
CP-183065
0440
1
F
Resolving ENs pertaining to server terminology
15.4.0
2018-12
CT-82
CP-183064
0443
2
A
Off-network corrections to clauses with multiple beginning states
15.4.0
2018-12
CT-82
CP-183064
0446
2
A
Off-Network cleanup of timers
15.4.0
2018-12
CT-82
CP-183063
0449
1
A
Off-network corrections to off-network private call type control
15.4.0
2018-12
CT-82
CP-183063
0452
1
A
Off-network corrections to call control and call type control
15.4.0
2018-12
CT-82
CP-183063
0455
1
A
Off-network timer TFP5 not stopped when leaving P4
15.4.0
2018-12
CT-82
CP-183063
0458
1
A
Off-network Timer TFP7 not stopped when leaving P1
15.4.0
2018-12
CT-82
CP-183047
0459
F
Correct aes-gcm reference to RFC 5288t
15.4.0
2018-12
CT-82
CP-183047
0460
F
Correct source of stored status in 6.3.4.3
15.4.0
2018-12
CT-82
CP-183063
0463
A
SIP session timer and MCPTT session id in Chat
15.4.0
2019-03
CT-83
CP-190078
0468
1
A
Corrections to Off-network Broadcast group call control
15.5.0
2019-03
CT-83
CP-190096
0469
1
F
MCPTT Emergency location triggering criteria
15.5.0
2019-03
CT-83
CP-190103
0464
1
F
24.379 addition of conference event subscription
16.0.0
2019-03
CT-83
CP-190103
0465
2
F
24.379 Copy MCPTT ID Fix
16.0.0
2019-03
CT-83
CP-190103
0470
F
Media feature tag corrections
16.0.0
2019-06
CT-84
CP-191116
0474
A
Resolving editor's notes on MONP port
16.1.0
2019-06
CT-84
CP-191142
0475
2
F
Fix for alert element
16.1.0
2019-06
CT-84
CP-191142
0476
3
F
Emergency upgrade wording fix
16.1.0
2019-09
CT-85
CP-192065
0477
F
TS 24.379 reference fix
16.2.0
2019-09
CT-85
CP-192065
0478
F
Subsequent corrections to sections upgrading calls to emergency or imminent peril
16.2.0
2019-09
CT-85
CP-192065
0479
F
ASN.1 specification 24.379
16.2.0
2019-09
CT-85
CP-192065
0480
1
F
Corrections related to MCPC
16.2.0
2019-09
CT-85
CP-192066
0481
1
B
Restricting incoming private communications - call control
16.2.0
2019-09
CT-85
CP-192066
0482
1
B
Using functional alias in private calls – client procedures
16.2.0
2019-09
CT-85
CP-192066
0483
1
B
Using functional alias in private calls – server procedures
16.2.0
2019-09
CT-85
CP-192066
0484
1
B
Support of functional aliases in broadcast group calls
16.2.0
2019-12
CT-86
CP-193110
0485
2
B
Triggering an emergency group call after an emergency alert automatically
16.3.0
2019-12
CT-86
CP-193110
0486
6
B
List of MCPTT group members who did not acknowledge the group call request
16.3.0
2019-12
CT-86
CP-193109
0489
F
Correct MCPTT location schema
16.3.0
2019-12
CT-86
CP-193109
0493
1
F
Correct target of error response
16.3.0
2019-12
CT-86
CP-193109
0494
F
Correct some errors in 24.379
16.3.0
2019-12
CT-86
CP-193082
0498
1
A
Error in MBMS service area element
16.3.0
2019-12
CT-86
CP-193110
0500
1
B
Support of functional aliases in emergency alerts
16.3.0
2019-12
CT-86
CP-193110
0501
1
B
Automatic activation and deactivation of functional aliases based on location
16.3.0
2019-12
CT-86
CP-193109
0503
F
Remove references to 3rd party registration for location reporting
16.3.0
2019-12
CT-86
CP-193103
0504
1
B
Preconfigured regroup – 4.4.2 Warning texts
16.3.0
2019-12
CT-86
CP-193103
0505
2
B
Preconfigured regroup – SIP MESSAGE types
16.3.0
2019-12
CT-86
CP-193103
0506
2
B
Preconfigured regroup – X.1 General section
16.3.0
2019-12
CT-86
CP-193103
0508
2
B
Preconfigured regroup – X.2.1.1 Client create request
16.3.0
2019-12
CT-86
CP-193103
0509
1
B
Preconfigured regroup – X.2.1.2 Client remove request
16.3.0
2019-12
CT-86
CP-193103
0510
2
B
Preconfigured regroup – X.2.2.2 Originating participating create request
16.3.0
2019-12
CT-86
CP-193103
0511
2
B
Preconfigured regroup – X.2.2.3 Orig. Partip. remove request
16.3.0
2019-12
CT-86
CP-193103
0512
3
B
Preconfigured regroup –X.2.2.4 Term. Partip. create request
16.3.0
2019-12
CT-86
CP-193103
0513
1
B
Preconfigured regroup – X.2.2.5 Term. Partip. remove request
16.3.0
2019-12
CT-86
CP-193103
0514
3
B
Preconfigured regroup – X.2.3.1 Controlling create request
16.3.0
2019-12
CT-86
CP-193103
0515
3
B
Preconfigured regroup –X.2.3.2 Controlling remove request
16.3.0
2019-12
CT-86
CP-193103
0516
1
B
Preconfigured regroup – X.2.3.3 Controlling remove decision
16.3.0
2019-12
CT-86
CP-193103
0517
1
B
Preconfigured regroup – X.2.4.1 Non-controlling create request
16.3.0
2019-12
CT-86
CP-193103
0518
1
B
Preconfigured regroup – X.2.4.2 Non-controlling remove request
16.3.0
2019-12
CT-86
CP-193103
0520
2
B
Preconfigured regroup – X.3.1.1 Client create request
16.3.0
2019-12
CT-86
CP-193103
0521
1
B
Preconfigured regroup – X.3.1.2 Client remove request
16.3.0
2019-12
CT-86
CP-193103
0522
2
B
Preconfigured regroup – X.3.2.2 Originating participating create request
16.3.0
2019-12
CT-86
CP-193103
0523
2
B
Preconfigured regroup – X.3.2.3 Orig. Partip. remove requestt
16.3.0
2019-12
CT-86
CP-193103
0524
2
B
Preconfigured regroup – X.3.2.4 Term. Partip. create request
16.3.0
2019-12
CT-86
CP-193103
0525
2
B
Preconfigured regroup – X.3.2.5 Term. Partip. remove request
16.3.0
2019-12
CT-86
CP-193103
0526
3
B
Preconfigured regroup – X.3.3.1 Controlling create request
16.3.0
2019-12
CT-86
CP-193103
0527
2
B
Preconfigured regroup – X.3.3.2 Controlling remove request
16.3.0
2019-12
CT-86
CP-193103
0528
1
B
Preconfigured regroup –X.3.3.3 Controlling remove decision
16.3.0
2019-12
CT-86
CP-193284
0529
5
B
Preconfigured regroup – XML schema for regroup using preconfigured group
16.3.0
2019-12
CT-86
CP-193082
0533
A
Corrections to off-network private call control state machine
16.3.0
2019-12
CT-86
CP-193082
0537
3
A
Corrections to Off-network private call type control state machine
16.3.0
2019-12
CT-86
CP-193109
0538
1
D
Editorial corrections
16.3.0
2019-12
CT-86
CP-193110
0540
2
B
Implicit activation and deactivation of functional alias(es)
16.3.0
2019-12
CT-86
CP-193110
0542
1
B
Additional commencement modes for group calls
16.3.0
2020-03
CT-87e
Editorial fixes by MCC
16.4.0
2020-03
CT-87e
CP-200122
0541
3
B
Automatic group affiliation and deaffiliation based on location or functional alias
16.4.0
2020-03
CT-87e
CP-200121
0543
F
Correcting SIP related terminology
16.4.0
2020-03
CT-87e
CP-200116
0544
1
F
Affiliation in a regroup
16.4.0
2020-03
CT-87e
CP-200121
0547
1
F
Check for controlling function identity in 10.1.1.3.1.1
16.4.0
2020-03
CT-87e
CP-200121
0548
1
F
Check for groups that are already regrouped
16.4.0
2020-03
CT-87e
CP-200121
0549
1
F
Correct clause reference in 11.1.1.3.1.2
16.4.0
2020-03
CT-87e
CP-200116
0550
2
F
Missing client procedures for preconfigured regroup
16.4.0
2020-03
CT-87e
CP-200122
0551
1
B
Support of functional alias in first-to-answer calls
16.4.0
2020-03
CT-87e
CP-200122
0552
2
B
Update service authorization procedures to support limiting the number of authorized clients per MCPTT user
16.4.0
2020-06
CT-88e
CP-201122
0553
1
F
Check of Regroup ID at CF
16.5.0
2020-06
CT-88e
CP-201122
0554
1
F
Clarification of 11.1.6.2.1.2
16.5.0
2020-06
CT-88e
CP-201122
0555
1
F
Update affiliation definition to support preconfigured regroups
16.5.0
2020-06
CT-88e
CP-201122
0556
3
F
Authorisation validation for first-to-answer call origination requesting user using pre-established session
16.5.0
2020-06
CT-88e
CP-201122
0557
1
F
Check for MCPTT ID bindng and validity period of existing binding
16.5.0
2020-06
CT-88e
CP-201122
0558
1
F
Corrections to location sharing during call setup
16.5.0
2020-06
CT-88e
CP-201122
0559
1
F
Corrections to current talker location in ambient call
16.5.0
2020-06
CT-88e
CP-201122
0560
F
Corrections to step reference in terminating controlling function
16.5.0
2020-06
CT-88e
CP-201122
0561
F
Corrections to step reference in create a group regroup using preconfigured group
16.5.0
2020-06
CT-88e
CP-201122
0562
F
Corrected the client origination procedure clause text of 11.1.6.2.1.1
16.5.0
2020-06
CT-88e
CP-201122
0563
F
Allow an emergency and immenit peril calls during max simultaneous sessions
16.5.0
2020-06
CT-88e
CP-201122
0565
1
F
Cancellation of a Private Call (without Floor Control) prior the setup
16.5.0
2020-06
CT-88e
CP-201086
0569
1
A
Corrections to Off-network group call control
16.5.0
2020-06
CT-88e
CP-201086
0573
A
Corrections to Off-network group call type control
16.5.0
2020-06
CT-88e
CP-201122
0575
2
F
Group document definitions for preconfigured regroup
16.5.0
2020-06
CT-88e
CP-201122
0580
2
F
MCPTT server stores preconfigured regroup information
16.5.0
2020-06
CT-88e
CP-201122
0589
2
F
6.3.5.4 Correct reference to group document
16.5.0
2020-06
CT-88e
CP-201122
0590
2
F
6.3.5.5 Correct reference to group document
16.5.0
2020-06
CT-88e
CP-201124
0605
F
Correct editorial in FA status definition
16.5.0
2020-06
CT-88e
CP-201122
0606
D
Correct spelling of functional alias
16.5.0
2020-06
CT-88e
CP-201124
0607
F
Correct clause references in 9A
16.5.0
2020-06
CT-88e
CP-201122
0608
1
F
Correct warning message and number in 10.1.1.4.2
16.5.0
2020-06
CT-88e
CP-201094
0609
1
A
Schema error – FA Coding 9A.3.1.2
16.5.0
2020-06
CT-88e
CP-201087
0612
A
Specification of MONP messages to support off-network MCData and MCVideo
16.5.0
2020-06
CT-88e
CP-201086
0613
1
A
SSRC handling for implicit floor request case
16.5.0
2020-06
CT-88e
CP-201124
0616
1
B
Limiting the number of emergency group calls accepted based on calling FA
16.5.0
2020-06
CT-88e
CP-201124
0617
1
B
Resolution of called functional alias in first-to-answer calls
16.5.0
2020-06
CT-88e
CP-201122
0619
F
Error in the pidf+xml schema - 9A.3.1.2
16.5.0
2020-09
CT-89e
CP-202155
0628
F
Make regroup warning messages generic for MCX
16.6.0
2020-09
CT-89e
CP-202155
0629
1
F
10.1.1.4.2 correction
16.6.0
2020-09
CT-89e
CP-202155
0637
F
Preconfigured group corrections and clarifications
16.6.0
2020-09
CT-89e
CP-202165
0644
1
F
Corrections on MCPTT related MONASTERY2 CRs implementation
16.6.0
2020-09
CT-89e
CP-202180
0622
1
F
Check for emergency call on constituent group
17.0.0
2020-09
CT-89e
CP-202180
0623
2
F
Clarify setting of p-id-fa entry in 9A.2.2.2.3
17.0.0
2020-09
CT-89e
CP-202180
0624
2
F
Correct error in 9A.3.1.2
17.0.0
2020-09
CT-89e
CP-202178
0625
B
Add altitude, timestamp to MCPTT location XML schema
17.0.0
2020-09
CT-89e
CP-202178
0626
1
B
Check for Preconfigured Group Use Only
17.0.0
2020-09
CT-89e
CP-202180
0627
1
F
Cancel of regroup in emergency state
17.0.0
2020-09
CT-89e
CP-202180
0631
1
F
Emergency Alert – Designated Group
17.0.0
2020-09
CT-89e
CP-202180
0632
F
Remove space in header field value
17.0.0
2020-09
CT-89e
CP-202180
0634
F
Reference corrections in clause 12.1.3.2
17.0.0
2020-09
CT-89e
CP-202180
0635
F
Text reference corrections in clause 10.1.1.3.1.3
17.0.0
2020-09
CT-89e
CP-202180
0636
2
F
Functional alias support and the mcptt-client-id is missing in clause 12.1.1.2
17.0.0
2020-09
CT-89e
CP-202180
0639
1
F
Sending emergency notification of MCPTT user's emergency indication
17.0.0
2020-09
CT-89e
CP-202180
0642
1
F
Standalone in-progress emergency group state cancel while not in a call
17.0.0
2020-12
CT-90e
CP-203198
0630
4
F
De-affiliation upon logoff MCPTT
17.1.0
2020-12
CT-90e
CP-203202
0646
1
A
Correct 9.2.2.2.3 p-id-fa to p-id
17.1.0
2020-12
CT-90e
CP-203198
0649
F
ProSe one-to-many required for MCPTT UE
17.1.0
2020-12
CT-90e
CP-203198
0651
1
F
Corrections in clause 10.1.1.4.2
17.1.0
2020-12
CT-90e
CP-203198
0653
1
F
Corrected the functionalAliasID and group refered as element instead of attribute.
17.1.0
2020-12
CT-90e
CP-203198
0654
1
F
Corrections to emergency group state cancelation handling
17.1.0
2020-12
CT-90e
CP-203198
0655
F
Corrections for authorization request handling for emergency and imminent peril call initiation
17.1.0
2020-12
CT-90e
CP-203198
0656
1
F
Corrections to cancelation of group in-progress emergency (Part of C1-205500 & C1-205501)
17.1.0
2020-12
CT-90e
CP-203198
0657
1
F
Handle group in-progress emergency cancel while other user transmitting in emergency state
17.1.0
2020-12
CT-90e
CP-203198
0659
D
Correct editorials in 16.3.2.4, 16.3.3.1
17.1.0
2020-12
CT-90e
CP-203198
0660
1
D
Correct editorials in F.3.3
17.1.0
2020-12
CT-90e
CP-203198
0661
1
D
Correct plurals - editorial
17.1.0
2020-12
CT-90e
CP-203201
0667
1
A
Reject the unauthorized user request for functional alias activation
17.1.0
2021-03
CT-91e
CP-210126
0669
1
F
Corrections to protection attribute for altitude and loctimestamp elements
17.2.0
2021-03
CT-91e
CP-210104
0670
5
A
Emergency alert area notification handling at client side for MCPTT
17.2.0
2021-03
CT-91e
CP-210100
0671
3
A
Appropriate handling of P-Answer-State in private and ambient call procedure
17.2.0
2021-03
CT-91e
CP-210100
0672
2
A
Appropriate handling of P-Answer-State in group call procedure
17.2.0
2021-03
CT-91e
CP-210125
0673
1
B
Call transfer for MCPTT private call, call control part
17.2.0
2021-03
CT-91e
CP-210127
0674
1
F
Clarify the use of the term N2 for MCPTT
17.2.0
2021-03
CT-91e
CP-210127
0675
D
Correct bullet styles in 10.1.1.4.7
17.2.0
2021-03
CT-91e
CP-210127
0676
F
Correct naming of SIP SUBSCRIBE for conference event
17.2.0
2021-03
CT-91e
CP-210127
0677
D
Improve the wording in F.1.3 step 2)
17.2.0
2021-03
CT-91e
CP-210127
0678
1
F
Required Ambient Call Handling
17.2.0
2021-03
CT-91e
CP-210127
0687
F
Errors in 24.379
17.2.0
2021-03
CT-91e
CP-210105
0690
2
A
Determination of the FAs activated by another user
17.2.0
2021-03
CT-91e
CP-210125
0691
1
B
Call control of FAs allowed in a first-to-answer call
17.2.0
2021-06
CT-92e
CP-211126
0715
1
A
FA indication in subscription request MCPTT_16
17.3.0
2021-06
CT-92e
CP-211154
0699
3
B
Functional alias support for a client side procedure of a first-to-answer call based on the pre-established session
17.3.0
2021-06
CT-92e
CP-211154
0707
1
F
Integrity protection of pidf+xml and xcap-diff+xml MIME bodies
17.3.0
2021-06
CT-92e
CP-211157
0710
F
Corrected the mispalcement of the authorization validation for origination of the first-to-answer call
17.3.0
2021-06
CT-92e
CP-211157
0711
F
Step reference corrections in clause 11.1.1.4.2
17.3.0
2021-06
CT-92e
CP-211157
0703
2
F
Clarify "refresh" in 9.2.1.2 and 9A.2.1.2
17.3.0
2021-06
CT-92e
CP-211157
0704
2
F
Correct affiliation based on geo location - MCPTT
17.3.0
2021-06
CT-92e
CP-211157
0705
2
F
Corrections to 7.2 clauses
17.3.0
2021-06
CT-92e
CP-211157
0712
1
F
Added missing INVITE request handling for first-to-answer call in clause 11.1.1.2.2.2
17.3.0
2021-06
CT-92e
CP-211157
0700
2
F
Missing corrections to cancelation of group in-progress emergency (Part of C1-205500 & C1-205501)
17.3.0
2021-06
CT-92e
CP-211161
0698
1
B
Add accuracy to MCPTT location XML schema
17.3.0
2021-06
CT-92e
CP-211169
0709
2
B
Call forwarding for MCPTT private call, call control part
17.3.0
2021-06
CT-92e
Editorial correrctions
17.3.1
2021-09
CT-93e
CP-212150
0720
1
B
Interconnect - MCPTT Gateway Server functional entity
17.4.0
2021-09
CT-93e
CP-212148
0722
-
D
Missing words
17.4.0
2021-09
CT-93e
CP-212145
0723
1
F
Resolution of editor's notes on handling of call forwarding based on manual user input for automatic commencement mode
17.4.0
2021-09
CT-93e
CP-212145
0724
-
F
Align call transfer with TS 24.484
17.4.0
2021-09
CT-93e
CP-212123
0726
-
A
Correct spelling of deaffiliation boolean
17.4.0
2021-09
CT-93e
CP-212148
0727
1
F
Corrections to group document notifications
17.4.0
2021-09
CT-93e
CP-212148
0728
1
F
Handling non-2xx SIP responses
17.4.0
2021-09
CT-93e
CP-212122
0730
1
A
MCPTT service binding - R17
17.4.0
2021-09
CT-93e
CP-212148
0732
-
F
Correcting Request-URI for emergency alert
17.4.0
2021-09
CT-93e
CP-212122
0734
1
A
MCPTT - Define undeclared XML element(s) of location & mbms usage in XML schema
17.4.0
2021-09
CT-93e
CP-212116
0737
1
A
MCPTT - Corrections to Request-URI and <mcptt-request-uri> for group geo and emergency alert area notification
17.4.0
2021-09
CT-93e
CP-212116
0740
-
A
Correction on Functional Alias activation procedures
17.4.0
2021-09
CT-93e
CP-212148
0741
-
F
Plugtest corrections on Functional Alias take-over procedures
17.4.0
2021-12
CT-94e
CP-213062
0721
2
B
Interconnect - MCPTT Pre-arranged group originating participating procedures
17.5.0
2021-12
CT-94e
CP-213062
0742
-
B
Interconnect - MCPTT Pre-arranged group contrlling procedures
17.5.0
2021-12
CT-94e
CP-213062
0751
-
B
Interconnect - MCPTT Common procedures
17.5.0
2021-12
CT-94e
CP-213062
0752
-
B
Interconnect - MCPTT Affiliation procedures
17.5.0
2021-12
CT-94e
CP-213062
0753
-
B
Interconnect - MCPTT Chat group procedures
17.5.0
2021-12
CT-94e
CP-213062
0754
-
B
Interconnect - MCPTT Remote change of selected group procedures
17.5.0
2021-12
CT-94e
CP-213062
0755
-
B
Interconnect - MCPTT Remotely initiated group call procedures
17.5.0
2021-12
CT-94e
CP-213062
0756
-
B
Interconnect - MCPTT Emergency alert procedures
17.5.0
2021-12
CT-94e
CP-213062
0757
-
B
Interconnect - MCPTT Private call procedures
17.5.0
2021-12
CT-94e
CP-213062
0758
-
B
Interconnect - MCPTT Group regroup procedures
17.5.0
2021-12
CT-94e
CP-213062
0759
-
B
Interconnect - MCPTT User regroup procedures
17.5.0
2021-12
CT-94e
CP-213022
0769
1
A
Corrections to private call without floor control using pre-established session
17.5.0
2021-12
CT-94e
CP-213022
0773
1
A
Correction to terminating participating procedure for chat group
17.5.0
2021-12
CT-94e
CP-213029
0743
-
F
Private Call Forwarding - functional alias correction
17.5.0
2021-12
CT-94e
CP-213029
0746
1
B
Inclusion of functional alias in conference event package notification - mcptt
17.5.0
2021-12
CT-94e
CP-213029
0747
1
B
Functional alias association with MCPTT group - protocol implementation
17.5.0
2021-12
CT-94e
CP-213029
0749
1
B
MCPTT control of limit of the number of simultaneous logins
17.5.0
2021-12
CT-94e
CP-213029
0763
2
B
Support target FA in private calls
17.5.0
2021-12
CT-94e
CP-213029
0764
2
F
Resolve EN in first-to-answer call to an FA
17.5.0
2021-12
CT-94e
CP-213059
0775
1
B
5GS/EPS alignment in MCPTT procedures
17.5.0
2021-12
CT-94e
CP-213060
0762
-
F
Clause reference correction in 11.1.1.4.2
17.5.0
2021-12
CT-94e
CP-213060
0774
-
F
Correction on reference and warning code
17.5.0
2021-12
CT-94e
CP-213062
0760
1
B
Interconnect - MCPTT Gateway server procedures
17.5.0
2022-03
CT-95e
CP-220280
0776
-
F
Interconnect - Clarification to MCPTT Gateway server procedures
17.6.0
2022-03
CT-95e
CP-220280
0777
1
C
Interconnect - Correction of pre-arranged group regroup call set up procedures
17.6.0
2022-03
CT-95e
CP-220281
0780
1
B
Additional private call rejection reasons
17.6.0
2022-03
CT-95e
CP-220276
0781
-
F
Corrections and clarifications routing to a PSI
17.6.0
2022-03
CT-95e
CP-220273
0783
-
B
Update of IETF references for ICE
17.6.0
2022-03
CT-95e
CP-220276
0784
-
F
Correction of dev/null
17.6.0
2022-03
CT-95e
CP-220276
0785
-
F
Removal of Warning header field from INVITE
17.6.0
2022-03
CT-95e
CP-220276
0787
1
F
Clarify support of group calls notification on entry/exit
17.6.0
2022-03
CT-95e
CP-220276
0791
1
F
Reference fix and CR implementation issues
17.6.0
2022-03
CT-95e
CP-220276
0794
-
F
Correction to media plane reference in non-controlling function of an MCPTT group procedures
17.6.0
2022-06
CT-96
CP-221193
0802
1
A
Fix use of mcptt-request-uri with anyExt
17.7.0
2022-06
CT-96
CP-221193
0811
1
A
Corrections to private call without floor control using pre-established session
17.7.0
2022-06
CT-96
CP-221193
0820
1
A
Correcting the downgrade of first-to-answer call to private call
17.7.0
2022-06
CT-96
CP-221225
0816
1
F
Several corrections related to use of functional alias URI and its resolution response
17.7.0
2022-06
CT-96
CP-221225
0824
1
B
Support location reporting based on FA
17.7.0
2022-06
CT-96
CP-221225
0813
1
F
Corrections for call transfer
17.7.0
2022-06
CT-96
CP-221225
0825
1
B
Support preventing of de-affiliating for certain FAs
17.7.0
2022-06
CT-96
CP-221225
0798
3
B
Support user-provided application layer priority in MCPTT
17.7.0
2022-06
CT-96
CP-221227
0796
1
B
5GS QoS aspects in MCPTT
17.7.0
2022-06
CT-96
CP-221227
0823
1
B
Resource sharing aspects in MCPTT
17.7.0
2022-06
CT-96
CP-221233
0806
-
D
Editorial fixes
17.7.0
2022-06
CT-96
CP-221233
0821
-
F
Clarify conditions of emergency alert notification on area entry/exit
17.7.0
2022-06
CT-96
CP-221233
0822
-
F
Location not included at implicit floor request
17.7.0
2022-06
CT-96
CP-221233
0807
1
F
Clarification of inclusion of Warning header fields in 6.3.4.2.2.2
17.7.0
2022-06
CT-96
CP-221345
0815
2
B
Group area configuration procedure
17.7.0
2022-06
CT-96
CP-221234
0812
1
F
Interconnect - Additional corrections to MCPTT pre-arranged group regroup call set up procedures
17.7.0
2022-06
CT-96
CP-221248
0795
1
F
Reference corrections
17.7.0
2022-06
CT-96
CP-221194
0805
2
A
Fix use of mcptt-called-party-id with anyExt
17.7.0
2022-09
CT-97e
CP-222160
0827
1
F
Corrections for MCPTT private call forwarding
17.8.0
2022-09
CT-97e
CP-222135
0830
1
A
Fix use of mcptt-request-uri with anyExt
17.8.0
2022-09
CT-97e
CP-222160
0831
1
F
Plugtest Issue 10.1.2 of May 2022
17.8.0
2022-09
CT-97e
CP-222135
0834
2
A
Plugtest issue 10.1.1 of May 2022: Fix for routing of remotely initiated private call response
17.8.0
2022-09
CT-97e
CP-222162
0835
-
F
Functional Alias resolution reference correction
17.8.0
2022-09
CT-97e
CP-222162
0836
1
F
Plugtest FA take-over clarification
17.8.0
2022-09
CT-97e
CP-222162
0837
1
B
Support providing FAs used by affiliated group members
17.8.0
2022-09
CT-97e
CP-222160
0838
1
B
Support user-provided application layer priority in MCPTT
17.8.0
2022-09
CT-97e
CP-222173
0833
2
F
Differentiating user and group regroup
18.0.0
2022-09
CT-97e
CP-222173
0839
1
F
Correction of ETSI plugtest finding 10.1.10 from report in C1-223358
18.0.0
2022-12
CT-98e
CP-223152
0844
1
A
Corrections for MCPTT private call forwarding
18.1.0
2022-12
CT-98e
CP-223131
0845
F
Correction of application/pidf+xml MIME body extensions
18.1.0
2022-12
CT-98e
CP-223131
0846
1
F
Fix use of call-to-functional-alias-ind, called-functional-alias-URI and functional-alias-URI within anyExt
18.1.0
2022-12
CT-98e
CP-223131
0849
1
F
Correct usage of public service identity
18.1.0
2022-12
CT-98e
CP-223131
0850
1
F
Fix references to application/resource-lists+xml MIME body
18.1.0
2022-12
CT-98e
CP-223132
0853
A
Correction to MCPTT non controlling procedure 6.3.4.1.2.
18.1.0
2022-12
CT-98e
CP-223131
0854
F
Clean up unused MCPTT procedures for SIP OPTIONS
18.1.0
2022-12
CT-98e
CP-223131
0855
2
B
MCPTT Chat group join to group regroup
18.1.0
2022-12
CT-98e
CP-223131
0856
F
Correction to MCPTT procedure 10.1.1.3.2.
18.1.0
2022-12
CT-98e
CP-223152
0860
1
A
Fixes in mcpttinfo XML schema
18.1.0
2022-12
CT-98e
CP-223131
0862
1
F
Corrections of handling of called party in MCPTT first-to-answer calls
18.1.0
2023-03
CT-98e
CP-230241
0848
3
B
MBMS listening status coding
18.2.0
2023-03
CT-98e
CP-230230
0868
2
A
Corrections and enhancements for MCPTT private call forwarding
18.2.0
2023-03
CT-98e
CP-230239
0866
2
B
5G MBS transmission usage procedure
18.2.0
2023-03
CT-99
Correction of Formatting errors
18.2.1
2023-06
CT-100
CP-231256
0877
-
F
Fix erroneous references in 24.379
18.3.0
2023-06
CT-100
CP-231256
0874
1
F
Correction of SIP INVITE from NCF to CF
18.3.0
2023-06
CT-100
CP-231256
0875
1
F
Correction of P-Asserted-Identity header fields in MCPTT
18.3.0
2023-06
CT-100
CP-231256
0876
1
F
Correction of Referred-By header fields in MCPTT
18.3.0
2023-06
CT-100
CP-231235
0872
3
A
Corrections for MCPTT private call transfer
18.3.0
2023-06
CT-100
CP-231235
0880
1
A
Corrections for authorization check for calls to functional alias
18.3.0
2023-06
CT-100
CP-231256
0881
1
F
Correction to service authorisation, MCPTT
18.3.0
2023-06
CT-100
CP-231255
0873
4
B
Addition of 5G MBS inter-RAT information in MCPTT signalling
18.3.0
2023-06
CT-100
CP-231256
0883
1
F
Protection of <associated-group-id> and <group-geo-area-ind> elements
18.3.0
2023-06
CT-100
CP-231283
0870
2
B
Enhancements to remotely initiated call request procedure to support pre-emptive and commencement mode
18.3.0
2023-06
CT-100
Fixing formatting errors
18.3.1
2023-09
CT-101
CP-232221
0900
-
F
Clarification and addition of 5G ProSe terms
18.4.0
2023-09
CT-101
CP-232229
0897
1
A
Corrections for MCPTT private call forwarding
18.4.0
2023-09
CT-101
CP-232228
0901
1
B
MC GW UE functions in MCPTT
18.4.0
2023-09
CT-101
CP-232234
0898
1
F
Corrections for MCPTT private call transfer
18.4.0
2023-09
CT-101
CP-232206
0902
2
B
General adhoc group call procedures in single system - Protoc impl for MCPTT
18.4.0
2023-09
CT-101
CP-232224
0899
1
B
Add the description of 5MBS in MCPTT
18.4.0
2023-12
CT-102
CP-233173
0905
-
B
Support MCPTT over 5G ProSe
18.5.0
2023-12
CT-102
CP-233169
0907
-
F
Update the warning texts and corresponding reference in the procedure
18.5.0
2023-12
CT-102
CP-233176
0903
1
F
Clarification on usage of PSIs in MCPTT clients
18.5.0
2023-12
CT-102
CP-233155
0889
4
B
MCPTT support of multiplexing - SDP offers and answers
18.5.0
2023-12
CT-102
CP-233175
0908
1
F
Re-arranging MBS clause
18.5.0
2023-12
CT-102
CP-233169
0906
1
B
Adhoc group call participants modify procedures in single system - protoc impl MCPTT
18.5.0
2023-12
CT-102
CP-233153
0882
7
B
Migration service authorization; uplink
18.5.0
2023-12
CT-102
CP-233176
0911
-
F
Corrections for functional alias activation
18.5.0
2023-12
CT-102
CP-233176
0914
-
D
Correction in the <mcpttinfo> element
18.5.0
2023-12
CT-102
CP-233154
0910
1
A
Corrections for MCPTT private call forwarding
18.5.0
2023-12
CT-102
CP-233153
0913
1
B
Private call to user that is migrated to a partner system
18.5.0
2023-12
CT-102
CP-233155
0917
1
F
Use of port number in case of separate MBMS subchannel for floor control
18.5.0
2023-12
CT-102
CP-233169
0915
1
B
General Adhoc group call procedures using pre-established session in Single system - Protoc impl for MCPTT
18.5.0
2023-12
CT-102
CP-233173
0916
2
B
MC over 5GProSe
18.5.0
2023-12
CT-102
CP-233153
0912
2
B
Migration service authorization; downlink
18.5.0
2024-03
CT-103
CP-240103
0924
-
F
Correction in the SIP MESSAGE requests used for migration service authorization
18.6.0
2024-03
CT-103
CP-240103
0925
-
F
Code value for call forwarding due to migration
18.6.0
2024-03
CT-103
CP-240104
0930
-
F
Fix references to application/resource-lists+xml MIME body (mcptt)
18.6.0
2024-03
CT-103
CP-240111
0927
1
B
General adhoc group call procedures in multiple systems - Protoc impl for MCPTT
18.6.0
2024-03
CT-103
CP-240111
0928
1
B
General Adhoc group call procedures using pre-established session in Single system - procedures at CF (mcptt)
18.6.0
2024-03
CT-103
CP-240104
0926
1
F
Update of location information and triggers provided by / to MCPTT UEs
18.6.0
2024-03
CT-103
CP-240103
0918
1
F
Alignment in migration service authorization among MC services
18.6.0
2024-03
CT-103
CP-240104
0922
1
B
Location information request from an MCPTT client
18.6.0
2024-03
CT-103
CP-240104
0919
1
B
Emergency alert to client doing late affiliation
18.6.0
2024-03
CT-103
CP-240114
0934
-
F
Undefined SIP MESSAGE request
18.6.0
2024-03
CT-103
CP-240103
0935
-
F
Correction in the <migration-auth-result> element
18.6.0
2024-03
CT-103
CP-240111
0929
1
B
Subscribe to the participant information of the ongoing adhoc group call - MCPTT
18.6.0
2024-03
CT-103
CP-240114
0948
-
F
Corrections to MCPTT emergency private call response handling in participating function
18.6.0
2024-03
CT-103
CP-240114
0938
1
F
Clarification on PSI of controlling and terminating participating function for functional alias procedures for MCPTT
18.6.0
2024-03
CT-103
CP-240112
0921
2
B
Enable QoS for MCPTT clients behind MC gateway UEs
18.6.0
2024-03
CT-103
CP-240104
0946
1
C
Auto affiliation of remote MCPTT user to MCPTT Group for remotely initiated MCPTT Call procedure
18.6.0
2024-03
CT-103
CP-240111
0931
1
F
Check if the associated group-identity was learnt previously, while initiating an adhoc group call using on-demand session
18.6.0
2024-03
CT-103
CP-240104
0933
1
B
Group-regroup notification to MCPTT client on affiliation after regroup operation
18.6.0
2024-03
CT-103
CP-240103
0947
2
B
MCPTT service authorization notification handling in migration procedure
18.6.0
2024-03
CT-103
CP-240111
0945
2
B
Determine the users based on the criteria to invite, release from, an ad hoc group session - MCPTT
18.6.0
2024-03
CT-103
CP-24010
0923
6
B
Migration service deauthorization notification
18.6.0
2024-03
CT-103
CP-240111
0937
2
B
Adhoc group emergency alert procedures - Protoc impl for MCPTT
18.6.0
2024-06
CT-104
CP-241183
0951
-
F
Corrections for MCPTT private call forwarding
18.7.0
2024-06
CT-104
CP-241173
0956
-
F
Service authorization notification
18.7.0
2024-06
CT-104
CP-241174
0961
-
F
MCPTT Location information xml schema corrections
18.7.0
2024-06
CT-104
CP-241174
0965
-
F
Fix the use of unknown emergency state values - Plugtest issue 1 (10.1.11)
18.7.0
2024-06
CT-104
CP-241174
0966
-
F
Fix the wrong state referenced - Plugtest issue 2 (10.1.11)
18.7.0
2024-06
CT-104
CP-241174
0967
-
F
Fix the missing reset of MCPTT emergency group call state - Plugtest issue 4 (10.1.11)
18.7.0
2024-06
CT-104
CP-241183
0955
1
F
Cleanup in distinction of SIP MESSAGE requests
18.7.0
2024-06
CT-104
CP-241173
0957
1
F
Correction in the <req-type> element
18.7.0
2024-06
CT-104
CP-241173
0958
1
F
Correction in the <selected-user-profile-index> element
18.7.0
2024-06
CT-104
CP-241173
0959
1
F
<partner-mcptt-id> and <migration-auth-result> under <anyExt>
18.7.0
2024-06
CT-104
CP-241182
0960
2
F
MCPTT gateway UE updates due to stage-2 changes
18.7.0
2024-06
CT-104
CP-241174
0962
1
B
MCPTT Location request with functional alias
18.7.0
2024-06
CT-104
CP-241181
0964
1
F
Corrections to inclusion of multiple MIME bodies for adhoc group call request - MCPTT
18.7.0
2024-06
CT-104
CP-241181
0963
2
B
Support for emergency adhoc group call and imminent peril adhoc group call - MCPTT
18.7.0
2024-06
CT-104
CP-241174
0969
-
B
Location information request with location filter for MCPTT
18.7.0
2024-06
CT-104
CP-241173
0973
1
F
Distinction of SIP MESSAGE requests for migration service authorization
18.7.0
2024-06
CT-104
CP-241182
0972
1
F
Clarification on MCPTT gateway UE hosting MCPTT clients
18.7.0
2024-06
CT-104
CP-241182
0974
1
F
MCPTT QoS - Resource Management
18.7.0
2024-06
CT-104
CP-241174
0968
1
B
Location reporting configuration provided by authorized MCPTT user
18.7.0
2024-06
CT-104
CP-241174
0981
1
F
Cancel imminent peril group state when no group call exists - Plugtest issue 3 (10.1.11)
18.7.0
2024-06
CT-104
CP-241181
0950
4
F
Adhoc group call - Protoc impl for MCPTT
18.7.0
2024-06
CT-104
CP-241181
0976
1
B
Handling of a SIP MESSAGE request for adhoc group emergency alert cancellation in controlling function
18.7.0
2024-06
CT-104
CP-241181
0977
1
B
Handling of Adhoc group emergency alert participants start/stop determination procedures in PF
18.7.0
2024-06
CT-104
CP-241181
0978
1
B
Handling of Adhoc group emergency alert participants modification procedures in PF and CF
18.7.0
2024-06
CT-104
CP-241181
0979
1
F
Indicate the participating function to stop determining the ad-hoc group participants (mcptt)
18.7.0
2024-06
CT-104
CP-241181
0953
5
F
Corrections for adhoc emergency alert
18.7.0
2024-06
CT-104
CP-241181
0980
3
F
Remove the use of adhoc-emergency-ind from adhoc group emergency alert procedures
18.7.0
2024-06
CT-104
CP-241181
0975
2
F
Corrections in handling of a SIP MESSAGE request for adhoc group emergency alert origination
18.7.0
2024-09
CT-105
CP-242182
0992
1
F
Corrections to issues found in the XSDs (poc-settings and Location info)
18.8.0
2024-09
CT-105
CP-242182
0993
1
F
FRMCS Plugtest 3 - Issue 10.1.8: 10.1.8 FA affiliation analogue to Group affiliation
18.8.0
2024-09
CT-105
CP-242186
0991
2
F
Corrections in adhoc group emergency alert procedures
18.8.0
2024-09
CT-105
CP-242186
0988
-
F
Correction in the <allow-cancel-adhoc-group-emergency-alert> element
19.0.0
2024-09
CT-105
CP-242186
0990
-
F
Correction in the controlling MCPTT server operation for an MCPTT user not authorized for MCPTT ad hoc group emergency alert participant information
19.0.0
2024-09
CT-105
CP-242189
0982
1
F
Corrections for MCPTT private call transfer
19.0.0
2024-09
CT-105
CP-242189
0983
1
F
Corrections to Group Regroup Procedures
19.0.0
2024-12
CT-106
CP-243191
0995
F
Clarifications for MCPTT private call forwarding
19.1.0
2024-12
CT-106
CP-243218
0996
-
C
Enhance handling of criteria for ad hoc group communication (MCPTT)
19.1.0
2024-12
CT-106
CP-243224
1003
-
A
MCPTT Location-info correction R19
19.1.0
2024-12
CT-106
CP-243198
1005
-
A
Add missing MIME bodies
19.1.0
2024-12
CT-106
CP-243191
1007
-
F
Correction in the ad hoc group call setup
19.1.0
2024-12
CT-106
CP-243218
1004
2
B
Modify list of participants by changing the criteria during an ongoing MCPTT ad hoc group call
19.1.0
2025-03
CT#107
CP-250167
1008
1
C
MCPTT Prevent multiple participations in a group regroup
19.2.0
2025-03
CT#107
CP-250158
1009
-
F
Enhancement to functional alias status determination
19.2.0
2025-03
CT#107
CP-250158
1010
1
F
MCPTT control plane user plane separation
19.2.0
2025-03
CT#107
CP-250158
1011
-
F
Corrections to adhoc group call
19.2.0
2025-03
CT#107
CP-250160
1013
-
A
Correction in the element for authorization of AHGC participants modification
19.2.0
2025-06
CT#108
CP-251163
1014
-
B
Adhoc group emergency alert add criteria to the SIP message containing the participant lists sent to the authorised users
19.3.0
2025-06
CT#108
CP-251157
1016
-
F
Corrections to adhoc group emergency alert and adhoc group call for MCPTT
19.3.0
2025-06
CT#108
CP-251157
1019
1
F
Reference to obsoleted IETF RFC 4122
19.3.0
2025-06
CT#108
CP-251163
1015
1
B
MCPTT adhoc group call to migrated user
19.3.0
2025-06
CT#108
CP-251163
1017
1
F
Additional information for ad hoc group emergency alert cancellation
19.3.0
2025-06
CT#108
CP-251157
1020
-
F
Corrections for handling of sending a SIP BYE request on receipt of a SIP REFER request
19.3.0
2025-06
CT#108
CP-251163
1021
-
B
Adding option to apply automatic commencement for adhoc group calls
19.3.0
2025-06
CT#108
CP-251157
1023
-
F
Clarifications on MCPTT private call transfer
19.3.0
2025-06
CT#108
CP-251157
1024
-
F
Corrections related to P-Asserted-Service header
19.3.0
2025-06
CT#108
CP-251163
1018
3
B
Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert
19.3.0
2025-06
CT#108
CP-251163
1022
2
B
Adhoc group call release by an authorized user (MCPTT)
19.3.0
2025-09
CT#109
CP-252147
1028
-
F
Correction in ad hoc group call release by an authorized user
19.4.0
2025-09
CT#109
CP-252147
1029
-
B
FRMCS_Ph5 Adding reason to leave a session in MCPTT
19.4.0
2025-09
CT#109
CP-252141
1025
1
B
Emergency remote floor request procedures
19.4.0
2025-09
CT#109
CP-252147
1026
1
F
Correction related to adhoc group call
19.4.0
2025-09
CT#109
CP-252147
1027
1
F
Add functional alias to adhoc group call
19.4.0
|
556719e8696c25b4ac3572453768229c
|
22.843
|
1 Scope
|
The present document provides additional use cases of UAV and identifies potential requirements to improve 5G system’s support of UAV applications, UAV operations and management, including:
• Provide additional information to the UAV operator/USS to execute pre-flight preparations and inflight operation (e.g, flight mission application, flight path recommendation, flight monitoring and control);
• Use 5G system to support enhancing the UAV flight/route management based on network capacity and QoS information along the planned route;
• Use 5G system to further enhance the safety and security of UAV operations, e.g. supporting UTM in UAV detection and DAA (Detect and Avoid);
• Identify potential new security, charging and regulatory requirements on 5GS, when used for UAS operation;
• Identify potential new requirements related to redundancy and reliability of command and control (C2) traffic for UAV.
For the identified use cases, a gap analysis is performed between potential new service requirements and existing 3GPP requirements and functionalities.
NOTE: This study investigates requirements for additional 5GS capabilities to assist UTM, with the assumption that liability and responsibility for UAV operation remain under the domain of the UTM/UAV operator.
NOTE: Potential overlaps with ongoing stage-2 work (on UAS), and other SA1 studies (e.g. FS_Sensing) have been considered and avoided.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] Global UTM Association UTM Architecture v1: https://www.gutma.org/docs/Global_UTM_Architecture_V1.pdf
[3] 3GPP TS 22.125: "Uncrewed Aerial System (UAS) support in 3GPP".
[4] 3GPP TS 22.261: "Service requirements for the 5G system".
[5] 3GPP TS 22.101: "Service aspects; Service principles".
|
556719e8696c25b4ac3572453768229c
|
22.843
|
3 Definitions of terms, symbols and abbreviations
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AAM Advanced Air Mobility
BRID Broadcast Remote Identification
BVLOS Beyond Visual Line of Sight
CAA Civil Aviation Authority
C2 Command and Control
C2C Command and Control Centre
DAA Detect And Avoid
GUTMA Global UTM Association
NASA North American Space Agency
UAS Uncrewed Aerial System
UAV-C Uncrewed Aerial Vehicle Controller
USS Uncrewed Aerial System Service Supplier
UTM Uncrewed Aerial System Traffic Management
VLoS Visual Line of Sight
|
556719e8696c25b4ac3572453768229c
|
22.843
|
4 Overview
|
The present document focuses on improving the 3GPP support for the applications and security for various scenarios using low altitude UAVs. The present document provides potential use cases and defines potential new service level requirements and KPIs for supporting identified use cases by 3GPP system. Use cases cover various scenarios to enhance the combination of 3GPP system and UAV ecosystem and this study presents use cases based on continuation/enhancement of TS 22.125 [3]. The present document considers service requirements related to further enhancement of the Network support and exposure for UAV usage and further enhancement of the control, safety, and security of UAV operations.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5 Use cases
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1 Use case on UAV detection
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.1 Description
|
3GPP aerial features are activated based on "aerial subscription" flag specified in Rel-15. This implies that an operator using these features will provide UAV users with USIMs that are associated to a user profile with the "aerial subscription" flag set.
It is however technically possible for a UAV user to insert a USIM not meant for UAV in a UE that is on board a UAV (this UE being used for C2C or for other purpose). The user could do that either intentionally (e.g. to have a lower tariff or to bypass some restrictions applied to UAVs) or not (e.g. because he/she is not aware that UAVs need to be used with specific USIMs).
In this case, with current specifications, the 3GPP network is not able to recognize that the UE is on board a UAV and therefore cannot activate aerial features. More importantly, the 3GPP network will not perform UAV Authentication and Authorization procedures with the UTM, and may cause the UE to use a frequency band that is not allowed for aerial usage where the UAV is located due to the risk of interference to users or adjacent frequency bands (e.g. military installation, weather radar). This has security implications. In addition, the 3GPP network cannot fulfill the requirements of TS 22.125 [3] applicable to UE on board a UAV.
From Rel-17 onwards, the 3GPP network is able to reject registration when the UE provides a "CAA-level UAV ID" and does not have the "aerial subscription" flag set in its subscription. This mitigates the above issue, but the issue still exists if the UE is pre-R17 or is not configured with a CAA-level UAV ID.
There is therefore a need to enable the 5G System network to detect that a UE is on board a UAV, without relying on subscription information or on indication provided by the UE.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.2 Pre-conditions
|
A UAV user has inserted in a UE on board a UAV, a USIM that is associated to a user profile without the "aerial subscription" flag set.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.3 Service Flows
|
1. The UE registers in 5GS and starts communicating. The UAV takes off.
2. The network detects that the UE is on board a UAV.
3. The network takes action, e.g. activates aerial features, changes the QoS, populates charging records, alert the UTM and/or let the UTM take over the communication used to control the UAV.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.4 Post-conditions
|
The UTM may take over the communication used to control the UAV and force the UAV to land safely.
Later, the UTM and/or network operator informs or reminds the user that a specific USIM needs to be used for proper operation of a UE on board a UAV.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.5 Existing features partly or fully covering the use case functionality
|
- "aerial subscription" flag in subscription;
- Provision of "CAA-level UAV ID" by the UE;
- detection of UE above altitude thresholds by the eNB / gNB (per TS 36.331 & TS 38.331).
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.1.6 Potential New Requirements needed to support the use case
|
[PR 5.1.6-001] The 5G system shall be able to detect that a connected UE is airborne, while UE’s subscription does not include the "aerial subscription" flag set.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2 Use case on supporting UAV pre-flight preparation
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.1 Description
|
During the operation of UAVs using the 3GPP network access, the network needs to ensure that the UAVs can access the network smoothly and timely. UAV flight mission need to be ensured for the real-time performance and stability of flight control link to guarantee the continuity of the flight.
5G network can provide wide-area, high-quality and secure connectivity that can enable cost-efficient UAV operations beyond visual line-of-sight (BVLOS) range. In some industrial UAV scenarios, the UAV would be provided pre-scheduled flight plan for autonomous flying. When UAV uses 3GPP network as the access type, the UTM/UAV operator may need to acknowledge the network status for flight path scheduling with the help of 3GPP network.5G system can assist the UTM and drone operator with providing alternative flight path based on the supported QoS in specific area or reconfigure network resources to achieve the needed QoS.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.2 Pre-conditions
|
Pipeline company uses UAV A and logistics company uses UAV B. UAV A and UAV B are both individual terminals that subscribe to the communication service from 5G network.
Operator A provides 5G network coverage and communication services for remote command and control (C2) communication between UAV and UAV control platform.
The UTM has good cooperation with Operator A to have UAV-related information which is fetched from the 5G network.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.3 Service Flows
|
Figure 5.2.3-1: Supporting UAV pre-flight preparation
1. The pipeline company plans to use UAV A to provide video inspection of pipelines from X to Y and the logistics company uses UAV B to deliver express from X to Z.
2. UAV/UAV-C A and UAV/UAV-C B register in 5G network and can communicate with UTM though 5G network.
3. The UAV-C A provides planned flight path information from X to Y to UTM (e.g. waypoints and required QoS from X to Y). The UAV-C B provides planned flight path on start point X, end point Z and needed QoS.
4. UTM checks with 5G system for required and needed QoS information in predictions/statistics (e.g. end-to-end latency, QoE) along required and possible flight paths.
5. Based on the available analytics information, the 5G system can provide confirmation that required QoS is available for UAV A flight path or alternatively can reconfigure network resources to be able to provide the required QoS to UAV A along the flight path. As UAV B can take alternative routes, 5G system can provide optimized flight path considering where the QoS is available.
6. UTM/UAS determines the final flight paths based on the information from Operator A and sends to UAV/UAV-C A and UAV/UAV-C B separately.
7. UAV A and UAV B receive the flight path information from UTM/UAS via the 5G system and start flight mission.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.4 Post-conditions
|
UAV A and UAV B can finish their respective tasks with the support of 5G system.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.5 Existing features partly or fully covering the use case functionality
|
None.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.2.6 Potential New Requirements needed to support the use case
|
[P.R 5.2.6-001] Based on operator’s policy, the 5G system shall be able to support a method to predict network conditions and QoS (e.g. bitrate, latency, reliability) along a continuous geographic planned flight path of a UAV at specific times of its expected flight duration.
[P.R 5.2.6-002] Based on operator’s policy, the 5G system shall be able to provide UTM with the information about geographic areas where UAV service requirements could or could not be met based on predicted network conditions and QoS (e.g. bitrate, latency, reliability).
[P.R 5.2.6-003] Based on 3rd party request, the 5G system shall be able to provide to the 3rd party alternative UAV flight paths, as long as UTM-provided required waypoints (e.g. start/end locations), required QoS, and exclusion zones are fulfilled.
[P.R 5.2.6-004] Based on 3rd party request and operator’s policy, the 5G system shall be able to reconfigure network resources to provide the required QoS along a UAV planned flight path, e.g. at particular geographical area(s) and time(s).
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3 Use case on Geofencing for Visual Line-of-Sight UAV missions
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.1 Description
|
3GPP has specified a wide range of aerial features, activated through an "aerial subscription". Three types of C2 communications have been defined for R17, in TS.22.125 [3]:
• Direct C2 communications (when the UAV controller and UAV establish a direct C2 link to communicate with each other);
• Network-Assisted C2 communications (when the UAV controller and UAV communicate with each other via 5G network);
• UTM-Navigated C2 communication (for pre-scheduled autonomous flights).
3GPP features for Network-Assisted C2 communications and UTM-Navigated C2 communication mostly cover Beyond Visual Line-of-Sight (BVLoS) UAV operations, and Direct C2 communications are constrained by their radio coverage range, which is generally much wider than the VLoS constraints imposed by airspace authorities.
In all three cases, it is thus technically possible that an UAV controller does not comply with airspace regulatory requirements related to VLoS operations.
Ensuring that an aerial UE is complying with regulatory Visual Line-of-Sight constraints, by supporting pre-flight preparations and inflight operation flight monitoring and control, enhances the safety and security of UAV operations.
There is a need to enable the 5G system to be aware if VLoS constraints should be applied to UAV operations, and if so, to monitor the relative positions of an aerial UE with respect to its pilot to ensure that this aerial UE is complying with Line-of-Sight constraints.
NOTE: UAV-C is capable of 3GPP communications or not, but remains attached to the DN using other technologies.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.2 Pre-conditions
|
The UAV is associated with an aerial UE profile and a “VLoS” option is activated together with its subscription. The UAV is associated with an UAV Controller (UAV-C). The 5G system is informed by the UTM of the maximal distance authorized between the UAV and the UAV-C (VLoS distance threshold, usually around 200 or 300m), which usually depends on airspace regulation and may potentially account for other conditions (e.g. weather, type of environment, type of UAV, temporary or localized special authorization, etc.).
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.3 Service Flows
|
1. The UAV registers in 5GS as an aerial UE with the VLoS option activated.
2. The UAV is associated with an UAV-C. The UAV takes off.
3. The network tracks the geolocalization of both the UAV and UAV-C, and deduces the distance between both. If the UAV-C does not belong to the 3GPP system, its geolocalization may be obtained, for example, from the USS/UTM.
4. In case this distance exceeds the VLoS threshold, the network takes action, e.g. alerts the UTM and/or lets the UTM takes over the communication used to bring back the UAV within the authorized VLoS constraints, or sends a new waypoint within the authorized VLoS constraints.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.4 Post-conditions
|
The UTM may take over the communication used to control the UAV and force the UAV to land safely.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.5 Existing features partly or fully covering the use case functionality
|
- "Aerial subscription" option in subscription, as specified in Rel-15;
- UAV / UAV-C association, as in TS 23.256 for example;
- Tracking of the geolocalization of the UAV as in TS 23.256 for example.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.3.6 Potential New Requirements needed to support the use case
|
[PR 5.3.6-001] The 5G system shall be able to be informed of VLoS regulatory requirements (e.g. maximal distance threshold) and shall be informed if the UTM needs to be supported in meeting such requirements for a given UAS.
[PR 5.3.6-002] The 5G system shall be able to track the UAV-Controller, regardless of the type of connection.
[PR 5.3.6-003] Based on MNO policies and/or regulatory requirements, the 5G system shall be able to alert the UTM, when the 5G system detects that a condition is met (e.g. maximal distance threshold exceeded).
[PR 5.3.6-004] Based on MNO policies and/or regulatory requirements, the 5G system shall enable the UTM to take over the communication used to control the UAV, when the 5G system detects that a condition is met (e.g. maximal distance threshold exceeded).
5.4. Use case on network-assisted UAV DAA
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.1 Description
|
Collection of information for UAV detection and avoidance in order to support tactical deconfliction is one of the key functions to guarantee UAV service safety. Previous studies on 3GPP mostly focused on the aspect that the detection and resolution of collisions is locally performed between UAVs using direct UAV to UAV communication over PC5. However, UAV to UAV DAA is only one component of the overall solution and, as in current aviation system, support by ground systems for tactical deconfliction and collision avoidance is an essential complement. With the development of network capabilities for the support of UAVs, new system capabilities like sensing in the 3GPP network can also effectively assist the UAV DAA scenario to ensure the flight safety by providing a ground-assisted component.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.2 Pre-conditions
|
UAV A is 3GPP aerial UE and subscribes the communication service from 5G network.
UAV B is an aerial vehicle not capable of 3GPP communications and could setup communication with USS/UTM directly.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.3 Service Flows
|
Figure 5.4.3-1: Network-assisted UAV DAA
1. UAV A registers in 5G network and can setup communications with UTM though 5G network. UAV B setup communication with UTM directly.
2. The UTM subscribes network-assisted UAV DAA service from Operator M.
3. Operator M could use base station(s) to perform sensing to collect information about the UAV A and B in certain area and provide the collected information to UTM for DAA operation or to UAV A.
4. Operator M could also collect information from UAV A about the flight status and reports to UTM.
5. UTM could trigger DAA notifications for the flying UAV A and B under its area based on the information from network.
6. UAV A and B receive the notification and take actions accordingly.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.4 Post-conditions
|
UAV A and B can fly safely under the control of UTM with the support of 5G network.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.5 Existing features partly or fully covering the use case functionality
|
SA1 has performed a study on UAV DAA in previous releases, where related normative stage 1 requirements are introduced in TS 22.125 [3].
TS 22.125 [3] clause 6.2 introduces the network support for UAV detection as below:
[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.
[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM to a UAS with a latency of less than 500ms.
[R-5.2.1-003] The 3GPP system shall be able to deliver the notifications received from a UTM to a UAV controller with a latency of less than 500ms.
[R-5.2.1-004] Based on MNO policies and/or regulatory requirements, the 3GPP system shall enable the UTM to take over the communication used to control the UAV.
TS 22.125 [3] clause 5.2 introduces the introduces network support for UAV avoidance as below:
[R-6.2-001] The 3GPP system shall provide means to allow a 3rd party to request and obtain real-time monitoring the status information (e.g., location of UAV, communication link status) of a UAV.
[R-6.2-002] Based on operator 's policy, the 3GPP system shall provide means to provide a 3rd party with the information regarding the service status for UAVs in a certain geographical area and/or at a certain time.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.4.6 Potential New Requirements needed to support the use case
|
[P.R 5.4.6-001] Based on operator’s policy, the 5G system shall be able to provide a method to provide UTM and UAVs with the information collected or generated by the 5G system (e.g., based on sensing results), including e.g. the location or relative distance of 3GPP UAVs and other flying objects (can be drones not using 3GPP connectivity) with timestamp.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5 Use case on the 3GPP network as an information source to the UTM
| |
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.1 Description
|
The UTM is a complex system in which actors outside the 3GPP System work to ensure the required safety level of UAS operations. For this reason, the UTM is defined by GUTMA (Global UTM Association) as “a system of stakeholders and technical systems collaborating in certain interactions, and according to certain regulations, to maintain safe separation of uncrewed aircraft, between themselves and from ATM users, at very low level, and to provide an efficient and orderly flow of traffic”
A system like UTM requires a high-quality set of data flows to remain fully aware of the system it is operating within and to effectively meet the mission brief. In figures 1 and 2 below, the GUTMA architecture [2] shows that a high number of data sources are considered to keep the UTM functional.
Figure 5.5.1-1: A view of a UTM system (source: GUTMA Global UTM Architecture v1 [2])
Figure 5.5.1-2: NASA UTM system (source: GUTMA Global UTM Architecture v1 [2])
The 3GPP System can act as a data source towards the UTM in order to provide spatial, surveillance, meteorological, and real-time positioning information.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.2 Pre-conditions
|
A UTM exists which is capable of accepting a 3GPP network as data source. A partner 3GPP operator is prepared to supply information to the UTM based on the capabilities of the network. Agreements on trust, responsibility, liability, privacy, and data management have been made.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.3 Service Flows
|
1. A UTM determines what data is required from the 3GPP network which can act as an information source.
2. Based on the capabilities of the 3GPP network, an operator begins to gather data according to agreements made with a UTM operator where the UTM provides the type of information and optional conditions regarding such information (e.g. reporting for a specific area, reporting specific events, etc.). This data is gathered from a number of sources which may include the following: RAN awareness of UE altitude (detect UEs above a certain altitude from the ground), Wireless Sensing results, UE registration, UE location reporting, network-based UE location determination.
3. The operator begins to feed data towards a UTM according to the information requested by the UTM.
4. The UTM accepts the data from the operator and is responsible for processing (corelating data sets, identifying objects, deduplication) and acting on (warnings, notifications) this data according to mechanisms outside the scope of 3GPP.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.4 Post-conditions
|
The UTM has an increased situational awareness because of the increased data provided by the 3GPP network.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.5 Existing features partly or fully covering the use case functionality
|
Related requirements in TS 22.125 [3]:
[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.
[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.
[R-5.1-006] The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future.
[R-5.1-009] The 3GPP system should enable an MNO to augment the data sent to a UTM with the following: network-based positioning information of UAV and UAV controller.
[R-5.1-017] The 3GPP system shall support the UTM in detection of UAV operating without authorization.
[R-6.3-001] The 3GPP network shall be able to support network-based 3D space positioning (e.g., with altitude 30~300m) of a UE onboard UAV.
Table 7.3-1 lists typical scenarios and the corresponding positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
Related requirements in TS 22.261 [4]:
The 5G system shall be able to make the position-related data available to an application or to an application server existing within the 5G network, external to the 5G network, or in the User Equipment.
NOTE: the position service latency can be tailored to the use cases.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.5.6 Potential New Requirements needed to support the use case
|
[P.R 5.5.6-001] Based on operator policy and UTM’s request, the 5G system shall be able to provide UTM with a UEs’ location (specifically 5GC Location Services derived positioning or UE-derived positioning e.g. from GNSS) and identity.
[P.R 5.5.6-002] Subject to user consent and national or regional regulation, based on operator policy, and the UTM’s request, the 5G system may be able to provide aerial object location(s) derived by 5G Wireless Sensing to the UTM.
|
556719e8696c25b4ac3572453768229c
|
22.843
|
5.6 Use case on supporting UAV inflight operations
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.