Understand · 1.8
Quality, availability and security
Time: about 9–12 minutes including the task; estimate
Guiding question: How do performance, availability and protection of a communication service differ?
Learning objective: You distinguish data rate, delay, availability, security and safety.
Prerequisites: Previous lessons through 1.7, particularly the case file developed there.
Transmitting data does not mean arriving on time
Talbahn wants to transmit conversations and measurements. From 1.3 you know a radio cell as a base station's coverage area. Besides coverage, the connection needs properties that suit the information.
A data packet is a bounded transmission unit containing payload and transport information. In simplified terms, it resembles an addressed shipment. A file or speech stream can be carried in many such units.
IP, the Internet Protocol, specifies rules for transmitting addressed packets. A protocol is a shared agreement on how technical participants exchange information. IP uses source and destination addresses and can also operate in a closed railway network. It is not a synonym for the public internet. IP alone guarantees neither the arrival of every packet nor a fixed transit time. [S19]
Keep three properties separate
The data rate describes an amount of data per unit of time. A high usable rate helps, for example, to transfer large measurement files on time. Comparisons must make clear whether theoretical capacity or the rate actually achieved is meant.
Latency is the delay between specified points. It can be measured between sending a message in the train application and receiving it in the workshop application. A small message can wait a long time even though the network carries a large amount of data per second overall. [S20]
Here, availability describes whether the required communication capability is usable under the specified conditions. For Lea, the service on Talstadt–Bergheim matters, not just a reachable server. A high data rate elsewhere does not compensate for a missing connection inside the tunnel.
In everyday language, data rate is often called “bandwidth”. In radio engineering, however, bandwidth means the width of a frequency range. It then describes how much frequency space a signal or transmission channel occupies and is a different quantity. We therefore use “data rate” for the amount of data per unit of time.
Two connections, two tasks
In this teaching example, connection A carries many measurement files per hour, but individual messages arrive late. Connection B carries less data but delivers the small message under consideration on time.
A may suit later file analysis, B the time-critical message in this example. The application determines which property is needed; one marketing figure does not describe overall suitability.
Comparing GSM-R and FRMCS
In circuit-switched communication, transmission capacity is assigned to a connection for its duration. The established transmission arrangement persists for that connection. In packet-switched communication, information travels as packets; data streams can share transmission resources. Packets from different exchanges are forwarded according to the intended rules. GSM-R also supports packet-switched data transmission. FRMCS is based on packet communication. “GSM-R cannot carry packets” would be wrong. [S02, S07]
Quality also needs protection and a usable service
Availability means the required function is usable under defined conditions. It depends on more than radio: incorrect role permission may prevent a conversation while packets are still transferred. Security protects against unauthorised access and manipulation. Safety concerns avoiding unacceptable risks to people and operations. The concepts are related but require different assessments.
Talbahn therefore asks four questions: does information arrive on time? Is the service usable when needed? Are access and changes adequately protected? What operational consequences follow a fault? Answering one well does not replace the others. Level 2 introduces technical procedures; here the essential outcome is a justified distinction. [S15; S25]
Check your understanding
A small message arrives late. The supplier points to the data rate. Which measurement is missing, which endpoints would you choose, and why does availability also matter?
Model answer
Latency between relevant points is missing, for example sending in the train application and receiving in the workshop application. The data rate does not answer this transit-time question. The exchange must also be usable on the intended route. The measurement boundary must be stated explicitly: reception does not automatically mean completed application processing.
Additional application
Why is a manipulated role permission not simply a data-rate problem?
Model answer
The change concerns security and can affect service availability and operations. More data rate does not restore correct permission.
What to remember
- IP can also be used in closed networks.
- Data rate, latency and availability answer different questions.
- The application's purpose determines the required performance.
Your Talbahn case file
For both pairs of communication partners, add questions about the three properties and name the endpoints.
Sources
S02 · UIC EIRENE SRS
Version: 16.1.0 · Checked: 2026-10-11
Scope: Section 1.4 architecture; requirements for GSM-R system functions and addressing.
Limitations: No blanket statement about every installed GSM-R implementation.
Used in: 1.3, 1.5, 1.6, 1.8
S07 · ETSI TS 103 764: FRMCS System Architecture
ETSI TS 103 764: FRMCS System Architecture
Version: 1.1.1, January 2026 · Checked: 2026-10-11
Scope: Architecture sections: FRMCS boundary, service and transport, applications using the system.
Limitations: Course diagrams are original simplifications, not normative reference drawings.
Used in: 1.3, 1.5, 1.8, 1.9, 1.10, 2.1, 2.22
S15 · EN 50126-1: Generic RAMS process
EN 50126-1: Generic RAMS process
Version: 2017 + A1:2024, BSI edition · Checked: 2026-10-11
Scope: RAMS process framework over the life cycle.
Limitations: Catalogue and scope only; no complete review of the paid standard. Determine national adoption and project edition separately.
Used in: 1.8, 2.21, 3.8, 3.14
S19 · IETF RFC 8200: Internet Protocol, Version 6
IETF RFC 8200: Internet Protocol, Version 6
Version: July 2017 · Checked: 2026-10-11
Scope: Basic principles of IP packet transmission.
Limitations: IPv6 specification as a terminology foundation; does not define a complete FRMCS IP profile.
Used in: 1.8
S20 · IETF RFC 7679: A One-Way Delay Metric
IETF RFC 7679: A One-Way Delay Metric
Version: January 2016 · Checked: 2026-10-11
Scope: Measurement boundaries, timing and treatment of observed delay.
Limitations: 150 ms in this course is a fictional budget, not a limit derived from this RFC.
Used in: 1.8, 3.7
S25 · 3GPP TS 33.180 / ETSI TS 133 180: Security of the MC service
3GPP TS 33.180 / ETSI TS 133 180: Security of the MC service
Version: 16.13.0, February 2026 · Checked: 2026-10-11
Scope: Security architecture of Mission Critical services.
Limitations: Explicit teaching reference; cross-check newer release branches and the specific project baseline separately.
Used in: 1.8, 2.21, 3.8
Your progress is stored in this browser on this device.