Content for  TS 23.280  Word version:  19.4.0

Table 10.2.2.1-1 describes the information flow group creation request from the group management client to the group management server.

Table 10.2.2.2-1 describes the information flow group creation response from the group management server to the group management client.

Table 10.2.2.3-1 describes the information flow for the group regroup request from the group management client to the group management server.

Table 10.2.2.4-1 describes the information flow for the group regroup response from the group management server to the group management client.

Table 10.2.2.5-1 describes the information flow group regroup teardown request from the group management client to the group management server.

Table 10.2.2.6-1 describes the information flow group regroup teardown response from the group management server to the group management client.

Table 10.2.2.7-1 describes the information flow group creation notify from the group management server to the MC service server(s).

Table 10.2.2.8-1 describes the information flow group regroup notify from the group management server to the MC service server.

Table 10.2.2.9-1 describes the information flow group regroup teardown notify from the group management server to the MC service server.

Table 10.2.2.10-1 describes the information flow group regroup teardown notification between group management servers and from the group management server to the group management client.

Table 10.2.2.11-1 describes the information flow group regroup teardown notification response between group management servers and from the group management client to the group management server.

Table 10.2.2.12-1 describes the information flow group regroup request between group management servers.

Table 10.2.2.13-1 describes the information flow group regroup response between group management servers.

Table 10.2.2.14-1 describes the information flow group regroup notification between group management servers and from the group management server to the group management client.

Table 10.2.2.15-1 describes the information flow group regroup notification response between group management servers and from the group management client to the group management server.

Table 10.2.2.16-1 describes the information group information query request from group management client to group management server.

Table 10.2.2.17-1 describes the information flow group information query response from group management server to group management client.

Table 10.2.2.18-1 describes the information flow group membership update request from the group management client to the group management server.

Table 10.2.2.19-1 describes the information flow group membership update response from the group management server to the group management client.

Table 10.2.2.20-1 describes the information flow group membership notification from the group management server to the MC service server.

Table 10.2.2.20-2 describes the information flow group membership notification from the group management server to the group management client.

Table 10.2.2.21-1 describes the information flow group deletion request from the group management client to the group management server.

Table 10.2.2.22-1 describes the information flow group deletion response from the group management server to the group management client.

Table 10.2.2.23-1 describes the information flow group deletion notification from the group management server to the MC service server, and from the group management server to the group management clients for MC service users which are members of the group.

Table 10.2.2.24-1 describes the information flow group information provision request from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group.

Table 10.2.2.25-1 describes the information flow group information provision response from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group.

Table 10.2.2.26-1 describes the information flow group information request from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group.

Table 10.2.2.27-1 describes the information flow group information response from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group.

Table 10.2.2.28-1 describes the information flow group information subscribe request from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group.

Table 10.2.2.29-1 describes the information flow group information subscribe response from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group.

Table 10.2.2.30-1 describes the information flow group information notify request from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group.

Table 10.2.2.31-1 describes the information flow group information notify response from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group.

Figure 10.2.4.1-1 below illustrates the group regroup operations to create a temporary group within an MC system. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined. The temporary group formation is applicable only for groups configured with at least one common MC service. The temporary group formation shall be rejected if any of the requested MC services are not common to all MC service groups in the list. The temporary group created can be a broadcast group or a non-broadcast group. The broadcast 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 regroup 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). The broadcast regroup satisfies the temporary group-broadcast group requirements defined in TS 22.179 and is an alternative to the "Temporary group - broadcast group call" procedure (subclause 10.6.2.5.3 in TS 23.379). Pre-conditions:

1. The group management client, group management server, MC service server and the MC service group members belong to the same MC system.
2. The group management client has retrieved the group configurations of the groups to be regrouped.

Figure 10.2.4.2-1 below illustrates the group regroup operations to create a temporary group involving multiple MC systems. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined. Pre-conditions:

1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MC system does not share their users' information to the primary MC system.
2. The primary MC system consists of the group management server 1 and MC service server (primary). The partner MC system consists of the group management server 2 and MC service server (partner).
3. The group management client of the authorized MC service user belongs to the primary MC system.
4. The group management client has retrieved the group configurations of the groups to be regrouped.

Figure 10.2.4.2a-1 below illustrates the tearing down procedure of temporary group created through the group regroup operation. The procedure can be used when, e.g., the specific task for which the temporary group was created has been completed or a busier period occurs. For simplicity, only the teardown case for a temporary group with two MC service groups is represented. The procedure is applicable for more than two groups combined in this temporary group. Pre-condition:

• The temporary group to be torn down is comprised of multiple MC service groups, and is created through the group regrouping procedure as described in subclause 10.2.4.1.

Figure 10.2.4.3-1 below illustrates the tearing down procedure of temporary group created through the group regroup operation. The procedure can be used when, e.g., the specific task for which the temporary group was created has been completed or a busier period occurs. For simplicity, only the teardown case for a temporary group with two MC service groups is represented. The procedure is applicable for more than two groups combined in this temporary group. Pre-conditions:

1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it considers the partner MC system does not share their users' information to the primary MC system.
2. The primary MC system consists of the group management server 1 and MC service server (primary). The partner MC system consists of the group management server 2 and MC service server (partner).
3. The group management client of the authorized MC service user belongs to the primary MC system.
4. The temporary group to be torn down is comprised of multiple MC service groups, and is created through the group regrouping procedure as described in subclause 10.2.4.2.

To prevent routing issues and complexity related to group regrouping, the following rules shall be applied:

• Group regroup in either single MC system or multiple MC systems can take place if:
  • None of the groups to be regrouped are temporary groups; and
  • The groups to be regrouped are not already regrouped into another temporary group; and
  • If the policy of the MC system does not allow a temporary group to include groups that are currently in emergency state, then regrouping of groups can take place if none of the groups to be regrouped are in emergency state.
• If the policy of the MC system allows a temporary group to include groups from other MC systems, group regrouping containing groups with multiple MC systems can take place if:
  • the MC service server (controlling role) for the regrouped group is the MC service server (controlling role) for all MC service groups involved in the regrouping; or
  • the MC service server (controlling role) for the regrouped group is an MC service server (controlling role) for at least one of the MC service groups involved in the regrouping; or
  • the MC service server (controlling role) for the regrouped group is an MC service server homed by at least one of the MC service groups and the MC system of any involved MC service group allows floor control for the set of regrouped groups to be deferred to the MC service server (controlling role) of the temporary group.
• If the policy of the MC system does not allow a temporary group to include groups from other MC systems, regrouping of groups with members spanning multiple MC systems can take place if:
  • the MC service server (controlling role) for the regrouped group is the MC service server (controlling role) for all MC service groups involved in the regrouping; or
  • the MC service server (controlling role) for the regrouped group is an MC service server (controlling role) for at least one of the MC service groups involved in the regrouping, and the MC service servers with the controlling roles for all of the groups that are regrouped are within the same MC system.

An MC service user can request the membership or affiliation list on an MC service group regardless the user's group membership or affiliation.

Figure 10.2.5.2-1 below illustrates the membership or affiliation list query on an MC service group.