hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
4.4 Warning Header Field
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 (miscellaneous warning) and includes the host name set to the host name of the MCPTT server.
EXAMPLE: Warning: 399 "100 User not authorised to make group calls"
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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
mcptt-warn-text = *( qdtext | quoted-pair )
Table 4.4.2-2 defines the warning texts that are defined for the Warning header field when a Warning header field is included in a response to a SIP INVITE request as specified in clause 4.4.1.
Table 4.4.2-2: Warning texts defined for the Warning header field
Code
Explanatory text
Description
100
function not allowed due to <detailed reason>
The function is not allowed to this user.
The <detailed reason> will be either "group definition", "access policy", "local policy", "user authorisation" or "pre-established session not supported", or can be a free text string.
101
service authorisation failed
The service authorisation of the MCPTT ID against the IMPU failed at the MCPTT server.
102
too many simultaneous affiliations
The MCPTT user already has N2 maximum number of simultaneous affiliations (see <MaxAffiliationsN2> element of user profile configuration document).
103
maximum simultaneous MCPTT group calls reached
The number of maximum simultaneous MCPTT group calls supported for the MCPTT user has been exceeded.
104
isfocus not assigned
A controlling MCPTT function has not been assigned to the MCPTT session.
105
subscription not allowed in a broadcast group call
Subscription to the conference event package rejected during a group call initiated as a broadcast group call.
106
user not authorised to join chat group
The MCPTT user is not authorised to join this chat group.
107
user not authorised to make private calls
The MCPTT user is not authorised to make private calls.
108
user not authorised to make chat group calls
The MCPTT user is not authorised to make chat group calls.
109
user not authorised to make prearranged group calls
The MCPTT user is not authorised to make group calls to a prearranged group.
110
user declined the call invitation
The MCPTT user declined to accept the call.
111
group call proceeded without all required group members
The required members of the group did not respond within the acknowledged call time, but the call still went ahead.
112
group call abandoned due to required group members not part of the group session
The group call was abandoned, as the required members of the group did not respond within the acknowledged call time.
113
group document does not exist
The group document requested from the group management server does not exist.
114
unable to retrieve group document
The group document exists on the group management server but the MCPTT server was unable to retrieve it.
115
group is disabled
The group has the <disabled> element set to "true" in the group management server.
116
user is not part of the MCPTT group
The group exists on the group management server but the requesting user is not part of this group.
117
the group identity indicated in the request is a prearranged group
The group id that is indicated in the request is for a prearranged group, but did not match the request from the MCPTT user.
118
the group identity indicated in the request is a chat group
The group id that is indicated in the request is for a chat group, but did not match the request from the MCPTT user.
119
user is not authorised to initiate the group call
The MCPTT user identified by the MCPTT ID is not authorised to initiate the group call.
120
user is not affiliated to this group
The MCPTT user is not affiliated to the group.
121
user is not authorised to join the group call
The MCPTT user identified by the MCPTT ID is not authorised to join the group call.
122
too many participants
The group call has reached its maximum number of participants.
123
MCPTT session already exists
Inform the MCPTT user that the group call is currently ongoing.
124
maximum number of private calls reached
The maximum number of private calls allowed at the MCPTT server for the MCPTT user has been reached.
125
user not authorised to make private call with automatic commencement
The MCPTT user is not authorised to make a private call with automatic commencement.
126
user not authorised to make private call with manual commencement
The MCPTT user is not authorised to make a private call with manual commencement.
127
user not authorised to be called in private call
The called MCPTT user is not allowed to be part of a private call.
128
isfocus already assigned
The MCPTT server owning an MCPTT group received a SIP INVITE request destined to the MCPTT group from another MCPTT server already assigned as the controlling MCPTT function and the MCPTT server owning the MCPTT group does not support mutual aid or supports trusted mutual aid but does not authorise trusted mutual aid.
136
authentication of the MIKEY-SAKKE I_MESSAGE failed
The MCPTT client's application of the procedures of 3GPP TS 33.180 [78] to authenticate the received I_MESSAGE fails.
137
the indicated group call does not exist
The participating MCPTT function cannot find an ongoing group session associated with the received MCPTT session identity.
138
subscription of conference events not allowed
The controlling MCPTT function could not allow the MCPTT user to subscribe to the conference event package.
139
integrity protection check failed
The integrity protection of an XML MIME body failed.
140
unable to decrypt XML content
The XML content cannot be decrypted.
141
user unknown to the participating function
The participating function is unable to associate the public user identity with an MCPTT ID.
142
unable to determine the controlling function
The participating function is unable to determine the controlling function for the group call or private call.
143
not authorised to force auto answer
The calling user is not authorised to force auto answer on the called user.
144
user not authorised to call this particular user
The calling user is not authorised to call this particular called user.
145
unable to determine called party
The participating function was unable to determine the called party from the information received in the SIP request.
146
T-PF unable to determine the service settings for the called user
The service settings have not been uploaded by the terminating client to the terminating participating server.
147
user is authorized to initiate a temporary group call
The non-controlling MCPTT function has authorized a request from the controlling MCPTT function to authorize a user to initiate a temporary group session.
148
group is regrouped
The group hosted by a non-controlling function is part of a temporary group session as the result of the group regroup function.
149
SIP INFO request pending
The MCPTT client needs to wait for a SIP INFO request with specific content, before taking further action.
150
invalid combinations of data received in MIME body
The MCPTT client included invalid combinations of data in the SIP request.
151
user not authorised to make a private call call-back request
The MCPTT user is not authorised to make a private call call-back request.
152
user not authorised to make a private call call-back cancel request
The MCPTT user is not authorised to make a private call call-back cancel request.
153
user not authorised to call any of the users requested in the first-to-answer call
All users that were invited in the first-to-answer call cannot be involved in a private call with the inviting user.
154
user not authorised to make ambient listening call
The MCPTT user is not authorised to make an ambient listening call.
155
user not authorised to change user's selected group
The MCPTT user is not authorised to change the selected group of the targeted user.
156
user not authorised to originate a first-to-answer call
The MCPTT user is not authorised to make a first-to-answer call.
157
user not authorised to request a remotely initiated group call
The MCPTT user is not authorised to request a remotely initiated group call.
158
user not authorised to request a remotely initiated private call
The MCPTT user is not authorised to request a remotely initiated private call.
159
user not authorised to be called by this originating user
The called user is not authorised to receive a call by this originating user.
160
user not authorised to request creation of a regroup
The user is not authorised to request creation of a regroup.
161
user not authorised to request removal of a regroup
The user is not authorised to request removal of a regroup.
162
group call abandoned due to required group members not affiliated
The group call was abandoned as the required number of affiliated group members is not met or some required members are not affiliated.
163
the group identity indicated in the request does not exist
The server determines that the group identity indicates a user or group regroup based on a preconfigured group that does not exist.
164
maximum number of service authorizations reached
The number of maximum simultaneous service authorizations for the MCPTT user has been reached.
165
group ID for regroup already in use
The group ID proposed by the client for the user/group regroup based on a preconfigured group is already in use.
166
constituent group is in an emergency call state
The proposed constituent group cannot be added to the temporary group because there is a call on the constituent group that is in an emergency state.
167
call is not allowed on the preconfigured group
Calls are not allowed on this group that is administratively designated for preconfigured group use only.
168
alert is not allowed on the preconfigured group
Alerts are not allowed on this group that is administratively designated for preconfigured group use only.
169
user is not authorised to remove regroup in an emergency state
The MCPTT user is not authorised to remove a regroup that is in an in-progress emergency state.
170
user not authorised to make a private call transfer request
The MCPTT user is not authorised to make a private call transfer request.
171
functional alias not allowed to call this particular functional alias
The calling user is not authorised to call this particular functional alias by using this activated functional alias.
172
functional alias not allowed to be called from this functional alias
The called functional alias is not authorised to receive a call from the originating user using this particular Functional Alias.
173
user not authorised to make a private call forwarding request
The MCPTT user is not authorized to use MCPTT private call forwarding.
174
maximum number of allowed forwardings exceeded
The maximum number of allowed call forwardings has been exceeded.
175
call is forwarded
The MCPTT private call that is requested to be established is released, and a new MCPTT private call is originated to the target of the call forwarding.
176
user not authorized to request for binding/unbinding of a functional alias with the MCPTT group(s) for the MCPTT user
The function is not allowed to this user.
177
unable to determine target functional alias or group for creating/removing a binding information for the MCPTT user
The MCPTT server is unable to determine the targeted functional alias or group for creating/removing a binding information for the MCPTT user.
178
MCPTT group binding already exists with other functional alias for the MCPTT user
The requested functional alias binding with MCPTT group already exist with other functional alias for the MCPTT user.
179
service not authorized with the interconnected system
The MCPTT service is not authorized between the local and the interconnected system and is rejected in the local system.
180
service not authorized by the interconnected system
The MCPTT service is not authorized between the local and the interconnected system and is rejected by the interconnected system.
181
called user requires to use floor control
The called user has rejected the call request because floor control is required to be used.
182
called user requires to not use floor control
The called user has rejected the call request because floor control is required not to be used.
183
MCPTT codec required
The call requires an MCPTT defined codec to be used.
184
user not authorised to make adhoc group calls
The MCPTT user is not authorised to make adhoc group calls.
185
user not authorised to initiate the adhoc group call
The MCPTT user identified by the MCPTT ID is not authorised to initiate the adhoc group call.
186
the MCPTT system do not support adhoc group call
The MCPTT system doesn’t support the adhoc group call or support of adhoc group call is turned off
187
can't determine the adhoc group participants
The MCPTT server can not determine the adhoc group participants based on the input parameters.
188
user is not allowed to participate in adhoc group call
The MCPTT user is not allowed to participate in adhoc group call e.g. user no longer meets the criteria.
189
maximum number of allowed adhoc group participants exceeded
The maximum number of allowed adhoc group participants exceeded the configured limit.
190
user is not authorised to initiate modify adhoc group call participants
The MCPTT user is not allowed to modify the participants list of the adhoc group call.
191
call forwarding due to migration
The private call or adhoc call is subject for call forwarding because the target user has migrated to a partner MCPTT system.
192
invalid location request target client list
The MCPTT server cannot determine the target client of the location information or location configuration change request.
193
user not authorized to request location information
The MCPTT user is not allowed to request location information of other MCPTT clients.
194
user not authorized to request location configuration changes
The MCPTT user is not allowed to request changes in the location reporting configuration of other MCPTT clients.
195
can't determine the adhoc group
The MCPTT server cannot determine that target adhoc group.
196
user participates under another constituent group
The MCPTT user participates to the group regroup or temporary group under another of its constituent groups.
197
targeted emergency group call is not ongoing
The emergency remote floor request trigger does not target an ongoing emergency group call
198
targeted emergency private call is not ongoing
The emergency remote floor request trigger does not target an ongoing emergency private call
199
remote user is not in emergency state
The emergency remote floor request trigger targets a user who is not in emergency state
200
user not authorised to trigger an emergency remote floor request
The MCPTT user is not authorised to trigger an emergency remote floor request
301-350
Value allocated for use in interworking (see NOTE).
NOTE: Usage of these values are described in 3GPP TS 29.379 [88].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 function and the participating MCPTT function.
The MCPTT session identity shall be a GRUU as defined in IETF RFC 5627 [72] assigned by the MCPTT server as per 3GPP TS 24.229 [4].
The MCPTT session identity identifies the MCPTT session in such a way that e.g.:
- the MCPTT user is able to subscribe to the participant information of the ongoing MCPTT session;
- the MCPTT user is able to rejoin an ongoing MCPTT session; and
- the IM CN subsystem is able to route an initial SIP request to the controlling MCPTT function.
The controlling MCPTT function allocates a unique MCPTT session identity hosted at the controlling MCPTT function for the MCPTT session at the time of session establishment.
The non-controlling MCPTT function allocates a unique MCPTT session identity hosted at the non-controlling MCPTT function for the MCPTT session at the time of session establishment.
When protection of sensitive application data is required by the MCPTT operator, the MCPTT session identity cannot contain identity information that is classed as sensitive such as the MCPTT ID or the MCPTT Group ID, as specified in clause 4.8.
The controlling MCPTT function and non-controlling MCPTT function send the MCPTT session identity towards the MCPTT client during MCPTT session establishment by including it in the Contact header field of the final SIP response to a session initiation request.
The participating MCPTT function allocates a unique MCPTT session identity hosted at the participating MCPTT function for the MCPTT session when it receives a MCPTT session identity in the Contact header field of a SIP request or a SIP response from the controlling MCPTT function or non-controlling MCPTT function and includes it in the Contact header field of the SIP request or SIP response sent towards the MCPTT client. The participating MCPTT function maintains a mapping of the MCPTT session identities it sends to the MCPTT client to the corresponding MCPTT session identities received from the controlling MCPTT function.
The MCPTT client can cache the MCPTT session identity until a time when it is no longer needed.
The MCPTT session identity is also used in floor control requests and responses as specified in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
4.6 MCPTT priority calls and alerts
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 group emergency cancel.
NOTE 1: In-progress group emergency cancel means the cancellation of the in-progress emergency state of the group, which is managed by the controlling MCPTT function.
The above functionalities are supported using both MCPTT prearranged group calls and MCPTT chat group calls.
Key aspects of MCPTT emergency group calls include:
- adjusted EPS bearer priority for all participants whether or not they themselves are in an emergency condition (i.e. have their MCPTT emergency state set). For unicast bearers this is achieved by using the Resource-Priority header field as specified in IETF RFC 4412 [29] with namespaces defined for use by MCPTT specified in IETF RFC 8101 [48], and for MBMS bearers this is achieved by having the participating MCPTT function adjust the ARP (priority, PVI, PCI) and executing the Modify MBMS Bearer Procedure per 3GPP TS 29.468 [42];
- pre-emptive floor control priority over MCPTT users in MCPTT emergency group calls who themselves do not have their MCPTT emergency state set;
- restoration of normal EPS bearer priority to the call participants when the in-progress emergency group state is cancelled;
- restoration of normal floor control priority participants when the in-progress emergency group state is cancelled;
- requires the MCPTT user to be authorised to either originate or cancel an MCPTT emergency group call;
- requests to originate MCPTT emergency group calls may also include an indication of an MCPTT emergency alert; and
- requests to cancel MCPTT emergency group calls may also include an indication of cancelling a previously issued MCPTT emergency alert.
There are a number of states that are key in managing these aspects of MCPTT emergency group calls, which include:
- MCPTT emergency state: as defined in 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3], indicates that the MCPTT user is in a life-threatening situation. Managed by the MCPTT user of the device or an authorised MCPTT user. While the MCPTT emergency state is set on the client, all calls originated by the client will be MCPTT emergency calls, assuming the MCPTT user is authorised for MCPTT emergency calls on them.
- in-progress emergency group state: as defined in 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3], indicates whether or not there is an MCPTT emergency group call ongoing on the specified group. This state is managed by the controlling MCPTT function. All group calls originated on this MCPTT group when in an in-progress emergency state are MCPTT emergency group calls until this state is cancelled, whether or not the originator is themselves in an MCPTT emergency state.
- MCPTT emergency group (MEG) state: this is an internal state managed by the MCPTT client which tracks the in-progress emergency state of the group as defined in 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3] and managed by the controlling MCPTT function. Ideally, the MCPTT client would not need to track the in-progress emergency group state, but doing so enables the MCPTT client to request MCPTT emergency-level priority earlier than otherwise possible. For example, if the MCPTT user wishes to join an MCPTT emergency group call and is not in MCPTT emergency state itself, the MCPTT client should have emergency level priority. If it has knowledge of the in-progress emergency state of the group, it can request priority by including a Resource-Priority header field set to the MCPTT namespace specified in IETF RFC 8101 [48], and appropriate priority level in the SIP INVITE request (or SIP re-INVITE request).
- MCPTT emergency group call (MEGC) state: this is an internal state managed by the MCPTT client which in conjunction with the MCPTT emergency alert state aids in managing the MCPTT emergency state and related actions.
- MCPTT emergency alert (MEA) state: this is also an internal state of the MCPTT client which in conjunction with the MCPTT emergency group call state aids in managing the MCPTT emergency state and related actions.
NOTE 2: The above states and their transitions are described in Annex G.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 of an MCPTT private call to an MCPTT emergency private; and
- cancellation of the MCPTT emergency private call priority.
Key aspects of MCPTT emergency private calls include:
- adjusted EPS bearer priority for both participants whether or not they are both in an emergency condition (i.e. both have their MCPTT emergency state set). This is achieved by using the Resource-Priority header field as specified in IETF RFC 4412 [29] with namespaces defined for use by MCPTT specified in IETF RFC 8101 [48];
- the initiator of the MCPTT emergency private call can override the other MCPTT user in the MCPTT emergency private call unless that user also has their MCPTT emergency state set;
- restoration of normal EPS bearer priority to the call according to system policy (e.g., configured time limit for the emergency priority of an MCPTT emergency private call or cancellation of the emergency condition of the private call);
- restoration of normal floor control priority participants when the emergency elevated priority is cancelled;
- requires the MCPTT user to be authorised to either originate or cancel an MCPTT emergency private call;
- requires the targeted MCPTT user to be authorised to receive an MCPTT emergency private call;
- requests to originate MCPTT emergency private calls may also include an indication of an MCPTT emergency alert; and
- the originator of the MCPTT emergency private call can request that the call use either manaual or automatic commencement mode.
There are a number of states that are key in managing these aspects of MCPTT emergency private calls, which include:
- MCPTT emergency state (MES): as defined in 3GPP TS 22.179 [2] and 3GPP TS 23.379 [3], indicates that the MCPTT user is in a life-threatening situation. Managed by the MCPTT user of the device or an authorised MCPTT user. While the MCPTT emergency state is set on the client, all MCPTT group and private calls originated by the client will be MCPTT emergency calls, assuming the MCPTT user is authorised for MCPTT emergency calls on them.
- MCPTT private emergency alert (MPEA) state: this is an internal state of the MCPTT client which in conjunction with the MCPTT emergency private call state aids in managing the MCPTT emergency state and related actions.
- MCPTT emergency private call (MEPC) state: this is an internal state managed by the MCPTT client which in conjunction with the MCPTT emergency alert state aids in managing the MCPTT emergency state and related actions.
- In-progress emergency private call (IPEPC) state: indicates whether or not there is an MCPTT emergency private call in-progress for the two participants. This state is managed by the controlling MCPTT function. All private calls originated between these two participants when in an in-progress emergency private call state are MCPTT emergency private calls until this state is cancelled, whether or not the originator is in an MCPTT emergency state.
- MCPTT emergency private priority (MEPP) state: this is an internal state managed by the MCPTT client which tracks the in-progress emergency private call state of the private call managed by the controlling MCPTT function. Ideally, the MCPTT client would not need to track the in-progress emergency private priority state, but doing so enables the MCPTT client to request MCPTT emergency-level priority earlier than otherwise possible. For example, if the MCPTT user wishes to join an MCPTT emergency private call and is not in the MCPTT emergency state, the MCPTT client should have emergency level priority. If it has knowledge of the in-progress emergency private priority state of the private call (i.e., the two participants), it can request priority by including a Resource-Priority header field set to the MCPTT namespace specified in IETF RFC 8101 [48], and appropriate priority level in the SIP INVITE request (or SIP re-INVITE request).
NOTE: The above states and their transitions are described in Annex G.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 supported procedurally by two general mechanisms. One mechanism is embedded within the MCPTT emergency call (both emergency private call and emergency group call using both prearranged and chat session models) signalling procedures documented in clause 10 and clause 11 of this specification. The other mechanism utilizes SIP MESSAGE requests and is documented in clause 12.
MCPTT emergency alerts can be initiated or cancelled as options in the following signalling procedures documented in clause 10 and clause 11:
- MCPTT emergency group call initiation;
- MCPTT group call upgraded to MCPTT emergency call;
- MCPTT emergency group call cancellation (i.e., in-progress emergency state of the group set to false);
- MCPTT emergency private call initiation; and
- MCPTT private call upgrade to MCPTT emergency private call.
MCPTT emergency alerts can also be initiated or cancelled as described in the procedures of clause 12 which include:
- MCPTT emergency alert initiation; and
- MCPTT emergency alert cancellation (with optional cancelling of the in-progress emergency state of a group).
When MCPTT emergency alerts are initiated as an option in initiating or upgrading to an MCPTT emergency group call or are initiated using SIP MESSAGE requests, they are targeted to an MCPTT group, and, if not already affiliated, will result in the initiator being implicitly affiliated to the MCPTT group. When initiated as an option in initiating or upgrading to an MCPTT emergency private call, an MCPTT emergency alert is targeted to an individual MCPTT user, not to an MCPTT group.
Key aspects of MCPTT emergency alerts include:
- MCPTT emergency (MES) state: the MCPTT client's MCPTT emergency state as described in clause G.1 is set upon initiation of an MCPTT emergency alert. While the MCPTT emergency state is set, assuming the MCPTT user has the needed authorisations, if the user initiates a private call and is authorised to do so, the MCPTT private call will be an MCPTT emergency private call. Similarly, assuming the needed authorisations, any subsequent MCPTT group call initiated by an MCPTT user with the MCPTT emergency state set will be an MCPTT emergency group call.
- MCPTT emergency alert (MEA) state: the MCPTT client maintains the internal MCPTT emergency alert state (MEA) which aids in the management of the MCPTT emergency state as described in clause G.5.
- MCPTT private emergency alert (MPEA) state: the MCPTT client maintains the MCPTT private emergency alert state of an MCPTT emergency alert targeted to an MCPTT user which aids in the management of the MCPTT emergency state.
- In-progress emergency group (IPEG) state : MCPTT emergency alert initiation or cancellation in and of itself does not impact the in-progress emergency state of the targeted group, which is maintained by the controlling MCPTT function, nor does it impact the priority of the EPS bearers. However, in setting the MCPTT emergency state, assuming an MCPTT user is authorised to make MCPTT emergency calls on the targeted group, any subsequent MCPTT group call the MCPTT user initiates on the group will cause the in-progress emergency state of the group to be set as described in clause G.2 and will result in upgraded priority of the EPS bearers used in the MCPTT emergency call.
- Authorisations for emergency alerts: MCPTT users need to be authorised to initiate MCPTT emergency alerts and additionally need to be authorised to cancel MCPTT emergency alerts. The parameters related to these authorisations are specified in 3GPP TS 24.483 [45] and 3GPP TS 24.484 [50].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 imminent peril group call;
- upgrade from an MCPTT imminent peril group call to an MCPTT emergency group call; and
- cancellation of the in-progress imminent peril state of the group.
Key aspects of MCPTT imminent peril include:
- adjusted EPS bearer priority for all participants when the in-progress imminent peril state of the group is set whether or not they themselves initiated an imminent peril group call. For unicast bearers this is achieved by using the Resource-Priority header field as specified in IETF RFC 4412 [29] with namespaces defined for use by MCPTT specified in IETF RFC 8101 [48], and for MBMS bearers this is achieved by having the participating MCPTT function adjust the ARP (priority, PVI, PCI) and executing the Modify MBMS Bearer Procedure per 3GPP TS 29.468 [42];
- restoration of normal EPS bearer priority to the call when the in-progress imminent peril group state is cancelled; and
- requires the MCPTT user to be authorised to either originate or cancel an MCPTT imminent peril group call.
Relationship to other MCPTT priority group call types:
- A normal MCPTT group call can be upgraded to an MCPTT imminent peril group call;
- An MCPTT imminent peril group call can be upgraded to an MCPTT emergency group call;
- When either an MCPTT imminent peril group call or an MCPTT emergency group call (i.e., their respective "in-progress" states) the group call returns to the priority designated for normal group calls, i.e., their is no direct transition from an MCPTT emergency group call to an MCPTT imminent peril group call;
- MCPTT imminent peril functionality is only applicable to MCPTT group calls, not MCPTT private calls; and
- MCPTT imminent peril group calls have no associated alert capabilities such as the MCPTT emergency alert capability which is associated with MCPTT emergency group calls.
There are a number of states that are key in managing these aspects of MCPTT imminent peril group calls, which include:
- MCPTT imminent peril group (MIG) state: this is an internal state of the MCPTT client which in conjunction with the MCPTT imminent peril group call state aids the client in managing the use of the Resource-Priority header field and related actions.
- MCPTT imminent peril group call (MIGC) state: this is an internal state managed by the MCPTT client which in conjunction with the MCPTT imminent peril group state aids the client in managing the use of the Resource-Priority header field and related actions.
- In-progress imminent peril group (IPIG) state: this a state of the MCPTT group which is managed by the controlling MCPTT function. While an MCPTT group is in an in-progress imminent peril group state, all participants in group calls using this group will receive elevated priority.
The above states and their transitions are described in Annex G.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
4.7 Communication security
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 no unauthorised access to communications is taking place within the MCPTT network. An MCPTT key management server (KMS) manages the security domain. For any end-point to use or access end-to-end secure communications, it needs to be provisioned with keying material associated to its identity by the KMS as specified in 3GPP TS 33.180 [78].
For group calls, the security context is set up at the time of creation of the group or temporary group. The group management server creates group call keying material associated with the group and distributes it to all members of the group or temporary group, in advance of the initiation of a group call as specified in 3GPP TS 24.481 [31] and 3GPP TS 33.180 [78]. The establishment of a security context for group calls has no impact on this specification.
For private calls, the security context is initiated at call setup. An end-to-end security context is established that is unique to the pair of users involved in the call. The procedure involves transferral of an encapsulated private call key (PCK) and private call key id (PCK-ID) from the initiator to the terminator. The PCK is encrypted using the terminator's MCPTT ID and domain-specific material provided from the terminating user's KMS. The domain-specific key material of the terminator's KMS is identified by a KMS URI stored in the terminating user profile. The domain-specific key material for all KMSs is downloaded in advance from the initiator's home KMS as described in 3GPP TS 33.180 [78]. The PCK and PCK-ID are distributed within a MIKEY payload within the SDP offer of the private call request. This payload is called a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [75], which ensures the confidentiality, integrity and authenticity of the payload. The encoding of the MIKEY payload in the SDP offer is described in IETF RFC 4567 [47] using an "a=key-mgmt" attribute. The payload is signed using a key associated to the identity of the initiating user. At the terminating side, the signature is validated. If valid, the UE extracts and decrypts the encapsulated PCK. The MCPTT UE also extracts the PCK-ID. This process is described in 3GPP TS 33.180 [78]. With the PCK successfully shared between the two MCPTT UEs, the UEs are able to use SRTP/SRTCP to create an end-to-end secure session.
For first-to-answer calls, the security context is initiated at call setup. An end-to-end security context is established that is unique to the pair of users involved in the call. The procedure involves transferral of an encapsulated private call key (PCK) and private call key id (PCK-ID) from the terminator to the initiator. The PCK is encrypted using the originator's MCPTT ID and domain-specific material provided from the originating user's KMS. The domain-specific key material of the originator's KMS is identified by a KMS URI stored in the originator's user profile. The domain-specific key material for all KMSs is downloaded in advance from the terminator's home KMS as described in 3GPP TS 33.180 [78]. The PCK and PCK-ID are distributed within a MIKEY payload within the SDP answer of the first-to-answer call response. This payload is called a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [75], which ensures the confidentiality, integrity and authenticity of the payload. The encoding of the MIKEY payload included in the SDP answer using an "a=key-mgmt" attribute is described in IETF RFC 4567 [47]. The payload is signed using a key associated to the identity of the terminating user. At the originating side, the signature is validated. If valid, the UE extracts and decrypts the encapsulated PCK. The MCPTT UE also extracts the PCK-ID. This process is described in 3GPP TS 33.180 [78]. With the PCK successfully shared between the two MCPTT UEs, the UEs are able to use SRTP/SRTCP to create an end-to-end secure session.
End-to-end security is independent of the transmission path and hence is applicable to both on and off-network communications. With a security context established, the group call key and private call key can be used to encrypt media between the end-points as described in 3GPP TS 24.380 [5] clause 13.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 4.8)
- User plane control over unicast: Floor control messages
- User plane control over multicast: Floor control messages and MBMS subchannel control messages
NOTE 1: According to 3GPP TS 24.380 [5], currently the multicast floor control messages are Floor Idle and Floor Taken and the multicast MBMS subchannel control messages are Map Group To Bearer and Unmap Group To Bearer.
For unicast signalling between the participating MCPTT function and the MCPTT client, the signalling can be protected using the Client-Server Key (CSK), identified by a Client-Server Key Identifier (CSK-ID). The CSK and CSK-ID are initially uploaded from the MCPTT client to the MCPTT server within a MIKEY MIME payload within a SIP REGISTER message for service authorisation or a SIP PUBLISH message for service authorisation, as specified in clause 9.2.1.3 of 3GPP TS 33.180 [78]. The CSK is confidentiality and integrity protected to the public service identity identifying the participating MCPTT function serving the MCPTT user and signed by the MCPTT ID of the MCPTT user.
The CSK and CSK-ID can also be updated by the participating MCPTT function. The procedure involves the participating MCPTT function generating a new CSK and CSK-ID and distributing the new key to the MCPTT client using a CSK 'key download' SIP MESSAGE, as specified in clause 9.2.1.4 of 3GPP TS 33.180 [78]. The message contains a MIKEY MIME payload containing the CSK and CSK-ID. The CSK is confidentiality and integrity protected to the public service identity identifying the participating MCPTT function serving the MCPTT user and signed by the MCPTT ID of the MCPTT user. The client only uses a single CSK at any one time and discards the previously established CSK on receiving a new CSK.
In case of multicast, the protection of MBMS subchannel control messages on the general purpose MBMS subchannels can be done with MSCCKs (each identified by a corresponding MSCCK-ID), distributed during MBMS bearer announcement. Each general purpose MBMS subchannel is associated with an MSCCK and a corresponding MSCCK‑ID. There can be multiple general purpose MBMS subchannels deployed, each associated with its own MSCCK and corresponding MSCCK-ID. The (MSCCK-ID, MSCCK) pair is provided for each general purpose MBMS subchannel separately.
The protection of floor control messages sent over MBMS subchannels can be done with Multicast Signalling Keys (MuSiK), (each identified by a corresponding (MuSiK-ID)), distributed via MuSiK download messages. The MSCCK and MuSiKs can be distributed independently of each other and in any order and can also be used independently. Signalling supports initial keying, as well as repeated re-keying and un-keying for both MSCCK and MuSiKs.
NOTE 2: When an MCPTT client interworks with a participating MCPTT function compliant only to Release 13 of the present document, the floor control messages can be protected using the MKFC and MKFC-ID as specified in 3GPP TS 24.380 [5].
The MuSiK download message contains an embedded MIME payload which is the MIKEY payload containing the MuSiK and MuSiK-ID, as well as an embedded XML payload potentially containing an explicit list of MCPTT group ids to which the key applies. Both payloads are protected as described in 3GPP TS 33.180 [78], as they are transferred between the participating MCPTT function and the MCPTT client. Within the XML payload, the list of MCPTT group ids is protected as application sensitive data (see clause 4.8). Within the MIKEY payload, the MuSiK is encrypted using the MCPTT ID of the served MCPTT client. The payload is signed using a key associated to the identity of the participating MCPTT function. To distribute MuSiK, the participating MCPTT function uses the I_MESSAGE format from clause 5.2.4 of 3GPP TS 33.180 [78], which includes associated parameters. The participating function sets the Status associated parameter to values defined in clause E.6.9 of 3GPP TS 33.180 [78], namely "Not-revoked" when keying or rekeying and "Revoked" when unkeying, respectively. Upon receipt, the MCPTT client validates the signature and, if valid, the MCPTT client first examines the Status attribute and either marks the associated security functions as "not in use" or stores the MuSiK and the MuSiK-ID, and then replies with a success code; otherwise, the MCPTT client can reply with a failure code. if a success code is not received from the MCPTT client in response to the MuSiK download message, the participating MCPTT function starts using only unicast floor control signalling to the respective MCPTT client for the listed groups.
For MBMS subchannel control messages sent over the general purpose MBMS subchannel of an MBMS bearer, the MSCCK can be used. The security context is initiated when the MBMS bearer is announced to the MCPTT clients. The procedure involves the participating MCPTT function creating an MBMS subchannel control key (MSCCK) and a corresponding key identifier (MSCCK-ID) associated with the MBMS bearer when the MBMS bearer is activated, and then transferring the MSCCK and the MSCCK-ID associated with the MBMS bearer to served MCPTT clients using SIP signalling. The MSCCK is encrypted using the MCPTT ID of the served MCPTT client and domain-specific material provided from the KMS. The MSCCK and the MSCCK-ID associated with the MBMS bearer are distributed within a MIKEY payload within the SDP describing the general purpose MBMS subchannel of the MBMS bearer. This payload is called a MIKEY-SAKKE I_MESSAGE, as defined in IETF RFC 6509 [75], which ensures the confidentiality, integrity and authenticity of the payload. The encoding of the MIKEY payload in the SDP is described in IETF RFC 4567 [47] using an "a=key-mgmt" attribute. The payload is signed using a key associated to the identity of the participating MCPTT function. To distribute MSCCK, the participating MCPTT function uses the I_MESSAGE format from clause 5.2.4 of 3GPP TS 33.180 [78], which includes associated parameters. The participating function sets the Status associated parameter to values defined in clause E.6.9 of 3GPP TS 33.180 [78], namely "Not-revoked" when keying or rekeying and "Revoked" when unkeying, respectively. Upon receipt, the MCPTT client validates the signature and, if the signature is found valid and the I_MESSAGE contains a Status attribute, the MCPTT client first examines the Status attribute and either marks the associated security functions as "not in use" or extracts and stores the encapsulated MSCCK and the corresponding MSCCK-ID. The decrypted key is used as described in 3GPP TS 33.180 [78]. With the MSCCK successfully shared between the participating MCPTT function and the served UEs, the participating MCPTT function is able to securely send MBMS subchannel control messages to the MCPTT clients.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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:
- MCPTT ID;
- MCPTT group ID;
- user location information;
- emergency, alert and imminent-peril indicators;
- access token (containing the MCPTT ID);
- MCPTT client ID; and
- functional alias.
The above data is transported as XML content in SIP messages. in XML elements or XML attributes.
Data is transported in attributes in the following circumstances in the procedures in the present document:
- an MCPTT ID, an MCPTT Group ID, and an MCPTT client ID in an XML document published in SIP PUBLISH request for affiliation according to IETF RFC 3856 [51];
- an MCPTT ID or an MCPTT Group ID in XML document notified in a SIP NOTIFY request for affiliation according to IETF RFC 3856 [51];
- an MCPTT ID and functional alias in an XML document published in SIP PUBLISH request for functional alias management according to IETF RFC 3856 [51];
- an MCPTT ID and functional alias in an XML document notified in a SIP NOTIFY request for functional alias management according to IETF RFC 3856 [51];
- an MCPTT ID in application/resource-lists+xml document included in an SIP INVITE request setting up a private call according to IETF RFC 5366 [20];
- an MCPTT ID in application/resource-lists+xml document included in an SIP INVITE request setting up a group call to a temporary group involving a non-controlling function that works in "Trusted Mode" according to IETF RFC 5366 [20], whereby the participants are returned to the controlling function in a MIME body of a SIP 403 (Forbidden) with the P-Refused-URI-List header field according to IETF RFC 5318 [36];
- an MCPTT ID in XML document provided in SIP NOTIFY request of a conference event package according to IETF RFC 4575 [30]; and
- an MCPTT ID or MCPTT Group ID in a "uri" attribute of an <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml document according to IETF RFC 5366 [20], included in a SIP REFER request when using a pre-established session (the application/resource-lists+xml MIME body is pointed to by a Cid-URL as specified in IETF RFC 2392 [62] contained in the Refer-To header field of the SIP REFER request);
- an MCPTT ID in XML document provided in SIP INFO request according to IETF RFC 6086 [64], after receiving the SIP ACK for a SIP 200 (OK) with the Warning header field set with the Warning text "111 group call proceeded without all required group members".
3GPP TS 33.180 [78] describes a method to provide confidentiality protection of sensitive application data in elements by using XML encryption (i.e. xmlenc) and in attributes by using an attribute confidentiality protection scheme described in clause 6.6.2.3 of the present document. Integrity protection can also be provided by using XML signatures (i.e. xmlsig).
Protection of the data relies on a shared XML protection key (XPK) used to encrypt and sign data:
- between the MCPTT client and the MCPTT server, the XPK is a client-server key (CSK); and
- between MCPTT servers and between MCPTT domains, the XPK is a signalling protection key (SPK).
The CSK (XPK) and a key-id CSK-ID (XPK-ID) are generated from keying material provided by the key management server. Identity based public key encryption based on MIKEY-SAKKE is used to transport the CSK between SIP end-points. The encrypted CSK is transported from the MCPTT client to the MCPTT server when the MCPTT client performs service authorisation as described in clause 7 and is also used during service authorisation to protect the access token.
The SPK (XPK) and a key-id SPK-ID (XPK-ID) are directly provisioned in the MCPTT servers.
Configuration in the MCPTT client and MCPTT server is used to determine whether one or both of confidentiality protection and integrity protection are required.
The following four examples give a brief overview of the how confidentiality and integrity protection is applied to application data in this specification.
EXAMPLE 1: Pseudo code showing how confidentiality protection is represented in the procedures in the document for sensitive data sent by the originating client.
IF configuration is set for confidentiality protection of sensitive data
THEN
Encrypt data element using the CSK (XPK) by following TS 33.180;
Include in an <EncryptedData> element of the XML MIME body according to TS 33.180:
(1) the encryption method;
(2) the key-id (XPK-ID);
(3) the cipher data;
Encrypt URIs in attribute using the CSK (XPK) by following clause 6.6.2.3;
ELSE
include application data into XML MIME body in clear text;
ENDIF;
EXAMPLE 2: Pseudo code showing how integrity protection is represented in the procedures in the present document for data sent by the originating client.
IF configuration is set for integrity protection of application data
THEN
Use a method to hash the content as specified in TS 33.180;
Generate a signature for the hashed content using the CSK (XPK) as specified in TS 33.180;
Include within a <Signature> XML element of the XML MIME body according to TS 33.180:
(1) a cannonicalisation method to be applied to the signed information;
(2) the signature method used for generating the signature;
(3) a reference to the content to be signed;
(4) the hashing method used;
(5) the hashed content;
(6) the key-id (XPK-ID);
(7) the signature value;
ENDIF;
EXAMPLE 3: Pseudo code showing how confidentiality protection is represented in the procedures in the present document at the server side when receiving encrypted content.
IF configuration is set for confidentiality protection of sensitive data
THEN
Check that the XML content contains the <EncryptedData> element;
Check that the XML document contains a URI with the domain name for MCPTT confidentiality protection;
Return an error if the <EncryptedData> element or domain name for MCPTT confidentiality protection are not found;
Otherwise:
(1) obtain the CSK (XPK) using the CSK-ID (XPK-ID) in the received XML body;
(2) for encrypted data in elements, decrypt the data elements using the CSK as specified in TS 33.180 as required;
(3) for encrypted URIs in attributes, decrypt the URIs using the CSK as specified in clause 6.6.2.3;
ENDIF;
EXAMPLE 4: Pseudo code showing how integrity protection is represented in the procedures in the present document at the server side when receiving signed content.
IF configuration is set for integrity protection of application data
THEN
Check that the XML content contains the <Signature> element;
Return an error if the <Signature> element is not found;
Otherwise:
(1) obtain the CSK (XPK) using the CSK-ID (XPK-ID) in the received XML body;
(2) verify the signature of the content using the CSK;
Return an error if the validation of the signature fails;
IF validation of the signature passes
THEN
decrypt any data found in <EncryptedData> elements;
decrypt any encrypted URIs found in attributes;
ENDIF;
ENDIF;
The content can be re-encrypted and signed again using the SPK between MCPTT servers.
The following examples show the difference between normal and encrypted data content. In this example consider the MCPTT client initiating a prearranged group session.
EXAMPLE 5: application/vnd.3gpp.mcpttinfo+xml MIME body represented with data elements in the clear:
Content-Type: application/vnd.3gpp.mcptt-info+xml
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</session-type>
<mcptt-request-uri type="Normal">
<mcpttURI>sip:group123@mcpttoperator1.com></mcpttURI>
</mcptt-request-uri>
</mcptt-Params>
</mcptt-info>
EXAMPLE 6: application/vnd.3gpp.mcpttinfo+xml MIME body represented with the <mcptt-request-uri> encrypted:
Content-Type: application/vnd.3gpp.mcptt-info+xml
<?xml version="1.0"?>
<mcpttinfo>
<mcptt-Params>
<session-type>prearranged</session-type>
<mcptt-request-uri type="Encrypted">
<EncryptedData xmlns='http://www.w3.org/2001/04/xmlenc#'
Type='http://www.w3.org/2001/04/xmlenc#Content'>
<EncryptionMethod Algorithm="http://www.w3.org/2009/xmlenc11#aes128-gcm"/>
<ds:KeyInfo>
<ds:KeyName>base64XpkId</KeyName>
</ds:KeyInfo>
<CipherData>
<CipherValue>A23B45C5657689090</CipherValue>
</CipherData>
</EncryptedData>
</mcptt-request-uri>
</mcptt-Params>
</mcptt-info>
EXAMPLE 7: application/pidf+xml MIME body represented with clear URIs in attributes:
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence entity="sip:somebody@mcptt.org">
<tuple id="acD4rhU87bK">
<status>
<affiliation group="sip:thegroup@mcptt.org"/>
</status>
</tuple>
</presence>
EXAMPLE 8: application/pidf+xml MIME body represented with encrypted URIs in attributes:
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence entity="sip:c4Hrt45XG8IohRFT67vfdr3V;iv=45RtfVgHY23k8Ihy;xpk-id=b7UJv9;alg=128-aes-gcm@mc1-encryption.3gppnetwork.org">
<tuple id="acD4rhU87bK">
<status>
<affiliation group="sip:98yudFG45tx_89TYGedb4ujF ;iv=FGD567kjhfH7d4-D;key-id=eV9kl7;alg=128-aes-gcm@mc1-encryption.3gppnetwork.org"/>
</status>
</tuple>
</presence>
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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-established session for establishing MCPTT calls with other MCPTT users. The procedures for establishing, modifying and releasing a pre-established session are defined in clause 8.
The pre-established session can later be used in MCPTT calls. This avoids the need to negotiate media parameters (including evaluating ICE candidates) and reserving bearer resources during the MCPTT call establishment that results in delayed MCPTT call establishment.
The use of pre-established session on the origination side is compatible with the use of on demand session on the termination side. The use of pre-established session on the termination side is compatible with the use of on demand session on the origination side.
The MCPTT client procedures for:
- leaving an MCPTT call using a pre-established session that was initiated by the MCPTT client are defined in clause 6.2.4.2;
- releasing a MCPTT call using a pre-established session that was initiated by the MCPTT client are defined in clause 6.2.5.2;
- establishing a pre-arranged group call using a pre-established session are defined in clause 10.1.1.2.2;
- rejoining a pre-arranged group call using a pre-established session are defined in clause 10.1.1.2.4.2;
- joining a chat MCPTT group call using a pre-established session are defined in clause 10.1.2.2.2;
- establishing a private call using a pre-established session are defined in clause 11.1.1.2.2; and
- releasing a private call using a pre-established session are defined in clause 11.1.3.1.2.
The participating MCPTT function procedures for:
- establishing a MCPTT session using automatic commencement mode are defined in clause 6.3.2.2.5.3;
- establishing a MCPTT session using manual commencement mode are defined in clause 6.3.2.2.6.3;
- releasing a MCPTT call using a pre-established session are defined in clause 6.3.2.2.8.2;
- establishing a pre-arranged group call using a pre-established session are defined in clause 10.1.1.3.1.2;
- releasing a pre-arranged group call using a pre-established session are defined in clause 10.1.1.3.3.2;
- rejoining a pre-arranged group call using a pre-established session are defined in clause 10.1.1.3.5.2;
- establishing a MCPTT group call using a pre-established session are defined in clause 10.1.2.3.2;
- originating a private call from a MCPTT client using a pre-established session are defined in clause 11.1.1.3.1.2;
- establishing a private call to a MCPTT client using a pre-established session are defined in clause 11.1.1.3.2;
- releasing a private call initiated by the served MCPTT client using a pre-established session are defined in clause 11.1.3.2.1.2; and
- releasing a private call initiated by the remote MCPTT client using a pre-established session are defined in clause 11.1.3.2.2.2.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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];
- while the MCPTT client is not SIP registered as specified in 3GPP TS 24.229 [4] and the UE serving the MCPTT client is switched on;
- while the UE serving the MCPTT client is switched off; and
- while the UE serving the MCPTT client is power-cycled.
NOTE: MCPTT client ID is not preserved when the UE is reset to factory settings.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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-broadcast group and group-broadcast group calls as specified in 3GPP TS 22.179 [2], 3GPP TS 22.280 [76] and 3GPP TS 23.379 [3]. In the present release of the specification, a broadcast group call can be initiated by an MCPTT user on any MCPTT group that the MCPTT user is part of.
NOTE 1: Configuration related to the authorisation to create a user-broadcast group or a group-broadcast exists in the user profile document as specified in 3GPP TS 24.484 [50], but is not used by any procedures in 3GPP TS 24.481 [31] in the current release, as the ability for an authorised user to create user-broadcast groups and group-broadcast groups is not provided in the current release.
NOTE 2: Configuration related to broadcast group hierarchies can be found in the group document as specified in 3GPP TS 24.481 [31] and in the service configuration document as specified in 3GPP TS 24.484 [50]. However, this configuration is not used by any procedures in 3GPP TS 24.380 [5] in the current release.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 interface for 5G networks with a trusted application function as defined in 3GPP TS 29.514 [96]; or
- indirectly via N33 interface for 5G networks with an untrusted application function as defined in 3GPP TS 29.522 [97];
When the MCPTT client uses an access network in which dedicated bearers cannot be established, the MCPTT system may decide to not request resources via Rx, N5 or N33. The MCPTT system may determine which access network the MCPTT client is using from the SIP header P-Access-Network-Info, see reference 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
5 Functional entities
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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]).
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 present document, an MCPTT client shall:
- support the MCPTT client on-network procedures defined in 3GPP TS 23.379 [3];
- support the GCS UE procedures defined in 3GPP TS 23.468 [57] for unicast delivery, MBMS delivery and service continuity;
- support 5G multicast-broadcast services defined in 3GPP TS 23.247 [91];
- act as a SIP UA as defined in 3GPP TS 24.229 [4];
- generate SDP offer and SDP answer in accordance with 3GPP TS 24.229 [4] and clause 6.2;
- act as a floor participant responsible for floor requests and implement the on-network procedures for floor requests as specified in 3GPP TS 24.380 [5];
- for registration and service authorisation, implement the procedures specified in clause 7.2;
- for pre-established sessions, implement the procedures specified in clause 8.2.1, clause 8.3.1, clause 8.4.1, and the procedures specified in 3GPP TS 24.380 [5];
- for affiliation, implement the procedures specified in clause 9.2;
- for functional alias management, implement the procedures specified in clause 9A.2;
- for group call functionality (including broadcast, emergency and imminent peril), implement the MCPTT client procedures specified in clause 10.1; and
- for private call functionality (including emergency), implement the MCPTT client procedures specified in clause 11.1;
- for emergency alert, implement the procedures specified in clause 12.1;
- for location reporting, implement the procedures specified in clause 13.3;
- for MBMS transmission usage, implement the procedures in clause 14.3; and
- for MBS transmission usage, implement the procedures in clause 14B.3.
To be compliant with the off-network procedures in the present document, an MCPTT client shall:
- support the off-network procedures defined in 3GPP TS 23.379 [3];
- support the MCPTT off-network protocol (MONP) defined in clause 15;
- act as a floor participant for floor requests and implement the off-network procedures for floor requests as specified in 3GPP TS 24.380 [5];
- act as a floor control server providing distributed floor control and implement the off-network procedures for floor control as specified in 3GPP TS 24.380 [5];
- implement the procedures for ProSe direct discovery for public safety use as specified in 3GPP TS 24.334 [28];
- implement the procedures for one-to-one ProSe direct communication for Public Safety use as specified in 3GPP TS 24.334 [28];
- implement the procedures for one-to-many ProSe direct communication for Public Safety use as specified in 3GPP TS 24.334 [28];
- for group call functionality (including emergency and imminent peril), implement the MCPTT client procedures specified in clause 10.2;
- for broadcast group call functionality implement the procedures specified in clause 10.3; and
- for private call functionality (including emergency), implement the MCPTT client procedures specified in clause 11.2.
To be compliant with the service continuity procedures in the present document, an MCPTT client shall:
- implement the registration requirements for service continuity as specified in clause 7.2.1; and
- implement the procedures specified in clause 14A.
To be compliant with the on-network and off-network procedures in the present document requiring end-to-end private call security key distribution, an MCPTT client shall support the procedures specified in 3GPP TS 33.180 [78].
To be compliant with the procedures for confidentiality protection of XML elements in the present document, the MCPTT client shall implement the procedures specified in clause 6.6.2.
To be compliant with the procedures for integrity protection of XML MIME bodies in the present document, the MCPTT client shall implement the procedures specified in clause 6.6.3.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
5.3 MCPTT server
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 involving groups from multiple MCPTT systems as specified in 3GPP TS 23.379 [3].
An MCPTT server can perform a non-controlling role for temporary group calls involving groups only from the primary MCPTT system.
An MCPTT server performing the participating role can serve an originating MCPTT user.
An MCPTT server performing the participating role can serve a terminating MCPTT user.
The same MCPTT server can perform the participating role and controlling role for the same group session.
The same MCPTT server can perform the participating role and non-controlling role for the same group session.
When referring to the procedures in the present document for the MCPTT server acting in a participating role for the served user, the term, "participating MCPTT function" is used.
When referring to the procedures in the present document for the MCPTT server acting in a controlling role for the served user, the term "controlling MCPTT function" is used.
When referring to the procedures in the present document for the MCPTT server acting in a non-controlling role for a group call, the term "non-controlling MCPTT function of an MCPTT group" is used.
To be compliant with the procedures in the present document, an MCPTT server shall:
- support the MCPTT server procedures defined in 3GPP TS 23.379 [3];
- implement the role of an AS performing 3rd party call control acting as a routing B2BUA as defined in 3GPP TS 24.229 [4];
- support the GCS AS procedures defined in 3GPP TS 23.468 [57] for unicast delivery, MBMS delivery and service continuity;
- support 5G multicast-broadcast services defined in 3GPP TS 23.247 [91];
- generate SDP offer and SDP answer in accordance with 3GPP TS 24.229 [4] and clause 6.3;
- implement the role of a centralised floor control server and implement the on-network procedures for floor control as specified in 3GPP TS 24.380 [5];
- for registration and service authorisation, implement the procedures specified in clause 7.3;
- for pre-established sessions, implement the procedures specified in clause 8.2.2, clause 8.3.2, clause 8.4.2 and the procedures specified in 3GPP TS 24.380 [5];
- for affiliation, implement the procedures specified in clause 9.2.2;
- for functional alias management, implement the procedures specified in clause 9A.2.2;
- for group call functionality (including broadcast, emergency and imminent peril), implement the MCPTT server procedures specified in clause 10.1;
- for private call functionality (including emergency), implement the MCPTT server procedures specified in clause 11.1;
- for priority sharing, implement the MCPTT server procedures in clause 6.7; and
- for MBMS transmission usage, implement the procedures in clause 14.2; and
- for MBS transmission usage, implement the procedures in clause 14B.2.
To be compliant with the procedures in the present document requiring the distribution of private call keying material between MCPTT clients as specified in 3GPP TS 33.180 [78], an MCPTT server shall ensure that the keying material is copied from incoming SIP messages into the outgoing SIP messages.
To be compliant with the procedures for confidentiality protection of XML elements in the present document, the MCPTT server shall implement the procedures specified in clause 6.6.2.
To be compliant with the procedures for integrity protection of XML MIME bodies in the present document, the MCPTT server shall implement the procedures specified in clause 6.6.3.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 implemented on more than one MCPTT server. For example, there could be an instantiation of an MCPTT server that only serves as a controlling MCPTT function, but not as a participating MCPTT function for any MCPTT clients. When an MCPTT server supports more than one function, then sending requests from one function to another does not incur a traversal of the underlying IMS SIP core network.
Figure 5.3.2-1 shows the basic functions of the MCPTT server when operating within the primary MCPTT system.
Figure 5.3.2-1: Functions of the MCPTT server in the primary MCPTT system
Figure 5.3.2-2 shows the use of the non-controlling MCPTT function of an MCPTT group within the primary MCPTT system. This can occur due to group re-grouping of groups within the same MCPTT system, where the MCPTT server(s) of one or more of the constituent groups are not controlled by the same controlling MCPTT function as that of the temporary group. The non-controlling MCPTT function of an MCPTT group either provide the identities of the users of the group to the controlling MCPTT function, or the non-controlling MCPTT function of an MCPTT group can invite the users of the group on behalf of the controlling MCPTT function.
Figure 5.3.2-2: The non-controlling function operating in the primary MCPTT system
Figure 5.3.2-3 shows the roles of the MCPTT server in a mutual aid relationship between a primary MCPTT system and a partner MCPTT system. Here, the controlling MCPTT function is in the primary MCPTT system and the called user is homed in a partner MCPTT system.
Figure 5.3.2-3: Mutual aid relationship between the primary MCPTT system and a partner MCPTT system with the controlling MCPTT function in the primary MCPTT system
Figure 5.3.2-4 shows the roles of the MCPTT server in a mutual aid relationship between a primary MCPTT system and a partner MCPTT system. Here, the controlling MCPTT function is in the partner MCPTT system.
Figure 5.3.2-4: Mutual aid relationship between the primary MCPTT system and a partner MCPTT system with the controlling MCPTT function in the partner MCPTT system
Figure 5.3.2-5 shows the roles of the MCPTT server in a mutual aid relationship between a primary MCPTT system and a partner MCPTT with the use of a non-controlling MCPTT function of an MCPTT group within the partner MCPTT system. This can occur due to group re-grouping where the MCPTT server(s) of one or more of the constituent groups are homed on the partner system. If the primary MCPTT system and partner MCPTT system operate in a trusted mutual aid relationship, then the non-controlling MCPTT function of an MCPTT group can provide the identities of the users of the group to the controlling MCPTT function. If the primary MCPTT system and partner MCPTT system operate in an untrusted mutual aid relationship, then the non-controlling MCPTT function of an MCPTT group invites the users of the group on behalf of the controlling MCPTT function.
Figure 5.3.2-5: Mutual aid relationship between the primary MCPTT system and a partner MCPTT system involving the use of a non-controlling MCPTT function of an MCPTT group in the partner MCPTT system
Figure 5.3.2-6 illustrates a functional connectivity model involving multiple partner systems where the partner system that owns the group does not home any of the group members.
Figure 5.3.2-6: : Mutual aid relationship between the primary MCPTT system and more than one partner MCPTT system
Other functional connectivity models can exist.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 to "pf-mcptt-server", "cf-mcptt-server" or "ncf-mcptt-server" depending on the current role endorsed by the MCPTT server and in accordance with clause 7.2.17 of 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 and deallocate TMGIs when no longer necessary, per 3GPP TS 23.468 [57] and 3GPP TS 29.468 [42];
- handle MBMS bearers related notifications per 3GPP TS 23.468 [57] and 3GPP TS 29.468 [42]; and
- adjust the priority / pre-emption characteristics of MBMS bearers, as appropriate, in response to relevant events (e.g. emergency or imminent peril call), using procedures specified in per 3GPP TS 23.468 [57] and 3GPP TS 29.468 [42].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 3GPP TS 23.247 [91];
- update the MBS sessions to be used for updating the MBS service areas and/or MBS Service Information, per 3GPP TS 23.247 [91].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
5.5 MCPTT gateway server
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 gateway server acts as an application and security gateway with a partner MCPTT system in a different trust domain.
An MCPTT gateway server provides topology hiding to the partner MCPTT system in a different trust domain.
An MCPTT gateway server enforces local policies and local security.
An MCPTT gateway server can be an exit point from its MCPTT system to a partner MCPTT system in a different trust domain, an entry point to its MCPTT system from a partner MCPTT system in a different trust domain, or both.
An MCPTT gateway server is transparent to MCPTT controlling and participating servers. When required for interconnection, MC gateway servers URIs are known and used by MCPTT servers in place of the PSIs of the interconnected MCPTT server. The MCPTT server does not need to know if it finally addresses directly an MCPTT controlling function or an intermediate MCPTT gateway server.
To be compliant with the procedures in the present document, an MCPTT gateway server shall:
- support the MC gateway server procedures defined in 3GPP TS 23.280 [82] and 3GPP TS 23.379 [3]; and
- support the MC gateway server procedures defined in 3GPP TS 33.180 [78];
- implement the procedures specified in clause 6.8
To be compliant with the procedures for confidentiality protection in the present document, the MCPTT gateway server shall implement the procedures specified in clause 6.6.2, acting on behalf of the MCPTT server when sending or receiving confidentiality protected content to or from an MCPTT server in another trust domain.
To be compliant with the procedures for integrity protection of XML MIME bodies in the present document, the MCPTT gateway server shall implement the procedures specified in clause 6.6.3, acting on behalf of the MCPTT server when sending or receiving integrity protected content to or from an MCPTT server in another trust domain.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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. Here, the originating participating MCPTT function and the controlling MCPTT function are in the primary MCPTT system and a terminating participating MCPTT function is in a partner MCPTT system.
Figure 5.5.2-1: Non trusted relationship between the primary MCPTT system and a partner MCPTT system with a terminating participating MCPTT function in the partner MCPTT system
Figure 5.5.2-2 shows the roles of the MCPTT servers in a non trusted relationship between a primary MCPTT system and a partner MCPTT system. Here, the originating participating MCPTT function is in the primary MCPTT system and the controlling MCPTT function and a terminating participating MCPTT function are in a partner MCPTT system.
Figure 5.5.2-2: Non trusted relationship between the primary MCPTT system and a partner MCPTT system with a controlling MCPTT function in the partner MCPTT system
Other functional connectivity models for non trusted relationship exist, based on the same principle of use of MCPTT gateway servers, e.g. with non-controlling MCPTT functions.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
5.6 MCPTT gateway UE
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 functions:
- Relay of signaling, media and floor control between an MCPTT client in the non-3GPP device and MCPTT servers; and
- Access to a MCPTT system with required quality of service using 3GPP network.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 corresponding service types. MC gateway UEs for different service types can be deployed in the same UE.
Figure 5.6.2-1 shows the scenario when the MCPTT client resides in the MCPTT gateway UE. Handling of the MCPTT service by the MCPTT client on the MCPTT gateway UE follows the procedures defined in this document for MCPTT clients hosted on regular MCPTT UEs. How the non-3GPP device interacts with the MCPTT client over a non‑3GPP access technology is not part of the current specification.
Figure 5.6.2-1: Relationship between non-3GPP device, MCPTT gateway UE and the MCPTT server with the MCPTT client located in the MCPTT gateway UE
Figure 5.6.2-2 shows the scenario when the MCPTT client resides in the non-3GPP device that uses a non‑3GPP access technology to access the MCPTT service. In this case the MCPTT gateway UE will relay the signaling between the MCPTT client and the MCPTT System as well as forward the media plane.
Figure 5.6.2-2: Relationship between non-3GPP device, MCPTT gateway UE and the MCPTT server with the MCPTT client located in the non-3GPP device
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 gateway UE. In the case that a local IP network is used, MCPTT gateway UE needs to handle routing including network address translation (NAT).
When using a MCPTT gateway UE, the 3GPP QoS and priority functions shall be utilized between the MCPTT gateway UE and the packet gateway. QoS between the non 3GPP device and the MCPTT gateway UE is out of scope of 3GPP.
In the case that MCPTT clients are hosted in non 3GPP devices the following applies. The MCPTT system may use the P-Access-Network-Info header to determine the type of access network. However, the P-Access-Network-Info header does not include sufficient information for the MCPTT system to determine that the MCPTT client is using a MCPTT gateway UE. Hence, the MCPTT client shall additionally inform the MCPTT system that the MCPTT client uses a MCPTT gateway UE for which the MCPTT system shall request network resources.
In the case that MCPTT clients are instantiated in a MCPTT gateway UE, the MCPTT clients shall utilize the existing quality of services functions.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6 Common procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.1 Introduction
|
This clause describes the common procedures for each functional entity as specified.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2 MCPTT client procedures
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.0 Distinction of requests at the MCPTT client
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 element. Such requests are known as "SIP MESSAGE request for location report configuration" in the present document;
- 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 Request element. Such requests are known as "SIP MESSAGE request for location report request" in the present document;
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "private-call-call-back-request". Such requests are known as "SIP MESSAGE request for private call call-back request for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "private-call-call-back-cancel-request". Such requests are known as "SIP MESSAGE request for private call call-back cancel request for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <response-type> element set to a value of "private-call-call-back-response". Such requests are known as "SIP MESSAGE request for private call call-back response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <response-type> element set to a value of "private-call-call-back-cancel-response". Such requests are known as "SIP MESSAGE request for private call call-back cancel response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "group-selection-change-request". Such requests are known as "SIP MESSAGE request for group selection change request for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <response-type> element set to a value of "group-selection-change-response". Such requests are known as "SIP MESSAGE request for group selection change response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "remotely-initiated-group-call-request". Such requests are known as "SIP MESSAGE request for remotely initiated group call request for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <response-type> element set to a value of "remotely-initiated-group-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated group call response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "remotely-initiated-private-call-request". Such requests are known as "SIP MESSAGE request for remotely initiated private call request for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <response-type> element set to a value of "remotely-initiated-private-call-response". Such requests are known as "SIP MESSAGE request for remotely initiated private call response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/mikey" and a CSB-ID containing a CSK-ID. Such requests are known as "SIP MESSAGE request for CSK download for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcptt-info> root element containing the <mcptt-Params> element and an <emergency-alert-area-ind> element. Such requests are known as "SIP MESSAGE request for notification of entry into or exit from an emergency alert area";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcptt-info> root element containing the <mcptt-Params> element and an <group-geo-area-ind> element. Such requests are known as "SIP MESSAGE request for notification of entry into or exit from a group geographic area";
- SIP MESSAGE requests routed to the MCPTT client with the Request-URI set to a public user identity of the MCPTT user that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body and a <regroup-action> element set to "create". Such requests are known as "SIP MESSAGE request to the MCPTT client to request creation of a regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE requests routed to the MCPTT client with the Request-URI set to a public user identity of the MCPTT user that contains a <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body and a <regroup-action> element set to "remove". Such requests are known as "SIP MESSAGE request to the MCPTT client to request removal of a regroup using preconfigured group" in the procedures in the present document;
- SIP MESSAGE request routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "transfer-private-call-request". Such requests are known as "SIP MESSAGE request for transfer private call request for terminating client";
- SIP MESSAGE request routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <responset-type> element set to a value of "transfer-private-call-response". Such requests are known as "SIP MESSAGE request for transfer private call response for terminating client";
- SIP MESSAGE request routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <request-type> element set to a value of "forward-private-call-request". Such requests are known as "SIP MESSAGE request for forwarding private call request for terminating client";
- SIP MESSAGE request routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and includes an XML body containing a <mcpttinfo> root element containing the <mcptt-Params> element and an <anyExt> element containing the <responset-type> element set to a value of "forward-private-call-response". Such requests are known as "SIP MESSAGE request for forwarding private call response for terminating client";
- SIP MESSAGE requests routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcptt-info> root element containing the <mcptt-Params> element and an <adhoc-emergency-alert-ind> element. Such requests are known as "SIP MESSAGE request for adhoc group emergency notification";
- SIP MESSAGE requests routed to the MCPTT client with the Request-URI set to the public user identity of the MCPTT user and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <imminentperil-ind> element. Such requests are known as "SIP MESSAGE request for imminent peril state change notification for terminating MCPTT client" in the procedures in the present document;
- SIP MESSAGE requests routed to the MCPTT client with the Request-URI set to the public user identity of the MCPTT user and containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing a <mcptt-Params> element containing an <anyExt> element containing a <forwarding-reason> element set to "migrated". Such requests are known as "SIP MESSAGE request with notification of ad hoc group call redirection " in the procedures in the present document;
- a SIP MESSAGE request which is routed to the MCPTT client and includes an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcptt-Params> element containing a <resp-type> element set to "ad-hoc-emergency-alert-participant-criteria-modification". Such requests are known as "SIP MESSAGE request for participant criteria modification response for ad hoc group emergency alert from participating MCPTT function" in the procedures in the present document; and
- SIP MESSAGE request routed to the MCPTT client containing a Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and including an XML body containing a <mcpttinfo> root element containing an <mcptt-Params> element with an <anyExt> element containing a <req-type> element set to the value of "emergency-remote-floor-request-trigger". Such requests are known as "SIP MESSAGE request for emergency remote floor request trigger for terminating client".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 address of the MCPTT client for the offered MCPTT speech media stream and, if media plane control messages shall be used, for the offered media plane control channel;
NOTE 1: If the MCPTT client is behind a NAT the IP address and port included in the SDP offer can be a different IP address and port than the actual IP address and port of the MCPTT client depending on the NAT traversal method used by the SIP/IP Core.
2) shall include an "m=audio" media-level section for the MCPTT media stream consisting of:
a) the port number for the media stream selected, with the following clarification:
i) if the MCPTT client is requesting an upgrade (resp. downgrade) of an already established session to (resp. from) emergency or imminent peril and if multiplexing of media streams was used, the MCPTT client should select a different port number not to impact the resource priority used for the other multiplexed media streams;
b) the codec(s) and media parameters and attributes with the following clarification:
i) if the MCPTT client is initiating a call to a group identity;
ii) if the <preferred-voice-encodings> element is present in the group document retrieved by the group management client as specified in 3GPP TS 24.481 [31] containing an <encoding> element with a "name" attribute; and
iii) if the MCPTT client supports the encoding name indicated in the value of the "name" attribute;
then the MCPTT client:
i) shall insert the value of the "name" attribute in the <encoding name> field of the "a=rtpmap" attribute as defined in IETF RFC 4566 [12];
c) if the SDP offer is for an ambient listening call:
i) if this is a remotely initiated ambient listening call, include an "a=recvonly" attribute; or
ii) if this is a locally initiated ambient listening call, include an "a=sendonly" attribute;
d) "i=" field set to "speech" according to 3GPP TS 24.229 [4]; and
e) if the MCPTT client is initiating a call with implicit floor request:
i) may include an "a=ssrc" attribute as specified in IETF RFC 5576 [86] where the MCPTT client may indicate to the MCPTT server which RTP SSRC it would like to use in the subsequent RTP media flow if the implicit floor request is granted;
NOTE 2: The actual RTP SSRC that the client will have to use if the implicit floor request is granted will be received either in the mc-ssrc attribute of the SDP answer in the case of an implicit floor grant, or in the corresponding information element of the floor granted message in the case of an explicit floor grant. The client will use the RTP SSRC received from the MCPTT server regardless of this optional a=ssrc attribute.
3) if media plane control messages shall be used during the session, shall include an "m=application" media-level section as specified in 3GPP TS 24.380 [5] clause 4.3, consisting of:
a) the port number for the media plane control channel selected as specified in 3GPP TS 24.380 [5], ], with the following clarification:
i) if the MCPTT client is requesting an upgrade (resp. downgrade) of an already established session to (resp. from) emergency or imminent peril and if multiplexing of media plane control channels was used, the MCPTT client should select a different port number not to impact the resource priority used for the other multiplexed media plane control channels;
b) an mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14, with the RTCP SSRC that the MCPTT client has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the participating MCPTT function in the floor control messages sent to the MCPTT client for this session; and
NOTE 3: The MCPTT client will receive in the SDP answer the RTP SSRC it will have to use in the floor control message it will send to the participating MCPTT function in this session.
c) any other necessary 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14; and
NOTE 4: The same media plane control channel is used for transport of messages associated with floor control, pre-established session call control and MBMS bearer management.
4) if end-to-end security is required for a private call and the SDP offer is not for establishing a pre-established session, shall include the MIKEY-SAKKE I_MESSAGE in an "a=key-mgmt" attribute as a "mikey" attribute value in the SDP offer as specified in IETF RFC 4567 [47].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 address of the MCPTT client for the accepted MCPTT speech media stream and, if included in the SDP offer, for the accepted media-floor control entity;
NOTE 1: If the MCPTT client is behind a NAT the IP address and port included in the SDP answer can be a different IP address and port than the actual IP address and port of the MCPTT client depending on the NAT traversal method used by the SIP/IP Core.
3) shall include an "m=audio" media-level section for the accepted MCPTT speech media stream consisting of:
a) the port number for the media stream with the following clarification:
i) if the MCPTT client is responding to an upgrade (resp. downgrade) of an already established session to (resp. from) emergency or imminent peril and if multiplexing of media streams was used, the MCPTT client should select a different port number not to impact the resource priority used for the other multiplexed media streams;
b) media-level attributes as specified in 3GPP TS 24.229 [4];
c) if the "a=recvonly" attribute is present in the SDP offer, include an "a=sendonly" attribute;
d) if the "a=sendonly" attribute is present in the SDP offer, include an "a=recvonly" attribute; and
e) "i=" field set to "speech" according to 3GPP TS 24.229 [4];
4) if included in the SDP offer, shall include an "m=application" media-level section of the offered media-floor control entity as specified in 3GPP TS 24.380 [5] clause 4.3, consisting of:
a) the port number for the media plane control channel selected as specified in 3GPP TS 24.380 [5], with the following clarification:
i) if the MCPTT client is requesting an upgrade (resp. downgrade) of an already established session to (resp. from) emergency or imminent peril and if multiplexing of media plane control channels was used, the MCPTT client should select a different port number not to impact the resource priority used for the other multiplexed media plane control channels; and
b) an mc_floor_ssrc 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14, with the RTCP SSRC that the MCPTT client has selected as specified in 3GPP TS 24.380 [5] clause 4.3 and shall be used by the participating MCPTT function in the floor control messages sent to the MCPTT client for this session; and
NOTE 2: The MCPTT client has received in the SDP offer the RTP SSRC it will have to use in the floor control message it will send to the participating MCPTT function in this session.
c) any other necessary 'fmtp' attribute as specified in 3GPP TS 24.380 [5] clause 14; and
5) if end-to-end security is required for a first-to-answer call, shall include the MIKEY-SAKKE I_MESSAGE in an "a=key-mgmt" attribute as a "mikey" attribute value in the SDP answer as specified in 3GPP TS 33.180 [78].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.3 Commencement modes
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.3.1 Automatic commencement mode
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP 200 (OK) response;
4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP 200 (OK) response;
5) shall include the Session-Expires header field in the SIP 200 (OK) response and start the SIP session timer according to IETF RFC 4028 [7]. The "refresher" parameter in the Session-Expires header field shall be set to "uas";
6) shall, if the incoming SIP INVITE request contains a Replaces header field, include in the SDP answer in the SIP 200 (OK) response to the SDP offer the parameters used for the pre-established session identified by the contents of the Replaces header field;
7) shall, if the incoming SIP INVITE request does not contain a Replaces header field, include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP INVITE request according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.2;
NOTE: In the case of a new emergency call where the terminating client is using a pre-established session, the SIP INVITE request containing a Replaces header is used to replace the pre-established session.
7a) shall, if the incoming SIP INVITE request contains a <transfer-announced-ind> element in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body, set the value of the <replaces-header-value> element contained in the <anyExt> element of the <mcptt-Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body to the following value: The Call-ID header field, and the value of the from-tag header field parameter set to the value contained in the incoming SIP INVITE request. The value of the to-tag is the one set by the MCPTT client in the 200 (OK) response. Together they represent a dialog identifier;
8) shall send the SIP 200 (OK) response towards the MCPTT server according to rules and procedures of 3GPP TS 24.229 [4];
9) shall, if the incoming SIP INVITE request contains a Replaces header field, release the pre-established session identified by the contents of the Replaces header field; and
10) shall interact with the media plane as specified in 3GPP TS 24.380 [5] clause 6.2.
When NAT traversal is supported by the MCPTT client and when the MCPTT client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [15].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.3.2 Manual commencement mode
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 specified in clause 4.4, and not continue with the rest of the steps in this clause; and
2) if the MCPTT user requests to forward the MCPTT private call based on manual user input, the MCPTT client shall send a SIP 480 (Temporarily Unavailable) response including warning text set to "175 call is forwarded" in a Warning header field as specified in clause 4.4 and follow the procedures as specified in clause 11.1.9.2.1, and not continue with the rest of the steps in this clause.
The MCPTT client:
1) shall accept the SIP INVITE request and generate a SIP 180 (Ringing) 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 180 (Ringing) response;
3) shall include the g.3gpp.mcptt media feature tag in the Contact header field of the SIP 180 (Ringing) response;
4) shall include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP 180 (Ringing) response; and
5) shall send the SIP 180 (Ringing) response to the MCPTT server.
When sending the SIP 200 (OK) response to the incoming SIP INVITE request, the MCPTT client shall follow the procedures in clause 6.2.3.1.1.
When NAT traversal is supported by the MCPTT client and when the MCPTT client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [15].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 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 specified in clause 4.4, and not continue with the rest of the steps in this clause.
When generating a SIP 183 (Session Progress) response, the MCPTT client:
1) 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 feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt";
When sending the SIP 200 (OK) response to the incoming SIP INVITE request, the MCPTT client shall follow the procedures in clause 6.2.3.1.2.
When NAT traversal is supported by the MCPTT client and when the MCPTT client is behind a NAT, generation of SIP responses is done as specified in this clause and as specified in IETF RFC 5626 [15].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.4 Leaving an MCPTT session initiated by MCPTT client
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 MCPTT session identity to leave;
4) if the MCPTT user leaves the session due to migration, shall set the Reason SIP header according to IETF RFC 3326 [98] with the protocol set to SIP, the cause value set to 200, and the reason-text set to "User migration"; and
5) shall send a SIP BYE request towards MCPTT server according to 3GPP TS 24.229 [4].
Upon receiving a SIP 200 (OK) response to the SIP BYE request, the MCPTT client shall interact with the media plane as specified in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27];
3) shall set the Request-URI of the SIP REFER request to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
4) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
5) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
6) shall set the Refer-To header field of the SIP REFER request to the MCPTT session identity to leave;
7) shall include the "method" SIP URI parameter with the value "BYE" in the URI in the Refer-To header field;
8) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session;
9) if the MCPTT user leaves the session due to migration, shall set the Reason SIP header according to IETF RFC 3326 [98] with the protocol set to SIP, the cause value set to 200, and the reason-text set to "User migration"; and
10) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response to the SIP REFER request, the MCPTT client shall interact with media plane as specified in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.5 Releasing an MCPTT session initiated by MCPTT client
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 3GPP TS 24.380 [5];
3) shall generate a SIP BYE request according to 3GPP TS 24.229 [4];
4) shall set the Request-URI to the MCPTT session identity to release; and
5) shall send a SIP BYE request towards MCPTT server according to 3GPP TS 24.229 [4].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27];
3) shall set the Request-URI of the SIP REFER request to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
4) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
5) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
6) shall set the Refer-To header field of the SIP REFER request to the MCPTT session identity to release;
7) shall include the "method" SIP URI parameter with the value "BYE" in the URI in the Refer-To header field;
8) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session; and
9) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
Upon receiving a SIP 2xx response to the SIP REFER request, the MCPTT client shall interact with media plane as specified in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.7 Void
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8 Priority call conditions
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.1 MCPTT emergency group call conditions
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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+xml MIME body in the SIP INVITE request or SIP REFER request, an <emergency-ind> element set to "true";
2) if the MCPTT emergency group call state is set to "MEGC 1: emergency-gc-capable", shall set the MCPTT emergency group call state to "MEGC 2: emergency-call-requested";
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, and the MCPTT emergency alert state is set to "MEA 1: no-alert", shall:
a) set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "true" and set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP INVITE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent and the MCPTT emergency alert state is set to "MEA 1: no-alert", shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT client emergency group state of the group is set to a value other than "MEG 2: in-progress" set the MCPTT client emergency group state of the MCPTT group to "MEG 4: confirm-pending".
NOTE 1: This is the case of an MCPTT user already being in the MCPTT emergency state it initiated previously while originating an MCPTT emergency group call or MCPTT emergency alert. All group calls the MCPTT user originates while in MCPTT emergency state will be MCPTT emergency group calls.
When the MCPTT emergency state is clear and the MCPTT emergency group call state is set to "MEGC 1: emergency-gc-capable" and the the MCPTT user is authorised to initiate an MCPTT emergency group call on the targetted MCPTT group as determined by the procedures of clause 6.2.8.1.8, the MCPTT client:
1) shall set the MCPTT emergency state;
2) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request or SIP REFER request an <emergency-ind> element set to "true" and set the MCPTT emergency group call state to "MEGC 2: emergency-call-requested" state;
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, shall:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body the <alert-ind> element set to "true" and set the MCPTT emergency alert state to "MEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP INVITE request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT client emergency group state of the group is set to a value other than "MEG 2: in-progress" shall set the MCPTT client emergency group state of the MCPTT group to "MEG 4: confirm-pending".
NOTE 2: This is the case of an initial MCPTT emergency group call and optionally an MCPTT emergency alert being sent. As the MCPTT emergency state is not sent, there is no MCPTT emergency alert outstanding.
NOTE 3: An MCPTT group call originated by an affiliated member of an MCPTT group which is in an in-progress emergency state (as tracked on the MCPTT client by the MCPTT client emergency group state) but is not in an MCPTT emergency state of their own will also be an MCPTT emergency group call. The <emergency-ind> and <alert-ind> elements of the application/vnd.3gpp.mcptt-info+xml MIME body do not need to be included in this case and hence no action needs to be taken in this clause.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 emergency group state of the group is set to "MEG 2: in-progress", the MCPTT client shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for an MCPTT emergency group call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress emergency state of the group (as tracked on the MCPTT client by the MCPTT client emergency group state) but can use this knowledge to provide a Resource-Priority header field set to emergency level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
If this is an authorised request to cancel the MCPTT emergency group call as determined by the procedures of clause 6.2.8.1.7, and the MCPTT client emergency group state of the group is "no-emergency" or "cancel-pending", the MCPTT client shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.2.8.1.15.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 below.
NOTE 1: This procedure assumes that the calling procedure has verified that the MCPTT user has made an authorised request for cancelling MCPTT in-progress emergency group state of the group.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall clear the MCPTT emergency state; and
3) shall set MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending"
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT emergency group call and wants to cancel it.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to a value other than "MEA 1: no-alert" and the MCPTT user has indicated only the MCPTT emergency group call should be cancelled, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false"; and
2) shall set the MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending".
NOTE 3: This is the case of an MCPTT user has initiated both an MCPTT emergency group call and an MCPTT emergency alert and wishes to only cancel the MCPTT emergency group call. This leaves the MCPTT emergency state set.
If the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted" and the MCPTT emergency alert state is set to a value other than "MEA 1: no-alert" and the MCPTT user has indicated that the MCPTT emergency alert on the MCPTT group should be cancelled in addition to the MCPTT emergency group call, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall if this is an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to "false";
b) set the MCPTT emergency alert state to "MEA 4: Emergency-alert-cancel-pending"; and
c) clear the MCPTT emergency state;
3) should, if this is not an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.1.6, indicate to the MCPTT user that they are not authorised to cancel the MCPTT emergency alert; and
4) shall set the MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending".
NOTE 4: This is the case of an MCPTT user that has initiated both an MCPTT emergency group call and an MCPTT emergency alert and wishes to cancel both.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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" or "MEGC 3: emergency-call-granted":
a) shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress" if it was not already set;
b) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending" and the SIP 2xx response to the SIP request for a priority group call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated;
c) shall set the MCPTT emergency group call state to "MEGC 3: emergency-call-granted"; and
d) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable" and the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; or
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted" and the SIP 2xx response to the SIP request for an imminent peril group call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149":
a) set the MCPTT imminent peril group call state to "MIGC 3: imminent-peril-call-granted"; and
b) set the MCPTT imminent peril group state to "MIG 2: in-progress".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 set to "MEGC 2: emergency-call-requested" or "MEGC 3: emergency-call-granted":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
b) if the MCPTT client emergency group state of the group is "MEG 4: confirm-pending" shall set the MCPTT client emergency group state of the group to "MEG 1: no-emergency"; and
c) if the sent SIP request for a priority group call contained an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element set to a value of "true", shall set the MCPTT emergency alert state to "MEA 1: "no-alert"; and
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted":
a) shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true"; and
2) if the "entry-info" attribute of the <entry> element of the <EmergencyAlert> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of:
a) "DedicatedGroup", and if the <uri-entry> element of the <entry> element of the <EmergencyAlert> element of the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the MCPTT group identity of the MCPTT group targeted by the calling MCPTT user; or
b) "UseCurrentlySelectedGroup" and the <allow-MCPTT-emergency-alert> element of the <actions> element of a <rule> element of the <ruleset> element of the <list-service> element of the group document identified by the MCPTT group identity targeted for the emergency alert is set to a value of "true" as specified in 3GPP TS 24.481 [31];
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency alert to an MCPTT group, and if the <allow-cancel-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 MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request to cancel an MCPTT emergency alert.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 user profile document in 3GPP TS 24.484 [50]) is set to a value of "true" and
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> element contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <uri-entry> element of the <entry> element of the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element of the <EmergencyCall> contained within the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the MCPTT emergency group call request shall be considered to be an authorised request for an MCPTT emergency group call;
In all other cases, the request to originate an MCPTT emergency group call shall be considered to be an unauthorised request to originate an MCPTT emergency group call.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril group call the MCPTT client shall check the following:
1 if the <allow-imminent-peril-call> element of <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 [50]) is set to a value of "true" and:
a) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "DedicatedGroup" and if the <MCPTTGroupInitiation> element contains the identity of the MCPTT group targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTGroupInitiation> element contained within the <ImminentPerilCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UseCurrentlySelectedGroup";
then the MCPTT imminent peril group call request shall be considered to be an authorised request for an MCPTT imminent peril group call;
In all other cases, the request to originate an MCPTT imminent peril group call shall be considered to be an unauthorised request to originate an MCPTT imminent peril group call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 client imminent peril call group state is set to "MIGC 1: imminent-peril-gc-capable" and the MCPTT client emergency group state of the MCPTT group is set to "MEG 1: no-emergency":
a) shall include in the SIP request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in Annex F.1 with the <imminentperil-ind> element set to "true" and set the MCPTT imminent peril group call state to "MIGC 2: imminent-peril-call-requested" state; and
b) if the MCPTT client imminent peril group state of the group is set to a value other than "MIG 2: in-progress" shall set the MCPTT client imminent peril group state of the MCPTT group to "MIG 4: confirm-pending".
NOTE: An MCPTT group call originated by an affiliated member of an MCPTT group which is in an in-progress imminent peril state (as tracked on the MCPTT client by the MCPTT client imminent peril group state) will also have the priority associated with MCPTT imminent peril group calls. The <imminentperil-ind> element of the application/vnd.3gpp.mcptt-info MIME body does not need to be included in this case, nor do any state changes result and hence no action needs to be taken in this clause.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 document in 3GPP TS 24.484 [50]) is set to a value of "true" the MCPTT imminent peril call cancellation request shall be considered to be an authorised request to cancel the MCPTT imminent peril group call; or
2) 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 document in 3GPP TS 24.484 [50]) is set to a value of "false" the MCPTT imminent peril call cancellation request shall be considered to be an unauthorised request to cancel the MCPTT imminent peril group call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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] with the clarifications given below.
NOTE 1: This procedure assumes that the calling procedure has verified that the MCPTT user has made an authorised request for cancelling the in-progress imminent peril group state of the group.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <imminentperil-ind> element set to "false"; and
2) shall set MCPTT imminent peril group state of the MCPTT group to "MIG 3: cancel-pending".
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT imminent peril group call and wants to cancel it, or another authorised member of the group who wishes to cancel the in-progress imminent peril state of the group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 procedures of clause 6.2.8.1.8, or the MCPTT client imminent peril state of the group is set to "MIG 2: in-progress", the MCPTT client:
1) shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for an MCPTT imminent peril group call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress imminent peril state of the group (as tracked on the MCPTT client by the MCPTT client imminent peril group state) but can use this knowledge to provide a Resource-Priority header field set to imminent peril level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
When the MCPTT imminent peril group call state is set to "MIGC 1: imminent-peril-gc-capable" and the MCPTT user is authorised to cancel MCPTT imminent peril group calls as determined by the procedures of clause 6.2.8.1.10, or the MCPTT client imminent peril group state of the group is "MIG 1: no-imminent-peril" or "MIG 3: cancel-pending", the MCPTT client:
1) shall include in the SIP INVITE request or SIP REFER request a Resource-Priority header field populated with the values for a normal MCPTT group call as specified in clause 6.2.8.1.15.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 package according to IETF RFC 6086 [64]; and
- with one or more of the <alert-ind>, <imminentperil-ind> and <emergency-ind> elements set in the application/vnd.3gpp.mcptt-info+xml MIME body;
the MCPTT client:
1) shall send a SIP 200 (OK) response to the SIP INFO request as specified in 3GPP TS 24.229 [4];
2) if the MCPTT emergency group call state is set to "MEGC 3: emergency-call-granted":
a) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending":
i) if the <alert-ind> element is set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
ii) if the <alert-ind> element is set to a value of "true", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated";
3) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested" or "MIGC 3: imminent-peril-call-granted":
a) if the <imminentperil-ind> element is set to a value of "false" and an <emergency-ind> element is set to a value of "true", shall:
i) set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril";
ii) set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable"; and
iii) set the MCPTT client emergency group state of the group to "MEG 2: in-progress"; and
NOTE 1: This is the case of an MCPTT client attempting to make an imminent peril group call when the group is in an in-progress emergency group state. The MCPTT client will then receive a notification that the imminent peril call request was denied, however they will be participating at the emergency level priority of the group. This could occur for example when an MCPTT client requests an imminent peril call to a group that they are not currently affiliated with.
NOTE 2: the MCPTT client emergency group state above is the MCPTT client's view of the in-progress emergency state of the group.
4) if the SIP request for a priority group call sent by the MCPTT client did not contain an <originated-by> element and if the MCPTT emergency alert state is set to "MEA 4: Emergency-alert-cancel-pending":
a) if the <alert-ind> element contained in the SIP INFO request is set to a value of "true", shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; and
b) if the <alert-ind> element contained in the SIP INFO request is set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 clarifications given below.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall set MCPTT emergency group state of the MCPTT group to "MEG 3: cancel-pending"; and
3) if the MCPTT user has indicated that an MCPTT emergency alert on the MCPTT group originated by another MCPTT user should be cancelled and this is an authorised request for an MCPTT emergency alert cancellation as determined by the procedures of clause 6.2.8.1.6:
a) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set a value of "false"; and
b) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body an <originated-by> element set to the MCPTT ID of the MCPTT user who originated the MCPTT emergency alert.
NOTE: When an MCPTT emergency alert is cancelled by a MCPTT user other than its originator, the <originated-by> element is needed to identify which MCPTT emergency alert is being cancelled, as more than one MCPTT user could have originated emergency alerts to the same group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 the <resource-priority-namespace> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <emergency-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for an MCPTT imminent peril group call or MCPTT imminent peril adhoc group call, the MCPTT client:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <imminent-peril-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
When determining the Resource-Priority header field namespace and priority values as specified in IETF RFC 8101 [48] for a normal MCPTT group or private call or normal MCPTT adhoc group call, the MCPTT client:
1) shall retrieve the value of the <resource-priority-namespace> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]); and
2) shall retrieve the value of the <resource-priority-priority> element contained in the <normal-resource-priority> element contained in the <OnNetwork> element of the MCPTT service configuration document (see the service configuration document in 3GPP TS 24.484 [50]).
NOTE: The "normal" Resource-Priority header field value is needed to return to a normal priority value from a priority value adjusted for an MCPTT emergency group or private call or an MCPTT imminent peril group call. The "normal" priority received from the EPS by use of the "normal" Resource-Priority header field value is expected to be the same as the "normal" priority received from the EPS when initiating a call with no Resource-Priority header field included.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 emergency group call state is set to "MEGC 2: emergency-call-requested":
a) if there is no <emergency-ind> element or an <emergency-ind> element set to a value of "true" contained in the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP re-INVITE request, and if no <imminentperil-ind> element is included:
i) shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress" if it was not already set; and
ii) shall set the MCPTT emergency group call state to "MEGC 3: emergency-call-granted"; and
b) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending":
i) if the SIP re-INVITE request contains an <alert-ind> element set to a value of "true" or does not contain an <alert-ind> element, shall set the MCPTT emergency alert state to "MEA 3: emergency-alert-initiated"; or
ii) if the SIP re-INVITE request contains an <alert-ind> element set to a value of "false", shall set the MCPTT emergency alert state to "MEA 1: no-alert"; and
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested:
a) if the sip re-INVITE request contains an <imminentperil-ind> element set to a value of "true" or does not contain an <imminentperil-ind> element, shall:
i) set the MCPTT imminent peril group call state to "MIGC 3: imminent-peril-call-granted"; and
ii) set the MCPTT imminent peril group state to "MIG 2: in-progress"; or
b) if the SIP re-INVITE request contains <imminentperil-ind> element set to a value of "false" and an <emergency-ind> element set to a value of "true", shall set the MCPTT client emergency group state of the group to "MEG 2: in-progress".
NOTE: This is the case of an MCPTT client attempting to make an imminent peril group call when the group is in an in-progress emergency group state. The MCPTT client will then receive a notification that the imminent peril call request was denied, however they will be participating at the emergency level priority of the group. This could occur for example when an MCPTT client requests an imminent peril call to a group that they are not currently affiliated with.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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-requested":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable";
b) if the MCPTT client emergency group state of the group is "MEG 4: confirm-pending" shall set the MCPTT client emergency group state of the group to "MEG 1: no-emergency"; and
c) if the MCPTT emergency alert state is set to "MEA 2: emergency-alert-confirm-pending" shall set the MCPTT emergency alert state to "MEA 1: "no-alert";
2) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent-peril-call-requested":
a) if the MCPTT imminent peril group call state of the group is "MIG 4: confirm-pending", shall set the MCPTT imminent peril group state to "MIG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-gc-capable";
3) if the MCPTT emergency group call state is set to "MEGC 2: emergency-call-granted":
a) shall set the MCPTT emergency group call state to "MEGC 1: emergency-gc-capable"; and
4) if the MCPTT imminent peril group call state is set to "MIGC 2: imminent peril-call-granted":
a) shall set the MCPTT imminent peril group call state to "MIGC 1: imminent-peril-capable".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 emergency private call state to "MEPC 1: emergency-pc-capable";
b) if the MCPTT emergency private priority state of the private call is "MEPP 4: confirm-pending" shall set the MCPTT emergency private priority state of the private call to "MEPP 1: no-emergency"; and
c) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending shall set the MCPTT private emergency alert state to "MPEA 1: no-alert".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 of 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 initiating user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then the MCPTT adhoc group emergency alert origination request shall be considered to be an authorised request to originate the MCPTT adhoc group emergency alert. In all other cases, it shall be considered to be an unauthorised request for the origination of the MCPTT adhoc group emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT adhoc group emergency alert to an MCPTT adhoc group, and:
1) if the <allow-cancel-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 initiating MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then the MCPTT adhoc group emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT adhoc group emergency alert. In all other cases, it shall be considered to be an unauthorised request for cancellation of an MCPTT adhoc group emergency alert.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 not.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request or SIP REFER request, an <adhoc-emergency-ind> element set to "true";
3) shall set the MCPTT emergency adhoc group call state to "MEAGC 2: emergency-call-requested";
4) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 4: confirm-pending"; and
5) shall include the Resource-Priority header field populated with the values for an MCPTT emergency adhoc group call as specified in clause 6.2.8.1.15.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 2: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 2: in-progress" if it was not already set;
b) shall set the MCPTT emergency adhoc group call state to "MEAGC 3: emergency-call-granted"; and
c) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable" and the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; or
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) set the MCPTT imminent peril adhoc group call state to "MIAGC 3: imminent-peril-call-granted"; and
b) set the MCPTT imminent peril adhoc group state to "MIAG 2: in-progress".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
b) if the MCPTT emergency adhoc group state of the MCPTT adhoc group is "MEAG 4: confirm-pending", shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency"; or
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) if the MCPTT imminent peril adhoc group state of the MCPTT adhoc group is "MIAG 1: confirm-pending", shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", the MCPTT emergency adhoc group call request shall be considered to be an authorised request for an MCPTT emergency adhoc group call.
In all other cases, the request to originate an MCPTT emergency adhoc group call shall be considered to be an unauthorised request to originate an MCPTT emergency adhoc group call.
When the MCPTT client receives a request from the MCPTT user to originate an MCPTT imminent peril adhoc group call the MCPTT client shall check the following:
1 if the <allow-imminent-peril-adhoc-group-call> element of <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 [50]) is set to a value of "true", the MCPTT imminent peril adhoc group call request shall be considered to be an authorised request for an MCPTT imminent peril adhoc group call;
In all other cases, the request to originate an MCPTT imminent peril adhoc group call shall be considered to be an unauthorised request to originate an MCPTT imminent peril adhoc group call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 1: imminent-peril-gc-capable" and the MCPTT emergency adhoc group state of the MCPTT group is set to "MEAG 1: no-emergency":
a) shall include in the SIP request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in Annex F.1 with the <imminentperil-ind> element set to "true";
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 2: imminent-peril-call-requested" state;
c) shall set the MCPTT imminent peril adhoc group state of the MCPTT adhoc group to "MIAG 4: confirm-pending"; and
d) shall include the Resource-Priority header field populated with the values for an MCPTT imminent peril adhoc group call as specified in clause 6.2.8.1.15.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-requested":
a) if there is no <adhoc-emergency-ind> element or an <adhoc-emergency-ind> element set to a value of "true" contained in the application/vnd.3gpp.mcptt-info+xml MIME body received in the SIP re-INVITE request, and if no <imminentperil-ind> element is included:
i) shall set the MCPTT emergency adhoc group state of the MCPTT adhoc group to "MEAG 2: in-progress" if it was not already set; and
ii) shall set the MCPTT emergency adhoc group call state to "MEAGC 3: emergency-call-granted";
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested:
a) if the sip re-INVITE request contains an <imminentperil-ind> element set to a value of "true" or does not contain an <imminentperil-ind> element, shall:
i) set the MCPTT imminent peril adhoc group call state to "MIAGC 3: imminent-peril-call-granted"; and
ii) set the MCPTT imminent peril adhoc group state to "MIAG 2: in-progress"; or
b) if the SIP re-INVITE request contains <imminentperil-ind> element set to a value of "false" and an <adhoc-emergency-ind> element set to a value of "true", shall set the MCPTT emergency adhoc group state of the adhoc group to "MEAG 2: in-progress".
NOTE: This is the case of an MCPTT client attempting to make an imminent peril adhoc group call when the adhoc group is in an in-progress emergency adhoc group state. The MCPTT client will then receive a notification that the imminent peril adhoc call request was denied, however they will be participating at the emergency level priority of the adhoc group.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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: emergency-call-requested":
a) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
b) if the MCPTT emergency adhoc group state of the MCPTT adhoc group is "MEAG 3: confirm-pending", shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency";
2) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent-peril-call-requested":
a) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-gc-capable"; and
b) if the MCPTT imminent peril adhoc group state of the MCPTT adhoc group is "MIAG 3: confirm-pending", shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril";
3) if the MCPTT emergency adhoc group call state is set to "MEAGC 2: emergency-call-granted":
a) shall set the MCPTT emergency adhoc group state to "MEAG 1: no-emergency"; and
b) shall set the MCPTT emergency adhoc group call state to "MEAGC 1: emergency-gc-capable"; and
4) if the MCPTT imminent peril adhoc group call state is set to "MIAGC 2: imminent peril-call-granted":
a) shall set the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril"; and
b) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-capable".
NOTE: The above conditions can be applied upon a call being released within a pre-established by the procedures specified in clause 9.2.2 in 3GPP TS 24.380 [5].
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 of a group cancel request or not.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 clause F.1; and
2) in the case the prearranged group call is initiated using a pre-established session, shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the hname "body" parameter in the headers portion of the SIP URI in the Refer-To header field the <broadcast-ind> element set to "true" as defined in clause F.1.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3 MCPTT emergency private call conditions
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.1 Authorisations
| |
e34e50ff54835e88e5e7b14a5e4c1405
|
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 [50]) is set to a value of "true"; and
a) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "UsePreConfigured" and if the <uri-entry> element of the <entry> element of the <MCPTTPrivateRecipient> element contains the MCPTT ID of the MCPTT user targeted by the calling MCPTT user; or
b) if the "entry-info" attribute of the <entry> element of the <MCPTTPrivateRecipient> element of the <EmergencyCall> element contained within the <PrivateCall> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "LocallyDetermined";
then the MCPTT client shall consider the MCPTT emergency private call request to be an authorised request for an MCPTT emergency private call. In all other cases the MCPTT client shall consider the MCPTT emergency private call request to be an unauthorised request for an MCPTT emergency private call.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 [50]) is set to a value of "true", then the MCPTT emergency private call cancellation request shall be considered to be an authorised request for an MCPTT emergency private call cancellation.
In all other cases, the MCPTT emergency private call cancellation request shall be considered to be an unauthorised request for an MCPTT emergency private call cancellation.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 set to a value of "true"; and
2) if the "entry-info" attribute of the <entry> element of the <PrivateEmergencyAlert> element contained within the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of:
a) "UsePreConfigured", and if the <uri-entry> element of the <entry> element of the <PrivateEmergencyAlert> element of the <OnNetwork> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) contains the MCPTT ID of the targeted MCPTT user; or
b) "LocallyDetermined";
then the MCPTT emergency alert request shall be considered to be an authorised request for an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request for an MCPTT emergency alert.
If the MCPTT client receives a request from the MCPTT user to cancel an MCPTT emergency alert to an MCPTT user, and if the <allow-cancel-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 set to a value of "true", then the MCPTT emergency alert cancellation request shall be considered to be an authorised request to cancel an MCPTT emergency alert. In all other cases, it shall be considered to be an unauthorised request to cancel an MCPTT emergency alert.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
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 not already set;
2) shall include in the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP request an <emergency-ind> element set to "true" and set the MCPTT emergency private call state to "MEPC 2: emergency-pc-requested";
3) if the MCPTT user has also requested an MCPTT emergency alert to be sent and this is an authorised request for MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3, shall:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body the <alert-ind> element set to "true" and set the MCPTT private emergency alert state to "MPEA 2: emergency-alert-confirm-pending"; and
b) include in the SIP request the specific location information for MCPTT emergency alert as specified in clause 6.2.9.1;
4) if the MCPTT user has not requested an MCPTT emergency alert to be sent, shall set the <alert-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body to "false"; and
5) if the MCPTT emergency private priority state of this private call is set to a value other than "MEPP 2: in-progress" shall set the MCPTT emergency private priority state to "MEPP 4: confirm-pending".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.3 Resource-Priority header field for MCPTT emergency private calls
|
This clause is referenced from other procedures.
If the MCPTT emergency private call state is set to either "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted" 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, or the MCPTT emergency private priority state of the call is set to "MEPP 2: in-progress", the MCPTT client shall include in the SIP request a Resource-Priority header field populated with the values for an MCPTT emergency private call as specified in clause 6.2.8.1.15.
NOTE: The MCPTT client ideally would not need to maintain knowledge of the in-progress emergency state of the call (as tracked on the MCPTT client by the MCPTT client emergency private state) but can use this knowledge to provide a Resource-Priority header field set to emergency level priority, which starts the infrastructure priority adjustment process sooner than otherwise would be the case.
If this is an authorised request to cancel the MCPTT emergency private call as determined by the procedures of clause 6.2.8.3.1.2, or the MCPTT emergency private priority state of the private call is "MEPP 1: no-emergency" or "MEPP 3: cancel-pending", the MCPTT client shall include in the SIP request a Resource-Priority header field populated with the values for a normal MCPTT private call as specified in clause 6.2.8.1.15.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.4 Receiving a SIP 2xx response to a SIP request for an MCPTT emergency private call
|
This clause is referenced from other procedures.
On receiving a SIP 2xx response to a SIP request for an MCPTT emergency private call and if the MCPTT emergency private call state is set to "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted", the MCPTT client:
1) shall set the MCPTT emergency private priority state of the call to "MEPP 2: in-progress" if it was not already set;
2) shall set the MCPTT emergency private call state to "MEPC 3: emergency-pc-granted"; and
3) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending" and the SIP 2xx response to the SIP request for a priority private call does not contain a Warning header field as specified in clause 4.4 with the warning text containing the mcptt-warn-code set to "149", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.5 Receiving a SIP 4xx response, SIP 5xx response or SIP 6xx response to a SIP request for an MCPTT emergency private call
|
Upon receiving a SIP 4xx response, SIP 5xx response or a SIP 6xx response to a SIP request for an MCPTT emergency private call and if the MCPTT emergency private call state is set to "MEPC 2: emergency-pc-requested" or "MEPC 3: emergency-pc-granted", the MCPTT client:
1) shall set the MCPTT emergency private call state to "MEPC 1: emergency-pc-capable";
2) if the MCPTT emergency private priority state of the private call is "MEPP 4: confirm-pending" shall set the MCPTT emergency private priority state of the private call to "MEPP 1: no-emergency"; and
3) if the sent SIP request for an MCPTT emergency private call contained an application/vnd.3gpp.mcptt-info+xml MIME body with an <alert-ind> element set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert".
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.6 SIP re-INVITE request for cancelling MCPTT emergency private call state
|
This clause is referenced from other procedures.
When the MCPTT emergency private call state is set to "MEPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to "MPEA 1: no-alert", the MCPTT client shall generate a SIP re-INVITE request according to 3GPP TS 24.229 [4] with the clarifications given below.
NOTE 1: This procedure assumes that the MCPTT client in the calling procedure has verified that the MCPTT user has made an authorised request for cancelling MCPTT the in-progress emergency private call state of the call.
The MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false";
2) shall clear the MCPTT emergency state; and
3) shall set MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending".
NOTE 2: This is the case of an MCPTT user who has initiated an MCPTT emergency private call and wants to cancel it.
When the MCPTT emergency private call state is set to "MEPPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to a value other than "MPEA 1: no-alert" and the MCPTT user has indicated only the MCPTT emergency private call should be cancelled, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in clause F.1 with the <emergency-ind> element set to "false"; and
2) shall set the MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending";
NOTE 3: This is the case of an MCPTT user has initiated both an MCPTT emergency private call and an MCPTT emergency alert and wishes to only cancel the MCPTT emergency private call. This leaves the MCPTT emergency state set.
When the MCPTT emergency private call state is set to "MEPC 3: emergency-pc-granted" and the MCPTT emergency alert state is set to a value other than "MPEA 1: no-alert" and the MCPTT user has indicated that the MCPTT emergency alert on the MCPTT private call should be cancelled in addition to the MCPTT emergency private call, the MCPTT client:
1) shall include in the SIP re-INVITE request an application/vnd.3gpp.mcptt-info+xml MIME body as defined in annex F.1 with the <emergency-ind> element set to "false";
2) shall, if this is an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3:
a) include in the application/vnd.3gpp.mcptt-info+xml MIME body an <alert-ind> element set to "false"; and
b) set the MCPTT private emergency alert state to "MPEA 4: emergency-alert-cancel-pending";
3) if this is not an authorised request to cancel an MCPTT emergency alert as determined by the procedures of clause 6.2.8.3.1.3, should indicate to the MCPTT user they are not authorised to cancel the MCPTT emergency alert;
4) shall set the MCPTT emergency private priority state of the MCPTT emergency private call to "MEPP 3: cancel-pending"; and
5) shall clear the MCPTT emergency state.
NOTE 4: This is the case of an MCPTT user that has initiated both an MCPTT emergency private call and an MCPTT emergency alert and wishes to cancel both.
|
e34e50ff54835e88e5e7b14a5e4c1405
|
24.379
|
6.2.8.3.7 Receiving a SIP INFO request in the dialog of a SIP request for a priority private call
|
This clause is referenced from other procedures.
Upon receiving a SIP INFO request within the dialog of the SIP request for a priority private 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 package according to IETF RFC 6086 [64]; and
- with one or more of the <alert-ind>, <imminentperil-ind> and <emergency-ind> elements set in the application/vnd.3gpp.mcptt-info+xml MIME body;
the MCPTT client:
1) if the MCPTT private emergency alert state is set to "MPEA 2: emergency-alert-confirm-pending":
a) if the <alert-ind> element is set to a value of "false", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert"; and
b) if the <alert-ind> element set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated"; and
2) if the MCPTT private emergency alert state is set to "MPEA 4: Emergency-alert-cancel-pending":
a) if the <alert-ind> element is set to a value of "true", shall set the MCPTT private emergency alert state to "MPEA 3: emergency-alert-initiated"; and
b) if the <alert-ind> element is set to a value of "false", shall set the MCPTT private emergency alert state to "MPEA 1: no-alert".
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.