Content for TR 22.990 Word version: 18.0.0
5 Communication Applications related use cases
5.1 Introduction
5.2 Trackside Maintenance Warning System communication
5.3 Remote Control of Engines communications
5.4 Train integrity monitoring data communication
5.5 Shunting communication
5.6 Train ready for departure communication
5.7 Autonomous Train Control and Operation
5.8 Virtual Coupling
5.9 Monitoring and control of critical infrastructure communication
8 Identified issues
8.1 Introduction
8.2 Identified issue 1: Communication range
8.3 Identified issue 2: MCX Support
9 Consolidated potential requirements
10 Conclusion and recommendations
$ Change history
5 Communication Applications related use cases Word‑p. 7
5.1 Introduction Word‑p. 7
5.2 Trackside Maintenance Warning System communication Word‑p. 7
5.2.1 Description Word‑p. 7
5.2.2 Pre-conditions Word‑p. 9
5.2.3 Service Flows Word‑p. 9
5.2.4 Post-conditions Word‑p. 10
5.2.5 Existing features partly or fully covering the use case functionality Word‑p. 10
5.2.6 Potential New Requirements needed to support the use case and gap analysis Word‑p. 10
5.3 Remote Control of Engines communications Word‑p. 11
5.3.1 Description Word‑p. 11
5.3.2 Pre-conditions Word‑p. 13
5.3.3 Service Flows Word‑p. 13
5.3.4 Post-conditions Word‑p. 14
5.3.5 Existing features partly or fully covering the use case functionality Word‑p. 14
5.3.6 Potential New Requirements needed to support the use case Word‑p. 14
5.4 Train integrity monitoring data communication Word‑p. 15
5.4.1 Description Word‑p. 15
5.4.2 Pre-conditions Word‑p. 16
5.4.3 Service Flows Word‑p. 16
5.4.4 Post-conditions Word‑p. 17
5.4.5 Existing features partly or fully covering the use case functionality Word‑p. 17
5.4.6 Potential New Requirements needed to support the use case Word‑p. 17
5.5 Shunting communication Word‑p. 18
5.5.1 Description Word‑p. 18
5.5.2 Pre-conditions Word‑p. 18
5.5.3 Service Flows Word‑p. 18
5.5.4 Post-conditions Word‑p. 20
5.5.5 Existing features partly or fully covering the use case functionality Word‑p. 20
5.5.6 Potential New Requirements needed to support the use case Word‑p. 20
5.6 Train ready for departure communication Word‑p. 22
5.6.1 Description Word‑p. 22
5.6.2 Pre-conditions Word‑p. 23
5.6.3 Service Flows Word‑p. 23
5.6.4 Post-conditions Word‑p. 24
5.6.5 Existing features partly or fully covering the use case functionality Word‑p. 24
5.6.6 Potential New Requirements needed to support the use case Word‑p. 24
5.7 Autonomous Train Control and Operation Word‑p. 25
5.7.1 Description Word‑p. 25
5.7.2 Pre-conditions Word‑p. 26
5.7.3 Service Flows Word‑p. 26
5.7.4 Post-conditions Word‑p. 26
5.7.5 Existing features partly or fully covering the use case functionality Word‑p. 26
5.7.6 Potential New Requirements needed to support the use case Word‑p. 26
5.8 Virtual Coupling Word‑p. 27
5.8.1 Description Word‑p. 27
5.8.2 Pre-conditions Word‑p. 28
5.8.3 Service Flows Word‑p. 29
5.8.4 Post-conditions Word‑p. 29
5.8.5 Existing features partly or fully covering the use case functionality Word‑p. 29
5.8.6 Potential New Requirements needed to support the use case Word‑p. 29
5.9 Monitoring and control of critical infrastructure communication Word‑p. 30
5.9.1 Description Word‑p. 30
5.9.2 Pre-conditions Word‑p. 31
5.9.3 Service Flows Word‑p. 31
5.9.4 Post-conditions Word‑p. 31
5.9.5 Existing features partly or fully covering the use case functionality Word‑p. 31
5.9.6 Potential New Requirements needed to support the use case Word‑p. 32
6 Void
7 Void
8 Identified issues Word‑p. 33
8.1 Introduction Word‑p. 33
8.2 Identified issue 1: Communication range Word‑p. 33
8.2.1 Description Word‑p. 33
8.2.2 Limitations, missing requirements and gaps Word‑p. 33
8.3 Identified issue 2: MCX Support Word‑p. 33
8.3.1 Description Word‑p. 33
8.3.2 Limitations, missing requirements and gaps Word‑p. 34
9 Consolidated potential requirements Word‑p. 35
10 Conclusion and recommendations Word‑p. 35
$ Change history Word‑p. 36
