Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  17.8.0

Top   Top   Up   Prev   Next
1…   4…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.18…   10.6.2.2.34…   10.6.2.3…   10.6.2.3.2…   10.6.2.4…   10.6.2.5…   10.6.2.6…   10.6.2.7…   10.6.2.9…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.6…   10.9…   10.9.1.3…   10.9.2…   10.10…   10.14…   A…   A.4…   B…

 

10.6.2.9  Group regroup with preconfigured group |R16|Word‑p. 95

10.6.2.9.1  GeneralWord‑p. 95
A group regroup may be achieved by regrouping MCPTT groups into a new MCPTT regroup group which uses the configuration of a separate preconfigured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT group members of the MCPTT groups that will be regrouped in advance of the regrouping operation.
The preconfigured MCPTT group that provides the configuration is not used as the MCPTT regroup group itself, it only provides configuration for one or more MCPTT regroup groups. The MCPTT group ID of the regroup group is provided by the authorized user when the preconfigured regrouping is carried out.
The MCPTT regroup group can be specified to be a broadcast or non-broadcast type according to the configuration of the MCPTT group whose configuration is specified by the regroup request. The broadcast type of regroup is used for one-way communication where only an authorized MCX user is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e, the regroup group call behaves like a normal non-broadcast group call).
These procedures provide a regrouping service for MCPTT only and are independent of group regrouping procedures specified in TS 23.280. If the MCPTT server has been notified by the group management server that one of the MCPTT groups that has been requested for regrouping by means of this procedure has already been regrouped by the group regrouping procedure specified in TS 23.280, the MCPTT server shall reject the request for regrouping described in the following procedure.
Up
10.6.2.9.2  Regroup procedures in single MCPTT systemWord‑p. 96
10.6.2.9.2.1  Regroup formation using preconfigured group in single MCPTT systemWord‑p. 96
Figure 10.6.2.9.2.1-1 illustrates the procedure to initiate a group regroup procedure using a preconfigured MCPTT group. The procedure takes place prior to the establishment of a group call to the regroup group.
Pre-conditions:
  • MCPTT client 2 is an affiliated member of MCPTT group 1 and MCPTT client 3 is an affiliated member of MCPTT group 2.
  • The MCPTT group identity and group configuration for the regroup MCPTT group have been preconfigured in MCPTT clients 2 and 3, and MCPTT clients 2 and 3 have received the relevant security related information to allow them to communicate in the regroup MCPTT group.
  • MCPTT client 1 is authorized to initiated a preconfigured regroup procedure.
  • MCPTT client 1 is aware of a suitable preconfigured regroup group whose configuration has been preconfigured in the MCPTT UEs of the group members who will be regrouped.
  • In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS.
  • The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 in TS 23.280 from the MCPTT server using the procedures defined in subclause 10.1.5.6 in TS 23.280.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.2.1-1: Regroup procedure using preconfigured group in single MCPTT system
Up
Step 1.
The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped (MCPTT groups 1 and 2), the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken.
Step 2.
MCPTT client 1 sends the preconfigured regroup request to the MCPTT server.
Step 3.
The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to MCPTT groups 1 and 2. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. The MCPTT server also checks that none of the MCPTT groups that are requested for regrouping are already regrouped by any mechanism.
Step 4.
If the MCPTT server determines that any of the groups requested for regrouping, including the regroup group, have been regrouped by other group regrouping procedures, the MCPTT server then sends a preconfigured regroup reject back to MCPTT client 1 with a reject reason indicating that one of the groups has already been regrouped, and this procedure terminates.
Step 5.
If the preconfigured regroup request is not rejected, the MCPTT server sends the preconfigured regroup requests to MCPTT clients 2 and 3 in steps 5a and 5b respectively.
Step 6.
MCPTT clients 2 and 3 notify their users of the regrouping in steps 6a and 6b respectively.
Step 7.
MCPTT clients 2 and 3 may send the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request.
Step 8.
The MCPTT server affiliates the regrouped MCPTT clients to the regroup group.
Step 9.
The MCPTT server sends a preconfigured regroup response to MCPTT client 1.
After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in clause 10.6.2.9.2.2.
MCPTT client participation in the ongoing regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure).
MCPTT client affiliation to the regroup group may cease when the UE's MCPTT service ceases, e.g. when the UE is powered down, or by performing a log-off operation.
Up
10.6.2.9.2.2  Regroup cancellation in single MCPTT systemWord‑p. 98
Figure 10.6.2.9.2.2-1 illustrates the procedure to cancel a regrouping that uses a preconfigured MCPTT group.
Pre-conditions:
  • MCPTT clients 2 and 3 have been regrouped into an MCPTT regroup group.
  • MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured MCPTT group.
  • The GMS has subscribed to group dynamic data as specified in subclause 10.1.5.5.1 in TS 23.280 from the MCPTT server using the procedures defined in subclause 10.1.5.6 in TS 23.280.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.2.2-1: Cancel preconfigured regroup procedure in single MCPTT system
Up
Step 1.
The authorized user of MCPTT client 1 initiates the cancellation of the regrouping that uses a preconfigured MCPTT group.
Step 2.
MCPTT client 1 sends the preconfigured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group.
Step 3.
The MCPTT server checks that MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured group regroup procedure.
Step 4.
The MCPTT server sends the preconfigured regroup cancel requests to MCPTT clients 2 and 3 (steps 4a and 4b respectively).
Step 5.
MCPTT clients 2 and 3 notify their users of the cancellation of the group regrouping in steps 5a and 5b respectively.
Step 6.
MCPTT clients 2 and 3 may send the preconfigured regroup cancel response to the MCPTT server to acknowledge the cancellation of the regrouping function. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup cancel request.
Step 7.
The MCPTT server de-affiliates MCPTT clients 2 and 3 from the MCPTT regroup group.
Step 8.
The MCPTT server sends a preconfigured regroup cancel response to MCPTT client 1.
Up
10.6.2.9.3  Regroup procedures in multiple MCPTT systemsWord‑p. 99
10.6.2.9.3.1  Regroup formation using preconfigured group in multiple MCPTT systemsWord‑p. 99
Figure 10.6.2.9.3.1-1 illustrates the procedure to initiate a regroup procedure using a preconfigured MCPTT group, where at least one of the groups to be regrouped is configured in a partner MCPTT system. The primary MCPTT system where the preconfigured group regrouping is initiated does not need to be aware of the list of group members belonging to groups whose group home system is the partner MCPTT system. If the group management server in the primary MCPTT of the regroup group shares the necessary security related parameters together with the group configuration of the MCPTT regroup group with the group management server in the partner MCPTT system and the group management server in the partner MCPTT system distributes this configuration including those security parameters to its served MCPTT users according to the procedures in TS 23.280, subclause 10.2.7, the primary MCPTT system does not need to be aware of the list of group members of the preconfigured regroup group that are receiving service in the partner MCPTT system.
The procedure takes place prior to the establishment of a group call to the regroup group.
In this procedure, any gateway MC servers in the primary or partner MCPTT systems are not shown.
Pre-conditions:
  • MCPTT client 1 is authorized to initiated a preconfigured regroup procedure, and is receiving MCPTT service in the primary MCPTT system of MCPTT client 1.
  • MCPTT client 2 is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the partner MCPTT system and MCPTT client 2 is receiving service in the partner MCPTT system of MCPTT client 1.
  • The MCPTT group identity and group configuration for the regroup MCPTT group have been preconfigured in MCPTT client 2, and MCPTT client 2 has received the relevant security related information to allow communication in the regroup MCPTT group.
  • In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS.
  • The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 in TS 23.280 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in TS 23.280.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.3.1-1: Regroup procedure using preconfigured group in multiple MCPTT systems
Up
Step 1.
The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken.
Step 2.
MCPTT client 1 sends the preconfigured regroup request to the MCPTT server.
Step 3.
The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the primary MCPTT system. The MCPTT server identifies any partner systems which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server.
Step 4.
The MCPTT server sends the preconfigured regroup requests to the MCPTT server in the partner MCPTT system.
Step 5.
The partner MCPTT server checks the status of any MCPTT groups hosted by that partner MCPTT server, and identifies affiliated group members of any of the identified MCPTT groups (both MCPTT groups that are hosted in the primary MCPTT system and MCPTT groups that are hosted in the partner MCPTT system) that are receiving MCPTT service in the partner MCPTT system, which include MCPTT client 2.
Step 6.
The partner MCPTT server sends the preconfigured regroup request to MCPTT client 2.
Step 7.
MCPTT client 2 notifies the user of the regrouping.
Step 8.
MCPTT client 2 may send the preconfigured regroup response to the partner MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup request.
Step 9.
The partner MCPTT server affiliates the regrouped MCPTT client 2 to the regroup group.
Step 10.
The MCPTT server sends a preconfigured regroup response to the primary MCPTT server.
Step 11.
The primary MCPTT server sends the preconfigured regroup response to MCPTT client 1.
After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.6.2.9.3.2.
MCPTT client participation in the ongoing regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure).
MCPTT client affiliation to the regroup group may cease when the UE's MCPTT service ceases, e.g. when the UE is powered down, or by performing a log-off operation.
Up
10.6.2.9.3.2  Regroup cancellation using preconfigured group in multiple MCPTT systemsWord‑p. 101
Figure 10.6.2.9.3.2-1 illustrates the procedure to cancel a regrouping that uses a preconfigured MCPTT group where multiple MCPTT systems were involved in the regrouping.
Pre-conditions:
  • MCPTT client 2 has been regrouped into an MCPTT regroup group, and is receiving MCPTT service in the partner MCPTT system of the regroup group.
  • MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured MCPTT group, and is receiving MCPTT service in the primary MCPTT system of the regroup group.
  • The GMS has subscribed to group dynamic data as specified in subclause 10.1.5.5.1 in TS 23.280 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in TS 23.280.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.3.2-1: Cancel preconfigured regroup procedure using preconfigured group in multiple MCPTT systems
Up
Step 1.
The authorized user of MCPTT client 1 initiates the cancellation of the regrouping that uses a preconfigured MCPTT group.
Step 2.
MCPTT client 1 sends the preconfigured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group.
Step 3.
The MCPTT server checks that MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured group regroup procedure.
Step 4.
The primary MCPTT server sends the regroup cancel request to the partner MCPTT server.
Step 5.
The partner MCPTT server sends the preconfigured regroup cancel requests to MCPTT client 2.
Step 6.
MCPTT client 2 notifies the user of the cancellation of the group regrouping.
Step 7.
MCPTT client 2 may send the preconfigured regroup remove response to the partner MCPTT server to acknowledge the cancellation of the regrouping function. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup cancel request.
Step 8.
The partner MCPTT server de-affiliates MCPTT client 2 from the MCPTT regroup group.
Step 9.
The partner MCPTT server sends the preconfigured regroup cancel response to the primary MCPTT server.
Step 10.
The primary MCPTT server sends a preconfigured regroup cancel response to MCPTT client 1.
Up
10.6.2.9.3.3  Regroup rejection using preconfigured group in multiple MCPTT systemsWord‑p. 103
Figure 10.6.2.9.3.3-1 illustrates the case where the procedure to initiate a regroup procedure with multiple MCPTT systems using a preconfigured MCPTT group described in subclause 10.6.2.9.3.1 commences, but where the request for the regroup is rejected by the partner MCPTT server, for example because one of the groups hosted by the partner MCPTT server is already regrouped by other group regrouping procedures.
In this procedure, any gateway MC servers in the primary or partner MCPTT systems are not shown.
Pre-conditions:
  • MCPTT client 1 is authorized to initiated a preconfigured regroup procedure, and is receiving MCPTT service in the primary MCPTT system of MCPTT client 1.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.3.3-1: Regroup rejection using preconfigured group in multiple MCPTT systems
Up
Step 1.
The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken.
Step 2.
MCPTT client 1 sends the preconfigured regroup request to the MCPTT server.
Step 3.
The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the primary MCPTT system. The MCPTT server identifies any partner systems which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server.
Step 4.
The MCPTT server sends the preconfigured regroup requests to the MCPTT server in the partner MCPTT system.
Step 5.
The partner MCPTT server checks the status of any MCPTT groups hosted by that partner MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure.
Step 6.
The partner MCPTT server sends a preconfigured regroup reject to the primary MCPTT server, indicating the reason for rejection.
Step 7.
The primary MCPTT server sends a preconfigured regroup reject to MCPTT client 1, indicating the reason for rejection.
Up
10.6.2.9.4  Adding newly affiliated user to preconfigured group regroupWord‑p. 104
Figure 10.6.2.9.4-1 illustrates the procedure to add a newly affiliated user to an in-progress preconfigured MCPTT group regroup operation.
Pre-conditions:
  • The MCPTT client is a member of a MCPTT group that is part of an in-progress preconfigured group regroup operation.
  • The MCPTT group identity and group configuration for the regroup MCPTT group has been preconfigured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow it to communicate in the regroup MCPTT group.
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.4-1: Procedure to add a newly affiliated user to a preconfigured regroup
Up
Step 1.
The MCPTT client affiliates to an MCPTT group that is currently part of an in-progress preconfigured group regroup. The affiliation follows the procedure in clause 10.8.3.1 of TS 23.280.
Step 2.
The MCPTT server retrieves the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken.
Step 3.
The MCPTT server sends the preconfigured regroup request to the MCPTT client.
Step 4.
The MCPTT client notifies the user of the regrouping.
Step 5.
The MCPTT client may send the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request.
Step 6.
The MCPTT server affiliates the regrouped MCPTT client to the regroup group.
Up
10.6.2.9.5  Preconfigured regroup update proceduresWord‑p. 105
10.6.2.9.5.1  MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroupWord‑p. 105
Figure 10.6.2.9.5.1-1 illustrates the procedure when a user attempts to setup an MCPTT group call on a group involved in an in-progress preconfigured MCPTT group regroup.
Pre-conditions:
  • The MCPTT client is an affiliated member of MCPTT group A that is part of an in-progress preconfigured group regroup with MCPTT groups B and C.
  • MCPTT group D is being used as the preconfigured regroup group.
  • The MCPTT client has missed the preconfigured regroup request message (e.g. poor signalling conditions, race condition).
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.5.1-1: Procedure for MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroup
Up
Step 1.
The MCPTT client attempts to start a call on MCPTT group A. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group A as the target group.
Step 2.
The MCPTT server checks to see whether MCPTT group A is currently part of a preconfigured group regroup. In this case the group is part of an active preconfigured group regroup.
Step 3.
The MCPTT server sends a group call response to the MCPTT client indicating that the call setup is denied because the group is part of an in-progress group regroup.
Step 4.
The MCPTT server sends the preconfigured regroup request to the MCPTT client containing MCPTT group D, the group ID of the preconfigured group.
Step 5.
The MCPTT client notifies the user of the group call setup failure and of the regrouping procedure.
Step 6.
The MCPTT client sends the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action.
Step 7.
The MCPTT server affiliates the regrouped MCPTT client to the regroup group.
Up
10.6.2.9.5.2  MCPTT client PTTs on preconfigured regroup group after group regroup has been cancelledWord‑p. 106
Figure 10.6.2.9.5.2-1 illustrates the procedure when a user attempts to setup a MCPTT group call on a preconfigured regroup group after the preconfigured MCPTT group regroup has been cancelled.
Pre-conditions:
  • The MCPTT client is a member of MCPTT group A that was part of an in-progress preconfigured group regroup with MCPTT groups B and C that has been cancelled. MCPTT group D was used as the MCPTT regroup group.
  • The MCPTT client has missed the preconfigured regroup cancel request message (e.g. poor signalling conditions, race condition).
Copy of original 3GPP image for 3GPP TS 23.379, Figure 10.6.2.9.5.2-1: Procedure for MCPTT client PTTs on regroup group after the group regroup is cancelled
Up
Step 1.
The MCPTT client attempts to start a call on MCPTT group D, the MCPTT regroup group. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group D as the target group.
Step 2.
The MCPTT server checks to see whether MCPTT group D is currently being used as part of a preconfigured group regroup. In this case the preconfigured group regroup is no longer active.
Step 3.
The MCPTT server sends a group call response to the MCPTT client indicating that the call setup is denied because the group regroup is no longer active.
Step 4.
The MCPTT server sends the preconfigured regroup cancel request to the MCPTT client.
Step 5.
The MCPTT client notifies the user of the group call setup failure and of the regrouping cancellation.
Step 6.
The MCPTT client sends the preconfigured regroup cancel response to the MCPTT server to acknowledge the regrouping cancellation.
Up

Up   Top   ToC