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

Content for  TS 23.280  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.17…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C… 
10.2.4.3 Temporary group tear down involving multiple group host servers  10.2.4.4 Group regroup rules 
...

 

10.2.4.3  Temporary group tear down involving multiple group host servers  p. 113

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.
Reproduction of 3GPP TS 23.280, Fig. 10.2.4.3-1: Temporary group tear down
Figure 10.2.4.3-1: Temporary group tear down
Up
Step 1.
The group management client of the MC service user requests group regroup teardown operation to the group management server 1 (which is the group management server where the temporary group is created and stored). The identity of the temporary group (MC service group ID) being torn down shall be included in this message. This message may route through some other signalling nodes.
Step 2.
The group management server checks whether group regroup operation is performed by an authorized MC service user, based on group policy. The group management server 1 checks whether the MC service group ID is a temporary group. If MC service group ID is not a temporary group, then the group regroup teardown request will be rejected, otherwise the group regroup teardown can proceed.
Step 3.
The group management server 1 tears down the temporary group, i.e., remove the temporary group related information.
Step 4.
The group management server 1 notifies the primary MC service server regarding the temporary group teardown.
Step 5.
Any active group call for the temporary group is preserved until it is completed.
Step 6.
The group management server 1 notifies the affiliated MC service group members regarding the temporary group teardown by sending the group regroup teardown notification (6a) and receives a group regroup teardown notification response (6b) messages.
Step 7.
The group management server 1 sends a group regroup teardown notification (7a) and receives a group regroup teardown notification response (7b) messages with the group management server 2 - group management server in another MC system regarding the temporary group teardown.
Step 8.
The group management server 2 notifies the partner MC service server.
Step 9.
The group management server 2 notifies the affiliated MC service group members regarding the temporary group teardown by sending the group regroup teardown notification (9a) and receives a group regroup teardown notification response (9b) messages. Any active group call for the temporary group is preserved until it is completed.
Step 10.
The group management server 1 provides a group regroup teardown confirmation response to the group management client of the authorized MC service user.
Up

10.2.4.4  Group regroup rules |R15|  p. 114

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.
Up

Up   Top   ToC