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.283  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   10…   10.2…   10.3…   10.3.2   10.3.3…   10.3.4…   10.3.5…   10.3.6…   10.3.7…   10.3.8…   10.4…   10.5…   10.6…   10.6.2…   10.6.3…   10.7…   10.8…   10.11…   10.12…   10.14…   10.15…   10.17… 
10.2 Group management  10.2.1 Information flows for group management  10.2.2 Group regrouping  10.2.2.1 General  10.2.2.2 MC system initiates the group regroup  10.2.2.3 IWF initiates the group regroup  10.2.2.4 Ownership of the group regroup  10.2.2.5 Simultaneous group regroup requests from each side of the IWF-1 interface  10.2.2.6 Resolution of vocoder and encryption mode for the group regroup  10.2.3 Group configuration for interworking  10.2.3.1 Overview  10.2.3.2 MC system provides group configuration to the IWF  10.2.3.3 IWF requests group configuration from the MC system  10.2.3.4 IWF provides group configuration to the MC system  10.2.3.5 MC system requests group configuration from the IWF  10.2.3.6 IWF subscribes to group configuration  10.2.3.7 MC system notifies group configuration  10.2.3.8 MC system subscribes to group configuration  10.2.3.9 IWF notifies group configuration 
...

 

10.2  Group management  p. 23

10.2.1  Information flows for group management  p. 23

10.2.1.1  General  p. 23

The following subclauses define information flows for group management on the IWF-1 interface. Group management related information flows on reference points other than IWF-1 are defined in TS 23.280.

10.2.1.2  IWF group regroup teardown notification  p. 23

Table 10.2.1.2-1 describes the information flow IWF group regroup teardown notification between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group IDMMC service group ID of the temporary group which is torn down
Up

10.2.1.3  IWF group regroup teardown notification response  p. 23

Table 10.2.1.3-1 describes the information flow IWF group regroup teardown notification response between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group IDMMC service group ID of the temporary group which was torn down
ResultMIndicates success or failure of the notification
Up

10.2.1.4  IWF group regroup request  p. 23

Table 10.2.1.4-1 describes the information flow IWF group regroup request between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group ID listMList of constituent MC service group IDs
Up

10.2.1.5  IWF group regroup response  p. 23

Table 10.2.1.5-1 describes the information flow IWF group regroup response between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group IDO (see NOTE)MC service group ID of the temporary group
MC service group ID listMList of constituent MC service group IDs
ResultMIndicates whether the IWF group regroup was accepted or rejected
NOTE:
Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present.
Up

10.2.1.6  IWF group regroup notification  p. 24

Table 10.2.1.6-1 describes the information flow IWF group regroup notification between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group ID listMList of constituent MC service group IDs
MC service group IDMMC service group ID of the temporary group
Priority levelORequired priority level for the temporary group
Security level (see NOTE)ORequired security level for the temporary group
NOTE:
Security level refers to the configuration of media and floor control protection parameters as listed in TS 23.280.
Up

10.2.1.7  IWF group regroup notification response  p. 24

Table 10.2.1.7-1 describes the information flow IWF group regroup notification response between the group management server and the IWF or between the IWF and the group management server.
Information Element Status Description
MC service group ID listMList of constituent MC service group IDs
MC service group IDMMC service group ID of the temporary group
Priority levelMRequired priority level for the temporary group
Security levelMRequired security level for the temporary group
Up

10.2.1.8  IWF group information request  p. 24

Table 10.2.1.8-1 describes the IWF group information request from the IWF to the group management server or from the group management server to the IWF.
Information Element Status Description
MC service group IDMThe identity of the MC service group.
Up

10.2.1.9  IWF group information response  p. 24

Table 10.2.1.9-1 describes the IWF group information response from the group management server to the IWF or the IWF to the group management server.
Information Element Status Description
MC service group IDMThe identity of the MC service group.
MC service group provisioning informationO (see NOTE 1)The group information retrieved from the group management server or from the IWF in the case where the IWF is performing the provision.
ResultO (see NOTE 2)Indicates reason for failure to provide MC service group configuration information
NOTE 1:
Shall be present if the request can be fulfilled.
NOTE 2:
Shall be present if the request cannot be fulfilled.
Up

10.2.1.10  IWF group information provision request  p. 24

Table 10.2.1.10-1 describes the IWF group information provision request from the group management server to the IWF or the IWF to the group management server.
Information Element Status Description
MC service group IDMThe identity of the MC service group.
MCPTT group configuration informationMThe group information retrieved from the group management server or from the IWF in the case where the group is defined in the IWF.
Up

10.2.1.11  IWF group information provision response  p. 25

Table 10.2.1.11-1 describes the IWF group information provision response from the IWF to the group management server or from the group management server to the IWF.
Information Element Status Description
MC service group IDMThe identity of the MC service group
ResultMIndicates success or failure of reception, modification and storage of MC service group configuration information
Up

10.2.1.12  IWF group information subscribe request  p. 25

Table 10.2.1.12-1 describes the information flow IWF group information subscribe request from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Information Element Status Description
MC service group IDMMC service group ID of the group
MC services requestedOService(s) for which group configuration is requested; one or more of MCPTT, MCData
Up

10.2.1.13  IWF group information subscribe response  p. 25

Table 10.2.1.13-1 describes the information flow IWF group information subscribe response from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Information Element Status Description
MC service group IDMMC service group ID of the group
ResultMIndicates success or failure of the subscribe request
Up

10.2.1.14  IWF group information notify request  p. 25

Table 10.2.1.14-1 describes the information flow IWF group information notify request from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group.
Information Element Status Description
MC service group IDMMC service group ID of the group
MC service group information reference (see NOTE)OReference to information stored relating to the MC service group
Group related key material (see NOTE)OKey material for use with the MC service group
NOTE:
At least one of these information elements shall be present.
Up

10.2.1.15  IWF group information notify response  p. 26

Table 10.2.1.15-1 describes the information flow IWF group information notify response from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group.
Information Element Status Description
MC service group IDMMC service group ID of the group
ResultMIndicates success or failure of the notification request
Up

10.2.2  Group regrouping  p. 26

10.2.2.1  General  p. 26

The procedures in TS 23.280 are followed, but with changes required for interworking. The IWF will behave on the interface as if it is a peer MC service server with a peer group management client and peer group management server.
Exceptions to the TS 23.280 procedures are detailed in the subclauses below.

10.2.2.2  MC system initiates the group regroup  p. 26

The MC system can initiate a group regroup that includes groups defined at the IWF. The IWF is informed and may reject the regroup if conditions do not allow it to support the regroup. This is described in Figure 10.2.2.2-1.
Pre-conditions:
  1. The group management client has retrieved the group configurations of the groups to be regrouped.
  2. At least one MC service group has been defined in the MC system.
  3. At least one MC service group has been defined in the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.2.2.2-1: Group regrouping to an IWF
Figure 10.2.2.2-1: Group regrouping to an IWF
Up
Step 1.
The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server (which is the group management server of one of the MC service 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.
Step 2.
The group management server checks whether group regroup operation is performed by an authorised MC service user, based on group policy. The group management server checks whether the group is a temporary group. If the group is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed.
Step 3.
The group management server forwards the IWF group regroup request to the IWF with the information about the IWF's groups.
Step 4.
The IWF provides an IWF group regroup response. Due to security aspects concerning sharing information among different MC systems, the IWF does not share the users' information of the groups under its management to the group management server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping)
Step 5.
The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the authorised MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups.
Step 6.
The group management server notifies the IWF about its group regroup operation.
Step 7.
The IWF acknowledges the group management server.
Step 8.
The group management server notifies the MC service server of the temporary group creation with the information of the constituent groups.
Step 9.
The MC service server acknowledges the notification from the group management server.
Step 10.
The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of lower security level.
Step 11.
The group management server provides a group regroup response to the group management client of the authorised MC service user (e.g. dispatcher).
Up

10.2.2.3  IWF initiates the group regroup  p. 28

The procedure in TS 23.280 is followed, except for steps 1 and 2. The IWF will behave on the interface as if it is a peer MC service server with a peer group management server. This is described in Figure 10.2.2.3-1.
Pre-conditions:
  1. At least one MC service group has been defined in the MC system.
  2. At least one MC service group has been defined in the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.2.2.3-1: Group regrouping from an IWF
Figure 10.2.2.3-1: Group regrouping from an IWF
Up
Step 1.
The IWF sends an IWF group regroup request to the group management server.
Step 2.
The group management server checks whether the group can be included in a temporary group.
Step 3.
The group management server provides an IWF group regroup response.
Step 4.
The IWF notifies the group management server regarding the temporary group creation with information of the constituent groups.
Step 5.
The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups.
Step 6.
The MC service server acknowledges the notification from the group management server. The MC service server may reject the IWF group regroup, e.g. if one of its constituent groups is already in a regroup.
Step 7.
The group management server acknowledges the notification from the IWF.
Step 8.
The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of a lower security level.
Up

10.2.2.4  Ownership of the group regroup  p. 29

The group management server that performs the group regroup operation owns the temporary group created by the regroup, as implied in TS 23.280.

10.2.2.5  Simultaneous group regroup requests from each side of the IWF-1 interface  p. 29

To prevent routing issues and complexity that could result from regrouping the same users from both sides of the interface, the following rules can be applied:
  • If group regrouping signalling using temporary groups is used on the MC system, the IWF must prevent the regroup signalling from propagating to the LMR system if the LMR system does not support regrouping;
  • the IWF must handle the translation between temporary group identities on the MC system and the original interworking group identities used on the LMR system; and
  • the regrouping rules in subclause 10.2.4.4 of TS 23.280 also apply.
Up

10.2.2.6  Resolution of vocoder and encryption mode for the group regroup  p. 29

If one of the LMR groups to be included in a group regroup requires the use of LMR E2EE the preferred voice codecs for an MCPTT temporary group should be LMR codecs. If any of the mission critical users to be included in this MCPTT temporary group do not support LMR E2EE or the preferred LMR codecs, voice calls using LMR E2EE will fail for those users.
Up

10.2.3  Group configuration for interworking  p. 29

10.2.3.1  Overview  p. 29

The procedures in the following subclauses describe the process for sharing group configuration from an MC system to an IWF where the IWF needs to make use of the MC service group and from an IWF to an MC system where the MC system's clients need to make use of the group. The procedures in this subclause are based upon subclause 10.2.7 in TS 23.280.

10.2.3.2  MC system provides group configuration to the IWF  p. 30

Figure 10.2.3.2-1 below illustrates the case where the MC system provides the group configuration to the IWF, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the IWF.
Pre-conditions:
  1. The MC service group is defined in the MC system.
  2. One or more LMR users are members of the group.
  3. The MC system of the MC service group has been configured with addressing information for the group management function in the IWF.
  4. The MC system of the MC service group is authorized to provide group configuration information to the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.2-1: MC system provides group configuration to the IWF
Figure 10.2.3.2-1: MC system provides group configuration to the IWF
Up
Step 1.
The group management server in the MC system of the MC service group provides the configuration information related to the MC service group to the IWF.
Step 2.
The IWF responds to the group management server of the MC system of the MC service group that the configuration has been received and stored correctly.

10.2.3.3  IWF requests group configuration from the MC system  p. 30

Figure 10.2.3.3-1 below illustrates the case where the IWF requests the group configuration from the MC system, for example because a user on the IWF is a member of the group.
Pre-conditions:
  1. The MC service group is defined in the MC system.
  2. One or more LMR users are members of the group.
  3. The IWF does not have the configuration for the MC service group stored.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.3-1: Partner MC system requests group configuration from primary MC system
Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system
Up
Step 1.
The IWF requests the group configuration from the group management server in the primary MC system of the MC service group.
Step 2.
The group management server in the MC system of the MC service group provides the requested group configuration information.

10.2.3.4  IWF provides group configuration to the MC system  p. 31

Figure 10.2.3.4-1 below illustrates the case where the IWF provides the group configuration to the MC system, e.g. due to an action by an administrator or because some of the IWF's MC service group members are homed on the MC system.
Pre-conditions:
  1. The group is defined in the IWF.
  2. One or more MC service users are members of the group.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.4-1: MC system provides group configuration to the IWF
Figure 10.2.3.4-1: MC system provides group configuration to the IWF
Up
Step 1.
The IWF provides the configuration information related to the group to the group management server in the MC system.
Step 2.
The group management server in the MC system responds to the IWF that the configuration has been received and stored correctly.

10.2.3.5  MC system requests group configuration from the IWF  p. 32

Figure 10.2.3.5-1 below illustrates the case where the MC system requests the group configuration from the IWF, for example because an MC service user receiving service in the MC system has the group configured in the user profile.
Pre-conditions:
  1. The MC service group is defined in the IWF.
  2. One or more MC service users are members of the group.
  3. The group management server in the MC system does not have the configuration for the MC service group stored.
  4. The MC system has been configured with addressing information for the group management function in the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.5-1: Partner MC system requests group configuration from primary MC system
Figure 10.2.3.5-1: Partner MC system requests group configuration from primary MC system
Up
Step 1.
The MC system requests the group configuration from the group management function in the IWF.
Step 2.
The IWF provides the requested group configuration information.

10.2.3.6  IWF subscribes to group configuration  p. 32

The procedure for subscription from IWF for group configuration information to the group management server in the primary MC system of the MC service group is shown in Figure 10.2.3.6-1.
Pre-conditions:
  1. The MC service group is defined in its MC system.
  2. One or more group members are defined in the LMR system.
  3. The IWF has received group information from the GMS in the primary MC system of the MC service group.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration
Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration
Up
Step 1.
The IWF subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group.
Step 2.
The group management server in the primary MC system of the MC service group sends an IWF group information subscribe response to IWF indicating success or failure of the request.

10.2.3.7  MC system notifies group configuration  p. 33

The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the IWF is shown in Figure 10.2.3.7-1.
Pre-conditions:
  1. The IWF has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group.
  2. The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.7-1: Notification of group configuration information to the IWF
Figure 10.2.3.7-1: Notification of group configuration information to the IWF
Up
Step 1.
The group management server in the primary MC system of the MC service group sends an IWF group information notify request to the IWF.
Step 2.
The IWF sends an IWF group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification.

10.2.3.8  MC system subscribes to group configuration  p. 33

The procedure for subscription by the group management server in the MC system to the IWF for group configuration information is shown in Figure 10.2.3.8-1.
Pre-conditions:
  1. The group is defined in the LMR system.
  2. One or more group members are defined in the MC system.
  3. The group management server in the MC system has received group information from the IWF.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration
Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration
Up
Step 1.
The group management server of the MC system subscribes to the group configuration information stored in the IWF.
Step 2.
The IWF provides an IWF group information subscribe response to group management server of the MC system indicating success or failure of the request.

10.2.3.9  IWF notifies group configuration  p. 34

The procedure for notification of group information from the IWF to the group management server in the MC system is shown in Figure 10.2.3.9-1.
Pre-conditions:
  1. The group management server of the MC system has subscribed to the group configuration information for the group in the IWF.
  2. The IWF has new information for the group.
Reproduction of 3GPP TS 23.283, Fig. 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group
Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group
Up
Step 1.
The IWF sends an IWF group information notify request to the group management server in the MC system.
Step 2.
The group management server in the MC system sends an IWF notify group information notify response to the IWF indicating the success or failure of the notification.

Up   Top   ToC