Skip to content
Independent reference on the Future Railway Mobile Communication System
← Organisations & bodies

TOBA · UIC

UIC TOBA: FRMCS On Board

Telecom On-Board Architecture (TOBA) stands, within the UIC FRMCS programme, for the on-board architecture and the associated functional requirements. UIC: FRMCS – organisation and document directory

v1.0Source material checked: 02 Oct 2026

Type: UIC working group · ID: G04

Telecom On-Board Architecture (TOBA) stands, within the UIC FRMCS programme, for the on-board architecture and the associated functional requirements. UIC: FRMCS – organisation and document directory

Role in the FRMCS Context

For vehicle keepers, manufacturers and integrators, the on-board side is therefore the right starting point. ERA lists the On-Board FRMCS Functional Requirements Specification as a standalone document. The UIC also lists documents on migration variants for existing ETCS and cab-radio units. ERA: Opinion ERA/OPI/2024-10 and associated specifications UIC: FRMCS – organisation and document directory

For practical work, target equipment and the conversion path should be described separately. A vehicle concept must fit both the planned communication and the existing fleet. This profile therefore recommends recording existing applications, interfaces and conversion steps together before a specific equipment configuration is selected.

Significance and Binding Nature

A migration study and a requirements specification serve different purposes. For project requirements, the version used must be reconciled with the applicable regulatory framework and the agreed project scope. CCS TSI Annex A references TOBA-7510 with a specific version. ERA: CCS TSI Appendix A – mandatory specifications

Working Groups and Cooperation

Closely related areas are the ATWG for the overall system and the FFFIS work on application interfaces. The connection of on-board applications is described in FFFIS-7950 via OBAPP. UIC: FRMCS SRS AT-7800, version 2.1.0 (at ERA) UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)

Practical Guidance

Recommendation for vehicle projects: for each application, document the current connection, the planned FRMCS connection and the transitional state.

Documents and deliverables

Document

On-Board FRMCS FRS – TOBA-7510

Functional requirements for the vehicle side

Documented status

Listed in ERA's V2 document package

Document

TOBA-7515 / TOBA-7540

Documents on migration variants and on-board architecture

Documented status

Listed in the UIC document directory

Practical perspective

Recommendation for vehicle projects: for each application, document the current connection, the planned FRMCS connection and the transitional state.

Frequently asked question

Are TOBA and OBAPP the same thing?

No. TOBA refers to the on-board architecture context. OBAPP refers to the interface specified in the FFFIS between on-board applications and On-Board FRMCS. [UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)](https://www.era.europa.eu/sites/default/files/2025-05/frmcs%20fffis%20%28fffis-7950%29%20v2.1.0.pdf?t=1790918959)

Related bodies

Sources and review status

  1. [1]UIC: FRMCS – organisation and document directory(02 Oct 2026)
  2. [2]ERA: Opinion ERA/OPI/2024-10 and associated specifications(02 Oct 2026)
  3. [3]ERA: CCS TSI Appendix A – mandatory specifications(02 Oct 2026)
  4. [4]UIC: FRMCS SRS AT-7800, version 2.1.0 (at ERA)(02 Oct 2026)
  5. [5]UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)(02 Oct 2026)

Editorial note: TOBA full text was not available at the time of retrieval. Statements are limited to publicly documented responsibility and document metadata; no detailed review of individual TOBA requirements is claimed.