Documente Academic
Documente Profesional
Documente Cultură
AbstractPredictive monitoring of train wagons can allow to quantities like vibrations and temperature whose cross-analysis
anticipate possible malfunctioning due to wear and avoid allows to determine the state of the carriage and estimate the
potential accidents. In this paper some network architectures probability of faults within a certain timeline. The sensors are
adopting low-power wireless communication technologies are autonomous for energy provisioning, assuming they are
introduced. A performance comparison is provided based on ns-2 powered by specific harvester recovering energy from the
simulation results, suggesting that the combined use of WSN and environment. Sensor data locally collected by sensing nodes
WiFi in a hierarchical architecture is adequate for long trains are finally transmitted via radio communication to a gathering
with several coaches and a large number of sensing nodes. center. Several requirements in terms of bandwidth, radio
channel capacity, energy consumption, data security and
Keywordscondition-based monitoring; railway scenarios;
wireless sensors; ns-2 simulations
devices physical robustness have to be considered. In this
work, we focus our attention on communication aspects, which
will be presented and analyzed in major detail in section IV
I. INTRODUCTION AND MOTIVATION devoted to proposed system architectures. Before, section II
Passengers trains and, even more, freight cars cover long lists the main system requirements, in particular concerning
distances during the span of their railway life. National and data management and communication, and section III reviews
international railway legislation exists which imposes periodic the state of the art about wireless (particularly WSN-based)
checks of railway carriages conditions and the appropriate monitoring systems in railway scenarios. Simulation results
maintenance in railways workshops. Nonetheless the persistent involving the proposed architectures are illustrated and
monitoring of wagons conditions finalized to anticipate commented in section V. Section VI concludes the paper.
possible malfunctioning caused by wear and to avoid potential
accidents represents an added value. This concept is known as II. MAIN SYSTEM REQUIREMENTS
condition-based monitoring.
The sensing nodes integrated with bearings and positioned
The monitoring is made possible by the presence of sensors in axle-box must satisfy a set of physical restrictions in terms
installed on bearings positioned along the wheel-axle of the of sizes and deployment, as well as covers of adequate
several bogies and coaches composing a train. Bearings materials for device protection. Geometrical features also
deployed in axle-box collect acceleration samples which, concern carriage shape and train composition. Fig. 1 depicts the
opportunely correlated and fused, allow to derive real time shape of a real passenger coach, and the reported dimensions
information about the bogie state in terms of stability. Beside are used as inputs in the simulated scenario.
accelerometer values, temperature readings are of interest too
since overheating of bearings could compromise the correct
functioning and, definitively, the bogie solidity.
Bearings for railway bogie equipped with sensors already
exist which provide continuous time analogue signals.
However, the data communication is enabled by a wired
system and, similarly, the system energy requirements force the Fig. 1. A single carriage and, quoted, its dimensions in length.
bearings to be inline powered. The challenge, now, is instead to
realize a wireless communication system whose nodes are More important for communication system design are those
powered by energy harvesting solutions. A wireless system is requirements concerning temperature and acceleration data
desirable for costs reduction: installation and maintenance are sampling. Approximately, updated temperature readings should
simple and economic. be available about every minute while older samples than four
or five minutes are useless for application purposes.
Definitively, the system we have in mind can be described Acceleration data related to vibrations require to be collected
as follows. It consists of a number of sensors deployed in the much more frequently than temperature values since only long
carriage and able to capture, while the train is moving, physical
Some of these parameters are kept unvaried from one Fig. 5. NAM: the node deployment in a coach according to the hierarchical
two-tier architecture.
simulation to another. On the contrary others are tuned to
Ns-2 provides several traffic generators. The simplest one, D. Performance evaluation
and the only one considered in the simulations results In this section the simulation results achieved for the
presented in this paper, is the CBR traffic model, able to different system architectures and scenarios described in
simulate a source of packets periodically transmitted. It is section IV are presented. CBR traffic model is used and the
based on two input parameters whose combined tuning allows only parameter kept unvaried in all the simulations is the
to set out the traffic load as desired: the transmission interval packet size, selected equal to 96 bytes in order to avoid
(TI), i.e., the period between two distinct consecutive packets fragmentation. Hence the resulting offered traffic only depends
generated by the same sensing node, and the packet size. on the TI value. When running simulations, larger TI values
corresponding to lower traffic loads were initially set while
C. Performance metrics shorter transmission intervals and higher traffic loads were
Simulation trials have been carried out to evaluate network gradually chosen until overload conditions were obtained and
performance, discuss adequacy of each solution highlighting the actual system capacity was identified. When the generation
pros and cons, finally identify and select the most appropriate rate of new packets by source nodes exceeds a certain
network topology and overall architecture able to meet the threshold, buffers occupation locally at nodes tends to rapidly
requirements. Performance metrics taken into consideration increase until packet discards and losses consequently follow.
concern latency, number of transmissions and packet loss Roughly speaking, system instability conditions are reached.
probability. The respective definitions are better detailed in the
1) Hierarchical two-tier architecture with single-hop WSN
following.
As mentioned in section V.A the concurrent simulation of
The latency is intended on a per packet basis. The latency two (or more) different technologies is not possible in ns-2,
of a packet is defined as the time period elapsed from the which does not conceive multi-radio devices. The trick to
instant when the packet is generated at the application layer of elude the problem is based on the idea to decompose the
the source node to the instant when the same packet is analysis, by simulating earlier the IEEE 802.15.4 section of the
delivered to the application layer of the final recipient node. In network and, subsequently, the Wi-Fi part which, in some way,
ns-2, these two time instants are associated with two specific receives the output of the IEEE 802.15.4 simulation as its own
events, marked as AGT (agent) and logged in the trace file input.
available at the end of the simulation, when an enough large
At the bottom tier, an IEEE 802.15.4 network rules a single
number of packets will be collected. A pdf (probability
coach. The simulations have been carried out with the standard
distribution function) of latencies can then be built by suitably
parameters set in ns-2 for the IEEE 802.15.4 communication
dividing into disjointed sub-intervals (bins) the range of
technology. The node transmission power has been set to make
experienced latencies. Statistical moments like mean value
each sensing node in the sink node radio coverage thus
(first order) and variance (correlated with the second order) can
enabling a star topology. Any sensing node is representative for
be calculated.
all the other network nodes in terms of average performance.
Similarly to the latency, the number of transmissions is a
If TI is set equal to 0.4 seconds the aggregate network
metric associated with a single packet. It is defined as the total
packet loss probability is negligible: 0.001. Very rare loss
number of transmissions a packet has experienced from the
events are reasonably caused by some queues overflow or
first transmission by the original source node to the final
temporary node overload, such that some packet is dropped or
delivery to the sink node. In the most general scenario, a multi-
not received. Fig. 6 and Fig. 7 respectively display the pdf of
hop network where packet losses can occur on a link basis, a
latency and number of transmissions, aggregated on all sensing
new transmission can happen due to two different reasons. If
nodes. The latency is very low although extremely rare samples
the MAC layer supports link-based acknowledgments and
up to around 3000 milliseconds occur, but are cut in the plot to
consequent retransmissions, as it happens for IEEE 802.15.4, a
better display the part of the curve where the 99.9% of samples
transmission can be triggered by a Time-Out expiration.
are concentrated. The number of transmissions is more
However, even the forwarding of a packet by an intermediate
frequently equal to one, rare retransmissions events are
node along the route from source to sink node represents a new
coherent with the negligible but not null packet loss
packet transmission.
probability.
The third performance metric, packet loss probability, is
Fig. 8 is a latency curve with the same semantics as Fig. 6
defined, for each end-to-end pair of source-destination (the
but specifically referring to sensing node 1, the furthest from
latter is always the sink node), as the ratio between the number
the sink node (see Fig. 5). The plot shows that retransmissions
of data packets originally generated by the source node but
occasionally occur causing longer latencies. Nonetheless, as
never delivered to the sink node and the total number of data
expected for a star topology, the performance of a sensing node
packets originally generated by the source node. Differently
is in line with the network aggregate performance. The same
from the two previous metrics, just a single probability value
holds for the number of transmissions, not reported here.
can be computed for each sensing node at the end of a
simulation. Aggregation is clearly possible, thus resulting in
network-based packet loss probability with respect to the many
per node-based packet loss probabilities.
Network: Latency for received packets node. Concerning the number of transmissions, Fig. 10
0.5
witnesses a decreasing rate following a negative exponential
0.45
fall where values from 1 to 5 are remarkable.
0.4
Sensing node 1, the most distant from the sink node,
0.35
experiences high latency values, quite commonly reaching 2
0.3 seconds and sometimes overpassing the barrier of 4 seconds.
The related graph is omitted since quite specular to the
pdf
0.25
0.2
correspondent network aggregate. Similar comments regard the
number of transmissions.
0.15
Network: Latency for received packets
0.1
0.05 0.6
0
0 5 10 15 20 25 30 35 40 45 50
0.5
Latency (ms)
0.4
Fig. 6. Star topology TI = 0.4 s Aggregated latency.
pdf
0.3
Network: Transmissions (including the first) for received packets
1
0.2
0.9
0.8
0.1
0.7
0
0.6 0 1000 2000 3000 4000 5000 6000
Latency (ms)
pdf
0.5
0.4
Fig. 9. Star topology TI = 0.1 s Aggregated latency.
0.3
Network: Transmissions (including the first) for received packets
0.2 1
0.1 0.9
0 0.8
1 2 3 4 5
Transmissions 0.7
0.6
Fig. 7. Star topology TI = 0.4 s Aggregated number of transmissions.
pdf
0.5
0.3 0.2
0.1
0.25
0
1 2 3 4 5 6 7 8 9
0.2 Transmissions
pdf
0.15
Fig. 10. Star topology TI = 0.1 s Aggregated number of transmissions.
0.1
2) Hierarchical two-tier architecture with multi-hop WSN
0.05 A mesh topology inside a coach is forced when not all of
the sensing nodes lie in the radio coverage range of the sink
0
0 10 20 30 40 50 60 node. In ns-2, this scenario can be easily achieved by setting
Latency (ms) the transmission power smaller than the threshold value which
guarantees a star topology. The communication among sensing
Fig. 8. Star topology TI = 0.4 s Node 1 latency. nodes and the sink deployed in the same coach exploits multi-
hop routing protocols like AODV [8], whose implementation is
Reducing TI to 0.1 seconds brings to a proportional made available in ns-2. It is worth noting that, in presence of a
increase of the traffic load. The tangible effect is an aggregate mesh topology, the number of transmissions experienced by a
packet loss probability reaching the impacting value of 0.454. packet results from two distinct events: retransmissions driven
Fig. 9 shows that, not so infrequently, some latency values are by link losses or packet discard at queues; and, packet
extremely high, comprised between 1 and 3 seconds, forwarding at intermediate relay nodes in accordance with
sometimes even larger. Very often, this is the result of long multi-hop routing.
queues and consequently long waiting/service time locally at a
Similarly to what happens with the star topology scenario, 1, relate to received packets only, in this scenario just a
the traffic load in correspondence of TI equal to 0.4 seconds is minority. The performances strictly depend on the node
not high enough to overload the system. The average packet position. Packets generated by sensing node 1 experience 4 to 6
loss probability is again negligible, specifically equal to 0.003. transmissions, responsible for the particular shape of the
As reported in Fig. 11 the latency samples are mostly latency pdf, resembling a uniform distribution on specific short
concentrated in the interval [0;50] milliseconds and just a ranges of values, probably due to network mechanisms that
minor part of them is comprised between 25 and 50 make periodical some impacting events (see Fig. 15).
milliseconds. However some isolated sample suffers from
Network: Latency for received packets
latencies even close to 500 milliseconds. Fig. 12 shows that
almost half of the packets needs just one transmission, while
one or two additional transmissions occur on the average for 0.25
the remaining 50% of packets.
0.2
Network: Latency for received packets
0.7
pdf
0.15
0.6
0.5 0.1
0.4 0.05
pdf
0.3
0
0 5 10 15
Latency (ms)
0.2
0.7
Network: Transmissions (including the first) for received packets
1 0.6
pdf
0.9 0.5
0.8 0.4
0.7 0.3
0.6 0.2
pdf
0.5 0.1
0.4 0
1 2 3 4 5 6 7 8 9
0.3 Transmissions
0.2
Fig. 14. Mesh topology TI = 0.1 s Aggregated number of transmissions.
0.1