Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.2.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…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

10.2.3  Group creationp. 104

Figure 10.2.3-1 below illustrates the group creation operations by authorized MC service user/ MC service administrator to create a group. It applies to the scenario of normal group creation by an MC service administrator and user regrouping operations by authorized user/dispatcher.
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 administrator/authorized user/dispatcher is aware of the users' identities which will be combined to form the MC service group.
Reproduction of 3GPP TS 23.280, Fig. 10.2.3-1: Group creation
Up
Step 1.
The group management client of the administrator/dispatcher/authorized MC service user requests group create operation to the group management server. The identities of the users being combined and the information of the MC services that are enabled on the group shall be included in this message.
Step 2a.
If the proposed MC service group ID information element is not present in the group creation request, the group management server generates the MC service group ID. If the proposed MC service group ID information element is present and acceptable to the group management server, the group management server uses the proposed MC service group ID for the new group. If the proposed MC service group ID information element is present but not acceptable to the group management server, the group management server modifies proposed MC service group ID or generates the MC service group ID or rejects the group creation request.
Step 2b.
During the group creation, the group management server stores or creates and stores the information of the group as group configuration data as described in subclause 10.1.5.4. The group management server performs the check on the maximum limit of the total number (Nc6) of MC service group members for the MC service group(s).
Step 3.
The group management server may conditionally notify the MC service server regarding the group creation with the information of the group members (if any). During user regroup, the group management server notifies the MC service server regarding the group creation with the information of the temporary group members. The MC service users of the temporary group may be automatically affiliated, if configured on the MC service server.
Step 4.
The MC service group members (if any) of the MC service group are notified about the newly created MC service group configuration data.
Step 5.
The group management server provides a group creation response to the group management client of the administrator/dispatcher/authorized MC service user. The result information element indicates:
  • success (using proposed MC service group ID); or
  • success (MC service group ID provided by the group management server); or
  • failure (proposed MC service group ID not acceptable); or
  • failure for other reason.
Up

10.2.4  Group regroupingp. 106

10.2.4.1  Temporary group formation - group regrouping within an MC systemp. 106

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.
Reproduction of 3GPP TS 23.280, Fig. 10.2.4.1-1: Group regroup for the groups within the same MC system
Up
Step 1.
The group management client of the MC service user requests group regroup operation to the group management server, which is the group management server of one of the groups to be regrouped. The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group. The group management client indicates whether the temporary group is a broadcast regroup.
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 checks whether group1 or group2 is a temporary group. If group 1 or group2 is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed.
Step 3.
The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, the MC service group ID of the groups being combined, the priority level of the temporary group, the security level of the temporary group, and whether the temporary group is a broadcast regroup. If the authorized MC service user does not specify the security level and the priority level, the group management server shall set the lowest security level and the highest priority of the constituent groups. If MC service types of the groups being combined are not identical, group management server determines the overlapping part and stores the MC service list for the temporary group.
Step 4.
The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups, i.e. temporary MC service group ID, group1's MC service group ID and group2's MC service group ID. If MC service list is included, MC service server stores it and provides MC service types accordingly.
Step 5.
The group management server notifies the affiliated MC service group members of the constituent MC service groups by sending group regroup notification messages.
Step 6.
The affiliated MC service group members of the constituent MC service groups send individual group regroup notification response messages.
Step 7.
The group management server provides a group regroup response to the group management client of the authorized MC service user. If MC service list is included, group management client stores it and initiates MC service types accordingly.
Step 8.
The affiliated MC service group members of the constituent MC service groups individually request group configuration data from the group management server for the temporary group, as described in clause 10.1.5.2. The group configuration data includes security, priority, and other parameters.
Up

Up   Top   ToC