1 / 15

Wireless Interface Options for 1451

Wireless Interface Options for 1451. Presented at Sensors Expo San Jose, CA May 20, 2002. Mike Moore Steve Smith Oak Ridge National Laboratory. Presentation Sections. Key Goals of Standard Other Standards That Can be Leveraged IEEE 802 IT Architecture Various PHY components

unity-ballard
Télécharger la présentation

Wireless Interface Options for 1451

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wireless Interface Options for 1451 Presented at Sensors Expo San Jose, CA May 20, 2002 Mike Moore Steve Smith Oak Ridge National Laboratory

  2. Presentation Sections • Key Goals of Standard • Other Standards That Can be Leveraged • IEEE 802 IT Architecture • Various PHY components • Variety of Nodes • Sensor, Network, Repeater, etc.

  3. Key Elements of Sensor Standard • TEDS (Transducer Electronic Data Sheet) • Synchronization of Data Sampling • Unique Identification of Transducer • Accessibility to Networks (e.g. Internet) • Plug-and-Play Sensor Connections

  4. Candidate 1451 MAC/PHYFrom Other Wireless Standards • Use IEEE 802 Family As a Model • Use TEDS features from IEEE 1451.x (esp. .3) • Look at PHY options from other standards • IEEE 802.15.1 • IEEE 802.15.4 • RTLS, others • Use Unique ID functionality based on the MIT AutoID’s ePC program.

  5. Candidate 1451 MAC/PHY From Other Wireless Standards OFDM =Orthogonal Frequency Division Multiplex FHSS = Frequency Hopping Spread-Spectrum DSSS = Direct-Sequence Spread-Spectrum

  6. Existing IEEE 802 Wireless Projects • IEEE 802.15 • 802.15.1 (Bluetooth) • 802.15.2 (Compatibility) • 802.15.4 DSSS PHY longer-range, lower-power option • IEEE 802.11 • Clause 14 - 1,2 Mbps FHSS LAN MAC for 2.4 GHz • Clause 15 - 1,2 Mbps DSSS LAN for 2.4 GHz • IEEE 802.11a • Adds Clause 17 - £54 Mbps OFDM LAN for 5 GHz • IEEE 802.11b • Adds Clause 18 - 5.5 and 11 Mbps DSSS for 2.4 GHz • IEEE 802.16b (Task group 4) Wireless High-Speed Unlicensed Metropolitan Area Network (Wireless HUMAN) • MAC: IEEE 802.16 • PHY: IEEE 802.11a; ETSI BRAN HIPERLAN/2

  7. The Layered 802 Family ArchitectureProvides a Good Framework for Organizing the 1451 Family of Standards

  8. IEEE P1451.5 Should Accommodate the Rapidly Changing Wireless Arena App Layer 1451.1 Object Model Data Link Layer 1451.5 Tblock MAC/ Wire- less 1451.4 Tblock MAC/ MMI 1451.3 Tblock MAC/ HPNA 1451.2 Tblock MAC/ TII 1451 PHY 1451.5a (802.15.1) 1451.5b (802.15.4) RTLS Other

  9. Real-Time Locating System (RTLS) user community is seeking a generally similar solution to IEEE P1451.5 Replies to “What user need(s) does RTLS solve?” ·One air interface · Wireless telemetry · Global license-free frequency (e.g., FCC Part 15) · Non-interfering / non-susceptible to interference from wireless LANs · X, y, and possibly z axis · Battery-life (if required) (standard test methods) · Resolution (standard test methods) · Range (standard test methods) · Safety (intrinsic) · Security (authentication, non-repudiation, encryption, authorization) · No additional wireless infrastructures to manage · Refresh rate · Tag density · Data standards for common interface between components and host systems output data stream From: Minutes NCITS T20 RTLS 21 August 2001 Bolded/Underlined Items May Overlap with P1451.5

  10. MITs AutoID Program Provides World-wide Unique ID Functionality in the Form of an Electronic Product Code (ePC). • Use the ePC (electronic version of the UPC; having 64 or 96-bits) for the TBC, TBIM and transducer UUID's [additional TEDS, compact TEDS and metaTEDS could still be stored on the devices if desired]. • An NCAP F-block would send the ePC to the object name server (ONS -- analogous to DNS) which returns a URL for detailed information on the device. • TEDS and additional information could be available at the referenced URL all described using PML which uses the same format and structure as the eXtensible Markup Language (XML). • Software (The SAVANT by MIT) will be available later this year to implement ePC/ONS/PML transactions.

  11. 1451.5 Wireless Work Leverages Other 1451 Projects • Smart Transducer Object Model from 1451.1 • Basic TEDS Concept from 1451.2 • Synch and XML TEDS from P1451.3 • Compact TEDS and Transducer Interface from P1451.4

  12. The Architecture Needs to Accommodate Various Types of Nodes Courtesy of Axonn L.L.C.

  13. P1451.5 SG Is Considering SeveralTypes of System Nodes • Transducer Nodes • Bidirectional (Synchronous) • Transmit-Only (Asynchronous) • Mobility Capable • Network Nodes • Bidirectional • Receive-Only • Mobility-Capable • Repeater Node • Compute Node • Display Node

  14. Path Ahead for Future Growth A Well-Planned Architecture for 1451.5 Enables the Quick Incorporation of... • Emerging Wireless Technologies • Data Security (as described in IEEE 1363) • Mobile Ad-Hoc Networking • Other Useful Features

  15. Conclusion A New Wireless Transducer Interface, IEEE P1451.5, is currently being studied that will ideally ... • Efficiently Leverage Sensor Networking Capabilities From the Other IEEE 1451 Projects • Include Multiple Robust MAC/PHY Combinations • Use the IEEE 802 Family-of-Standards Approach as a Model • Have a Layered Architecture • Enabling Rapid Ramp-Up Utilizing Existing Products • Enabling Flexible Future Growth

More Related