hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4 General
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.1 MCPTT overview
| The MCPTT service supports communication between several users (i.e., group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users. Group calls and private calls can be provided on-network and off-network. ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.2 URI and address assignments
| In order to support MCPTT, the following URI and address assignments are assumed:
1) the participating MCPTT function is configured to be reachable using:
a) public service identities identifying pre-established sessions on the MCPTT server serving the MCPTT user;
b) the MBMS public service identity of the participa... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.3 MCPTT speech
| A session that contains MCPTT speech is either a full-duplex session or a half-duplex session with an SDP media component containing an audio media type with a codec suitable for conversational speech that exists between an MCPTT client and an MCPTT server.
If the MCPTT speech session is a half-duplex session, it addi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.4 Warning Header Field
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.4.1 General
| The MCPTT server can include a free text string in a SIP response to a SIP request. When the MCPTT server includes a text string in a response to a SIP INVITE request the text string is included in a Warning header field as specified in IETF RFC 3261 [24]. The MCPTT server includes the Warning code set to 399 (miscella... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.4.2 Warning texts
| The text string included in a Warning header field consists of an explanatory text preceded by a 3-digit text code, according to the following format in Table 4.4.2-1.
Table 4.4.2-1 ABNF for the Warning text
warn-text =/ DQUOTE mcptt-warn-code SP mcptt-warn-text DQUOTE
mcptt-warn-code = DIGIT DIGIT DIGIT
m... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.5 MCPTT session identity
| The MCPTT session identity is a SIP URI, which identifies the MCPTT session between:
- the MCPTT client and the participating MCPTT function;
- the participating MCPTT function and the controlling MCPTT function
- the controlling MCPTT function and the non-controlling MCPTT function; and
- the non-controlling MCPTT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.6 MCPTT priority calls and alerts
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.6.1 MCPTT emergency group calls
| MCPTT emergency group calls as defined by 3GPP TS 23.379 [3] are supported by the procedures in this specification. The following MCPTT emergency group call functionalities are described:
- MCPTT emergency group call origination;
- upgrade of an MCPTT group call to an MCPTT emergency group call; and
- in-progress gr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.6.2 MCPTT emergency private calls
| MCPTT emergency private calls as defined by 3GPP TS 23.379 [3] are supported by the procedures in this specification. The following MCPTT emergency private call functionalities are specified in the present document:
- MCPTT emergency private call origination with optional MCPTT emergency alert initiation;
- upgrade o... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.6.3 MCPTT emergency alerts
| MCPTT emergency alerts as defined by 3GPP TS 23.379 [3] are supported by the procedures in this specification. The following MCPTT emergency group call functionalities are specified in the present document:
- MCPTT emergency alert origination; and
- MCPTT emergency alert cancellation.
MCPTT emergency alerts are supp... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.6.4 MCPTT imminent peril group call
| MCPTT imminent peril group calls as defined by 3GPP TS 23.379 [3] are supported by the procedures in this specification. The following MCPTT imminent peril group calls functionalities are specified in the present document:
- MCPTT imminent peril group calls origination;
- upgrade of an MCPTT group call to an MCPTT im... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.7 Communication security
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.7.1 Media security
| If a mission critical organisation requires MCPTT users to communicate using end-to-end security, a security context needs to be established between the initiator of the call and the recipient(s) of the call, prior to the establishment of media, or floor control signalling. This provides assurance to MCPTT users that n... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.7.2 Signalling security
| Signalling security is established between the participating MCPTT function and the MCPTT client. This allows the following signalling to be integrity and confidentiality protected through the communication path between them:
- Signalling plane control (unicast only): Sensitive application data (as described in clause... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.8 Protection of sensitive application data
| In certain deployments, for example, in the case that the MCPTT operator uses the underlying SIP core infrastructure from the carrier operator, the MCPTT operator can prevent certain sensitive application data from being visible in the clear to the SIP layer. The following data are classed as sensitive application data... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.9 Pre-established session
| When establishing a pre-established session, the MCPTT client negotiates the media parameters, including establishing IP addresses and ports using interactive connectivity establishment (ICE) as specified in IETF RFC 8445 [89] and IETF RFC 8839 [90] with the participating MCPTT function, prior to using the pre-establis... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.10 MCPTT client ID
| The MCPTT client assigns the MCPTT client ID when the MCPTT client is used for the first time. The MCPTT client generates the MCPTT client ID as specified in clause 4.2 of IETF RFC 9562 [67].
The MCPTT client preserves the MCPTT client ID:
- while the MCPTT client is SIP registered as specified in 3GPP TS 24.229 [4];... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.11 Off-network MCPTT
| Off-network services are available for the user if the value of "/<x>/<x>/OffNetwork/Authorised" leaf node present in user profile as specified in 3GPP TS 24.483 [45] is set to "true".
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.12 Broadcast Group Calls
| A broadcast group call is a group call where the initiating MCPTT user expects no response from the other MCPTT users, so that when the user's transmission is complete, so is the call. The functionality in the present release of the specification for broadcast group calls is not compliant to the requirements for user-b... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.13 MCPTT Resource Management
| MCPTT utilizes the QoS functionality of a 3GPP network. For MCPTT calls dedicated bearers are used for the media plane and could be used for the control plane. To do this the MCPTT system shall requests resources from the 3GPP network over:
- Rx interface for 4G and 5G networks as defined in 3GPP TS 29.214 [79];
- N5... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 4.14 Functional alias
| A functional alias is a user selectable alias that is tied to the assignment or task of the MCPTT user. A functional alias can be used to identify for example the dispatcher role assigned to a particular MCPTT user. The functional alias is (similarly to MCPTT ID) a shared identity among other MCPTT users, so the MCPTT ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5 Functional entities
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.1 Introduction
| This clause associates the functional entities with the MCPTT roles described in the stage 2 architecture document (see 3GPP TS 23.379 [3]).
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.2 MCPTT client
| To be compliant with the procedures in the present document, an MCPTT client shall:
- act as the user agent for all MCPTT application transactions (e.g. initiation of a group call); and
- support handling of the MCPTT client ID as described in clause 4.10.
To be compliant with the on-network procedures in the presen... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3 MCPTT server
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3.1 General
| An MCPTT server can perform the controlling role for group calls and private calls as defined in 3GPP TS 23.379 [3].
An MCPTT server can perform the participating role for group calls and private calls as defined in 3GPP TS 23.379 [3].
An MCPTT server can perform a non-controlling role for temporary group calls invol... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3.2 Functional connectivity models
| The following figures give an overview of the connectivity between the different functions of the MCPTT server as described in clause 5.3.1.
NOTE: Separate boxes are shown for each of the functions of the MCPTT server. In each MCPTT system, these functions can be physically combined into one MCPTT server or can be imp... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3.3 Failure case
| When initiating a failure response to any received request, depending on operator policy, the MCPTT server may insert a SIP Response-Source header field with an "fe" header field parameter constructed with the URN namespace "urn:3gpp:fe", the fe-id part of the URN set to "as" and the "role" header field parameter set t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3.4 Management of MBMS bearers
| When providing services over MBMS, an MCPTT server acting in the participating MCPTT function role shall:
- allocate TMGIs and activate MBMS bearers in MBMS service areas to be used for MCPTT media and media control distribution via multicast, per 3GPP TS 23.468 [57] and 3GPP TS 29.468 [42];
- deactivate MBMS bearers... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.3.5 Management of MBS sessions
| When providing services over MBS, an MCPTT server acting in the participating MCPTT function role shall:
- create MBS sessions in MBS service areas to be used for MCPTT media and media control distribution via multicast and broadcast, per 3GPP TS 23.247 [91];
- delete the MBS sessions when no longer necessary, per 3G... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.4 MCPTT UE-to-network relay
| To be compliant with the procedures in the present document for service continuity, an MCPTT UE- to-network relay shall support the ProSe UE-to-network relay procedures as specified in 3GPP TS 24.334 [28] and 3GPP TS 23.379 [3].
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.5 MCPTT gateway server
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.5.1 General
| To allow interconnection between MCPTT system in different trust domains, MC Gateway Servers can be optionally added on the path between controlling and participating MCPTT functions.
An MCPTT gateway server acts as a SIP and HTTP proxy for signalling with a partner MCPTT system in a different trust domain.
An MCPTT ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.5.2 Functional connectivity models
| The following figures give an overview of the connectivity between the different functions of the MCPTT server in different trust domains when MCPTT gateway servers are used.
Figure 5.5.2-1 shows the roles of the MCPTT servers in a non trusted relationship between a primary MCPTT system and a partner MCPTT system. Her... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.6 MCPTT gateway UE
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.6.1 General
| An MCPTT gateway UE enables MCPTT service access for a MCPTT user utilizing non-3GPP device connected to the MCPTT gateway UE via non-3GPP access network.
NOTE: A UE that is not using 3GPP network access is also considered a non-3GPP device in this context.
An MCPTT gateway UE provides the following MCPTT gateway fun... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.6.2 Functional connectivity models
| The following figures give an overview of the connectivity between the different functional entities when using a MCPTT gateway. One MCPTT client can only utilize one MCPTT gateway UE at the same time.
NOTE: MC clients for other service types (e.g. MCVideo or MCData) can utilize the MC gateway UE supporting the corre... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 5.6.3 QoS for MCPTT gateway UE
| When the MCPTT client is on a non-3GPP device the use of the MCPTT gateway UE requires an IP network behind the MCPTT gateway UE. In a 5G network this can be achieved by the use of framed routing (see reference 3GPP TS 23.501 [95]). In a 4G and 5G network this can be achieved by using local IP network behind the MCPTT ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6 Common procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.1 Introduction
| This clause describes the common procedures for each functional entity as specified.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.0 Distinction of requests at the MCPTT client
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.0.1 SIP MESSAGE request
| The MCPTT client needs to distinguish between the following SIP MESSAGE requests:
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml" and including an XML body containing a Location root element containing a Configuration elemen... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.1 SDP offer generation
| The SDP offer shall contain one SDP media-level clause for MCPTT speech according to 3GPP TS 24.229 [4] and, may contain one SDP media-level section for a media plane control messages according to 3GPP TS 24.380 [5].
When composing an SDP offer according to 3GPP TS 24.229 [4] the MCPTT client:
1) shall set the IP add... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.2 SDP answer generation
| When the MCPTT client receives an initial SDP offer for an MCPTT session, the MCPTT client shall process the SDP offer and shall compose an SDP answer according to 3GPP TS 24.229 [4].
When composing an SDP answer, the MCPTT client:
1) shall accept the MCPTT speech media stream in the SDP offer;
2) shall set the IP a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3 Commencement modes
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.1 Automatic commencement mode
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.1.1 Automatic commencement mode for private calls
| When performing the automatic commencement mode procedures, the MCPTT client:
1) shall accept the SIP INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
2) shall include the option tag "timer" in a Require header field of the SIP 200 (OK) response;
3) shall i... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.1.2 Automatic commencement mode for group calls
| When performing the automatic commencement mode procedures, the MCPTT client shall follow the procedures in clause 6.2.3.1.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.2 Manual commencement mode
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.2.1 Manual commencement mode for private calls
| When performing the manual commencement mode procedures:
1) if the MCPTT user declines the MCPTT session invitation the MCPTT client shall send a SIP 480 (Temporarily Unavailable) response towards the MCPTT server with the warning text set to: "110 user declined the call invitation" in a Warning header field as specif... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.3.2.2 Manual commencement mode for group calls
| When performing the manual commencement mode procedures:
1) the terminating MCPTT client may automatically generate a SIP 183 (Session Progress) in accordance with 3GPP TS 24.229 [4], prior to the MCPTT user's acknowledgement; and
2) if the MCPTT user declines the MCPTT session invitation the MCPTT client shall send ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.4 Leaving an MCPTT session initiated by MCPTT client
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.4.1 On-demand session case
| Upon receiving a request from an MCPTT user to leave an MCPTT session established using on-demand session signalling, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
3) shall set the Request-URI to the M... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.4.2 Pre-established session case
| Upon receiving a request from an MCPTT user to leave an MCPTT session within a pre-established session, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate an initial SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.5 Releasing an MCPTT session initiated by MCPTT client
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.5.1 On-demand session case
| When the MCPTT client wants to release an MCPTT session using on-demand session signalling, the MCPTT client:
1) if the session is in the process of being established, shall send a SIP CANCEL request according to 3GPP TS 24.229 [4] and skip the rest of the steps;
2) shall interact with the media plane as specified in... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.5.2 Pre-established session case
| When the MCPTT client wants to release an MCPTT call using a pre-established session, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5];
2) shall generate an initial SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.6 Receiving an MCPTT session release request
| Upon receiving a SIP BYE request, the MCPTT client:
1) shall interact with the media plane as specified in 3GPP TS 24.380 [5]; and
2) shall send SIP 200 (OK) response towards MCPTT server according to 3GPP TS 24.229 [4].
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.7 Void
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8 Priority call conditions
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.0 General
| The clauses of the parent clause contain common procedures to be used for MCPTT emergency group calls and MCPTT imminent peril group calls.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1 MCPTT emergency group call conditions
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.1 SIP INVITE request or SIP REFER request for originating MCPTT emergency group calls
| This clause is referenced from other procedures.
When the MCPTT emergency state is set and the MCPTT user is authorised to initiate an MCPTT emergency group call on the targeted MCPTT group as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) shall include in the application/vnd.3gpp.mcptt-info+x... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.2 Resource-Priority header field for MCPTT emergency group calls
| This clause is referenced from other procedures.
If the MCPTT emergency group call state is set to either "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted" and this is an authorised request for an MCPTT emergency group call as determined by the procedures of clause 6.2.8.1.8, or the MCPTT client e... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.3 SIP re-INVITE request for cancelling MCPTT in-progress emergency group state
| This clause is referenced from other procedures.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to "MEA 1: no-alert", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given belo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.4 Receiving a SIP 2xx response to a SIP request for a priority call
| In the procedures in this clause, a priority group call refers to an MCPTT emergency group call or an MCPTT imminent peril group call.
On receiving a SIP 2xx response to a SIP request for a priority group call, the MCPTT client:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-requested" o... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a priority group call
| In the procedures in this clause, a priority group call refers to an MCPTT emergency group call or an MCPTT imminent peril group call.
Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for a priority group call the MCPTT client:
1) if the MCPTT emergency group call state is se... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.6 Determining authorisation for initiating or cancelling an MCPTT emergency alert
| If the MCPTT client receives a request from the MCPTT user to send an MCPTT emergency alert and:
1) if the <allow-activate-emergency-alert> 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 calling MCPTT user (see the MCPT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.7 Determining authorisation for cancelling the in-progress emergency state of an MCPTT group
| When the MCPTT client receives a request from the MCPTT user to cancel the in-progress emergency state of a group the MCPTT client, determines, based on local policy (e.g if the requester is dispatcher or initiator of the MCPTT emergency group call etc), whether to send the emergency group state cancel request or not.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.8 Determining authorisation for originating a priority group call
| When the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency group call the MCPTT client shall check the following:
1) if the <allow-emergency-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT us... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.9 SIP request for originating MCPTT imminent peril group calls
| This clause is referenced from other procedures.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril group call, and this is an authorised request for an MCPTT imminent peril group call as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) if the MCPTT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.10 Determining authorisation for cancelling an imminent peril group call
| When the MCPTT client receives a request from the MCPTT user to cancel an MCPTT imminent peril group call the MCPTT client shall:
1) if the <allow-cancel-imminent-peril> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile docume... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.11 SIP re-INVITE request for cancelling MCPTT in-progress imminent peril group state
| This clause is referenced from other procedures.
If the MCPTT imminent peril group call state is set to "MIGC 3: imminent-peril-call-granted" or the MCPTT imminent peril group state of the MCPTT group is set to "MIG 2: in-progress", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.12 Resource-Priority header field for MCPTT imminent peril group calls
| This clause is referenced from other procedures.
When the MCPTT imminent peril group call state is set "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted" and the MCPTT user is authorised to initiate an MCPTT imminent peril group call on the targeted MCPTT group as determined by the proced... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.13 Receiving a SIP INFO request in the dialog of a SIP request for a priority group call
| This clause is referenced from other procedures.
Upon receiving a SIP INFO request within the dialog of the SIP request for a priority group call:
- with the Info-Package header field containing the g.3gpp.mcptt-info package name;
- with the application/vnd.3gpp.mcptt-info+xml MIME body associated with the info pack... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.14 SIP re-INVITE request for cancelling the in-progress emergency group state of a group by a third-party
| This clause is referenced from other procedures.
Upon receiving an authorised request to cancel an in-progress emergency group state of a group as determined by the procedures of clause 6.2.8.1.7 from an MCPTT user, the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarif... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.15 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 MCPTT client:
1) shall retrieve the value of ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.16 Handling receipt of a SIP re-INVITE request for priority group call origination status within a pre-established session
| This clause is referenced from other procedures.
Upon receipt of a SIP re-INVITE request within the pre-established session targeted by the sent SIP REFER request, and if the sent SIP REFER request was a request for an MCPTT emergency group call or an MCPTT imminent peril group call, the MCPTT client:
1) if the MCPTT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.17 Priority group call conditions upon receiving call release
| This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT emergency group call or an MCPTT imminent peril group call in an MCPTT group session is in-progress or is in the process of being established:
1) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-req... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.18 Emergency private call conditions upon receiving call release
| This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT session when an MCPTT emergency private call is in-progress or is in the process of being established:
1) if the MCPTT emergency private call state is set to "MEPC 2: emergency-call-requested":
a) shall set the MCPTT emerg... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.19 Determining authorisation for initiating or cancelling an MCPTT adhoc group emergency alert
| If the MCPTT client receives a request from the MCPTT user to send an MCPTT adhoc group emergency alert and:
1) if the <allow-activate-adhoc-group-emergency-alert> 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 initiati... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.20 Determining authorisation for initiating or cancelling the in-progress emergency state of an MCPTT adhoc group
| When the MCPTT client receives a request from the MCPTT user to cancel the in-progress emergency state of a group the MCPTT client, determines, based on local policy (e.g., if the requester is dispatcher or initiator of the MCPTT emergency group call etc.), whether to send the emergency group state cancel request or no... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.21 SIP INVITE request or SIP REFER request for originating MCPTT emergency adhoc group calls
| This clause is referenced from other procedures.
If the MCPTT user is authorised to initiate an MCPTT emergency adhoc group call on the targeted MCPTT adhoc group as determined by the procedures of clause 6.2.8.1.24, the MCPTT client:
1) if the MCPTT emergency state is clear, shall set the MCPTT emergency state;
2) ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.22 Receiving a SIP 2xx response to a SIP request for a priority adhoc group call
| In the procedures in this clause, a priority adhoc group call refers to an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call.
On receiving a SIP 2xx response to a SIP request for a priority adhoc group call, the MCPTT client:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.23 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for a priority adhoc group call
| In the procedures in this clause, a priority adhoc group call refers to an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call.
Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for a priority adhoc group call the MCPTT client:
1) if the MCPTT emergenc... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.24 Determining authorisation for originating a priority adhoc group call
| When the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency adhoc group call the MCPTT client shall check the following:
1) if the <allow-emergency-adhoc-group-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.25 SIP request for originating MCPTT imminent peril adhoc group calls
| This clause is referenced from other procedures.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril adhoc group call, and this is an authorised request for an MCPTT imminent peril adhoc group call as determined by the procedures of clause 6.2.8.1.24, the MCPTT client:
1)... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.26 Handling receipt of a SIP re-INVITE request for priority adhoc group call origination status within a pre-established session
| This clause is referenced from other procedures.
Upon receipt of a SIP re-INVITE request within the pre-established session targeted by the sent SIP REFER request, and if the sent SIP REFER request was a request for an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call, the MCPTT client:
1) ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.27 Priority adhoc group call conditions upon receiving call release
| This clause is referenced from other procedures.
Upon receiving a request to release the MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call in an MCPTT group session is in-progress or is in the process of being established:
1) if the MCPTT emergency adhoc group call state is set to "MEAGC 2:... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.1.28 Determining authorisation for cancelling the in-progress imminent peril state of an MCPTT group
| When the MCPTT client receives a request from the MCPTT user to cancel the in-progress imminent peril state of a group, the MCPTT client, determines, based on local policy (e.g if the requester is dispatcher or initiator of the MCPTT imminent peril group call etc), whether to send the in-progress imminent peril state o... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.2 Request for an originating broadcast group call
| NOTE: This clause is referenced from other procedures.
When the MCPTT user initiates a broadcast group call, the MCPTT client:
1) in the case of the prearranged group call is initiated on-demand, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body the <broadcast-ind> element set to "true" as defined in... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3 MCPTT emergency private call conditions
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3.1 Authorisations
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3.1.1 Determining authorisation for initiating an MCPTT emergency private call
| If the MCPTT client receives a request from the MCPTT user to originate an MCPTT emergency private call and:
1) if the <allow-emergency-private-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3.1.2 Determining authorisation for cancelling an MCPTT emergency private call
| If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency private call and if the <allow-cancel-private-emergency-call> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling user (see the MCPTT user profile document in 3GPP TS 24.484 ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3.1.3 Determining authorisation for initiating or cancelling an MCPTT emergency alert to a MCPTT user
| If the MCPTT client receives a request from the MCPTT user to send an MCPTT emergency alert to an MCPTT user and:
1) if the <allow-activate-emergency-alert> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user as specified in 3GPP TS 24.484 [50] is se... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 6.2.8.3.2 SIP request for originating MCPTT emergency private calls
| This clause is referenced from other procedures.
When the MCPTT emergency private call state is set to "MEPC 1: emergency-pc-capable" and this is an authorised request for an MCPTT emergency private call as determined by the procedures of clause 6.2.8.3.1.1, the MCPTT client:
1) shall set the MCPTT emergency state if... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.