2009年6月17日 星期三
The Third Wireless Evolution – Sensor Networks?
From Symbian developer's journal
If you ever had the foresight in 1970 to wonder along what sequence of events wireless technologies would start penetrating society, you probably would not have started first with high quality voice networks, then followed with high speed data-networks and finally ended with low data rate, low duty cycle simple sense and control networks. Most likely you would have suggested a sequence the other way around: let's start "slow and easy" with sense and control networks (sending temperature information every 5 minutes and control our heaters or air conditioners); then you may have guessed that this would have been followed by more complex data networks, as a higher speed next generation data network, and finally the wireless revolution would have been completed with the most complex voice networks with its high demands on low latency and high quality.
Not so. The first revolution was about wireless voice networks, in two steps: in-house and then outdoors (DECT/GSM). The second revolution was about wireless high speed data (Wi-Fi) in every laptop, you can't buy them without it anymore. And finally, the third wave with sense and control networks (ZigBee)?
Actually: remote controls for our televisions have been around for a while, our remote keys for our cars, for our garage door openers. But that never grew out of the stage of the wireless extension of a push button... Something feels wrong with this picture, what are we missing?
As usual the devil is in the details and going back to the 70-ies, it seemed that we missed an essential point, the usage model. And interestingly, only very recently we have started to pick up on this. The difference between voice and data networks on one side and sense and control networks on the other side is how to use these. We are used to live with handling a phone or a laptop and make sure that the batteries are charged - actually we have learnt it the hard way ("Where can I find an outlet?" Or worse: "I forgot my adaptor"). But with sense and control networks we need a "use and forget" model, that is, we do not want to be bothered with making sure that we have to regularly charge our remote control(s) or our car key(s)... and here is where trouble starts.
Let take our "house of the future"... remote controls for switching on/off lights; temperature sensors; motion sensors (whether someone is in the room) for comfort or security, etc. Without having to be too creative we can easily calculate 50 sensors (actually a not too sophisticated car has already 50 sensors today). Well... let's assume a battery life of 1 year per sensor. This means that we have on average to change a battery every week. And worse: to find out which battery we have to change, we will have every week at least one sensor down. OK, battery life will increase, but so will the number of sensors.
But there is more, and everyone who has a wireless switch in his house for a lamp will recognize this. In the past if a lamp does not work, well... change the bulb. But with a wireless switch this game has changed. If a lamp does not work, what is the problem: is the bulb broken, or is the battery of the switch empty?
All of a sudden "changing a bulb" has become a "diagnostics problem", with different possible outcomes: the lamp is broken, the battery is empty (,or both!?). All of a sudden something as simple as "changing a light bulb" is not anymore what it has been.
So, after all there is a simple explanation that the acceptance of sense and control networks is lagging compared to their sophisticated cousins in voice and data and this has nothing to do with the network sophistication, it is purely about the usage model: ease of installation/maintenance (and: "fix and forget").
With the arrival of standards for sense and control networks, as well as with the increased possibilities for energy harvesting out of the environment (solar cells, motion energy), all the focus is going towards making these networks low maintenance, or better: total maintenance-free - and this will become the time of arrival of the third wireless wave, that originally was considered to be the most simple one.
2009年4月2日 星期四
不需電池 能量採集技術魅力足
那 些永久性裝置的關鍵特性,就是他們能無限期執行任務,而且使用者不用擔心換電池的問題。在美國加州嵌入式系統會議(Embedded Systems Conference)期間的一場能量採集技術座談會上,與會者針對二十年來該技術的發展歷程分享了不少意見;多數人都認為,無線與低功耗電子元件的發 展,以及感測器、MEMS等元件的演進,是對今日能量採集技術造成基礎性變革的因素。
德州儀器(TI)的工程經理Dave Freeman表示,低功耗電子元件與無線技術的發展,讓能量採集技術打開在許多應用領域的「能見度」。伊利諾大學(University of Illinois)副教授Patrick Chapman也同意,由於無線通訊元件的功耗越來越低,是讓小型能量採集裝置終於找到「用武之地」的主要因素。
自動化解決 方案供應商EnOcean的應用工程師Eugene You補充指出,無線元件的成本越來越低、讓永久性裝置的應用越來越廣泛,這也是量採集技術日益蓬勃發展的原因。電池製造商Cymbet的行銷副總裁 Steve Grady還表示,使用能量採集裝置也會需要電力儲存設備,例如該公司正在開發的一種長壽命薄膜電池。
但無論是哪一種新技術,都需要有大量需求來推波助欄,才能降低技術的成本,並使該技術成為廣泛應用的主流;而能量採集技術的「殺手級應用」為何?
MEMS技術專家Perpetuum的業務開發總監Keith Abate認為,答案是無線應用;TI的Freeman則指出,許多不同應用的「無線感測網路」將會推動能量採集技術的普及。而Cymbet的Grady將智慧建築(smart buildings)與智慧監測(intelligent monitoring)方案視為能量採集技術的殺手級應用:「我認為各種經濟振興方案將有助於增加能量採集技術的應用。」
伊利諾大學的Chapman透露,最近的技術新進展讓MEMS感測器未來可能變成具備能量採集技術的元件;而他認為,可能需要植入人體的醫療感測器應用會是上述這類能量採集元件的殺手級應用。而能量採集技術應用的「聖杯」,也就是該技術與無線元件或感測器的結合。
透過能量採集裝置的協助,一套系統能收集/處理資訊、或是傳送並分析其內容;而這類資訊的共通性也是一個需要關注的議題。對此Cymbet的Grady則認為,在該領域使用網際網路通訊協定(IP)是合適的,如此一來,收集自不同無線感測網路的資料就能整合在一起。
不過使用IP的問題在於,這對無線元件的耗電量太大,此外如果使用IP,就需要為成千上萬個感測器都指定一個IP位址。而針對各種無線感測網路開發標準通訊協定的工作,目前還僅在起步階段。
Grady表示,無線感測網路可使用的技術,包括Wi-Fi、藍牙(Bluetooth)、Zigbee等等;但若缺乏共通性,恐怕難以形成真正的能量採集殺手級應用。
(參考原文:Advancements in wireless, sensors and MEMs are set to change energy harvesting ,by Junko Yoshida)
2009年3月19日 星期四
To ZigBee or Not to ZigBee? Factors to consider when selecting ZigBee Technology
RF Designline
The explosion of wireless technologies in recent years has allowed the emergence of several standards, especially in the Industrial Scientific & Medical (ISM) band. Among these emerging standards ZigBee is considered one of the most promising. Analysts are forecasting several hundreds of millions of ZigBee-enabled devices in coming years. Without a clear understanding of whether or not the ZigBee standard is the right fit for their application, many engineers have been developing new products based on the ZigBee platform. This article aims to help engineers answer a fundamental question when faced with selecting ZigBee technology: Is ZigBee the right technology platform for the next product to be developed?
ZigBee Platform Overview
The ZigBee standard is supported by a consortium of over 200 companies grouped under the name of ZigBee Alliance. The goals driving the ZigBee Alliance are the creation of a reliable, low-cost, low-power, open global standard for low data rate wireless solutions, while allowing multi-hop routing of data. The ZigBee standard through mesh network capability and AES 128-bit encryption provides support for self-healing and high security. Figure 1 describes a ZigBee network topology which typically includes three types of devices or nodes:
Coordinator : One coordinator exists in each network. It starts the network and handles management functions as well as data routing functions. These functions require that the coordinator always be powered. Therefore, this type of node is recommended to be main-powered.
Routers: In most cases, routers are also main-powered. They help carry data across multi-hop ZigBee networks including a variable number of routers and, in some cases, are without routers, thus, transforming the network into a point-to-multipoint.
End Devices: These are devices that are battery-powered due to their low-power consumption. They sleep most of the time and wake up regularly to collect and transmit data. Devices such as sensors are configured as end devices. They are connected to the network through the routers.
The type of node is assigned during the commissioning process. The main-powered requirement for coordinators can be a limiting factor for ZigBee, especially if minimizing power consumption is actively targeted for each and every device.
As the number of nodes in a ZigBee network increases, potential communication bottlenecks can occur in some parts of the network. Two main techniques can be used to limit the congestion issue within ZigBee networks:
- Through node placement and adequate ZigBee router coverage within an installation area. This provides multiple paths for messages to reach a concentrator and alleviates potential bottleneck points in the network.
- Use several data concentrators instead of a single concentrator. This can reduce the number of hops required for nodes for their messages to reach a concentrator, and also reduces the chance of having a single point of failure.
In addition to the three methods mentioned earlier, techniques such as network partitioning through channel or PANID (or network ID) are available to deal with the ZigBee network congestion. These techniques, however, can be resource intensive.
Taking a close look at the ZigBee stack can help better understand challenges that implementing ZigBee can pose, especially when choosing a hardware platform. The ZigBee technology stack architecture has utilized the IEEE 802.15.4 standard, adding a set of layers to it to achieve the targeted features. Figure 2 describes the ZigBee stack architecture topology.
Two lower layers, the physical layers (PHY) and the media access layer (MAC) are defined by the IEEE 802.15.4 specification. The PHY deals with the implementation of the direct sequence spread spectrum (DSSS) radio hardware in both 2.4GHz and sub-1GHz band, while the MAC handles access to the PHY layer. The above layers are defined by the ZigBee Alliance, except the application layer which is defined by the end user.
The layers defined by the ZigBee Alliance are respectively: the network layer, the application framework layer, and the application profile layer. The routing and the mesh capability are defined within the network layer. The security features implemented within the ZigBee stack are very flexible as it can be implemented in any of the layers. Security also can be defined for the application framework by the profile. The application profile plays a big role in the standard interoperability by helping implement a common data exchange protocol as well as a set of processing actions.
The application profile layer specifies the application domains and allows devices from different manufacturers to communicate with each other. Profiles for a specific application regroup different related ZigBee clusters library that specifies functional domains within that application. As of today, the ZigBee Alliance has defined three application profiles: Smart Energy, Home Automation and Personal Home and Hospital Care (PHHC). Several other profiles are expected to be completed in the near future. It is always possible for the users to implement their own profile, therefore, making the application proprietary.
The application layer in which the application code is implemented, is fully owned by the end user to control the specific application.
By analyzing the ZigBee stack architecture, you can appreciate its role when the end user chooses a processor. It is imperative that you use a high code efficiency, and large memory size processor when dealing with ZigBee in certain applications such as Smart Energy. The performance required from the processor can vary from one processor vendor to another for the same ZigBee stack. This factor should be carefully weighted during the ZigBee platform selection process.
To ZigBee or Not to ZigBee?
While ZigBee technology presents attractive features, several factors need to be analyzed before selecting the technology. A poor analysis of these factors could result in a very cost-inefficient product. Consider the following factors when selecting the technology process:
- Interoperability: The need for interoperability is a major factor in choosing ZigBee , especially when the product developed is expected to communicate with other manufacturer's devices. If interoperability is not required or desired, then a proprietary solution could be considered for the sake of cost efficiency.
- Power consumption: As the coordinator and routers in the network always need to be "ON," using the main power is highly recommended.
- Software overhead: ZigBee has the characteristic of high software overhead due to the stack size. ZigBee is not recommended for applications targeting very low CPU resource use such as CODE/RAM.
- Full mesh network: The benefit of the mesh configuration is to enable data exchange between points through multi-hoping link. A network of sensors in a large building could be a good example. In such a case ZigBee might be a perfect platform. However, a smart use of a star network provided by IEEE 802.15.4 standard or some other proprietary protocols can help route data at a cheaper cost.
Many engineers are snared by the attractiveness of the ZigBee technology, and possibly overlook solutions that could have helped design more cost-efficient products. In this article we presented an overview of the ZigBee technology as well as possible limitations. We also explained the main factors to considered, avoiding any pitfalls during the technology selection process.
References:
- To learn more about the ZigBee Alliance, visit: http://www.ZigBee.org/
- For more information about the IEEE 802.15.4 standard, visit: http://standards.ieee.org/getieee802/802.15.html.
- For more ZigBee solutions from Texas Instruments, visit: www.ti.com/ZigBee .
About the Author
Iboun Sylla is currently managing business development in the Americas for Texas Instruments Low Power RF products. Prior to this position, Iboun was a senior RF design engineer. Iboun received his Bachelor in Telecommunications Engineering from ESPT (Tunis-Tunisia), and his Master's and PhD in Electrical Engineering from Ecole Polytechnique de Montreal, Canada. Iboun also holds a Master's in Business Administration from the University of Texas at Dallas with focus on Corporate Finances and Strategic Leadership. Iboun can be reached at: ti_ibounsylla@list.ti.com.
2009年2月19日 星期四
ZigBee vs. IPv6
Something is bothering me. I keep hearing that ZigBee and 6LoWPANare competing technologies. The ZigBee Alliance has taken a stand to force such a confrontation. Its like comparing apples and, well, New York
6LoWPAN = IPv6 = The Internet
Think about it. The Internet… the most successfull, innovative, massive network ever created. Now what was that Zig thing called again? Does anyone even remember the proprietary, link-specific networking protocols from the 90s?
Here is why ZigBee is not competetive, and shouldn’t be compared to 6LoWPAN and IPv6:
- ZigBee = small-scale isolated ad-hoc networking. 6LoWPAN = massively scalable networking as an end-to-end part of the Internet, it is IPv6!
- ZigBee = limited to a single radio standard. 6LoWPAN = applicable to any low-power, low-rate wireless radio (or even wired! See Watteco). IP protocols tie together heterogeneous networks.
- The only good part of ZigBee is application protocol profiles. And guess what, there is an IETF specification for using ZigBee profiles over UDP/IP. http://www.ietf.org/internet-drafts/draft-tolle-cap-00.txt
- ZigBee is not a standard, it is a special interest group. Will it be around in a few years? The IETF produces open, long-lived, standards. IPv6 will be around for 20+ years.
- Large-scale enterprise automation, M2M, metering systems etc. require end-to-end addressing, security, mobility, traffic multiplexing, reusability, maintainability, and web-services which are globally scalable… this is the kind of thing IPv6 was designed for.
I only see one option for ZigBee, and that is to get properly networked. I bet soon we’ll be seeing something called ZigBee/IP 2010.
ZigBee over UDP/IPv6
2009年2月10日 星期二
The ISM Revolution: The Next Big Thing
RF Designline
(02/09/2009 1:48 H EST)
Imagine a farmer in the American Midwest facing the challenges of tracking the temperatures of 1000 head of cattle daily in order to prevent some animal diseases such as foot and mouth disease from decimating his herd. With wireless technology, such challenges can be easily overcome by simply attaching a temperature sensor equipped with a wireless transmitter on each cow, transmitting its reading to a main terminal. Such a method helps save time and the costs of dispatching crews for frequent and more often than not, unnecessary measurements. This illustrates the level of penetration of the low-power wireless devices operating in the ISM frequency band into everyday life (security, medical, industrial, agricultural, etc.). This penetration is being driven by three main factors:
- The desire to get rid of hardwired communications that are otherwise required for transmitting data over a long range.
- The allocation of the Industrial Scientific & Medical (ISM) frequency band by the regulatory bodies of various countries.
- The emergence of different wireless standards to offer interoperability in the ISM band.
Eliminating Wire Wherever and Whenever Possible
For a long time, hardwired communication has been the most reliable way of transmitting or receiving information between two points. Wired communication systems have been able to provide reliable transmission media as well as high speed along with a long life. While presenting many qualities, the wired solution presents limitations that tend to make it obsolete in favor of wireless technologies. Among these limitations are:
- Geographic: Depending on geography and terrain, wire becomes very challenging to install, especially in rural mountainous areas.
- Economic: The cost of the wired system is proportionally related to the length of wire required as in some cases repeaters are needed to compensate for the loss of signal strength. This implies that more cable translates into more costly solution.
- Comfort: When looking at today's consumer desires, dragging wire across certain places is highly undesirable. Therefore, wire systems are being considered as the last choice for consumers.
These three main limitations of wire transmissions explain the momentum gained by the wireless technology.
The Industrial Scientific & Medical (ISM) Band
The ISM band is a general purpose part of the radio spectrum that can be used without a license. The only requirement for developing products in the ISM band is compliance with rules governing this part of the frequency spectrum. These rules vary from country to country. In the US, the Federal Communication Commission (FCC) defines these rules, whereas ETSI is the governing body in Europe. Table 1 illustrated how FCC and ETSI have categorized devices functioning in the ISM band.
Systems designed in the ISM band are characterized by their low-power and low data rates. However, in recent years, data rates have been increasingly higher, challenging the designation of low data rates. Mostly used ISM bands are the 2.4GHz band and the sub-1GHz bands. Because of the cluttering in the 2.4GHz bands, some activities have been seen in the 5GHz band, but they remain very limited because of achievable range concerns. While the 2.4GHz is universal, the sub-1GHz bands allocated to the low-power wireless application vary from country to country. In the United States the most popular band remaining is the 902 " 928MHz band, whereas in Europe most activities are in the 868MHz. Understanding the fundamental differences between the 2.4GHz and the sub-1GHz band is an important factor when developing products in the ISM band.
The 2.4GHz band is recommended when interoperability with other systems is required as well as operation in different geographical spaces is a key target. Designing in the 2.4GHz presents two main challenges:
- Numerous wireless systems such as Bluetooth, Wi-Fi, 802.15.4, Zigbee and Microwave ovens operate in this band. Therefore, high interference levels pose a formidable challenge. The presence of these interference sources requires high frequency selectivity devices to ensure a good wireless link quality. Another efficient way to counter interference is to use techniques such as frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS) that provide more significant noise immunities.
- The second challenge of choosing the 2.4GHz lies in its achievable range. The 2.4GHz frequency tends to be absorbed more readily by the environment and surrounding objects, limiting the range. The rule of thumb is doubling the frequency of operation reduces the range by one half. It is worth noting that the range limitation can be overcome with the use of an external power amplifier (PA).
Choosing to design in the sub-1GHz band helps solve some of the issues faced in the 2.4GHz band; however, the sub-1GHz has its own limitations such as:
- The duty cycle in this band is restricted.
- Impossibility of achieving interoperability with other systems.
- Geographical limitation in the operation, for example: a wireless meter designed in the 902 " 928 MHz band for the US will not be able to operate in Europe.
Different Standards in the ISM Band
The last few years have witnessed the emergence of several wireless standards operating in the ISM band. These standards, along with proprietary solutions provide huge opportunities for developing a wide range of wireless products. These standards differ from each other by their data rates, communication ranges, application domains, as well as the modulation techniques used. Figure 1 illustrates the range versus data rate of several wireless standards.
Among the wireless standards cited on Figure 1, Bluetooth, Wi-Fi, Zigbee and IEEE 802.15.4 can be considered as the most prominent today. Most of these standards are operating in the 2.4GHz band.
- Bluetooth: This technology is based on the IEEE 802.15.1 standard. It is a wireless technology that enables devices to communicate in the 2.400 " 2.4835 GHz band. Bluetooth allows devices such as mobile phones, PDAs, printers, laptops and headsets to exchange data. It uses the Gaussian frequency shift keying (GFSK) type of modulation along with frequency hopping spread spectrum (FHSS). Three output power levels are available in the Bluetooth standards. Classes 1, 2 and 3 devices deliver 20dBm, 4dBm and 0dBm of output powers respectively. Recently, another variant of Bluetooth called Bluetooth Low Energy has been introduced by the Bluetooth SIG. Bluetooth Low Energy targets data exchange using lower power consumption than the earlier Bluetooth versions.
- Wi-Fi: As of today it represents the most prominent technology for wireless connectivity for computers and internet. Wi-Fi technology integrates most personal computers, PDA and other devices such as gaming and portable audio devices. Wi-Fi term is applicable to wireless devices that utilize the suite of IEEE 802.11 standard. Excepted 802.11b, WI-FI standard operates in the 2.4GHz band (2.4GHz " 2.4835GHz) and use FHSS and DSSS techniques. One area of concern of the 802.11 technology is the security of the network, as WLAN network can be penetrated by a third party.
- IEEE 802.15.4: Compared with Bluetooth and WI-FI/802.11, IEEE 802.15.4 targets low data rate application within the 868MHz, 915MHz and 2.4GHz bands. The number of channels and the data rates used in this standard vary with the chosen frequency band. The most popular frequency band is the 2.4GHz with 20 available channels with a maximum data rate of 250kbps. The primary target application of this standard is home automation, remote metering, gaming and wireless sensors networks. One key feature of the IEEE 802.15.4 standard is its low-power consumption ability, providing a long battery life (10 to 20 years).
- Zigbee: Built on top of the IEEE 802.15.4 PHY layer, Zigbee is a standard that utilizes the 802.15.4 standard. The 2.4GHz band remains the most used frequency band for Zigbee. To resolve the range and interference issue faced in the 2.4GHz, some companies are exploring the design of 915MHz Zigbee products. Unlike IEEE 802.15.4, Zigbee allows full mesh network. The announcement by utility companies of the deployment of several millions of Zigbee-based electric and gas meters has built a tremendous momentum for Zigbee and its smart metering applications.
In addition to the wireless standards presented above, the wireless industry is experiencing the emergence of several new standards that are in early development stages. On the other hand, many applications still remain proprietary as companies are concerned about compatibility with legacy products.
The world is experiencing a wireless revolution that is democratizing this very practical technology. Its use in all segments of life is not without problems for governing regulatory bodies that are at the center of more solicitations to make new frequency bands available. A careful and well thought out frequency spectrum management is required.
The second challenge highlighted by this revolution is the need of inventing new techniques to handle more interferers resulting from the crowdedness of the frequency spectrum.
About the Author
Iboun Taimiya Sylla manages business development for Low-Power RF products at Texas Instruments. Prior to his current position, Iboun was a Sr. RF Design Engineer. Iboun received his Bachelor in Telecommunication Engineering at ESPT, University of Tunis, Tunisia). He received his Master and Ph.D in Electrical Engineering from Ecole Polytechnique de Montreal, University of Montreal, Canada. He also holds a Master's in Business Administration with focus on Corporate Finance and Strategic Leadership from the University of Dallas, Texas.