10.1.6 MC service UE migration

23.2803GPPCommon functional architecture to support mission critical servicesRelease 18Stage 2TS

10.1.6.1 MC service UE obtains migration connectivity information of partner MC system

Connectivity information for the partner MC system, including MC system identification and access information, is contained in the on-network user profiles for MCPTT in 3GPP TS 23.379 [16], for MCVideo in 3GPP TS 23.281 [12] and for MCData in 3GPP TS 23.282 [13].

10.1.6.2 Signalling plane registration for the MC service UE between the primary and the partner MC systems

The MC service UE performs the following procedure when connecting to a partner MC system for one or more MC services.

Pre-conditions:

1. The MC service UE has successfully obtained migration connectivity information for the partner MC system (see subclause 10.1.6.1).

2. The MC service UE has successfully set-up bearers to the partner MC system’s PDN(s).

3. The configuration management client has secure access to the configuration management server in the primary MC system.

4. The migration management server in the partner MC system has been configured with the mapping between the SIP identities of the partner MC system and the SIP identities of the primary MC system.

Figure 10.1.6.2-1: MC service UE signalling plane registration in a partner MC system

1. The signalling user agent sends a SIP registration request to the SIP core of the partner MC system, which includes the partner MC system SIP identities.

NOTE 1: The signalling user agent uses the partner MC system SIP identities instead of the default SIP private user identity and default SIP public user identity obtained from the MC service UE’s ISIM (as typically occurs when registering to the primary MC system).

2. The SIP core in the partner MC system sends get SIP authentication information request to the migration management server also in the partner MC system, which includes the partner MC system SIP identities received in step 2.

3. The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the partner MC system SIP identities and determines the identifier of the MC service user’s migration management server in the primary MC system and the primary MC system SIP identities.

4. The migration management server in the partner MC system sends get SIP authentication information request to the migration management server in the primary MC system, which includes the primary MC system SIP identities as determined in step 3.

NOTE 2: The messaging in the above step traverses the SIP core / IMS of the partner MC system and the SIP core / IMS of the primary MC system. However, for brevity this is not shown in figure 10.1.6.2-1.

5. The migration management server in the primary MC system sends get SIP authentication information request to the SIP database, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities received in step 4.

6. The SIP database in the primary MC system recognises the primary MC system SIP identities and sends get SIP authentication information response to the migration management server, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities and authentication information (e.g. authentication vectors).

7. The migration management server in the primary MC system sends get SIP authentication information request to the migration management server in the partner MC system, which includes the primary MC system SIP identities and authentication information received in step 6.

NOTE 3: The messaging in the above step traverses the SIP core / IMS of the primary MC system and the SIP core / IMS of the partner MC system. However, for brevity this is not shown in figure 10.1.6.2-1.

8. The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the primary MC system SIP identities, and determines the partner MC system SIP identities.

9. The migration management server in the partner MC system sends get SIP authentication information response to the SIP core also in the partner MC system, which includes the partner MC system SIP identities and the authentication information as received in step 7.

10. The SIP core and MC service UE perform the SIP authentication procedure.

11. The SIP core in the partner MC system sends SIP registration response to the signalling user agent in the MC service UE, which includes an indication that the authentication is successful.