doc.: ieee 802.15- submission march, 2009 rachel reinhardt, paul smelser, time domain...

doc.: IEEE 802.15-<doc#>

Submission

March, 2009

Rachel Reinhardt, Paul Smelser, Time Domain CorporationSlide 1

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.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 922 9229], FAX: [+1 256 922 0387], E-Mail:[[email protected], [email protected]]

Re: [Response to IEEE P802.15.4f Active RFID System Call For Applications document number IEEE P802.15-09/0059r2]

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 IEEEP802.15.4f 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 P802.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 P802.15.

Doc.: IEEE 802.15-09-0174-00-004f


Submission

Slide 2

Applications for Active RFID

Rachel Reinhardt, Paul Smelser

Time Domain Corporation

March, 2009

Rachel Reinhardt, Paul Smelser, Time Domain Corporation

Doc.: IEEE 802.15-09-0174-00-004f


Submission

Slide 3

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?”

March, 2009


Doc.: IEEE 802.15-09-0174-00-004f


Submission

Slide 4

What is Active RFID Not?

• Passive RFID, with tags costing 20c 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– Mesh network

– Body area network

– Personal area network

– Local area network

March, 2009


Doc.: IEEE 802.15-09-0174-00-004f


Submission

The Standard Setting Process

Slide 5

Markets

Use Cases

Features

Requirements

March, 2009

Standard Development

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Slide 6

Markets

March, 2009 Doc.: IEEE 802.15-09-0174-00-004f



Submission

Slide 7

Market Segments Adopting Active RFID

• Significant adoption– Manufacturing

– Retail

– Healthcare

• Emerging Adoption– Corrections

– Simulation and Training

– Childcare

– Animal husbandry

March, 2009


– Sporting Events

– Transportation

– Supply Chain

– Entertainment

Doc.: IEEE 802.15-09-0174-00-004f


Submission

Slide 8

Use Cases

Requirements

March, 2009


Doc.: IEEE 802.15-09-0174-00-004f


Submission

Slide 9

Use Case Analysis

• There are too many markets to describe in detail, but use cases fall into several key categories across all markets

• Use case categories– Business automation and optimization

– Safety

– Security

– Statistics and monitoring

– Immersive Environments

March, 2009


Doc.: IEEE 802.15-09-0174-00-004f


Submission

Use Cases: Business Automation & OptimizationA Manufacturing Example

March, 2009

Slide 10

Cell 1

Cell 2

Cell 3

Cell 4

WIPPartsOperatorTool

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Business Automation & OptimizationA Manufacturing Example

March, 2009

Slide 11

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

People/Objects

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Business Automation & OptimizationA Healthcare Example

March, 2009

Slide 12

• Device associated with patient based on location• Patient-Device association enables automatic

collection of medical data• Automatic billing for use of device

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Business Automation & OptimizationA Healthcare Example

March, 2009

Slide 13



Patient = disposable

Device/Patient

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Business Automation & OptimizationA Supply Chain Example

March, 2009

Slide 14

Portal monitoringfor accountability

Area monitoringfor inventory

2D tracking for put-awayand safety

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Business Automation & OptimizationA Supply Chain Example

March, 2009

Slide 15



Items/Forklift

Doc.: IEEE 802.15-09-0174-00-004f


Items/Forklift


Submission

Use Cases: Safety SystemsA Manufacturing Example

March, 2009

Slide 16

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Safety SystemsA Manufacturing Example

March, 2009

Slide 17



Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Safety SystemsA Childcare Example

March, 2009

Slide 18

Nursery Activity Room

Playground

Reception Area

Annie leaving through reception area

All infants present in nursery

Johnny alone in activity room

Second supervisor required in play area

Warning: too many children near swing set

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Safety SystemsA Childcare Example

March, 2009

Slide 19



Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Security Systems / Loss PreventionAn Office Example

March, 2009

Slide 20

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

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Security SystemsAn Office Example

March, 2009

Slide 21



Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Statistics and Monitoring SystemsA Retail Example

• Analytics– Promotion evaluation

– Store layout optimization

• Marketing and customer experience– Store navigation

– Real time coupons

March, 2009

Slide 22

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Use Cases: Statistics and Monitoring SystemsA Retail Example

March, 2009

Slide 23



Doc.: IEEE 802.15-09-0174-00-004f



Submission

Slide 24

Features

Requirements

March, 2009 Doc.: IEEE 802.15-09-0174-00-004f



Submission

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– Low total cost of ownership

– Low maintenance

– Highly reliable

– Scalable

– Upgradeable

March, 2009

Slide 25

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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’

March, 2009

Slide 26

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 27

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 28

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 29

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Active RFID System Scalability

• Scalability has four forms– 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 and upgrade the system over time

March, 2009

Slide 30

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 31

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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.)

March, 2009

Slide 32

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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– 1D tracking for linear applications (e.g. production line)– 2D tracking– 3D tracking

• All modes must be supported and must be interoperable

March, 2009

Slide 33

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 34

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Slide 35

Requirements

March, 2009 Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 36

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Requirements Guidance – Optional Modes

March, 2009

Slide 37

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 and control

• Sensor data

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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? (!)

March, 2009

Slide 38

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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

March, 2009

Slide 39

Doc.: IEEE 802.15-09-0174-00-004f



Submission

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?

March, 2009

Slide 40

Doc.: IEEE 802.15-09-0174-00-004f



Submission

Slide 41

Requirements

Standard Development

March, 2009 Doc.: IEEE 802.15-09-0174-00-004f


doc.: ieee 802.15- submission march, 2009 rachel reinhardt, paul smelser, time domain...

Documents