hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
206be7a57129464f73be1aa9d853095b | 23.283 | 10.1.2.2 Group affiliation to a group defined in the MC system | The LMR system may affiliate its group members to an interworking group defined in the MC system via the IWF.
For group regroup, the affiliated group members are automatically affiliated to the temporary group.
The signalling procedure of interworking group affiliation is described in figure 10.1.2.2-1.
Pre-conditions:
1. The group to be affiliated to is defined in the MC system.
2. The IWF is connected to and is authorized to interwork with the MC system.
3. The interworking group information is available at the IWF.
4. The mapping relationship of group and user identities between MC system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system
1. The IWF sends an IWF group affiliation request to the MC service server on behalf of the LMR system.
2a. The MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then the MC service server requests the group policy from the group management server.
2b. The MC service server receives the group policy from the group management server.
3. Based on the group policy, the MC service server checks if the MC service group(s) is not disabled and if the user identified by the MCPTT ID supplied by the IWF is authorised to affiliate to the requested MC service group(s).
4. Based on the group policy and user subscription, the MC service server affiliates the IWF to the group. If a separate affiliation for each LMR user is expected, the status of the affiliating user is stored by the MC service server as the status associated with an MC service ID provided by the IWF that corresponds to the identity of that LMR user. If a separate affiliation for each LMR user is not expected, an affiliation status for the group using the MC service ID provided by the IWF is stored.
5. The MCPTT server sends the group affiliation status update message to the group management server, the group management server stores and updates the group affiliation status.
6. The MC service server returns an IWF group affiliation response to the IWF.
NOTE 2: How the LMR user(s) affiliates to a group is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.1.2.3 Group de-affiliation from a group defined in the MC system | The signalling procedure of interworking group de-affiliation from a group defined in the MC system is described in figure 10.1.2.3-1.
The LMR system manages the individual de-affiliation requests from the LMR users. The LMR system can de-affiliate its group members from the interworking group via the IWF.
Pre-conditions:
1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
2. The affiliation procedure described in subclause 10.1.2.2 was previously performed.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.3-1: Group de-affiliation from group defined in the MC system
1. The IWF sends an IWF group de-affiliation request to the MC service server on behalf of the LMR system.
2. If a separate de-affiliation from each LMR user is expected and based on the group policy and user subscription, the MC service server may de-affiliate the LMR group member from the group. Further, the MC service server may store the affiliation status of the user(s) for the requested MC service group(s). If a separate de-affiliation from each LMR user is not expected, the de-affiliation signalling de-affiliates the IWF and therefore the entire LMR system from the group.
3. The MC service server sends the group de-affiliation status update message to the group management server, the group management server stores and updates the group affiliation status.
4. The MC service server returns an IWF group de-affiliation response to the IWF.
NOTE 2: How the LMR user(s) de-affiliate from a group is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.1.2.4 Group affiliation to group defined in the LMR system | The MC system may affiliate its group members to an interworking group defined in the LMR system via the IWF.
The signalling procedure of group affiliation via the IWF is described in figure 10.1.2.4‑1.
Pre-conditions:
1. The group to be affiliated to is defined in the LMR system.
2. The IWF is connected to and is authorized to work with the MC system.
3. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.4-1: Group affiliation to group defined in the LMR system
1. The MC service client sends a MC service group affiliation request, including the MC service group ID(s), to the MC service server.
2. The MC service server checks if the MC service group ID(s) is an interworking group defined in the LMR system.
3. The MC service server sends an IWF group affiliation request to the IWF.
NOTE 2: The IWF can forward the request to the LMR system that could check whether the MC service client is authorized to affiliate to this interworking group.
NOTE 3: The IWF can reject the affiliation if the MC service group ID is either unknown to the IWF or not mapped to an LMR group identity in the IWF configuration.
4. The IWF returns an IWF group affiliation response to the MC service server, informing the successful affiliation to the LMR group.
5. The MC service server stores the group affiliation status of the MC service client for the requested interworking group.
6. The MC service server sends an MC service group affiliation response to the MC service client.
NOTE 4: How the affiliation is conducted on the LMR system is outside the scope of the present document.
NOTE 5: If an MC service client is implicitly affiliated to an MC service group defined in the LMR system the MC service server only performs steps 3, 4, and 5. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.1.2.5 Group de-affiliation from a group defined in the LMR system | The signalling procedure of interworking group de-affiliation from a group defined in the LMR system is described in figure 10.1.2.5-1.
The MC system manages the individual de-affiliation requests from the MC service users. The MC system may de-affiliate its group members from the interworking group via the IWF.
Pre-conditions:
1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF.
2. The affiliation procedure described in subclause 10.1.2.4 was previously performed.
NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.1.2.5-1: Group de-affiliation from a group defined in the LMR system
1. The MC service client of the MC service user sends an MC service group de-affiliation request to the MC service server. The MC service client shall provide the initiating MC service ID and the MC service group ID(s) being de-affiliated from.
2. Based on the user subscription and stored group policy, the MC service server checks if the user of the MC service client is affiliated to the requested MC service group(s). The MC service server checks if the MC service group(s) is an interworking group.
3a. If the MC service group(s) is an interworking group, the MC service server sends an IWF group de-affiliation request to the IWF.
3b. The IWF returns an IWF group de-affiliation response to the MC service server.
4. If the user of the MC service client is authorized to de-affiliate from the requested MC service group(s), the MC service server removes the affiliation status of the user for the requested MC service group(s).
5. The MC service server returns an MC service group de-affiliation response to the MC service client.
NOTE 2: If an MC service client is implicitly de-affiliated from an MC service group defined in the LMR system the MC service server only performs steps 3a, 3b, and 4. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2 Group management | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1 Information flows for group management | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.1 General | The following subclauses define information flows for group management on the IWF-1 interface. Group management related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.2 IWF group regroup teardown notification | Table 10.2.1.2-1 describes the information flow IWF group regroup teardown notification between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.2-1: IWF group regroup teardown notification
Information element
Status
Description
MC service group ID
M
MC service group ID of the temporary group which is torn down |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.3 IWF group regroup teardown notification response | Table 10.2.1.3-1 describes the information flow IWF group regroup teardown notification response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.3-1: IWF group regroup teardown notification response
Information element
Status
Description
MC service group ID
M
MC service group ID of the temporary group which was torn down
Result
M
Indicates success or failure of the notification |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.4 IWF group regroup request | Table 10.2.1.4-1 describes the information flow IWF group regroup request between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.4-1: IWF group regroup request
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.5 IWF group regroup response | Table 10.2.1.5-1 describes the information flow IWF group regroup response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.5-1: IWF group regroup response
Information element
Status
Description
MC service group ID
O (see NOTE)
MC service group ID of the temporary group
MC service group ID list
M
List of constituent MC service group IDs.
Result
M
Indicates whether the IWF group regroup was accepted or rejected.
NOTE: Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.6 IWF group regroup notification | Table 10.2.1.6-1 describes the information flow IWF group regroup notification between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.6-1: IWF group regroup notification
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs
MC service group ID
M
MC service group ID of the temporary group
Priority level
O
Required priority level for the temporary group
Security level (see NOTE)
O
Required security level for the temporary group
NOTE: Security level refers to the configuration of media and floor control protection parameters as listed in 3GPP TS 23.280 [5] |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.7 IWF group regroup notification response | Table 10.2.1.7-1 describes the information flow IWF group regroup notification response between the group management server and the IWF or between the IWF and the group management server.
Table 10.2.1.7-1: IWF group regroup notification response
Information element
Status
Description
MC service group ID list
M
List of constituent MC service group IDs
MC service group ID
M
MC service group ID of the temporary group
Priority level
M
Required priority level for the temporary group
Security level
M
Required security level for the temporary group |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.8 IWF group information request | Table 10.2.1.8-1 describes the IWF group information request from the IWF to the group management server or from the group management server to the IWF.
Table 10.2.1.8-1: IWF group information request
Information element
Status
Description
MC service group ID
M
The identity of the MC service group. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.9 IWF group information response | Table 10.2.1.9-1 describes the IWF group information response from the group management server to the IWF or the IWF to the group management server.
Table 10.2.1.9-1: IWF group information response
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
MC service group provisioning information
O (see NOTE 1)
The group information retrieved from the group management server or from the IWF in the case where the IWF is performing the provision.
Result
O (see NOTE 2)
Indicates reason for failure to provide MC service group configuration information
NOTE 1: Shall be present if the request can be fulfilled.
NOTE 2: Shall be present if the request cannot be fulfilled. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.10 IWF group information provision request | Table 10.2.1.10-1 describes the IWF group information provision request from the group management server to the IWF or the IWF to the group management server.
Table 10.2.1.10-1: IWF group information provision request
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
MCPTT group configuration information
M
The group information retrieved from the group management server or from the IWF in the case where the group is defined in the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.11 IWF group information provision response | Table 10.2.1.11-1 describes the IWF group information provision response from the IWF to the group management server or from the group management server to the IWF.
Table 10.2.1.11-1: IWF group information provision response
Information element
Status
Description
MC service group ID
M
The identity of the MC service group.
Result
M
Indicates success or failure of reception, modification and storage of MC service group configuration information |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.12 IWF group information subscribe request | Table 10.2.1.12-1 describes the information flow IWF group information subscribe request from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Table 10.2.1.12-1: IWF group information subscribe request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC services requested
O
Service(s) for which group configuration is requested; one or more of MCPTT, MCData |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.13 IWF group information subscribe response | Table 10.2.1.13-1 describes the information flow IWF group information subscribe response from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Table 10.2.1.13-1: IWF group information subscribe response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates success or failure of the subscribe request |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.14 IWF group information notify request | Table 10.2.1.14-1 describes the information flow IWF group information notify request from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Table 10.2.1.14-1: IWF group information notify request
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
MC service group information reference (see NOTE)
O
Reference to information stored relating to the MC service group
Group related key material (see NOTE)
O
Key material for use with the MC service group
NOTE: At least one of these information elements shall be present. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.1.15 IWF group information notify response | Table 10.2.1.15-1 describes the information flow IWF group information notify response from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Table 10.2.1.15-1: IWF group information notify response
Information element
Status
Description
MC service group ID
M
MC service group ID of the group
Result
M
Indicates success or failure of the notification request |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2 Group regrouping | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.1 General | The procedures in 3GPP TS 23.280 [5] are followed, but with changes required for interworking. The IWF will behave on the interface as if it is a peer MC service server with a peer group management client and peer group management server.
Exceptions to the 3GPP TS 23.280 [5] procedures are detailed in the subclauses below. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.2 MC system initiates the group regroup | The MC system can initiate a group regroup that includes groups defined at the IWF. The IWF is informed and may reject the regroup if conditions do not allow it to support the regroup. This is described in figure 10.2.2.2-1.
Pre-conditions:
1. The group management client has retrieved the group configurations of the groups to be regrouped.
2. At least one MC service group has been defined in the MC system.
3. At least one MC service group has been defined in the IWF.
Figure 10.2.2.2-1: Group regrouping to an IWF
1. The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server (which is the group management server of one of the MC service groups to be regrouped). The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group.
2. The group management server checks whether group regroup operation is performed by an authorised MC service user, based on group policy. The group management server checks whether the group is a temporary group. If the group is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed.
3. The group management server forwards the IWF group regroup request to the IWF with the information about the IWF's groups.
4. The IWF provides an IWF group regroup response. Due to security aspects concerning sharing information among different MC systems, the IWF does not share the users' information of the groups under its management to the group management server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping)
5. The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the authorised MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups.
6. The group management server notifies the IWF about its group regroup operation.
NOTE: How the IWF uses the MC service group ID that identifies the temporary group is outside the scope of the present document.
7. The IWF acknowledges the group management server.
8. The group management server notifies the MC service server of the temporary group creation with the information of the constituent groups.
9. The MC service server acknowledges the notification from the group management server.
10. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of lower security level.
11. The group management server provides a group regroup response to the group management client of the authorised MC service user (e.g. dispatcher). |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.3 IWF initiates the group regroup | The procedure in 3GPP TS 23.280 [5] is followed, except for steps 1 and 2. The IWF will behave on the interface as if it is a peer MC service server with a peer group management server. This is described in figure 10.2.2.3-1.
Pre-conditions:
1. At least one MC service group has been defined in the MC system.
2. At least one MC service group has been defined in the IWF.
Figure 10.2.2.3-1: Group regrouping from an IWF
1. The IWF sends an IWF group regroup request to the group management server.
2. The group management server checks whether the group can be included in a temporary group.
3. The group management server provides an IWF group regroup response.
NOTE: Due to security aspects concerning sharing information among different systems, the group management server does not share the users' information of the groups under its management to the IWF.
4. The IWF notifies the group management server regarding the temporary group creation with information of the constituent groups.
5. The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups.
6. The MC service server acknowledges the notification from the group management server. The MC service server may reject the IWF group regroup, e.g. if one of its constituent groups is already in a regroup.
7. The group management server acknowledges the notification from the IWF.
8. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of a lower security level. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.4 Ownership of the group regroup | The group management server that performs the group regroup operation owns the temporary group created by the regroup, as implied in 3GPP TS 23.280 [5]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.5 Simultaneous group regroup requests from each side of the IWF-1 interface | To prevent routing issues and complexity that could result from regrouping the same users from both sides of the interface, the following rules can be applied:
- If group regrouping signalling using temporary groups is used on the MC system, the IWF must prevent the regroup signalling from propagating to the LMR system if the LMR system does not support regrouping;
- the IWF must handle the translation between temporary group identities on the MC system and the original interworking group identities used on the LMR system; and
- the regrouping rules in subclause 10.2.4.4 of 3GPP TS 23.280 [5] also apply. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.2.6 Resolution of vocoder and encryption mode for the group regroup | If one of the LMR groups to be included in a group regroup requires the use of LMR E2EE the preferred voice codecs for an MCPTT temporary group should be LMR codecs. If any of the mission critical users to be included in this MCPTT temporary group do not support LMR E2EE or the preferred LMR codecs, voice calls using LMR E2EE will fail for those users.
NOTE 1: How the MC system determines that the temporary group needs to support LMR E2EE is outside the scope of the present document.
NOTE 2: How the MC system determines that the temporary group needs to support an LMR codec is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3 Group configuration for interworking | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.1 Overview | The procedures in the following subclauses describe the process for sharing group configuration from an MC system to an IWF where the IWF needs to make use of the MC service group and from an IWF to an MC system where the MC system's clients need to make use of the group. The procedures in this subclause are based upon subclause 10.2.7 in 3GPP TS 23.280 [5]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.2 MC system provides group configuration to the IWF | Figure 10.2.3.2-1 below illustrates the case where the MC system provides the group configuration to the IWF, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the IWF.
Pre-conditions:
1. The MC service group is defined in the MC system.
2. One or more LMR users are members of the group.
3. The MC system of the MC service group has been configured with addressing information for the group management function in the IWF.
4. The MC system of the MC service group is authorized to provide group configuration information to the IWF.
NOTE: The MC system of the MC service group could be configured with an address of the IWF which is a proxy address.
Figure 10.2.3.2-1: MC system provides group configuration to the IWF
1. The group management server in the MC system of the MC service group provides the configuration information related to the MC service group to the IWF.
2. The IWF responds to the group management server of the MC system of the MC service group that the configuration has been received and stored correctly. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.3 IWF requests group configuration from the MC system | Figure 10.2.3.3-1 below illustrates the case where the IWF requests the group configuration from the MC system, for example because a user on the IWF is a member of the group.
Pre-conditions:
1. The MC service group is defined in the MC system.
2. One or more LMR users are members of the group.
3. The IWF does not have the configuration for the MC service group stored.
Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system
1. The IWF requests the group configuration from the group management server in the primary MC system of the MC service group.
2. The group management server in the MC system of the MC service group provides the requested group configuration information. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.4 IWF provides group configuration to the MC system | Figure 10.2.3.4-1 below illustrates the case where the IWF provides the group configuration to the MC system, e.g. due to an action by an administrator or because some of the IWF's MC service group members are homed on the MC system.
Pre-conditions:
1. The group is defined in the IWF.
2. One or more MC service users are members of the group.
NOTE: The group management server within the MC system is responsible for providing group configuration information to group members for whom the MC system is their serving MC system.
Figure 10.2.3.4-1: MC system provides group configuration to the IWF
1. The IWF provides the configuration information related to the group to the group management server in the MC system.
2. The group management server in the MC system responds to the IWF that the configuration has been received and stored correctly. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.5 MC system requests group configuration from the IWF | Figure 10.2.3.5-1 below illustrates the case where the MC system requests the group configuration from the IWF, for example because an MC service user receiving service in the MC system has the group configured in the user profile.
Pre-conditions:
1. The MC service group is defined in the IWF.
2. One or more MC service users are members of the group.
3. The group management server in the MC system does not have the configuration for the MC service group stored.
4. The MC system has been configured with addressing information for the group management function in the IWF.
NOTE: The group management server within the MC system is responsible for providing group configuration information to MC service group members for whom the MC system is their serving MC system.
Figure 10.2.3.5-1: Partner MC system requests group configuration from primary MC system
1. The MC system requests the group configuration from the group management function in the IWF.
2. The IWF provides the requested group configuration information. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.6 IWF subscribes to group configuration | The procedure for subscription from IWF for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.3.6-1.
Pre-conditions:
1. The MC service group is defined in its MC system.
2. One or more group members are defined in the LMR system.
3. The IWF has received group information from the GMS in the primary MC system of the MC service group.
Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration
1. The IWF subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group.
2. The group management server in the primary MC system of the MC service group sends an IWF group information subscribe response to IWF indicating success or failure of the request. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.7 MC system notifies group configuration | The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the IWF is shown in figure 10.2.3.7-1.
Pre-conditions:
1. The IWF has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group.
2. The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group.
Figure 10.2.3.7-1: Notification of group configuration information to the IWF
1. The group management server in the primary MC system of the MC service group sends an IWF group information notify request to the IWF.
2. The IWF sends an IWF group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.8 MC system subscribes to group configuration | The procedure for subscription by the group management server in the MC system to the IWF for group configuration information is shown in figure 10.2.3.8-1.
Pre-conditions:
1. The group is defined in the LMR system.
2. One or more group members are defined in the MC system.
3. The group management server in the MC system has received group information from the IWF.
Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration
1. The group management server of the MC system subscribes to the group configuration information stored in the IWF.
2. The IWF provides an IWF group information subscribe response to group management server of the MC system indicating success or failure of the request. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.2.3.9 IWF notifies group configuration | The procedure for notification of group information from the IWF to the group management server in the MC system is shown in figure 10.2.3.9-1.
Pre-conditions:
1. The group management server of the MC system has subscribed to the group configuration information for the group in the IWF.
2. The IWF has new information for the group.
Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group
1. The IWF sends an IWF group information notify request to the group management server in the MC system.
2. The group management server in the MC system sends an IWF notify group information notify response to the IWF indicating the success or failure of the notification. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3 Group call | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.1 General | The following subclauses define information flows and signaling procedures for group calls and broadcast group calls.
Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF group call request / IWF group call release request message is sent to the IWF at the commencement / release of a group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document.
Where the group is defined in the LMR system, the IWF shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2 Information flows for group call over interworking group | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.1 General | The following subclauses define information flows for group calls on the IWF-1 interface. Group call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.2 IWF group call request | Table 10.3.2.2-1 describes the information flow IWF group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.2-1: IWF group call request information elements
Information Element
Status
Description
MCPTT ID
(see NOTE 1)
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the interworking group on which the call is initiated
SDP offer
M
Media parameters of MCPTT server
Implicit floor request
(see NOTE 2)
O
Indicates that the originator requests the floor.
Broadcast indicator
O
Indicates that the group call request is for a broadcast group call
Location
O
Location of the calling party
NOTE 1: If the LMR system does not provide the calling party identity when the group call is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for LMR user at the IWF.
NOTE 2: This element shall be included only when the originating client requests the floor. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.3 IWF group call response (IWF – MCPTT server) | Table 10.3.2.3-1 describes the information flow IWF group call response from the MCPTT server to the IWF and from the IWF to MCPTT server.
Table 10.3.2.3-1: IWF group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP answer
M
Media parameters selected |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.4 IWF Group-broadcast group call setup request | Table 10.3.2.4-1 describes the information flow IWF group-broadcast group call setup request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.4-1: IWF Group-broadcast group call setup request information elements
Information Element
Status
Description
MCPTT ID
(see NOTE 1)
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP offer
M
Media parameters of MCPTT clients
Implicit floor request
(see NOTE 2)
O
Indicates that the originating client requests the floor
Location
O
Location of the calling party
NOTE 1: If the LMR system does not provide the calling party identity when the group-broadcast group call setup request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF.
NOTE 2: This element shall be included only when the originating client requests the floor. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.5 IWF Group-broadcast group call setup response | Table 10.3.2.5-1 describes the information flow IWF group-broadcast group call setup response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.5-1: IWF Group-broadcast group call setup response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT group ID
M
The MCPTT group ID of the group on which the call is requested
SDP answer
M
Media parameters selected |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.6 IWF Group-broadcast group call release request | Table 10.3.2.6-1 describes the information flow IWF group-broadcast group call release request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.6-1: IWF Group-broadcast group call release request information elements
Information Element
Status
Description
MCPTT ID
M (see NOTE)
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released
NOTE: If the LMR system does not provide the calling party identity when the group-broadcast group call release request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.7 IWF group-broadcast group call release response | Table 10.3.2.7-1 describes the information flow IWF group-broadcast group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.7-1: IWF Group-broadcast group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.8 IWF group join request | Table 10.3.2.8-1 describes the information flow IWF group join request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.8-1: IWF group join request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the originator of the request.
(see NOTE 1)
Functional alias
O
The functional alias of the calling party
MCPTT group ID
M
The MCPTT group ID of the group to which the group communication is requested
SDP offer
M
Media parameters of originator
Implicit floor request
(see NOTE 2)
O
Indicates that the originating client requests the floor.
NOTE 1: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system.
NOTE 2: This element is included only when the originating client requests the floor. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.9 IWF group join response | Table 10.3.2.9-1 describes the information flow group join response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.9-1: IWF group join response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the originator of the request.
(see NOTE)
MCPTT group ID
M
The MCPTT group ID of the group to which the group communication is requested
SDP answer
M
Media parameters selected
NOTE: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.10 IWF group call leave request | Table 10.3.2.10-1 describes the information flow IWF group call leave request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.3.2.10-1: IWF group call leave request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group from which the user is leaving |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.11 IWF group call leave response | Table 10.3.2.11-1 describes the information flow IWF group call leave response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.11-1: IWF group call leave response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group from which the user is leaving |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.12 IWF group call release request | Table 10.3.2.12-1 describes the information flow IWF group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.12-1: IWF group call release request information elements
Information element
Status
Description
MCPTT ID
(see NOTE)
O
The MCPTT ID of the initiating MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released
Release reason
O
The reason why the call is released
NOTE: This IE is not included if the group call release is initiated by the server (e.g. due to timeout) |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.13 IWF group call release response | Table 10.3.2.13-1 describes the information flow IWF group call release response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.13-1: IWF group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the target MCPTT group member
MCPTT group ID
M
The MCPTT group ID of the group on which the call is released. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.14 IWF pre-configured regroup request | Table 10.3.2.14-1 describes the information flow IWF pre-configured regroup request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.14-1 IWF pre-configured regroup request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester
MCPTT group ID
M
MCPTT group ID of the regroup group
MCPTT group ID
M
MCPTT group ID of the MCPTT group from which configuration is to be taken
MCPTT group ID list
O
(see NOTE)
List of MCPTT groups to be regrouped into the pre-configured regroup group
MCPTT ID list
O
(see NOTE)
List of MCPTT IDs to be regrouped into the pre-configured user regroup group
NOTE: One and only one of these shall be present. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.15 IWF pre-configured regroup response | Table 10.3.2.15-1 describes the information flow IWF pre-configured regroup response from IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.15-1 IWF pre-configured regroup response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester of the regrouping operation
MCPTT group ID
M
MCPTT group ID of the regroup group
Result
M
Result of the regrouping operation |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.16 IWF pre-configured regroup cancel request | Table 10.3.2.16-1 describes the information flow pre-configured regroup cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.16-1 IWF pre-configured regroup cancel request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester
MCPTT group ID
M
MCPTT group ID of the regroup group |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.17 IWF pre-configured regroup cancel response | Table 10.3.2.17-1 describes the information flow IWF pre-configured regroup cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.17-1 IWF pre-configured regroup cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the requester of the regroup removal
MCPTT group ID
M
MCPTT group ID of the regroup group
Result
M
Result of the regroup removal operation |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.2.18 IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF) | Table 10.3.2.18-1 describes the information flow IWF pre-configured regroup reject from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.3.2.18-1 IWF pre-configured regroup reject information elements
Information Element
Status
Description
MCPTT group ID
M
MCPTT group ID of the regroup group
Reject reason
M
Reason for rejecting the regrouping operation |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3 Pre-arranged group call | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.1 General | The subclauses 10.3.3.2 and 10.3.3.3 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the MCPTT system. The subclauses 10.3.3.4 and 10.3.3.5 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the LMR system. The subclause 10.3.3.7 describes the late entry procedures and subclause 10.3.3.8 describes the group call release procedures. Group calls can use MC media encryption between the IWF and the MCPTT clients as described in 3GPP TS 33.180 [8]. A call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys.
The procedures in the present subclause are applicable to the following non-broadcast group call types: pre-configured group regroup calls, pre-configured user regroup calls and group regroup calls.
NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.2 Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system | In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.2-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.2-1: Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system
1. MCPTT user at MCPTT client 1 initiates a group call for the selected interworking group identified by MCPTT group ID.
2. MCPTT client 1 sends a group call request to the MCPTT server.
3. MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call on the selected interworking group.
4. MCPTT server proceeds group call setup procedures towards the affiliated MCPTT system users as described in 3GPP TS 23.379 [7].
5. MCPTT server sends IWF group call request(s) towards the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call request is sent (to the IWF) for each affiliated LMR user.
NOTE 2: How the LMR users are called is outside the scope of the present document.
NOTE 3: Steps 4 and 5 can occur in any order.
6. The IWF returns IWF group call response(s) to the MCPTT server. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
7. The MCPTT server sends group call response to the MCPTT client 1 about successful call establishment.
8. The group call on the interworking group has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.3 Group call setup initiated by LMR user on an interworking group defined in MCPTT system. | In this procedure, an LMR user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.3-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. LMR user initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system
1. The IWF sends an IWF group call request to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information.
2. MCPTT server calls the affiliated users from MCPTT system as described in 3GPP TS 23.379 [7]. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user.
NOTE 2: Steps 2 and 3 can occur in any order.
NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document.
4. The IWF returns IWF group call response(s) to the MCPTT server.
5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF.
NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document.
6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.4 Group call setup initiated by MCPTT user on an interworking group defined in the LMR system | In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.4-1.
This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.4-1: Group call initiated by MCPTT user on an interworking group defined in the LMR system
1. MCPTT user at MCPTT client 1 initiates a group call on the selected interworking group identified by MCPTT group ID.
2. MCPTT client 1 sends a group call request to the MCPTT server.
3. As the interworking group is defined in the LMR system the MCPTT server sends an IWF group call request to the IWF.
4. The IWF sends individual IWF group call request(s) to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the user in MCPTT client 2.
NOTE 2: How the LMR users are called is outside the scope of the present document.
5. The MCPTT server sends a group call request to the MCPTT client 2.
6. The MCPTT client 2 acknowledges towards the MCPTT server by sending a group call response.
7. The MCPTT server acknowledges towards the IWF by sending an IWF group call response.
8. The IWF sends an IWF group call response to the MCPTT server to acknowledge the IWF group call request received in step 3.
9. The MCPTT server sends a group call response to the initiating MCPTT user. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
10. The group call over the interworking group has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.5 Group call setup initiated by LMR user on an interworking group defined in the LMR system. | In this procedure, an LMR user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.5-1.
This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. LMR user initiates a group call.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.5-1: Group call initiated by LMR user on an interworking group defined in the LMR system
1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information.
2. MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7].
3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response.
4. The MCPTT server acknowledges the IWF group call request(s) by sending a IWF group call response(s) to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document.
5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.6 Encrypted group call with transcoding | Pre-conditions:
1. An MCPTT session is established between an MCPTT client, the interworked LMR system (represented by the IWF), and the MCPTT server.
2. There is an ongoing media transmission.
3. An SDP negotiation has occurred between the IWF and MCPTT Server to establish both the vocoder and the security parameters for the call.
4. The IWF is configured to perform transcoding of voice media and has obtained key material from the MCPTT system using the procedures in 3GPP TS 33.180 [8].
Figure 10.3.3.6-1: Encrypted group call with transcoding
1. The MCPTT client has been given the floor and is transmitting voice media.
2. The MCPTT client encodes audio using a codec defined for the MCPTT group, encrypts the encoded voice using procedures in 3GPP TS 33.180 [8], and forwards the encrypted voice media to the MCPTT server.
3. The MCPTT server forwards the encrypted voice media to other participants in the group call including the IWF.
4. The IWF decrypts the voice media from the MCPTT client using the procedures in 3GPP TS 33.180 [8]. The IWF transcodes the voice to a LMR codec. If needed, the IWF re-encrypts the transcoded voice media using LMR security procedures (these are out-of-scope of this specification), and forwards the voice media to the LMR system.
NOTE: Where transcoding occurs is outside the scope of this specification. In this procedure, it is assumed to take place internal to the IWF.
5. Sometime later the floor becomes idle.
6. The LMR system (represented by the IWF in figure 10.3.3.6‑1) requests and is granted the floor.
7. The IWF has been given the floor and is transmitting voice media.
8. The IWF receives voice media from the LMR system. If the voice media is encrypted, the IWF decrypts the voice media using LMR security procedures (these are out-of-scope of this specification). The IWF transcodes the voice to the group's MCPTT codec. The IWF re-encrypts the transcoded voice using the procedures in 3GPP TS 33.180 [8].
9. The IWF forwards the voice media to the MCPTT server.
10. The MCPTT server forwards the voice media to other participants in the group call. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.7 Late Entry | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.7.1 General | Late Entry for an ongoing interworking group call is triggered by a successful group affiliation procedure from the participating system.
NOTE: These procedures apply to all types of group calls, including, for example, emergency call, imminent peril call and broadcast call. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.7.2 Group call late entry on an interworking group defined in the MCPTT system | In this procedure, the group affiliation from IWF triggers a late entry procedure in the MCPTT system. The signalling procedure is described in figure 10.3.3.7.2-1.
For the first affiliating LMR user, this procedure is applicable for both IWF affiliation options (see subclauses 10.1.2.1 and 10.3.1). For the following LMR users affiliating to the same group, this procedure is triggered only if the IWF passes through individual affiliations for each group member.
This subclause is based upon subclauses in 3GPP TS 23.379 [7] for:
- Late entry for pre-arranged group call, subclause 10.6.2.3.1.1.4, and
- Group call for an MCPTT group defined in partner MCPTT system, subclause 10.6.2.4.3.1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call in the interworking group involving MCPTT clients 1 and 2.
4. First LMR user affiliates to the interworking group.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system
1. The IWF triggers a group affiliation towards the MCPTT server (see subclause 10.1.2.2).
2. The MCPTT server initiates a group call late entry for an interworking group.
3. The MCPTT server sends an IWF group call request to the IWF.
NOTE 2: How the IWF delivers the group call request to the LMR system is out of the scope of the present document.
4. The IWF confirms the group call request by sending IWF group call response to the MCPTT server.
5. The IWF (and the LMR user) is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the LMR user joining the group call.
6. If the floor has been granted to another user, the MCPTT server sends a IWF floor taken (6a) to the IWF. If the floor is not granted to any party, an IWF floor idle (6b) is sent to the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.7.3 Group call late entry on an interworking group defined in the LMR system | In this procedure, the group affiliation from MCPTT system triggers a late entry procedure in the LMR system. The signalling procedure is described in figure 10.3.3.7.3-1.
This procedure describes the affiliation and late entry of the first MCPTT user into the interworking group, but it is applicable also for all subsequent MCPTT users' affiliations to the same group.
This subclause is based upon subclauses in 3GPP TS 23.379 [7] for:
- Late entry pre-arranged group call, subclause 10.6.2.3.1.1.4, and
- Group call setup involving groups from multiple MCPTT systems, subclause 10.6.2.4.1.1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call in the interworking group, involving only LMR users.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.7.3-1: Group call late entry on an interworking group defined in the LMR system
1. MCPTT user (client 1) affiliates to the group (see subclause 10.1.2.4).
NOTE 2: How the IWF delivers the affiliation to LMR system and how the LMR system handles the late entry is out of scope of the present document.
2. The IWF sends an IWF group call request to the MCPTT server.
3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7].
4. The MCPTT server confirms the successful establishment of the group call by sending IWF group call response to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF.
5. MCPTT client 1 is successfully added to the ongoing group call.
6. If the floor has been granted to another user, the IWF sends an IWF floor taken (6a) to the MCPTT server. If the floor is not granted to any party, an IWF floor idle (6b) is sent.
7. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7]. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.8 Interworking group call release | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.8.1 General | The procedures in this subclause define the cases where the group host server releases an ongoing interworking group call for all the participants of that group.
If the group host server is an MCPTT server, the release conditions are described in 3GPP TS 23.379 [7], subclause 10.6.2.4.1.2.
If the group host server is an LMR system, represented by an IWF, the release conditions are outside the scope of the present document. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.8.2 Group call release on an interworking group defined in the MCPTT system | In this procedure, the MCPTT system is releasing a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.8.2-1.
This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7].
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.8.2-1: Group call release initiated by MCPTT system on an interworking group
1. The MCPTT server initiates a group call release on an interworking group.
NOTE 2: The MCPTT server may decide to release the group call for different reasons, see subclause 10.6.2.4.1.2 in 3GPP TS 23.379 [7].
2. The MCPTT server identifies the participants of the ongoing group call, at least one of them being an LMR user, represented by an IWF.
3. The MCPTT server sends IWF group call release request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call release request is sent (to the IWF) for each affiliated LMR user.
NOTE 3: How the group call release request(s) is(are) forwarded to the LMR system is out of scope of the present document.
4. The MCPTT server sends the (MCPTT) group call release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7].
NOTE 4: Steps 3 and 4 can occur in any order.
5. The IWF confirms the IWF group call release request(s) received in step 3 by IWF group call release response(s) to the MCPTT server.
6. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.3.8.3 Group call release on an interworking group defined in the LMR system | In this procedure, the LMR system is releasing a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.8.3-1.
This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7].
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2.
4. The LMR system initiates release of the group call.
NOTE 1: The reasons for the LMR system's decision to release the group call are out of scope of the present document.
NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.3.8.3-1: Group call release initiated by LMR system on an interworking group defined in the LMR system
1. The IWF sends IWF group call release requests to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call.
2. The MCPTT server forwards the release requests to the group's MCPTT users (in this example to users in MCPTT clients 1 and 2), as described in 3GPP TS 23.379 [7].
3. The MCPTT clients respond with group call release response(s).
4. The MCPTT server confirms the IWF group call release requests received in step 1 by IWF group call release responses to the IWF.
5. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4 Group broadcast | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.1 General | A broadcast group call is a special group call where the initiating user expects no response from the receiving users so that when the transmission is complete, so is the call. The initiating user can be an MCPTT user or can be an LMR user.
The group-broadcast group is defined as a set of groups, not a set of users. The user that originates the group-broadcast group call is the only one transmitting media during this call.
The group-broadcast group is defined with a hierarchy. For example, groups A and B may be subordinate to a group-broadcast group. All subordinate groups belonging to a group-broadcast group are defined either in the MCPTT system or the LMR system. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.2 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system | 3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF.
In this procedure, the MCPTT server is initiating the broadcast and is the owner of the group-broadcast group.
The procedure shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden.
Figure 10.3.4.2-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the MCPTT system).
Pre-conditions:
1. The group (e.g. A) to which MCPTT client 2 and the IWF are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group).
2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call.
3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group).
4. The group-broadcast group and its subordinate groups are defined in the same group management server and served by the same MCPTT server.
Figure 10.3.4.2-1: Group-broadcast group call involving IWF (group-broadcast group is defined in the MCPTT system)
1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure.
2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server.
3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups.
4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may affect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus, the MCPTT users involved in the group call on this subordinate group.
5. The MCPTT server performs group call release procedures of groups defined in the MCPTT system as described in subclause 10.3.3.8.2.
6. A group-broadcast group call request is sent to MCPTT client 2 and an IWF group-broadcast group call request to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user.
NOTE 1: How the group-broadcast group call request(s) is(are) forwarded to the LMR system is out of scope of the present document.
7. MCPTT client 2 is notified of the incoming group-broadcast group call.
NOTE 2: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document.
8. MCPTT client 2 and the IWF respond to the IWF group-broadcast group call request by sending an IWF group-broadcast group call response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user.
9. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response.
10. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources.
Once the user of MCPTT cleint 1 completes transmitting, the group-broadcast group call is released. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.3 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system | 3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF.
In this procedure, the IWF is the owner of the group-broadcast group and is initiating the group-broadcast group call.
The procedure only shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden.
Figure 10.3.4.3-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the LMR system).
Pre-conditions:
1. The group (e.g. A) to which MCPTT client 2 is a member is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group).
2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call.
3. The call initiator, MCPTT client 1, of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group).
4. The group-broadcast group and its subordinate groups are defined in the IWF.
Figure 10.3.4.3-1: Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system)
1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure.
2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server.
3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call setup request to the IWF.
4. The IWF performs group call release procedures of groups defined in the LMR system as described in subclause 10.3.3.8.3.
5. The IWF issues a group-broadcast group call setup request to establish the group-broadcast call.
6. The MCPTT user of MCPTT client 2 is notified.
NOTE: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document.
7. Optionally, MCPTT client 2 respond with a group-broadcast group call response to the MCPTT server and then to the IWF.
8. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response.
9. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources.
Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.4 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system | When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released.
Figure 10.3.4.4-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group is defined in the MCPTT system).
Pre-conditions:
1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists.
Figure 10.3.4.4-1: Group-broadcast group call transmission ended (group-broadcast group is defined in the MCPTT system)
1. MCPTT user on MCPTT client 1 finished transmitting.
2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group.
3. The MCPTT users of MCPTT client 2 and the IWF of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user.
4. MCPTT client 2 and the IWF notify their users that the group-broadcast group call has ended.
NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document.
5. MCPTT client 2 and the IWF respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user.
6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now ended. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.5 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system | When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released.
Figure 10.3.4.5-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group defined in the LMR system).
Pre-conditions:
1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists.
Figure 10.3.4.5-1: Group-broadcast group call transmission ended (group-broadcast group defined in the LMR system)
1. The MCPTT user on MCPTT client 1 finished transmitting.
2. A group-broadcast group call release request is sent to the MCPTT server.
3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call release request to the IWF.
4. The IWF sends an IWF group-broadcast group call release request to the MCPTT server hosting client 2. The MCPTT server sends the group-broadcast group call release request to MCPTT client 2.
5. MCPTT client 2 is notified that the group-broadcast group call has ended.
NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document.
6. MCPTT client 2 responds to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response.
7. The MCPTT server sends an IWF group-broadcast group call release response to the IWF. The IWF becomes aware that MCPTT client 2 has confirmed the group-broadcast group call release and replies with another IWF group-broadcast group call release response back to the MCPTT server to trigger step 8.
8. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the group-broadcast group call is now ended. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.6 Broadcast group regroup call using pre-configured group | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.6.1 General | The temporary group created using a pre-configured group can be a broadcast group or a non-broadcast group.
A broadcast group regroup call using pre-configured groups can be achieved by first regrouping users into a pre-configured group regroup, making the broadcast group call on the pre-configured group, and then cancelling the pre-configured group regroup. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.6.2 Broadcast group regroup call using pre-configured group the MCPTT system | The broadcast group regroup call procedure using pre-configured group allows an authorized MCPTT user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. The regroup is cancelled at the end of the broadcast call to prevent users from talking back on the pre-configured group regroup. This procedure requires that the authorized MCPTT user is a group member of at least one of the MCPTT groups included in the regroup operation.
Figure 10.3.4.6.2‑1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured MCPTT regroup group owned by the MCPTT system. For simplicity, no receiving clients are shown.
Pre-conditions:
- The MCPTT client is registered with the MCPTT service.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client and the IWF. The MCPTT client and the IWF have received the relevant security related information to allow them to communicate in the pre-configured group regroup.
- The MCPTT client is authorized to initiate a pre-configured group regroup using the pre-configured group regroup procedure.
- The MCPTT client is aware of a suitable pre-configured group whose configuration has been pre-configured in the IWF and the MC service UEs of the MCPTT users who will be regrouped.
- The MCPTT client is affiliated to group 1.
- The IWF is affiliated to one or more of MCPTT group 1, 2 or 3.
- The pre-configured group regroup is homed in the MCPTT server.
- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup.
Figure 10.3.4.6.2-1: Broadcast group regroup call using pre-configured group in the MCPTT system
1. The authorized user of the MCPTT client initiates the pre-configured group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1, 2, and 3 are regrouped into group 4.
2. The MCPTT user at the MCPTT client performs the broadcast group call procedure as specified in subclause 10.3.4.
3. The MCPTT client initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.4.6.3 Broadcast group regroup call using pre-configured group in the IWF | The broadcast group regroup call procedure using a pre-configured group allows an IWF user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call.
Figure 10.3.4.6.3-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured group owned by the IWF.
Pre-conditions:
- MCPTT clients 1 and 2 are registered with the MCPTT service.
- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in MCPTT clients 1 and 2, and MCPTT clients 1 and 2 have received the relevant security related information to allow them to communicate in the pre-configured group regroup.
- MCPTT client 1 is affiliated to group 1, MCPTT client 2 is affiliated to group 2. Group 3 is used as the pre-configured group regroup.
- The pre-configured group regroup is homed in the IWF.
- The MCPTT server is home to at least one group that's a constituent group of the pre-configured group regroup.
Figure 10.3.4.6.3-1: Broadcast group regroup call using pre-configured group in the IWF
1. The IWF initiates the group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1 and 2 are regrouped into group 3.
2. The IWF performs the broadcast group call procedure as specified in subclause 10.3.4.
3. The IWF initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5 Chat group call | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.1 General | This subclause is based upon subclause for chat group call in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.2. For LMR systems that do not support the concept of chat groups, the IWF might still adapt its calls to the MCPTT chat model. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.2 MCPTT user initiated chat group call in an interworking group defined in LMR system | In this procedure, an MCPTT user initiates a chat group call in an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.5.2-1.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.5.2-1: MCPTT user initiated chat group call in an interworking group defined in the LMR system
1. MCPTT user of the MCPTT client indicates to join the group communication for the group. The MCPTT client joins the group by sending a group join request to the MCPTT server. If there is a request to transmit, then the group join request contains an indication of an implicit floor request and the location of the joining party if required.
2. The MCPTT server inspects the Group join request for presence of location information of the calling party. If location information is included in the join request, the MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF.
3. The MCPTT server notices that the interworking group is defined in the LMR system and forwards the group join request with or without location depending on the outcome of the privacy check as an IWF group join request to the IWF.
4. The IWF replies with an IWF group join response indicating the acceptance of the group join request and also returns the IWF selected media parameters for the chat group call in the IWF group join response.
5. The MCPTT server forwards the IWF group join response to the MCPTT client as a group join response.
6. If the MCPTT client requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call.
7. Floor control will continue to be used by the floor participants associated with the MCPTT client and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.3 LMR user initiated chat group call in an interworking group defined in MCPTT system | In this procedure, an LMR user initiates a chat group call in an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.5.3-1.
Pre-conditions:
1. The interworking group information is known at the IWF by configuration. The interworking group has been defined in the MCPTT system.
2. MCPTT user 1 and MCPTT user 2 have previously joined (affiliated) to the group.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
4. LMR user initiates a join to the group.
NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.3.5.3-1: LMR user initiated chat group call in an interworking group defined in the MCPTT system
1. The IWF sends an IWF group join request to the MCPTT server. The request to join may contain location information of the transmitting party. If there is a request to transmit, then the IWF group join request contains an indication of an implicit floor request and the location of the joining party if required.
2. The MCPTT server checks whether the MCPTT ID is authorized to affiliate to the group. MCPTT server generates an implicit affiliation if the MCPTT ID is not already affiliated to the group.
3. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the chat group call in the IWF group join response.
4. If the IWF requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call.
5. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.4 Release chat group call on an interworking group defined in the LMR system | This procedure describes the case where the LMR system releases an ongoing MCPTT chat group call on an interworking group defined in the LMR system, for all the participants of that group call. The signalling procedure is described in figure 10.3.5.4-1.
Pre-conditions:
1. A chat group call is ongoing involving an MCPTT client and the IWF.
2. The LMR system initiates release of the chat group call.
Figure 10.3.5.4-1: Release chat group call on an interworking group defined in the LMR system
1. The IWF sends an IWF group call release request to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call.
2. MCPTT server forwards the release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7].
3. MCPTT users are notified about the release of the group call.
4. Optionally, the MCPTT client confirms the group call release request received in step 2 with a group call release response to the MCPTT server.
5. The MCPTT server forwards the group call release response to the IWF as an IWF group call release response.
6. The MCPTT client and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.5 Release chat group call on an interworking group defined in the MCPTT system | This procedure describes the case where the MCPTT server releases an ongoing MCPTT chat group call, on an interworking group defined in the MCPTT system, for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted.
The signalling procedure is described in figure 10.3.5.5-1.
Pre-conditions:
1. A chat group call is ongoing involving MCPTT clients 1, 2 and the IWF.
Figure 10.3.5.5-1: Release chat group call on an interworking group defined in the MCPTT system
1. The MCPTT server decides to release the MCPTT chat 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.
2. The MCPTT server sends an IWF group call release request to the IWF to release the ongoing session. If the IWF has joined itself to this group on behalf of all the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual joins from the group's LMR users, an individual IWF group call release request is sent to the IWF for each joined LMR user.
3. The MCPTT server sends a group call release request towards each MCPTT participant of the ongoing group call.
4. The MCPTT users are notified about the release of the group call.
5. The IWF confirms the IWF group call release request(s) received in step 2 by IWF group call release response(s) to the MCPTT server.
6. Optionally, the MCPTT client(s) receiving a group call release request may send a group call release response to the MCPTT server.
7. MCPTT client 1, client 2 and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.6 Void | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.7 Void | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.8 Newly joined MCPTT group member of a group defined in the LMR system | Procedures in figure 10.3.5.8-1 are those for a group member entering an ongoing MCPTT group call, i.e. performing a late entry.
Pre-conditions:
1. The MCPTT client is registered and the MCPTT user has been authenticated and authorized to use the MCPTT service.
2. There is an ongoing group call on the group homed on the LMR system.
3. The MCPTT client has not yet joined the group call.
4. The MCPTT user indicates to join the group call.
Figure 10.3.5.8-1: Late entry of a newly joined MCPTT group member
1. The MCPTT client sends a group join request with the MCPTT group ID of the desired group to the MCPTT server. If there is a request to transmit, then the group joint request contains an indication of an implicit floor request.
2. The MCPTT server forwards the request to the IWF.
3. The IWF replies with a group join response indicating the acceptance of the group join request.
4. The MCPTT server forwards the response to the MCPTT client.
5. The IWF establishes the media plane with the MCPTT client.
6. The IWF may notify its users that an MCPTT user has joined the group.
7 a. The IWF sends an IWF floor taken (for the current talker) to the MCPTT server if the floor has been taken.
7b. The MCPTT responds to any incoming IWF floor taken message by forwarding a floor taken message to the MCPTT client.
8. Floor control will continue to be used by the floor participants. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.9 Newly joined LMR group member of a group defined in the MCPTT system | Procedures in figure 10.3.5.9-1 are those for the IWF entering an ongoing MCPTT group call, i.e. performing a late entry.
Pre-conditions:
1. MCPTT user 1 and MCPTT user 2 have previously joined to the group.
2. MCPTT users using MCPTT client 1 and MCPTT client 2 are in an ongoing group call.
3. The IWF has not yet joined the group call.
Figure 10.3.5.9-1: Late entry of a newly joined LMR group member
1. The IWF sends a group join request with the MCPTT group ID of the desired group and either using the MCPTT ID corresponding to the LMR group member or using the pre-configured MCPTT ID for use when the IWF is affiliating itself on behalf of the group's LMR users. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. If the group join request includes an implicit floor request it may also include location information.
2. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation using the MCPTT ID used by the IWF (if the IWF or the LMR user is not already affiliated to the group) and verifies that IWF is authorized to affiliate to the group.
3. The MCPTT server replies with a group join response indicating the acceptance of the group join request.
4. The MCPTT server establishes the media plane between the IWF and the MCPTT server.
5. MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the IWF joining the group call.
6. The MCPTT server sends a floor taken (for the current talker) to the IWF.
7. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.5.10 MCPTT client returning to coverage on a group homed in the LMR system | Procedures in figure 10.3.5.10-1 are those for an MCPTT client returning to coverage during an ongoing MCPTT chat group call.
Pre-conditions:
1. The MCPTT user using an MCPTT client is in an ongoing chat group call when the MCPTT client goes out of radio coverage.
Figure 10.3.5.10-1: Late entry of a MCPTT client returning from out of coverage
1. The MCPTT client or MCPTT server detects that MCPTT client has returned to coverage.
NOTE: How the MCPTT client or MCPTT server detects that the client has returned to coverage is out of scope of the present document.
2. The media plane between the MCPTT client and the IWF are re-established using media plane control signalling
3a. The IWF sends an IWF floor taken to the MCPTT server if anyone currently has the floor.
3b. The MCPTT server forwards a floor taken message to the MC Client if anyone currently has the floor.
4. Floor control will continue to be used by the floor participants. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.6 Exiting group call due to de-affiliation | |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.6.1 General | The following procedures are applicable both for the pre-arranged and chat group calls. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.6.2 Exiting group call defined in the LMR system due to de-affiliation | Procedures in figure 10.3.6.2-1 are the signalling control plane procedures for the IWF requesting a newly de-affiliated MCPTT user to leave an ongoing MCPTT group call.
Pre-conditions:
1. The MCPTT group is previously defined on the IWF with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID.
2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call.
Figure 10.3.6.2-1: Exiting MCPTT group call due to de-affiliation
1. The MCPTT client is de-affiliated.
2. The IWF sends an IWF group call leave request to the MCPTT client via the MCPTT server.
3. The MCPTT server forwards the IWF group call leave request as a group call leave request to the MCPTT client.
4. The MCPTT user at the MCPTT client is notified about leaving the group call.
5. The MCPTT client sends the group call leave response to the MCPTT server and leaves the group call.
6. The MCPTT server forwards the group call leave response to the IWF as an IWF group call leave response.
7. The MCPTT client is now removed from the ongoing group call. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.6.3 Exiting group call defined in the MCPTT system due to de-affiliation | Procedures in figure 10.3.6.3-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated LMR user to leave an ongoing MCPTT group call.
Pre-conditions:
1. The MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID.
2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call.
Figure 10.3.6.3-1: Exiting MCPTT group call due to de-affiliation
1. The LMR user represented by the IWF has been de-affiliated.
2. The MCPTT server sends an IWF group call leave request to the LMR user via the IWF.
3. The IWF sends an IWF group call leave response to the MCPTT server and leaves the group call.
4. The LMR user represented by the IWF is now removed from the ongoing group call. |
206be7a57129464f73be1aa9d853095b | 23.283 | 10.3.7 Group regroup with pre-configured group |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.