Advanced

An On-Demand WebRTC and IoT Device Tunneling Service for Hospitals

Sandholm, Thomas; Magnusson, Boris LU and Johnsson, Björn A LU (2014) FiCloud 2014 In [Host publication title missing] p.53-60
Abstract
In this paper we present the implementation of a WebRTC gateway service that can forward ad-hoc RTP data plane traffic from a browser inside a local hospital network to a browser on a local home network. The gateway leverages the same infrastructure used by the hospital to tunnel sensor and control data for medical devices in home-care deployments. In our use case, doctors at hospitals can only access port 80 through the hospital firewall on external machines, and they need to communicate with patients who are typically behind a NAT in a local WiFi network. VPN solutions only work for staff but not between patients and staff. Our solution solves this problem by redirecting all WebRTC traffic through a gateway service on the local network... (More)
In this paper we present the implementation of a WebRTC gateway service that can forward ad-hoc RTP data plane traffic from a browser inside a local hospital network to a browser on a local home network. The gateway leverages the same infrastructure used by the hospital to tunnel sensor and control data for medical devices in home-care deployments. In our use case, doctors at hospitals can only access port 80 through the hospital firewall on external machines, and they need to communicate with patients who are typically behind a NAT in a local WiFi network. VPN solutions only work for staff but not between patients and staff. Our solution solves this problem by redirecting all WebRTC traffic through a gateway service on the local network that has a secure tunnel established with a public gateway. The public gateway redirects traffic from multiple concurrent streams securely between local gateway services that connect to it. The local gateways also communicate with browsers on their local network to mimic a direct browser-to-browser connection without having to change the browser runtime. We have demonstrated that this technique works well within the hospital network and arbitrary patient networks, without the need for any individual host configuration. In our evaluation we show that the latency overhead is 18-20 ms for each concurrent stream added to the same gateway service, which is not discernible with a naked eye until you have more than 10 concurrent streams. (Less)
Please use this url to cite or link to this publication:
author
organization
publishing date
type
Chapter in Book/Report/Conference proceeding
publication status
published
subject
in
[Host publication title missing]
pages
53 - 60
conference name
FiCloud 2014
external identifiers
  • Scopus:84922541278
ISBN
978-1-4799-4357-9
DOI
10.1109/FiCloud.2014.19
project
PalCom
language
English
LU publication?
yes
id
596910b6-1f9b-4a93-a023-ff88d52d8108 (old id 7854869)
date added to LUP
2015-09-04 13:16:06
date last changed
2017-02-19 04:35:42
@inproceedings{596910b6-1f9b-4a93-a023-ff88d52d8108,
  abstract     = {In this paper we present the implementation of a WebRTC gateway service that can forward ad-hoc RTP data plane traffic from a browser inside a local hospital network to a browser on a local home network. The gateway leverages the same infrastructure used by the hospital to tunnel sensor and control data for medical devices in home-care deployments. In our use case, doctors at hospitals can only access port 80 through the hospital firewall on external machines, and they need to communicate with patients who are typically behind a NAT in a local WiFi network. VPN solutions only work for staff but not between patients and staff. Our solution solves this problem by redirecting all WebRTC traffic through a gateway service on the local network that has a secure tunnel established with a public gateway. The public gateway redirects traffic from multiple concurrent streams securely between local gateway services that connect to it. The local gateways also communicate with browsers on their local network to mimic a direct browser-to-browser connection without having to change the browser runtime. We have demonstrated that this technique works well within the hospital network and arbitrary patient networks, without the need for any individual host configuration. In our evaluation we show that the latency overhead is 18-20 ms for each concurrent stream added to the same gateway service, which is not discernible with a naked eye until you have more than 10 concurrent streams.},
  author       = {Sandholm, Thomas and Magnusson, Boris and Johnsson, Björn A},
  booktitle    = {[Host publication title missing]},
  isbn         = {978-1-4799-4357-9},
  language     = {eng},
  pages        = {53--60},
  title        = {An On-Demand WebRTC and IoT Device Tunneling Service for Hospitals},
  url          = {http://dx.doi.org/10.1109/FiCloud.2014.19},
  year         = {2014},
}