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.3 Regroup procedures in multiple MCPTT systems  10.6.2.9.3.1 Regroup formation using preconfigured group in multiple MCPTT systems  10.6.2.9.3.2 Regroup cancellation using preconfigured group in multiple MCPTT systems  10.6.2.9.3.3 Regroup rejection using preconfigured group in multiple MCPTT systems 
...

 

10.6.2.9.3  Regroup procedures in multiple MCPTT systems  p. 100
10.6.2.9.3.1  Regroup formation using preconfigured group in multiple MCPTT systems  p. 100
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.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.9.3.1-1: Regroup procedure using preconfigured group in multiple MCPTT systems
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 clause 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 systems  p. 102
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.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.9.3.2-1: Cancel preconfigured regroup procedure using preconfigured group in multiple MCPTT systems
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 systems  p. 104
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.
Reproduction of 3GPP TS 23.379, Fig. 10.6.2.9.3.3-1: Regroup rejection using preconfigured group in multiple MCPTT systems
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

Up   Top   ToC