外文文獻(xiàn)翻譯-基于ZigBee的車內(nèi)無(wú)線傳感器網(wǎng)絡(luò)【中文6400字】 【PDF+中文WORD】,中文6400字,PDF+中文WORD,外文文獻(xiàn)翻譯-基于ZigBee的車內(nèi)無(wú)線傳感器網(wǎng)絡(luò)【中文6400字】,【PDF+中文WORD】,外文,文獻(xiàn),翻譯,基于,ZigBee,無(wú)線,傳感器,網(wǎng)絡(luò),中文,6400 See discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/224719440 ZigBee-based Intra-car Wireless Sensor Network Conference Paper · July 2007 DOI: 10.1109/ICC.2007.653 · Source: IEEE Xplore CITATIONS 36 READS 216 6 authors, including: Cem Saraydar General Motors Company 33 PUBLICATIONS 2,191 CITATIONS A. Macdonald General Motors Company 5 PUBLICATIONS 182 CITATIONS All content following this page was uploaded by Cem Saraydar on 22 May 2014. The user has requested enhancement of the downloaded file. SEE PROFILE SEE PROFILE O.K. Tonguz Carnegie Mellon University 265 PUBLICATIONS 6,999 CITATIONS SEE PROFILE This full text paper was peer reviewed at the direction of IEEE Communications Society subject matter experts for publication in the ICC 2007 proceedings. ZigBee-based Intra-car Wireless Sensor Network Hsin-Mu Tsai1, Cem Saraydar2, Timothy Talty2, Michael Ames2, Andrew Macdonald2, and Ozan K. Tonguz1 1 Carnegie Mellon University, ECE Department, Pittsburgh, PA 15213-3890, USA 2 General Motors Corporation, ECI Lab, Research and Development, Warren, MI 48092-2031, USA Email: {hsinmut, tonguz}@ece.cmu.edu, {cem.saraydar, timothy.talty, michael.ames, andrew.macdonald}@gm.com Abstract— Due to an increasing number of sensors deployed in cars, recently there is a growing interest in implementing a wireless sensor network within a car. In this paper, we report the results of packet transmission experiments using ZigBee sensor nodes within a car under various scenarios. The results of the experiments suggest that both Received Signal Strength Indicator (RSSI) and Link Quality Indicator (LQI) can only be used as a threshold-based indicator to evaluate the link quality - indicating poor link quality when dropping below a certain threshold. Preliminary experimental results show that a detection algorithm developed by the authors based on RSSI/LQI/error patterns and an adaptive strategy might increase the goodput performance of the link while improving power consumption of the radio. I. INTRODUCTION Wireless sensor networks have been implemented in various monitoring applications such as industrial, health, environmen- tal, security, etc. Recently, vehicular applications have entered the list of applications, mainly through tire pressure monitoring systems. More widespread use of wireless sensors in a vehicle will result from one or more of several different factors including difficulty with wired sensing and cost reduction opportunity. Fueled by the emerging interest in the industry for deploying a higher number of wireless sensors, there is a need to understand and characterize the wireless channel within a vehicle. To this end, we report a case study using wireless sensor nodes that are compliant with ZigBee. ZigBee is an industry alliance that promotes a set of rules which builds on top of the IEEE 802.15.4 standards [1]. Channel behavior under various scenarios is observed for ZigBee nodes placed throughout a midsize sedan. To the best of our knowledge this paper presents the first attempt to characterize ZigBee performance within a vehicle environment. The rest of the paper is organized as follows. In section II, the details of the experimental setup are described. The results of the experiments and the discussions of these results are presented in section III. In section IV, we propose a set of detection algorithms and an adaptive strategy that can adjust to channel conditions for improving the error performance of the wireless channel and preliminary evaluation results are presented. Finally, the concluding remarks are given in section V. II. EXPERIMENTAL METHOD A. Sensor node hardware In our experiments, we use Crossbow MPR2400 [2] as our sensor node hardware platform. The specifications are shown in Table I.  Fig. 1. The block diagram of the experimental setup B. Experimental setup and sensor node firmware Figure 1 shows the experimental setup. In the experiment, sensor nodes (SN) are placed in different locations in the vehicle. The base station (BS) is placed inside the instrument panel of the vehicle, next to the vent. The base station is connected to a MIB510 programmer and a RS-232 to USB converter is used to connect the laptop and MIB510. The sensor nodes periodically retrieve sensor information from the attached sensors and send (broadcast) sensor packets to the base station. The base station acts as a bridging device between the sensor nodes and the laptop, relaying the sensor packets from sensor nodes to the laptop and the command packets from the laptop to sensor nodes, as well as logging various metrics such as Received Signal Strength Indicator (RSSI), Link Quality Indicator (LQI), CRC, etc., and append- ing them to each received packet. The packet logger/parser software in the laptop processes the packets sent by the base station, and saves them to a log file for further analysis. The command sender in the laptop can be used to issue commands to adjust the parameters of sensor nodes such as transmitting power, packet sending rate, etc. The firmware of sensor nodes and the base station is based on TinyOS 1.1.15 [3]. TinyOS is an open source component- based operating system and platform targeting wireless sensor networks. Our implementations use various API and libraries provided by TinyOS. 1-4244-0353-7/07/$25.00 ?2007 IEEE TABLE I CROSSBOW MPR2400 (MICAZ) SPECIFICATION TABLE III EXPERIMENTAL SCENARIOS Parameter Value/Description Processor ATMega 128L Processor Radio Chip Chipcon CC2420 Radio Operating Frequency 2.4 GHz Effective Data Rate 250 Kb/s Modulation Format Offset Quadrature Phase-Shift keying (OQPSK) Scenario No. Location Driver Engine 1 Maintenance Garage Present ON 2 Maintenance Garage Not Present OFF 3 Corporate Parking Lot Present ON 4 Corporate Parking Lot Not Present OFF 5 On the road Present ON TABLE II SENSOR NODE LOCATIONS IN THE CAR Node No. Location B Embedded in the instrument panel, next to the vent 6 On the dashboard, next to the light sensor 7 On the right side of the trunk, next to the stability actuator 1 In the engine compartment, next to the fuse box 0 In front of the radiator, between the temperature sensor and the air quality sensor C. Sensor node locations The vehicle used in the experiment is a General Motors 2005 Cadillac STS. Figure 2 and Table II show the locations of the sensor nodes as well as the base station in the vehicle. D. Experimental scenarios We performed different experiments under various scenarios shown in Table III. The details of these scenarios are discussed in the following. 1) Location a) Maintenance garage This is similar to the service depot of a regular car dealer. Technicians walk by frequently and several other cars are parked nearby. There are a lot of service equipments in the garage. b) Corporate parking lot This is a regular corporate parking lot. The test vehicle was parked in one of the parking space and surrounded by other cars. Pedestrians passed by the test vehicle sometimes. Fig. 2. Sensor node locations in the car. The numbers in the circles are showing the number of the sensor node. See Table II for descriptions.  Nearby vehicles sometimes moved in or out of the parking lot. c) Road This is the driving scenario. The car was driven on the highway most of the time and some- times on large (multiple-lane) local roads. 2) Driver In “driver present” scenarios, the driver was sitting in the car and has frequent movements, such as operating A/C, radio, steering wheel, etc. In “driver not present” scenarios, the driver’s seat was empty. 3) Engine In “engine on” scenarios, the engine was started and kept running throughout the whole measurement. The air conditioner and the radio in the vehicle were also turned on. In “engine off” scenarios, the engine was turned off (not in the accessory mode) and the key was removed from the vehicle. E. Communication parameters ? Transmitting power: In the experiment, we set the trans- mitting power of the sensor nodes to be at 5 different levels: 0, -5, -10, -15, and -25 dBm. The transmitting power of the base station was fixed at 0 dBm (The base station only transmits when sending commands to sensor nodes). ? Packet sending rate: We configured the sensor node to send a sensor packet every 100 ms. This sending rate is sufficient for non-safety sensors in the vehicle. ? Channel selection: The physical layer standard of MI- CAz nodes follows IEEE 802.15.4 standard [4]. Since 802.11b/g devices are the most common devices in 2.4 GHz ISM band and are likely to create a lot of interfer- ence, we select a channel that is away from the bandwidth occupied by 802.11b/g standard. The bandwidth used by 802.11b/g and 802.15.4 devices are 3 MHz and 22 MHz, respectively. In our experiment, we configured the sensor nodes to use channel 26 (2480 MHz) to avoid interference from 802.11b/g devices. In this case, the closest 802.11b/g channel is channel 11 (2462 MHz) and does not overlap with our 802.15.4 channel. ? Packet format: Figure 3 shows the sensor packet format used in the experiment. The total size of MAC Protocol Data Unit (MPDU) plus the frame length field is 31 bytes. Note that most of the fields in the application level payload are used to record the information for the experiments. For example, we used 12 bytes to record the sensor information, as well as 1 byte each to record transmitting power and version number of the firmware. The size of the sensor packet can be reduced by removing Fig. 3. Sensor packet format (the number above each field represent the size of the field in byte) [5] unnecessary fields and results in a lower packet error rate. Depending on applications, the size of the sensor information field can also be reduced. ? Node transmissions: In the experiments conducted, only one of the sensor nodes transmitted at a time. We used this setting to avoid interference from other sensor nodes and focus on measuring the link quality. ? MAC related parameters: In the experiment, we disabled the automatic ACK feature, as well as the retransmissions. The sensor nodes use a MAC protocol similar to the Car-  ? Cyclic Redundancy Check (CRC) field Chipcon CC2420 radio chip has automatic CRC checking capability and TinyOS has a CRC field in its radio packet indicating whether the packet received pass the CRC checking. The CRC scheme used in CC2420 is CRC-16 (ITU-T). G. Definitions of metrics In this sub-section, we define the metrics used later. First we define the following variables: ? G 全 The number of packets received by the base station and passed the CRC check. ? LE 全 The number of packets received by the base station and either the length of the packet or the type of the packet (indicated by the type field) was not correct. ? CE 全 The number of packets received by the base station and failed the CRC check. ? A 全 The total number of packets transmitted Note that our packet parser will first detect length/type errors. If the length/type of the packet is not correct, it will be put into LE category. The CRC field of these packets might indicate that it is in error, but these will not be included in CE. Now we define the following error-related performance metrics using the above variables: ? Packet Reception Rate (PRR): G + LE + CE rier Sense Multiple Access (CSMA) used in 802.11b/g, in which it will wait until the channel is clear (perform clear channel assessment) and then start transmitting. PRR = ? Packet Error Rate (PER): (1) A ? Data collection: For each scenario/transmitting power/sensor node, we configured the sensor node to transmit 6000 sensor packets, which took 10 minutes. The total time to complete the data collecting process  ? Goodput: PER = LE + CE G + LE + CE G (2) for each scenario was around 200 minutes. F. Observable entities The following describes various observable entities recorded by the base station. ? Link Quality Indicator (LQI) LQI is calculated by Chip- con CC2420 radio chip and is actually Chip Correlation Indicator (CCI). It is related to the chip error rate. LQI ranges from 50 to 110 and is calculated over 8 bits following the start frame delimiter. ? Received Signal Strength Indicator (RSSI) RSSI is mea- sured by Chipcon CC2420 radio chip and represents the amount of energy received by the sensor node. According to [5], RSSI has a range from -100 dBm to 0 dBm and the maximum error (accuracy) is 6 dB. The RSSI is calculated over 8 symbol periods. ? Sequence Number In the sensor data packet, there is an application-level sequence number field which will be increased each time the sensor node sends out a packet. This can be used by the base station to detect a lost packet. Goodput = (3) A H. Experiment for understanding the impact of Bluetooth To study how the existence of an interference source can im- pact the performance of the ZigBee sensor nodes, we used the integrated Bluetooth hands-free in the Cadillac and a Motorola RAZR V3 cell phone to create interference. We performed the experiment with and without the Bluetooth interference in scenario no. 3 in Table III (with limited Bluetooth data set; each node transmitted using only one transmitting power setting). In the experiment with Bluetooth interference, the cell phone was used to place a phone call and maintain a Bluetooth connection with the hands-free during the whole experiment period. The Bluetooth protocol uses a Frequency Hopping Spread Spectrum (FHSS) mechanism. It hops to one of the available channels every 0.625 ms according to a hopping sequence specified by the master node. The Bluetooth standard used in U.S. has 79 1-MHz-wide channels spread from 2402 MHz to 2480 MHz. Hence, the last two channels will overlap with the 802.15.4 channel (2479 MHz) used in our experiment and will create interference to the sensor nodes. Node 6 Node 7 Node 1 Node 0 Receive Sensitivity (?94 dBm) 100 90 Channel Loss (dB) 80 70 60 50 40 ?30 ?25 ?20 ?15 ?10 ?5 0 5 Transmitting Power (dBm) Fig. 4. Channel loss of the channels to all sensor nodes. The error bars show one standard deviation from the mean. III. EXPERIMENTAL RESULTS AND DISCUSSION In this section, we present the experimental results and discuss the implications of these results. A. Channel loss The attenuation of signal strength experienced as the signal propagates from the transmitter antenna to the receiver antenna is referred to as channel loss and it is typically measured in decibels (dB): CL(dB)= Ptransmitted ? Preceived (4) Note that CL includes the antenna gains. The channel loss depends on a complex set of factors, including the distance between the transmitter-receiver pair and the type of medium along the path between the transmitter and the receiver. The location of each of our wireless sensors identifies a channel between the base station node and the corresponding wireless sensor node. As seen in Figure 4, the best channel among the four that were measured in our experiments is the channel to node 6 on the dashboard (next to the twilight sensor) whereas the worst channel has been observed as the channel to node 0 in front of the radiator (between the air quality sensor and the ambient temperature sensor). Since we fix the locations of our wireless sensor nodes, ideally the channel loss curve should be a flat line (independent from the transmitting power) for each channel. However, it can be observed from our results that for low transmit power values, especially for the channel to node 0, channel loss seems to be decreasing! Such a result appears to be counter-intuitive, however a careful consideration of the circumstances reveals that if the channel loss is large and transmitting power level is sufficiently low, the received power level will be lower than the receive sensitivity of the receiver hardware most of the time and will not be received successfully. Without these high  channel loss packets, the average channel loss is higher than the expected value. Observe from Figure 4 that insufficient amount of data and statistical effects result in some variations of the channel loss curves, as opposed to perfectly flat lines. B. Error metrics and RSSI profiles The receive sensitivity of the radio chip in the sensor nodes is -95 dBm (typical) and -90 dBm (minimum), as specified by [5]. The sensitivity corresponds to the minimum received signal strength beyond which the packet error rate exceeds 1%, as defined in [4]. To study the relation between various error metrics and RSSI, we computed the plots as follows. Each 6000-packet sequence of one setting was split to segments of 50 consecutive packets. For each of the segments, error metrics were calcu- lated over these 50 packets, which is represented by y. The mean of the RSSIs of these 50 packets were also calculated and represented by μx. Then we plot the point with coordinate (μx, y) on the figure to represent this segment, and repeat this procedure with all segments in this setting, and all the data of other settings. Figure 5(a)-(e) shows the profiles of PRR versus RSSI for each of the scenarios. Figure 6 and Figure 7 show the profiles of 1-PER and Goodput versus RSSI, respectively. In Figure 5, one can observe that, in agreement with the specified receive sensitivity, the PRR drops from 1 to 0 within the range -91 to -94 dBm. The outliers that violate this general observation are due to external effects such as driver movement within the cabin, interference from other wireless devices, etc. For instance, 802.11b/g access points are deployed in the maintenance garage in scenario no. 1 and 2, which is configured to operate on channel 11, which is rather close to the frequency band the wireless nodes operate at. As a result of such effects, the receive sensitivity boundary experiences slight shifts to the right of the figure, representing a less “friendly” propagation environment. One can also observe that the trunk data manifests a higher level of fluctuations (more outliers), possibly due to the rich multipath environment caused by the presence and the motion of the passenger along the direct path that lies between the sensor node and the base station node. In Figure 6, we observe that in scenarios where the engine is on or the driver is present, there is a higher noise level which leads to poorer PER performance. We also observe that there are fewer outliers as compared to the results in Figure 5, which could be explained by a relatively lower impact of the driver or the engine noise on the correlation between PER and RSSI. In Figure 7, one can also observe that the goodput performance is good only when RSSI is much larger than the received sensitivity boundary. C. Error metrics and LQI profiles In Figure 8, we calculate the mean (μx) and the standard deviation (σx) of the LQIs of the 50 packets in a segment. Then we plot the points (μx - σx, y) and (μx + σx, y), and connect these two points with a line to represent this segment and repeat the procedure for all other segments. Scenario 1 Node 6 Node 7 Node 1 Node 0 Receive Sensitivity 1 Scenario 2 Node 6 Node 7 Node 1 Node 0 Receive Sensitivity 1 Scenario 3 Node 6 Node 7 Node 1 Node 0 Receive Sensitivity 1 0.8 0.8 0.8 PRR PRR PRR 0.6 0.6 0.6 0.4 0.4 0.4 0.2 0.2 0.2 0 ?100 ?90 ?80 ?70 ?60 ?50 ?40 RSSI (dBm) 0 ?100