Skip to content
Independent reference on the Future Railway Mobile Communication System

Apply · 2.18

Public mobile networks and roaming

Time: about 8–11 minutes including the task; estimate

Guiding question: Under which conditions can public mobile access support the selected case?

Learning objective: You distinguish public access, roaming, multipath and service access.

Prerequisites: Previous lessons through 2.17, particularly the case file developed there.

Public coverage is not yet a railway service

Talbahn's diagnostic application should be able to use public mobile access. A Mobile Network Operator (MNO) operates a mobile network. A public network can provide a transport path without taking over all FRMCS service functions. First establish which service the application needs to reach and through which approved access.

Roaming means a subscriber uses a visited network under the relevant subscriber and operator agreements. A separate public-mobile subscription can instead be used directly in its own home network. Public-network use is therefore not automatically roaming. Changing transport paths is also not automatically a service-domain change. [S08; S13]

Three decisions for the teaching case

Talbahn first determines whether public access is permitted for this application. Second, it checks a protected, reachable path to the service platform. Third, it establishes the treatment and performance actually provided under agreed conditions. The SRS includes permission to use a Non-FRMCS Transport Domain as a configuration aspect. This is not blanket permission to use arbitrary public networks for every application. [S06, clause 19.3]

Question Why it needs a separate check
May the subscriber use the network? Network permission is not service authorisation.
Is the service platform reachable? Internet access alone does not prove a suitable connection to the required endpoints.
What QoS is agreed? Local priority requests are not automatically honoured in every network.
What happens to an ongoing exchange? A new connection does not prove continuity of an existing session.
Who leads incident resolution? Access and service operators may be different organisations.

Use multiple paths deliberately

Multipath means using several transport paths through a function designed for that purpose. Depending on the method, data may be distributed, duplicated or moved to another path. Two modems alone do not implement this behaviour. Shared power, antenna sites and service platforms may also limit independence.

DB reports testing hybrid railway/public access and multipath methods in the Ore Mountains within 5G-RACOM. This is evidence from the described experimental configuration, not a blanket availability guarantee for Talbahn. [S47]

Check your understanding

A public network delivers a high data rate. A supplier claims this also secures the prioritised railway call during overload. What is missing?

Model answer

Missing evidence includes permitted access and service authorisation, the path to the service platform, agreed priority and QoS treatment, and a test under the claimed load. A high rate in one trial demonstrates neither admission under scarcity nor continuity or the appropriate service function.

What to remember

Public access, roaming, multipath and service-domain transition are distinct mechanisms. Their combination must be explained and tested for the particular service.

Your Talbahn case file

Design an approved public access and a failure trial for the diagnostic application. Do not automatically transfer its approval to voice or ETCS.

Sources

  • S06 · UIC FRMCS SRS AT-7800

    UIC FRMCS SRS AT-7800

    Version: 2.1.0, 30 April 2025 · Checked: 2026-10-11

    Scope: System requirements, architecture, service/transport interaction and mobility. Functional Alias: 11.6/21.3; voice profiles: 24.2.3.3 and 24.3.3.2–4; TSCTRL: 6.4.1.3.

    Limitations: The project baseline must specify the applicable parts.

    Used in: 1.3, 2.4, 2.7, 2.9, 2.11, 2.13, 2.15, 2.16, 2.17, 2.18, 2.19, 3.2, 3.3, 3.16

  • S08 · ETSI TS 103 765-1: FRMCS Transport Stratum

    ETSI TS 103 765-1: FRMCS Transport Stratum

    Version: 1.1.1, January 2026 · Checked: 2026-10-11

    Scope: Transport architecture, 5G, n100/n101 spectrum, mobility and multiple paths.

    Limitations: No general end-to-end performance guarantee; QoS terminology additionally uses S13.

    Used in: 1.9, 2.1, 2.3, 2.18, 3.6

  • S13 · 3GPP TS 23.501, published as ETSI TS 123 501

    3GPP TS 23.501, published as ETSI TS 123 501

    Version: 16.14.0, September 2022 · Checked: 2026-10-11

    Scope: Section 5.7: QoS Flow, 5QI, ARP, GBR and Non-GBR.

    Limitations: Explicit terminology reference, not presented as the latest edition or a complete FRMCS project baseline.

    Used in: 2.2, 2.3, 2.10, 2.18

  • S47 · DB: 5G-RACOM

    DB: 5G-RACOM

    Version: 2026 · Checked: 2026-10-11

    Scope: Report on hybrid networks and multipath trials.

    Limitations: Named teaching edition; no blanket product or project approval.

    Used in: 2.18, 3.11

Shared source register

Your progress is stored in this browser on this device.