1 / 15

MobiHealth Communication Infrastructure

MobiHealth Communication Infrastructure. MobiHealth WP3 meeting September 20 , 2002 MobiHealth Team, University of Twente Email: mhealth@mobihealth.org Internet: www.mobihealth.org. Presentation Layout. MobiHealth Communication Infrastructure Communication Requirements How to proceed?

shoose
Download Presentation

MobiHealth Communication Infrastructure

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. MobiHealthCommunication Infrastructure MobiHealth WP3 meeting September 20, 2002 MobiHealth Team, University of Twente Email: mhealth@mobihealth.org Internet: www.mobihealth.org MobiHealth IST-2001-36006

  2. Presentation Layout • MobiHealth Communication Infrastructure • Communication Requirements • How to proceed? • Info: MobiHealth testbed Netherlands MobiHealth IST-2001-36006

  3. “Communication infrastructure for bi-directional multimedia data communication between a MobiHealth BAN and arbitrary host on the Internet.” Communication infrastructure issues: MobiHealthCommunication Infrastructure • Speed • Coverage • Availability • Scalability • Mobility • Security • … MobiHealth IST-2001-36006

  4. MobiHealth ExternalCommunication Environment IEEE 802.3/11/15 IEEE 802.11/15 2.5G, 3G IP ► Focus 2.5G, 3G MobiHealth IST-2001-36006

  5. Communication Requirements • GPRS or UMTS as ‘bearer service’ (mandatory) • IP = network protocol (Internet standard) • Performance (e.g. ‘goodput’ = speed, delaymax) • Coverage (GPRS and/or UMTS) • Reliability (e.g. packet loss, availability) • Traffic management (e.g. prioritization of data) • Mobility of a BAN (network node) • Security (e.g. authentication, authorization, encryption) • … “Communication requirements are derived from the MobiHealth system requirements.” MobiHealth system - application, BANOS, BAN MobiHealth IST-2001-36006

  6. Communication Requirements (cont.) • Performance • Depends on BAN application = MobiHealth trials example: MST trauma team • Bandwidthu: peak(ti=30) 236 kbps, sustained 20-100 kbps • Bandwidthd: 64-256 kbps • Max speed E2E connection = speed slowest segment • GPRS ~ 14-112 kbps (CS2 coding) • UMTS ~ 64-144 kbps • High delay between transmission and receipt of a packet • GPRS ~ 1500ms avg. (ICMP) roundtrip delay • UMTS ~ ??? MobiHealth IST-2001-36006

  7. Communication Requirements (cont.) • Coverage (GPRS and/or UMTS) • Depends on BAN application = MobiHealth trials example: City of Barcelona (ES), Lulea (S) region, Enschede (NL) city centre, Duisburg (D) region MobiHealth IST-2001-36006

  8. Communication Requirements (cont.) • Reliability Transport of patient vital sign data, remote control of BANs. What to aim for? 99.999% uptime? 100% error free communication? Where to implement? • Application Layer • protocols: http, … • Transport Layer • CO service (TCP): E2E reliable delivery, flow control • CL service (UDP): unreliable delivery, no flow control • Lower Layers (Network, Link, Physical)? How to evaluate reliability of MobiHealth infrastructure? MobiHealth IST-2001-36006

  9. Communication Requirements (cont.) • Traffic management Transport of patient vital sign data, remote control of BANs. • Guaranteed bidirectional communication in congested networks • MNO, Internet, Enterprise network, … • Mobile Network Operators: No voice over data priority scheme! How to deal with traffic management in the MobiHealth infrastructure? MobiHealth IST-2001-36006

  10. Communication Requirements (cont.) • Security Transport of personal (medical) data, remote control of a BAN, … Is end-to-end (BAN-to-Internet host) security needed? What level? Depends on user requirements (WP1)! Security can be added to most communication layers! Different security features depending on layer: • Link layer: Bluetooth, GPRS/UMTS, ... • Network layer: IPsec, ... • Transport layer: SSL/TLS, HTTPS, ... • Application layer: Data encryption (OpenSSL Libraries, MIME) MobiHealth IST-2001-36006

  11. Communication Requirements (cont.) • Mobility of a BAN • Cross border connectivity? • Speed limitation? (e.g. MST trauma trial 80-100 km/hr) • Application disruption? • How to handle “handovers”? • … MobiHealth IST-2001-36006

  12. MNO Internet BAN Intranet Communication Requirements (cont.) • Mobility of a BAN Horizontal Handover MobiHealth IST-2001-36006

  13. MNO MNO Internet BAN Intranet Communication Requirements (cont.) • Mobility of a BAN Vertical Handover MobiHealth IST-2001-36006

  14. How to proceed? • WP1 user requirements needed: • Performance, coverage, reliability, security • WP2 system requirements needed • Derived from WP1 • WP3 communication infrastructure requirements • Derived from WP1 and WP2 • WP3 preliminary testing • ‘testdrive’ with plain IP E2E communication • develop measurement strategy: • performance, reliability (incl. mobility), coverage, security MobiHealth IST-2001-36006

  15. MobiHealth testbed Netherlands MobiHealth IST-2001-36006

More Related