21.01.2014 Views

Structural Health Monitoring Using Smart Sensors - ideals ...

Structural Health Monitoring Using Smart Sensors - ideals ...

Structural Health Monitoring Using Smart Sensors - ideals ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ecords is not necessarily efficient for single packet transfer. Communication protocol for<br />

long data records and single packets are, therefore, designed separately.<br />

In the SHM architecture employed in this research, most communication takes place<br />

inside a smart sensor cluster as unicast or multicast. Unicast is communication between<br />

one sender and one receiver, while multicast is communication from one sender to<br />

multiple receivers. Both unicast and multicast protocols are, therefore, developed for long<br />

data records and for short message communication. Communication protocols developed<br />

in this chapter suffice for most communication requirements in DCS for SHM with the<br />

exception being communication involved in time synchronization.<br />

1. Communication protocol for long data records<br />

Communication protocols suitable to transfer long data records reliably are<br />

developed. The length of data assumed in this section is the acceleration record length<br />

used in DCS. The first step of DCS estimates the CSD using FFT. The estimation is<br />

frequently based on 10 to 20 times the number of data points used in the FFT. Assuming<br />

the number of FFT points is 1,024, the target length of data to be transmitted is set as<br />

11,264.<br />

Though repeated data transmission without acknowledgment can statistically improve<br />

the reliability of communication, such protocols cannot guarantee communication success<br />

rate deterministically. If the packet loss rate is expected to be approximately constant over<br />

long time, repeated sending practically results in no data loss; the number of repetitions<br />

can be dynamically adjusted based on the packet loss rate of the last communication.<br />

When many packets are lost statistically, the number of repetitions can be increased.<br />

However, in smart sensor networks, burst packet loss may take place. RF transmission<br />

devices nearby, for example, may cause the large number of communication packets to be<br />

dropped. The fluctuation in packet loss rate is considered large, as shown in Figure 5.11.<br />

Repeated transmission is not a sufficient solution to the packet loss problem.<br />

Acknowledgment packets potentially guarantee reliable communication between<br />

nodes. However, a poorly-designed communication protocol involving acknowledgment<br />

messages can be notably inefficient. Many acknowledgment messages may be required,<br />

waiting times may be long, and the same packets may need to be sent many times. With<br />

careful consideration of efficiency, reliable communication protocols are realized in this<br />

section using acknowledgment messages. These protocols are similar to error control<br />

methods for data transmission, which are briefly reviewed and then modified for use in the<br />

proposed reliable communication protocol for SHM applications.<br />

Automatic Repeat reQuest (ARQ) is an error control method which repeats sending<br />

packets based on the request from the receiver. On reception of packets without error, the<br />

receiver replies with a positive acknowledgment (ACK). If an error is detected, the<br />

receiver sends a negative acknowledgment (NACK) and requests retransmission. There<br />

are several ARQ protocols, some of which are described in the following paragraphs.<br />

In the stop-and-wait protocol, the sender waits for an acknowledgment after the<br />

transmission of each packet. If an ACK is received, the sender transmits the next packet.<br />

63

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!