Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.989  Word version:  19.2.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.3…   6.4…   6.5…   6.8…   6.13…   6.16…   7…   8…   10…

 

8  Business communication applications related use casesp. 146

9  Critical support applications related use casesp. 149

9.1  Overviewp. 149

9.2  Assured voice communication (AVC)p. 149

9.3  Functional identities and role managementp. 154

9.3.1  Introductionp. 154

9.3.2  General pre-conditionsp. 155

9.3.3  Use case: Registration to a functional identityp. 158

9.3.4  Use case: Deregistration of a functional identityp. 161

9.3.5  Use case: User log-in to the FRMCS Systemp. 162

9.3.6  Use case: User log-out from FRMCS Systemp. 163

9.3.7  Use case: Presentation of identitiesp. 164

9.3.8  Use case: Interrogation of identities within a certain contextp. 166

9.4  Location services related use casesp. 172

9.5  FRMCS User communication handling related use casesp. 175

9.5.1  Introductionp. 175

9.5.2  Use Case: Inviting-FRMCS User(s) to a voice communicationp. 176

9.5.3  Use Case: FRMCS User receiving an invitation to a voice communicationp. 177

9.5.4  Use case: FRMCS User accepting an invitation to a voice communicationp. 178

9.5.5  Use case: FRMCS User rejecting an invitation to a voice communicationp. 179

9.5.6  Use case: FRMCS User ignoring an invitation to a voice communicationp. 180

9.5.7  Service interworking with GSM-Rp. 180

9.6Void

9.7  Multiuser talker control related use casesp. 183

9.7.1  General Description and potential requirementsp. 183

9.7.2  Use case: Set the number of simultaneous talkersp. 184

9.7.3  Use case: Set initial talker permissions and prioritiesp. 184

9.7.4  Use case: Request permission to talkp. 186

9.7.5  Use case: Grant permission to talkp. 187

9.7.6  Use case: Revoke permission to talkp. 190

9.7.7  Use case: Service interworking and service continuation with GSM-R |R19|p. 191

9.8  Authorisation of communicationp. 191

9.9  Authorisation of applicationp. 193

9.10  Sharing FRMCS Equipment by FRMCS Usersp. 202

9.11  FRMCS naming authorityp. 203

9.12  Wayside-Centric Automatic Train Controlp. 204

9.13  Autonomous Train Control and Operationp. 206

9.14  Virtual Couplingp. 208

9.15  Composite-based train operationp. 211

9.16  Arbitration related use casesp. 212

9.17  Data communication to exchange key information for train safety application use casesp. 217


Up   Top   ToC