Content for TR 22.989 Word version: 19.4.0
8 Business communication applications related use cases
8.1 Multimedia applications related use cases
8.2 Use Case: Live streaming of multimedia
8.3 Use Case: Bulk transfer of multimedia from ground to train
8.4 Use case: Transportation convenience service for the passengers for the reduced mobility
8.5 Use case: Multiple concurrent mobility services
9 Critical support applications related use cases
9.1 Overview
9.2 Assured voice communication (AVC)
9.3 Functional identities and role management
9.4 Location services related use cases
9.5 FRMCS User communication handling related use cases
9.7 Multiuser talker control related use cases
9.8 Authorisation of communication
9.9 Authorisation of application
9.10 Sharing FRMCS Equipment by FRMCS Users
9.11 FRMCS naming authority
9.12 Wayside-Centric Automatic Train Control
9.13 Autonomous Train Control and Operation
9.14 Virtual Coupling
9.15 Composite-based train operation
9.16 Arbitration related use cases
9.17 Data communication to exchange key information for train safety application use cases
8 Business communication applications related use cases p. 147
8.1 Multimedia applications related use cases p. 147
8.1.1 Introduction p. 147
8.2 Use Case: Live streaming of multimedia p. 148
8.2.1 Description p. 148
8.2.2 Pre-conditions p. 148
8.2.3 Service flows p. 148
8.2.4 Post-conditions p. 148
8.2.5 Potential requirements and gap analysis p. 148
8.3 Use Case: Bulk transfer of multimedia from ground to train p. 148
8.3.1 Description p. 148
8.3.2 Pre-conditions p. 149
8.3.3 Service flows p. 149
8.3.4 Post-conditions p. 149
8.3.5 Potential requirements and gap analysis p. 149
8.4 Use case: Transportation convenience service for the passengers for the reduced mobility p. 150
8.4.1 Description p. 150
8.4.2 Pre-conditions p. 150
8.4.3 Service flows p. 150
8.4.4 Post-conditions p. 150
8.4.5 Potential requirements and gap analysis p. 151
8.5 Use case: Multiple concurrent mobility services p. 151
8.5.1 Description p. 151
8.5.2 Pre-conditions p. 151
8.5.3 Service flows p. 152
8.5.4 Post-conditions p. 152
8.5.5 Potential requirements and gap analysis p. 152
9 Critical support applications related use cases p. 152
9.1 Overview p. 152
9.2 Assured voice communication (AVC) p. 152
9.2.1 Introduction p. 152
9.2.2 Use case: Invocation of Assured Voice Communication p. 153
9.2.2.1 Description p. 153
9.2.2.2 Pre-conditions p. 153
9.2.2.3 Service flows p. 153
9.2.2.4 Post-conditions p. 153
9.2.2.5 Potential requirements and gap analysis p. 153
9.2.3 Use case: Stopping Assured Voice Communication p. 153
9.2.3.1 Description p. 153
9.2.3.2 Pre-conditions p. 153
9.2.3.3 Service flows p. 154
9.2.3.4 Post-conditions p. 154
9.2.3.5 Potential requirements and gap analysis p. 154
9.2.4 Use case: Degradation of a communication link p. 154
9.2.4.1 Description p. 154
9.2.4.2 Pre-conditions p. 154
9.2.4.3 Service flows p. 155
9.2.4.4 Post-conditions p. 155
9.2.4.5 Potential requirements and gap analysis p. 156
9.2.5 Use case: Extension of Assured Voice Communication p. 157
9.2.5.1 Description p. 157
9.2.5.2 Pre-conditions p. 157
9.2.5.3 Service flows p. 157
9.2.5.4 Post-conditions p. 157
9.2.5.5 Potential requirements and gap analysis p. 157
9.3 Functional identities and role management p. 157
9.3.1 Introduction p. 157
9.3.2 General pre-conditions p. 158
9.3.3 Use case: Registration to a functional identity p. 161
9.3.3.1 Description p. 161
9.3.3.2 Pre-conditions p. 161
9.3.3.3 Service flows p. 161
9.3.3.4 Post-conditions p. 162
9.3.3.5 Potential requirements and gap analysis p. 163
9.3.4 Use case: Deregistration of a functional identity p. 164
9.3.4.1 Description p. 164
9.3.4.2 Pre-conditions p. 164
9.3.4.3 Service flows p. 164
9.3.4.4 Post-conditions p. 164
9.3.4.5 Potential requirements and gap analysis p. 165
9.3.5 Use case: User log-in to the FRMCS System p. 165
9.3.5.1 Description p. 165
9.3.5.2 Pre-conditions p. 165
9.3.5.3 Service flows p. 166
9.3.5.4 Post-conditions p. 166
9.3.5.5 Potential requirements and gap analysis p. 166
9.3.6 Use case: User log-out from FRMCS System p. 166
9.3.6.1 Description p. 166
9.3.6.2 Pre-conditions p. 166
9.3.6.3 Service flows p. 166
9.3.6.4 Post-conditions p. 167
9.3.6.5 Potential requirements and gap analysis p. 167
9.3.7 Use case: Presentation of identities p. 167
9.3.7.1 Description p. 167
9.3.7.2 Pre-conditions p. 168
9.3.7.3 Service flows p. 168
9.3.7.4 Post-conditions p. 168
9.3.7.5 Potential requirements and gap analysis p. 169
9.3.8 Use case: Interrogation of identities within a certain context p. 169
9.3.8.1 Description p. 169
9.3.8.2 Pre-conditions p. 169
9.3.8.3 Service flows p. 169
9.3.8.4 Post-conditions p. 170
9.3.8.5 Potential requirements and gap analysis p. 171
9.3.9.5 Potential requirements and gap analysis p. 174
9.4 Location services related use cases p. 175
9.4.1 Introduction p. 175
9.4.2 Use Case: Provide location information p. 175
9.4.2.1 Description p. 175
9.4.2.2 Pre-conditions p. 175
9.4.2.3 Service flows p. 175
9.4.2.4 Post-conditions p. 176
9.4.2.5 Potential requirements and gap analysis p. 176
9.4.3 Use Case: Request for location information p. 176
9.4.3.1 Description p. 176
9.4.3.2 Pre-conditions p. 176
9.4.3.3 Service flows p. 177
9.4.3.4 Post-conditions p. 177
9.4.3.5 Potential requirements and gap analysis p. 177
9.4.4 Use Case: Request for identities in a certain area p. 177
9.4.4.1 Description p. 177
9.4.4.2 Pre-conditions p. 178
9.4.4.3 Service flows p. 178
9.4.4.4 Post-conditions p. 178
9.4.4.5 Potential requirements and gap analysis p. 178
9.5 FRMCS User communication handling related use cases p. 178
9.5.1 Introduction p. 178
9.5.2 Use Case: Inviting-FRMCS User(s) to a voice communication p. 179
9.5.2.1 Description p. 179
9.5.2.2 Pre-conditions p. 179
9.5.2.3 Service flows p. 179
9.5.2.4 Post-conditions p. 179
9.5.2.5 Potential requirements and gap analysis p. 180
9.5.3 Use Case: FRMCS User receiving an invitation to a voice communication p. 180
9.5.3.1 Description p. 180
9.5.3.2 Pre-conditions p. 180
9.5.3.3 Service flows p. 180
9.5.3.4 Post-conditions p. 180
9.5.3.5 Potential requirements and gap analysis p. 181
9.5.4 Use case: FRMCS User accepting an invitation to a voice communication p. 181
9.5.4.1 Description p. 181
9.5.4.2 Pre-conditions p. 181
9.5.4.3 Service flows p. 181
9.5.4.4 Post-conditions p. 181
9.5.4.5 Potential requirements and gap analysis p. 182
9.5.5 Use case: FRMCS User rejecting an invitation to a voice communication p. 182
9.5.5.1 Description p. 182
9.5.5.2 Pre-conditions p. 182
9.5.5.3 Service flows p. 182
9.5.5.4 Post-conditions p. 182
9.5.5.5 Potential requirements and gap analysis p. 183
9.5.6 Use case: FRMCS User ignoring an invitation to a voice communication p. 183
9.5.6.1 Description p. 183
9.5.6.2 Pre-conditions p. 183
9.5.6.3 Service flows p. 183
9.5.6.4 Post-conditions p. 183
9.5.6.5 Potential requirements and gap analysis p. 183
9.5.7 Service interworking with GSM-R p. 183
9.5.7.1 Description p. 183
9.5.7.2 Pre-condition p. 185
9.5.7.3 Service flow p. 185
9.5.7.4 Post-condition p. 185
9.5.7.5 Potential requirements p. 186
9.6 Void
9.7 Multiuser talker control related use cases p. 186
9.7.1 General Description and potential requirements p. 186
9.7.2 Use case: Set the number of simultaneous talkers p. 187
9.7.2.1 Description p. 187
9.7.2.2 Pre-conditions p. 187
9.7.2.3 Service flows p. 187
9.7.2.4 Post-conditions p. 187
9.7.2.5 Potential requirements and gap analysis p. 187
9.7.3 Use case: Set initial talker permissions and priorities p. 187
9.7.3.1 Description p. 187
9.7.3.2 Pre-conditions p. 188
9.7.3.3 Service flows p. 188
9.7.3.4 Post-conditions p. 188
9.7.3.5 Potential requirements and gap analysis p. 189
9.7.4 Use case: Request permission to talk p. 189
9.7.4.1 Description p. 189
9.7.4.2 Pre-conditions p. 190
9.7.4.3 Service flows p. 190
9.7.4.4 Post-conditions p. 190
9.7.4.5 Potential requirements and gap analysis p. 190
9.7.5 Use case: Grant permission to talk p. 190
9.7.5.1 Description p. 190
9.7.5.2 Pre-conditions p. 190
9.7.5.3 Service flows p. 191
9.7.5.4 Post-conditions p. 191
9.7.5.5 Potential requirements and gap analysis p. 192
9.7.6 Use case: Revoke permission to talk p. 193
9.7.6.1 Description p. 193
9.7.6.2 Pre-conditions p. 193
9.7.6.3 Service flows p. 193
9.7.6.4 Post-conditions p. 193
9.7.6.5 Potential requirements and gap analysis p. 194
9.7.7 Use case: Service interworking and service continuation with GSM-R p. 194
9.7.7.1 Description p. 194
9.8 Authorisation of communication p. 194
9.8.1 Introduction p. 194
9.8.2 Use case: Permit / deny communication p. 194
9.8.2.1 Description p. 194
9.8.2.2 Pre-conditions p. 194
9.8.2.3 Service flows p. 195
9.8.2.4 Post-conditions p. 195
9.8.2.5 Potential requirements and gap analysis p. 196
9.9 Authorisation of application p. 196
9.9.1 Introduction p. 196
9.9.2 Use case: Enabling/Disabling applications p. 196
9.9.2.1 Description p. 196
9.9.2.2 Pre-conditions p. 196
9.9.2.3 Service flows p. 196
9.9.2.4 Post-conditions p. 197
9.9.2.5 Potential requirements and gap analysis p. 198
9.9.3 Use case: Robust mission critical group communication services p. 199
9.9.3.1 Description p. 199
9.9.3.2 Pre-conditions p. 199
9.9.3.3 Service Flows p. 200
9.9.1.4 Post-conditions p. 200
9.9.3.5 Potential requirements and gap analysis p. 201
9.9.3a Use case: Enabling/Disabling communication privileges per FRMCS User based on identities/talker status p. 201
9.9.3a.1 Description p. 201
9.9.3a.2 Pre-conditions p. 201
9.9.3a.3 Service flows p. 201
9.9.3a.4 Post-conditions p. 202
9.9.3a.5 Potential requirements and gap analysis p. 203
9.10 Sharing FRMCS Equipment by FRMCS Users p. 205
9.10.1 Description p. 205
9.10.2 Pre-conditions p. 205
9.10.3 Service Flows p. 205
9.10.4 Post-conditions p. 205
9.10.5 Potential requirements and gap analysis p. 206
9.11 FRMCS naming authority p. 206
9.11.1 Description p. 206
9.11.2 Pre-conditions p. 206
9.11.3 Service Flows p. 206
9.11.4 Post-conditions p. 207
9.11.5 Potential requirements and gap analysis p. 207
9.12 Wayside-Centric Automatic Train Control p. 207
9.12.1 Description p. 207
9.12.2 Pre-conditions p. 208
9.12.3 Service flows p. 208
9.12.4 Post-conditions p. 209
9.12.5 Potential requirements and gap analysis p. 209
9.13 Autonomous Train Control and Operation p. 209
9.13.1 Description p. 209
9.13.2 Pre-conditions p. 209
9.13.3 Service Flows p. 210
9.13.4 Post-conditions p. 210
9.13.5 Potential requirements and gap analysis p. 211
9.14 Virtual Coupling p. 211
9.14.1 Description p. 211
9.14.2 Pre-conditions p. 212
9.14.3 Service Flows p. 213
9.14.4 Post-conditions p. 213
9.14.5 Potential requirements and gap analysis p. 214
9.15 Composite-based train operation p. 214
9.15.1 Description p. 214
9.15.2 Pre-conditions p. 214
9.15.3 Service Flows p. 214
9.15.4 Post-conditions p. 215
9.15.5 Potential requirements and gap analysis p. 215
9.16 Arbitration related use cases p. 215
9.16.1 Introduction p. 215
9.16.2 Use case: Arbitration p. 216
9.16.2.1 Description p. 216
9.16.2.2 Pre-conditions p. 216
9.16.2.3 Service flows p. 216
9.16.2.4 Post-conditions p. 216
9.16.2.5 Potential requirements and gap analysis p. 216
9.16.3 Use case: Arbitration for communication auto-connection p. 217
9.16.3.1 Description p. 217
9.16.3.2 Pre-conditions p. 217
9.16.3.3 Service flows p. 217
9.16.3.4 Post-conditions p. 218
9.16.3.5 Potential requirements and gap analysis p. 219
9.17 Data communication to exchange key information for train safety application use cases p. 220
9.17.1 Introduction p. 220
9.17.2 Use case: Initiation of a Key Management data communication p. 220
9.17.2.1 Description p. 220
9.17.2.2 Pre-conditions p. 220
9.17.2.3 Service flows p. 220
9.17.2.4 Post-conditions p. 220
9.17.2.5 Potential requirements and gap analysis p. 222
9.17.3 Use case: Termination of a Key Management data communication p. 223
9.17.3.1 Description p. 223
9.17.3.2 Pre-conditions p. 223
9.17.3.3 Service flows p. 223
9.17.3.4 Post-conditions p. 223
9.17.3.5 Potential requirements and gap analysis p. 224
9.17.4 Use case: service interworking and service continuation with GSM-R p. 224
9.17.4.1 Description p. 224
9.17.4.2 Pre-conditions p. 224
9.17.4.3 Service flows p. 224
9.17.4.4 Post-conditions p. 225
