Content for TR 23.779 Word version: 13.0.0
5 Candidate solutions
5.1 Off-network operations
5.2 On-network operations
5.3 UE-to-network relay
5.4 Group management
...
...
5 Candidate solutions p. 19
5.1 Off-network operations p. 19
5.1.1 Solution 1-1: Distributed mesh support for MCPTT off-network MCPTT group calls p. 19
5.1.1.1 Functional description p. 19
5.1.1.2 Procedures p. 20
5.1.1.3 Impact on existing entities and interfaces p. 20
5.1.1.4 Solution evaluation p. 20
5.1.2 Solution 1-2: Off-network MCPTT service using ProSe UE-to-UE relay p. 20
5.1.2.1 Functional description p. 20
5.1.2.2 Procedures p. 22
5.1.2.2.1 General p. 22
5.1.2.2.2 Registration for MCPTT service and MCPTT group communication setup p. 22
5.1.2.2.3 Floor control procedure p. 23
5.1.2.3 Impact on existing entities and interfaces p. 24
5.1.2.4 Solution evaluation p. 25
5.1.3 Solution 1-3: Application level device to device relay operation for off-network MCPTT p. 25
5.1.3.1 Functional description p. 25
5.1.3.1.1 Detecting the relay opportunity p. 25
5.1.3.1.2 Selecting the best of multiple relay choices p. 25
5.1.3.1.3 Relay routes p. 26
5.1.3.1.4 Message structure to support relay p. 26
5.1.3.1.5 Message flows for relay p. 27
5.1.3.1.5.1 Message flows for preferred approach for relay setup p. 27
5.1.3.1.5.2 Message flows for relay deactivation p. 28
5.1.3.1.5.3 Message flows for alternative approach for relay setup p. 29
5.1.3.1.6 Operation for devices in direct communication p. 30
5.1.3.1.7 Operation for devices sending relay accept messages p. 30
5.1.3.1.8 Operation for devices receiving relay accept messages p. 30
5.1.3.1.9 Operation for devices sending relay deactivate messages p. 30
5.1.3.1.10 Operation for devices receiving relay deactivate messages p. 30
5.1.3.1.11 Relaying messages p. 31
5.1.3.2 Impact on existing entities and interfaces p. 31
5.1.3.3 Solution evaluation p. 31
5.1.4 Solution 1-4: Group priority solution for off-network communication when UE in coverage of PLMN network p. 31
5.1.4.1 Procedures p. 31
5.1.4.2 Impact on existing entities and interfaces p. 33
5.1.4.3 Solution evaluation p. 33
5.1.5 Solution 1-5: MCPTT off-network p. 33
5.1.5.1 Functional description p. 33
5.1.5.2 Procedures p. 33
5.1.5.2.1 Call Setup p. 33
5.1.5.2.2 Floor Control p. 35
5.1.5.3 Impact on existing entities and interfaces p. 36
5.1.5.4 Solution evaluation p. 36
5.1.5.4.1 Analysis of solutions p. 36
5.1.5.4.2 Summary p. 37
5.2 On-network operations p. 38
5.2.1 Solution 2-1: IMS based architecture for MCPTT applications p. 38
5.2.1.1 Functional description p. 38
5.2.1.1.1 Overall architecture p. 38
5.2.1.1.2 Functionalities and capabilities already provided by existing technologies p. 41
5.2.1.1.2.1 Functionalities and capabilities already provided by IMS p. 41
5.2.1.1.2.2 Functionalities and capabilities already provided by OMA PCPS p. 41
5.2.1.1.2.3 Functionalities and capabilities already provided by other entities p. 42
5.2.1.1.3 Overview of reference points p. 42
5.2.1.1.4 Reference Points Mapping p. 43
5.2.1.1.5 New Functional Entities p. 46
5.2.1.1.5.1 The Public Safety User Data Function (PS-UDF) p. 46
5.2.1.1.5.2 The MCPTT Application Server (MCPTT AS) p. 49
5.2.1.1.5.3 The MCPTT Server p. 50
5.2.1.1.5.4 Group Management Function (GMF) p. 50
5.2.1.1.5.5 XML Document Server (XDMS) p. 50
5.2.1.1.5.6 MCPTT Interworking Function (MCPTT IWF) p. 50
5.2.1.2 Procedures p. 50
5.2.1.2.1 Registration information flow - MCPTT UE not registered p. 50
5.2.1.2.2 MCPTT interaction with telephony service p. 52
5.2.1.3 Impact on existing entities and interfaces p. 54
5.2.1.4 Solution evaluation p. 54
5.2.2 Solution 2-2: NGCN-based architecture p. 55
5.2.2.1 Functional Description p. 55
5.2.2.2 Procedures p. 57
5.2.2.3 Impact on existing entities and interfaces p. 59
5.2.2.4 Solution evaluation p. 59
5.2.3 Solution 2-3: Generic high level architecture for MCPTT within a public safety ecosystem with user-based services application sublayer p. 59
5.2.3.1 Functional description p. 59
5.2.3.2 Procedures p. 62
5.2.3.2.1 Detailed user authentication procedure information flow p. 63
5.2.3.2.2 Registration and user authentication information flow for a single domain p. 64
5.2.3.2.3 Detailed user authentication Information Flow (two domains) p. 66
5.2.3.3 Impact on existing entities and interfaces p. 67
5.2.3.4 Solution evaluation p. 67
5.2.4 Solution 2-4: Application domain routing over non-trusted SIP core p. 67
5.2.4.1 Functional description p. 67
5.2.4.1.1 Principles p. 67
5.2.4.1.2 Management of identities p. 68
5.2.4.1.3 SIP routing principles p. 68
5.2.4.1.4 Architecture p. 70
5.2.4.2 Procedures p. 74
5.2.4.2.1 Authentication and discovery of IMS identities and parameters p. 74
5.2.4.2.2 Registration p. 75
5.2.4.2.3 Permanent NAT traversal p. 76
5.2.4.2.4 Originating procedure p. 77
5.2.4.2.5 Terminating procedure p. 77
5.2.4.3 Impact on existing entities and interfaces p. 78
5.2.4.4 Solution evaluation p. 79
5.3 UE-to-network relay p. 79
5.3.1 Solution 3-1: ALG relay for MCPTT UE-to-network relay p. 79
5.3.1.1 Functional description p. 79
5.3.1.2 Procedures p. 80
5.3.1.2.1 General p. 80
5.3.1.2.2 Registration for MCPTT service p. 81
5.3.1.2.3 Establishment of MCPTT session p. 82
5.3.1.3 Impact on existing entities and interfaces p. 84
5.3.1.4 Solution evaluation p. 85
5.3.2 Solution 3-2: Relay for UE-to-network relay MCPTT p. 85
5.4 Group management p. 89
5.4.1 Off-network p. 89
5.4.2 On-network p. 92
5.4.2.1 Solution 4-2-1: Group management - search p. 92
5.4.2.1.1 Functional description p. 92
5.4.2.1.2 Procedures p. 93
5.4.2.1.3 Impact on existing entities and interfaces p. 94
5.4.2.1.4 Solution evaluation p. 94
5.4.2.2 Dynamic group management p. 94
5.4.2.2.1 Solution 4-2-2-1: Group regroup for groups within the same MCPTT system p. 94
5.4.2.2.1.1 Functional description p. 94
5.4.2.2.1.2 Procedures p. 95
5.4.2.2.1.3 Impact on existing entities and interfaces p. 95
5.4.2.2.1.4 Solution evaluation p. 95
5.4.2.2.2 Solution 4-2-2-2: Group regroup for groups from the different MCPTT systems p. 96
