<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors</journal-id>
<journal-title>Sensors</journal-title>
<issn pub-type="epub">1424-8220</issn>
<publisher>
<publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name></publisher></journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3390/s100706307</article-id>
<article-id pub-id-type="publisher-id">sensors-10-06307</article-id>
<article-categories>
<subj-group>
<subject>Article</subject></subj-group></article-categories>
<title-group>
<article-title>EMMNet: Sensor Networking for Electricity Meter Monitoring</article-title></title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Lin</surname><given-names>Zhi-Ting</given-names></name><xref ref-type="aff" rid="af1-sensors-10-06307"><sup>1</sup></xref><xref ref-type="aff" rid="af2-sensors-10-06307"><sup>2</sup></xref><xref ref-type="corresp" rid="c1-sensors-10-06307">*</xref></contrib>
<contrib contrib-type="author">
<name><surname>Zheng</surname><given-names>Jie</given-names></name><xref ref-type="aff" rid="af1-sensors-10-06307"><sup>1</sup></xref><xref ref-type="aff" rid="af2-sensors-10-06307"><sup>2</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Ji</surname><given-names>Yu-Sheng</given-names></name><xref ref-type="aff" rid="af3-sensors-10-06307"><sup>3</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Zhao</surname><given-names>Bao-Hua</given-names></name><xref ref-type="aff" rid="af1-sensors-10-06307"><sup>1</sup></xref><xref ref-type="aff" rid="af2-sensors-10-06307"><sup>2</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Qu</surname><given-names>Yu-Gui</given-names></name><xref ref-type="aff" rid="af1-sensors-10-06307"><sup>1</sup></xref><xref ref-type="aff" rid="af2-sensors-10-06307"><sup>2</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Huang</surname><given-names>Xu-Dong</given-names></name><xref ref-type="aff" rid="af4-sensors-10-06307"><sup>4</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Jiang</surname><given-names>Xiu-Fang</given-names></name><xref ref-type="aff" rid="af1-sensors-10-06307"><sup>1</sup></xref><xref ref-type="aff" rid="af2-sensors-10-06307"><sup>2</sup></xref></contrib></contrib-group>
<aff id="af1-sensors-10-06307">
<label>1</label> School of Computer Science and Technology, University of Science and Technology of China, Hefei, Anhui 230027, China; E-Mails: <email>zhengms@mail.ustc.edu.cn</email> (J.Z.); <email>bhzhao@ustc.edu.cn</email> (B.-H.Z.); <email>ygqu@ustc.edu.cn</email> (Y.-G.Q.); <email>suphone@mail.ustc.edu.cn</email> (X.-F.J.)</aff>
<aff id="af2-sensors-10-06307">
<label>2</label> The State Key Laboratory of Networking and Switching Technology, Beijing, 100876, China</aff>
<aff id="af3-sensors-10-06307">
<label>3</label> National Institute of Informatics, Tokyo, 101-8430, Japan; E-Mail: <email>kei@nii.ac.jp</email> (Y.-S.J.)</aff>
<aff id="af4-sensors-10-06307">
<label>4</label> Hangao Electronics Co., Ltd. Anhui, China; E-Mail: <email>huangxudong1227@163.com</email> (X.-D.H.)</aff>
<author-notes>
<corresp id="c1-sensors-10-06307">
<label>*</label> Author to whom correspondence should be addressed; E-Mails: <email>ztlin@mail.ustc.edu.cn</email>; Tel.: +86-0551-03607462; Fax: +86-0551-03607462.</corresp></author-notes>
<pub-date pub-type="collection">
<year>2010</year></pub-date>
<pub-date pub-type="epub">
<day>24</day>
<month>6</month>
<year>2010</year></pub-date>
<volume>10</volume>
<issue>7</issue>
<fpage>6307</fpage>
<lpage>6323</lpage>
<history>
<date date-type="received">
<day>11</day>
<month>5</month>
<year>2010</year></date>
<date date-type="rev-recd">
<day>27</day>
<month>5</month>
<year>2010</year></date>
<date date-type="accepted">
<day>6</day>
<month>6</month>
<year>2010</year></date></history>
<permissions>
<copyright-statement>© 2010 by the authors licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2010</copyright-year>
<license>
<p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (http://creativecommons.org/licenses/by/3.0/).</p></license></permissions>
<abstract>
<p>Smart sensors are emerging as a promising technology for a large number of application domains. This paper presents a collection of requirements and guidelines that serve as a basis for a general smart sensor architecture to monitor electricity meters. It also presents an electricity meter monitoring network, named EMMNet, comprised of data collectors, data concentrators, hand-held devices, a centralized server, and clients. EMMNet provides long-distance communication capabilities, which make it suitable suitable for complex urban environments. In addition, the operational cost of EMMNet is low, compared with other existing remote meter monitoring systems based on GPRS. A new dynamic tree protocol based on the application requirements which can significantly improve the reliability of the network is also proposed. We are currently conducting tests on five networks and investigating network problems for further improvements. Evaluation results indicate that EMMNet enhances the efficiency and accuracy in the reading, recording, and calibration of electricity meters.</p></abstract>
<kwd-group>
<kwd>smart sensor</kwd>
<kwd>electricity meter monitoring</kwd>
<kwd>dynamic tree protocol</kwd>
<kwd>application</kwd></kwd-group></article-meta></front>
<body>
<sec sec-type="intro">
<label>1.</label>
<title>Introduction</title>
<p>Power line networking devices were developed decades ago for automatic electricity-meter monitoring. Any electronic device connected to an electrical power line can use this technology for data communications without additional wiring. However, this use remains on the sidelines due to problems with quality of service, low data rates, range limitations, interoperability, and high cost. Recently, industries have provided remote reading for electricity meters via wireless connectivity, such as CDMA, GPRS, and PHS, using various radio spectra. These solutions are generally limited to peer-to-peer and one-level communication architectures [<xref ref-type="bibr" rid="b1-sensors-10-06307">1</xref>]. When subjected to different user environments, they face various challenges. Therefore, we have developed an electricity meter monitoring network (EMMNet) based on heterogeneous smart sensor networks.</p>
<p>According to the classification given by Rivera <italic>et al</italic>. a smart sensor includes certain functionalities such as processing, communication and integration [<xref ref-type="bibr" rid="b2-sensors-10-06307">2</xref>]. The smart sensor is emerging as a promising technology in a large number of application domains. For instance, Granados <italic>et al</italic>. [<xref ref-type="bibr" rid="b3-sensors-10-06307">3</xref>] developed a smart sensor for real-time high-resolution frequency estimation in power systems. Their proposed smart sensor uses the chirp z-transform to compute the power spectrum and utilizes a commercially available current clamp, a Hall-effect sensor or a resistor as the primary sensor. Rodriguez-Donate <italic>et al.</italic> [<xref ref-type="bibr" rid="b4-sensors-10-06307">4</xref>] presented a novel smart sensor to estimate motion dynamics, inclination, and vibration parameters on industrial manipulator robot links based on two primary sensors: an encoder and a triaxial accelerometer. Trejo-Hernandez <italic>et al.</italic> [<xref ref-type="bibr" rid="b5-sensors-10-06307">5</xref>] developed a fused smart-sensor in order to improve the online quantitative estimation of flank-wear area in CNC machine inserts, from the information provided by primary sensors such as the monitoring current output of a servoamplifier and an accelerometer. Son <italic>et al.</italic> [<xref ref-type="bibr" rid="b6-sensors-10-06307">6</xref>] developed a smart sensor system to acquire three types of signals involving vibration, current, and flux from induction motors. This system consisted of four modules: sensor, interface, server, and fault diagnosis module. The authors claimed that the smart sensor system can replace expensive traditional sensors for fault testing of induction motors.</p>
<p>In most applications, a smart sensor node is expected to acquire some physical measurements, perform local processing and storage, and communicate within a short distance [<xref ref-type="bibr" rid="b7-sensors-10-06307">7</xref>–<xref ref-type="bibr" rid="b9-sensors-10-06307">9</xref>]. The ability to communicate not only allows information and control to be communicated across the network, but also enables nodes to cooperate in performing more complex tasks, such as statistical sampling, data aggregation, and system status monitoring [<xref ref-type="bibr" rid="b10-sensors-10-06307">10</xref>].</p>
<p>Although sensor network platforms already exist, for electricity meter monitoring we have to design an entirely new system because a meter-monitoring scenario has specific requirements. First, wireless access is very challenging in urban environments, where electricity meters in tall buildings are often installed in a metal chest and separated by concrete walls. Most of the existing platforms can only provide very short-distance communication in this environment. We find that they cannot satisfy our requirements, through field measurement. Second, none of the existing platforms conform to the China National Standard for automatic electricity-meter monitoring. The radio frequency band is specifically designated to 470–510 MHz [<xref ref-type="bibr" rid="b11-sensors-10-06307">11</xref>]. Finally, the nodes, which are called data collectors in the automatic electricity meter-reading field, need to be connected to electricity meters. Thus, we should consider safety factors in the node layout. In light of such needs, we present EMMNet, an integrated sensor environment for remote electricity meter monitoring. EMMNet is composed of data collectors, data concentrators, hand-held devices, a centralized server, and clients. The novelty of this work is the development of a smart sensor for real-time electricity meter monitoring. In addition, our EMMNet has following features compared with other existing remote meter monitoring systems:
<list list-type="bullet">
<list-item>
<p>Dedicated design of radio-frequency (RF) circuit. Application of automatic electricity meter monitoring faces various challenges, such as tall buildings in urban areas, long distances in suburban regions, and signal interference. However, the indoor communication range of the most typical sensor network platforms is about 25 m and this distance cannot meet the requirements of electricity meter monitoring. Therefore, we added broadband, fixed-gain, linear amplifiers, and low noise amplifiers to the data collectors and the data concentrators. A data concentrator is equivalent to a base station or gateway in sensor networks.</p></list-item>
<list-item>
<p>High reliability and performance. Some existing automatic meter monitoring systems utilize ZigBee [<xref ref-type="bibr" rid="b12-sensors-10-06307">12</xref>], which is a specification for a suite of high level communication protocols for wireless personal area networks. But ZigBee can only operate in three radio bands, which limits its applications. A high-performance dynamic tree (DT) protocol is proposed in this paper. It is based on CSMA/CA and has no frequency limit. Even if some nodes (data collectors) lose their connection frequently because of environmental changes, other nodes can quickly repair the routes.</p></list-item>
<list-item>
<p>Low operational cost. Compared with other existing remote meter monitoring systems based on GPRS [<xref ref-type="bibr" rid="b13-sensors-10-06307">13</xref>], the operational cost of EMMNet is relatively low because only the data concentrators incur in costs for using GSM/GPRS network.</p></list-item>
<list-item>
<p>Changeability. China Power System is currently being reconstructed, and the requirements of the automatic electricity-meter-reading system change from time to time. Data collectors and data concentrators in EMMNet support wireless reprogramming, which can satisfy customer requirements in a timely manner.</p></list-item></list></p></sec>
<sec>
<label>2.</label>
<title>Existing Sensor Network Platforms</title>
<p>Recently, a number of sensor network platforms have been proposed. <xref ref-type="table" rid="t1-sensors-10-06307">Table 1</xref> compares the prices and features of our EMMNet and some typical systems. The MICA2 mote is a third-generation mote module used for enabling low-power wireless sensor networks. It is supported by the MoteWorks wireless sensor network platform for reliable <italic>ad hoc</italic> mesh networking [<xref ref-type="bibr" rid="b14-sensors-10-06307">14</xref>]. The TelosB mote is an open source platform designed to enable cutting-edge experimentation for the research community. TelosB bundles all the essentials for lab studies into a single platform, including USB programming capability, an IEEE 802.15.4 radio with integrated antenna, a low-power microprogrammed control unit (MCU) with extended memory, and an optional sensor suite (TPR2420) [<xref ref-type="bibr" rid="b15-sensors-10-06307">15</xref>]. The MICAZ is also a 2.4-GHz mote module based on the Atmel ATmega128L [<xref ref-type="bibr" rid="b16-sensors-10-06307">16</xref>]. Unlike most existing platforms, the Imote2 contains the Intel PXA271 CPU, which can operate at 13–416 MHz with dynamic voltage scaling [<xref ref-type="bibr" rid="b17-sensors-10-06307">17</xref>]. Building on the highly successful Tmote Sky, Moteiv introduced Tmote Mini, the latest generation of wireless sensor network hardware. Moteiv’s Tmote Sky and Tmote Mini platforms both combine Texas Instruments MSP430 microcontrollers with TI/Chipcon low-power radios [<xref ref-type="bibr" rid="b18-sensors-10-06307">18</xref>,<xref ref-type="bibr" rid="b19-sensors-10-06307">19</xref>]. In addition, BTnode is a versatile, autonomous wireless communication and computing platform based on a Bluetooth radio, low-power radio, and microcontroller. The low-power radio is the same as that used on the Berkeley MICA2 mote, making BTnode a twin of MICA2 [<xref ref-type="bibr" rid="b20-sensors-10-06307">20</xref>].</p>
<p>As shown in <xref ref-type="table" rid="t1-sensors-10-06307">Table 1</xref>, among all these platforms the smart sensor in EMMNet provides the longest communication distance. It is thus suitable for applications in complex urban environments, where electricity meters in tall buildings are often installed inside metal chests and separated by concrete walls. The external memory space of the data collector in EMMNet is 4 MB and that of data concentrators is 8 MB. The external memory space of EMMNet is large, because collectors and concentrators need to record the data and parameters from hundreds of electricity meters. The cost of EMMNet is also lower than that of any other platform listed in <xref ref-type="table" rid="t1-sensors-10-06307">Table 1</xref>. A dynamic power-management technique is an additonal feature of our system. This technique dynamically reconfigures the system to provide the requested services. The current draw of the processor is 8 mA in active mode, and it drops to about 30 uA while in sleep mode.</p></sec>
<sec>
<label>3.</label>
<title>System Architecture</title>
<p>EMMNet is built on a heterogeneous networking infrastructure. In the automatic electricity meter-reading field, a sensor node is usually called a data collector, and a base station or gateway in the sensor network is called a data concentrator. EMMNet involves data collection, transmission, and access phases, as shown in <xref ref-type="fig" rid="f1-sensors-10-06307">Figure 1</xref>.</p>
<p>To obtain average real power information the electricity meter utilizes an ADE7755, which is a high accuracy electrical energy measurement sensor. The error of an ADE7755 is less than 0.1% over a dynamic range of 500 to 1. The only analog circuitry used in an ADE7755 is in the ADCs and reference circuit. All other signal processing (e.g., multiplication and filtering) is carried out in the digital domain. This approach provides superior stability and accuracy over extremes in environmental conditions and over time. We connect electricity meters to data collectors via an RS485 bus. Electricity meters are installed in a metal chest, and data collectors are usually beside them for safety purposes. The sensor data in our system flow from the data collectors to a data concentrator over the DT protocol. Data can also be relayed via data collectors if the electricity meters are far from the data concentrator. The data concentrators transmit electricity meter data to the remote centralized server that provides data logging. The data is transmitted using the TCP/IP suite of protocols and therefore can be carried over types of many networks, including LAN, CDMA, and GPRS. We also propose a back-end client/server architecture to provide a user interface to the system and support further centralized processing for higher-level applications. The GUI visualization component has a graphical display that enables an overall view of the network to be shown. The visualization component also has a relation layer to display relationships between nodes and a node layer to draw the nodes themselves. Customers can access their electricity bills whenever necessary, and an administrator can check the electricity meters’ status and modify the parameters of each electricity meter if needed. Hand-held devices are also included and used as “mobile data concentrators” in the EMMNet. If any fault occurs in the fixed data concentrators, the hand-held devices can still be used to collect data in a timely manner. Hand-held devices can communicate with other devices in four different ways: 470 MHz wireless channel, IrDA, RS232, and RS485. In addition, data collectors and data concentrators can be reprogrammed by hand-held devices if the requirements of the automatic electricity-meter-reading change.</p></sec>
<sec sec-type="methods">
<label>4.</label>
<title>Hardware Design</title>
<p>EMMNet is composed of data collectors, data concentrators, hand-held devices, a centralized server, and clients. The hardware design of smart sensors will be detailed in subsequent subsections.</p>
<sec sec-type="methods">
<label>4.1.</label>
<title>Data Collector</title>
<p>Each node, also called a data collector or collector, has a microprocessor, serial interface flash memory, RF transceiver, linear amplifier, low-noise amplifier, RS-485 transceiver, and IrDA module. The basic hardware structure schematic and a photo of the data collector are shown in <xref ref-type="fig" rid="f2-sensors-10-06307">Figure 2</xref>.</p>
<p><italic>Microprocessor</italic>: Usually, one of the three microcontrollers, <italic>i.e</italic>., ATmega128L, MSP430, and Silicon Labs C8051, is used in nodes of the sensor network. After intensive investigations, we chose the ATmega128L microcontroller for our EMMNet platform, because it is a low-power microcontroller based on the AVR-enhanced Reduced Instruction-Set Computer (RISC) architecture. The ATmega128L provides the following features: 128 K bytes of in-system programmable flash with read-while-write capabilities, 4 K bytes Electrically Erasable Programmable Read-Only Memory (EEPROM), 4 K bytes static RAM (SRAM), and 53 general purpose IOs. Making rational use of the microprocessor resources, we leave ample room for expansion. At present, we have used 62.00% of the port, 34.87% of the code memory, 72.75% of the data memory and 88.23% of the EEPROM. Ports assignment is listed in <xref ref-type="table" rid="t2-sensors-10-06307">Table 2</xref>.</p>
<p><italic>RF Transceiver</italic>: We use the Nordic nRF905 transceiver because its carrier frequencies are suitable for automatic electricity meter monitoring and there is no associated proprietary protocol. Its current consumption is very low: in transmit mode, only 9 mA at an output power of −10 dBm, and in receive mode, 12.5 mA. However, EMMNet faces various challenges. Therefore, we add a broadband, fixed-gain, linear amplifier and a low-noise amplifier to the RF circuit.</p>
<p><italic>Memory</italic>: A memory bank with relatively large capacity is believed to be beneficial for data storage and buffering in EMMNet since there can be up to 100 electricity meters connected to a single data collector. Therefore, we chose the AT45DB041D, a 4-Mbit serial-interface flash memory. In addition to the main memory, the AT45DB041D also contains two SRAM buffers of 264 bytes each. In our design, we take full advantage of this external SRAM, greatly easing the problem of small SRAM in the ATmega128L.</p></sec>
<sec sec-type="methods">
<label>4.2.</label>
<title>Data Concentrator</title>
<p>The key components of the data concentrator are similar to those of the data collector. These devices can share most of the drivers and application codes, which greatly reduces the difficulty of our design and of debugging. However, the data concentrator requires more external memory because it is responsible for transmitting electricity meter data from hundreds of data collectors to the remote centralized server. A GPRS module is also added to the design of the data concentrator. Modularity is a key tenet of our design, reflected in the separation of the GPRS module and the 470 MHz wireless module on the data concentrator. The basic hardware structure is illustrated in <xref ref-type="fig" rid="f3-sensors-10-06307">Figure 3</xref>.</p>
<p><italic>Memory</italic>: We use the AT45DB642D instead of the AT45DB041D. Its 69,206,016 bits of memory are organized as 8,192 pages. In addition to the main memory, the AT45DB642D also contains two SRAM buffers of 1,056 bytes each.</p>
<p><italic>GPRS module</italic>: We chose the SIM300C for the data concentrator. The SIM300C is a tri-band GSM/GPRS engine that works in the EGSM 900 MHz, DCS 1,800 MHz, and PCS 1,900 MHz frequencies. With a tiny configuration of 50 × 33 × 6.2 mm, SIM300C meets the space requirements in our industrial application. The SIM300C is designed to have power-saving features: the current consumption is as low as 2.5 mA in sleep mode.</p></sec>
<sec>
<label>4.3.</label>
<title>Memory Arrangement</title>
<p>The ATmega128L contains 128 K bytes of in-system programmable flash with read-while-write capabilities, 4 K bytes EEPROM, and 4 K bytes SRAM. The in-system programmable flash, which is used for storing program code, does not cause a bottleneck in our design. The problem is that the SRAM is relatively insufficient. It is used for temporary storage of data, produced as a result of processing, until instructions call for the data to be used again in subsequent processing. In addition, during interrupts and subroutine calls, the return address is stored on the stack. The stack is effectively allocated in the general data SRAM, and consequently the stack size is only limited by the total SRAM size and the usage of the SRAM. Therefore, we have to reserve enough SRAM space. As mentioned before, the AT45DB041D contains two SRAM buffers of 264 bytes each, and the AT45DB642D also contains two SRAM buffers of 1,056 bytes each. Therefore, we can take full advantage of these parts of the space and treat them as external SRAM buffers. Thus, the available SRAM of the collector is increased by 12.89%, and that of the concentrator is increased by 50.10%. EEPROM in the ATmega128L is used for storing the device parameters and the routing table. Since each entry of the routing table occupies 5 bytes, the EEPROM can record about 800 entries, which is sufficient for this type of application. The external flash is a type of non-volatile storage that can be electrically erased and reprogrammed. No power is needed to maintain the information stored in the chip. Therefore, all the data obtained from the electricity meters are kept in external flash. The data concentrator is required to record hourly electricity meter data in last fifteen days and daily electricity meter data in last sixty days. And the flash memory size used in a concentrator is 69,206,016 bits, so a single data concentrator can monitor at most 2,300 electricity meters, which is sufficient for the application of the automatic electricity meter monitoring.</p></sec>
<sec>
<label>4.4.</label>
<title>Energy Consumption</title>
<p>Minimizing the energy consumption of our platform is essential, so a dynamic power-management technique is a feature of our system. This technique dynamically reconfigures the system to provide the requested services and performance levels with a minimum number of active components or a minimum activity level on such components. We chose the SP6201 to dynamically control the RF module. The SP6201 is CMOS low dropout regulator (LDO), which offers an extremely low quiescent current. The current of the nRF905 and the SP485E is zero in the sleep mode using the SP6201. <xref ref-type="table" rid="t3-sensors-10-06307">Table 3</xref> shows the average current of a data collector under different modes.</p></sec>
<sec>
<label>4.5.</label>
<title>Protection Measure</title>
<p>The design of an automatic electricity monitoring system needs to consider lightning and fire protection as well as waterproofness. Therefore, transient voltage suppressors are added to protect devices from damage due to lightning strikes by intercepting such strikes and safely passing their extremely high voltage. Thermistors are also included in our design. A thermistor is a type of resistor whose resistance varies with temperature. Thermistors are widely used as inrush current limiters, temperature sensors, overcurrent protectors, and self-regulating heating elements. In addition, waterproof sealing is also needed for collectors and concentrators.</p></sec></sec>
<sec>
<label>5.</label>
<title>Dynamic Tree (DT) Protocol</title>
<p>Many intricate protocols of sensor networks have been proposed based on laboratory settings in the past few years. However, a significant gap remains between the laboratory settings and the application environments. In this section, we present a dynamic tree (DT) protocol that is designed for smart sensors in harsh environments. We also discuss problems that are hard to be modeled and simulated in laboratory settings and how to improve the reliability of the network in a real scenario.</p>
<sec>
<label>5.1.</label>
<title>Network Initiation</title>
<p>Initially, the <italic>DtA</italic> value of each data collector equals <italic>DtA_Max</italic> + 1, where <italic>DtA</italic> indicates the hop count to the data concentrator<italic>,</italic> and <italic>DtA_Max</italic> is the maximum depth of the EMMNet. The <italic>DtA</italic> value of the data concentrator is set to 0. When the collector is opened, it will regularly send a request message, RM. This request message includes two fields: <italic>packet_sender_ID</italic> and <italic>packet_DtA</italic>. Here, <italic>packet_sender_ID</italic> indicates who sends the message, and <italic>packet_DtA</italic> describes the hop count between the sender and the concentrator. When any collector receives an RM packet, it can reply if its <italic>DtA</italic> is smaller than the <italic>packet_DtA</italic> in RM and does not equals <italic>DtA_Max</italic>. Therefore, only the data concentrator can reply to collector requests at the beginning. The reply to the request message, RRM, has the following fields: <italic>packet_source_ID</italic>, <italic>packet_DtA</italic>, and <italic>packet_sender_ID</italic>. Here, <italic>packet_source_ID</italic> denotes the ID of the concentrator.</p>
<p>If any collector receives an RRM and its <italic>DtA</italic> equals <italic>DtA_Max</italic> + 1, its <italic>DtA</italic> is set to <italic>packet_DtA</italic> + 1 no matter what the <italic>packet_DtA</italic> value is. Meanwhile, its <italic>father_ID</italic> list and <italic>root_ID</italic> are updated according to <italic>packet_sender_ID</italic> and <italic>packet_source_ID</italic>, where <italic>father_ID</italic> list and <italic>root_ID</italic> are used for recording the potential relay nodes and the concentrator ID.</p>
<p>If a collector receives another RRM and its <italic>DtA</italic> is smaller than <italic>DtA_Max</italic> + 1, it should make judgments based on the value of <italic>packet_DtA</italic> and its own <italic>DtA</italic>. If <italic>packet_DtA</italic> + 1&lt;<italic>DtA</italic>, the value of <italic>DtA</italic> and <italic>root _ID</italic> should be updated. Meanwhile, it should clear the <italic>father_ID</italic> list before inserting <italic>packet_sender_ID</italic> as a new relay node. If (1) <italic>packet_DtA</italic> + 1=<italic>DtA</italic>, (2) <italic>packet_source_ID</italic> equals <italic>root _ID</italic>, and (3) <italic>packet_sender_ID</italic> is not in the <italic>father_ID</italic> list, <italic>packet_sender_ID</italic> is added to the end of the <italic>father_ID</italic> list.</p>
<p>In the electricity meter monitoring application, we not only collect the quantity of electric, but also control the parameters of the electricity meters. Transmission is divided into uplink and downlink channels. The uplink channel is used for transmission of information from the collectors to the concentrator. The downlink channel is used for transmission of information from the concentrator to the collectors, including resetting the sample ratio, altering the collection parameter, and sending query commands. Therefore, we should establish the downlink channel. Each collector needs to transmit a routing message to the concentrator when its <italic>DtA</italic> is smaller than <italic>DtA_Max</italic> + 1. If a collector receives routing messages from its child collectors, the routing information is recorded in the routing table and the messages are relayed to its parent collectors.</p>
<p>The structure of the EMMNet after network initiation is shown in <xref ref-type="fig" rid="f4-sensors-10-06307">Figure 4</xref>. Each device has a communication range, which is illustrated by the dotted line. The communication range is not a perfect circle due to the complicated communication environment. The dashed lines indicate relationships among the collectors and the concentrator. The numbers in the circles indicate the value of <italic>DtA</italic>. The node whose <italic>DtA</italic> value equals zero denotes the data concentrator. A collector whose <italic>DtA</italic> value is larger than zero at least has a parent collector, and the <italic>DtA</italic> value of this collector is larger than that of its parent collector by one.</p></sec>
<sec sec-type="methods">
<label>5.2.</label>
<title>Data Transmission</title>
<p>Every fifteen minutes, collectors report electricity meter data to the concentrator. However, most of the time collectors are in sleep mode. The concentrator transmits the control message to collectors according to the routing table, while collectors report the data based on the <italic>father_ID</italic> list. If a child collector detects that one of its parent collectors does not respond, it can choose another spare parent collector to relay the message. If all of its parent collectors fail to respond—the situation may be caused by network structure change—it should rejoin the network. In other words, this collector needs to reset <italic>DtA</italic> to <italic>DtA_Max</italic> + 1 and send request messages, RM. If a collector receives an RM from its parent collector and its <italic>packet_DtA</italic> does not equal <italic>DtA</italic>-1, it needs to remove the corresponding item from the <italic>father_ID</italic>. A special case is when the <italic>father_ID</italic> list contains only one single item: the collector should also rejoin the network. Making use of this strategy, EMMNet can maintain connectivity without frequent network reconstruction, even if some collectors die because of non-recoverable errors or malfunction.</p></sec>
<sec sec-type="methods">
<label>5.3.</label>
<title>Analysis of DT Protocol</title>
<p>We analyze the DT protocol under the ideal case and discuss the problems occurring in practical applications in this section.</p>
<p>First, we make several assumptions to simplify the analysis:
<list list-type="order">
<list-item>
<p>The collectors in the EMMNet are distributed as a homogeneous spatial Poisson process□ in two-dimensional space.</p></list-item>
<list-item>
<p>All collectors and concentrators transmit at the same power level and have the same radio range <italic>r</italic>.</p></list-item>
<list-item>
<p>A distance of <italic>d</italic> between any collector and its concentrator is equivalent to [d/(0.75 r)] hops. This can be explained as follows: as shown in <xref ref-type="fig" rid="f5-sensors-10-06307">Figure 5</xref>, two hops require at least an interval of <italic>r + ε</italic>, and three hops require at least an interval of <italic>r + 2ε</italic>, where ε is an arbitrary small value.</p></list-item></list></p>
<p>This can then be extended to the situation of 2<italic>n</italic> hops by concatenating <italic>n</italic> 2-hop topological graphs. In the same way, 2<italic>n</italic> + 1 hops can be extended by concatenating <italic>n</italic> − 1 2-hop topological graphs and one 3-hop topological graph. We can conclude that 2n-hop or 2<italic>n</italic> + 1-hop requires at least an interval of <italic>nr</italic>. Thus, with the fact that 2 <italic>n</italic> hops require at most an interval of 2<italic>nr</italic>, it could be deduced that on average there are [d/(0.75 r)] hops between any collector and its concentrator.
<list list-type="simple">
<list-item>
<p>(4) Taking into account the short distance in one hop, we use the free space channel model for estimating the radio hardware energy dissipation:
<disp-formula id="FD1">
<label>(1)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>E</mml:mi></mml:mrow>
<mml:mrow>
<mml:mi>T</mml:mi>
<mml:mi>X</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">elec</mml:mi></mml:msub>
<mml:mi>k</mml:mi>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>e</mml:mi>
<mml:mi mathvariant="italic">fs</mml:mi></mml:msub>
<mml:msup>
<mml:mrow>
<mml:mi>d</mml:mi></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mi>k</mml:mi></mml:mrow></mml:math></disp-formula></p></list-item></list></p>
<p>To receive this message, the radio expends:
<disp-formula id="FD2">
<label>(2)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">RX</mml:mi></mml:msub>
<mml:mo>=</mml:mo>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">elec</mml:mi></mml:msub>
<mml:mi>k</mml:mi></mml:mrow></mml:math></disp-formula></p>
<p>The electronics energy (<italic>E<sub>elec</sub></italic>) depends on such factors as digital coding, modulation, and filtering. The variable <italic>d</italic> indicates the distance to the receiver. The amplifier energy, e<sub>fs</sub>, depends on the distance <italic>d</italic> and the acceptable bit-error rate [<xref ref-type="bibr" rid="b21-sensors-10-06307">21</xref>]. <italic>k</italic> is the length of the message.</p>
<p>According to the results in Reference [<xref ref-type="bibr" rid="b22-sensors-10-06307">22</xref>], the expectation value of the total length of all segments connecting the collectors to the concentrator, L<sub>v</sub>, is given by:
<disp-formula id="FD3">
<label>(3)</label>
<mml:math display="block">
<mml:mrow>
<mml:mi>E</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>L</mml:mi></mml:mrow>
<mml:mi>v</mml:mi></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>≈</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<mml:mrow>
<mml:mn>2</mml:mn>
<mml:msup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mrow>
<mml:mn>3</mml:mn>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn></mml:mrow></mml:msup></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula>where <italic>n</italic> is the number of collectors. With this formula and the third assumption mentioned above, we can calculate the number of hops, <italic>J</italic>, in an EMMNet as:
<disp-formula id="FD4">
<label>(4)</label>
<mml:math display="block">
<mml:mrow>
<mml:mi>J</mml:mi>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>E</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>L</mml:mi></mml:mrow>
<mml:mi>v</mml:mi></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow>
<mml:mrow>
<mml:mi>r</mml:mi>
<mml:mo>×</mml:mo>
<mml:mn>3</mml:mn>
<mml:mo>/</mml:mo>
<mml:mn>4</mml:mn></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mn>2</mml:mn>
<mml:mrow>
<mml:mn>3</mml:mn>
<mml:msup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mrow>
<mml:mn>3</mml:mn>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn></mml:mrow></mml:msup>
<mml:mi>r</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula></p>
<p>The energy consumption of the communication between the collectors and the concentrator, <italic>C</italic>, can be evaluated as:
<disp-formula id="FD5">
<label>(5)</label>
<mml:math display="block">
<mml:mrow>
<mml:mi>E</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mi>C</mml:mi>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mi>J</mml:mi>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">TX</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">RX</mml:mi></mml:msub></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mi mathvariant="italic">Jk</mml:mi>
<mml:mrow>
<mml:mo stretchy="false">[</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">elec</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>e</mml:mi>
<mml:mi mathvariant="italic">fs</mml:mi></mml:msub>
<mml:msup>
<mml:mrow>
<mml:mi>r</mml:mi></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">elec</mml:mi></mml:msub></mml:mrow>
<mml:mo stretchy="false">]</mml:mo></mml:mrow></mml:mrow></mml:math></disp-formula></p>
<p><italic>E</italic>[<italic>C</italic>] is minimized by the value of <italic>r</italic> that is a solution of:
<disp-formula id="FD6">
<label>(6)</label>
<mml:math display="block">
<mml:mrow>
<mml:mo>−</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>2</mml:mn>
<mml:msub>
<mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">elec</mml:mi></mml:msub></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:mfrac>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>e</mml:mi>
<mml:mi mathvariant="italic">fs</mml:mi></mml:msub>
<mml:mo>=</mml:mo>
<mml:mn>0</mml:mn></mml:mrow></mml:math></disp-formula></p>
<p>This equation shows how to maximize the performance of the sensor network. However, a significant gap remains between the assumptions and the application environment. Certain problems may arise in a practical application:
<list list-type="order">
<list-item>
<p>In the conventional literature on sensor networks, protocols are designed on the assumption of reciprocity between uplink and downlink channels. However, affected by the imbalance of the RF circuitries in practice, the reciprocity between the uplink and downlink channels cannot be maintained, which will cause a performance decrease.</p></list-item>
<list-item>
<p>It used to be widely believed that sensor networks with smaller average hop counts perform better than those with larger average hop counts. Nevertheless, we find out that when a collector chooses a parent collector with a much smaller <italic>DtA</italic> value, it may actually reduce the transmission success rate. That is because the child and parent nodes are too far from each other and the bit error rate is relatively high.</p></list-item>
<list-item>
<p>In the theoretical analysis, we ignore the fact that packet length affects the transmission success rate. Therefore, even if nodes can communicate with others without any trouble in the process of constructing the network, they may need to retransmit many times before the concentrator successfully receives the monitoring data. The reason is that the size of the monitoring data is usually much larger than that of RRM or RM.</p></list-item></list></p>
<p>We set the packet length of RRM and RM to equal that of the longest data packet to solve the above problems. The collector can only broadcast the RM a limited number of times, marked as <italic>LT</italic>, when the value of <italic>DtA</italic> is smaller than <italic>DtA_Max</italic> + 1. Evaluation results of the DT protocol from several applications show that our strategy greatly improves the performance of the EMMNets.</p></sec></sec>
<sec>
<label>6.</label>
<title>EMMNet Validation</title>
<sec>
<label>6.1.</label>
<title>Experiment Environment</title>
<p>The experiment environment for the proposed smart sensors is shown in this section. Collaborating with Hangao Electronics Co., Ltd., we deployed our systems in two cities and tested our systems over a three-month period. The data of 2024 electricity meters were +collected. All the devices of the test networks are listed in <xref ref-type="table" rid="t4-sensors-10-06307">Table 4</xref> and the elements used in EMMNet are listed in <xref ref-type="table" rid="t5-sensors-10-06307">Table 5</xref>.</p>
<p>The interval between sending two RMs is 1 minute, the packet length of an RRM or RM equals 330 bytes, and the maximal depth of the EMMNet is 10 in these EMMNets.</p>
<p><xref ref-type="fig" rid="f6-sensors-10-06307">Figure 6</xref> shows the architectural plans of the Zhiyang residence community, Yangzhou City, Jiangsu Province, China. We deployed two of our systems in this community. The numbers in circles indicate the last two digits of the collector addresses.</p></sec>
<sec sec-type="results">
<label>6.2.</label>
<title>Results</title>
<p>In our original design, there was no limit to the number of times a RM could be sent, even when the collectors had joined the EMMNets. A collector had a great chance of selecting a relay node with a smaller <italic>DtA</italic> value, when it constantly sent RMs. However, the performance of such relay nodes might be poor. We found that the transmission success rate decreased if a collector chose a parent collector with a very small <italic>DtA</italic> value. Therefore, we limited the number of broadcast packets when the value of <italic>DtA</italic> is smaller than <italic>DtA_Max</italic> + 1.</p>
<p>The distribution of the <italic>DtA</italic> value is shown in <xref ref-type="fig" rid="f7-sensors-10-06307">Figure 7</xref>, and the transmission success rate is illustrated in <xref ref-type="fig" rid="f8-sensors-10-06307">Figure 8</xref>. From November 3–18, 2009, collectors could broadcast RMs without any limit. As shown in <xref ref-type="fig" rid="f7-sensors-10-06307">Figure 7</xref>, the network structure does not seem very good. All the <italic>DtA</italic> values of collectors are less than 3, and the average transmission success rate is relatively low. That is because child and parent nodes are too far from each other and the bit error rate is relatively high. Therefore, we reprogrammed the collectors with a hand-held device in the 470 MHz wireless channel. When the value of <italic>DtA</italic> was smaller than <italic>DtA_Max</italic> + 1, the collector could only broadcast the RM three times. On Deceber 24, 2009, we reprogrammed the devices and made the EMMNets dynamically choose the limited times that RM packets were broadcasted according to the transmission success rate. At first, the limited-times value <italic>LT</italic> was set to two; if the performance was poor, the <italic>LT</italic> was increased by two. <xref ref-type="fig" rid="f8-sensors-10-06307">Figure 8</xref> shows that average transmission success rate is improved due to the advantage of the network topology. And <xref ref-type="fig" rid="f9-sensors-10-06307">Figure 9</xref> plots the corresponding network structures of the EMMNets deployed in Zhiyang residence community. With the EMMNets, customers can obtain the energy flow amount at any time through internet and the maintainers can control the parameters of the electricity meters if necessary. The meter monitoring task can be done at the management department by using this system. What should be emphasized is that the operational cost of EMMNet is relatively low, compared with other existing remote meter monitoring systems based on GPRS. Meanwhile, EMMNets can realize automatic charge if they are connected to bank systems.</p></sec></sec>
<sec sec-type="conclusions">
<label>7.</label>
<title>Conclusions</title>
<p>In this paper, we have presented a hierarchical smart sensor system for electricity meter monitoring. EMMNet is built on a heterogeneous networking infrastructure that includes data collectors, data concentrators, hand-held devices, a centralized server, and clients. The major challenge of adopting a sensor network to fulfill the requirements of electricity meter monitoring is the complicated environments, such as those with tall building structures, long distances, and signal interference. Our practical experience with sensor network deployment can provide guidance for the production of remote monitoring. We plan to extend the EMMNet to gas-meter and water-meter monitoring systems in the future. This work would be easily accomplished without changing the system a lot, because the main components of EMMNet are also suitable for these applications. And cameras may be added into data collectors in some applications. The major task of it is to compress images with low cost MCU.</p></sec></body>
<back>
<ack>
<p>This research is supported by the National Natural Science Foundation of China (Grant No. 60602016), the China Postdoctoral Science Foundation funded project (Grant Nos. 20090460739), the Hi-Tech Research and Development 863 Program of China (Grant No. 2007AA01Z428), and the Innovation Fund for Graduate Students of USTC (Grant No. KD2005042).</p></ack>
<ref-list>
<title>References</title>
<ref id="b1-sensors-10-06307"><label>1.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Ni</surname><given-names>DC</given-names></name><name><surname>Chou</surname><given-names>HC</given-names></name></person-group><article-title>Sensor Network for Gas Meter Application</article-title><conf-name>Proceedings of Third International Conference on Sensor Technologies and Applications</conf-name><conf-loc>Athens/Glyfada, Greece</conf-loc><conf-date>14–19 June, 2009</conf-date><fpage>410</fpage><lpage>414</lpage></citation></ref>
<ref id="b2-sensors-10-06307"><label>2.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rivera</surname><given-names>J</given-names></name><name><surname>Herrera</surname><given-names>G</given-names></name><name><surname>Chacon</surname><given-names>M</given-names></name><name><surname>Acosta</surname><given-names>P</given-names></name><name><surname>Carrillo</surname><given-names>M</given-names></name></person-group><article-title>Improved Progressive Polynomial Algorithm for Self Adjustment and Optimal Response in Intelligent Sensors</article-title><source>Sensors</source><year>2008</year><volume>8</volume><fpage>7410</fpage><lpage>7427</lpage><pub-id pub-id-type="doi">10.3390/s8117410</pub-id></citation></ref>
<ref id="b3-sensors-10-06307"><label>3.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Granados-Lieberman</surname><given-names>D</given-names></name><name><surname>Romero-Troncoso</surname><given-names>RJ</given-names></name><name><surname>Cabal-Yepez</surname><given-names>E</given-names></name><name><surname>Osornio-Rios</surname><given-names>RA</given-names></name><name><surname>Franco-Gasca</surname><given-names>LA</given-names></name></person-group><article-title>A Real-time Smart Sensor for High-Resolution Frequency Estimation in Power Systems</article-title><source>Sensors</source><year>2009</year><volume>9</volume><fpage>7412</fpage><lpage>7429</lpage><pub-id pub-id-type="doi">10.3390/s90907412</pub-id><pub-id pub-id-type="pmid">22400002</pub-id></citation></ref>
<ref id="b4-sensors-10-06307"><label>4.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rodriguez-Donate</surname><given-names>C</given-names></name><name><surname>Morales-Velazquez</surname><given-names>L</given-names></name><name><surname>Osornio-Rios</surname><given-names>RA</given-names></name><name><surname>Herrera-Ruiz</surname><given-names>G</given-names></name><name><surname>Romero-Troncoso</surname><given-names>RJ</given-names></name></person-group><article-title>FPGA-Based Fused Smart Sensor for Dynamic and Vibration Parameter Extraction in Industrial Robot Links</article-title><source>Sensors</source><year>2010</year><volume>10</volume><fpage>4114</fpage><lpage>4129</lpage><pub-id pub-id-type="doi">10.3390/s100404114</pub-id><pub-id pub-id-type="pmid">22319345</pub-id></citation></ref>
<ref id="b5-sensors-10-06307"><label>5.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Trejo-Hernandez</surname><given-names>M</given-names></name><name><surname>Osornio-Rios</surname><given-names>RA</given-names></name><name><surname>Romero-Troncoso</surname><given-names>RJ</given-names></name><name><surname>Rodriguez-Donate</surname><given-names>C</given-names></name><name><surname>Dominguez-Gonzalez</surname><given-names>A</given-names></name><name><surname>Herrera-Ruiz</surname><given-names>G</given-names></name></person-group><article-title>FPGA-Based Fused Smart-Sensor for Tool-Wear Area Quantitative Estimation in CNC Machine Inserts</article-title><source>Sensors</source><year>2010</year><volume>10</volume><fpage>3373</fpage><lpage>3388</lpage><pub-id pub-id-type="doi">10.3390/s100403373</pub-id><pub-id pub-id-type="pmid">22319304</pub-id></citation></ref>
<ref id="b6-sensors-10-06307"><label>6.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Son</surname><given-names>JK</given-names></name><name><surname>Niu</surname><given-names>G</given-names></name><name><surname>Yang</surname><given-names>BS</given-names></name><name><surname>Hwang</surname><given-names>DH</given-names></name><name><surname>Kang</surname><given-names>DS</given-names></name></person-group><article-title>Development of Smart Sensors System for Machine Fault Diagnosis</article-title><source>Expert. Syst. Appl</source><year>2009</year><volume>36</volume><fpage>11981</fpage><lpage>11991</lpage><pub-id pub-id-type="doi">10.1016/j.eswa.2009.03.069</pub-id></citation></ref>
<ref id="b7-sensors-10-06307"><label>7.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wu</surname><given-names>J</given-names></name><name><surname>Yuan</surname><given-names>S</given-names></name><name><surname>Zhou</surname><given-names>G</given-names></name><name><surname>Ji</surname><given-names>S</given-names></name><name><surname>Wang</surname><given-names>Z</given-names></name><name><surname>Wang</surname><given-names>Y</given-names></name></person-group><article-title>Design and Evaluation of a Wireless Sensor Network Based Aircraft Strength Testing System</article-title><source>Sensors</source><year>2009</year><volume>9</volume><fpage>4195</fpage><lpage>4210</lpage><pub-id pub-id-type="doi">10.3390/s90604195</pub-id><pub-id pub-id-type="pmid">22408521</pub-id></citation></ref>
<ref id="b8-sensors-10-06307"><label>8.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Gao</surname><given-names>T</given-names></name><name><surname>Pesto</surname><given-names>C</given-names></name><name><surname>Selavo</surname><given-names>L</given-names></name><name><surname>Chen</surname><given-names>Y</given-names></name><name><surname>Ko</surname><given-names>J</given-names></name><name><surname>Lim</surname><given-names>J</given-names></name><name><surname>Terzis</surname><given-names>A</given-names></name><name><surname>Watt</surname><given-names>A</given-names></name><name><surname>Deng</surname><given-names>J</given-names></name><name><surname>Chen</surname><given-names>BR</given-names></name><name><surname>Lorincz</surname><given-names>K</given-names></name><name><surname>Welsh</surname><given-names>M</given-names></name></person-group><article-title>Wireless Medical Sensor Networks in Emergency Response: Implementation and Pilot Results</article-title><conf-name>Proceedings of IEEE International Conference on Technologies for Homeland Security</conf-name><conf-loc>Waltham, UK</conf-loc><conf-date>12–13 May 2008</conf-date><comment>No. 1062</comment></citation></ref>
<ref id="b9-sensors-10-06307"><label>9.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Ghasemzadeh</surname><given-names>H</given-names></name><name><surname>Barnes</surname><given-names>J</given-names></name><name><surname>Guenterberg</surname><given-names>E</given-names></name><name><surname>Jafari</surname><given-names>R</given-names></name></person-group><article-title>A Phonological Expression for Physical Movement Monitoring in Body Sensor Networks</article-title><conf-name>Proceedings of the Fifth IEEE International Conference on Mobile Ad hoc and Sensor Systems (MASS)</conf-name><conf-loc>Atlanta, GA, USA</conf-loc><conf-date>September 2008</conf-date></citation></ref>
<ref id="b10-sensors-10-06307"><label>10.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Mainwaring</surname><given-names>A</given-names></name><name><surname>Polastre</surname><given-names>J</given-names></name><name><surname>Szewczyk</surname><given-names>R</given-names></name><name><surname>Culler</surname><given-names>D</given-names></name></person-group><article-title>Wireless Sensor Networks for Habitat Monitoring</article-title><conf-name>Proceedings of First ACM International Workshop on Wireless Workshop in Wireless Sensor Networks and Applications</conf-name><conf-loc>Atlanta, GA, USA</conf-loc><conf-date>September 28, 2002</conf-date><fpage>88</fpage><lpage>97</lpage></citation></ref>
<ref id="b11-sensors-10-06307"><label>11.</label><citation citation-type="other"><comment><italic>Q/GDW 374.2-2009 Power user electric energy data acquire system technical specification.</italic></comment></citation></ref>
<ref id="b12-sensors-10-06307"><label>12.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Cao</surname><given-names>LT</given-names></name><name><surname>Jiang</surname><given-names>W</given-names></name><name><surname>Zhang</surname><given-names>ZL</given-names></name></person-group><article-title>Networked wireless meter reading system based on ZigBee technology</article-title><conf-name>Proceedings of Chinese Control and Decision Conference,</conf-name><conf-loc>Yantai, China</conf-loc><conf-date>2–4 July 2008</conf-date><fpage>3455</fpage><lpage>3460</lpage></citation></ref>
<ref id="b13-sensors-10-06307"><label>13.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Wang</surname><given-names>JJ</given-names></name></person-group><article-title>Wireless <italic>ad hoc</italic> networks remote meter reading system based on GPRS</article-title><conf-name>Proceedings of the 2009 International Conference on Communication Software and Networks</conf-name><conf-loc>Macau, China</conf-loc><conf-date>26–28 February, 2009</conf-date><fpage>463</fpage><lpage>466</lpage></citation></ref>
<ref id="b14-sensors-10-06307"><label>14.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Crossbow Technology Inc</collab></person-group><source>MICA2 data sheet</source><comment>Available online: <ext-link xlink:href="http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/MICA2_Datasheet.pdf" ext-link-type="uri">http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/MICA2_Datasheet.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b15-sensors-10-06307"><label>15.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Crossbow Technology Inc</collab></person-group><source>TelosB data sheet</source><comment>Available online: <ext-link xlink:href="http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/TelosB_Datasheet.pdf" ext-link-type="uri">http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/TelosB_Datasheet.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b16-sensors-10-06307"><label>16.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Crossbow Technology Inc</collab></person-group><source>MICAZ data sheet</source><comment>Available online: <ext-link xlink:href="http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/MICAZ_Datasheet.pdf" ext-link-type="uri">http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/MICAZ_Datasheet.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b17-sensors-10-06307"><label>17.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Crossbow Technology Inc</collab></person-group><source>Imote2 data sheet</source><comment>Available online: <ext-link xlink:href="http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/Imote2_Datasheet.pdf" ext-link-type="uri">http://www.xbow.com/Products/Product_pdf_files/Wireless_pdf/Imote2_Datasheet.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b18-sensors-10-06307"><label>18.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Sentilla Inc</collab></person-group><source>Tmote Mini data sheet</source><comment>Available online: <ext-link xlink:href="http://sentilla.com/files/pdf/eol/Tmote_Mini_Datasheet.pdf" ext-link-type="uri">http://sentilla.com/files/pdf/eol/Tmote_Mini_Datasheet.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b19-sensors-10-06307"><label>19.</label><citation citation-type="web"><person-group person-group-type="author"><collab>Sentilla Inc</collab></person-group><source>Tmote Sky data sheet</source><comment>Available online: <ext-link xlink:href="http://sentilla.com/files/pdf/eol/tmote-sky-brochure.pdf" ext-link-type="uri">http://sentilla.com/files/pdf/eol/tmote-sky-brochure.pdf</ext-link> (Accessed 15 May 2010).</comment></citation></ref>
<ref id="b20-sensors-10-06307"><label>20.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Kasten</surname><given-names>O</given-names></name><name><surname>Beutel</surname><given-names>J</given-names></name><name><surname>Ringwald</surname><given-names>M</given-names></name></person-group><article-title>Btnodes—a Distributed Platform for Sensor Nodes</article-title><conf-name>Proceedings of Embedded Networked Sensor Systems</conf-name><conf-loc>New York, NY, USA</conf-loc><conf-date>November 2003</conf-date><fpage>292</fpage><lpage>293</lpage></citation></ref>
<ref id="b21-sensors-10-06307"><label>21.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Heinzelman</surname><given-names>W</given-names></name></person-group><source>Application-specific Protocol Architectures for Wireless Networks</source><comment>PhD Thesis</comment><publisher-name>Massachusetts Institute of Technology</publisher-name><publisher-loc>Cambridge, MA, USA</publisher-loc><year>2000</year></citation></ref>
<ref id="b22-sensors-10-06307"><label>22.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Foss</surname><given-names>SG</given-names></name><name><surname>Zuyev</surname><given-names>SA</given-names></name></person-group><article-title>On a Voronoi Aggregative Process Related to a Bivariate Poisson Process</article-title><source>Adv. Appl. Probab</source><year>1996</year><volume>28</volume><fpage>965</fpage><lpage>981</lpage><pub-id pub-id-type="doi">10.2307/1428159</pub-id></citation></ref></ref-list>
<sec sec-type="display-objects">
<title>Figures and Tables</title>
<fig id="f1-sensors-10-06307" position="float">
<label>Figure 1.</label>
<caption>
<p>Architecture of EMMNet.</p></caption>
<graphic xlink:href="sensors-10-06307f1.gif"/></fig>
<fig id="f2-sensors-10-06307" position="float">
<label>Figure 2.</label>
<caption>
<p>(a) Hardware architecture of a data collector. (b) Spot photo of data collector.</p></caption>
<graphic xlink:href="sensors-10-06307f2.gif"/></fig>
<fig id="f3-sensors-10-06307" position="float">
<label>Figure 3.</label>
<caption>
<p>Hardware architecture of a data concentrator.</p></caption>
<graphic xlink:href="sensors-10-06307f3.gif"/></fig>
<fig id="f4-sensors-10-06307" position="float">
<label>Figure 4.</label>
<caption>
<p>Structure of EMMNet with eight collectors.</p></caption>
<graphic xlink:href="sensors-10-06307f4.gif"/></fig>
<fig id="f5-sensors-10-06307" position="float">
<label>Figure 5.</label>
<caption>
<p>(a) Two hops require at least an interval of <italic>r</italic> + <italic>ε</italic>. (b) Three hops require at least an interval of <italic>r</italic> + <italic>2ε</italic>.</p></caption>
<graphic xlink:href="sensors-10-06307f5.gif"/></fig>
<fig id="f6-sensors-10-06307" position="float">
<label>Figure 6.</label>
<caption>
<p>Two EMMNets deployed in Zhiyang residence community, Yangzhou City, Jiangsu Province, China.</p></caption>
<graphic xlink:href="sensors-10-06307f6.gif"/></fig>
<fig id="f7-sensors-10-06307" position="float">
<label>Figure 7.</label>
<caption>
<p>Distribution of <italic>DtA</italic> value in three different cases.</p></caption>
<graphic xlink:href="sensors-10-06307f7.gif"/></fig>
<fig id="f8-sensors-10-06307" position="float">
<label>Figure 8.</label>
<caption>
<p>Average transmission success rate. System tested for three months; collectors reprogrammed twice during this period.</p></caption>
<graphic xlink:href="sensors-10-06307f8.gif"/></fig>
<fig id="f9-sensors-10-06307" position="float">
<label>Figure 9.</label>
<caption>
<p>Network structures of EMMNets deployed in Zhiyang residence community.</p></caption>
<graphic xlink:href="sensors-10-06307f9.gif"/></fig>
<table-wrap id="t1-sensors-10-06307" position="float">
<label>Table 1.</label>
<caption>
<p>Characteristic ubiquitous sensor network platforms.</p></caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th colspan="4" align="center" valign="bottom"><bold>Processor</bold></th>
<th colspan="5" align="center" valign="bottom"><bold>RF Transceiver</bold></th></tr>
<tr>
<th align="center" valign="middle"><bold>Platforms</bold></th>
<th align="center" valign="middle"><bold>Program Space</bold></th>
<th align="center" valign="middle"><bold>External Space</bold></th>
<th align="center" valign="middle"><bold>Current Draw</bold></th>
<th align="center" valign="middle"><bold>Frequency</bold></th>
<th align="center" valign="middle"><bold>Current Draw</bold></th>
<th align="center" valign="middle"><bold>Indoor Range</bold></th>
<th align="center" valign="middle"><bold>Tx speed</bold></th>
<th align="center" valign="middle"><bold>Cost</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="middle">MICA2</td>
<td align="center" valign="middle">128 kB</td>
<td align="center" valign="middle">512 kB</td>
<td align="center" valign="middle">8 mA</td>
<td align="center" valign="middle">868/916 MHz</td>
<td align="center" valign="middle">S: 27 mA at 5 dbm<break/>R: 10 mA</td>
<td align="center" valign="middle">—</td>
<td align="center" valign="middle">38.4 kbps</td>
<td align="center" valign="middle">$125</td></tr>
<tr>
<td align="center" valign="middle">TelosB</td>
<td align="center" valign="middle">48 kB</td>
<td align="center" valign="middle">1,024 kB</td>
<td align="center" valign="middle">1.8 mA</td>
<td align="center" valign="middle">2,400 MHz</td>
<td align="center" valign="middle">S: —<break/>R: 23 mA</td>
<td align="center" valign="middle">20–30m</td>
<td align="center" valign="middle">250 kbps</td>
<td align="center" valign="middle">$134</td></tr>
<tr>
<td align="center" valign="middle">MICAZ</td>
<td align="center" valign="middle">128 kB</td>
<td align="center" valign="middle">512 kB</td>
<td align="center" valign="middle">8 mA</td>
<td align="center" valign="middle">2,400 MHz</td>
<td align="center" valign="middle">S: 17.4 mA at 0 dbm<break/>R: 19.7 mA</td>
<td align="center" valign="middle">20–30m</td>
<td align="center" valign="middle">250 kbps</td>
<td align="center" valign="middle">$99</td></tr>
<tr>
<td align="center" valign="middle">Imote2</td>
<td align="center" valign="middle">32 MB</td>
<td align="center" valign="middle">32 MB</td>
<td align="center" valign="middle">66 mA</td>
<td align="center" valign="middle">2,400 MHz</td>
<td align="center" valign="middle">—</td>
<td align="center" valign="middle">&lt;30 m</td>
<td align="center" valign="middle">250 kbps</td>
<td align="center" valign="middle">$299</td></tr>
<tr>
<td align="center" valign="middle">Tmote Sky</td>
<td align="center" valign="middle">48 kB</td>
<td align="center" valign="middle">1,024 kB</td>
<td align="center" valign="middle">2 mA</td>
<td align="center" valign="middle">2,400 MHz</td>
<td align="center" valign="middle">17 mA</td>
<td align="center" valign="middle">—</td>
<td align="center" valign="middle">250 kbps</td>
<td align="center" valign="middle">$78</td></tr>
<tr>
<td align="center" valign="middle">Tmote Mini</td>
<td align="center" valign="middle">48 kB</td>
<td align="center" valign="middle">1,024 kB</td>
<td align="center" valign="middle">2 mA</td>
<td align="center" valign="middle">2,400 MHz</td>
<td align="center" valign="middle">17 mA</td>
<td align="center" valign="middle">&lt;30 m</td>
<td align="center" valign="middle">250 kbps</td>
<td align="center" valign="middle">—</td></tr>
<tr>
<td align="center" valign="middle">Btnode</td>
<td align="center" valign="middle">128 kB</td>
<td align="center" valign="middle">128 kB</td>
<td align="center" valign="middle">8 mA</td>
<td align="center" valign="middle">433/868/916 MHz</td>
<td align="center" valign="middle">S: 14.8 mA at 0 dbm<break/>R: 7.4 mA</td>
<td align="center" valign="middle">20 m</td>
<td align="center" valign="middle">76.8 kbps</td>
<td align="center" valign="middle">$120</td></tr>
<tr>
<td align="center" valign="middle">EMMNet</td>
<td align="center" valign="middle">128 kB</td>
<td align="center" valign="middle">4/8 MB</td>
<td align="center" valign="middle">8 mA/30 uA</td>
<td align="center" valign="middle">433/470/868/916 MHz</td>
<td align="center" valign="middle">S: 20 mA at 6 dbm<break/>R:13 mA</td>
<td align="center" valign="middle">180 m</td>
<td align="center" valign="middle">50 kbps</td>
<td align="center" valign="middle">$40</td></tr></tbody></table></table-wrap>
<table-wrap id="t2-sensors-10-06307" position="float">
<label>Table 2.</label>
<caption>
<p>Ports assignment of ATmega128L.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th align="center" valign="middle"><bold>Port</bold></th>
<th align="center" valign="middle"><bold>Function</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="middle">PB0-PB6</td>
<td align="center" valign="middle">Connected to RF module</td></tr>
<tr>
<td align="center" valign="middle">PD0-PD3</td>
<td align="center" valign="middle">Connected to IrDA</td></tr>
<tr>
<td align="center" valign="middle">PD4-PD7</td>
<td align="center" valign="middle">LED</td></tr>
<tr>
<td align="center" valign="middle">PE0-PE2</td>
<td align="center" valign="middle">Connected to RS485 transceiver</td></tr>
<tr>
<td align="center" valign="middle">PE3-PE7</td>
<td align="center" valign="middle">Connected to RF module</td></tr>
<tr>
<td align="center" valign="middle">PF0-PF3</td>
<td align="center" valign="middle">Connected to external flash</td></tr>
<tr>
<td align="center" valign="middle">PF4-PF7</td>
<td align="center" valign="middle">JTAG test interface</td></tr></tbody></table></table-wrap>
<table-wrap id="t3-sensors-10-06307" position="float">
<label>Table 3.</label>
<caption>
<p>Average current of the data collector</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle"><bold>Chip</bold></th>
<th align="center" valign="middle"><bold>Tx current at 10 dbm</bold></th>
<th align="center" valign="middle"><bold>Rx current</bold></th>
<th align="center" valign="middle"><bold>Sleep</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="top">ATmega128L</td>
<td align="center" valign="top">8 mA</td>
<td align="center" valign="top">8 mA</td>
<td align="center" valign="top">30 uA</td></tr>
<tr>
<td align="center" valign="top">nRF905</td>
<td align="center" valign="top">29 mA</td>
<td align="center" valign="top">13 mA</td>
<td align="center" valign="top">0</td></tr>
<tr>
<td align="center" valign="top">SP485E</td>
<td align="center" valign="top">1 mA</td>
<td align="center" valign="top">1 mA</td>
<td align="center" valign="top">0</td></tr>
<tr>
<td align="center" valign="top">AT45DB041D</td>
<td align="center" valign="top">25 uA</td>
<td align="center" valign="top">27 uA</td>
<td align="center" valign="top">25 uA</td></tr></tbody></table></table-wrap>
<table-wrap id="t4-sensors-10-06307" position="float">
<label>Table 4.</label>
<caption>
<p>Five EMMNets in two cities.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle"><bold>Concentrator address</bold></th>
<th align="center" valign="middle"><bold>Num. of concentrator</bold></th>
<th align="center" valign="middle"><bold>Num. of hand-held devices</bold></th>
<th align="center" valign="middle"><bold>Num. of collectors</bold></th>
<th align="center" valign="middle"><bold>Num. of electricity meters</bold></th>
<th align="center" valign="middle"><bold>Location</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="middle">320100091</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">2</td>
<td align="center" valign="middle">45</td>
<td align="center" valign="middle">368</td>
<td align="center" valign="middle">Huaian City, China</td></tr>
<tr>
<td align="center" valign="middle">320100092</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">2</td>
<td align="center" valign="middle">35</td>
<td align="center" valign="middle">439</td>
<td align="center" valign="middle">Huaian City, China</td></tr>
<tr>
<td align="center" valign="middle">320100093</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">23</td>
<td align="center" valign="middle">284</td>
<td align="center" valign="middle">Huaian City, China</td></tr>
<tr>
<td align="center" valign="middle">320100088</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">2</td>
<td align="center" valign="middle">29</td>
<td align="center" valign="middle">517</td>
<td align="center" valign="middle">Yangzhou City, China</td></tr>
<tr>
<td align="center" valign="middle">320100089</td>
<td align="center" valign="middle">1</td>
<td align="center" valign="middle">2</td>
<td align="center" valign="middle">36</td>
<td align="center" valign="middle">416</td>
<td align="center" valign="middle">Yangzhou City, China</td></tr></tbody></table></table-wrap>
<table-wrap id="t5-sensors-10-06307" position="float">
<label>Table 5.</label>
<caption>
<p>Elements used in EMMNet.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="bottom"><bold>Data Collector</bold></th>
<th align="center" valign="bottom"><bold>Data Concentrator</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="top">ATMEGA128L</td>
<td align="center" valign="top">ATMEGA128L</td></tr>
<tr>
<td align="center" valign="top">ADL5320</td>
<td align="center" valign="top">ADL5320</td></tr>
<tr>
<td align="center" valign="top">nRF905</td>
<td align="center" valign="top">nRF905</td></tr>
<tr>
<td align="center" valign="top">sp6201</td>
<td align="center" valign="top">sp6201</td></tr>
<tr>
<td align="center" valign="top">PS2051</td>
<td align="center" valign="top">PS2051</td></tr>
<tr>
<td align="center" valign="top">--</td>
<td align="center" valign="top">SIM300C</td></tr>
<tr>
<td align="center" valign="top">AT45DB041D-SU</td>
<td align="center" valign="top">AT45DB642D</td></tr></tbody></table></table-wrap></sec></back></article>
