<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Dual-Frequency EGNOS and Galileo-based GNSS Receiver and Antenna for Railway: TRENI Project</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Marco</forename><surname>Puccitelli</surname></persName>
							<email>marco.puccitelli@thalesaleniaspace.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Thales Alenia Space Italia</orgName>
								<address>
									<addrLine>Via E. Mattei 1</addrLine>
									<postCode>20064</postCode>
									<settlement>Gorgonzola (Milan)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Chiara</forename><surname>Manno</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Thales Alenia Space Italia</orgName>
								<address>
									<addrLine>Via E. Mattei 1</addrLine>
									<postCode>20064</postCode>
									<settlement>Gorgonzola (Milan)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Livio</forename><surname>Marradi</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Thales Alenia Space Italia</orgName>
								<address>
									<addrLine>Via E. Mattei 1</addrLine>
									<postCode>20064</postCode>
									<settlement>Gorgonzola (Milan)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Gaetano</forename><surname>Pastore</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Thales Alenia Space Italia</orgName>
								<address>
									<addrLine>Via Saccomuro 24</addrLine>
									<postCode>00131</postCode>
									<settlement>Rome</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Hanaa</forename><surname>Al Bitar</surname></persName>
							<affiliation key="aff2">
								<orgName type="institution">Thales Alenia Space France</orgName>
								<address>
									<addrLine>Av. Champollion 26</addrLine>
									<postCode>31100</postCode>
									<settlement>Toulouse</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Anne</forename><forename type="middle">Marie</forename><surname>Tobie</surname></persName>
							<affiliation key="aff2">
								<orgName type="institution">Thales Alenia Space France</orgName>
								<address>
									<addrLine>Av. Champollion 26</addrLine>
									<postCode>31100</postCode>
									<settlement>Toulouse</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Rodolfo</forename><surname>Guidi</surname></persName>
							<affiliation key="aff3">
								<orgName type="department">EikonTech</orgName>
								<address>
									<addrLine>Via Livornese 1019</addrLine>
									<postCode>56122</postCode>
									<settlement>San Piero a Grado (Pisa)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Giovanni</forename><surname>Galgani</surname></persName>
							<affiliation key="aff3">
								<orgName type="department">EikonTech</orgName>
								<address>
									<addrLine>Via Livornese 1019</addrLine>
									<postCode>56122</postCode>
									<settlement>San Piero a Grado (Pisa)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Inzirillo</surname></persName>
							<affiliation key="aff4">
								<orgName type="department">Mermec</orgName>
								<address>
									<addrLine>Via G. Oberdan 70</addrLine>
									<postCode>70043</postCode>
									<settlement>Monopoli (Bari)</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Filippo</forename><surname>Rodriguez</surname></persName>
							<affiliation key="aff5">
								<orgName type="institution">Telespazio Italia</orgName>
								<address>
									<addrLine>Via Tiburtina 965</addrLine>
									<postCode>00156</postCode>
									<settlement>Rome</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Alessio</forename><surname>Martinelli</surname></persName>
							<affiliation key="aff5">
								<orgName type="institution">Telespazio Italia</orgName>
								<address>
									<addrLine>Via Tiburtina 965</addrLine>
									<postCode>00156</postCode>
									<settlement>Rome</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yuval</forename><forename type="middle">B</forename><surname>Yossef</surname></persName>
							<affiliation key="aff6">
								<orgName type="department">Saphyrion</orgName>
								<address>
									<addrLine>Strada Regina 16</addrLine>
									<postCode>6934</postCode>
									<settlement>Bioggio</settlement>
									<country key="CH">Switzerland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Daniel</forename><surname>Lopour</surname></persName>
							<affiliation key="aff7">
								<orgName type="institution">EUSPA</orgName>
								<address>
									<addrLine>Janovského 438/2</addrLine>
									<postCode>170 00</postCode>
									<settlement>Prague 7, Holesovice</settlement>
									<country key="CZ">Czech Republic</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff8">
								<orgName type="institution">ICL-GNSS</orgName>
								<address>
									<addrLine>2022 WiP, June 07-09</addrLine>
									<postCode>2022</postCode>
									<settlement>Tampere</settlement>
									<country key="FI">Finland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Dual-Frequency EGNOS and Galileo-based GNSS Receiver and Antenna for Railway: TRENI Project</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">9A058E12FA7AAC833D043099CA1EBB87</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T08:07+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>GNSS</term>
					<term>EGNOS</term>
					<term>GALILEO</term>
					<term>RAIL</term>
					<term>SAFETY</term>
					<term>INTEGRITY</term>
					<term>CRPA</term>
					<term>HYBRID-PVT</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The railway signalling system in Europe is currently undergoing a major change, converging towards interoperability and safety to be ensured by the ongoing deployment of the European Rail Traffic Management System -ERTMS. However, at present, ERTMS does not envisage the use of GNSS positioning technology for safety relevant train localization. Introduction of GNSS is an opportunity to contribute towards increasing of both safety and security or simplifying and reducing trackside equipment. It can also contribute to reducing overall signaling system costs which is instrumental especially for keeping the rural capillary lines competitive with other modes of transport. To enable such benefits and to contribute toward Green and sustainable transport services the European Commission and European Union Agency for the Space Program (EUSPA) are collaborating with the main rail and space stakeholders on the inclusion of GNSS into the future evolution of ERTMS. This paper presents the TRENI railway GNSS receiver and antenna development, to be used directly or integrated in a train multi-sensor safe positioning platform, suitable for railway safety-related applications.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>According to the latest EUSPA GNSS Market Report <ref type="bibr" target="#b0">[1]</ref>, GNSS plays an important role in many non-safety related applications and the introduction of GNSS in future safety-related applications is expected to increase railway network capacity whilst decreasing operational costs. However, the rail scenario introduces several challenges: it is a dynamic scenario, moving in different environments from rural to urban, with different visibility conditions of the GNSS signals and with varying RF environment conditions. In addition, the criticality of the application requires a GNSS system robust to threats that may occur during operations.</p><p>In this context, the TRENI project aims at implementing a double step forward with respect to current state-of-the-art GNSS railway solutions. On the one side, the GNSS receiver will provide a dualfrequency (L1/L5) Galileo/GPS multi-constellation platform, with enhanced robustness and integrity features granted by the capability to autonomously identify and counteract to failures resulting from GNSS constellations faults, RF environment threats or from the receiver itself. Key features in terms of robustness to harsh RF environments will be based on receiver digitally Controlled Radiation Pattern Antenna (CRPA) techniques, pre/post-correlation algorithms for Jamming or Spoofing detection &amp; mitigation and lastly PVT hybridization with complementary PNT sensors (IMU and odometers) (Figure <ref type="figure" target="#fig_0">1</ref>). On top of this, the integrity information broadcasted by SBAS (EGNOS) will be used for the evaluation of the Along-Track Protection Level (ATPL) and solution confidence intervals, with alerts provision in case predefined thresholds for the service are exceeded. The second innovative element brought by the TRENI solution consists in the antenna element design. Indeed, currently only single-band (L1) GNSS antennas certified for rail applications (i.e. designed and tested against EN applicable standards) are available on the market, raising the need to develop a dual-band (L1/L5) multielement CRPA antenna capable to support the interference mitigation functionality and to comply with the EN standards, thus being certifiable for the use in railway environment. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Use Cases, CONOPS and Rail Environment Threat Scenario</head><p>GNSS may be used to increase the capacity of the railway network by allowing the development of future train operations such as moving block or virtual coupling. These systems are evaluated with the aim of ensuring fail-safe train location and location integrity. Moreover, GNSS is part of the digitalization that is reflected in the development of new applications, such as enhanced passengers information services, but also bringing benefits to railway operators and infrastructure managers because of the improved asset management and maintenance, thereby reducing the operational costs.</p><p>Different applications can be hence addressed by the TRENI platform, starting from primary safety systems, where GNSS is involved in direct safety chain of rail operations. As non-exhaustive examples, these primary safety systems encompass:  Train integrity (i.e. train length monitoring);  Train control (virtual balises, absolute positioning, guidance and navigation);  Trains spacing over the line for traffic control systems. In addition, overlaid safety systems can be considered as a potential use case, in which the GNSS could be to provide information to safety back-up systems, for instance:  Simplified signalling (back-up) systems, capable of providing safety in operational conditions (e.g. cold movement detectors or level-crossing protection).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Driving intelligent assistance (e.g. alarms to train driver);</p><p>Dealing with non-safety applications examples could be:  Fixed asset management (e.g. infrastructure surveying and monitoring);  Rolling stock management (e.g. fleet management, cargo monitoring, energy charging);  Passenger Information (e.g. journey assistant, customer information, on-train reservations). The main GNSS threats affecting accuracy and integrity of the position solution in the railway environment are listed in Table <ref type="table" target="#tab_0">1</ref>, which defines also associated models and anomalies that will be considered for the in laboratory validation campaign of the GNSS receiver.</p><p>Four critical scenarios have been selected to stress the performance of the GNSS receiver: the first two refer to the train in a stationary state respectively located at the station and in a rural area; the second two respectively refer to the train moving at low speed and located in urban environment and the train moving at high speed and located in rural area. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>-</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Signal Loss</head><p>Loss of signal based on visibility mask. -</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Dual-Band CRPA Antenna</head><p>The GNSS antenna for the TRENI project is asked to have features not available in commercial GNSS antennas currently on the market. Indeed the antenna is required to be dual band (i.e. L1/E1+L5/E5a) and to give the possibility to perform null forming by the receiver, in order to maintain integrity in presence of interference and spoofing. This leads to an antenna architecture of a 4-element array, necessary to apply beam forming strategies that give the additional requirement of an interelement spacing within lambda/2 at maximum operating frequency. Another constraint, not related to performance, is the need to design an antenna system keeping the cost within limits compatible with the railway market. An RF Front-End, capable to amplify the GNSS signal of about 25 dB and to reject quite demanding near and out-of-band interferences, is part of the antenna system. A calibration circuit allows the equalization of the four FEs. The whole antenna architecture is shown in Figure <ref type="figure" target="#fig_1">2</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Radiating Elements &amp; Array Design</head><p>The main characteristics of the radiating elements are listed below and shown in Figure <ref type="figure">3</ref> -Figure <ref type="figure">4:</ref>  Patch antenna technology for an easy and cheap manufacturing;  Grounding pin not interfering with radiative performance, implemented as overvoltage protection from overhead catenary;  Dual-band self-diplexed with two separated outputs (i.e. one for L1/E1, one for L5/E5), thus optimizing the front-end architecture;  Sequential rotation applied to array layout, in order to assure axial symmetry during installation. The Single Element Return Loss (left plot in Figure <ref type="figure" target="#fig_3">5</ref>), shows that the -10dB target in E5/L5 (i.e. in the band 1166 -1186 MHz) and E1/L1 (i.e. between 1565 -1585 MHz) is satisfied with a safe margin, allowing the matching of the requirement also at array level (right plot in Figure <ref type="figure" target="#fig_3">5</ref>).  Regarding the antenna front-end (FE) architecture, it consists in a single amplification stage based on COTS amplifier components and custom design band-pass filters, with low insertion loss and steep transition regions, specifically tailored to cope with RF interference masks specified by <ref type="bibr" target="#b1">[2]</ref>, <ref type="bibr" target="#b2">[3]</ref>. At the antenna FE level also coupling microstrip sections are foreseen to inject the RF calibration signal, provided by the GNSS Receiver for the end-to-end RF chain calibration (amplitude and phase).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">TRENI GNSS Receiver</head><p>The TRENI GNSS Receiver is a customization of Thales Alenia Space Italia latest Test User Receiver (TUR) 19"-1U platform, already foreseen to be used for rail applications, as well as for avionic or maritime users. The baseline architecture is adapted to handle and process signals from up to 4 parallel RF inputs, with a future-proof design granted by the RF Direct Sampling and Digital Down-Conversion approach, intrinsically allowing the receiver to accommodate any GNSS signal scenario evolution in terms of frequency plan and signal modulations by simply updating FPGA FW and Receiver Application SW.</p><p>The high-level architecture of the receiver is presented in Figure <ref type="figure" target="#fig_5">7</ref>, mainly consisting in a power supply module (i.e. a COTS AC/DC converter in the TRL7 prototype), an Analogue RF Front-End section (for RF signal filtering and antenna elements power feeding), a Digital Section (in charge of RF sampling, signal acquisition/tracking and navigation processing, calibration signal generation and external communication handling) and an I/O interface expansion module (for 1PPS and ERR/RESET TTL signals provision).  Besides the TRENI GNSS Receiver HW, the "Safe Multi-Sensor Positioning" equipment (i.e. a companion Host PC) will be interfaced to allow the receiver monitoring &amp; control, GNSS raw observables real-time visualization and storage (e.g. for post-processing and test replay under different configurations and data-fusion with external sensors data for GNSS-IMU Hybrid PVT solution evaluation).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Digital Null-steering with CRPA</head><p>Among pre-correlation techniques considered within the TRENI Receiver for mitigation of unintentional RF interference and/or malicious jammer, a focus is here below proposed w.r.t. the wellknown MUltiple SIgnal Classification (MUSIC) <ref type="bibr" target="#b5">[6]</ref> and Power Inversion (PI) <ref type="bibr" target="#b6">[7]</ref> methods, applied to antenna pattern digital null-steering. Both the mentioned algorithms can be implemented at receiver FPGA level by conveniently combining the I/Q digital signal samples generated by the digital Down-Conversion Chains (DDCs), associated to the different radiating elements. In particular the Digital Board FPGA engine performs the following main tasks associated to the CRPA functionality:  reception of 8 high-speed lanes (carrying I/Q samples from the 4 RF Channels) and feeding of the "covariance matrix" calculation block;  covariance matrices computation engine &amp; communication with DSP processor for provision of covariance indexes and reception of associated complex weights (computed by DSP for the following I/Q samples digital combination);  management of the calibration signal synthesis through an external dedicated DAC. The Eigen value decomposition of the covariance matrix, computed by the DSP processor as described above, gives a perfect interference detector: indeed without interference (i.e. without correlated signal at the antenna array), the correlation of the array matrix will be close to diagonal (signals of each antenna would consist in uncorrelated white noise) and the Eigen values will then correspond to the noise power. Otherwise, in presence for instance of one jammer, one Eigen value will increase to represent the power of the interference source.</p><p>Hence starting from the covariance matrix decomposition in eigenvalues and eigenvectors, the nullsteered antenna element complex weights (𝜔 * ) are computed with MUSIC or PI method and used to multiply the I/Q signal samples to generate a unique stream as follows:</p><formula xml:id="formula_0">𝑦 𝑜𝑢𝑡 = ∑ 𝑦 𝑛 • 𝜔 * 𝑁 𝑎𝑛𝑡 𝑛=1 ,<label>(1)</label></formula><p>The effects of a jammer on weighted signals combination, if properly managed, will result mitigated after the null-forming process. In general, despite the superior performance expected for MUSIC algorithm in terms of Direction of Arrival (DoA) estimation and maximum "peak-to-null" gain ratio (i.e. interference rejection), PI method is typically preferred in GNSS applications due to its simpler implementation based on a "blind" approach (i.e. it does not require a-priori knowledge about antenna array such as antenna element orientation, gain/phase patterns, calibration values, etc.).</p><p>Before qualitatively assessing the null-steering capability, by assuming an AWGN only environment (i.e. no interference) as the nominal antenna operating condition, default CRPA weights can be defined, for instance, in order to optimize RHCP gain pattern at zenith. The results for the combination of antenna elements embedded RHCP gain patterns in a single equivalent one are reported in the following Figure <ref type="figure" target="#fig_6">8</ref>.  Simulations results are provided in Figure <ref type="figure" target="#fig_8">10</ref>, showing as expected a higher interference rejection for MUSIC (minimum P2N ratio in the order of 50dB), compared to the PI algorithm one (approx. 20dB). </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Safe Multi-Sensor Positioning: Hybrid PVT &amp; Integrity</head><p>Hybridized PVT solutions will be implemented and evaluated in order to demonstrate the enhancements brought by GNSS data hybridization with additional sensors installed on the test rolling stock. This integration will allow for:  FDE capability to remove faulty ranges;  Accurate train positioning even under GNSS signal limited-visibility conditions;  Along track position, speed and the associated integrity protection level (ATPL). Each of these steps are briefly described in this section. An IMU is a complete 3D dead-reckoning navigation system. Therefore, it does not allow to obtain an absolute positioning solution by itself, but can significantly improve the accuracy and the integrity of the positioning solution when combined with other sensors. In the TRENI project, the IMU will be hybridized with GNSS, odometer and possibly 2D maps.</p><p>In order to prevent unavailability of maps or unavailability of associated integrity information, it is proposed to limit the impact of the map on the navigation filter design while keeping its potential information useful. If available and associated with integrity, it has been proposed to use the map to correct the navigation solution after the hybridization filter. Since the cartography in the Railways domain is expected to be highly accurate (yet with no integrity data associated), it is proposed to assume it fault free for the integrity concept. The method consists in projecting the navigation solution on to the nearest point of the rail in the map.</p><p>If the map is available, FDE methods will have to be derived to ensure that, in case where 2 rails are side by side but heading in opposite directions, the navigation solution is projected to the correct rail.</p><p>Therefore, in this article, the focus is on the coupling scheme between GNSS, IMU and odometer. According to <ref type="bibr" target="#b7">[8]</ref>; several hybridization schemes may be considered: loose (LC), tight (TC) and ultratight coupling (UTC).</p><p>The choice of the coupling strategy is not straightforward. A critical analysis has been performed and the TC is preferred for the TRENI hybridization module. The arguments considered are the following: the TC provides a more accurate solution than a LC and, a PVT can be computed even with less than 4 GNSS satellites but at the expense of a slightly more complex implementation. In addition, a TC solution requires the knowledge of the ephemeris as well as an accurate synchronization between the integrated navigation systems.</p><p>Following the previously defined TC solution, an integrity concept is also proposed. Solutions are designed at several levels (pre-processing techniques, error characterization and measurement rejection approaches) in order to meet the integrity requirements and Key Performance Indicators (KPIs).</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: TRENI Platform functional diagram</figDesc><graphic coords="2,72.00,312.33,450.91,155.85" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: CRPA antenna high-level architecture</figDesc><graphic coords="3,142.97,661.08,323.18,93.31" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :Figure 4 :</head><label>34</label><figDesc>Figure 3: CRPA single antenna radiating element design &amp; stack up</figDesc><graphic coords="4,122.75,210.44,349.12,120.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Single radiating element (left) and antenna array return loss (right) [dB]</figDesc><graphic coords="4,86.00,548.97,422.80,181.22" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Single Element Antenna RHCP and LHCP Gain [dBi] in L5 and L1 bands</figDesc><graphic coords="5,101.75,109.95,391.09,164.55" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 7 :</head><label>7</label><figDesc>Figure 7: TRENI DFMC GNSS Receiver architecture layout (left) and interfaces (right)</figDesc><graphic coords="5,72.00,586.45,453.20,106.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 8 :</head><label>8</label><figDesc>Figure 8: CRPA digitally combined pattern in AWGN only condition (weights optimized for zenith)</figDesc><graphic coords="7,72.13,161.24,450.69,149.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Figure 9 :</head><label>9</label><figDesc>Figure 9: Digital Null-Steering capability example in presence of 2 RFI sources</figDesc><graphic coords="7,72.00,438.17,453.50,240.18" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Figure 10 :</head><label>10</label><figDesc>Figure 10: CRPA Peak2Null (P2N) gain ratio cumulative distributions for MUSIC and PI methods</figDesc><graphic coords="8,108.30,109.95,378.31,166.30" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="9,72.00,85.39,450.79,182.54" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>GNSS threat sources, relative models and anomalies implemented in the emulation environment.</figDesc><table><row><cell>Threat Source</cell><cell>Models</cell><cell>Anomalies</cell></row><row><cell>Clocks</cell><cell>Atomic clock model for satellite clock, Quartz clock model for Rx clock.</cell><cell>Excessive acceleration, clock steps/ramps.</cell></row><row><cell>Ephemeris</cell><cell>Ephemeris model defined by NAVmsg.</cell><cell>Missing Update, Unflagged Maneuvers, Erroneous Broadcasting.</cell></row><row><cell>Ionosphere</cell><cell>NeQuick model for ionospheric error.</cell><cell>Spatial and temporal gradient.</cell></row><row><cell>Troposphere</cell><cell>RTCA DO-229F MOPS model for tropospheric error component.</cell><cell></cell></row></table><note>Excessive troposphere components w.r.t. identified model.InterferenceInterference by analogue TV or DVTB, jamming by device on train or in station.-SpoofingSpoofing attack performed by a device located either on board or in station.-Multipath &amp; Rx noiseMultipath/RX noise pseudorange error mapped vs elevation (scenario dependent parameters and DSM model considered).</note></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Acknowledgements</head><p>This project is part of "Fundamental Element" framework and is being conducted under a grant related to the development of a Galileo Receiver for localization in train signalling (GSA/GRANT/05/2019), supported by the European Union Agency for the Space Program (EUSPA) and coordinated by Thales Alenia Space Italia S.p.A (TAS-I), in collaboration with Thales Alenia Space France S.A.S. (TAS-F), MERMEC S.p.A. (Italy), Telespazio Italia S.p.A. (TPZ-I) and Saphyrion Sagl. (Switzerland).</p></div>
			</div>


			<div type="funding">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This project is part of "Fundamental Element" framework and is being conducted under a grant related to the development of a Galileo Receiver for localization in train signalling (GSA/GRANT/05/2019), supported by the European Union Agency for the Space Program (EUSPA) and coordinated by Thales Alenia Space Italia S.p.A (TAS-I), in collaboration with Thales Alenia Space France S.A.S. (TAS-F), MERMEC S.p.A. (Italy), Telespazio Italia S.p.A.</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The proposed integrity concept is illustrated in Figure <ref type="figure">11</ref>. On one side, the IMU is used to propagate the solution, and, on the other side, the odometer and GNSS are the measurements considered to update the solution.</p><p>The integrity solution leverages on a mixed use of Kalman Filter Measurement Innovation (KFMI) principle, and majority vote redundancy scheme. The FDE methods are applied both in the preprocessing step and in the update step. Majority vote method is applied in the pre-processing step to ensure the validity of the IMU measurements. Then, the combination of the KFMI based solution with majority vote solution is used to identify and reject potential faulty sensors.</p><p>In Figure <ref type="figure">11</ref>, four PVT solutions are represented: a hybrid IMU/GNSS/odometer tight coupling filter (PVT 1), a hybrid IMU/GNSS tight coupling filter (PVT 2), a hybrid IMU/odometer tight coupling filter (PVT 3) and an IMU only filter (PVT 4).</p><p>In order to limit the computational burden, a first step will consist in computing PVT 2, 3 and 4. If all 3 solutions are identical (assuming a tolerable variance), then PVT 1 will be computed and will be the final solution.</p><p>For PVT solutions 1, 2 and 3, the KFMI is applied, therefore, it is expected that faulty GNSS measurements will already be detected and excluded. PVT 4, IMU only, is expected to be fault free since the pre-processing step is expected to have detected and excluded faulty IMUs (based on majority voting among 3 IMUs). The comparison of PVT 2, 3 and 4 will allow the detection of remaining errors and the exclusion of sensors if they are identified as faulty. Majority vote methods will be applied to identify these remaining faults. For example:  If PVT 2, 3 and 4 provide the same solution (assuming a pre-defined tolerable difference) then the final solution will be PVT 1.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>If PVT 2 and 4 are equal but different from PVT 3, the odometer is detected as faulty, the final solution will be PVT 2.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>If PVT 3 and 4 are equal but different from PVT 2, the GNSS is detected as faulty, the final solution will be PVT 3. Based on the final PVT choice, the 2D map can be applied to correct the position, to ensure that the train is on the correct rail. As explained above, the map is expected to be use in a post PVT step to correct the PVT, therefore, it is assumed that the map is correct and fulfils integrity requirements to be defined.</p><p>Finally, the last step of hybridization section is the definition of the PL, as illustrated in Figure <ref type="figure">12</ref>. In fact, for the train case, the definition of PL can be simply projected on the train track in order to provide the ATPL (since there are no other degrees of freedom in the train motion, and thus the problem is essentially 1D). In this way the horizontal PL "collapses" into a 1D PL in the horizontal plane. Hence the ATPL, computed using all non-excluded measurements, is defined as:</p><p>where KPMI is a protection coefficient defined as a function of the integrity risk probability PMI, and σalong is the along track standard deviation defined as:</p><p>where θ is the azimuth of the track line segment on which the train has been determined to be situated, σE and σN are the East and North standard deviation components.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Way Forward &amp; Conclusion</head><p>The TRENI platform will go through an extensive verification and validation activity. Different phases are envisaged starting from laboratory subsystems integration and functional verification, validation at Telespazio laboratories in Rome against worst case expected threats models generated by a realistic emulation test bed, and lastly relying on the field test campaign, supported by additional equipment that will record I/Q data streams from the GNSS antenna during the train runs on the Italian national railway line (RFI). The gathered data will be very useful to replay the experienced scenario in laboratory and will allow for the characterization of the RF environment during the field test runs, as well as allow for the testing and comparison of the different receiver algorithms and techniques on the replayed data. Moreover GNSS receiver measurements gathered along with the IMU &amp; Odometer sensors data (but also with other external sensors data such as physical balises and geo-located reference points along the track), will finally allow for the definition of an a-posteriori reference "truth" trajectory, that will be exploited for the verification of GNSS performance achieved during the field tests campaign and verification of the hybridized PVT solution and integrity concept performance.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">EUSPA EO and GNSS Market Report issue</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Minimum Operational Performance Standards for Global Positioning System Satellite-Based Augmentation System Airborne Equipment</title>
		<idno>RTCA DO-229</idno>
		<imprint/>
	</monogr>
	<note>Issue F</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Minimum Operational Performance Specification for Galileo / Global Positioning System / Satellite-Based Augmentation System Airborne Equipment</title>
	</analytic>
	<monogr>
		<title level="j">EUROCAE</title>
		<imprint>
			<biblScope unit="volume">259</biblScope>
		</imprint>
	</monogr>
	<note>Issue 1.0</note>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">SBAS L1 Receiver Guidelines for Railway On-board Unit</title>
		<idno>ESSP-TN-25931 Issue 01-00</idno>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">SBAS DFMC Receiver Guidelines for Railway On-board Unit</title>
		<idno>ESSP-TN-26136 Issue 01-00</idno>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Multiple emitter location and signal parameter estimation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Schmidt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Transactions on Antennas and Propagation</title>
		<imprint>
			<biblScope unit="volume">34</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="276" to="280" />
			<date type="published" when="1986-03">March 1986</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Adaptive antenna arrays for interference cancellation in GPS and GLONASS receivers</title>
		<author>
			<persName><forename type="first">D.-J</forename><surname>Moelker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Van Der Pol</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Bar-Ness</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of Position, Location and Navigation Symposium -PLANS &apos;96</title>
				<meeting>Position, Location and Navigation Symposium -PLANS &apos;96</meeting>
		<imprint>
			<date type="published" when="1996">1996</date>
			<biblScope unit="page" from="191" to="198" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Principles of GNSS, inertial and multi sensor integrated navigation systems</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">D</forename><surname>Groves</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2007">2007</date>
			<publisher>Artech House</publisher>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
