hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.13.11 Determining authorisation for initiating an MCPTT emergency adhoc group call
| If the controlling MCPTT function has received a SIP request for an MCPTT emergency adhoc group call with the <adhoc-emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-emergency-adhoc-group-call> element of the <ruleset> element of the MCPTT user ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.13.12 Determining authorisation for initiating an MCPTT imminent peril adhoc group call
| If the controlling MCPTT function has received a SIP request with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "true" and:
1) if the <allow-imminent-peril-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.13.13 Determining authorisation for cancelling the in-progress imminent peril state of an MCPTT group
| If the controlling MCPTT function has received a SIP request for an MCPTT group with the <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body set to a value of "false", the controlling MCPTT function determines, based on local policy (e.g if the requester is dispatcher or not, initiator of t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.14 Generating a SIP 403 response for priority call request rejection
| If the controlling MCPTT function has received a SIP request with the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body is set to "true" and this is an unauthorised request for an MCPTT emergency call as determined by the procedures of clause 6.3.3.1.13.2, the controlling MCPTT function shall... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.15 Sending a SIP re-INVITE request for MCPTT imminent peril group call
| This clause is referenced from other procedures.
The controlling MCPTT function shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4].
The controlling MCPTT function:
1) shall include in the Contact header field an MCPTT session identity for the MCPTT session with the g.3gpp.mcptt media feature tag ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.16 Handling the expiry of timer TNG2 (in-progress emergency group call timer)
| Upon expiry of timer TNG2 (in-progress emergency group call timer) for an MCPTT group, the controlling MCPTT function:
1) shall set the in-progress emergency state of the group to a value of "false";
2) shall, if an MCPTT group call or MCPTT group session is in progress on the indicated group, for each of the partici... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.17 Validate priority request parameters
| This clause is referenced from other procedures. This procedure validates the combinations of <emergency-ind>, <imminentperil-ind> and <alert-ind> in the application/vnd.3gpp.mcptt-info+xml MIME body included in:
1) a SIP INVITE request or SIP re-INVITE request; or
2) the body "URI" header field of the SIP URI includ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.18 Sending a SIP INFO request in the dialog of a SIP request for a priority call
| This clause is referenced from other procedures and describes how the controlling MCPTT function generates a SIP INFO request due to the receipt of a SIP request for a priority call.
The controlling MCPTT function:
1) shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [4] and IETF R... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.19 Retrieving Resource-Priority header field values
| This clause is referenced from other procedures.
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT emergency group call or MCPTT emergency private call or MCPTT emergency adhoc group call, the controlling MCPTT function:
1) shall retrieve... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.20 Generating a SIP MESSAGE request to indicate successful receipt of an emergency alert or emergency cancellation
| This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify the originator of an emergency alert or emergency cancellation that the request was successfully received.
The controlling MCPTT function:
1) shall generate a SIP MESSAGE request in ac... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.23 Populate mcptt-info MIME bodies for adhoc group emergency alert
| This clause is referenced from other procedures.
This clause describes the procedures for populating the application/vnd.3gpp.mcptt-info+xml and application/vnd.3gpp.mcptt-location-info+xml MIME bodies for an MCPTT adhoc group emergency alert. The procedure is initiated by the controlling MCPTT function when it has re... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.24 Generating a SIP MESSAGE request to containing the participant lists of an MCPTT adhoc group emergency alert
| This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify the authorized users of an MCPTT adhoc group emergency alert with the list of users participating in the MCPTT adhoc group emergency alert.
The controlling MCPTT function:
1) shall gen... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.25 Validate adhoc group priority request parameters
| This clause is referenced from other procedures. This procedure validates the combinations of <adhoc-emergency-ind>, and <imminentperil-ind> in the application/vnd.3gpp.mcptt-info+xml MIME body included in:
1) a SIP INVITE request or SIP re-INVITE request; or
2) the body "URI" header field of the SIP URI included in ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.1.26 Generating a SIP MESSAGE request to the participant lists of an MCPTT adhoc group with redirection information
| This clause is referenced from other procedures.
This clause describes the procedures for generating a SIP MESSAGE request to notify the authorized users of an MCPTT adhoc group with redirection information.
The controlling MCPTT function:
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4]... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2 Requests terminated by the controlling MCPTT function
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.1 SDP answer generation
| When composing the SDP answer according to 3GPP TS 24.229 [4], the controlling MCPTT function:
1) for the accepted media stream in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the media distribution function of the controlling... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.2 Receipt of a SIP INVITE request
| On receipt of an initial SIP INVITE request the controlling MCPTT function shall cache SIP feature tags, if received in the Contact header field and if the specific feature tags are supported.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.3 Sending a SIP response to a SIP INVITE request
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.3.1 Provisional response
| When sending SIP provisional responses with the exception of the SIP 100 (Trying) response to the SIP INVITE request the controlling MCPTT function:
1) shall generate the SIP provisional response;
2) shall include a P-Asserted-Identity header field with the public service identity of the controlling MCPTT function;
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.3.2 Final response
| When sending a SIP 200 (OK) response to the initial SIP INVITE request, the controlling MCPTT function:
1) shall generate the SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the Session-Expires header field and start supervising the SIP session according to rules and pr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.2.4 Receiving a SIP BYE request
| Upon receiving a SIP BYE request the controlling MCPTT function:
1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.380 [5] for releasing the media plane resource associated with the SIP session towards the MCPTT client;
NOTE: The non-controlling MCPTT function is also regarded as a MCPTT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.3 Handling of the acknowledged call setup timer (TNG1)
| When the controlling MCPTT function receives a SIP INVITE request to initiate a group session and there are members of the group document retrieved from the group management server that are affiliated and are marked as <on-network-required> as specified in 3GPP TS 24.481 [31], then the controlling MCPTT function shall ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.4 Generating a SIP NOTIFY request
| The controlling MCPTT function shall generate a SIP NOTIFY request according to 3GPP TS 24.229 [4] with the clarification in this clause.
In the SIP NOTIFY request, the controlling MCPTT function:
1) shall set the P-Asserted-Identity header field to the public service identity of the controlling MCPTT function;
2) s... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.5 Handling of the group call timer (TNG3)
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.5.1 General
| When the controlling MCPTT function receives a SIP INVITE request to initiate a group session, then after an MCPTT session identity has been allocated for the group session and if the <on-network-maximum-duration> element is present in the group document as specified in 3GPP TS 24.481 [31], the controlling MCPTT functi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.5.2 Interaction with the in-progress emergency group call timer (TNG2)
| If the controlling MCPTT function starts timer TNG2 (in-progress emergency group call timer), it shall not start timer TNG3 (group call timer).
If timer TNG3 (group call timer) is running and the MCPTT group call is upgraded to an MCPTT emergency group call, then the controlling MCPTT function shall stop timer TNG3 (g... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.3.6 Void
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4 Non-controlling MCPTT function of an MCPTT group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.1 Request initiated by the non-controlling MCPTT function of an MCPTT group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.1.1 SDP offer generation
| The SDP offer is generated based on the received SDP offer. The SDP offer generated by the non-controlling MCPTT function of an MCPTT group:
1) shall include only one SDP media-level section for MCPTT speech as contained in the received SDP offer; and
2) shall include one SDP media-level section for media plane contr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.1.2 Sending an INVITE request towards the MCPTT client
| This clause is referenced from other procedures.
The non-controlling MCPTT function of an MCPTT group shall generate initial SIP INVITE requests according to 3GPP TS 24.229 [4].
For each SIP INVITE request, the non-controlling MCPTT function of an MCPTT group:
1) shall generate a new MCPTT session identity for the M... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.1.3 Sending a SIP INFO request
| This clause is referenced from other procedures.
The non-controlling MCPTT function shall generate a SIP INFO request according to rules and procedures of 3GPP TS 24.229 [4] and IETF RFC 6086 [64].
The non-controlling MCPTT function:
1) shall include the Info-Package header field set to g.3gpp.mcptt-floor-request;
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.1.4 Sending an INVITE request towards the controlling MCPTT function
| This clause is referenced from other procedures.
The non-controlling MCPTT function shall generate a SIP INVITE request according to rules and procedures of 3GPP TS 24.229 [4].
The non-controlling MCPTT function:
1) shall include in the Contact header field the g.3gpp.mcptt media feature tag, the g.3gpp.icsi-ref med... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.2 Requests terminated by the non-controlling MCPTT function of an MCPTT group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.2.1 SDP answer generation
| When composing the SDP answer according to 3GPP TS 24.229 [4], the non-controlling MCPTT function of an MCPTT group:
1) for the accepted media stream in the received SDP offer:
a) shall replace the IP address and port number in the received SDP offer with the IP address and port number of the non-controlling MCPTT fu... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.2.2 Sending a SIP response to the SIP INVITE request
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.2.2.1 Sending a SIP 183 (Session Progress) response
| When sending a SIP 183 (Session Progress) the non-controlling MCPTT function of an MCPTT group:
1) shall generate a SIP 183 (Session Progress) response according to 3GPP TS 24.229 [4];
2) shall include the following in the Contact header field:
a) the g.3gpp.mcptt media feature tag; and
b) the g.3gpp.icsi-ref media... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.2.2.2 Sending a SIP 200 (OK) response
| When sending a SIP 200 (OK) response, the non-controlling MCPTT function of an MCPTT group:
1) shall generate the SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the Session-Expires header field and start supervising the SIP session according to rules and procedures of ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.3 Generating a SIP NOTIFY request
| The non-controlling MCPTT function shall generate a SIP NOTIFY request according to 3GPP TS 24.229 [4] with the clarification in this clause.
In the SIP NOTIFY request, the non-controlling MCPTT function:
1) shall set the P-Asserted-Identity header field to the public service identity of the non-controlling MCPTT fun... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.4.4 Void
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5 Retrieving and processing a group document
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5.1 General
| This clause describes how an MCPTT server accesses a group document from a group management server. The MCPTT server which accesses a group document performs the role of a controlling MCPTT function or performs the role of a non-controlling MCPTT function of an MCPTT group when accessing a group document. In such cases... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5.2 Rules for retrieving Group Document(s)
| NOTE 1: In this clause, "MCPTT server" can refer to either the controlling MCPTT function of an MCPTT group or the non-controlling MCPTT function of an MCPTT group.
When the group document is retrieved for the controlling MCPTT function procedures or for the non-controlling MCPTT function terminating procedures (claus... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5.3 Rules for joining a group session
| The following conditions shall be met for the controlling MCPTT function to allow an MCPTT user to join an existing group session:
1) an <entry> element exists in the <list> element of the group document for the MCPTT user;
2) a <rule> exists in the group document with:
a) the <is-list-member> element of the <condit... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5.4 Rules for initiating a prearranged group session
| When the non-controlling MCPTT function of an MCPTT group receives a request to intiate a group session for the calling MCPTT user, if:
1) one of the following conditions is met:
a) the <on-network-regrouped> element in the <list-service> element is present in the group document associated with the MCPTT group ID ide... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.5.5 Determining the group members to invite
| The MCPTT server shall only invite affiliated group members to a group session.
If the group is not a regroup based on a preconfigured group, the MCPTT server determines the affiliated members from the entries contained in the <list> element of the group document by following the procedures specified in clause 6.3.6.
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.6 Affiliation check
| The MCPTT server checks if an MCPTT user is affiliated to an MCPTT group at an MCPTT client by following the procedures specified below:
1. the MCPTT server shall find the applicable MCPTT group information entry as an MCPTT group information entry of the list of MCPTT group information entries described in clause 9.2... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.7 Error handling
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.7.1 Public service identity does not exist
| Upon receiving a request that includes the Request-URI set to a public service identity that is not allocated in the participating or the controlling MCPTT function, the participating or the controlling MCPTT function shall return a SIP 404 (Not Found) response.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.8 Session release policy
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.8.1 Session release policy for group call
| If:
1) the call is a pre-arranged group call, or a broadcast group call, or an adhoc group call and if the controlling MCPTT function receives an indication from the media plane that the T4 (Inactivity) timer specified in 3GPP TS 24.380 [5] expired;
2) the call is a pre-arranged group call, or a broadcast group call,... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.3.8.2 Session release policy for private call
| If:
1) the controlling MCPTT function receives an indication from the media plane that the T4 (Inactivity) timer specified in 3GPP TS 24.380 [5] expired;
2) the MCPTT session has lasted longer than the maximum of duration of private call; or
3) there are only one or no participants in the MCPTT session;
the control... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.4 Implicit floor request
| An initial SIP INVITE request fulfilling the following criteria shall be regarded by the MCPTT server as an implicit floor request by the originating MCPTT client when the MCPTT client:
1) initiates an MCPTT speech session or initiates a pre-established session that is not used for a remotely initiated MCPTT ambient l... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.5 Handling of MIME bodies in a SIP message
| The MCPTT client and the MCPTT server shall support several MIME bodies in SIP request and SIP responses.
When the MCPTT client or the MCPTT server sends a SIP message and the SIP message contains more than one MIME body, the MCPTT client or the MCPTT server:
1) shall, as specified in IETF RFC 2046 [21], include one ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6 Confidentiality and Integrity Protection
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.1 General
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.1.1 Applicability and exclusions
| The procedures in clauses 6.6 apply in general to all procedures described in clause 9, clause 10, clause 11 and clause 12 with the exception that the confidentiality and integrity protection procedures for the registration and service authorisation procedures are described in clause 7.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.1.2 Performing XML content encryption
| Whenever the MCPTT UE includes XML elements or attributes pertaining to the data specified in clause 4.8 in SIP requests or SIP responses, the MCPTT UE shall perform the procedures in clause 6.6.2.3.1.
Whenever the MCPTT server includes XML elements or attributes pertaining to the data specified in clause 4.8 in SIP r... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.1.3 Performing integrity protection on an XML body
| The functional entity shall perform the procedures in the clause just prior to sending a SIP request or SIP response.
1) The MCPTT UE shall perform the procedures in clause 6.6.3.3.1; and
2) The MCPTT server shall perform the procedures in clause 6.6.3.3.2.
NOTE: The procedures in clause 6.6.3.3.1 and clause 6.6.3.3... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.1.4 Verifying integrity of an XML body and decrypting XML elements
| Whenever the functional entity (i.e. MCPTT UE or MCPTT server) receives a SIP request or a SIP response, the functional entity shall perform the following procedures before performing any other procedures.
1) The functional entity shall determine if integrity protection has been applied to an XML MIME body by followin... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2 Confidentiality Protection
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.1 General
| In general, confidentiality protection is applied to specific XML elements and attributes in XML MIME bodies in SIP requests and responses as specified in clause 4.8. However in the case of SIP REFER requests used for pre-established sessions, confidentiality protection is required for:
the targeted MCPTT ID or MCPTT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.2 Keys used in confidentiality protection procedures
| Confidentiality protection uses an XPK to encrypt the data which (depending on who is the sender and who is the receiver of the encrypted information) can be a CSK or an SPK as specified in clause 4.8. An XPK-ID (CSK-ID/SPK-ID) is used to key the XPK (CSK/SPK). It is assumed that before the procedures in this clause ar... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.3 Procedures for sending confidentiality protected content
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.3.1 MCPTT client
| If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <confidentiality-protection> element is present in the Service Configuration document, then sending confidentiality protected content from the MCPTT client to the MCPTT server is ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.3.2 MCPTT server
| If the <confidentiality-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <confidentiality-protection> element is present in the Service Configuration document, then sending confidentiality protected content from the MCPTT server to the MCPTT client is ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.3.3 Content Encryption in XML elements
| The following procedures shall be performed by an MCPTT client or an MCPTT server:
1) perform encryption as specified in W3C: "XML Encryption Syntax and Processing Version 1.1", https://www.w3.org/TR/xmlenc-core1/ [60] clause 4.3, using the "AES-128-GCM algorithm HMAC" as the encryption algorithm and the XPK as the ke... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.3.4 Attribute URI Encryption
| The following procedures shall be performed by an MCPTT client or an MCPTT server:
1) perform encryption as specified in IETF RFC 5288 [83], using the "AES-128-GCM algorithm HMAC" as the encryption algorithm and the XPK as the key, with a 96 bit randomly selected IV; and
2) replace the URI to be protected in the attr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.4 Procedures for receiving confidentiality protected content
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.4.1 Determination of confidentiality protected content
| The following procedure is used by the MCPTT client or MCPTT server to determine if an XML element is confidentiality protected.
1) if an XML element contains the <EncryptedData> XML element, then the content of the XML element is confidentiality protected; and
2) if an XML element does not contain the <EncryptedData... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.4.2 Decrypting confidentiality protected content in XML elements
| The following procedure shall be performed by an MCPTT client or an MCPTT server to decrypt an individual XML element that has a type of "encrypted" within an XML MIME body:
1) if the <EncryptedData> XML element or any of its sub-elements as described in 3GPP TS 33.180 [78] are not present in the MIME body then send a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.4.3 Decrypting confidentiality protected URIs in XML attributes
| The following procedure shall be performed by an MCPTT client or an MCPTT server to decrypt a URI in an attribute in a XML document:
1) the value between ";iv=" and the next ";" provides the base64 encoded value of the 96 bit IV and the value between ";=key-id" and the next ";" defines the key which has been used for ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.2.5 MCPTT server copying received XML content
| The following procedure is executed when an MCPTT server receives a SIP request containing XML MIME bodies, where the content needs to be copied from the incoming SIP request to the outgoing SIP request.
The MCPTT server:
1) shall copy the XML elements from the XML MIME body of the incoming SIP request that do not co... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3 Integrity Protection of XML documents
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.1 General
| Integrity protection can be applied to a whole XML MIME body. When integrity protection is enabled, all XML MIME bodies transported in SIP requests and responses are integrity protected. The following XML MIME bodies used in the present specification in SIP signalling can be integrity protected:
- application/vnd.3gpp... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.2 Keys used in integrity protection procedures
| Integrity protection uses an XPK to sign the data which (depending on who is the sender and who is the receiver of the signed information) can be a CSK or an SPK as specified in clause 4.8. An XPK-ID (CSK-ID/SPK-ID) is used to key the XPK (CSK/SPK). It is assumed that before the procedures in clause 6.6.3.3 and clause ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.3 Sending integrity protected content
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.3.1 MCPTT client
| If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true" or no <integrity-protection> element is present in the Service Configuration document, then sending integrity protected content from the MCPTT client to the MCPTT server is enabled, and the M... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.3.2 MCPTT server
| If the <integrity-protection> element in the Service Configuration document as specified in 3GPP TS 24.484 [50] is set to "true", or no <integrity-protection> element is present in the Service Configuration document, then sending integrity protected content from the MCPTT server to the MCPTT client is enabled. If the <... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.3.3 Integrity protection procedure
| The following procedure shall be performed by the MCPTT client and MCPTT server to integrity protect the XML bodies defined by the MIME types listed in clause 6.6.3.1:
1) include a Content-Type header field set to "application/vnd.3gpp.mcptt-signed+xml";
2) for each of the MIME types defined in clause 6.6.3.1 where t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.4 Receiving integrity protected content
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.4.1 Determination of integrity protected content
| The following procedure is used by the MCPTT client or MCPTT server to determine if an XML MIME body is integrity protected.
1) if the <Signature> XML element is not present in the XML MIME body, then the content is not integrity protected; and
2) if the <Signature> XML element is present in the XML MIME body, then t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.6.3.4.2 Verification of integrity protected content
| The following procedure is used by the MCPTT client or MCPTT server to verify the integrity of an XML MIME body:
1) if the required sub-elements of the <Signature> as described in 3GPP TS 33.180 [78] are not present in the MIME body and if not present, are not known to the sender and recipient by other means, then the... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.7 Priority sharing
| The participating MCPTT function shall enable or disable priority sharing as specified in 3GPP TS 24.229 [4].
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.8 Procedures at the MCPTT gateway
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.8.1 General
| As described in clause 5.5, the MCPTT gateway servers are inserted in the path between MCPTT functions that reside in MCPTT systems from different trust domains.
This clause specifies the behavior of an MCPTT gateway server that acts as an exit point from an MCPTT system or as an entry point in an MCPTT system.
Local... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.8.2 MCPTT gateway server acting as an exit point from an MCPTT system
| When acting as an exit point from a local MCPTT system to an interconnected MCPTT system, the MCPTT gateway server receives SIP requests and SIP responses intended for the controlling, non-controlling or participating function in the interconnected MCPTT system.
When receiving an outgoing SIP message, the MCPTT gatewa... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.8.3 MCPTT gateway server acting as an entry point in an MCPTT system
| When acting as an entry point in an MCPTT system from an interconnected MCPTT system, the MCPTT gateway receives SIP requests and SIP responses intended for the controlling, non-controlling or participating function in the local MCPTT system.
When receiving an incoming SIP message, the MCPTT gateway server acting as a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.8.4 Local policies enforcement
| Below is one example of local policy enforcement that can be handled by an MCPTT gateway server.
If an MCPTT gateway server acting as an exit point receives a SIP request or a SIP response that contains sensitive information that cannot be exposed to the targeted partner system based on local policies but does not pr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7 Registration and service authorisation
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.1 General
| This clause describes the procedures for SIP registration and MCPTT service authorization for the MCPTT client and the MCPTT service. The MCPTT UE can use SIP REGISTER or SIP PUBLISH for MCPTT service settings to perform service authorization for MCPTT. The decision which method to use is based on implementation and on... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2.1 SIP REGISTER request for service authorisation
| When the MCPTT client performs SIP registration for service authorisation the MCPTT client shall perform the registration procedures as specified in 3GPP TS 24.229 [4].
The MCPTT client shall include the following media feature tags in the Contact header field of the SIP REGISTER request:
1) the g.3gpp.mcptt media fe... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2.2 SIP PUBLISH request for service authorisation and MCPTT service settings
| If based on implementation the MCPTT client decides to use SIP PUBLISH for MCPTT server settings to also perform service authorization and
1) has successfully finished the user authentication procedure as described in 3GPP TS 24.482 [49]; and
2) has available an access-token;
then the MCPTT client:
1) shall perform... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2.3 Sending SIP PUBLISH for MCPTT service settings only
| To set, update, remove or refresh the MCPTT service settings, the MCPTT client shall generate a SIP PUBLISH request according 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 4354 [55]. In the SIP PUBLISH request, the MCPTT client:
1) shall perform the procedures in clause 7.2.1A;
2) if confidentiality protection ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2.4 Determination of MCPTT service settings
| In order to discover MCPTT service settings of another MCPTT client of the same MCPTT user or to verify the currently active MCPTT service settings of this MCPTT client, the MCPTT client shall generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26], and IETF RFC 4354 [55].
In the ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.2.5 Receiving a CSK key download message
| When the MCPTT client receives a SIP MESSAGE request containing:
1) a P-Asserted-Service header field containing the "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
2) an application/mikey MIME body;
Then, if the key identifier within the CSB-ID of the MIKEY payload is a CSK-ID (4 most-significant bits have the value '... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3 MCPTT server procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.1 General
| The MCPTT server obtains information that it needs to implement service authorization specific requirements from:
a) any received third-party SIP REGISTER request (e.g. including information contained in the body of the third-party SIP REGISTER request) as specified in 3GPP TS 24.229 [4]. The body will carry the SIP R... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.2 SIP REGISTER request for service authorisation
| The MCPTT server shall support obtaining service authorization specific information from the SIP REGISTER request sent from the MCPTT client and included in the body of a third-party SIP REGISTER request.
NOTE 1: 3GPP TS 24.229 [4] defines how based on initial filter criteria the SIP REGISTER request sent from the UE ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.