Content for TR 23.796 Word version: 16.0.0
7 Solutions p. 29
7.1 Solution 1 - Restricting incoming private communications p. 29
7.1.1 Solution description p. 29
7.1.1.1 General p. 29
7.1.1.2 Mission Critical Push-to-Talk p. 29
7.1.1.3 Mission Critical Video p. 30
7.1.1.3.1 Private video call setup procedures p. 30
7.1.1.3.2 Configuration data for private video calls p. 30
7.1.1.4 Mission Critical Data p. 31
7.1.2 Solution evaluation p. 32
7.2 Solution 2 - Implicit activation and deactivation of functional alias(es) p. 32
7.2.1 Solution description p. 32
7.2.1.1 General p. 32
7.2.1.2 Implicit activation of functional alias(es) within an MC system p. 33
7.2.1.3 Implicit deactivation of functional alias(es) within an MC system p. 33
7.2.1.4 Configuration management data p. 34
7.2.2 Solution evaluation p. 35
7.3 Solution 3 - Client performs automatic group affiliation/de-affiliation p. 35
7.3.1 Solution description p. 35
7.3.2 Solution evaluation p. 37
7.4 Solution 4 - Support of functional aliases in private calls and private emergency calls p. 37
7.4.1 Solution description p. 37
7.4.1.1 General p. 37
7.4.1.2 Private calls using functional aliases p. 37
7.4.1.3 MCPTT private emergency calls using functional aliases p. 39
7.4.2 Solution evaluation p. 41
7.5 Solution 5 - Support of functional aliases in emergency and imminent peril groups calls p. 41
7.5.1 Solution description p. 41
7.5.1.1 General p. 41
7.5.1.2 Emergency group calls using functional aliases p. 41
7.5.1.3 MCPTT imminent peril group call using functional aliases p. 43
7.5.1.4 MCPTT emergency alert p. 44
7.5.2 Solution evaluation p. 44
7.6 Solution 6 - Support of functional aliases in temporary voice group calls p. 44
7.6.1 Solution description p. 44
7.6.2 Solution evaluation p. 45
7.7 Solution 7 - Architecture to support GSM-R interworking p. 45
7.7.1 Solution description p. 45
7.7.1.1 General p. 45
7.7.1.2 Functional model for application plane interworking p. 46
7.7.1.3 Functional entities description p. 47
7.7.1.3.1 IWFR p. 47
7.7.1.4 Reference points p. 48
7.7.2 Solution evaluation p. 48
7.8 Solution 8 - Solution to support functional alias via broadcast group calls p. 49
7.8.1 Solution description p. 49
7.8.2 Solution evaluation p. 52
7.9 Solution 9 - Solution to support multiple functional alias use in private calls p. 52
7.9.1 Solution description p. 52
7.9.1.1 General p. 52
7.9.1.2 Private call setup procedure p. 52
7.9.2 Solution evaluation p. 54
7.10 Solution 10 - Location information for a specific functional alias p. 54
7.10.1 Solution description p. 54
7.10.1.1 General p. 54
7.10.1.2 Client-triggered one-time location information request p. 54
7.10.1.3 Client triggered periodic location information reporting p. 56
7.11.1.3 Group configuration data p. 58
7.11.2 Solution evaluation p. 59
7.12 Solution 12 - List of functional aliases used by affiliated group members p. 59
7.12.1 Solution description p. 59
7.12.1.1 General p. 59
7.12.1.2 Procedure for subscription and notification of activated functional aliases used associated with a group p. 59
7.12.2 Solution evaluation p. 60
7.13 Solution 13 - List of MCPTT group members who did not acknowledge the group call request p. 60
7.14 Solution 14 - MC service server limits the number of simultaneous successful service authorisations p. 62
7.14.1 Solution description p. 62
7.14.1.1 General p. 62
7.14.1.2 Using the client ID provided during user service authorisation p. 62
7.14.1.3 Service configuration data p. 63
7.14.2 Solution evaluation p. 63
7.15 Solution 15 - Support functional aliases for SDS p. 63
7.15.1 Solution description p. 63
7.15.1.1 General p. 63
7.15.1.2 One-to-one short data service (SDS) p. 63
7.15.1.4 Configuration data p. 66
7.15.2 Solution evaluation p. 67
7.16 Solution 16 - Support functional aliases for File distribution (FD) p. 67
7.16.1 Solution description p. 67
7.16.1.1 General p. 67
7.16.1.2 One-to-one file distribution using HTTP p. 67
7.16.1.3 Group standalone file distribution using HTTP p. 69
7.16.2 Solution evaluation p. 70
7.17 Solution 17 - Support functional aliases within MCData control procedures p. 70
7.17.1 Solution description p. 70
7.17.1.1 General p. 70
7.17.1.2 Transmission and reception control procedures p. 71
7.17.1.3 Control and conversation release procedures p. 72
7.17.2 Solution evaluation p. 73
7.18 Solution 18 - Support of functional aliases for video emergency group calls p. 73
7.18.1 Solution description p. 73
7.18.1.1 General p. 73
7.18.1.2 Emergency video group calls p. 73
7.18.1.3 Group emergency video alerts p. 75
7.18.2 Solution evaluation p. 77
7.19 Solution 19 - Support of functional aliases in private calls and private emergency calls p. 77
7.19.1 Solution description p. 77
7.19.1.1 General p. 77
7.19.1.2 Private calls using functional aliases p. 77
7.19.1.3 MCPTT private emergency calls using functional aliases p. 78
7.19.2 Solution evaluation p. 80
7.20 Solution 20 - Support of functional aliases for video group calls p. 80
7.20.1 Solution description p. 80
7.20.1.1 General p. 80
7.20.1.2 Pre-arranged video group calls p. 81
7.20.1.3 Chat video group calls p. 82
7.20.1.4 Configuration data p. 83
7.20.2 Solution evaluation p. 84
7.21 Solution 21 - Support of functional aliases for private and emergency video calls p. 84
7.22 Solution 22 - Support functional alias controlling for MCData services p. 87
7.23 Solution 23 - Support functional alias controlling for MCVideo service p. 88
7.24 Solution 24 - Additional commencement modes for MCPTT Group calls p. 88
7.24.1 Solution description p. 88
7.24.1.1 General p. 88
7.24.1.2 Procedure p. 89
7.24.2 Solution evaluation p. 90
7.25 Solution 25 - Triggering an emergency group communication after an emergency alert automatically p. 90
7.25.1 Solution description p. 90
7.25.1.1 General p. 90
7.25.1.2 Procedure p. 90
7.25.2 Solution evaluation p. 91
7.26 Solution 26 - User requests application layer priorities p. 91
7.26.1 Solution description p. 91
7.26.1.1 General p. 91
7.26.1.2 Mission Critical Push-to-Talk p. 91
7.26.1.3 Mission Critical Video p. 92
7.26.1.4 Mission Critical Data p. 92
7.26.1.5 GSM-R interworking p. 92
7.26.2 Solution evaluation p. 93
7.27 Solution 27 - MC gateway UE p. 93
7.27.1 Solution description p. 93
7.27.1.1 General p. 93
7.27.1.2 MC gateway UE definition p. 93
7.27.1.3 Baseline MC gateway UE architecture p. 93
7.27.1.4 Layer 7 versus layer 3 MC gateway consideration p. 94
7.27.1.4.1 Introduction p. 94
7.27.1.4.2 User identification p. 94
7.27.1.4.3 Communication priority and QoS treatment p. 94
7.27.1.4.4 Resource sharing of the MC gateway UE p. 94
7.27.1.4.5 Summary layer 3 versus layer 7 MC gateway UE p. 94
7.27.1.5 User identities p. 95
7.27.1.5.1 User identities in the control plane p. 95
7.27.1.5.2 Conclusion on user identities p. 95
7.27.1.6 User identification behind the MC gateway UE p. 95
7.28 Solution 28 - IP connectivity p. 97
7.28.1 Solution description p. 97
7.28.1.1 General p. 97
7.28.1.2 Baseline IP connectivity p. 97
7.28.1.3 IP connectivity communication modes p. 97
7.28.1.4 Distinction between IP connectivity and other MCData services p. 98
7.28.1.5 IP connectivity point-to-point MCData bearer service p. 99
7.28.1.5.1 General p. 99
7.28.1.5.2 Procedure p. 99
7.28.1.5.3 MCData IPcon point-to-point request p. 100
7.28.1.5.4 IP connectivity group service p. 100
7.28.1.5.4.1 General p. 100
7.28.1.5.4.2 Procedure p. 101
7.28.1.5.4.3 MCData IPcon group request p. 102
7.28.1.5.5 IP connectivity response p. 102
7.28.1.6 Functional model update p. 103
7.28.2 Solution evaluation p. 104
7.29 Solution 29 - Call forwarding and call transfer for private calls p. 104
7.29.1 Solution description p. 104
7.29.1.1 General p. 104
7.29.1.2 Call forwarding unconditional p. 105
7.29.1.3 Call forwarding no reply p. 106
7.29.1.4 Call forwarding not reachable p. 108
7.29.1.5 Call deflection p. 110
7.29.1.6 Call transfer unattended p. 112
7.29.1.8 Call transfer with temporary three-way call p. 115
7.29.1.9 Update configuration of call forwarding p. 117
7.29.2 Solution evaluation p. 118
7.30 Solution 30 - Arbitration of incoming communications p. 118
7.31 Solution 31 - Client performs automatic activation and deactivation of functional aliases based on location p. 118
7.31.1 Solution description p. 118
7.31.1.1 General p. 118
7.31.1.2 Solution principles p. 118
7.31.1.3 Configuration management data p. 119
7.31.2 Solution evaluation p. 120
7.32 Solution 32 - Functional alias and alternative addressing scheme for interworking with LMR systems p. 120
7.32.1 Solution description p. 120
7.32.1.1 General p. 120
7.32.1a Solution description for key issues #16-2 and #16-3 p. 120
7.32.1a.1 Identity mapping for alternative user addressing schemes p. 120
7.32.1a.2 Affected messages p. 120
7.32.1b Solution description for key issues #16-1 p. 122
7.32.1b.1 IWF functional alias management p. 122
7.32.1b.1.1 General p. 122
7.32.1b.1.2 IWF information flows for functional alias management p. 122
7.32.1b.1.2.1 IWF functional alias information query request p. 122
7.32.1b.1.2.2 IWF functional alias information query response p. 122
7.32.1b.1.2.3 IWF functional alias activation request p. 122
7.32.1b.1.2.4 IWF functional alias activation response p. 123
7.32.1b.1.2.5 IWF functional alias de-activation request p. 123
7.32.1b.1.2.6 IWF functional alias de-activation response p. 123
7.32.1b.1.2.7 IWF functional alias status notification p. 124
7.32.1b.1.2.8 IWF Functional alias take over request p. 124
7.32.1b.1.2.9 IWF Functional alias take over response p. 124
7.32.1b.1.2.10 IWF Functional alias revoke notification p. 124
7.32.1b.1.3 IWF (authorised MC service user) retrieves active functional alias(es) for a certain MC service user p. 125
7.32.1b.1.4 IWF (MC service user) activates functional alias(es) within an MC system p. 125
7.32.1b.1.5 IWF (MC service user) de-activates functional alias(es) within an MC system p. 126
7.32.1b.1.6 IWF (Authorised MC service user) takes over functional alias(es) within an MC system p. 127
7.32.2 Solution evaluation p. 128
7.33 Solution 33 - Communication priority for functional aliases p. 128
7.33.1 Solution description p. 128
7.33.1.1 General p. 128
7.33.1.3 Configuration management data p. 129
7.33.2 Solution evaluation p. 129
