doc.: IEEE 802. 15-09- 0611-01-004f Submiss ion September 2009 Adrian Jennings, Time Domain Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Time Domain Active RFID PHY Proposal] Date Submitted: [11 September, 2009] Source: [Adrian Jennings] Company [Time Domain] Address [330 Wynn Drive, Suite 300, Huntsville, AL. 35805. USA] Voice:[+1 256 759 4708], FAX: [+1 256 922 0387], E-Mail: [[email protected]] Re: [Response to Call for Final Proposals contained in IEEE P802.15-09- 0418-01-004f] Abstract: [Proposal describing two new PHYs for 802.15.4f to meet the requirements of an Active RFID system. A UWB PHY and a narrowband 2.4 GHz PHY are described.] Purpose: [For consideration in developing a draft standard for ballot] 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.
Transcript
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
September 2009
Slide 1
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Time Domain Active RFID PHY Proposal]
Re: [Response to Call for Final Proposals contained in IEEE P802.15-09-0418-01-004f]
Abstract: [Proposal describing two new PHYs for 802.15.4f to meet the requirements of an Active RFID system. A UWB PHY and a narrowband 2.4 GHz PHY are described.]
Purpose: [For consideration in developing a draft standard for ballot]
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.
• Cheap, small, long duration tags• Active RFID with location awareness (precise
location in many applications)• Flexibility to add functionality for more
complex applications and regulatory compliance
• Worldwide usage and coexistence
September 2009
Slide 5
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Outline Proposal
• UWB transmit-only tag for active RFID and location– Low cost, very low power consumption transmitter– Enables precise location
• Optional narrowband 2.4 GHz PHY for downlink to tag– Narrowband for better coexistence– 2.4 GHz receiver low cost and low power consumption
compared to UWB receiver– Enables regulatory compliance, security, and command link
to tags
September 2009
Slide 6
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Why the asymmetric link?
• To minimize power consumption, cost and size of tag• UWB transmitter advantages
– Required waveform for accurate location determination– Very simple, low cost, low power consumption
implementation
• 2.4 GHz receiver advantages– Very mature silicon available (low cost, small, low power
consumption)– Good link budget
September 2009
Slide 7
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
SYSTEM OVERVIEW
September 2009
Slide 8
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Basic Mode Of Operation
September 2009
Slide 9
UWB Reader
UWB Tag
Blink Frame
To application: Tag ID, decoded LEI
UWB 2.4 GHz
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Bidirectional Mode Of Operation
September 2009
Slide 10
UWB/2.4 GHz Reader
UWB/2.4 GHz Tag
Blink/Status Frame
To application: Tag ID, decoded LEI
From application: Commands
Commands
UWB 2.4 GHz
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Typical Infrastructure Layout
September 2009
Slide 11
UWB 2.4 GHz
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Optional Infrastructure Layout
September 2009
Slide 12
UWB 2.4 GHz
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Optional Infrastructure Layout
• Two factors drive option for reduced number of 2.4 GHz nodes:
• Link Budget– 2.4 GHz radio may have longer range, therefore
fewer nodes may be required
• In RTLS configuration– Tag must be heard by at least three readers– Tag only needs to talk to one 2.4 GHz radio– Therefore fewer 2.4 GHz nodes are required
September 2009
Slide 13
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Robustness Advantage Of Asymmetric PHY
• Probability of both propagation channels being unusable is small (or at least less than probability of one unusable channel)
• Infrastructure loses UWB link– Signals tag over 2.4 GHz link– Unlikely in RTLS network due to over-specification of UWB
coverage
• Tag loses 2.4 GHz link– Signals to infrastructure over UWB link– Useful LQI metric for potential 2.4 GHz channel change
September 2009
Slide 14
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY FUNDAMENTALS
September 2009
Slide 15
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY - Basics
• Pulsed UWB– Simple transmitter– Very low power consumption– Excellent location accuracy– Very high tag throughput
• 2 Mpps– No lower than 1 Mpps for regulatory compliance– Supportable by a wide range of low cost micro-
controllers and oscillators– Plenty of guard time for multipath (low ISI)
September 2009
Slide 16
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY - Modulation
• On-Off Keyed– Simplest possible transmitter– Can be demodulated by both coherent and non-
coherent (low complexity) receiver
September 2009
Slide 17
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Band Plan
• Bands are defined by spectrum regulations• Devices are optionally single region or multi-
region• Regional usage also depends on use of 2.4
GHz link
September 2009
Slide 18
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Band Definition
September 2009
Slide 19
Band # Fmin (GHz) Fmax (GHz) EIRP(dBm/MHz)
Band Edge (dBm/MHz)
1 5.925 7.250 -41.3 -51.3
2 6.000 8.500 -41.3 -70.0
3 7.200 10.200 -41.3 -51.3
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Regions Today
September 2009
Slide 20
Region 1
Region 2
Region 3
Region 4
Region 5
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY - Band Usage
September 2009
Slide 21
Band 2.4 GHz? Region 1 Region 2 Region 3 Region 4 Region 5
1No
Yes
2No *
Yes
3No **
Yes **
* Subject to current review * * 50 Mbps minimum data rate in Japan
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PHY HEADER
September 2009
Slide 22
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PHY Header Format
September 2009
Slide 23
Preamble SFD PHR
32pulses
16bits
19bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PHY Header Format
• Preamble contains all 1’s (pulses)• Requirement is energy detect and coarse
pulse alignment
September 2009
Slide 24
Preamble SFD PHR
32pulses
16bits
19bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – SFD
• The SFD is the 16 bit sequence0001 0011 0101 1110
• Chosen to provide– Robust alignment with up to 2 preamble/SFD bit errors– 8 pulses to function as primary LEI
September 2009
Slide 25
Preamble SFD PHR
32pulses
16bits
19bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PHR
• The PHR defines the frame length end error correction type for the remainder of the frame
• The PHR is itself encoded for robust reception
September 2009
Slide 26
Preamble SFD PHR
32pulses
13bits
19bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PHR
• Frame length: number of bytes in rest of frame• Encoding type: TBD. “0” denotes no encoding• SECDED bits: (19,13) Hamming block code as
defined in 802.15.4a (but note error in C5 equation in 4a)
September 2009
Slide 27
FrameLength
Encoding Type
SECDED bits
8bits
5bits
6bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – MAC HEADER
September 2009
Slide 28
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – MAC Frame
• Uses standard 15.4 MAC Frame
September 2009
Slide 29
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Frame control Fields
September 2009
Slide 30
Field ValueFrame Type 0b100 (new Blink frame type)
Security Enabled Optional (default 0b0)Frame Pending 0b0Ack Request 0b0PAN ID Compression 0b0Reserved 0b000Destination Addressing Mode ?? (See MAC Enhancements)Frame Version 0b10? (will this need to be incremented?)Source Addressing mode 0b11
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Sequence Number
• Same format as 15.4• Usage different:
– Used to aggregate LEI measurements for location determination
– One location calculation uses packets from all readers with same tag ID and same sequence number
September 2009
Slide 31
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Destination PAN ID
• Same format and functionality as 15.4• Particularly important for adjacent but non-
interacting RTLS networks
September 2009
Slide 32
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Unused Fields
• These fields are not required for RFID/RTLS functionality
• They are optionally zero in 15.4 so no change is required
September 2009
Slide 33
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Source Address
• This is more normally thought of as “Tag ID” in RFID parlance
• Standard 64 bit ID– 8 bits = Tag Class assigned by application– 56 bits = Tag ID assigned uniquely per tag
• Tag Class allows functional groups of tags to be addressed– E.g. “All garment tags switch to sleep mode”– E.g. “All forklift tags switch to 10 Hz blink rate”
September 2009
Slide 34
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Security Header
• Same format and functionality as 15.4• Optional
September 2009
Slide 35
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – FCS
• Same format and functionality as 15.4• CCITT algorithm
– x16 + x12 + x5 + 1
September 2009
Slide 36
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PAYLOAD FORMAT DISCUSSION
September 2009
Slide 37
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Payload Types
• An RFID tag that meets the requirements will have several modes of operation:– RFID: ID only– RTLS: ID + LEI– Sensor: ID + payload + special LEI (if
required)– Etc.
• Therefore, multiple payload types must be defined
September 2009
Slide 38
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Mandatory Blink Payload
• There is no payload for the mandatory Blink frame
• This is the minimum length packet possible– Preamble– SFD– PHR– MHR– FCS
• The SFD doubles as the LEI in this packet
September 2009
Slide 39
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Blink + Status Payload
• On receiving a beacon and/or mode change command over the 2.4 GHz link, the tag responds with a Status Packet
• The Status Packet includes– Command read-back (to confirm mode changes or
respond to mode queries)– LEI– ACK status– Link Quality Indicator (LQI)
September 2009
Slide 40
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Location Enablers
• Location determination can be enabled in three different ways:– Signal strength determination
• Doesn’t necessarily require a dedicated LEI– Pulse timing measurement
• Doesn’t necessarily require a dedicated LEI– Carrier phase information
• Requires a special LEI
• Coherent systems may also require special LEIs• Therefore multiple LEIs should be supported in additional
packet types
September 2009
Slide 41
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PAYLOAD FORMAT DEFINITION
September 2009
Slide 42
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Blink PPDU
The Blink PPDU contains no additional payload
September 2009
Slide 43
PHY Header MAC Header FCS
67bits
104bits
16bits
Packet Stats:
Bits: 187
Duration: 93.5ms
Energy: 49mJ
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Status PPDU
The Status PPDU contains additional ACK and LQI data and is only used by tags that include a 2.4 GHz downlink
September 2009
Slide 44
PHY Header
MAC Header
FCS
67bits
104bits
16bits
Packet Stats:
Bits: 267
Duration: 133.5ms
Energy: 60mJ
PayloadType
8bits
ParamIndex
8bits
ParamValue
16bits
BatteryStatus
2bits
AckStatus
2bits
Reserved
4bits
RSSI
8bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Status PPDU
• Payload type– 8 bits– Defines standard payload formats– One format is this proposed status PPDU– Others may included alternative LEIs etc.
September 2009
Slide 45
PayloadType
ParamIndex
ParamValue
BatteryStatus
AckStatus Reserved RSSI
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Status PPDU
• Parameter Index– 8 bits– Address of tag read/write parameter– Used as
• ACK for parameter change• Response to parameter value query
September 2009
Slide 46
PayloadType
ParamIndex
ParamValue
BatteryStatus
AckStatus Reserved RSSI
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – Status PPDU
• Parameter Value– 16 bits– Value of indexed parameter– Used as
• ACK for parameter change• Response to parameter value query
Receive Bandwidth MHz 1000 1000 1000Noise Temperature K 300 300 300Noise Figure dB 2.5 1.5 1.5kTBF dBm -81.3 -82.3 -82.3
Center frequency MHz 6600 6600 6600Path loss exponent 2 2 21m path loss dB -48.8 -48.8 -48.8
Tx Antenna Gain dB 0 0 0Rx Antanna Gain dB 5 5 5Implementation Losses dB 2 1 1Eb/No required dB 20 14 11Link Margin required dB 0 0 0Other Loss dB 0 3 3Other Gain dB 0 0.0 2.4Data Rate Mbps 1 0.33 0.33
Range Achieved m 48.6 150.6 279.0
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHZ PHY - FUNDAMENTALS
September 2009
Slide 58
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
Overview
• 2.4 GHz PHY provides optional downlink to tag– Regulatory compliance– Security– Functionality (e.g. tag mode changes)
• There is no 2.4 GHz uplink in this proposal– All data from tag to infrastructure uses UWB PHY– Minimizes tag power consumption
September 2009
Slide 59
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Band Plan
• Channel bandwidth: 296 kHz (99% occupied)• Center frequencies
– Start 2400 MHz– Then 333.251953 kHz steps– To 2483 MHz
• 249 Channels total available– It is expected that tags will support only a subset
for a given installation– Subset supported defined based on local RF
survey
September 2009
Slide 60
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Modulation & Data Rate
• MSK Modulation– Small occupied bandwidth– Lower side-lobe levels
• 250 Kbps data rate– Small occupied bandwidth– Reasonable packet duration– Good link budget compromise
September 2009
Slide 61
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHZ PHY – PHY HEADER
September 2009
Slide 62
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – PHY Header Format
September 2009
Slide 63
Preamble SFD
32pulses
16bits
PHR
8bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – PHY Header Format
• The preamble is an alternating sequence of 1’s and 0’s
1010101010….
September 2009
Slide 64
Preamble SFD
32pulses
16bits
PHR
8bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – SFD
• The SFD is the 16 bit sequence1101 0011 1001 0001
September 2009
Slide 65
Preamble SFD
32pulses
16bits
PHR
8bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – PHR
• 8 bits defining packet length
September 2009
Slide 66
Preamble SFD
32pulses
16bits
PHR
8bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHZ PHY - MAC HEADER
September 2009
Slide 67
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – MAC Frame
• Uses standard 15.4 MAC Frame
September 2009
Slide 68
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Frame control Fields
September 2009
Slide 69
Field ValueFrame Type 0b001 (Data)
Security Enabled Optional (default 0b0)Frame Pending 0b0Ack Request 0b0PAN ID Compression 0b1Reserved 0b000Destination Addressing Mode 0b11Frame Version 0b10? (will this need to be incremented?)Source Addressing mode 0b10
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Sequence Number
• Same format as 15.4
September 2009
Slide 70
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Destination PAN ID
• Not required for RFID/RTLS functionality• Optionally zero in 15.4 so no change is
required
September 2009
Slide 71
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Destination Address
• This is more normally thought of as “Tag ID” in RFID parlance
• Standard 64 bit ID– 8 bits = Tag Class assigned by application– 56 bits = Tag ID assigned uniquely per tag
• Tag Class allows functional groups of tags to be addressed– E.g. “All garment tags switch to sleep mode”– E.g. “All forklift tags switch to 10 Hz blink rate”
September 2009
Slide 72
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Source PAN ID
• Same format and functionality as 15.4• Particularly important for adjacent but non-
interacting RTLS networks
September 2009
Slide 73
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Source Address
• Not required for RFID/RTLS functionality• Optionally zero in 15.4 so no change is
required
September 2009
Slide 74
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – Security Header
• Same format and functionality as 15.4• Optional
September 2009
Slide 75
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY – FCS
• CRC 16 FCS– x16 + x15 + x2 + 1
September 2009
Slide 76
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
UWB PHY – PAYLOAD FORMAT DEFINITION
September 2009
Slide 77
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY –PPDU
The 2.4 GHz PPDU acts as ACK to tags, and also reads/writes parameter values
September 2009
Slide 78
PHY Header
MAC Header
FCS
48bits
120bits
16bits
Packet Stats:
Bits: 216
Duration: 864ms
Energy: 99.8mJ
PayloadType
8bits
ParamIndex
8bits
ParamValue
16bits
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY –PPDU
• Payload type– 8 bits– Defines standard payload formats– Only one format described in this proposal
• Standard ACK packet that double as parameter read/write
September 2009
Slide 79
PayloadType
ParamIndex
ParamValue
doc.: IEEE 802. 15-09-0611-01-004f
Submission
Adrian Jennings, Time Domain
2.4 GHz PHY –PPDU
• Parameter Index– 8 bits– Address of tag read/write parameter– Used as
