Content for TS 23.280 Word version: 18.6.0

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.16.3… 11… 11.3… 11.5… 11.5.2… 11.5.3… 11.5.3.3.2A… 11.5.4… A… B… C…

10.16 Generic procedures for migration 10.16.1 General 10.16.2 Migration during an ongoing group communication
...

10.16 Generic procedures for migration |R18| p. 296

10.16.1 General p. 296

Migration provides a means for an MC service user to obtain MC service directly from a partner MC system. This subclause describes generic procedures for migration which are variations of specific procedures detailed in TS 23.379, TS 23.281 and TS 23.282. These procedures should be read in conjunction with specific procedures in those specifications.

10.16.2 Migration during an ongoing group communication p. 296

10.16.2.1 General p. 296

This provides the capability for an MC service user to migrate to another MC system during an ongoing group communication and to continue the group communication in the other MC system.

10.16.2.2 Procedure p. 296

The procedure is based on the following existing procedures:

MC service group de-affiliation procedure as described in clause 10.8.4.2, or
De-affiliation from MC service group(s) defined in partner MC service system as described in clause 10.8.4.3.
MC service user receiving MC service from a partner MC system as described in clause 10.1.4.3.2.
MC service group affiliation procedure as described in clause 10.8.3.1, or
Affiliation to MC service group(s) defined in partner MC system as described in clause 10.8.3.2 or clause 10.8.3.2a.
Late entry MCPTT group call as described in clause 10.6.2.3.1.1.4 of TS 23.379 (pre-arranged group call) and clause 10.6.2.3.1.2.5 of TS 23.379 (chat group call).
Late entry MCVideo group call as described in clause 7.1.2.3.1.1.4 of TS 23.281 (pre-arranged) and clause 7.1.2.3.1.2.6 of TS 23.281 (chat group call).

Pre-conditions:

The MC service client is a receiving party in one or more ongoing group calls in the primary MC system.
The MC service UE detects the need to change the MC system.

Reproduction of 3GPP TS 23.280, Fig. 10.16.2.2-1: Migration to partner MC system during an ongoing group call

Figure 10.16.2.2-1: Migration to partner MC system during an ongoing group call

Step 1.

The MC service client requests de-affiliation from MC service groups. The MC service groups are either defined in the primary MC system (see clause 10.8.4.2) or the partner MC system (see clause 10.8.4.3).

Step 2.

After migration to the partner MC system, the configuration management client triggers retrieval of the MC service user profile used within the partner MC system (see clause 10.1.4.3.2).

Step 3.

The MC service client requests affiliation to MC service groups. The MCPTT groups are either defined in the primary MC system (see clause 10.8.3.1) or the partner MC system (see clause 10.8.3.2 or clause 10.8.3.2a).

Step 4.

If any of the received group calls are ongoing in the partner MC system, the partner MC system shall initiate a late-entry procedure towards the MC service client. If any of the received group calls are taken place in the primary MC system but not yet in the partner MC system, the affiliation by the migrated MC service UE triggers the late-entry procedure which then includes the MC service UE and the partner MC system into the group call.

The MC service client may indicate the successful migration of group communications to the MC service user.