1 / 18

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Tutorial on Body Ar

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Tutorial on Body Area Networks ] Date Submitted: [ July 18, 2006 ] Source: [ Stefan Drude ] Company [ Philips ] Address [ High Tech Campus 60, 5656 AG Eindhoven, The Netherlands] ]

omer
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Tutorial on Body Ar

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. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Tutorial on Body Area Networks] Date Submitted: [July 18, 2006] Source: [Stefan Drude] Company [Philips] Address [High Tech Campus 60, 5656 AG Eindhoven, The Netherlands]] Voice:[+31 40 27-23431], FAX: [+31 40 27-22764], E-Mail:[stefan.drude@philips.com] Re: [Tutorial] Abstract: [The contribution reflects the information presented at the tutorial on body area networks presented at the San Diego meeting on July 18, 2006.] Purpose: [To provide information on body area network use cases, typical requirements, and to start the process on possibly starting a study group in 802.15 on this topic.] 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. Stefan Drude, Philips

  2. Overview • Body Area Networks – S. Drude • Quick summary use cases, requirements • Channel Models and Health Aspects of PAN and BAN – A. J Johansson • Magnet and Magnet Beyond • Channel modelling • Medical implant communications • Health aspects of PAN/BAN implants Stefan Drude, Philips

  3. Body Area Network • Broad range of possible devices • Broad range of media types • Connect everything you carryon you and with you • Offer “Connected User” experience • Matches low power environment • Challenge – scalability data rate, power Stefan Drude, Philips

  4. Body Area Networks –Target PositionAverage power consumption, sustained data rate Body Area Network 1 Gbit/s Wireless USB 100 Mbit/s IEEE 802.11 a/b/g 10 Mbit/s Bluetooth 1 Mbit/s 100 kbit/s ZigBee 10 kbit/s 1 kbit/s 100 mW 200 mW 500 mW 1000 mW 2 mW 5 mW 10 mW 20 mW 50 mW Stefan Drude, Philips

  5. Body Area Networks • Usage Scenarios • Body senor network • Fitness monitoring • Wearable audio • Mobile device centric • Video stream • Remote control &I/O devices Stefan Drude, Philips

  6. Body Sensor Network • Medical application • Vital patient data • Wireless sensors • Link with bedside monitor • Count on 10 – 20 sensors • Five similar networks in range • Minimum setup interaction • Potentially wide application • Total traffic / patient < 10 kbps Stefan Drude, Philips

  7. Fitness Monitoring • Central device is MP3 player • Wireless headset included • Expand functionality • Speed, distance • Heart rate, respiration monitor • Temperature sensor • Pacing information • Location information • Wristwatch display unit • Etc. • Total system load < 500 kbps • Synchronization may go faster Stefan Drude, Philips

  8. Wearable Audio • Central device is headset • Stereo audio, microphone • Connected devices • Cellular phone • MP3 player, PDA • CD audio player • AP at home • Handsfree car • Remote control • Others • Requires priority mechanism • Network load < 500 kbps Stefan Drude, Philips

  9. Mobile Device Centric • Mobile terminal is central point • Covers broad set of data • Sensors – vital, other • Headset • Peripheral devices • Handsfree / car • Provide gateway to outside • Offload sensor data, other • Requires priority mechanism • Network load < 500 kbps Stefan Drude, Philips

  10. Remote Control & I/O Devices • Remote control device • Increase consumer convenience • Makes headset control practical • Stand-alone vs shared function • Combine with wristwatch display ? • Printers • Identification, storage • Wireless pen • Complement BAN functionality Stefan Drude, Philips

  11. Technical Requirements • There is no specific standard for BANs • Current standards come close for specific use cases, not broad enough • Issues: power consumption, discovery, QoS • Support for very low power devices, sensors • Target less than 10% power consumption for communications compared to total device • Have single standard with broad range of supported data rate - scalability Stefan Drude, Philips

  12. BAN Requirements - Draft • Distance 2 m std, 5 m special • Piconet density 2 - 4 nets / m2 • Devices per network max. 100 • Net network throughput 100 Mbit/s max. • Power consumption ~ 1mW / Mbps (@ 1 m distance) • Startup time < 100 us, or < 10% of TX slot • Latency (end to end) 10 ms • Network setup time < 1 sec (after initial setup, per device) Stefan Drude, Philips

  13. BAN Requirements - Draft • Implementation module cost • Should be comparable to Bluetooth module • Effective sleep mode(s) • Concept for effective, remote wake-up • Operates in global, license-exempt band Stefan Drude, Philips

  14. BAN Requirements - Draft • Privacy, security • Peer to peer communication, point to multi-point • Omni-directional antennas: small, flexible • Future proof [for 5 years?] • Upgradeable, scaleable, backwards compatibility • Support for several power management / consumption schemes [classes] Stefan Drude, Philips

  15. BAN Requirements - Draft • Quality of service, guaranteed bandwidth • Specific definitions, depends on application • Graceful degradation of services • Depends on application, not always desireable • Concurrent availability of asynchronous and isochronous channels • Low duty cycle and high duty cycle modes • Very low duty cycle applications (sensors) Stefan Drude, Philips

  16. Interest Group on BAN in 802.15Conclusions on low data rate applications • Operates on, inside, or in the vicinity of the body • Limited range (< .01 – 2 meters) • The channel model will include human body effects. (absorption, health effects) • Extremely low consumption power (.1 to 1 mW) for each device • Capable of energy scavenging / battery-less operation • Support scalable Data Rate: 0.01 – 1,000 kbps (optional 10 Mbps) Stefan Drude, Philips

  17. Interest Group on BAN in 802.15 (2)Conclusions on low data rate applications • Support different classes of QoS for high reliability, asymmetric traffic, power constrained • Needs optimized, low complexity MAC and Networking layer • High number of simultaneously operating piconets required • Application specific, security/privacy required • Small form factor for the whole radio, antenna, power supply system • Locating radios (” find me”) mode Stefan Drude, Philips

  18. Overview • Body Area Networks – S. Drude • Quick summary use cases, requirements • Channel Models and Health Aspects of PAN and BAN – A. J Johansson • Magnet and Magnet Beyond • Channel modelling • Medical implant communications • Health aspects of PAN/BAN implants Stefan Drude, Philips

More Related