body area-networks
DESCRIPTION
TRANSCRIPT
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 1
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 2
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 3
Body Area Networks –Target PositionAverage power consumption, sustained data rate
1000 mW500 mW100 mW 50 mW 10 mW
1 Gbit/s
100 kbit/s
1 Mbit/s
10 Mbit/s
100 Mbit/s
1 kbit/s
10 kbit/s
Wireless USB
IEEE 802.11 a/b/g
Bluetooth
ZigBee
200 mW 20 mW
Body Are
a Netw
ork
5 mW 2 mW
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 4
Body Area Networks
• Usage Scenarios– Body senor network– Fitness monitoring– Wearable audio– Mobile device centric– Video stream
– Remote control &I/O devices
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 5
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 6
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 7
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 8
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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 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
doc.: IEEE 802.15-06-0331
Submission
July 2006
Stefan Drude, PhilipsSlide 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)