Presentation is loading. Please wait.

Presentation is loading. Please wait.

MobiHealth Communication Infrastructure

Published byErika Mona Tiedeman Modified over 6 years ago

Similar presentations

Presentation on theme: "MobiHealth Communication Infrastructure"— Presentation transcript:

1 MobiHealth Communication Infrastructure
MobiHealth WP3 meeting September 20, 2002 MobiHealth Team, University of Twente Internet: 11/23/2018 MobiHealth IST

2 Presentation Layout MobiHealth Communication Infrastructure
Communication Requirements How to proceed? Info: MobiHealth testbed Netherlands 11/23/2018 MobiHealth IST

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

4 MobiHealth External Communication Environment
IEEE 802.3/11/15 IEEE 802.11/15 2.5G, 3G Three communication domains: Healthcare (e.g. Hospital) Public access (mobile operator network) Home (premises, in-house + garden) IEEE – Ethernet (wired) IEEE – WLAN: FHSS, DSSS (x.a,x.b) IEEE – WPAN: Bluetooth (x.1) IP ► Focus 2.5G, 3G 11/23/2018 MobiHealth IST

5 Communication Requirements
“Communication requirements are derived from the MobiHealth system requirements.” MobiHealth system - application, BANOS, BAN 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) … 11/23/2018 MobiHealth IST

6 Communication Requirements (cont.)
Performance Depends on BAN application = MobiHealth trials example: MST trauma team Bandwidthu: peak(ti=30) 236 kbps, sustained kbps Bandwidthd: kbps Max speed E2E connection = speed slowest segment GPRS ~ kbps (CS2 coding) UMTS ~ kbps High delay between transmission and receipt of a packet GPRS ~ 1500ms avg. (ICMP) roundtrip delay UMTS ~ ??? 11/23/2018 MobiHealth IST

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 11/23/2018 MobiHealth IST

8 Communication Requirements (cont.)
Reliability Transport of patient vital sign data, remote control of BANs. What to aim for? % 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? 11/23/2018 MobiHealth IST

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? 11/23/2018 MobiHealth IST

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) 11/23/2018 MobiHealth IST

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

12 Communication Requirements (cont.)
Mobility of a BAN Internet MNO Horizontal Handover BAN Intranet 11/23/2018 MobiHealth IST

13 Communication Requirements (cont.)
Mobility of a BAN BAN Internet MNO Vertical Handover Intranet MNO 11/23/2018 MobiHealth IST

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 11/23/2018 MobiHealth IST

15 MobiHealth testbed Netherlands
11/23/2018 MobiHealth IST

Download ppt "MobiHealth Communication Infrastructure"

Similar presentations

Ch. 2 Protocol Architecture. 2.1 The Need for a Protocol Architecture Same set of layered functions need to exist in the two communicating systems. Key.

Ch. 2 Protocol Architecture. 2.1 The Need for a Protocol Architecture Same set of layered functions need to exist in the two communicating systems. Key.
© 2007 Cisco Systems, Inc. All rights reserved.ICND1 v1.0—1-1 Building a Simple Network Understanding the TCP/IP Transport Layer.

© 2007 Cisco Systems, Inc. All rights reserved.ICND1 v1.0—1-1 Building a Simple Network Understanding the TCP/IP Transport Layer.
The OSI Model. 001 011 0 1 1 0 FTP API 7. Application 6. Presentation 5. Session 4. Transport 3. Network 2. Data Link 1. Physical HTTP Software.

The OSI Model FTP API 7. Application 6. Presentation 5. Session 4. Transport 3. Network 2. Data Link 1. Physical HTTP Software.
1 Review of Important Networking Concepts Introductory material. This slide uses the example from the previous module to review important networking concepts:

1 Review of Important Networking Concepts Introductory material. This slide uses the example from the previous module to review important networking concepts:
Lecture slides prepared for “Business Data Communications”, 7/e, by William Stallings and Tom Case, Chapter 8 “TCP/IP”.

Lecture slides prepared for “Business Data Communications”, 7/e, by William Stallings and Tom Case, Chapter 8 “TCP/IP”.
Presentation Title Subtitle Author Copyright © 2002 OPNET Technologies, Inc. TM Introduction to IP and Routing.

Presentation Title Subtitle Author Copyright © 2002 OPNET Technologies, Inc. TM Introduction to IP and Routing.
Telefónica Móviles España WP3 meeting 2.5 - 3G Communication Infrastructure Madrid, November 12 & 13, 2002.

Telefónica Móviles España WP3 meeting G Communication Infrastructure Madrid, November 12 & 13, 2002.
Vertical Handover Nawshad Rehan Rasha 1014052020.

Vertical Handover Nawshad Rehan Rasha
Telefónica Móviles España Status of trial-ready GPRS and UMTS networks in the trial countries.

Telefónica Móviles España Status of trial-ready GPRS and UMTS networks in the trial countries.
SEED Infotech Pvt. Ltd. 1 Networking in Java. SEED Infotech Pvt. Ltd. 2 Objectives of This Session Describe issues related to any type of network using.

SEED Infotech Pvt. Ltd. 1 Networking in Java. SEED Infotech Pvt. Ltd. 2 Objectives of This Session Describe issues related to any type of network using.
I-D: draft-rahman-mipshop-mih-transport-01.txt Transport of Media Independent Handover Messages Over IP 67 th IETF Annual Meeting MIPSHOP Working Group.

I-D: draft-rahman-mipshop-mih-transport-01.txt Transport of Media Independent Handover Messages Over IP 67 th IETF Annual Meeting MIPSHOP Working Group.
TCP/IP and the Internet ARPANET (1969) –R&D network funded by DARPA. –Packet Switching Survive nuclear war. –Experimental to operational (1975). –Not suitable.

TCP/IP and the Internet ARPANET (1969) –R&D network funded by DARPA. –Packet Switching Survive nuclear war. –Experimental to operational (1975). –Not suitable.
CS 3214 Computer Systems Godmar Back Lecture 23. Announcements Project 5 due Dec 8 Exercise 10 handed out Exercise 11 coming before Thanksgiving CS 3214.

CS 3214 Computer Systems Godmar Back Lecture 23. Announcements Project 5 due Dec 8 Exercise 10 handed out Exercise 11 coming before Thanksgiving CS 3214.
Module 4: Designing Routing and Switching Requirements.

Module 4: Designing Routing and Switching Requirements.
Component 9 – Networking and Health Information Exchange Unit 1-1 ISO Open Systems Interconnection (OSI) This material was developed by Duke University,

Component 9 – Networking and Health Information Exchange Unit 1-1 ISO Open Systems Interconnection (OSI) This material was developed by Duke University,
© Ramon Martí, DMAG, Universitat Pompeu Fabra 1 WP2 UPF Contribution to MobiHealth Security in the MobiHealth BAN Enschede 2002/09/18-20.

© Ramon Martí, DMAG, Universitat Pompeu Fabra 1 WP2 UPF Contribution to MobiHealth Security in the MobiHealth BAN Enschede 2002/09/18-20.
Transport Layer OSI Model. The transport layer is responsible for the segmentation and the delivery of a message from one process to another.

Transport Layer OSI Model. The transport layer is responsible for the segmentation and the delivery of a message from one process to another.
The Transport Layer application transport network data link physical application transport network data link physical application transport network data.

The Transport Layer application transport network data link physical application transport network data link physical application transport network data.
1 End-user Protocols, Services and QoS. 2 Layering: logical communication application transport network link physical application transport network link.

1 End-user Protocols, Services and QoS. 2 Layering: logical communication application transport network link physical application transport network link.
MobiHealth Communication Infrastructure Measurement strategy of E2E communication link MobiHealth WP3 meeting November 13, 2002 MobiHealth Team, University.

MobiHealth Communication Infrastructure Measurement strategy of E2E communication link MobiHealth WP3 meeting November 13, 2002 MobiHealth Team, University.

Similar presentations

Ads by Google