hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.18.1 General
|
The MCPTT service shall support the procedures and related information flows as specified in subclauses 10.13.10 of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.18.2 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.18.3 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19 Ad hoc group call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.1 General
|
This subclause contains procedures for ad hoc group call across a one or more MCPTT systems, and associated functions such as emergency call, Imminent peril call, broadcast call and others.
The ad hoc group calls can use the participants list provided by either an initiator of the call or MCPTT server. The MCPTT server can use the criteria provided by the initiator of the call to determine the participants list along with its own criteria or local policies. The resulting ad hoc group uses the configuration of a separate preconfigured MCPTT group.
NOTE 1: A preconfigured group which is intended only to provide configuration for the ad hoc group is identified by a parameter in the group configuration described in 3GPP TS 23.280 [16].
The preconfigured MCPTT group that provides the configuration is not used for the MCPTT group communication, it only provides configuration for one or more adhoc group calls. The MCPTT group ID of the ad hoc group call is provided by the MCPTT server when the ad hoc group call is originated. In order to establish security context for the end-to-end secured ad hoc group call, the security related information is used from this preconfigured group.
NOTE 2: The configurations defined for the adhoc group call in user profile and service configuration document as described in the Annex A.3 and A.5 is applicable only for single MCPTT system.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2 Information flows
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.1 Ad hoc group call request (MCPTT client – MCPTT server)
|
Table 10.19.2.1-1 describes the information flow ad hoc group call request from the MCPTT client to the MCPTT server.
Table 10.19.2.1-1: Ad hoc group call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID (see NOTE 1)
O
The MCPTT group ID to be associated with the ad hoc group communication
Encryption supported (see NOTE 2)
O
Indicates whether this ad hoc group call supports end-to-end encryption
MCPTT ID list (see NOTE 3, NOTE 6, NOTE 7)
O
MCPTT IDs of the participants being invited for the ad hoc group call
SDP offer
M
Offered Media parameters
Implicit floor request (see NOTE 4)
O
When originating client requests the floor, this element shall be included
Broadcast indicator
(see NOTE 5)
O
Indicates that the ad hoc group call request is for a broadcast ad hoc group call
Imminent peril indicator (see NOTE 5)
O
Indicates that the ad hoc group call request is an MCPTT imminent peril ad hoc group call
Emergency Indicator (see NOTE 5)
O
Indicates that the ad hoc group call request is an MCPTT emergency ad hoc group call
MCPTT ID list (see NOTE 3)
O
List of participants required to acknowledge the ad hoc group call before start of the audio transmission
Location information
O
Location of the calling party.
Criteria for determining the participants (see NOTE 6, NOTE 7)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
Requested priority
O
Application priority level requested for this group call
NOTE 1: If this information element is not included, the MCPTT server assigns an MCPTT ad hoc group ID to be used for the ad hoc group communication. This information element is returned to the calling party to use in the ad hoc group communication. If the request follows an ad hoc group for emergency alert, then this element must be present.
NOTE 2: This information element is present and set to true only if this ad hoc group call is encrypted. When the ad hoc group call is initiated with participants provided by the initiator this acts as an indicator that subsequent requests follow targeting the individual participants and carrying the relevant key material. If this information element is set to false or not present, then this ad hoc group call is unencrypted.
NOTE 3: This element is included only when the originating client sends the list of participants.
NOTE 4: This element is included only when the originating client requests the floor.
NOTE 5: If used, only one of these information elements is present.
NOTE 6: Only one of these information elements is present.
NOTE 7: If the request follows an ad hoc group for emergency alert, then this element is not present.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.2 Ad hoc group call request return (MCPTT server – MCPTT client)
|
Table 10.19.2.2-1 describes the information flow ad hoc group call request return from the MCPTT server to the MCPTT client. This response could be intermediate response to provide the server assigned MCPTT ad hoc group ID.
Table 10.19.2.2-1: Ad hoc group call request return information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ad hoc group ID (see NOTE)
O
The MCPTT group ID to be associated with the ad hoc group call which is either provided by the group call initiator or assigned by the MCPTT server. This information element shall be present if the authorization result is success.
Pre-configured group ID (see NOTE)
O
The preconfigured MCPTT group ID whose group configuration is to be used for the ad hoc group call (e.g. information for end-to-end security).
Authorization result
M
Indicate if authorization is success or failure
NOTE: These IEs are included only when the Authorization Result IE indicates authorization is successful.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.3 Ad hoc group call request (MCPTT server – group host MCPTT server)
|
Table 10.19.2.3-1 describes the information flow ad hoc group call request between the MCPTT server and the group host MCPTT server.
Table 10.19.2.3-1: Ad hoc group call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID to be associated with the ad hoc group call
MCPTT ID list
(see NOTE 1, NOTE 3)
O
MCPTT IDs of the participants being invited for the ad hoc group call
SDP offer
M
Offered Media parameters of MCPTT server
Implicit floor request (see NOTE 4)
O
Indicates that the originating client requests the floor
Broadcast indicator
(see NOTE 2)
O
Indicates that the ad hoc group call request is for a broadcast ad hoc group call
Imminent peril indicator (see NOTE 2)
O
Indicates that the ad hoc group call request is an MCPTT imminent peril ad hoc group call
Emergency Indicator (see NOTE 2)
O
Indicates that the ad hoc group call request is an MCPTT emergency ad hoc group call
Preconfigured MCPTT group ID
O
Group identity whose configuration is to be applied for this ad hoc group call.
Criteria for determining the participants (see NOTE 3)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
Requested priority
O
Application priority level requested for this group call
NOTE 1: This element is included only when the originating client sends the list of participants.
NOTE 2: If used, only one of these information elements is present.
NOTE 3: Only one of these information elements is present.
NOTE 4: This information element shall be included only when the originating client requests the floor.
Editor's Note: It is FFS if the server to server message is needed in a call request or response message.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.4 Ad hoc group call request (MCPTT server – MCPTT client)
|
Table 10.19.2.4-1 describes the information flow ad hoc group call request from the MCPTT server to the MCPTT client.
Table 10.19.2.4-1: Ad hoc group call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The identity of the MCPTT user towards which the request is sent
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID to be associated with the ad hoc group call
SDP offer
M
Offered Media parameters of MCPTT server
Broadcast indicator
(see NOTE)
O
Indicates that the ad hoc group call request is for a broadcast ad hoc group call
Imminent peril indicator (see NOTE)
O
Indicates that the ad hoc group call request is an MCPTT imminent peril ad hoc group call
Emergency Indicator (see NOTE)
O
Indicates that the ad hoc group call request is an MCPTT emergency ad hoc group call
Preconfigured MCPTT group ID
O
Group identity whose configuration is to be applied for this ad hoc group call.
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
NOTE: If used, only one of these information elements is present.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.5 Ad hoc group call response (MCPTT server – MCPTT client)
|
Table 10.19.2.5-1 describes the information flow ad hoc group call response from the MCPTT server to the MCPTT client.
Table 10.19.2.5-1: Ad hoc group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the group call request (success or failure)
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.6 Ad hoc group call response (MCPTT server – MCPTT server)
|
Table 10.19.2.6-1 describes the information flow ad hoc group call response between the MCPTT servers.
Table 10.19.2.6-1: Ad hoc group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT user
Functional alias
O
The functional alias of the target MCPTT user
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the ad hoc group call request (success or failure)
Editor's Note: It is FFS if the server to server message is needed in a call request or response message.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.7 Ad hoc group call response (MCPTT client – MCPTT server)
|
Table 10.19.2.7-1 describes the information flow ad hoc group call response from the MCPTT client to the MCPTT server.
Table 10.19.2.7-1: Ad hoc group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT user
Functional alias
O
The functional alias of the target MCPTT user
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the ad hoc group call request (success or failure)
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.8 Ad hoc group call release request (MCPTT server – MCPTT client)
|
Table 10.19.2.8-1 describes the information flow ad hoc group call release request from the MCPTT server to the MCPTT client.
Table 10.19.2.8-1: Ad hoc group call release request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant
Functional alias
O
The functional alias of the ad hoc group call participant
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call on which call is released
10.19.2.8a Ad hoc group call release request (MCPTT client – MCPTT server)
Table 10.19.2.8a-1 describes the information flow ad hoc group call release request from the MCPTT client to the MCPTT server.
Table 10.19.2.8a-1: Ad hoc group call release request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the user authorized to release the ad hoc group call
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call on which call is released
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.9 Ad hoc group call release response (MCPTT client – MCPTT server)
|
Table 10.19.2.9-1 describes the information flow ad hoc group call release response from the MCPTT client to the MCPTT server.
Table 10.19.2.9-1: Ad hoc group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant
Functional alias
O
The functional alias of the ad hoc group call participant
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call that is released
10.19.2.9a Ad hoc group call release response (MCPTT server – MCPTT client)
Table 10.19.2.9a-1 describes the information flow ad hoc group call release response from the MCPTT server to the MCPTT client.
Table 10.19.2.9a-1: Ad hoc group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the user authorized to release the ad hoc group call
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call that is released
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.10 Ad hoc group call notify (MCPTT server – MCPTT client)
|
Table 10.19.2.10-1 describes the information flow ad hoc group call notify from MCPTT server to MCPTT client.
Table 10.19.2.10-1: Ad hoc group call notify
Information element
Status
Description
MCPTT ID
M
The MCPTT ID of ad hoc group call participant
Functional alias
O
The associated functional alias of the MCPTT user of the ad hoc group call participant
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group call
MCPTT ID list
O
The list of the invited MCPTT users who did not acknowledge the ad hoc group call request within a configured time or the list of the invited MCPTT users who acknowledged the ad hoc group call request and joined or the list of the MCPTT users who joined or left the ongoing MCPTT ad hoc group call.
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.11 Modify ad hoc group call participants request (MCPTT client – MCPTT server)
|
Table 10.19.2.11-1 describes the information flow Modify ad hoc group call participants request from the MCPTT client to the MCPTT server.
Table 10.19.2.11-1: Modify ad hoc group call participants request
Information element
Status
Description
MCPTT ID
M
The MCPTT ID of the requesting MCPTT user who is authorized to modify the ad hoc group call participants
Functional alias
O
The functional alias of the requesting MCPTT user who is authorized to modify the ad hoc group call participants
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants needs to be modified
MCPTT ID list (see NOTE)
O
List of additional MCPTT users to be added to the on-going ad hoc group call
MCPTT ID list (see NOTE)
O
List of MCPTT users to be removed from the on-going ad hoc group call
NOTE: Either one or both of these information elements is present
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.12 Modify ad hoc group call participants response (MCPTT server – MCPTT client)
|
Table 10.19.2.12-1 describes the information flow Modify ad hoc group call participants response from the MCPTT server to the MCPTT client.
Table 10.19.2.12-1: Modify Ad hoc group call participants response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requesting MCPTT user who is authorized to modify the ad hoc group call participants
Functional alias
O
The functional alias of the requesting MCPTT user who is authorized to modify the ad hoc group call participants
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
MCPTT ID list
O
List of MCPTT users who are not allowed to be added to the on-going ad hoc group call. This list is provided if the operation is partially success.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.13 Ad hoc group call leave request (MCPTT server – MCPTT client)
|
Table 10.19.2.13-1 describes the information flow ad hoc group call leave request from the MCPTT server to the MCPTT client.
Table 10.19.2.13-1: Ad hoc group call leave request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant leaving the call
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call on which call is on-going
Reason to leave
O
Carries the reason of why the MCPTT client is being asked to leave the ongoing ad hoc group call
10.19.2.13a Ad hoc group call leave request (MCPTT client – MCPTT server)
Table 10.19.2.13a-1 describes the information flow ad hoc group call leave request from the MCPTT client to the MCPTT server.
Table 10.19.2.13a-1: Ad hoc group call leave request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant leaving the call
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call on which call is on-going
Reason to leave
M
Carries the reason of why the MCPTT client is leaving ongoing ad hoc group call (e.g. Due to migration).
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.14 Ad hoc group call leave response (MCPTT client – MCPTT server)
|
Table 10.19.2.14-1 describes the information flow Ad hoc group call leave response from the MCPTT client to the MCPTT server.
Table 10.19.2.14-1: Ad hoc group call leave response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant leaving the call
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call on which call is on-going
10.19.2.14a Ad hoc group call leave response (MCPTT server – MCPTT client)
Table 10.19.2.14a-1 describes the information flow Ad hoc group call leave response from the MCPTT server to the MCPTT client.
Table 10.19.2.14a-1: Ad hoc group call leave response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant leaving the call
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call on which call is on-going
Result
M
Result of the ad hoc group call leave request – success or failure.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.15 Ad hoc group call add user notification (MCPTT server – MCPTT server)
|
Table 10.19.2.15 -1 describes the information flow Ad hoc group call add user notification from one MCPTT server to another MCPTT server. This notification is to provide the list of MCPTT IDs meeting the criteria specified in the ad hoc group communication get userlist request from one MCPTT server to another MCPTT server.
Table 10.19.2.15-1: Ad hoc group call add user notification information elements
Information Element
Status
Description
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group communication
MCPTT ID list
M
List of MCPTT IDs meeting the criteria specified in the ad hoc group communication get userlist
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.16 Ad hoc group call remove user notification (MCPTT server – MCPTT server)
|
Table 10.19.2.16-1 describes the information flow Ad hoc group call remove user notification from one MCPTT server to another MCPTT server. This notification is to provide the list of MCPTT IDs no longer meeting the criteria specified in the ad hoc group communication get userlist request from one MCPTT server to another MCPTT server.
Table 10.19.2.16-1: Ad hoc group call remove user notification information elements
Information Element
Status
Description
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group communication
MCPTT ID list
M
List of MCPTT IDs no longer meeting the criteria specified in the ad hoc group communication get userlist
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.17 Ad hoc group call release notification (MCPTT server – MCPTT server)
|
Table 10.19.17 -1 describes the information flow Ad hoc group call release notification from one MCPTT server to another MCPTT server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCPTT server is having the criteria specified in the ad hoc group communication get userlist request.
Table 10.19.17-1: Ad hoc group call release notification information elements
Information Element
Status
Description
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group communication
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.18 Ad hoc group call get userlist (MCPTT server – MCPTT server)
|
Table 10.19.2.18-1 describes the information flow ad hoc group call get userlist between MCPTT servers.
Table 10.19.2.18-1: Ad hoc group call get userlist
Information element
Status
Description
MCPTT ad hoc group ID
M
The associated MCPTT group ID of the ad hoc group call
Criteria for determining the participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.19 Ad hoc group call get userlist response (MCPTT server – MCPTT server)
|
Table 10.19.2.19-1 describes the information flow ad hoc group call get userlist response between MCPTT servers.
Table 10.19.2.19-1: Ad hoc group call get userlist response
Information element
Status
Description
MCPTT ad hoc group ID
M
The associated MCPTT group ID of the ad hoc group call
MCPTT ID list
M
List of MCPTT IDs meeting the criteria specified in the ad hoc group call get userlist
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.20 Modify ad hoc group call criteria request (MCPTT client – MCPTT server)
|
Table 10.19.2.20-1 describes the information flow Modify ad hoc group call criteria request from the MCPTT client to the MCPTT server.
Table 10.19.2.20-1: Modify ad hoc group call criteria request
Information element
Status
Description
MCPTT ID
M
The MCPTT ID of the requesting MCPTT user who is authorized to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MCPTT user who is authorized to modify the ad hoc group call criteria
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants list needs to be modified
Criteria to determine the list of participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
10.19.2.20a Modify ad hoc group call criteria request (MCPTT server – MCPTT server)
Table 10.19.2.20a-1 describes the information flow Modify ad hoc group call criteria request from the MCPTT server to the MCPTT server.
Table 10.19.2.20a-1: Modify ad hoc group call criteria request
Information element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants list needs to be modified
Criteria to determine the list of participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.2.21 Modify ad hoc group call criteria response (MCPTT server – MCPTT client)
|
Table 10.19.2.21-1 describes the information flow Modify ad hoc group call criteria response from the MCPTT server to the MCPTT client.
Table 10.19.2.21-1: Modify Ad hoc group call criteria response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requesting MCPTT user who is authorized to modify the ad hoc group call criteria
Functional alias
O
The functional alias of the requesting MCPTT user who is authorized to modify the ad hoc group call criteria
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants list needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
10.19.2.21a Modify ad hoc group call criteria response (MCPTT server – MCPTT server)
Table 10.19.2.21a-1 describes the information flow Modify ad hoc group call criteria response from the MCPTT server to the MCPTT server.
Table 10.19.2.21a-1: Modify Ad hoc group call criteria response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID of ad hoc group call whose participants list needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3 Procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1 Ad hoc group call procedures in single MCPTT system
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.1 Ad hoc group call setup
|
Figure 10.19.3.1.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user.
Pre-conditions:
1. The authorized user at MCPTT client 1 wants to invite MCPTT users at MCPTT client 2, MCPTT client 3 and MCPTT client 4 for the ad hoc group call and is aware of the MCPTT IDs of the participants or to invite the ad hoc group member if the ad hoc group call follows an ad hoc group emergency alert, the MCPTT client 1 is aware of the ad hoc group ID.
2. Number of participants being invited for the ad hoc group call is within the limit.
3. End-to-End encryption is supported for this ad hoc group call.
4. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCPTT client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
NOTE 1: Selection of MCPTT IDs of the participants can be manual or from the user profile configuration data or by any other means. This is left for the implementation.
Figure 10.19.3.1.1-1: Ad hoc group call setup
1. User at MCPTT client 1 would like to initiate an ad hoc group call. The MCPTT client 1 initiates the ad hoc group call by sending the ad hoc group call request containing the list of participants or an ad hoc group ID from an ad hoc group emergency alert to the MCPTT server. Encryption supported information element shall be set to true since end-to-end encryption is supported. An SDP offer containing the MCPTT client media parameters is included. If there is a floor request to transmit, then the ad hoc group call request contains an indication of an implicit floor request. If the MCPTT user of MCPTT client 1 has selected a functional alias, then the ad hoc group call request contains that functional alias. If the ad hoc group call request contains an implicit floor request it may also include location information.
If the MCPTT user at MCPTT client 1 initiates an MCPTT emergency ad hoc group call or the MCPTT emergency state is already set for the MCPTT client 1 (due to a previously triggered MCPTT emergency alert):
i. the MCPTT ad hoc group call request shall contain an emergency indicator;
ii. if the MCPTT emergency state is not set already, MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state of MCPTT client 1 is retained until explicitly cancelled by the user of MCPTT client 1.
2. If the ad hoc group call is supported, the MCPTT server verifies whether the user at MCPTT client 1 is authorized to initiate an ad hoc group call. If not authorized, the MCPTT server rejects the ad hoc group call request as specified in the step 3. The MCPTT server accepts the ad hoc group call request if the ad hoc group call is supported and authorized. If authorised, it validates whether the number of invited participants is within the configured limit before proceeding with the call setup.
If functional alias is present, the MCPTT server checks whether the provided functional alias allowed to be used and has been activated for the user.
If location information was included in the ad hoc group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
If an emergency indicator is present in the received MCPTT ad hoc group call request, the MCPTT ad hoc group is considered to be in the in-progress emergency state until this ad hoc group call is terminated; and
If an imminent peril indicator is present in the received MCPTT ad hoc group call request, the MCPTT ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group call is terminated.
If the MC service users' information received in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCPTT server forms the ad hoc group by using MCPTT users' information received in step 1, determines the preconfigured group to be used for the configuration of the ad hoc group and assigns a MC service group ID for the newly formed ad hoc group. If no MC service ad hoc group ID was included in the ad hoc group call request of step 1, or if the provided MC service ad hoc group ID is not accepted by the MC service server, the MCPTT server assigns a MCPTT group ID for the newly formed ad hoc group.
The MCPTT server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
3. The MCPTT server shall send the ad hoc group call request return message to MCPTT client 1 containing the below:
i. The MCPTT ad hoc group ID either generated by the MCPTT server or provided by the MCPTT client 1 if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group call is authorized);
ii. The group ID of the pre-configured group to be used for the ad hoc group call (only included when the ad hoc group call is authorized); and
iii. Result of whether the ad hoc group call is authorized or not.
If the ad hoc group call request is not authorized, the MCPTT server and MCPTT client 1 shall not proceed with the rest of the steps.
4a-4c. The MCPTT server sends the ad hoc group call requests towards the MCPTT clients of the invited users based on step 1. While sending the ad hoc group call requests, the MCPTT server shall remove the information elements that are not required to be conveyed to the target MCPTT clients (e.g. MCPTT ID list of the users who are required to acknowledge)
5a-5c. The receiving MCPTT clients notify their corresponding MCPTT user about the incoming ad hoc group call request with the information of the MCPTT group ID for the ad hoc group.
6a-6c. The receiving MCPTT clients may accept or reject the ad hoc group call requests and send ad hoc group call responses to the MCPTT server. The response may also contain a functional alias of the responding MCPTT user, which is verified (valid and activated for the user) by the MCPTT server.
NOTE 2: For emergency ad hoc group calls the receiving MCPTT client shall always accept the request.
7. The MCPTT server sends the ad hoc group call response to MCPTT client 1 through the signalling path to inform about successful call establishment.
NOTE 3: Steps 5 to step 7 can start to occur before all of step 4 is completed since the MCPTT server do not require to wait for the previous ad hoc group call request to complete before sending the ad hoc group request to another participant.
8. If the initiating MCPTT user requires the acknowledgement from the invited MCPTT users, and the required MCPTT users do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCPTT server may proceed with or abandon the call and then notify the initiating MCPTT user that the acknowledgements did not include all required members according to ad hoc group call policy from the user profile configuration. The MCPTT server may notify the initiating MCPTT user of all MCPTT users who did not acknowledge the ad hoc group call request within the configured time. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call.
9. MCPTT client 1, MCPTT client 2, MCPTT client 3 and MCPTT client 4 establish media plane and floor control resources.
NOTE 4: Step 9 can occur any time following step 7 if the conditions to proceed with the call are met.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.2 Release ad hoc group call
|
The procedure focuses on the case where the MCPTT server releases an ongoing MCPTT ad hoc group call for all the participants of that ad hoc group call, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving.
Figure 10.19.3.1.2-1 below illustrates the signalling control plane procedure for the MCPTT server initiating termination an ongoing ad hoc group call.
Figure 10.19.3.1.2-1: Release ad hoc group call by the MCPTT server
1. It is assumed that MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing ad hoc group call.
2. MCPTT server would like to release the MCPTT ad hoc group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving.
3. MCPTT server identifies the participants of the ongoing ad hoc group call and generates ad hoc group call release request to release ongoing session. The MCPTT server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group call is an emergency or imminent peril call respectively.
4. MCPTT server sends ad hoc group call release request via SIP core towards each participant of the ongoing ad hoc group call.
5. MCPTT users are notified about the release of the ad hoc group call.
6. MCPTT client(s) receiving ad hoc group call release request, acknowledge towards the MCPTT server by sending an ad hoc group call release response.
NOTE: If the initiator of the ad hoc group call does not supply the participants list, the MCPTT client(s) may choose to store the list of participants for easy re-initiation of another ad hoc group call with the same participants.
7. MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group, otherwise if the ad hoc group call follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further calls over the same ad hoc group are possible).
10.19.3.1.2a Release ad hoc group call by an authorized user
The procedure focuses on the case where an authorized user releases an ongoing MCPTT ad hoc group call for all the participants of that ad hoc group call.
Figure 10.19.3.1.2a-1 below illustrates the signalling control plane procedure for the MCPTT client initiating termination of an ongoing ad hoc group call.
Figure 10.19.3.1.2a-1: Release ad hoc group call by an authorized user
1. It is assumed that MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing ad hoc group call.
2. The authorized MCPTT user on MCPTT client 1 would like to release the MCPTT ad hoc group call which is ongoing and sends an ad hoc group call release request to the MCPTT server.
3. MCPTT server checks whether the MCPTT user on MCPTT client 1 is authorized to release the ad hoc group call and generates ad hoc group call release request to release ongoing session. The MCPTT server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group call is an emergency or imminent peril call respectively.
4. The MCPTT server sends ad hoc group call release request via SIP core towards MCPTT client 2 and MCPTT client 3.
5. MCPTT users on MCPTT client 2 and MCPTT client 3 are notified about the release of the ad hoc group call.
6. MCPTT client 2 and MCPTT client 3 acknowledge the ad hoc group call release request towards the MCPTT server by sending an ad hoc group call release response.
7. The MCPTT server sends ad hoc group call release response to MCPTT client 1.
8. MCPTT user on MCPTT client 1 is notified about the release of the ad hoc group call.
9. MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group, otherwise if the ad hoc group call follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further calls over the same ad hoc group are possible).
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.3 Ad hoc group call setup with MCPTT server determining the participants lists
|
Figure 10.19.3.1.3-1 below illustrates the ad hoc group call setup procedure initiated by the MCPTT user and MCPTT client 1 wherein the list of participants is determined by the MCPTT server based on the citeria received from the MCPTT client.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initate ad hoc group call.
2. The MCPTT user at MCPTT client 1 wants to invite MCPTT users who are satisying certain criteria for the ad hoc group call.
Figure 10.19.3.1.3-1: Ad hoc group call participants determined by MCPTT server
1. User at MCPTT client 1 would like to initiate an ad hoc group call in-order to invite the participants satisfying specific criteria. The MCPTT client 1 initiates the ad hoc group call by sending the ad hoc group call request containing the details of the criteria to be applied by the MCPTT server for determining the participant list. If end-to-end encryption is supported, the Encryption supported information element shall be set to true and pre-configured MCPTT group whose configuration is to be applied is included. An SDP offer containing the MCPTT client media parameters is included. If there is a floor request to transmit, then the ad hoc group call request contains an indication of an implicit floor request. If the MCPTT user of MCPTT client 1 has selected a functional alias, then the ad hoc group call request contains that functional alias. If the ad hoc group call request contains an implicit floor request it may also include location information.
If the MCPTT user at MCPTT client 1 initiates an MCPTT emergency ad hoc group call or the MCPTT emergency state is already set for the MCPTT client 1 (due to a previously triggered MCPTT emergency alert):
i. the MCPTT ad hoc group call request shall contain an emergency indicator;
ii. if the MCPTT emergency state is not set already, MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state of MCPTT client 1 is retained until explicitly cancelled by the user of MCPTT client 1.
2. If the ad hoc group call is supported, the MCPTT server verifies whether the user at MCPTT client 1 is authorized to initiate an ad hoc group call. If not authorized, the MCPTT server rejects the ad hoc group call request as specified in the step 3. The MCPTT server accepts the ad hoc group call request if the ad hoc group call is supported and authorized.
If functional alias is present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user.
If location information was included in the ad hoc group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
If an emergency indicator is present in the received MCPTT ad hoc group call request, the MCPTT ad hoc group is considered to be in the in-progress emergency state until this ad hoc group call is terminated; and
If an imminent peril indicator is present in the received MCPTT ad hoc group call request, the MCPTT ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group call is terminated.
If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCPTT server forms the ad hoc group by using received information, and determines the preconfigured group to be used for the configuration of the ad hoc group. The MCPTT server assigns a MCPTT group ID for the newly formed ad hoc group. Further, the ad hoc group participants are included to ad hoc group once determined as specified in the step 4.
3. The MCPTT server shall send the ad hoc group call request return message to MCPTT client 1 containing the below:
i. The MCPTT ad hoc group ID, either generated by the MCPTT server, if not included in the ad hoc group call request of step 1, or if the provided MCPTT ad hoc group ID is not accepted by the MCPTT server, or provided by the MCVideo client 1 if the ad hoc group ID is from an ad hoc group emergency alert;
ii. The group ID of the pre-configured group to be used for the ad hoc group communication (only included when the ad hoc group data session is authorized); and
iii. Result of whether the ad hoc group call is authorized or not
If the ad hoc group call request is not authorized, the MCPTT server and MCPTT client 1 shall not proceed with the rest of the steps.
4. The MCPTT server determines the list of participants to be invited for the ad hoc group call based on the information present in the information element Criteria for determining the participants. This information element could carry either criteria or indicator identifying pre-defined criteria or a combination of both. Depending on the criteria provided and based on local policy, the MCPTT server may modify the content of the criteria received in step 1 to determine the list of participants.
NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how the MCPTT server determines the list of participants are left to implementation.
5. The MCPTT server sends the ad hoc group call requests towards the MCPTT clients 2 and 3. While sending the ad hoc group call requests, the MCPTT server shall remove the information elements that are not required to be conveyed to the target MCPTT clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCPTT server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
6. The receiving MCPTT clients notify their corresponding MCPTT user about the incoming ad hoc group call request with the information of the MCPTT group ID for the ad hoc group.
7. The receiving MCPTT clients may accept or reject the ad hoc group call requests and send ad hoc group call responses to the MCPTT server. The response may also contain a functional alias of the responding MCPTT user, which is verified (valid and activated for the user) by the MCPTT server.
NOTE 2: For emergency ad hoc group calls the receiving MCPTT client shall always accept the request.
8. The MCPTT server sends the ad hoc group call response to MCPTT client 1 through the signalling path to inform about successful call establishment. The ad hoc group call response contains the call resulting criteria used by the MCPTT server from step 4 to determine the list of participants to be invited.
9. The MCPTT server may notify the initiating MCPTT user of all MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call. The authorized users (not shown in figure), who are configured to receive the participants information of ad hoc group call, are notified to receive the MCPTT IDs of the MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call, when the MCPTT users joins late or leave the MCPTT ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCPTT server from step 4 to determine the list of participants to be invited.
10. MCPTT client 1, MCPTT client 2 and MCPTT client 3 establish media plane and floor control resources.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.4 Modification of ad hoc group call participants by an authorized user
|
Figure 10.19.3.1.4-1 below illustrates the modification of ad hoc group call participants procedure by an authorized user.
Pre-conditions:
1. An ad hoc group call which is setup with participants list provided by the initiating MCPTT user as described in clause 10.19.3.1.1 or based on the criteria provided by the initiating MCPTT user as described in clause 10.19.3.1.3 is already in progress.
2. The participants of the MCPTT ad hoc group call belong to the single MCPTT system.
3. The MCPTT users on MCPTT client 1, MCPTT client 3 to MCPTT client n are on an ongoing ad hoc group call.
4. The MCPTT user at MCPTT client 1 determines to remove the user of MCPTT client 3 from the ad hoc group call and add user of MCPTT client 2 into the on-going ad hoc group call.
Figure 10.19.3.1.4-1: Modification of ad hoc group call participants by an authorized user
1. The MCPTT user at the MCPTT client 1 is authorized and requests to modify ad hoc group call participants. The MCPTT client 1 sends the modify ad hoc group call participants request to the MCPTT server in order to remove MCPTT client 3 from the ongoing ad hoc group call and add MCPTT client 2 into it.
2. The MCPTT server verifies whether the MCPTT client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group call regardless of the original group call setup parameters. When the group participants were initially determined by the MCPTT server with criteria and MCPTT users are to be removed, the MCPTT server removes MCPTT clients and marks them so that the MCPTT server will not add them back to the ad hoc group call based on the criteria. Participants to be added shall be marked and kept in the ad hoc group call and shall not be removed by the MCPTT server even if they do not meet the call criteria.
NOTE 1: In the above case participants being removed can be added back and the participants being added can be removed by the authorized user via the modify ad hoc group call participants request.
3. The MCPTT server sends modify ad hoc group call participants response to the MCPTT client 1.
4. The MCPTT server sends the ad hoc group call leave request to the MCPTT client 3 in order to remove it from the on-going ad hoc group call.
5. The MCPTT client 3 notifies the user of the ad hoc group call leave request.
6. The MCPTT client 3 sends the ad hoc group call leave response to the MCPTT server.
7. The MCPTT server sends the ad hoc group call request towards MCPTT client 2.
NOTE 2: Steps 7 to 9 can occur at any time following step 3.
8. The receiving MCPTT client 2 notifies the user about the incoming ad hoc group call.
9. The MCPTT client 2 accepts the ad hoc group call request and send ad hoc group call responses to the MCPTT server. The response may also contain a functional alias of the responding MCPTT user, which is verified (valid and activated for the user) by the MCPTT server. The MCPTT server considers the MCPTT user as implicitly affiliated to the ad hoc group.
10. The MCPTT server may notify the initiating MCPTT user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the ad hoc group call.
11. The MCPTT server may notify the participants about the change in the participants of on-going ad hoc group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.5 Modification of ad hoc group call participants by the MCPTT server
|
Figure 10.19.3.1.5-1 below illustrates the modification of ad hoc group call participants procedure by the MCPTT server.
Pre-conditions:
1. The MCPTT client 1 is the initiator of the ad hoc group call.
2. MCPTT server determined the participants for the ad hoc group call based on the criteria specified by the MCPTT client 1 while initiating the ad hoc group call.
3. MCPTT server continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group call.
4. The MCPTT server detects that the MCPTT client 5 satisfies the criteria and MCPTT client 4 stops to meet the criteria specified by the MCPTT client 1.
Figure 10.19.3.1.5-1: Modification of ad hoc group call participants by the MCPTT server
1. The ad hoc group call is established and on-going with the participants MCPTT client 1, MCPTT client 2, MCPTT client 3 and MCPTT client 4. The participants list is determined by the MCPTT server based on the criteria specified by the MCPTT client 1 while initiating the call
2. The MCPTT server detects that the MCPTT client 5 satisfies the criteria specified by the MCPTT client 1 and checks whether it has been previously removed by an authorized user as described in clause 10.19.3.1.4. If MCPTT client 5 has already been removed by an authorized user, the MCPTT server does not add the MCPTT client 5 back to the ad hoc group call and it skips step 3 to step 6. If MCPTT client 5has not been already removed by an authorized user, the procedure continues with step 3..
3. The MCPTT server sends the ad hoc group call request to the MCPTT client 5.
4. The MCPTT client 5 notifies the user about the incoming ad hoc group call.
5. The MCPTT client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCPTT server.
6. The on-going ad hoc group call is updated by adding MCPTT client 5 which satisfies the criteria specified by the MCPTT client 1.
7. The MCPTT server detects that the MCPTT client 4 is no more satisfying the criteria to be the participant of the ad hoc group call and checks whether it has been previously added by an authorized user as described clause 10.19.3.1.4. If MCPTT client 4 has already been added by an authorized user, the MCPTT server does not remove it from the ad hoc group call and skips step 8 to step 11. If MCPTT client 4 has not been already added by an authorized user, the procedure continues with step 8.
8. The MCPTT server sends the ad hoc group call leave request to the MCPTT client 4 and removes it from the on-going ad hoc group call.
9. The MCPTT client 4 notifies the user of the ad hoc group call leave request.
10. The MCPTT client 4 sends the ad hoc group call leave response to the MCPTT server.
11. The on-going ad hoc group call is updated by removing MCPTT client 4, which no more satisfies the criteria specified by the MCPTT client 1.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.1.6 Modification of ad hoc group call criteria by an authorized user
|
Figure 10.19.3.1.6-1 below illustrates the modification of ad hoc group call criteria procedure by an authorized user.
Pre-conditions:
1. The MCPTT user at the MCPTT client 1 is authorized to modify the criteria.
2. Both the MCPTT server and the MCPTT client 1 are aware of the criteria related to the ongoing ad hoc group call.
Figure 10.19.3.1.6-1: Modification of ad hoc group call criteria by the authorized user
1. The MCPTT user at the MCPTT client 1 is authorized and requests to modify the criteria for determining the list of participants. The MCPTT client 1 sends the modify ad hoc group call criteria request to the MCPTT server which contains an updated criteria to determine the list of participants.
2. The MCPTT server verifies whether the MCPTT client 1 is authorized to modify the criteria which determines the list of participants during on-going ad hoc group voice communication. The MCPTT server determines the list of ad hoc group call participants based on the criteria provided and the added/removed participant by the authorized user as marked in clause 10.9.3.1.4.
If MCPTT client 3 satisfies the new criteria to be removed and
- has been already added by an authorized user, the MCPTT server does not remove it from the call and skips the step 4 to step 6.
- has not been already added by an authorized user, the procedure continues with step 4.
If MCPTT client 2 satisfies the new criteria to be added and
- has been previously removed by an authorized user, the MCPTT server does not add it back to the call and skips the step 7 to step 9.
- has not been already removed by an authorized user, the procedure continues with step 4.
Depending on the criteria provided and based on local policy, the MCPTT server may modify the content of the criteria received in step 1 to determine the list of participants.
3. The MCPTT server sends modify ad hoc group call criteria response containing the call resulting criteria used by the MCPTT server to determine the list of participants to be invited to MCPTT client 1.
4. The MCPTT server sends the ad hoc group call leave request to the MCPTT client 3 to remove it from the on-going ad hoc group call.
5. The MCPTT client 3 notifies the user of the ad hoc group call leave request.
6. The MCPTT client 3 sends the ad hoc group call leave response to the MCPTT server.
7. The MCPTT server sends the ad hoc group call request towards MCPTT client 2.
NOTE 1: Steps 7 to 9 can occur at any time following step 3.
8. The receiving MCPTT client 2 notifies the user about the incoming ad hoc group call.
9. The MCPTT client 2 accepts the ad hoc group call request and send ad hoc group call responses to the MCPTT server. The response may also contain a functional alias of the responding MCPTT user, which is verified (valid and activated for the user) by the MCPTT server. The MCPTT server considers the MCPTT user as implicitly affiliated to the ad hoc group.
10. The MCPTT server may notify the initiating MCPTT user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
11. The MCPTT server may notify the participants about the change in the participants list of on-going ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
The MCPTT server continuously checks whether other MCPTT clients meet or if participating MCPTT clients no longer meet the criteria for the ad hoc group emergency call.
NOTE 2: If the ad hoc group call is associated with an ad hoc group emergency alert and the change of criteria caused the modification of ad hoc group call participant list then the ongoing ad hoc group emergency alert is modified accordingly.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2 Ad hoc group call involving multiple MC systems
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.1 Procedure for ad hoc group call setup – Participants list provided by the Initiator
|
Figure 10.19.3.2.1-1 illustrates the procedure for ad hoc group call setup procedure initiated by an authorized user wherein either a list of participants or an ad hoc group ID from an ad hoc group emergency alert is provided by the authorised user and the determined MCPTT users are from multiple MCPTT systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system shares their users' information to the primary MC system.
2. The authorized MCPTT user/dispatcher belongs to the primary MC system.
3. The MCPTT server of the primary MC system is where the authorized MCPTT user/dispatcher controls the ad hoc group.
4. Some users of the ad hoc group belong to partner MC systems.
5. The preconfigured group identity and preconfigured group configuration to be used for an ad hoc group have been preconfigured in the MCPTT client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
6. If an ad hoc group ID from an ad hoc group emergency alert is used to invite the ad hoc group members, MCPTT client is aware of the ad hoc group ID.
Figure 10.19.3.2.1-1: Ad hoc group call setup
1. The MCPTT client of the authorized user initiates an ad hoc group call with multiple users from primary and partner MC systems. An ad hoc group call request message with the information of the MCPTT IDs or an ad hoc group ID if the ad hoc group call follows an ad hoc group emergency alert is routed to the MCPTT server of the primary MC system.
2. If the ad hoc group call is supported, the MCPTT server of the primary MC system verifies whether the user at of MCPTT client is authorized to initiate an ad hoc group call. If not authorized, the MCPTT server of the primary MC system rejects the ad hoc group call request as specified in the step 3. If the the MC service users' information received in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCPTT server of the primary MC system forms the ad hoc group by using MCPTT users' information received in step 1, determines the preconfigured group to be used for the configuration and assigns an MCPTT group ID for the newly formed ad hoc group. If no MC service ad hoc group ID was included in the ad hoc group call request of step 1, or if the provided MC service ad hoc group ID is not accepted by the MC service server, the MCPTT server assigns a MCPTT group ID for the newly formed ad hoc group.
The MCPTT server identifies the appropriate MCPTT server responsible for the MCPTT users of the ad hoc group. The MCPTT server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
NOTE 1: The ad hoc group information including the MCPTT group ID and the list of users is held in dynamic data in the MCPTT server.
3. The MCPTT server shall send the ad hoc group call request return message to the MCPTT client containing the below:
i. The MCPTT ad hoc group ID either generated by the MCPTT server or provided by the MCPTT client if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group call is authorized);
ii. The group ID of the pre-configured group to be used for the ad hoc group call (only included when the ad hoc group call is authorized); and
iii. Result of whether the ad hoc group call is authorized or not.
If the ad hoc group call request is not authorized, the MCPTT server and MCPTT client shall not proceed with the rest of the steps.
4. The MCPTT server of the primary MC system sends the ad hoc group call requests towards the MCPTT clients of the invited users belonging to the primary MC system based on step 1. While sending the ad hoc group call requests, the MCPTT server of the primary MC system shall remove the information elements that are not required to be conveyed to the target MCPTT clients (e.g. MCPTT ID list of the users who are required to acknowledge).
5. The receiving MCPTT clients notify their corresponding MCPTT users about the incoming ad hoc group call request with the information of the MCPTT group ID for the ad hoc group, and may accept or reject the call and respond with an adhoc group call response.
6. The primary MCPTT server further initiates an ad hoc group call request message to the MCPTT users of the partner MC system. The ad hoc group call request message is routed to the MCPTT users via the MCPTT server of the partner MC system.
7. The receiving MCPTT clients notify their corresponding MCPTT users about the incoming ad hoc group call request with the information of the MCPTT group ID for the ad hoc group. The MCPTT users upon receipt of the invitation may accept or reject the call, and respond with the ad hoc group call response. The ad hoc group call response message is routed to the MCPTT server of the primary MC system via the MCPTT server of the partner MC system.
8. The MCPTT server of the primary MC system provides an ad hoc group call response message to the MCPTT client of the authorized MCPTT user upon receiving response to the corresponding ad hoc group call request in step 1. The ad hoc group call response will consist of the success or failure result and/or detailed reason information in case of failure.
NOTE 2: The ad hoc group call response message is triggered depending on the conditions to proceed with the call.
9. Upon successful ad hoc group call setup, a group call is established amongst the multiple group members from primary and partner MC systems. The media plane and floor control resources are established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.2 Procedure for ad hoc group call release by MCPTT server – Participants list provided by the Initiator
|
This procedure focuses on the case where an MCPTT server initiates the termination of an ongoing MCPTT ad hoc group call for all the participants of that group call, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present.
Procedures in figure 10.19.3.2.2-1 are the signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT ad hoc group call.
Pre-condition:
- The MCPTT client 1 and MCPTT client 2 belong to primary MC system. The MCPTT client 3 belongs to partner MC system.
Figure 10.19.3.2.2-1: Ad hoc group call release
1. The MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing ad hoc group call (e.g. as a result of ad hoc group call setup as specified in clause 10.19.3.2.x).
2. The MCPTT server would like to release the ad hoc group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present.
3. The MCPTT server identifies the participants of the ongoing ad hoc group call and generates ad hoc group call release request to release ongoing session.
4. The MCPTT server sends a ad hoc group call release request via SIP core towards each participant of the ongoing group call. If the participants belong to partner MC system, then ad hoc group call release request is routed to the MCPTT clients of the partner MC system via the partner MCPTT server.
5. The MCPTT users are notified about the release of the ad hoc group call.
6. The MCPTT client(s) receiving ad hoc group call release request, send acknowledgement towards the MCPTT server by sending a ad hoc group call release response.
7. The MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated. The MCPTT servers remove the ad hoc group information from the dynamic data held in the MCPTT servers and the ad hoc group ceases to exist, otherwise if the ad hoc group call follows an ad hoc group emergency alert the MCPTT servers keep the dynamic data and the ad hoc group continues to exist.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.3 Ad hoc group call setup – Participants list determined by the MCPTT server
|
Figure 10.19.3.2.3-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user wherein the list of participants is determined by the MCPTT server based on the criteria received from the MCPTT client and determined MCPTT users are from multiple MCPTT systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system share their users' information to the primary MC system.
2. The authorized MCPTT user/dispatcher belongs to the primary MC system.
3. The MCPTT server 1 of the primary MC system is where the authorized MCPTT user/dispatcher creates the ad hoc group.
4. Some users of the ad hoc group belong to MCPTT server 2 of the partner MC systems.
5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCPTT client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
Figure 10.19.3.2.3-1: Ad hoc group call setup involving multiple MCPTT systems
1-3. Same as described in subclause 10.19.3.1.3.
4. The MCPTT server 1 determines the list of participants from the primary MC system and determines the partner MC system to be involved in the ad hoc group call based on the information present in the information element Criteria for determining the participants. This information element carries the criteria, indicator identifying pre-defined criteria, or a combination of both.
NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how the MCPTT server determines the list of participants are left to implementation.
5. If the MCPTT server 1 needs to involve the partner system based on the agreement and based on the criteria for determining the participant list, it sends the ad hoc group call get userlist request to the MCPTT server 2. This request carries the criteria to be used by the partner MC system and is equal or derived from the criteria received in the step 1. Depending on the criteria provided and based on local policy, the MCPTT server may modify the content of the criteria received in step 1 to determine the list of participants.
6. MCPTT server 2 evaluates the criteria and determines the participants satisfying the criteria (i.e., MCPTT client 3 and MCPTT client 4) and sends the response containing the list of MCPTT users satisfying the criteria. The partner MCPTT server may apply local policies if any while determining the participants satisfying the criteria.
7. The MCPTT server 1 compiles the list of participants to be invited for the ad hoc group call including the participants from both primary and partner MC system.
8a-8b. The MCPTT server 1 sends the ad hoc group call request towards the MCPTT client 3 and MCPTT client 4. While sending the ad hoc group call request, the MCPTT server shall remove the information elements that are not required to be conveyed to the target MCPTT clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCPTT server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
9. The MCPTT server 1 sends the ad hoc group call requests towards the MCPTT client 2. While sending the ad hoc group call request, the MCPTT server shall remove the information elements that are not required to be conveyed to the target MCPTT clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCPTT server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
10a-10c. The receiving MCPTT clients notify their corresponding MCPTT user about the incoming ad hoc group call request with the information of the MCPTT group ID for the ad hoc group.
11. The MCPTT client 2 may accept or reject the ad hoc group call request and send ad hoc group call response to the MCPTT server 1.
12. The MCPTT client 3 may accept or reject the ad hoc group call request, and sends ad hoc group call response to the MCPTT server 1.
13. The MCPTT client 4 may accept or reject the ad hoc group call request, and sends ad hoc group call response to the MCPTT server 1.
14. The MCPTT server 1 sends the ad hoc group call response to MCPTT client 1 through the signalling path to inform about successful call establishment. The ad hoc group call response contains the call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
15. The MCPTT server 1 may notify the initiating MCPTT user of all MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call. The MCPTT server 1 more than once during the call may send this notification to the initiating MCPTT user whenever an MCPTT user joins or leaves the MCPTT ad hoc group call. The authorized users (not shown in figure), who are configured to receive the participants information of ad hoc group call, are notified to receive the MCPTT IDs of the MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call, when the MCPTT users joins late or leave the MCPTT ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
16. The MCPTT client 1, MCPTT client 2, MCPTT client 3 and MCPTT client 4 establish media plane and floor control resources.
NOTE 2: The ad hoc group call request and response exchanged between MCPTT server 1 of primary MC system and MCPTT client 3/MCPTT client 4 will always traversal through the MCPTT server 2.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.4 Modification of ad hoc group call participants by the MCPTT server
|
Figure 10.19.3.2.4-1 below illustrates the MCPTT server modifying the ad hoc group call participants procedure involving multiple MCPTT systems.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initate ad hoc group call.
2. The MCPTT server 1 of the primary and MCPTT server 2 of the partner MCPTT systems determined the participants for the ad hoc group call based on the criteria specified by the MCPTT client 1 while initiating the ad hoc group call.
3. The MCPTT server 1 of the primary and MCPTT server 2 of the partner MCPTT systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group call.
4. The MCPTT server 1 of the primary MCPTT system detects that the MCPTT client 3 meets the criteria and MCPTT client 2 stops to meet the criteria specified by the MCPTT client 1.
5. The MCPTT server 2 of the partner MCPTT system detects that the MCPTT client 5 meets the criteria and MCPTT client 4 stops to meet the criteria specified by the MCPTT client 1.
Figure 10.19.3.2.4-1: Modification of ad hoc group call participants by the MCPTT server
1. The ad hoc group call is established and on-going with the participants MCPTT client 1, MCPTT client 2, and MCPTT client 4. The participants list is determined by both primary and partner systems MCPTT server based on the criteria specified by the MCPTT client 1 while initiating the call.
2. The MCPTT server 1 detects that MCPTT client 3 now meets criteria and successfully added to call.
3. The MCPTT server 1 detects that MCPTT client 2 does not meet criteria any more and successfully removed from a call.
4. The MCPTT server 2 detects that the MCPTT client 5 meets the criteria specified by the MCPTT client 1.
5. The MCPTT server 2 sends the notification to MCPTT server 1 of the primary MCPTT system to add the MCPTT user at MCPTT client 5 to on-going ad hoc group call.
6. The MCPTT server 1 sends the ad hoc group call request to the MCPTT client 5.
7. The MCPTT client 5 notifies the user about the incoming ad hoc group call.
8. The MCPTT client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCPTT server 1.
9. The on-going ad hoc group call is updated by adding MCPTT client 5 which meets the criteria specified by the MCPTT client 1.
10. The MCPTT server 2 detects that the MCPTT client 4 is no more satisfying the criteria to be the participant of the ad hoc group call.
11. The MCPTT server 2 sends the notification to MCPTT server 1 of the primary MCPTT system to remove the MCPTT user at MCPTT client 4 from on-going ad hoc group call.
12. The MCPTT server 1 sends the ad hoc group call leave request to the MCPTT client 4 and removes it from the on-going ad hoc group call.
13. The MCPTT client 4 notifies the user of the ad hoc group call leave request.
14. The MCPTT client 4 sends the ad hoc group call leave response to the MCPTT server 1.
15. The on-going ad hoc group call is updated by removing MCPTT client 4, which no more meets the criteria specified by the MCPTT client 1.
NOTE: The ad hoc group call request and response exchanged between MCPTT server 1 of primary MC system and MCPTT client 4/MCPTT client 5 will always traversal through the MCPTT server 2.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.5 Release ad hoc group call and stop determining the ad hoc group call participants by partner MCPTT system – Participants list determined by the MCPTT server
|
Figure 10.19.3.2.5-1 below illustrates the release of ad hoc group call and stopping of MCPTT server at the partner MC system from determining the ad hoc group call participants’ procedure once involving multiple MCPTT systems. This procedure, in particular describes about how the partner MC system is notified about ad hoc group call release to cease the determining of the participants by the partner MC system.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initiate ad hoc group call.
2. The MCPTT server 1 of the primary and MCPTT server 2 of the partner MCPTT systems determined the participants for the ad hoc group call based on the criteria specified by the MCPTT client 1 while initiating the ad hoc group call.
3. The MCPTT server 1 of the primary and MCPTT server 2 of the partner MCPTT systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group call.
Figure 10.19.3.2.5-1: MCPTT server releases an ad hoc group call and stops the determination of ad hoc group call participants involving multiple MCPTT systems
1. The ad hoc group call is established and on-going with the participants MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The participant list is determined by both primary and partner systems MCPTT server based on the criteria specified by the MCPTT client 1 while initiating the call.
2. The MCPTT server 1 detects that the ad hoc group call which is ongoing is to be released e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present.
3. The MCPTT server 1 sends the notification to MCPTT server 2 of the partner MCPTT system about the ad hoc group call release to stop determining the participant list by MCPTT server 2 of the partner MCPTT system.
4a-4d. The MCPTT server 1 sends ad hoc group call release request to all the participants of the ad hoc group call.
5a-5d. The MCPTT clients notifies the user about the release of the ad hoc group call.
5. The MCPTT server 1 sends the notification to MCPTT server 2 of the partner MCPTT system about the ad hoc group call release to stop determining the participant list by MCPTT server 2 of the partner MCPTT system.
6a-6d. All the participants of the ad hoc group call receives the ad hoc group call release request and sends the ad hoc group call release response to the MCPTT server 1 of the primary MCPTT server.
NOTE: The ad hoc group call request and response exchanged between MCPTT server 1 of primary MC system and MCPTT client 3/MCPTT client 4 will always traversal through the MCPTT server 2.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.6 Modification of ad hoc group call participants by an authorized user
|
Figure 10.19.3.2.6-1 below illustrates the MCPTT user modifying the ad hoc group call participants procedure involving multiple MCPTT systems.
Pre-conditions:
1. An MCPTT ad hoc group call is already in progress and the participants list provided by the originating MCPTT user while initiating the MCPTT ad hoc group call.
2. The participants of the MCPTT ad hoc group call belongs to the multiple MCPTT system.
3. The MCPTT user at MCPTT client 1 determines that the MCPTT client 3 needs to be invited to on-going ad hoc group call and MCPTT client 2 needs to be removed from the on-going ad hoc group call from the primary MCPTT system.
4. The MCPTT user at MCPTT client 1 determines that the MCPTT client 5 needs to be invited to on-going ad hoc group call and MCPTT client 4 needs to be removed from the on-going ad hoc group call from the partner MCPTT system.
Figure 10.19.3.2.6-1: Modification of ad hoc group call participants by an authorized user
1. The MCPTT client 1 sends the modify ad hoc group call participants request to the MCPTT server 1 to remove both MCPTT client 2 and MCPTT client 4 from the on-going ad hoc group call and to add both MCPTT client 3 and MCPTT client 5 into on-going ad hoc group call.
2. The MCPTT server 1 verifies whether the MCPTT client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group call.
3. The MCPTT server 1 sends modify ad hoc group call participants response to the MCPTT client 1.
4. The MCPTT server 1 determines that MCPTT client 1 has requested that MCPTT client 3 from the primary MC system be invited to an on-going ad hoc group call and successfully added to the call according to the procedure defined in clause 10.19.3.1.4.
5. The MCPTT server 1 determines that MCPTT client 1 has requested that MCPTT client 2 from the primary MC system be removed from the on-going ad hoc group call and successfully removed from call according to the procedure defined in clause 10.19.3.1.4.
6. The MCPTT server 1 determines that MCPTT client 1 has requested that MCPTT client 5 from the partner MC system be invited to an on-going ad hoc group call. The MCPTT server 1 sends the ad hoc group call request to the MCPTT client 5.
7. The MCPTT client 5 notifies the user about the incoming ad hoc group call.
8. The MCPTT client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCPTT server 1.
9. The on-going ad hoc group call is updated by adding MCPTT client 5 which is based on the modify participant list provided by the MCPTT client 1.
10. The MCPTT server 1 determines that MCPTT client 1 has requested that MCPTT client 4 from the partner MC system be removed from the on-going ad hoc group call. The MCPTT server 1 sends the ad hoc group call leave request to the MCPTT client 4.
11. The MCPTT client 4 notifies the user of the ad hoc group call leave request.
12. The MCPTT client 4 sends the ad hoc group call leave response to the MCPTT server 1.
13. The on-going ad hoc group call is updated by removing MCPTT client 4, which is based on the modify participant list provided by the MCPTT client 1.
NOTE: The ad hoc group call request and response exchanged between MCPTT server 1 of primary MC system and MCPTT client 4/MCPTT client 5 will always traversal through the MCPTT server 2.
14. The MCPTT server 1 may notify the initiating MCPTT user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the ad hoc group call.
15. The MCPTT server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.19.3.2.7 Modification of ad hoc group call criteria by an authorized user
|
Figure 10.19.3.2.7-1 illustrates the modification of ad hoc group call criteria procedure by the initiator of the ad hoc group call between multiple MC systems. Preconditions: - The MCPTT user at the MCPTT client 1 is authorized to modify the criteria. - The MCPTT server A and MCPTT server B are aware of the criteria related to the ongoing ad hoc group call. - MC system A and MC system B are interconnected. Figure 10.19.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group call between multiple MC systems 1. An ad hoc group call has been established based on criteria sent by an authorized MCPTT client upon initiating the ad hoc group call. 2. The MCPTT user at the MCPTT client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group call participants. 3a. MCPTT client 1 sends a modify ad hoc group call criteria request to MCPTT server A. 3b. MCPTT server A determines that the modify ad hoc group call criteria request received in step 3a has impact on users in MCPTT server B. Depending on the criteria provided and based on local policy, the MCPTT server may modify the content of the criteria received in step 3a to determine the list of participants. 3c. MCPTT server A sends a modify ad hoc group call criteria request to MCPTT server B containing the resulting criteria to be used by MCPTT server B. NOTE 1: If MCPTT server A identifies that the criteria require to add participants from another MC system then MCPTT server A sends an ad hoc group call request to the MCPTT server in that MC system. 4a/b. The MCPTT server A receives the ad hoc group call criteria modify response and forwards the response to MCPTT client 1 in MC system A. 5. MCPTT server B detects that MCPTT client 3 meets the criteria for the ongoing ad hoc group call initiated at MC system A. 5a. MCPTT server B sends an ad hoc group call add user notification message towards MCPTT server A. 5b. MCPTT server A sends an ad hoc group call request towards MCPTT client 3. 5c. The MCPTT user 3 is notified of entering an ongoing ad hoc group call. 5d. MCPTT client 3 sends an ad hoc group call response towards MCPTT server A. 5e. MCPTT server B sends an ad hoc group call remove user notification message towards MCPTT server A. 5f. MCPTT server A sends an ad hoc group call leave request towards MCPTT client 4. 5g. The MCPTT user 4 is notified of leaving an ongoing ad hoc group call. 5h. MCPTT client 4 sends an ad hoc group call leave response towards MCPTT server A. 6. The MCPTT server A may notify the authorised MCPTT user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the authorised MCPTT user by the MCPTT server A more than once during the call when MCPTT users join or leave the ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCPTT servers to determine the list of participants to be invited. 7. The MCPTT server A adds MCPTT client 3 to the ad hoc group call and removes MCPTT client 4 from the ad hoc group call. The MCPTT servers continuously check whether other MCPTT clients meet or if participating MCPTT clients no longer meet the criteria for the ad hoc group call. NOTE 2: If the ad hoc group call is associated with an ad hoc group emergency alert and the change of criteria caused the modification of the ad hoc group call participant list then the ongoing ad hoc group emergency alert is modified accordingly. Annex A (normative): MCPTT related configuration data A.1 General This Annex provides information about the static data needed for configuration for the MCPTT service, which belongs to one of the following categories: - MCPTT UE configuration data (see subclause A.2); - MCPTT user profile configuration data (see subclause A.3); - MCPTT related group configuration data (see subclause A.4); and - MCPTT service configuration data (see subclause A.5). For each configuration category, data is split between configuration data that is applicable to both on‑network and off‑network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCPTT UE, MCPTT group, MCPTT user and MCPTT service configuration data refers to the information that will be stored against each MCPTT UE, MCPTT group, MCPTT user and MCPTT service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. The columns in the tables have the following meanings: - Reference: the reference of the corresponding requirement in 3GPP TS 22.179 [2] or 3GPP TS 22.280 [17] or 3GPP TS 23.280 [16] or the corresponding subclause from the present document. - Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. - When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCPTT UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. A.2 MCPTT UE configuration data The general aspects of UE configuration are specified in 3GPP TS 23.280 [16]. Data in tables A.2-1 and A.2-2 have to be known by the MCPTT UE after MCPTT authorization. Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-2 contains the UE configuration required to support the use of off-network MCPTT service. Table A.2-1: UE configuration data (on and off network) Reference Parameter description [R-5. 4.2-002] of 3GPP TS 22.280 [17] Maximum number of simultaneous group calls (Nc4) [R-5.4.2-003] of 3GPP TS 22.280 [17] Maximum number of transmissions (Nc5) in a group [R-5.5.2-007] of 3GPP TS 22.280 [17] Maximum number of private calls (N10) Table A.2-2: UE configuration data (on network) Reference Parameter description Subclause 5.2.3 of 3GPP TS 23.280 [16] Relay service (Y/N) Subclause 5.2.3 of 3GPP TS 23.280 [16] List of allowed relayed MCPTT groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) > MCPTT group ID > Relay service code (as specified in 3GPP TS 23.303 [7]) NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. A.3 MCPTT user profile configuration data The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [16]. The MCPTT user profile configuration data is stored in the MCPTT user database. The MCPTT server obtains the MCPTT user profile configuration data from the MCPTT user database (MCPTT-2). The recording server obtains the MCPTT user profile configuration data from the configuration management server (REC-5 in 3GPP TS 23.280 [16]). Tables A.3-1 and A.3-2 contain the MCPTT user profile configuration required to support the use of on-network MCPTT service. Tables A.3-1 and A.3-3 contain the MCPTT user profile configuration required to support the use of off-network MCPTT service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. Table A.3-1: MCPTT user profile data (on and off network) Reference Parameter description MCPTT UE Rec. admin UE & Replay UE (NOTE 11) MCPTT Server Configuration management server Rec. server MCPTT user database Subclause 8.1.2 of 3GPP TS 23.280 [16] MCPTT user identity (MCPTT ID) Y Y Y Y Y Y 3GPP TS 33.180 [19] KMSUri for security domain of MCPTT ID (see NOTE 4) Y Y Y Y Subclause 5.2.4 of 3GPP TS 23.280 [16] Pre‑selected MCPTT user profile indication (see NOTE 3) Y Y Y Y Subclause 5.2.4 of 3GPP TS 23.280 [16] MCPTT user profile index Y Y Y Y Subclause 5.2.4 of 3GPP TS 23.280 [16] MCPTT user profile name Y Y Y Y [R-5.19-007], [R-6.13.4-002] of 3GPP TS 22.280 [17] User profile status (enabled/disabled) Y Y Y Y Y [R-5.8-001], [R-6.9-003] of 3GPP TS 22.280 [17] Authorised to create and delete aliases of an MCPTT User and its associated user profiles. Y Y [R-5.8-002], [R-6.9-003] of 3GPP TS 22.280 [17] Alphanumeric aliases of user Y Y Y Y [R-5.10-001] of 3GPP TS 22.280 [17] Participant type of the user Y Y Y Y [R-5.3-002], [R-5.10-001] of 3GPP TS 22.280 [17] User's Mission Critical Organization (i.e. which organization a user belongs to) Y Y Y Y Y Y [R-5.4.2-003] of 3GPP TS 22.280 [17] Maximum number of simultaneously received group calls (Nc5) Y Y Y [R-5.6.5-004] of 3GPP TS 22.179 [2] Authorised to make a private call Y Y Y Y [R-5.6.5-001] of 3GPP TS 22.179 [2] Authorised to make a private call with manual commencement Y Y Y Y [R-5.6.5-003] of 3GPP TS 22.179 [2] [R-6.7.3-007] of 3GPP TS 22.280 [17] List of user(s) who can be called in private call > MCPTT ID Y Y Y Y > User info ID Y N Y Y > ProSe discovery group ID Y N Y Y 3GPP TS 33.180 [19] > KMSUri for security domain of MCPTT ID (see NOTE 4) Y Y Y Y [R-6.7.4-004] of 3GPP TS 22.280 [17] > Presentation priority relative to other users and groups (see NOTE 2) Y Y Y Y [R-5.6.5-003] of 3GPP TS 22.179 [2] Authorised to make a private call to users not included in "list of user(s) who can be called in private call" Y Y Y Y [R-5.6.5-002] of 3GPP TS 22.179 [2] Authorised to make a private call with automatic commencement Y Y Y Y [R-5.6.3-011], [R-6.7.4-010] of 3GPP TS 22.179 [2] Authorisation of user to force automatic answer for a private call Y Y Y Y [R-5.6.5-006], [R-6.7.5-002] of 3GPP TS 22.179 [2] Authorised to restrict the provision of a notification of call failure reason for private call Y Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Authorisation to protect confidentiality and integrity of media in a private call (see NOTE 1) Y Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Authorisation to protect confidentiality and integrity of floor control signalling in a private call (see NOTE 1) Y Y Y Y [R-5.6.2.2.1-001] of 3GPP TS 22.280 [17] Authorisation to make an MCPTT emergency group call functionality enabled for user Y Y Y Y [R-5.6.2.4.1-001] of 3GPP TS 22.280 [17] Group used on initiation of an MCPTT emergency group call (see NOTE 7) Y Y Y Y [R-5.6.2.4.1-001] of 3GPP TS 22.280 [17] Recipient for an emergency private MCPTT call (see NOTE 7) > MCPTT ID Y Y Y Y 3GPP TS 33.180 [19] > KMSUri for security domain of MCPTT ID (see NOTE 4) Y Y Y Y [R-5.6.2.2.2-005] of 3GPP TS 22.280 [17] Authorisation to cancel an in progress emergency associated with a group Y Y Y Y [R-5.6.2.2.3-001] of 3GPP TS 22.280 [17] Authorised to make an Imminent Peril group call Y Y Y Y [R-5.6.2.2.3-009] of 3GPP TS 22.280 [17] Group used on initiation of an MCPTT imminent peril group call (see NOTE 8) Y Y Y Y [R-5.6.2.2.2-002] of 3GPP TS 22.280 [17] Authorised for imminent in- peril cancelation Y Y Y Y [R-5.6.2.3.1-001] of 3GPP TS 22.179 [2] Authorised to make an emergency private call Y Y Y Y [R-5.6.2.3.2-001] of 3GPP TS 22.179 [2] Authorised to cancel emergency priority in a private emergency call by an authorized user Y Y Y Y [R-5.6.2.4.1-002] of 3GPP TS 22.280 [17] Authorised to activate emergency alert Y Y Y Y [R-5.6.2.4.1-013] of 3GPP TS 22.280 [17] Automatically trigger a MCPTT emergency communication after initiating the MCPTT emergency alert Y Y Y Y [R-5.6.2.4.2-002] of 3GPP TS 22.280 [17] Authorisation to cancel an MCPTT emergency alert Y Y Y Y [R-6.15.6.2-002] of 3GPP TS 22.280 [17] Authorised to activate an MCPTT ad hoc group emergency alert Y Y Y Y [R-6.15.6.2-006] of 3GPP TS 22.280 [17] Authorisation to cancel an MCPTT ad hoc group emergency alert Y Y Y Y Authorised to receive the participants information of an MCPTT ad hoc group emergency alert N Y Y Y [R-6.15.6.2-007] of 3GPP TS 22.280 [17] Authorised to set up a group call using the ad hoc group used for the alert Y Y Y Y Authorised to modify the list of participants and criteria for an MCPTT ad hoc group emergency alert Y Y Y Y [R-5.1.7-002] and [R-6.8.7.2-007] and [R-6.8.7.2-008] of 3GPP TS 22.280 [17] Priority of the user (see NOTE 9) Y Y Y [R-5.2.2-003] and [R-6.6.3-002] of 3GPP TS 22.280 [17] Authorisation to create a group-broadcast group (see NOTE 10) Y Y [R-5.2.2-003] and [R-6.6.3-002] of 3GPP TS 22.280 [17] Authorisation to create a user-broadcast group (see NOTE 10) Y Y [R-5.3-003], [R-6.12-001], [R-7.2-005] of 3GPP TS 22.280 [17] Authorisation to provide location information to other MCPTT users on a call when talking Y Y Y 3GPP TS 23.283 [20] Authorised to use LMR E2EE for interworking Y Y Y Y 3GPP TS 23.283 [20] > List of supported LMR technology types 3GPP TS 23.283 [20] >> LMR technology type (P25, TETRA etc.) Y N Y Y 3GPP TS 23.283 [20] >> URI of LMR key management functional entity (see NOTE 6) Y N Y Y 3GPP TS 23.283 [20] >> LMR specific identity (RSI for P25 or ITSI for TETRA) (see NOTE 5) Y N Y Y 3GPP TS 23.283 [20] >>LMR specific security information (see NOTE 5) Y N Y Y [R-6.15.4-001…010] of 3GPP TS 22.280 [17] User is a target for recording Y (NOTE 13) Y Y Y Y Y [R-6.15.4-001…010] of 3GPP TS 22.280 [17] Recording server address (URI) (NOTE 12) Y (NOTE 13) Y Y Y Y NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [11]. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. NOTE 3: As specified in 3GPP TS 23.280 [16], for each MCPTT user's set of MCPTT user profiles, only one MCPTT user profile shall be indicated as being the pre‑selected MCPTT user profile. NOTE 4: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. NOTE 5: This is an LMR specific parameter with no meaning within MC services. NOTE 6: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. NOTE 7: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCPTT user's currently selected group will be used. NOTE 8: This group, if configured, will be used for imminent peril communication. If not configured the MCPTT user's currently selected group will be used. NOTE 9: The use of the parameter is left to implementation. NOTE 10: This parameter applies to temporary broadcast groups built from regrouping mechanism. This authorisation automatically sets the originator of the temporary group as the only transmitting party. NOTE 11: This is the recording admin UE and/or replay UE of a user who is authorized to set this MCPTT user as target for recording and/or authorized to replay this MCPTT user’s recordings. NOTE 12: If this parameter is absent, the recording server URI shall be that identified in the initial MC service UE configuration data (on-network, 3GPP TS 23.280 table A.6-1) or in the initial recording admin and replay UE configuration data (on-network, 3GPP TS 23.280 table A.10-1). NOTE 13: These parameters, when provided to an MCPTT UE, are relevant only for recording administrators and replay users. Table A.3-2: MCPTT user profile data (on network) Reference Parameter description MCPTT UE Rec. admin UE & Replay UE (NOTE 12) MCPTT Server Configuration management server MCPTT user database [R-5.1.5-001], [R-5.1.5-002], [R-5.10-001], [R-6.4.7-002], [R-6.8.1-008] of 3GPP TS 22.280 [17] List of on-network MCPTT groups for use by an MCPTT user > MCPTT Group ID Y Y Y Y Y > Application plane server identity information of group management server where group is defined >> Server URI Y Y N Y Y > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) >> Server URI Y Y N Y Y 3GPP TS 33.180 [19] > KMSUri for security domain of group (see NOTE 3) Y Y Y Y > Presentation priority of the group relative to other groups and users (see NOTE 2) Y Y Y Y [R-6.2.3.7.2-006] of 3GPP TS 22.179 [2] > Authorisation of an MCPTT user to change the maximum number of simultaneous talkers Y Y Y Y Subclause 5.2.5 of 3GPP TS 23.280 [16] List of groups user implicitly affiliates to after MCPTT service authorization for the user > MCPTT Group IDs Y Y Y Y [R-6.4.2-006] of 3GPP TS 22.280 [17] Authorisation of an MCPTT user to request a list of which groups an MCPTT user has affiliated to Y Y Y [R-6.4.6.1-002], [R-6.4.6.1-003] of 3GPP TS 22.280 [17] Authorisation to change affiliated groups of other specified user(s) Y Y Y [R-6.4.6.2-001], [R-6.4.6.2-002] of 3GPP TS 22.280 [17] Authorisation to recommend to specified user(s) to affiliate to specific group(s) Y Y Y [R-6.6.1-004] of 3GPP TS 22.280 [17] Authorisation to perform regrouping Y Y Y Y [R-6.7.2-001] of 3GPP TS 22.280 [17] Presence status is available/not available to other users Y Y Y Y [R-6.7.1-002], [R-6.7.2-002] of 3GPP TS 22.280 [17] List of MCPTT users that an MCPTT user is authorised to obtain presence of > MCPTT IDs Y Y Y Y [R-6.7.2-003] of 3GPP TS 22.280 [17] User is able/ unable to participate in private calls Y Y Y Y [R-6.7.1-004], [R-6.7.2-003], [R-6.7.2-004] of 3GPP TS 22.280 [17] Authorisation to query whether MCPTT User is available for private calls Y Y Y [R-6.7.1-010] of 3GPP TS 22.179 [2] Authorisation to override transmission in a private call Y Y Y Y [R-6.7.1-013] of 3GPP TS 22.179 [2] Authorisation to restrict provision of private call set-up failure cause to the caller Y Y Y [R-6.7.6-001] of 3GPP TS 22.179 [2] Authorized to make a private call‑back request Y Y Y Y [R-6.7.6-004] of 3GPP TS 22.179 [2] Authorized to cancel a private call‑back request Y Y Y Y [R-6.8.7.4.2-001], [R-6.8.7.4.2-002] of 3GPP TS 22.280 [17] Authorisation of an MCPTT user to cancel an emergency alert on any MCPTT UE of any MCPTT user Y Y Y [R-6.13.4-001] of 3GPP TS 22.280 [17] Authorisation for a MCPTT user to enable/disable an MCPTT user Y Y Y [R-6.13.4-003], [R-6.13.4-005], [R-6.13.4-006], [R-6.13.4-007] of 3GPP TS 22.280 [17] Authorisation for an MCPTT user to (permanently /temporarily) enable/disable a UE Y Y Y [R-6.2.3.4-001] of 3GPP TS 22.179 [2] Authorisation to revoke permission to transmit Y Y Y [R-7.14-002], [R-7.14-003] of 3GPP TS 22.280 [17] Authorization for manual switch to off-network while in on-network Y Y Y Y [R-5.1.5-004] of 3GPP TS 22.280 [17] Limitation of number of affiliations per user (N2) N Y Y Y [R-5.5.2-009] of 3GPP TS 22.179 [2] Maximum number of simultaneous transmissions received in one group call for override (N7) Y Y Y [R-6.4.6.1-001], [R-6.4.6.1-004] of 3GPP TS 22.280 [17] List of MCPTT users whose selected groups are authorized to be remotely changed > MCPTT IDs Y Y Y Y Subclause 10.15.3 Authorization to make a first‑to‑answer call Y Y Y Y [R-6.15.2.2.2-001] of 3GPP TS 22.280 [17] Authorization to make a remotely initiated ambient listening private call Y Y Y Y [R-6.15.2.2.3-001] of 3GPP TS 22.280 [17] Authorization to make a locally initiated ambient listening private call Y Y Y Y [R-6.15.3.2-001] of 3GPP TS 22.280 [17] Authorization to make a remotely initiated private call Y Y Y Y [R-6.15.3.2-003] of 3GPP TS 22.280 [17] Authorization to make a remotely initiated group call Y Y Y Y [R-5.9a-013] of 3GPP TS 22.280 [17] Authorised to request association between active functional alias(es) and MCPTT ID(s) Y Y Y [R-5.9a-012] of 3GPP TS 22.280 [17] Authorised to take over a functional alias from another MCPTT user Y Y Y List of functional alias(es) of the MCPTT user [R-5.9a-005] of 3GPP TS 22.280 [17] > Functional alias Y Y Y Y [R-5.4.2-007a] of 3GPP TS 22.280 [17] >> Maximum number of parallel emergency group calls Y Y Y [R-5.9a-018] of 3GPP TS 22.280 [17] >> Criteria for automatic activation by the MCPTT server (see NOTE 6) N Y Y Y [R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [17] >> Criteria for automatic de-activation by the MCPTT server (see NOTE 6) N Y Y Y [R-5.9a-019] of 3GPP TS 22.280 [17] >> Location criteria for activation Y Y Y [R-5.9a-019] of 3GPP TS 22.280 [17] >> Location criteria for de-activation Y Y Y >> Manual de-activation is not allowed if the location criteria are met Y Y Y [R-5.9a-020] of 3GPP TS 22.280 [17] List of functional aliases to which first-to-answer calls and private calls are allowed when using a certain functional alias > Used functional alias Y Y Y Y >> List of functional aliases which can be called >>> Functional alias Y Y Y Y [R-5.9a-021] of 3GPP TS 22.280 [17] List of functional aliases from which first-to-answer calls and private calls can be received when using a certain functional alias > Used functional alias N Y Y Y >> List of functional aliases from which calls can be received >>> Functional alias N Y Y Y [R-6.7.3-007a] of 3GPP TS 22.280 [17] List of user(s) from which private calls can be received > MCPTT ID Y Y Y Y 3GPP TS 33.180 [19] > KMSUri for security domain of MCPTT ID Y Y Y Y [R-6.7.4-004] of 3GPP TS 22.280 [17] > Presentation priority relative to other users and groups Y Y Y Y Authorised to receive private calls from any other MCPTT ID (see NOTE 8) Y Y Y Y Subclause 5.2.9 of 3GPP TS 23.280 [16] List of partner MCPTT systems in which this profile is valid for use during migration Subclause 5.2.9 of 3GPP TS 23.280 [16] > Identity of partner MCPTT system Y Y Y Y Subclause 10.1.1 of 3GPP TS 23.280 [16] > Access information for partner MCPTT system (see NOTE 4) Y Y Y Subclause 10.6.2.9 Authorized to initiate or cancel group regrouping using a preconfigured regroup group Y Y Y Y [R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [17] List of groups the client affiliates/de-affiliates when one or multiple criteria are met > MCPTT Group ID Y Y Y Y >> Criteria for affiliation (see NOTE 5) Y Y Y Y >> Criteria for de-affiliation (see NOTE 5) Y Y Y Y >> Manual de-affiliation is not allowed if the criteria for affiliation are met Y Y Y Y [R-6.6.4.2-002] of 3GPP TS 22.280 [17] List of groups the client affiliates after receiving an emergency alert > MCPTT Group ID Y Y Y Y >> Manual de-affiliation is not allowed if the criteria for affiliation are met Y Y Y Y [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Allow private call forwarding Y Y Y [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Call Forwarding NoAnswer Timeout Y Y Y [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Call forwarding turned on Y Y Y R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Target of the MCPTT private call forwarding R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] > Target MCPTT ID (see NOTE 10) Y Y Y R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] > Target functional alias (see NOTE 10) Y Y Y R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Condition Y Y Y [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] Allow private call transfer (see NOTE 7) Y Y Y Y [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] > MCPTT ID Y Y Y [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] List of functional aliases that the MCPTT user is authorised to use as targets for call transfer [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] > Functional alias Y Y Y ] [R-5.6.3-014], [R-6.7.4-015] of 3GPP TS 22.179 [2] Authorised to transfer private calls to any MCPTT user Y Y Y Y [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Authorised to forward private calls based on manual input to any MCPTT user (see NOTE 9) Y Y Y Y [R-5.10-001b] of 3GPP TS 22.280 [17] Maximum number of successful simultaneous MCPTT service authorizations for this user (see NOTE 11) N Y Y Y ad hoc group call authorizations [R-6.15.5.3-001] of 3GPP TS 22.280 [17] > Authorised to initiate ad hoc group call Y Y Y Y R-6.15.5.3-003] of 3GPP TS 22.280 [17] > Authorised to participate in ad hoc group call Y Y Y Y > Authorised to initiate emergency ad hoc group call Y Y Y Y > Authorised to initiate imminent peril ad hoc group call Y Y Y Y > Authorised to receive the participants information of an ad hoc group call N Y Y Y > Authorised to modify the list of participants and criteria for an ad hoc group call Y Y Y Y > Authorised to release ongoing ad hoc group calls Y Y Y Y Subclause 10.6.2.6.4, 10.7.2.4.3 Authorized to trigger another MCPTT client, who is in an emergency state, to initiate a floor request. Y Y Y Y NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. NOTE 4: Access information for each partner MCPTT system comprises the list of information required for initial UE configuration to access an MCPTT system, as defined in table A.6-1 of 3GPP TS 23.280 [16] NOTE 5: The criteria may consist of conditions such as the MCPTT user location or the active functional alias of the MCPTT user. NOTE 6: The criteria may consist of conditions such MCPTT user location or time. NOTE 7: Defines the right to perform a call transfer. For call transfer the MCPTT server does not check if the initial originating MCPTT user has the right to make a private MCPTT call to the final destination MCPTT user. NOTE 8: This parameter only applies to MCPTT users which are in the same security domain. NOTE 9: Defines the right to perform a call forwarding based on manual user input. For call forwarding based on manual user input the MCPTT server does not check if the initial originating MCPTT user has the right to make a private MCPTT call to the final destination MCPTT user. NOTE 10: Either the Target MCPTT ID or the Target functional alias may be present (but not both). NOTE 11: If configured, this value has precedence over the system level parameter "maximum number of successful simultaneous service authorisations" in table A.5-2. If not configured, the corresponding parameter from table A.5-2 shall be used. NOTE 12: This is the recording admin UE and/or replay UE of a user who is authorized to set this MCPTT user as target for recording and/or authorized to replay this MCPTT user’s recordings. Table A.3-3: MCPTT user profile data (off network) Reference Parameter description MCPTT UE MCPTT Server Configuration management server MCPTT user database [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [17] List of off-network MCPTT groups for use by an MCPTT user Y N Y Y > MCPTT Group ID Y N Y Y > Application plane server identity information of group management server where group is defined >> Server URI Y N Y Y > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) >> Server URI Y N Y Y 3GPP TS 33.180 [19] > KMSUri for security domain of group (see NOTE 3) Y N Y Y > Presentation priority of the group relative to other groups and users (see NOTE 2) Y N Y Y [R-7.3.3-008] of 3GPP TS 22.179 [2] Allowed listening of both overriding and overridden Y N Y Y [R-7.3.3-006] of 3GPP TS 22.179 [2] Allowed transmission for override (overriding and/or overridden) Y N Y Y [R-7.8.1-001] of 3GPP TS 22.280 [17] Authorization for participant to change an off-network group call in-progress to off-network emergency group call Y N Y Y [R-7.8.3.1-003] of 3GPP TS 22.280 [17] Authorization for participant to change an off-network group call in-progress to off-network imminent peril group call Y N Y Y [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [17] Authorization for off-network services Y N Y Y Subclauses 10.6.3, 10.7.3 User info id (as specified in 3GPP TS 23.303 [7]) Y N Y Y NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16] A.4 MCPTT related group configuration data The general aspects of group configuration are specified in 3GPP TS 23.280 [16]. Parameters specified in table A.4-1 are child parameters of the "MCPTT configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-2 are child parameters of the "MCPTT configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-3 are child parameters of the "MCPTT configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [16]. Table A.4-1: Group configuration data (on and off network) Reference Parameter description MCPTT UE MCPTT Server Group management server [R-6.4.9-006] of 3GPP TS 22.280 [17] >> Preferred voice codecs for MCPTT group Y Y Y [R-5.7.2.1.1-013], [R-5.7.2.4.1-008] of 3GPP TS 22.280 [17] >> Indication whether emergency group call is permitted on the MCPTT group Y Y Y [R-5.7.2.2.1-009] of 3GPP TS 22.280 [17] >> Indication whether imminent peril group call is permitted on the MCPTT group Y Y Y [R-5.7.2.4.1-012] of 3GPP TS 22.280 [17] >> Indication whether emergency alert is possible on the MCPTT group Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] >> Media confidentiality and integrity protection (see NOTE) Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] >> Floor control confidentiality and integrity protection (see NOTE) Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] >> Group media protection security material (see NOTE) Y N Y NOTE: Security mechanisms are specified in 3GPP TS 33.180 [19]. Table A.4-2: Group configuration data (on‑network) Reference Parameter description MCPTT UE MCPTT Server Group management server [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] >> Timeout value for the cancellation of an in‑progress emergency for an on‑network group call N Y Y [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] >> Timeout value for the cancellation of an in progress imminent-peril group call for an on‑network group call N Y Y [R-6.2.4-003], [R-6.4.9-002] of 3GPP TS 22.179 [2] >> Group call hang timer N Y Y [R-6.4.9-003] of 3GPP TS 22.280 [17] >> Maximum duration of group calls N Y Y Subclause 10.6.2 >> Group call model used for group (chat/ pre-arranged) Y Y Y [R-6.2.1-004], [R-6.2.1-007] of 3GPP TS 22.179 [2] >> Minimum number of affiliated group members acknowledging before start of audio transmission N Y Y [R-6.2.1-007] of 3GPP TS 22.179 [2] >> List of group members which, if affiliated, have to acknowledge before start of audio transmission >>>MCPTT IDs N Y Y [R-6.2.1-006], [R-6.2.1-007] of 3GPP TS 22.179 [2] >> Geographical area where acknowledgement of all affiliated group members is required before start of audio transmission N Y Y [R-6.2.1-008], [R-6.2.1-009] of 3GPP TS 22.179 [2] >> Timeout for acknowledgement of required group members N Y Y [R-6.2.1-008], [R-6.2.1-009], [R-6.2.1-012] of 3GPP TS 22.179 [2] >> Action upon failure to receive acknowledgement from required group members before call timeout (proceed or abandon) N Y Y [R-6.2.1-001a] of 3GPP TS 22.179 [2] >> Minimum number of group members which must be affiliated to allow the start of the group call N Y Y [R-6.2.1-001b] of 3GPP TS 22.179 [2] >> List of group members which must be affiliated to allow the start of the group call >>>MCPTT IDs N Y Y [R-6.4.9-004] of 3GPP TS 22.280 [17] >> List of group members with receive-only capability (see NOTE 1) >>>MCPTT IDs N Y Y [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [17] >> Authorisation of a user to request a list of affiliated members of a group Y Y Y [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006,] [R-6.8.6.2-003] of 3GPP TS 22.280 [17] >> Priority of the group N Y Y [R-6.8.6.2-003] of 3GPP TS 22.280 [17] >> Pre-emption capability Y Y Y [R-6.8.6.2-003] of 3GPP TS 22.280 [17] >> Pre-empted capability Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] >> Group floor control protection security material for multicast use (see NOTE 2) Y Y Y [R-6.2.3.6.2-001] of 3GPP TS 22.179 [2] >> Audio cut-in policy (enabled/disabled) N Y Y [R-6.2.3.7.2-001] of 3GPP TS 22.179 [2] >> Support of multi-talker control Y Y Y [R-6.2.3.7.2-005] of 3GPP TS 22.179 [2] >> Maximum number of simultaneous talkers applicable for multi-talker control N Y Y Subclause 7.4.2.3.5 and subclause 7.4.2.3.6 >> Audio mixing is performed in the UE or in the network to support multi-talker control Y Y Y [R-6.2.3.7.2-003] of 3GPP TS 22.179 [2], [R-5.2.1-001] of 3GPP TS 22.280 [17] >> List of group members which are allowed to talk (see NOTE 1, NOTE 4) >>> MCPTT ID Y Y Y 3GPP TS 23.283 [20] >> Indication whether use of LMR E2EE is permitted on the MCPTT group Y N Y 3GPP TS 23.283 [20] >> LMR specific identity for MCPTT group (see NOTE 3) Y N Y 3GPP TS 23.283 [20] >> Group to key binding (see NOTE 3) Y N Y NOTE 1: A group member shall not be listed in both the list of group members with receive only capability and the list of group members which are allowed to talk. NOTE 2: The details of security related elements are specified in 3GPP TS 33.180 [19]. NOTE 3: This is an LMR specific parameter with no meaning within MC services. NOTE 4: This parameter is applicable for MCPTT groups with multi-talker control / sets the authorization to talk in pre-arranged groups used in broadcast calls. Table A.4-3: Group configuration data (off‑network) Reference Parameter description MCPTT UE MCPTT Server Group management server [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] >> Timeout value for the cancellation of an in‑progress emergency for an off‑network group call Y N Y [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] >> Timeout value for the cancellation of an in progress imminent-peril group call for an off‑network group call Y N Y [R-7.4-002] of 3GPP TS 22.179 [2] >> Group call hang timer Y N Y [R-7.4-003] of 3GPP TS 22.280 [17] >> Max duration of group calls Y N Y Subclause 10.6.3.9.1 >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values >>> MCPTT group call signalling Y N Y >>> MCPTT group call media Y N Y >>> MCPTT emergency group call signalling Y N Y >>> MCPTT emergency group call media Y N Y >>> MCPTT imminent peril group call signalling Y N Y >>> MCPTT imminent peril group call media Y N Y A.5 MCPTT service configuration data The general aspects of MC service configuration are specified in 3GPP TS 23.280 [16]. The MCPTT service configuration data is stored in the MCPTT server. Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCPTT service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCPTT service. Data in tables A.5-1and A.5-3 can be configured offline using the CSC-11 reference point. Table A.5-1: MCPTT service configuration data (on and off network) Reference Parameter description MCPTT UE MCPTT Server Configuration management server [R-5.2.2-001] of 3GPP TS 22.280 [17] Levels of group hierarchy for group-broadcast groups (Bc1) Y Y Y [R-5.2.3-001] of 3GPP TS 22.280 [17] Levels of user hierarchy for user-broadcast groups (Bc2) Y Y Y [R-5.8-002] of 3GPP TS 22.280 [17] Minimum length (Nc3) of an alphanumeric identifier (i.e. alias) assigned by an MCPTT administrator. Y N Y Table A.5-2: MCPTT service configuration data (on‑network) Reference Parameter description MCPTT UE MCPTT Server Configuration management server [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] Timeout value for the cancellation of an in‑progress emergency for an on‑network private call N Y Y [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] Time limit for an in-progress emergency related to an on‑network MCPTT group N Y Y [R-5.6.5-004] of 3GPP TS 22.179 [2] Max on‑network private call (with floor control) duration N Y Y [R-6.2.4-003] of 3GPP TS 22.179 [2] Hang timer for private calls N Y Y [R-6.7.2-008] of 3GPP TS 22.280 [17] Max duration of private call (without floor control) N Y Y [R-6.2.3.3.1-001] of 3GPP TS 22.179 [2] Hierarchy of participant rights to override N Y Y [R-6.2.3.5-002] of 3GPP TS 22.179 [2] Transmit time limit from a single request to transmit in a group or private call transmission N Y Y [R-6.2.3.5-003], [R-6.2.3.5-004] of 3GPP TS 22.179 [2] Configuration of warning time before time limit of transmission is reached (on-network) N Y Y [R-6.2.4-005] of 3GPP TS 22.179 [2] Configuration of warning time before call hang time (on-network) N Y Y [R-6.2.3.2-006] of 3GPP TS 22.179 [2] Depth of floor control queue N Y Y [R-6.2.3.2-012] of 3GPP TS 22.179 [2] Max time for a user's floor control request to be queued N Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Protect confidentiality of signalling (see NOTE 1) Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Protect integrity of signalling (see NOTE 1) Y Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Use signalling protection between MCPTT servers (see NOTE 1) N Y Y [R-5.13-001] of 3GPP TS 22.280 [17] Use floor control protection between MCPTT servers (see NOTE 1) N Y Y List of functional alias identities [R-5.9a-005] of 3GPP TS 22.280 [17] > Functional alias N Y Y [R-5.9a-016] of 3GPP TS 22.280 [17] > Communication priority (see NOTE 2) N Y Y [R-5.9a-005] of 3GPP TS 22.280 [17] > Limit number of simultaneous activations N Y Y [R-5.9a-005] of 3GPP TS 22.280 [17] > This functional alias can be taken over N Y Y > List of users [R-5.9a-005] of 3GPP TS 22.280 [17] >> MCPTT ID N Y Y [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] Max number immediate forwardings N Y Y [R-5.10-001a] of 3GPP TS 22.280 [17] Maximum number of successful simultaneous service authorizations of clients from a user N Y Y Ad hoc group call configurations [R-6.15.5.3-005] of 3GPP TS 22.280 [17] > Support of ad hoc group call (enabled/disabled) (see NOTE 3) Y Y Y [R-6.15.5.3-002] of 3GPP TS 22.280 [17] > Maximum number of participants allowed to participate in an ad hoc group call Y Y Y [R-6.15.5.3-004] of 3GPP TS 22.280 [17] > Hang timer for ad hoc group call N Y Y > Maximum duration for ad hoc group call Y Y Y > List of preferred voice codecs for ad hoc group call Y Y Y Subclause 6.2.3.7.13 of 3GPP TS 22.179 [2] > Multi-talker floor control supported Y Y Y Subclause 7.4.2.3.5 and subclause 7.4.2.3.6 > Audio mixing is performed in the UE or in the network to support multi-talker control Y Y Y [R-6.2.3.7.2-005] of 3GPP TS 22.179 [2] > Maximum number of simultaneous talkers applicable for multi-talker control N Y Y NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [19]. NOTE 2: The usage of this parameter by the MCPTT server is up to implementation. NOTE 3: If the support for ad hoc group call is disabled by the MC system then all other configurations related to ad hoc group call are not applicable. Table A.5-3: MCPTT service configuration data (off‑network) Reference Parameter description MCPTT UE MCPTT Server Configuration management server [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] Timeout value for the cancellation of an in‑progress emergency for an off‑network private call Y N Y [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] Time limit for an in-progress emergency related to an off‑network MCPTT group Y N Y [R-5.6.5-004] of 3GPP TS 22.179 [2] Max off‑network private call (with floor control) duration Y N Y [R-7.4-002] of 3GPP TS 22.179 [2] [R-7.4-003] of 3GPP TS 22.280 [17] Hang timer for private calls in off-network Y N Y [R-7.3.3-001], [R-7.3.3-002], [R-7.3.3-003] of 3GPP TS 22.179 [2] Priority hierarchy for floor control override in off-network Y N Y [R-7.3.5-001], [R-7.3.5-002], [R-7.3.5-003] of 3GPP TS 22.179 [2] Transmit time limit from a single request to transmit in a group or private call. Y N Y [R-7.3.5-001], [R-7.3.5-004] of 3GPP TS 22.179 [2] Configuration of warning time before time limit of transmission is reached (off-network) Y N Y [R-7.4-004] of 3GPP TS 22.280 [17] Configuration of warning time before hang time is reached (off-network) Y N Y [R-7.7-001], [R-7.7-003] of 3GPP TS 22.280 [17] [R-7.7-002] of 3GPP TS 22.179 [2] Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values > MCPTT private call signalling Y N Y > MCPTT private call media Y N Y > MCPTT Emergency private call signalling Y N Y > MCPTT Emergency private call media Y N Y [R-7.15-001], [R-7.7-003] of 3GPP TS 22.280 [17] Configuration of metadata to log Y N Y Annex B (informative): Local UE settings for MCPTT B.1 Local UE settings for MCPTT Table B.1-1 details local UE settings for MCPTT that represent important functionalities that may be required by MCPTT UEs, however these functionalities do not require central configuration like the parameters in annex A, so these are detailed in this annex for information to UE vendors interested in producing MCPTT UEs. The various columns in the tables have the following meanings: - Reference: Is the reference of the corresponding requirement in 3GPP TS 22.179 [2]. - Definition: A short definition of the local UE setting. Table B.1-1: Local UE settings for MCPTT Reference Definition [R-5.1.1-003] of 3GPP TS 22.280 [17] Call reception signalling method [R-5.1.1-004] of 3GPP TS 22.280 [17] Disabling of call reception signalling [R-5.8-003] of 3GPP TS 22.280 [17] Configuration of display of MCPTT ID (on/off) [R-5.8-003] of 3GPP TS 22.280 [17] Configuration of display of aliases associated with the MCPTT ID (on/off) [R-5.8-003] of 3GPP TS 22.280 [17] Configuration of display of Selected MCPTT Group (on/off) [R-5.8-003] of 3GPP TS 22.280 [17] Configuration of display of Mission Critical Organization name (on/off) [R-6.8.7.4.1-003] of 3GPP TS 22.280 [17] Configuration of the notification of an emergency alert Annex C (informative): Change history Date Meeting TDoc CR Rev Cat Subject/Comment New 2016-04 Initial version. 0.0.0 2016-04 Alignment with the following Rel-13 CRs agreed at SA6#10: CR0053(S6-160271), CR0055(S6-160307), CR0057(S6-160312), CR0058(S6-160289), CR0059(S6-160346), CR0060(S6-160335), CR0061(S6-160268), CR0062(S6-160333), CR0067(S6-160274), CR0069(S6-160313), CR0071(S6-160199), CR0072(S6-160334), CR0075(S6-160331), CR0076(S6-160269), CR0078(S6-160284), CR0079(S6-160360), CR0080(S6-160297), CR0081(S6-160332), CR0085(S6-160361), CR0088(S6-160291), CR0089(S6-160347), CR0090(S6-160310), CR0093(S6-160293), CR0094(S6-160294), CR0099(S6-160342) 0.1.0 2016-06 Implemented the following pCRs approved during SA6#11: S6-160414, S6-160475, S6-160497, S6-160499, S6-160501, S6-160508, S6-160514, S6-160518, S6-160530, S6-160532, S6-160568, S6-160571, S6-160581, S6-160584, S6-160588, and merged relevant content from S6-160489. Editorial changes: renumbering subclauses as needed; added top level subclauses where needed with editor's notes; added a few missing subclauses at level 2 with editor's notes; use actual TS numbers made available at SA plenary: 23.379 and 23.280. 0.2.0 2016-09 Implemented the following pCRs approved during SA6#12: S6-160681, S6-160698, S6-160707, S6-160790, S6-160802, S6-160828, S6-160873, S6-160908, S6-160909, S6-160921, S6-160925. Editorial changes: renumbering subclauses as needed; added a few missing headings at level 2 and level 3 with editor's notes for consistency. 0.3.0 2016-10 Implemented the following pCRs approved during SA6#13: S6-160961, S6-161016, S6-161112, S6-161113, S6-161116, S6-161124, S6-161210, S6-161211, S6-161212, S6-161219, S6-161231, S6-161249, S6-161251, S6-161258, S6-161268 Editorial changes: renumbering subclauses as needed. 0.4.0 2016-11 Implemented the following pCRs approved during SA6#14: S6-161330, S6-161522, S6-161538, S6-161564, S6-161572, S6-161584, S6-161591, S6-161595, S6-161596, S6-161597, S6-161598, S6-161607. Editorial changes: renumbering subclauses as needed. 0.5.0 2016-12 SA#74 SP-160876 Submitted for Approval at SA#74 1.0.0 2016-12 SA#74 SP-160876 MCC Editorial update for publication after TSG SA approval (SA#74) 14.0.0 2017-03 SA#75 SP-170068 0003 1 F Alignment of definitions 14.1.0 2017-03 SA#75 SP-170068 0004 2 F Alignment of group affiliation and de-affiliation requirements 14.1.0 2017-03 SA#75 SP-170068 0005 1 F Alignment of bearer management 14.1.0 2017-03 SA#75 SP-170068 0006 1 F Resolve editor's note in clause 10.6.2.8.1 14.1.0 2017-03 SA#75 SP-170069 0008 1 F Store and update affiliation status in the GMS 14.1.0 2017-03 SA#75 SP-170068 0009 2 F Duplicated reference remove 14.1.0 2017-03 SA#75 SP-170068 0011 1 F Corrections to MCPTT UE configuration data 14.1.0 2017-03 SA#75 SP-170068 0013 1 D Correction of references 14.1.0 2017-03 SA#75 SP-170068 0016 1 D Message title alignment 14.1.0 2017-03 SA#75 SP-170068 0017 3 F Resolve group ID issue for temporary group call – user regroup 14.1.0 2017-03 SA#75 SP-170068 0018 1 F Addition of definition for MCPTT ID 14.1.0 2017-03 SA#75 SP-170068 0019 F Correction of requirement reference for list of implicitly affiliated groups in MCPTT user profile config 14.1.0 2017-03 SA#75 SP-170068 0020 2 F Simultaneous floor requests 14.1.0 2017-03 SA#75 SP-170068 0021 2 F Correction on floor control 14.1.0 2017-03 SA#75 SP-170068 0022 2 F Miscellaneous corrections on term 14.1.0 2017-06 SA#76 SP-170389 0042 1 F Miscellaneous corrections to configuration 14.2.0 2017-06 SA#76 SP-170389 0043 6 F Addition of identity management server address per group 14.2.0 2017-06 SA#76 SP-170389 0049 1 F Correction in Ambient Listening 14.2.0 2017-06 SA#76 SP-170389 0050 1 F Clarifications on response in off-network 14.2.0 2017-06 SA#76 SP-170389 0062 2 F Inclusion of KMSUri to allow multiple security domains 14.2.0 2017-06 SA#76 SP-170389 0068 1 F Corrections to configuration for ambient listening 14.2.0 2017-06 SA#76 SP-170389 0069 1 F Correction to configuration for first-to-answer call 14.2.0 2017-06 SA#76 SP-170389 0070 F Corrections to Group configuration data for all MC services 14.2.0 2017-06 SA#76 SP-170340 0044 1 B MCPTT unicast media flow stop and resume 15.0.0 2017-06 SA#76 SP-170398 0063 1 D Editorial corrections in call back cancel request 15.0.0 2017-06 SA#76 SP-170340 0066 1 C Resource Management enhancements for MCPTT 15.0.0 2017-06 SA#76 SP-170340 0067 2 C Addition of Floor acknowledgement 15.0.0 2017-09 SA#77 SP-170685 0074 2 B Updating IWF-1 description 15.1.0 2017-09 SA#77 SP-170678 0075 2 A CR on MapGroupToBearer message 15.1.0 2017-09 SA#77 SP-170678 0077 1 A Corrections for configuration references 15.1.0 2018-01 SA#78 SP-170895 0079 3 B Functional model for MCPTT interconnection 15.2.0 2018-01 SA#78 SP-170896 0086 2 B Introduction of the multi-talker control 15.2.0 2018-01 SA#78 SP-170896 0087 3 B Introduction of Functional alias(es) 15.2.0 2018-01 SA#78 SP-170896 0089 1 C Multi-talker floor release message and procedure 15.2.0 2018-01 SA#78 SP-170886 0101 2 A Rejection of group call 15.2.0 2018-01 SA#78 SP-170886 0103 2 A MCPTT server PSI configuration 15.2.0 2018-01 SA#78 SP-170886 0110 1 A authorization for remotely initiated MCPTT call 15.2.0 2018-01 SA#78 SP-170890 0090 2 F Renaming of MCPTT emergency group call cancel 15.2.0 2018-01 SA#78 SP-170890 0091 1 F Renaming of MCPTT "emergency condition" 15.2.0 2018-01 SA#78 SP-170890 0093 2 F Renaming of MCPTT imminent peril group call cancel 15.2.0 2018-01 SA#78 SP-170890 0094 2 F Renaming Off-network MCPTT emergency group cancel 15.2.0 2018-01 SA#78 SP-170890 0095 2 F Adding implicit floor request IE to MCPTT emergency group call request 15.2.0 2018-01 SA#78 SP-170890 0096 3 B Server-initiated Broadcast group call release procedure 15.2.0 2018-01 SA#78 SP-170890 0107 2 F Renaming of "MCPTT emergency state cancel" and corrections to information flow 15.2.0 2018-04 SA#79 SP-180146 0112 1 A Correction of security specification references 15.3.0 2018-04 SA#79 SP-180154 0113 1 A User profile for MCPTT migration 15.3.0 2018-04 SA#79 SP-180154 0114 4 B MCPTT specific group configuration for interconnection 15.3.0 2018-04 SA#79 SP-180155 0115 3 B LMR E2EE user profile and group parameters 15.3.0 2018-04 SA#79 SP-180158 0116 2 F Introduction of MCPTT call end response message 15.3.0 2018-04 SA#79 SP-180150 0117 1 F Update of references to stage 1 specifications 15.3.0 2018-04 SA#79 SP-180154 0119 B Definition of MCPTT-3 15.3.0 2018-04 SA#79 SP-180154 0120 D Editorial correction to gateway server entity 15.3.0 2018-06 SA#80 SP-180365 0123 3 A Addition of implicit floor request IEs 15.4.0 2018-06 SA#80 SP-180365 0125 1 A Corrections to implicit floor request handling 15.4.0 2018-06 SA#80 SP-180373 0129 1 F Correction of referenced subclauses 15.4.0 2018-06 SA#80 SP-180365 0133 A Clarification for presentation priority in MCPTT UE configuration 15.4.0 2018-06 SA#80 SP-180369 0134 2 F Update of MCPTT emergency alert for multicast 15.4.0 2018-06 SA#80 SP-180369 0135 1 F Correction of Group call rejoin response 15.4.0 2018-09 SA#81 SP-180672 0137 1 F Emergency Alert Area Trigger 15.5.0 2018-09 SA#81 SP-180672 0138 1 C Location of Current Talker via Floor Request 15.5.0 2018-09 SA#81 SP-180671 0140 2 A Removal of temporary regroup procedures 15.5.0 2018-09 SA#81 SP-180672 0141 F 23.379 Table A.3-1 duplicate note 4 15.5.0 2018-09 SA#81 SP-180672 0142 1 F Correction to Chat group call pre-condition 15.5.0 2018-09 SA#81 SP-180672 0145 1 F Removal of group call notify from normal group call setup 15.5.0 2018-09 SA#81 SP-180672 0147 F Correction to chat group join mechanism 15.5.0 2018-09 SA#81 SP-180678 0143 1 B Interconnection chat group call 16.0.0 2018-09 SA#81 SP-180676 0146 1 F Issues with temporary regroup procedures 16.0.0 2019-01 SA#82 SP-181177 0148 F Correction of intended mandatory call participants 16.1.0 2019-01 SA#82 SP-181177 0149 3 C Completing availability of talker location with floor control request 16.1.0 2019-01 SA#82 SP-181177 0150 4 C MCPTT add location to emergency and imminent peril 16.1.0 2019-01 SA#82 SP-181177 0151 3 B User regroup procedure 16.1.0 2019-01 SA#82 SP-181177 0152 1 F Late entry pre-arranged group call corrections for emergency 16.1.0 2019-01 SA#82 SP-181177 0161 4 F Late entry for chat group call 16.1.0 2019-01 SA#82 SP-181177 0162 5 B Application paging 16.1.0 2019-01 SA#82 SP-181177 0163 D Spelling of ProSe 16.1.0 2019-01 SA#82 SP-181177 0164 4 B Regroup using preconfigured group 16.1.0 2019-01 SA#82 SP-181177 0166 2 F Corrections to 'general' subclause for pre-arranged and chat group call 16.1.0 2019-01 SA#82 SP-181177 0168 1 F Pre-established session corrections 16.1.0 2019-03 SA#83 SP-190073 0170 2 B Broadcast group regroup 16.2.0 2019-03 SA#83 SP-190073 0171 2 F Corrections to MCPTT chat group call late entry procedures 16.2.0 2019-03 SA#83 SP-190073 0172 2 C Procedure for MCPTT user leaving a group call 16.2.0 2019-03 SA#83 SP-190075 0174 1 F MCPTT ID in interconnection floor control 16.2.0 2019-03 SA#83 SP-190073 0175 2 C Broadcast user regroup 16.2.0 2019-03 SA#83 SP-190073 0176 2 B Group regroup broadcast and rejection using preconfigured group 16.2.0 2019-03 SA#83 SP-190073 0177 1 F Broadcast user regroup 16.2.0 2019-06 SA#84 SP-190484 0180 3 B Adding newly affiliated user to preconfigured group regroup 16.3.0 2019-06 SA#84 SP-190484 0182 3 B Broadcast group regroup call using preconfigured group 16.3.0 2019-06 SA#84 SP-190484 0183 3 B Preconfigured regroup exception cases 16.3.0 2019-06 SA#84 SP-190488 0186 1 B Restricting incoming private communications 16.3.0 2019-06 SA#84 SP-190488 0187 1 B Support of functional aliases in private calls and private emergency calls 16.3.0 2019-06 SA#84 SP-190488 0188 3 B Support of functional aliases in emergency and imminent peril groups calls 16.3.0 2019-06 SA#84 SP-190488 0189 3 B Support of functional aliases via broadcast group calls 16.3.0 2019-06 SA#84 SP-190488 0190 2 B Support of multiple functional alias use in private calls 16.3.0 2019-06 SA#84 SP-190488 0191 4 B Provide list of MCPTT group members who did not acknowledge the group call request 16.3.0 2019-06 SA#84 SP-190484 0192 3 C Preconfigured regroup cancellation on log off 16.3.0 2019-06 SA#84 SP-190482 0194 A Clarifications on functional alias controlling role 16.3.0 2019-06 SA#84 SP-190488 0195 2 B User configuration for functional alias information query for MCPTT 16.3.0 2019-06 SA#84 SP-190488 0196 1 B User requested priority in 23.379 16.3.0 2019-06 SA#84 SP-190488 0200 2 B Functional alias call 16.3.0 2019-06 SA#84 SP-190488 0202 4 B Criteria based automatic group affiliation and de-affiliation 16.3.0 2019-06 SA#84 SP-190488 0203 1 B MCPTT configuration for implicit functional alias activation/deactivation 16.3.0 2019-06 SA#84 SP-190484 0206 2 F MCPTT ID list in Group call notify 16.3.0 2019-06 SA#84 SP-190484 0207 2 F Preconfigured regroup usage 16.3.0 2019-06 SA#84 SP-190484 0208 2 F Remove the duplicated MCPTT server URI in UE configuration table 16.3.0 2019-06 SA#84 SP-190488 0210 2 B Add configuration for call forwarding for MCPTT private calls 16.3.0 2019-06 SA#84 SP-190488 0211 3 B Add call forwarding for MCPTT private calls 16.3.0 2019-06 SA#84 SP-190488 0213 1 B MCPTT server limits the number of simultaneous successful service authorisations 16.3.0 2019-06 SA#84 SP-190488 0214 1 B Additional commencement modes for group calls 16.3.0 2019-06 SA#84 SP-190488 0215 B Triggering an emergency group communication after an emergency alert automatically 16.3.0 2019-06 SA#84 SP-190488 0216 B MCPTT client performs automatic activation and deactivation of functional aliases based on location 16.3.0 2019-06 SA#84 SP-190488 0217 2 B Communication priority for functional aliases 16.3.0 2019-06 SA#84 SP-190488 0218 F Information flows for the first-to-answer call procedure 16.3.0 2019-06 SA#84 SP-190484 0220 2 B User regroup using group creation and using preconfigured group 16.3.0 2019-06 SA#84 SP-190484 0222 4 C Preconfigured regrouping enhancements 16.3.0 2019-09 SA#85 SP-190731 0223 1 F Correct the error message is sent in the MCPTT emergency group call procedures 16.4.0 2019-09 SA#85 SP-190731 0224 3 F Correct the configuration parameters for the MCPTT emergency procedures 16.4.0 2019-09 SA#85 SP-190731 0227 3 F Corrections to MCPTT emergency alert procedures 16.4.0 2019-09 SA#85 SP-190732 0228 1 F Add condition "not reachable" to call forwarding for MCPTT private calls 16.4.0 2019-09 SA#85 SP-190732 0235 1 F Making functional alias optional in floor control messages 16.4.0 2019-09 SA#85 SP-190735 0225 3 B Support of functional aliases as called party address in MCPTT emergency private calls 17.0.0 2019-09 SA#85 SP-190735 0226 2 B Call restrictions when using a specific functional alias for private calls 17.0.0 2019-09 SA#85 SP-190735 0229 7 B Add call transfer for MCPTT private calls 17.0.0 2019-09 SA#85 SP-190735 0232 1 B Functional alias of Called party in private call 17.0.0 2019-12 SA#86 SP-191109 0237 1 A Corrections to preconfigured regroup procedures 17.1.0 2019-12 SA#86 SP-191113 0238 1 B Handling the originating side of functional alias for group calls 17.1.0 2019-12 SA#86 SP-191113 0239 1 B Add missing server to server information flows for group calls 17.1.0 2019-12 SA#86 SP-191113 0240 2 F Priority of the user for initiating/receiving calls 17.1.0 2019-12 SA#86 SP-191113 0241 F Correcting stage 1 reference on maximum number of simultaneously received group calls 17.1.0 2019-12 SA#86 SP-191110 0243 1 A Receiving a private call from any other user 17.1.0 2019-12 SA#86 SP-191114 0245 1 F Alignment on MCX emergency alert procedures 17.1.0 2020-03 SA#87-E SP-200118 0246 5 B Add announced call redirection for MCPTT private calls 17.2.0 2020-03 SA#87-E SP-200118 0247 5 B Add call forwarding based on manual input for MCPTT private calls 17.2.0 2020-03 SA#87-E SP-200118 0249 2 B Add call forwarding based on manual input for MCPTT private calls 17.2.0 2020-03 SA#87-E SP-200118 0250 2 F Clarification on functional alias to group binding function 17.2.0 2020-07 SA#88-E SP-200339 0252 3 A Clarification on target recipients in first-to-answer calls 17.3.0 2020-07 SA#88-E SP-200339 0254 3 A Media security for MCPTT private call forwarding immediate 17.3.0 2020-07 SA#88-E SP-200340 0255 3 F Corrections in MCPTT private call forwarding 17.3.0 2020-07 SA#88-E SP-200340 0256 3 F Media plane security when using a functional alias as target address for private MCPTT calls 17.3.0 2020-07 SA#88-E SP-200342 0257 1 D Minor corrections of the informational elements 17.3.0 2020-07 SA#88-E SP-200342 0258 1 F Minor changes to ambient listening procedures on user indication 17.3.0 2020-07 SA#88-E SP-200342 0259 1 F Removing subscription and notification for functional alias 17.3.0 2020-07 Correction of implementation of CR0255r3 17.3.1 2020-07 Correction of implementation of CR0256r3 (clause 10.7.2.1.8 omitted) 17.3.2 2020-09 SA#88-E SP-200844 0260 3 F Clarification on user subscription, group policy and functional alias policy 17.4.0 2020-09 SA#88-E SP-200843 0261 1 F Correction of private call setup procedures when using a functional alias as target address 17.4.0 2020-09 SA#88-E SP-200843 0262 1 B MCPTT private call forwarding to a functional alias as a target 17.4.0 2020-09 SA#88-E SP-200843 0263 1 B MCPTT private call transfer to a functional alias as a target 17.4.0 2020-09 SA#88-E SP-200843 0265 1 B Limit the number of simultaneous logins on per user basis 17.4.0 2020-09 SA#88-E SP-200843 0269 1 B Call restrictions for normal private calls 17.4.0 2020-09 SA#88-E SP-200844 0270 1 F MCPTT emergency group call clarifications 17.4.0 2020-09 SA#88-E SP-200844 0271 1 F MCPTT emergency private call clarifications 17.4.0 2020-09 SA#88-E SP-200844 0276 1 F Clarifications on the use of ProSe in off-network MCPTT calls 17.4.0 2020-09 SA#88-E SP-200843 0278 1 F Functional alias private call 17.4.0 2020-12 SA#90-E SP-200995 0279 2 B Authorized user being notified about other users floor queue status 17.5.0 2020-12 SA#90-E SP-200995 0280 1 C MCPTT in-progress emergency group state cancel modification 17.5.0 2020-12 SA#90-E SP-200995 0283 1 F Minor changes to information elements and procedures 17.5.0 2020-12 SA#90-E SP-200994 0285 F Clarifications for functional alias private calls 17.5.0 2021-04 SA#91-E SP-210179 0286 1 F Private Call Transfer Corrections 17.6.0 2021-04 SA#91-E SP-210180 0288 B Authorized user clearing the entire floor request queue 17.6.0 2021-04 SA#91-E SP-210180 0290 1 F Changes to the Queue Position Info information flow description 17.6.0 2021-06 SA#92-E SP-210567 0293 F Correction to MCPTT-5 reference point description 17.7.0 2021-09 SA#93-E SP-210963 0296 1 F Removal of temporary regroup procedures 17.8.0 2021-12 SA#94-E SP-211524 0301 F Correction to MCPTT group document for interconnect 17.9.0 2021-12 SA#94-E SP-211529 0300 1 B Connection authorisation configuration data 18.0.0 2022-03 SA#95-E SP-220109 0302 F Correction of two information flow descriptions 18.1.0 2022-03 SA#95-E SP-220109 0304 F MCPTT Group ID for pre-configured group call 18.1.0 2022-06 SA#96 SP-220476 0307 1 B Update to remotely initiated call request procedure to support pre-emptive or high priority and commencement mode 18.2.0 2022-06 SA#96 SP-220476 0308 B Allow the user to restrict the dissemination of the location information – MCPTT Configuration 18.2.0 2022-06 SA#96 SP-220476 0309 1 B Auto affiliate to MCPTT group for remotely initiated MCPTT call request procedure 18.2.0 2022-09 SA#97-E SP-220923 0310 1 B Private call forwarding between several MCPTT systems 18.3.0 2022-09 SA#97-E SP-220924 0311 F Private MCPTT call to a FA user 18.3.0 2022-09 SA#97-E SP-220926 0312 2 C Updating MCPTT private call end request information elements 18.3.0 2022-09 SA#97-E SP-220926 0313 1 B Private call transfer between several MCPTT systems 18.3.0 2022-09 SA#97-E SP-220924 0314 2 C Floor control signalling over QCI 69 and QCI 65 18.3.0 2022-12 SA#98-E SP-221241 0322 1 B Description for the terms used in the Ad hoc Group Communication procedures 18.4.0 2022-12 SA#98-E SP-221241 0323 1 B Information flows for the ad hoc group call 18.4.0 2022-12 SA#98-E SP-221241 0324 1 B Ad hoc group call procedures in single MCPTT system 18.4.0 2022-12 SA#98-E SP-221241 0326 1 B Modifying participants list of on-going ad hoc group call in single MCPTT system 18.4.0 2022-12 SA#98-E SP-221241 0327 1 B Configuration parameters for Ad hoc group call 18.4.0 2023-03 SA#99 SP-230289 0328 4 B Ad hoc group call procedures involving multiple MC systems 18.5.0 2023-03 SA#99 SP-230289 0330 2 B User profile configuration data to support MCPTT ad hoc group emergency alerts 18.5.0 2023-03 SA#99 SP-230289 0332 B Information flows for the ad hoc group call procedures involving multiple MCPTT systems - Participants list determined by the MCPTT servers 18.5.0 2023-03 SA#99 SP-230289 0333 2 B Ad hoc group call procedures involving multiple MCPTT systems - Participants list determined by the MCPTT servers 18.5.0 2023-03 SA#99 SP-230289 0335 2 B Corrections to Ad hoc group call procedures 18.5.0 2023-03 SA#99 SP-230287 0336 2 B MCPTT group ID for regroup group calls 18.5.0 2023-03 SA#99 SP-230287 0337 2 C MCPTT user profile configuration parameters for location information 18.5.0 2023-03 SA#99 SP-230289 0338 1 F Correction and update to configuration parameters of Ad hoc group call for MCPTT 18.5.0 2023-03 SA#99 SP-230289 0339 2 B Notifying authorized user about adhoc group participants list 18.5.0 2023-04 Editorial correction of implementation of CR 0332r2 (S6-230219) i.e. placing of the new clause “Ad hoc group call release notification” 18.5.1 2023-06 SA#100 SP-230703 0340 1 B Notifying authorized user about adhoc group participants list 18.6.0 2023-06 SA#100 SP-230703 0341 1 C Add Criteria to Preconfigured User Regroup Request 18.6.0 2023-06 SA#100 SP-230709 0342 1 B Configuration for receiving the adhoc group emergency alert participants list notification (MCPTT) 18.6.0 2023-06 SA#100 SP-230709 0343 1 C Correcting the ad hoc group communication criteria between multiple MCPTT systems 18.6.0 2023-06 SA#100 SP-230709 0344 B Notifying authorized user about adhoc group participants list involving multiple MC systems - MCPTT 18.6.0 2023-06 SA#100 SP-230709 0345 1 B Get user list Information flows for the ad hoc group call - MCPTT 18.6.0 2023-06 SA#100 SP-230709 0346 F Use of service specific terminologies (i.e. MCPTT) and other corrections 18.6.0 2023-06 SA#100 SP-230709 0347 2 F Corrections for ad hoc group call setup 18.6.0 2023-06 SA#100 SP-230703 0348 2 F Addition of Call Release Reason code in the PES based Call Disconnect procedure 18.6.0 2023-06 SA#100 SP-230703 0349 2 F Correct MCPTT ID usage in some information flow tables 18.6.0 2023-06 SA#100 SP-230709 0350 1 F MCPTT group ID correction 18.6.0 2023-06 SA#100 SP-230709 0351 2 F Remove unnecessary information flow tables 18.6.0 2023-06 SA#100 SP-230709 0352 1 F Addressing EN related to user configuration for ad hoc MCPTT communication 18.6.0 2023-06 SA#100 SP-230703 0353 1 B User regroup MCPTT ID list update 18.6.0 2023-06 SA#100 SP-230703 0354 1 B Updates adhoc group call procedures for allowing a subsequent MCPTT call after an adhoc group emergency alert 18.6.0 2023-06 SA#100 SP-230703 0356 F Corrections to ad hoc group call setup procedure involving multiple MC system 18.6.0 2023-09 SA#101 SP-230998 0359 1 F Adding missing group definitions (MCPTT) 18.7.0 2023-09 SA#101 SP-230997 0363 2 A Floor idle alignment with stage-3 18.7.0 2023-09 SA#101 SP-230998 0368 F Floor participant and floor control server alignment in 10.9.1.3 18.7.0 2023-09 SA#101 SP-230998 0369 1 F Missing pre-conditions and steps for ad hoc group MCPTT call 18.7.0 2023-09 SA#101 SP-230998 0370 F Correcting configuration for ad hoc group MCPTT communication 18.7.0 2023-09 SA#101 SP-230999 0357 3 B Clarifications on temporary and pre-arranged MCPTT broadcast groups 19.0.0 2023-09 SA#101 SP-231002 0358 2 B Support of multi-talker floor control for ad hoc group calls 19.0.0 2023-09 SA#101 SP-231002 0360 1 B Modify list of participants by changing the criteria during an ongoing MCPTT ad hoc group call (single MC system) 19.0.0 2023-09 SA#101 SP-231002 0367 2 B Revoke the floor by the authorized user in multi-talker case 19.0.0 2023-12 SA#102 SP-231556 0371 1 C Audio mixing is performed in the UE or in the network to support multi-talker control 19.1.0 2023-12 SA#102 SP-231556 0372 2 B Changing the criteria during an ongoing MCPTT ad hoc group call (multiple MC systems) 19.1.0 2023-12 SA#102 SP-231551 0378 1 A Clarification on floor idle for multi-talker case 19.1.0 2023-12 SA#102 SP-231554 0379 1 F Resolve regroup issue - void general clause 19.1.0 2023-12 SA#102 SP-231554 0380 1 F Void preconfigured Group Regroup formation in a single MC system in 10.6.2.9.2.1 19.1.0 2023-12 SA#102 SP-231554 0381 1 F Void user regroup formation in a single MCPTT system in 10.6.2.12.2.1 19.1.0 2023-12 SA#102 SP-231554 0382 1 F Void regroup cancellation clauses in 10.6.2.9.2.2 and 10.6.2.12.2.2 19.1.0 2023-12 SA#102 SP-231554 0383 1 F Void 10.6.2.9.3.1 Regroup formation using preconfigured group in multiple MCPTT systems 19.1.0 2023-12 SA#102 SP-231554 0384 1 F Void 10.6.2.9.3.2 Regroup cancellation using preconfigured group in multiple MCPTT systems 19.1.0 2023-12 SA#102 SP-231554 0385 1 F Void 10.6.2.9.4 Adding newly affiliated user to preconfigured group regroup 19.1.0 2023-12 SA#102 SP-231554 0386 1 F Void 10.6.2.12.3 User regroup MCPTT ID list update 19.1.0 2023-12 SA#102 SP-231554 0387 2 F Update clause 10.6.2.9.5.1 and 10.6.2.9.5.2. 19.1.0 2023-12 SA#102 SP-231554 0388 2 F Void preconfigured regroup information flows 19.1.0 2023-12 SA#102 SP-231558 0390 1 F Configuration for authorising modification of ad hoc group call participants - mcptt 19.1.0 2023-12 SA#102 SP-231556 0391 1 B Configuration for authorising modification of ad hoc group emergency alert participants - mcptt 19.1.0 2023-12 SA#102 SP-231558 0393 1 A Modification of ad hoc group call participants involving multiple MCPTT systems 19.1.0 2023-12 SA#102 SP-231558 0395 1 A Correction to ad hoc group call setup procedure 19.1.0 2023-12 SA#102 SP-231558 0397 1 A Correction to modification of ad hoc group call participants procedure - mcptt 19.1.0 2023-12 SA#102 SP-231556 0399 1 F Corrections on modifying the criteria during an ad hoc group call (MCPTT) 19.1.0 2023-12 SA#102 SP-231556 0402 1 B Adhoc group call release by an authorized user (MCPTT) 19.1.0 2023-12 SA#102 SP-231556 0404 D Correction of clause title style 19.1.0 2024-03 SA#103 SP-240314 0400 2 F Correction on List of members which can talk in a multi-talker group 19.2.0 2024-03 SA#103 SP-240314 0401 2 B Change list of participants when criteria was used to setup the ad hoc group call (MCPTT) 19.2.0 2024-03 SA#103 SP-240303 0408 1 A Void the clause 10.6.2.9.3.3 19.2.0 2024-06 SA#104 SP-240768 0422 1 B Handling of emergency ad hoc group call requests 19.3.0 2024-06 SA#104 SP-240758 0424 1 A Removal of GW MC service ID 19.3.0 2024-06 SA#104 SP-240767 0425 1 F Authorization check for MCPTT in-progress imminent peril group state cancel 19.3.0 2024-06 SA#104 SP-240757 0427 1 A Ambiguity on routing private calls 19.3.0 2024-06 SA#104 SP-240768 0430 1 F Multi-talker floor control involving multiple MCPTT systems 19.3.0 2024-09 SA#105 SP-241224 0432 2 F Correcting description of IEs in MCPTT ad hoc group call 19.4.0 2024-09 SA#105 SP-241223 0433 1 F Ambient Listening during incoming or outgoing MCPTT calls 19.4.0 2024-09 SA#105 SP-241224 0435 1 F Update the pre-conditions of clause 10.19.3.1.4 19.4.0 2024-09 SA#105 SP-241224 0436 1 B Migration during Ad hoc group call procedure 19.4.0 2024-12 SA#106 SP-241722 0437 1 B Target MCPTT user configuration for recording 19.5.0 2024-12 SA#106 SP-241723 0438 1 C Adding information elements to ad hoc group call 19.5.0 2024-12 SA#106 SP-241722 0440 1 C Clarification for Location user profile for MCPPT 19.5.0 2024-12 SA#106 SP-241707 0442 A Clarification on initial floor request 19.5.0 2024-12 SA#106 SP-241707 0445 1 A Resolving an EN in the First-to-answer call setup procedure 19.5.0 2024-12 SA#106 SP-241723 0446 1 F Update the ad-hoc group call modify procedures 19.5.0 2024-12 SA#106 SP-241723 0447 1 B MCPTT control plane user plane separation 19.5.0 2024-12 SA#106 SP-241722 0448 1 B Floor remote request in emergency communication 19.5.0 2024-12 SA#106 SP-241707 0448 1 A Removing EN on MCPTT server used as signalling proxy 19.5.0 2025-03 SA#107 SP-250211 0451 1 F Floor remote request in emergency communication for private call 19.6.0
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
1 Scope
|
The present document specifies the application layer architecture and procedures to support the MMTel service, and also specifies the service enabler layer capability exposure procedures and related APIs for enablement aspects of MMTel service
This work takes into consideration the existing stage 1 and stage 2 work within 3GPP related to MMTel service specified in 3GPP TS 22.261 [2], 3GPP TS 23.228 [3] and 3GPP TS 26.114 [4].
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system".
[3] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS)".
[4] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction"
[5] GSMA NG.134: "IMS Data Channel, Version 1.0".
[6] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL)".
[7] OMA-TS-REST_NetAPI_ThirdPartyCall-V1_0-20130212-C: "RESTful Network API for Third Party Call".
[8] OMA-AD-IMS-V1_0-20050809-A: "Utilization of IMS capabilities Architecture".
[9] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[10] IETF RFC 7989 (October 2016): "End-to-End Session Identification in IP-Based Multimedia Communication Networks".
[11] OMA-TS-REST_NetAPI_Common-V1_0-20180116-A: "Common definitions for RESTful Network APIs".
[12] 3GPP TS 23.502: " Procedures for the 5G System (5GS); Stage 2".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
3 Definitions of terms, symbols and abbreviations
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
MMTel service: An MTSI service as specified in 3GPP TS 26.114 [4] with or without Data channel support.
Root application: A root page of of the Data Channel Application that the subscriber could select and use, as specified in GSMA NG.134 [5].
For the purposes of the present document, the following terms and definitions given in 3GPP TS 26.114 [4] apply:
DCMTSI client
DCMTSI client in terminal
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [3] apply:
Application data channel
Bootstrap data channel
Data channel application
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
3.2 Symbols
|
Void
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
DC Data Channel
DCMTSI Data Channel Multimedia Telephony Service for IMS
IMS IP Multimedia Core Network Subsystem
OMA Open Mobile Alliance
SIP Session Initiation Protocol
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
4 Overview
|
The MMTel Enabler provides the Application enablement for MMTel service, mainly including the following aspects:
1 DC Application management: providing the management capabilities of Data Channel Applications and data channel application profile to PLMN operators which provide MMTel service with IMS Data Channel
2 DC Application downloading control: providing the capabilities to control the downloading of Data Channel applications on UE to PLMN operators which provide MMTel service with IMS Data Channel. The downloading is controlled by the data channel application profile downloaded to the UE.
3 usage of MMTel service: providing capabilities to application providers/Vertical service provider to use MMTel service including:
a. call between application and DCMTSI client:
b. Third-Party Call;
c. Person-to-Application (P2A) Application Data Channel; and
d. Application-to-Person (A2P) Application Data Channel.
The DC Application management is specified in clause 8.2, DC Application downloading control is specified in clause 8.3, and usage of MMTel service is specified in clause 8.4.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5 Architectural requirements
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.1 General
|
This clause specifies architectural requirements for MMTel Enabler.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.2 Data Channel Application management requirements
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.2.1 Description
|
This clause specifies the Data Channel Application management requirements for MMTel Enabler.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.2.2 Requirements
|
[AR-5.2.2-a] The MMTel Enabler shall provide capability for MMTel service provider to upload, update and delete the Data Channel applications on DCAR via MMTel Enabler .
[AR-5.2.2-b] The MMTel Enabler shall provide capability for MMTel service provider to configure, update, get and deleted the Data Channel application profile on DCAR via MMTel Enabler server.
[AR-5.2.2-c] The MMTel Enabler shall provide capability for Data Channel application provider to get the Data Channel application profile information.
[AR-5.2.2-d] The MMTel Enabler shall provide capability to control the downloading of data channel applications on UE by providing data channel application profile to UE.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.3 MMTel service enablement requirements
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.3.1 Description
|
This clause specifies the MMTel service enablement requirements for MMTel Enabler.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
5.3.2 Requirements
|
[AR-5.3.2-a] The MMTel Enabler shall provide capability for application without IMS capabilities to establish, modify or terminate a call with an Application supporting MMTel service.
[AR-5.3.2-b] The MMTel Enabler shall provide capability for application providers/Vertical service provider to use MMTel service including establish, modify or terminate a:
a. call between application and DCMTSI client:
b. Third-Party Call;
c. Person-to-Application (P2A) Application Data Channel; and
d. Application-to-Person (A2P) Application Data Channel
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6 Architecture
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.1 General
|
This clause specifies the architecture of MMTel Enabler.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.2 MMTel Enabler architecture
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.2.1 General
|
Figure 6.2-1 shows the MMTel Enabler architecture.
In this release, the MMTel Enabler Server is hosted within the PLMN operator network which supports the MMTel services capabilities exposure.
Figure 6.2.1-1: MMTel Enabler architecture
The MMTel functional entities on the UE and the server sides are MMTel Enabler Client and MMTel Enabler Server respectively.
The MMTel Enabler Client communicates with the MMTel Enabler Server over the MMTel-1 reference point to support the application layer interactions needed in MMTel service.
NOTE The interaction between MMTel Enabler Client and DCMTSI Client.is internal interaction in the dialler application on the UE and implementation specific.
The MMTel Enabler Client also communicates with the DCMTSI client over the MMTel-4 reference point to downloading behavior on DCMTSI Client based on the application policy provided by the MMTel Enabler Server. The DCMTSI client is specified in 3GPP TS 26.114 [4].
The Application Server communicates with the MMTel Enabler Server over the MMTel-2 reference point to invoke the MMTel service related capabilities provided by MMTel Enabler Server,
The Controlling Application Server communicates with the MMTel Enabler Server over the MMTel-3 reference point to manage the information needed in MMTel service.
The Application Server communicates with the Application Client on the UE over the App-1 reference point to provide the Data Channel Application specific logic.
The MMTel Enabler Client(s) interacts with SEAL Clients over the SEAL-C reference point specified for each SEAL service. The MMTel Enabler Server(s) interacts with SEAL Servers over the SEAL-S reference point specified for each SEAL service. The interaction between a SEAL Client and the corresponding SEAL Server is supported by SEAL-UU reference point specified for each SEAL service as specified in 3GPP TS 23.434 [6].
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.2.2 MMTel Enabler Server architecture model supporting IMS Session Management
|
The MMTel Enabler Server provides MMTel services capabilities including IMS Session Management capabilities and Data Channel related capabilities to Application Server.
NOTE 1: The MMTel Enabler Server architecture model supporting IMS Session Management will be updated after the IMS Session management capabilities provided by NEF is specified by SA2.
Figure 6.2.2-2: Option2: MMTel Enabler Server supports OMA OSE
Figure 6.2.2-1 shows the relationship between MMTel Enabler Server and IMS. The MMTel Enabler Server supports OMA Enabler, and interacts with IMS by using either:
a. IMS elements interfaces specified in.3GPP TS 23.228 [3] and OMAIMS [8]; or
b. implementation specified interfaces.
NOTE 2: The detailed interaction between MMTel Enabler Server and IMS is out of scope of the present document.
NOTE 3: The architecture to support the IMS Session Management will be updated if new capabilities are provided by IMS.
The MMTel Enabler Server interacts with IMS via N33/DC4/MDC2/MDC3 reference points to utilize the Data Channel related capabilities provided by IMS as specified in 3GPP TS 23.228 [3].
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3 Functional entities
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.1 General
|
The functional entities for MMTel Enabler are described in the following subclauses.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.2 MMTel Enabler Server
|
The MMTel Enabler Server provides the server side functionalities corresponding to the MMTel service.
The MMTel Enabler Server supports:
- the Application Server and Controlling Application Server to discover, to authenticate and to get authorization the MMTel/MMTel service APIs provided by the MMTel Enabler Server;
- the interaction with Controlling Application Server to configure the DC application profile;
- the integration of the multiple network layer capabilities provided by the underlying network, including the 3GPP core network and IMS into one service enabler layer API. The MMTel Enabler Server exposes these service enabler layer APIs to the Application Server and Controlling Application Server instead of exposes the network layer capabilities directly. The capabilities provided by the underlying network include:
a) the APIs provided by DCSF via DC3/N33 reference point;
b) the APIs provided by DCSF via DC4 reference point; and
c) the APIs provided by MF/MRF via MDC3/MDC4 reference points;
NOTE: in this release, the MMTel Enabler Server interacts with IMS via IMS elements interfaces specified in 3GPP TS 23.228 [3] or implementation specified interfaces;
- the communication with the corresponding functions in the underlying network on behalf of the Application Server and Controlling Application Server when the capabilities provided by the underlying network are needed to be invoked;
- the interaction with MMTel Enabler Client for exchanging service configuration related information, e.g. the DC application profile, needed in MMTel service,
- providing MMTel/MMTel specific value added services which can be used by the Application Server in the mmtel communication between UE and Application Server;
- the interaction with SEAL functionalities to use the corresponding SEAL services in MMTel service, e.g. to use SEAL notification management service to update of DC application profiles to UE;
- the storage of the application layer information associated with the MMTel services;
- the media function to support the media handling/translation, e.g. acts as a media gateway of WebRTC or if supported media type of application is different with the UE;
- the HTTP Proxy to support the establishes a Bootstrap data channel and application data channel, e.g. if the address type of application is different with the UE, e.g. IPv4 and IPv6, etc;
- providing call control handling consolidation when receiving call control requests from multiple Application Servers, e.g. to merge same control commands, to reject call control requests from certain Application Server with low priority when conflict happens or to decide the call control request execution sequence, etc; and
- acting as CAPIF API provider domain functions as specified in 3GPP TS 23.222 [9] and interacts with CAPIF core function via CAPIF-3/3e/4/4e/5/5e reference points.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.3 MMTel Enabler Client
|
The MMTel Enabler Client provide the client side functionality needed in MMTel service.
The MMTel Enabler Client interact with DCMTSI Client in the same UE to control the downloading behavior on DCMTSI Client based on the DC application profiles provided by the MMTel Enabler Server.
NOTE 1: the DCMTSI client is responsible for creating bootstrap channel and actually downloading the data channel applications.
NOTE 2 The interaction between MMTel Enabler Client and DCMTSI Client.is internal interaction in the dialler application on the UE and implementation specific.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.4 Application Server
|
The Application Server communicates with the MMTel Enabler Server over the MMTel-2 reference point to invoke the MMTel service related capabilities to communicate with the UE, e.g. establishes a MMTel session with or without IMS data channel to the UE, or establishes an application data channel to the UE. It may also communicate with Application Client to provide Application specific logic.
NOTE: The Application Server needs to support MMTel-2 reference point, but the detailed functionalities of the Application Server is out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.5 Controlling Application Server
|
The Controlling Application Server is a specific Application Server that only used by the MMTel service provider, i.,e. MNO, to manage the service configuration related information, e.g. DC application profiles, needed in MMTel service. It communicates with the MMTel Enabler Server over the MMTel-3 reference point to invoke the MMTel service related capabilities and does not interacts with Application Client on the UE directly.
NOTE: The functionalities of the Controlling Application Server is out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.6 Application Client
|
The Application Client is an entity in the application layer to implement and perform the application service logic for its own service.
NOTE: The Application Client can be the data channel application client. The functionalities of the Application Client is out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.7 SEAL Client
|
The following SEAL Clients for MMTel enablement service are supported:
- Notification management client as specified in clause 17 of TS 23.434 [6];
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.3.8 SEAL server
|
The following SEAL servers for MMTel enablement service are supported:
- Notification management server as specified in clause 17 of TS 23.434 [6];
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4 Reference points
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.1 General
|
The reference points for MMTel Enabler are described in the following subclauses.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.2 MMTel-1 (between the MMTel Enabler Client and the MMTel Enabler Server)
|
The MMTel-1 reference point supports the interactions between a MMTel Enabler Client and the corresponding MMTel Enabler Server. This reference point supports:
- the MMTel Enabler Client to download the DC application profile from MMTel Enabler Server;
- the MMTel Enabler Server notifies the MMTel Enabler Client in the UE to send application request messages to the MMTel Enabler Server to request the profiles of data channel applications; and
- the MMTel Enabler Server sends the profiles to the UE directly after the UE subscribes to the profile notification
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.3 MMTel-2 (between the MMTel Enabler Server and the Application Server)
|
The interactions between the Application Server and the underlying network are provided by the MMTel Enabler Server via MMTel-2 reference point to ensure the security access of the underlying network. This reference point supports:
- the Application Server to discover MMTel service APIs, to authenticate, to get authorization and to communicate with the MMTel service; and
- to provide the MMTel calling API with Data Channel capability to the Applications to use the MMTel service.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.4 MMTel-3 (between the MMTel Enabler Server and the Controlling Application Server)
|
The interactions between the MMTel Enabler Server and the Controlling Application Server are referred to MMTel-3 reference point. This reference point supports:
- the Controlling Application Server to manage the service configuration related information needed in MMTel service; and
- the Controlling Application Server to get the DC application profile information from the MMTel Enabler Server.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.5 MMTel-4 (between the MMTel Enabler Client and the DCMTSI client)
|
The interaction between MMTel Enabler Client and DCMTSI Client. are referred to MMTel-4 reference point. This reference point is internal interaction in the dialler application on the UE and implementation specific.
NOTE: The functionalities of the MMTel-4 reference point is out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.6 App-1 (between the Application Client and the Application Server)
|
The App-1reference point supports the communication between Application Client and Application Server to provide the Data Channel Application specific logic.
NOTE: The functionalities of the App-1 reference point is out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.7 SEAL-C
|
The following SEAL-C reference points for MMTel enablement service are supported:
- NM-C reference point for notification management as specified in 3GPP TS 23.434 [6];
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.8 SEAL-S
|
The following SEAL-S reference points for MMTel enablement service are supported:
- NM-S reference point for notification management as specified in 3GPP TS 23.434 [6];
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
6.4.9 SEAL-UU
|
The following SEAL-UU reference points for MMTel enablement service are supported:
- NM-UU reference point for notification management as specified in 3GPP TS 23.434 [6];
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
7 Identities
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
7.1 General
|
The following clauses list identities that are used in this technical specification.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
7.2 Application ID (APPID)
|
The APPID is a globally unique value that identifies a Data Channel Application. It is assigned by the MMTel Enabler Server. The value of this IE is also used to set the "req-app-id" parameter in "a=3gpp-req-app" media-level SDP attribute as specified in 3GPP TS 26.114 [4] when the application requests application data channel(s).
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8 Procedures and information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.1 General
|
This clause provides procedures and information flows necessary for application enablement aspects for MMTel including information elements used in the procedures.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2 DC application and profile management
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.1 General
|
The following clauses specify procedures and information flows for DC application and profile management.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2 DC application and profile configuration
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2.1 General
|
DC application and profile configuration enables a Controlling Application Server to configure the DC application and profile with the MMTel Enabler Server.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2.2 Procedure
|
Figure 8.2.2.2-1 illustrates the DC application and profile configuration procedure.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and configured with the necessary credentials to enable authenticating one another.
3. Both DC application and profile have been uploaded to Controlling Application Server.
Figure 8.2.2.2-1: DC application and profile configuration
1. The Controlling Application Server sends a DC application and profile configuration request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.2.2.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server initiates authentication procedures with the Requester Identity. If the registration is successful, the MMTel Enabler Server allocates an APPID and creates the DC application profile for each DC Application included in the DC application and profile configuration request, and maintain the mapping of APPID and DC Application Profile.
3. The MMTel Enabler Server configures the DC application and profile on DCAR.
4. The MMTel Enabler Server sends a DC application and profile configuration response to the Controlling Application Server. The response message includes information elements as specified in clause 8.2.2.3.2.
Editor's note: The detailed interactions between the MMTel Enabler Server and DCAR are FFS.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2.3.1 DC application and profile configuration request
|
Table 8.2.2.3.1-1 describes information elements for the DC application and profile configuration request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.2.3.1-1: Information elements in DC application and profile configuration request
Information element
Status
Description
Requester Identity
M
The identity of the DC Application provider
(VAL service provider) performing the request.
Security credentials
O
Security information required by the MMTel Enabler Server.
Number of DC Application included
M
Indicates total number of DC Application included in this request
DC Application list
M
A list of DC application and configuration parameters included in this request. Each element in this list contains a Data Channel Application package and corresponding configuration parameters.
The detailed information elements of DC application are listed in Table 8.2.2.3.1-2.
Table 8.2.2.3.1-2: Information elements in DC application list
Information element
Status
Description
Application Identifier
M
Identifier of the Data Channel Application assigned by the Application Provider
Application Name (see NOTE 1)
O
Name of the Data Channel Application
Service Type
O
Service type of the Data Channel Application, used to help the user understand the type of services provided by the application
Application Icon Url
O
Icon url of the Data Channel Application
Application Version (see NOTE 1)
O
The newest version of the application.
Application Validity
O
The latest validity of the application.
Application Loading Phase
O
Indicates when this Data Channel Application is allowed to be used. The values of this IE include:
Precall only:the Data Channel Application is allowed to be used before the MMTel call session is established, i.e. after the 18x response is sent/received and before the 200 OK of the initial SIP INVITE request is sent/received.
Incall:the Data Channel Application is allowed to be used after the MMTel call session is established, i.e. after the 200 OK of the initial SIP INVITE request is sent/received.
Precall+Incall: the Data Channel Application is allowed to be used during the entire Precall and incall.
Autoload (see NOTE 3)
O
Indicates whether this Data Channel Application is needed to be load to the UE automatically.
Autolaunch (see NOTE 3)
O
Indicates whether this Data Channel Application is needed to be downloaded to the UE and run automatically.
If Work Without Peer DC (see NOTE 2)
O
Indicates whether this Data Channel Application can be used if Data Channel is not supported by the other party of the call.
Supported Scenario (see NOTE 2)
O
Indicates supported media type required for this Data Channel Application. The values of this IE include:
Voice call only: this Data Channel Application can be used if and only if the corresponding call is a voice call.
Video call only: this Data Channel Application can be used if and only if the corresponding call is a video call.
Voice and video call: this Data Channel Application can be used in both voice call and video call.
Condition (see NOTE 2)
O
Indicates whether this Data Channel Application can be used if under this condition. The values of this IE include but not limited:
Service area: the application is allowed to be used in a certain area.
Time period: the application is allowed to be used for a certain period of time.
3gpp Qos Hint (see NOTE 2)
O
Indicates the QoS requirement of this Data Channel Application which is used to set the value of “a=3gpp-qos-hint” attribute in SDP for the data channel(s) used by the application.
PersonalDataCollection (see NOTE 4)
O
Indicates whether this Data Channel Application will collect the user personal data (along with related consent opt-in/opt-out procedures).
PersonalDataCollectionInfoURL (see NOTE 4)
O
URL to retrieve the description of the purpose of mandatory and optional personal data to be collected, their processing their protection etc.
Application Package (see NOTE 1)
O
The Code package of the Data Channel Application.
NOTE 1: This IE shall be present when when configuring the DC application.
NOTE 2: This IE shall be present when when configuring the DC application profile.
NOTE 3: These IEs can be applied only if the specific service using this data channel application is agreed to be used by the user based on the subscription of this specific service, or explicitly agreed to be applied by the user on the UE. The relationship with PersonalDataCollection should be considered, which is out of 3GPP scope.
NOTE 4: These IEs are mandatory when regulatory requirements request that the user has to be informed if the personal data are collected by the application and how they are treated.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.2.3.2 DC application and profile configuration response
|
Table 8.2.2.3.2-1 describes information elements for the DC Application and profile configuration response from the MMTel Enabler Server.
Table 8.2.2.3.2-1: Information elements for DC application and profile configuration response
Information element
Status
Description
DC application and profile configuration response list
M
A list of DC application and profile configuration response.
This list contains a response for each DC Application. The detailed information is listed in Table 8.2.2.3.2-2.
Table 8.2.2.3.2-2: Information elements in DC application and profile configuration response list
Information element
Status
Description
Application Identifier
M
Identifier of the Data Channel Application assigned by the Application Provider.
Successful response
O
Indicates the success of the configuration of this DC application and profile
> APPID
M
Identifier of the Data Channel Application assigned by the MMTel Enabler Server
Failure response
O
Indicates the failure of the configuration of this DC application and profile
> Reason
O
Indicates the reason for failure.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.3 DC application and profile update
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.3.1 General
|
DC application and profile update enables a Controlling Application Server to update the DC application and profile with the MMTel Enabler Server.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.3.2 Procedure
|
Figure 8.2.3.2-1 illustrates the DC application and profile update procedure.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and configured with the necessary credentials to enable authenticating one another.
Figure 8.2.3.2-1: DC application and profile update
1. The Controlling Application Server sends a DC application and profile update request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.2.3.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server initiates authentication procedures with the Requester Identity. If the registration is successful, the MMTel Enabler Server updates the DC Application or DC application profile for each DC Application based on information provided in the request.
3. The MMTel Enabler Server updates the DC application and profile to DCAR.
4. The MMTel Enabler Server sends a DC application and profile update response to the Controlling Application Server. The response message includes information elements as specified in clause 8.2.3.3.2.
Editor's note: The detailed interactions between the MMTel Enabler Server and DCAR are FFS.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.3.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.3.3.1 DC application and profile update request
|
Table 8.2.3.3.1-1 describes information elements for the DC application and profile update request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.3.3.1-1: Information elements in DC application and profile update request
Information element
Status
Description
Requester Identity
M
The identity of the DC Application provider
(VAL service provider) performing the request.
Security credentials
O
Security information required by the MMTel Enabler Server.
Number of DC Application included
M
Indicates total number of DC Application included in this request
DC Application list
M
A list of DC application and configuration parameters included in this request. Each element in this list contains a Data Channel Application package and corresponding configuration parameters.
The detailed information elements of DC application and profile are listed in Table 8.2.2.3.1-2.
Table 8.2.3.3.1-2: Information elements in DC application list
Information element
Status
Description
APPID
M
Identifier of the Data Channel Application
Application Name
O
Name of the Data Channel Application
Service Type
O
Service type of the Data Channel Application, used to help the user understand the type of services provided by the application
Application Icon Url
O
Icon url of the Data Channel Application
Application Version
O
The newest version of the application.
Application Validity
O
The latest validity of the application
Application Loading Phase
O
Indicates when this Data Channel Application is allowed to be used. The values of this IE include:
Precall only:the Data Channel Application is allowed to be used before the MMTel call session is established, i.e. after the 18x response is sent/received and before the 200 OK of the initial SIP INVITE request is sent/received.
Incall:the Data Channel Application is allowed to be used after the MMTel call session is established, i.e. after the 200 OK of the initial SIP INVITE request is sent/received.
Precall+Incall: the Data Channel Application is allowed to be used during the entire Precall and incall.
Autoload
O
Indicates whether this Data Channel Application is needed to be load to the UE automatically.
Autolaunch
O
Indicates whether this Data Channel Application is needed to be downloaded to the UE and run automatically.
If Work Without Peer DC
O
Indicates whether this Data Channel Application can be used if Data Channel is not supported by the other party of the call.
Supported Scenario
O
Indicates supported media type required for this Data Channel Application. The values of this IE include:
Voice call only: this Data Channel Application can be used if and only if the corresponding call is a voice call.
Video call only: this Data Channel Application can be used if and only if the corresponding call is a video call.
Voice and video call: this Data Channel Application can be used in both voice call and video call.
Condition
O
Indicates whether this Data Channel Application can be used if under this condition. The values of this IE include but not limited:
Service area: the application is allowed to be used in a certain area.
Time period: the application is allowed to be used for a certain period of time.
3gpp Qos Hint
O
Indicates the QoS requirement of this Data Channel Application which is used to set the value of “a=3gpp-qos-hint” attribute in SDP for the data channel(s) used by the application.
PersonalDataCollection
O
Indicates whether this Data Channel Application will collect the user personal data (along with related consent opt-in/opt-out procedures).
PersonalDataCollectionInfoURL
O
URL to retrieve the description of the purpose of mandatory and optional personal data to be collected, their processing their protection etc.
Application Package (see NOTE 2)
O
The Code package of the Data Channel Application.
NOTE 1: At least one of these optional IEs is present in the update request. A special case. When the application is updated, the request must carry the application package and application version.
NOTE 2: The Application Package also support incremental updates.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.