Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.781
Word version: 15.0.0
1…
4…
4
Migration and interconnection scenarios
5
Key Issues
6
Solutions
7
Overall Evaluation
8
Conclusions
$
Change history
4
Migration and interconnection scenarios
p. 8
4.1
Generic scenarios
p. 8
4.1.1
Scenario 1: UE in visited network using partner MC system with connection to primary MC system (migration)
p. 8
4.1.2
Scenario 2: Communicating between UEs in different home networks using different primary MC systems (interconnection)
p. 9
4.1.3
Further migration and interconnection scenarios
p. 9
4.2
MC service communication scenarios
p. 9
4.2.1
Scenario 1: Group communications
p. 9
4.2.1.1
Migrated UE communicates in group defined in partner MCPTT system
p. 9
4.2.1.2
Migrated UE communicates in group defined in primary MCPTT system
p. 10
4.2.1.3
Group communications between interconnected primary MCPTT systems
p. 11
4.2.1.4
Further group call scenarios
p. 11
4.2.2
Scenario 2: Private communications
p. 12
4.2.2.1
General
p. 12
4.2.2.2
UE A and UE Z in primary MC systems communicate using interconnection function
p. 12
4.2.2.3
UE A migrated to primary MC system of UE Z
p. 12
4.2.2.4
UE A migrated to partner MC system that is different from primary MC system of UE Z
p. 13
4.2.2.5
UE A and UE Z both migrated to different partner MC systems
p. 13
4.2.2.6
UE A and UE Z both migrated to the same partner MC system
p. 14
4.2.2.7
UE A migrated to the partner MC system communicating with UE B in primary MC system, which is primary MC system of UE A
p. 14
5
Key Issues
p. 15
5.1
Key Issues for interconnection
p. 15
5.1.1
Key issue 1.1: MC system authorization to support interconnection calls
p. 15
5.1.1.1
Description
p. 15
5.1.1.2
Architectural Requirements
p. 15
5.1.2
Key issue 1.2: Identification of users and groups in interconnection calls
p. 16
5.1.2.1
Description
p. 16
5.1.2.2
Architectural Requirements
p. 16
5.1.3
Key issue 1.3: Authorization for interconnection private calls
p. 16
5.1.3.1
Description
p. 16
5.1.3.2
Architectural Requirements
p. 16
5.1.4
Key issue 1.4: Affiliation and authorization for interconnection MC service group calls
p. 17
5.1.4.1
Description
p. 17
5.1.4.2
Architectural Requirements
p. 17
5.1.5
Key issue 1.5: MC service group configuration for group defined in partner MC system
p. 17
5.1.5.1
Description
p. 17
5.1.5.2
Architectural Requirements
p. 17
5.1.6
Key issue 1.6: Controlling MC service server and system for interconnection private calls
p. 17
5.1.6.1
Description
p. 17
5.1.6.2
Architectural Requirements
p. 18
5.1.7
Key issue 1.7: Media routing for interconnection private calls
p. 18
5.1.7.1
Description
p. 18
5.1.7.2
Architectural Requirements
p. 18
5.1.8
Key issue 1.8: Media routing for interconnection MC service group calls
p. 18
5.1.8.1
Description
p. 18
5.1.8.2
Architectural Requirements
p. 18
5.1.9
Key issue 1.9: Security for interconnection calls
p. 19
5.1.9.1
Description
p. 19
5.1.9.2
Architectural Requirements
p. 19
5.1.10
Key issue 1.10: MC system network topology hiding
p. 19
5.1.10.1
Description
p. 19
5.1.10.2
Architectural Requirements
p. 19
5.1.11
Key issue 1.11: Bearer control for interconnection calls
p. 19
5.1.11.1
Description
p. 19
5.1.11.2
Architectural Requirements
p. 20
5.1.12
Key issue 1.12: Group membership
p. 20
5.1.12.1
Description
p. 20
5.1.12.2
Architectural requirements
p. 20
5.2
Key Issues for migration
p. 20
5.2.1
Key issue 2.1: MC authorization for migration
p. 20
5.2.1.1
Description
p. 20
5.2.1.2
Architectural Requirements
p. 21
5.2.2
Key issue 2.2: Authentication at MC service application layer of MC service users during migration
p. 21
5.2.2.1
Description
p. 21
5.2.2.2
Architectural Requirements
p. 21
5.2.3
Key issue 2.3: Connectivity to partner MC system for migration
p. 22
5.2.3.1
Description
p. 22
5.2.3.2
Architectural Requirements
p. 22
5.2.4
Key issue 2.4: Tracking current MC system of MC service users during migration
p. 22
5.2.4.1
Description
p. 22
5.2.4.2
Architectural Requirements
p. 23
5.2.5
Key issue 2.5: Identification of migrated MC system during migration
p. 23
5.2.5.1
Description
p. 23
5.2.6
Key issue 2.6: Authorization, configuration and affiliation for MC service group calls during migration
p. 23
5.2.6.1
Description
p. 23
5.2.7
Key issue 2.7: Definition of controlling MC service server and media routing between MC service servers during migration
p. 23
5.2.7.1
Description
p. 23
5.2.8
Key issue 2.8: Security for calls whilst migrated
p. 23
5.2.8.1
Description
p. 23
5.2.8.2
Architectural Requirements
p. 24
5.2.9
Key issue 2.9: Migration during link failure conditions
p. 24
5.2.9.1
Description
p. 24
5.2.10
Key issue 2.10: Media routing during migration for logging and lawful interception
p. 24
5.2.10.1
Description
p. 24
5.2.10.2
Architectural Requirements
p. 24
6
Solutions
p. 25
6.1
Solution 1: System authorization and configuration for interconnection and migration
p. 25
6.1.1
Description
p. 25
6.1.2
Impacts on existing nodes and functionality
p. 26
6.1.3
Solution Evaluation
p. 26
6.2
Solution 2: Connectivity to partner MC system for migration
p. 26
6.2.1
Description
p. 26
6.2.2
Impacts on existing nodes and functionality
p. 29
6.2.3
Solution Evaluation
p. 30
6.3
Solution 3: Call control and media routing for MCPTT group calls for interconnection
p. 31
6.3.1
Description of solution
p. 31
6.3.2
Impacts on existing nodes and functionality
p. 32
6.3.3
Solution Evaluation
p. 32
6.4
Solution 4: User authorization and configuration for interconnection
p. 32
6.4.1
Description
p. 32
6.4.2
Impacts on existing nodes and functionality
p. 33
6.4.3
Solution Evaluation
p. 33
6.5
Solution 5: Group configuration management for interconnection
p. 34
6.5.1
Description of solutions
p. 34
6.5.1.1
Solution 5.1: Gateway in primary MC system of MC service users
p. 34
6.5.1.2
Solution 5.2: Gateway in primary MC system of MC service groups
p. 35
6.5.1.3
Solution 5.3: Gateways in primary MC system of MC service groups and primary MC system of MC service users
p. 36
6.5.2
Impacts on existing nodes and functionality
p. 36
6.5.3
Solution Evaluation
p. 36
6.6
Solution 6: User authorization and configuration for migration
p. 37
6.6.1
Description
p. 37
6.6.2
Impacts on existing nodes and functionality
p. 39
6.6.3
Solution Evaluation
p. 39
6.7
Solution 7: User profile management for migration - Partner MC system CMS configures UE
p. 39
6.7.1
Description
p. 39
6.7.2
Impacts on existing nodes and functionality
p. 42
6.7.3
Solution Evaluation
p. 42
6.8
Solution 8: User profile management for migration - Primary MC system CMS configures UE
p. 42
6.8.1
Description
p. 42
6.8.2
Impacts on existing nodes and functionality
p. 45
6.8.3
Solution Evaluation
p. 45
6.9
Solution 9: Controlling system and media routing for interconnection private calls
p. 46
6.9.1
Description
p. 46
6.9.2
Impacts on existing nodes and functionality
p. 47
6.9.3
Solution Evaluation
p. 47
6.10
Solution 10: Migration service authorization
p. 47
6.10.1
Description
p. 47
6.10.2
Impacts on existing nodes and functionality
p. 49
6.10.3
Solution Evaluation
p. 49
6.11
Solution 11: Migrated private call
p. 49
6.11.1
Description
p. 49
6.11.1.1
General
p. 49
6.11.1.2
Private call from UE Z to migrated UE A across different MC systems
p. 50
6.11.1.3
Private call from migrated UE A to UE Z across different MC systems
p. 52
6.11.1.4
Private call from UE Z to migrated UE A within the same MC system
p. 53
6.11.1.5
Private call from migrated UE A to UE Z within the same MC system
p. 54
6.11.1.6
Private call in remaining migration scenarios
p. 56
6.11.2
Impacts on existing nodes and functionality
p. 56
6.11.3
Solution Evaluation
p. 57
6.12
Solution 12: Affiliation for logging during migration
p. 57
6.12.1
Description
p. 57
6.12.2
Impacts on existing nodes and functionality
p. 59
6.12.3
Solution evaluation
p. 59
7
Overall Evaluation
p. 59
7.1
General
p. 59
7.2
Solution evaluation
p. 59
7.3
Key issues with no associated solutions
p. 64
7.4
Key issues with security implications
p. 65
8
Conclusions
p. 65
$
Change history
p. 66