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

3GPP TF · UIC

UIC 3GPP Task Force: Rail Requirements in 5G and MCX

The UIC 3GPP Task Force represents rail requirements in the international mobile communications standardisation of the 3rd Generation Partnership Project (3GPP). UIC: FRMCS – organisation and document directory

v1.0Source material checked: 02 Oct 2026

Type: UIC task force · ID: G08

The UIC 3GPP Task Force represents rail requirements in the international mobile communications standardisation of the 3rd Generation Partnership Project (3GPP). UIC: FRMCS – organisation and document directory

Role in the FRMCS Context

FRMCS uses 5G technologies and Mission Critical services. For these to support rail operations, specific requirements must be fed into the relevant 3GPP working groups. The UIC documents contributions to SA1, SA6, CT1 and RAN4 for May 2026. These address requirements, service architecture, protocols and radio aspects. UIC: Contributions to 3GPP, 17 June 2026

An illustrative example is a change request documented in the 3GPP portal to align with UIC FU-7120: it addresses a gap in multi-talker control. Entries like this show how a rail need becomes a concrete standardisation task. 3GPP: Change Request to align with UIC FU-7120

Significance and Binding Nature

A submitted contribution is not yet an adopted standard. For a technical reference, the affected specification, the release and the documented decision status are decisive. The 3GPP specification is the outcome of that process, not a sole publication of the UIC task force. 3GPP: Portal for specifications and working documents

Working Groups and Cooperation

The technical link runs from the UIC body of requirements into the relevant 3GPP groups. The UIC announcement published in June 2026 describes this work for Releases 19 and 20. UIC: Contributions to 3GPP, 17 June 2026

Practical Guidance

Recommendation for product planning: initially record new contributions as a development signal. Only commit to supported product features after checking against the specification and implementation status.

Documents and deliverables

Document

Technical contributions to 3GPP

Feed in rail-specific requirements and proposed solutions

Documented status

Check status per contribution and meeting

Document

Change requests and resulting specification changes

Document proposed and approved changes

Documented status

Distinguish proposal from approved status

Practical perspective

Recommendation for product planning: initially record new contributions as a development signal. Only commit to supported product features after checking against the specification and implementation status.

Frequently asked question

Does an FRMCS contribution mean the function is already available?

No. Contribution, standardisation, implementation and evidence in the product are separate steps. For procurement, each of these stages should be traceable.

Related bodies

Sources and review status

  1. [1]UIC: FRMCS – organisation and document directory(02 Oct 2026)
  2. [2]UIC: Contributions to 3GPP, 17 June 2026(02 Oct 2026)
  3. [3]3GPP: Change Request to align with UIC FU-7120(02 Oct 2026)
  4. [4]3GPP: Portal for specifications and working documents(02 Oct 2026)