Tech-invite  3GPPspace  IETF RFCs  SIP
index  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.379  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   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.1.2…   10.6.2.3.2…   10.6.2.4…   10.6.2.4.3…   10.6.2.5…   10.6.2.5.2.3…   10.6.2.6…   10.6.2.6.2…   10.6.2.7…   10.6.2.9…   10.6.2.9.3…   10.6.2.9.4…   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.5.2.3a…   10.7.6…   10.7.6.2.3…   10.9…   10.9.1.3…   10.9.1.3.2…   10.9.1.3.3…   10.9.1.4   10.9.1.5…   10.9.2…   10.9.2.6…   10.10…   10.12…   10.14…   10.15…   10.19…   10.19.3…   A…   A.4…   B… 
10.6.2.9 Group regroup with preconfigured group  10.6.2.9.1 General  10.6.2.9.2 Regroup procedures in single MCPTT system  10.6.2.9.2.1 Regroup formation using preconfigured group in single MCPTT system  10.6.2.9.2.2 Regroup cancellation in single MCPTT system 
...

 

10.6.2.9  Group regroup with preconfigured group |R16|  p. 96

10.6.2.9.1  General  p. 96
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 system  p. 97
10.6.2.9.2.1  Regroup formation using preconfigured group in single MCPTT system  p. 97
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.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.9.2.1-1: Regroup procedure using preconfigured group in single MCPTT system
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 system  p. 99
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.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.9.2.2-1: Cancel preconfigured regroup procedure in single MCPTT system
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

Up   Top   ToC