Study on feasibility of SATCOM for railway communication

Final Report
MEO / C-band
Criterion ID Criterion Evaluation Justification
CRT-TECH-9
The proposed satcom system shall provide priority and preemption
mechanisms.
C
The use in this solution of the DVB-S2X/RCS2 communications standards assures
the ability of the system to support and manage priority and pre-emption
mechanisms.
QoS in DVB standards are basically managed at layer 2, with the use of
differentiated queues for different type of traffic (real time, critical data, best
effort...).
The DAMA mechanism also assures the resources assignment to users by means
of several schedule techniques such as Continuous Rate Assignment (CRA),
Rate/Volume Based Dynamic Capacity (RBDC/VBDC), Free Capacity Allocation
(FCA), etc.
CRT-TECH-10
The proposed satcom system shall support Data and Voice
services.
C
This solution is full IP and based on a TDM/MF-TDMA (DAMA) scheme using
DVB-S2X / RCS2 standards respectively. Therefore, it will support all kind of IP
services (voice and data). It is worth to mention that DVB-RCS2+M includes also a
RA carrier for asynchronous data and network signalling.
CRT-TECH-11
The proposed satcom system shall support as minimum Low
bandwidth applications
C
Taking into account the correct dimensioning of the system, this MEO/C-band
solution is able to provide railway critical narrowband applications. In this case,
performance and/or business applications will not be offered by this solution since
they require more bandwidth (in fact, high frequency bands, such as Ku and Ka
bands will only offer them).
CRT-TECH-12
The proposed satcom system for the FRMCS shall provide
“user-to-user” and “multi-user” types of communications for
both voice and data services. In addition, each communication
can be bi-directional or uni-directional with any type of
asymmetry between forward and return channels (when bidirectional).
C
This MEO/C-band system is based on a theoretical future solution. Therefore, and
considering that this is an all-IP solution, all these types of communications can be
implemented (at least) at IP-level.
Doc.Nº: SRAIL-FNR-010-IND
Edit./Rev.: 1/1
Date: 16/02/2017
Page 227 of 285