Project: IEEE P1451.5 Task Group for Wireless Smart Sensors Title: [Industrial Sensing Applications] Date Submitted: [23 Sep, 2002] Source: [Kenneth D. Cornett] Company: [Motorola, Inc.] Address: [8000 W. Sunrise Blvd., ms:22-9c, Plantation, FL 33322 Voice:954-723-6397, FAX: 954-723-3712, E-Mail:Ken.Cornett@motorola.com] Abstract: [Description of Market Opportunities for a Wireless Sensor Standard] Purpose: [Industrial Sensing Applications Vision.] Notice: This document has been prepared to assist the IEEE 1451.5. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P1451.5. Slide 1
Industrial Sensing Applications Vision Ken Cornett Motorola, Inc. Florida Communication Research Lab Plantation, FL Slide 2
Pervasive Wireless Device Network Applications Basic Requirement: Provide low rate, wireless interconnection of low cost sensor/actuator devices to enable a network to sense and affect the physical environment. Applications: Industrial/Commercial Sensing - HVAC & Lighting, Condition Monitoring - Environmental and Health Monitoring - Security, Location and Asset Tracking Emergency and Disaster Response Home Automation and Toys Slide 3
Our Cornerstones Consider node energy & system cost at all times: - Prioritize battery life above link range and data thru-put. - Use extended, low power sleep modes. - Tolerate transient, moderately high volume data (wake, burst, sleep). - Do NOT support isochronous quality of service (QoS). Network Characteristics (to be supported by PHY & MAC) - Scalable from home to large industrial control and monitoring. - Acknowledge successful receipt of every message. - Extend coverage by multi-hop (avoids increased multi-path interference). - Self-organize & re-configure (for rapid deployment & self-healing). - Assume nodes are primarily fixed, but support infrequent, low mobility. - Use non-ip addressing/routing below IP Gateway node (lower cost). - Use RSSI (and ideally intrinsic node location) to support network admin. - Operate in unlicensed, globally-available spectrum. Slide 4
Application Description Application Question Industrial Ap Consumer Ap 1 How many devices are in this low rate network? indefinite <255 2 What are the types of devices in that application? sensors and control elements; data processing and storage devices household appliances, sensors, alarms, toys 3 Describe how the network is initiated. Self-organizing upon deployment and activation. Self-organizing upon deployment and activation. How do devices attach and detach from the network? Is human 4 intervention required? Self-maintaining; no intervention required. Self-maintaining; no intervention required. 5 Describe the traffic flow of the data. indeterminate indeterminate 6 Describe the type of data that flows in each branch of the network. asynchronous packetized asynchronous packetized 7 How much data is typically in each message? <10 bytes <10 bytes <6 per hour; more 8 How often are messages sent? often in emergencies 0.1-10 per minute 9 How much latency in the message transfer is acceptable? 10 sec; less in emergencies 30 ms 10 Describe the network topology. bus star Is there a master node? Where do data flows originate and terminate? 11 Are the devices peer to peer or master/slave? no; peer-peer yes; master/slave Slide 5
Applications Description Application Question Industrial Ap Consumer Ap Does this network have to interface to another network? If so, how 12 should these two networks be connected? yes, through a gateway master must be able to interface with IP no; however, master can control multiple If two low-rate networks are in the range of one another, should they 13 interact? If yes, how? simultaneous networks yes, through a gateway Primarily status, What is the type of data that would flow between two low rate networks? control, and queries; 14 How often would they communicate? as necessary How should these two low rate networks connect when they are within Communicate range? Should they configure themselves into one network or only through gateways 15 communicate between master, for example? only 16 Do the devices support authentication and security? yes. yes. 17 What is the data traffic type? (asynchronous) asynchronous asynchronous 18 What are the battery life requirements? 1-3 years 1-3 years 19 What is the physical size of the low-rate transceiver? credit card credit card 20 What is the range requirement of the application? 1-30 m 1-30 m 21 What is the estimate market size (units) of the proposed application? Many millions Many millions 22 Will this application benefit from location awareness? What is the required position accuracy and update rate [x, y, z, t]? yes; <1 to 3 meters; on demand, or event driven, up to latency Primarily status, control, and queries; as necessary Communicate through master only yes; 1 meter; 10 s, on demand or event driven Slide 6
Requirements of Large Industrial Customers Low cost wireless nodes & systems - Wireless Sensing means eliminating ALL wires below the gateway node (including power) ALMOST all the time. Otherwise, labor cost & permitting overhead factors are not adequately reduced. - Most actuators will still have power (to drive whatever). - Bluetooth & 802.11b becoming de facto upper-limits on radio cost. Easy installation (to the point of transparency) - Should be easily handled by barely-skilled technicians. - Networks must be highly scaleable and self-organizing. Very low maintenance (approaching $0) - Batteries can be replaced very infrequently, if ever. - Should support remote diagnostic tools & services. Diverse needs for Privacy, Security, and Authentication. Ideally, transducers become the limiting factor. Slide 7
Appeal of Standards to Industrial Customers Open standards are valued by customers - because interoperable components & systems from competing vendors is good for them. (Healthy for the market in the long run.) - only if the Standard adequately meets their application s needs. Sensor applications are VERY diverse. - One size cannot fit all. Attempting to create one will satisfying few. A combination of 1451 + 802 standards covers the bases. - 802.11b & Bluetooth (a.k.a. 802.15.1) are already factors in the market. - 802.15.4 fills a previous void for low data rate, extended battery life. - More high-rate standards are on the way (802.11a-g, 802.15.3, etc.). - The standards process in 802 is very competitive and rigorous! - Industry Consortia for compliance testing & marketing have already been formed to support & promote several 802 standards. Lower costs by leveraging aggregate market volumes. Slide 8
In Motorola s View 1451.5 s winning move is to not play the (radio) game. - Position 1451.5 such that system designers can pick & choose Use the right tool for each job! - Allow 1451.5 to benefit from future innovations ASAP. For instance. 802.15.3 is already studying UWB as an alternate PHY layer. 1451.5 could propose to work with (or in) 802 working/task groups, influence future standards to address any deficiencies. - Season with essential ingredients for sensing where they add value. Slide 9
In Motorola s View The (missing) essential ingredients are: 1) A clear, simple method for dynamic discovery of sensor/transducer node attributes on an as-needed basis. We anticipate that this would be coordinated by the wireless network s gateway nodes, and is probably limited to them. 2) A software bridge on wireless gateway devices that will: - Enable communications between different wireless gateways (using the same or different RF protocols) and wired 1451.x systems. - Gateways become responsible for 1451.x message compatibility to the wired network without burdening the wireless networks (esp. low rate, battery operated) with unnecessary overhead. - Gateways coordinate dozens to (potentially) tens-of-thousands of wireless sensor nodes, and can tolerate the cost of additional processing, memory and electrical power resources. Slide 10