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.15.3.4 Other preconfigured regroup procedures  10.15.3.4.1 Adding newly affiliated user to preconfigured group regroup  10.15.3.4.2 Updating the MC service ID list in a preconfigured regroup group based on user regroup  10.15.3.4.3 Adding a user to regroup group due to communication request to the group being regrouped  10.15.3.4.4 Regroup group cancel notification due to communication request to the cancelled regroup group 
...

 

10.15.3.4  Other preconfigured regroup procedures  p. 302

10.15.3.4.1  Adding newly affiliated user to preconfigured group regroup  p. 302
Figure 10.15.3.4.1-1 illustrates the procedure to add a newly affiliated user to an in-progress preconfigured MC service group regroup operation.
Pre-conditions:
  • The MC service client is a member of a MC service group that is part of an in-progress preconfigured group regroup operation.
  • The MC service group identity and group configuration for the preconfigured MC service group has been preconfigured in the MC service client, and the MC service client has received the relevant security related information to allow it to communicate in the MC service regroup group.
Reproduction of 3GPP TS 23.280, Fig. 10.15.3.4.1-1: Procedure to add a newly affiliated user to a preconfigured group regroup
Figure 10.15.3.4.1-1: Procedure to add a newly affiliated user to a preconfigured group regroup
Up
Step 1.
The MC service client affiliates to an MC service group that is currently part of an in-progress preconfigured group regroup. The affiliation follows the procedure in section 10.8.3.1 of this specification.
Step 2.
The MC service server retrieves the MC service group ID of the regroup group and the MC service group ID of the group from which configuration information for the regroup group is to be taken.
Step 3.
The MC service server sends the preconfigured regroup request to the MC service client.
Step 4.
The MC service client notifies the user of the regrouping.
Step 5.
The MC service client may send the preconfigured regroup response to the MC service server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request.
Step 6.
The MC service server affiliates the regrouped MC service client to the regroup group.
Up
10.15.3.4.2  Updating the MC service ID list in a preconfigured regroup group based on user regroup |R18|  p. 303
Figure 10.15.3.4.2-1 illustrates the procedure to add or remove an MC service user based on the MC service user criteria known at the MC service server.
Preconditions:
  • A preconfigured regroup group has been established.
  • The MC service server has selected MC service user 2 to participate in the preconfigured regroup group based on MC service user criteria known at the MC service server.
Reproduction of 3GPP TS 23.280, Fig. 10.15.3.4.2-1: Procedure to update the MC service ID list
Figure 10.15.3.4.2-1: Procedure to update the MC service ID list
Up
Step 1.
The MC service server detects that MC service client 2, which has been earlier included in the preconfigured regroup group, no longer meets the MC service user criteria known at the MC service server.
Step 2.
The MC service sends MC service client 2 a preconfigured user regroup remove request.
Step 3.
The MC service client 2 notifies the MC service user of the preconfigured user regroup removal.
Step 4.
The MC service client 2 may send the MC service server a preconfigured user regroup remove response to acknowledge the preconfigured user regroup removal.
Step 5.
The MC service server updates the preconfigured regroup group (including the MC service user ID list) and potential group communication.
Step 6.
The MC service server detects that the MC service client 3 meets the MC service user criteria.
Step 7.
The MC service server sends the MC service client 3 a preconfigured regroup request.
Step 8.
The MC service client 3 notifies the MC service user of the preconfigured regroup request.
Step 9.
The MC service client 3 may send the MC service server a preconfigured regroup response.
Step 10.
The MC service server updates the preconfigured regroup group (including the MC service user ID list), and potential group communication.
Up
10.15.3.4.3  Adding a user to regroup group due to communication request to the group being regrouped |R19|  p. 304
Figure 10.15.3.4.3-1 illustrates the procedure of adding a user to regroup group due to the user initiating a comunication request to the group involved in an in-progress preconfigured MC service group regroup.
Pre-conditions:
  • The MC service client is an affiliated member of MC service group A that is part of an in-progress preconfigured group regroup with MC service groups B and C.
  • MC servicec group D is being used as the regroup group.
  • The MC service client has missed the preconfigured regroup request message (e.g. poor signalling conditions, race condition).
Reproduction of 3GPP TS 23.280, Fig. 10.15.3.4.3-1: Procedure for communication request on MC service group during an in-progress group regroup
Figure 10.15.3.4.3-1: Procedure for communication request on MC service group during an in-progress group regroup
Up
Step 1.
The MC service client attempts to start a communication on MC service group A. The MC service server identifies that the MC service group A is currently part of an in-progress preconfigured group regroup. In this case, the MC service server rejects the communication. The procedure of signalling interactions between the MC service client and the MC service server for MCPTT, MCVideo and MCdata is specified in TS 23.379, TS 23.281, TS 23.282 accordingly.
Step 2.
The MC service server sends the preconfigured regroup request to the MC service client containing the MC service group ID of the preconfigured group, and the MC service group ID of the regroup group.
Step 3.
The MC service client notifies the user of the regrouping procedure.
Step 4.
The MC service client sends the preconfigured regroup response to the MC service server to acknowledge the regrouping action.
Step 5.
The MC service server affiliates the regrouped MC service client into the regroup group.
Up
10.15.3.4.4  Regroup group cancel notification due to communication request to the cancelled regroup group |R19|  p. 305
Figure 10.15.3.4.4-1 illustrates the procedure of notifying about the cancellation of the regroup group when a user initiates a communication to a regroup group after the MC service group regroup has been cancelled.
Pre-conditions:
  • The MC service client is a member of MC service group A that was part of an in-progress preconfigured group regroup with MC service groups B and C that has been cancelled. MC service group D was used as the MC service regroup group.
  • The MC service client has missed the preconfigured regroup cancel request message (e.g. poor signalling conditions, race condition).
Reproduction of 3GPP TS 23.280, Fig. 10.15.3.4.4-1: Procedure for communication request to regroup group after the regrouping cancellation
Figure 10.15.3.4.4-1: Procedure for communication request to regroup group after the regrouping cancellation
Up
Step 1.
The MC service client attempts to start a communication on MC service group D, which is the regroup group. The MC servce server identifies regroup group is no longer active or exist.
Step 2.
The MC service server may send the preconfigured regroup cancel request to the MC service client.
Step 3.
The MC service client may notify the user of the regrouping cancellation.
Step 4.
The MC service client may send the preconfigured regroup cancel response to the MC service server to acknowledge the regrouping cancellation.
Up

Up   Top   ToC