Doc IEEE 802 15 09 0174 00 004

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Applications for Active RFID Systems] Date Submitted: [9 March, 2009] Source: [Rachel Reinhardt, Paul Smelser] Company [Time Domain Corporation] Address [330 Wynn Drive, Suite 300, Huntsville, AL, 35805, USA] Voice: [+1 256 9229], FAX: [+1 256 922 0387], E-Mail: [rachel. reinhardt@timedomain. com, paul. smelser@timedomain. com] Re: [Response to IEEE P 802. 15. 4 f Active RFID System Call For Applications document number IEEE P 802. 15 -09/0059 r 2] Abstract: [Description of applications for Active RFID systems] Purpose: [This document defines applications of Active RFID in demand from end users and forms an input to the formal requirements for IEEEP 802. 15. 4 f in order to specify and later ratify a standard which will fulfill important market needs and promote widespread technology adoption. ] Notice: This document has been prepared to assist the IEEE P 802. 15. 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 P 802. 15. Submission Slide 1 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Applications for Active RFID Rachel Reinhardt, Paul Smelser Time Domain Corporation Submission Slide 2 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 What is Active RFID? • First and foremost, Active RFID is a technology for tagging people, animals or objects with a self-powered tag for the purpose of transmitting a unique ID across extended ranges Ø “What am I? ” • The majority of Active RFID applications also require precise tag location Ø “Where am I? ” • Some applications also require low rate communications to and from the tag Ø “How am I? ” Submission Slide 3 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 What is Active RFID Not? • Passive RFID, with tags costing 20 c or less • Battery Assisted Passive RFID, in which a small battery provides an extra boost to a passive tag to increase range • A communications network – – Submission Mesh network Body area network Personal area network Local area network Slide 4 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 The Standard Setting Process Markets Use Cases Features Requirements Standard Development Submission Slide 5 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Markets Submission Slide 6 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Market Segments Adopting Active RFID • Significant adoption – Manufacturing – Retail – Healthcare • Emerging Adoption – – Submission Corrections Simulation and Training Childcare Animal husbandry – – Slide 7 Sporting Events Transportation Supply Chain Entertainment Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases Requirements Submission Slide 8 Rachel Reinhardt, Paul

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Case Analysis • There are too many markets to describe in detail, but use cases fall into several key categories across all markets • Use categories – – – Submission Business automation and optimization Safety Security Statistics and monitoring Immersive Environments Slide 9 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Manufacturing Example Cell 1 Cell 2 WIP Parts Operator Tool Cell 3 Cell 4 Submission Slide 10 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Manufacturing Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 11 People/Objects Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Healthcare Example • Device associated with patient based on location • Patient-Device association enables automatic collection of medical data • Automatic billing for use of device Submission Slide 12 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Healthcare Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 13 Patient = disposable Device/Patient Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Supply Chain Example Portal monitoring for accountability Area monitoring for inventory 2 D tracking for put-away and safety Submission Slide 14 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Business Automation & Optimization A Supply Chain Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 15 Items/Forklift Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Safety Systems A Manufacturing Example Submission Slide 16 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Safety Systems A Manufacturing Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 17 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Safety Systems A Childcare Example Reception Area Annie leaving through reception area Nursery Activity Room All infants present in nursery Johnny alone in activity room Playground Second supervisor required in play area Warning: too many children near swing set Submission Slide 18 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Safety Systems A Childcare Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 19 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Security Systems / Loss Prevention An Office Example Company owned item being loaded into customer shipment in shipping and receiving Security tag recognizes tamper activity Unauthorized removal of company owned item to front lobby Submission Slide 20 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Security Systems An Office Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 21 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Statistics and Monitoring Systems A Retail Example • Analytics – Promotion evaluation – Store layout optimization • Marketing and customer experience – Store navigation – Real time coupons Submission Slide 22 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Use Cases: Statistics and Monitoring Systems A Retail Example Critical Functionality Y/N Small, cheap, low power consumption tag ID only functionality Location accuracy High tag ping rate High tag capacity Tag call button Communications to tag Communications from tag Submission Slide 23 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Features Requirements Submission Slide 24 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Global Features for All Markets and Use Cases • Every customer wants the tag to be – As cheap as possible – As long lasting as possible (battery) – As small as possible • Additionally, the full system is always required to be – – – Submission Low total cost of ownership Low maintenance Highly reliable Scalable Upgradeable Slide 25 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Tag Cost • The perfect tag is free! • The next best tag is disposable • Customers will not pay more for a tag with unwanted features, for example: – ‘If I only need the tag to last 30 days (disposable) then I don’t want to pay for a 10 year battery’ – ‘If I don’t need a push button and LED indicator on the tag, I want a plain, no-frills active tag’ – ‘If I don’t want to talk to the tag, I want a cheaper, transmit -only tag’ Submission Slide 26 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Tag Power Consumption • The perfect tag lasts forever! • The next best tag has a life of at least 4+ years (preferably longer) • However, some applications require only short duration tags – E. g. disposable patient tags – Drives desire for thin film batteries, with very low capacity • Energy harvesting systems are also desirable for future tags Submission Slide 27 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Tag Size • The perfect tag is smaller than a speck of dust! • Many applications drive very small tags – – Infant or elderly patient tags Tags for clothing Tags for tools Etc. • Just like cost and power consumption, tag size cannot be compromised by unneeded functionality Submission Slide 28 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Active RFID System Total Cost of Ownership • Total cost of ownership is much more than reader price – – – Cost of readers Number of readers required Ease/cost of installation Ease/cost of set up Maintenance Reliability • Minimizing TCO drives complex calculation – Longer range is not necessarily cheaper if the readers are expensive – Cheap, shorter range readers are not necessarily better if the installation cost is high Submission Slide 29 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Active RFID System Scalability • Scalability has four forms – – Submission The ability to track a large number of tags The ability to add layers of capability The ability to enable multiple applications The ability to expand upgrade the system over time Slide 30 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 System Scalability – Many Tags • Small or large installations may have many thousands of tags • Tags may be operating at slow update rates (for assets) to very high update rates (for safety systems) • This means that tag capacity (tags per second) is a very important parameter Submission Slide 31 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 System Scalability – Layers of Capability • Applications require varying levels capability • These range through various levels – Transmit-only tags for proximity, location and accountability – Transmit-only tags with very small data payloads (e. g. push button, temperature) – Location tags with a control link to the tag (e. g. mode setting, regulatory compliance) – Location tags with two way low-rate communications (command/control for attached devices, sensor data etc. ) Submission Slide 32 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 System Scalability – Multiple Applications • A single system might have one or many operating modes: – – – Wide area proximity detection for tag counting Choke point proximity detection for portal monitoring 1 D tracking for linear applications (e. g. production line) 2 D tracking 3 D tracking • All modes must be supported and must be interoperable Submission Slide 33 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 System Scalability – Upgrade/Expand • This is a combination of all the scalability features • Just as a system may span many applications over a wide area, so a user may add applications over time • An active RFID must be easy and cheap to install for a single application in a very small area, and have the capability to grow into many applications over a very wide area Submission Slide 34 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Submission Slide 35 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Guidance – Mandatory Modes • Mandatory modes should enable the minimum functionality (transmit-only active RFID) so as not to compromise – – Price Size Power consumption Tag capacity • Mandatory modes should ensure interoperability between vendors, but not constrain present or future receiver technologies and implementations Submission Slide 36 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Guidance – Optional Modes Optional modes should add value for the subset of applications that require more than basic functionality – Very low rate data from the tag • Push button, etc. – Very low rate data to the tag • Visual/audible indicator • Mode setting (e. g. ping rate) • Regulatory compliance, etc – Low rate two way data • Command control • Sensor data Submission Slide 37 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Guidance – Performance Parameters Performance parameters should reflect real world requirements. Questions to consider: – What location accuracy is required to enable these applications? – How best to minimize TCO, understanding that range of operation is just one input? – What are realistic numbers for tag density (# tags in one place) and total tag capacity (total tags in system)? – What kind of sensor data is likely to be included? Do we really need to stream video? (!) Submission Slide 38 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Guidance – Key Performance Parameters • Key Performance Parameters (KPPs) should be set • KPPs are those 3 or 4 requirements that, if not achieved, would signify a standard of little practical value. • Some KPP examples – Tag power consumption in mandatory mode – Location accuracy – Worldwide regulatory compliance Submission Slide 39 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Guidance – Active RFID System Considerations • Interoperability is paramount – Systems will be deployed in safety of life applications and a Wi-Fi network (for example) should not bring it down. • Security – How much is required if no data association occurs until it reaches a central server? • Network – How much overhead do we need to endure for the simplest applications? • FEC – How many electrons so I want to use up with fancy encoders when I have to send another packet anyway for location purposes? Submission Slide 40 Rachel Reinhardt, Paul Smelser,

Doc. : IEEE 802. 15 -09 -0174 -00 -004 f doc. : IEEE 802. 15 -<doc#> March, 2009 Requirements Standard Development Submission Slide 41 Rachel Reinhardt, Paul Smelser,