CONFERENCE INFORMATION
PAPERS BY SESSION
PAPERS BY AUTHOR
SEARCH
GETTING STARTED
TRADEMARKS
2016 International Conference on
Networking and Network Applications
23-25 July 2016
Hakodate City, Hokkaido, Japan
NaNA 2016
Papers by Session
Session C1
q
Analysis of an SEIVR Epidemic Model with Partial Immunization
and Nonlinear Infection Rate
Fangwei Wang, Changguang Wang, Dongmei Zhao, and Yunkai Zhang
q
ISO/IEEE 11073-Based Healthcare Services over IoT Platform Using
6LoWPAN and BLE: Architecture and Experimentation
Hyung-Woo Kang, Cheol-Min Kim, and Seok-Joo Koh
q
A Pixel Value Ordering Predictor for High-Capacity Reversible Data
Hiding
Chin-Feng Lee and Yu-Ju Tseng
q
Cumulative Space Time Coding-Based Visible Light Cell Identification
for Large-Scale Indoor Environment
Runmei Zhao, Zhitong Huang, Wei Li, and Yuefeng Ji
q
Load Prediction-Based Automatic Scaling Cloud Computing
Tao Li, Jingyu Wang, Wei Li, Tong Xu, and Qi Qi
q
Dynamic Load-Balancing Mechanism for Software-Defined Networking
ISO/IEEE 11073-based Healthcare Services over IoT Platform
using 6LoWPAN and BLE: Architecture and Experimentation
Hyung-Woo Kang
School of Computer Science and Engineering,
Kyungpook National University, Daegu, Korea
hwkang0621@gmail.com
Cheol-Min Kim
School of Computer Science and Engineering,
Kyungpook National University Daegu, Korea
cheolminkim@vanilet.pe.kr
Seok-Joo Koh
School of Computer Science and Engineering,
Kyungpook National University, Daegu, Korea
sjkoh@knu.ac.kr
Abstract—The Internet-of-Things (IoT) is a paradigm that
connects devices and objects through the network to share information. Recently, the IoT-based healthcare services are considered as one of the crucial services. However, the existing IoT technology, such as Bluetooth and ISO/IEEE 11073 standard, is not suitable for providing IoT-based healthcare services because it does not support the Internet Protocol (IP). Moreover, the oneM2M standard does not support the IoT-based healthcare services. In this paper, we propose a new architecture of ISO/IEEE 11073-based IoT healthcare services. The proposed architecture can support IP communication using IPv6 over Low power Wireless Personal Area Networks (6LoWPAN) technology in the Bluetooth Low Energy (BLE) network. We also use the Constrained Application Protocol (CoAP) to provide more efficient communication for constrained devices. For validation of the proposed architecture, we implemented the ISO/IEEE 11073-based healthcare services using 6LoWPAN and BLE. We also performed testbed experimentation. In addition, for evaluation of the associated protocols, we compare the transmission delay between CoAP and HTTP. From the results, we see that CoAP is more efficient than HTTP for the IoT healthcare services.
Keywords: IoT, ISO/IEEE 11073, 6LoWPAN, BLE, CoAP
I. INTRODUCTION
With the popularity of wearable devices such as Google’s google glass, Nike’s fuel band and Apple’s iWatch, the Internet-of-Things (IoT) technology and services have been focused. In particular, the IoT-based healthcare services are regarded as one of the crucial services [1-3]. However, the current version of ISO/IEEE 11073 Personal Healthcare Device (PHD) standard does not support the IoT or Internet Protocol (IP). Moreover, the oneM2M standard for IoT platform does not support the IP-based healthcare services which will be provided with the wearable devices using Zigbee and Bluetooth [4-6].
In this paper, we discuss how to provide the ISO/IEEE 11073-based healthcare services and communications over the oneM2M-based IoT platform using the 6LoWPAN and the BLE. We propose the protocol architecture for healthcare services over IoT platform with CoAP, 6LoWPAN and BLE
technology. We propose the protocol architecture to provide healthcare services over IoT platform with the 6LoWPAN and BLE technology. We also describe the implementation of ISO/IEEE 11073 Domain Information Model (DIM) to support the healthcare services. With this implementation, testbed experimentations will be performed with IoT platform and healthcare devices. By experimentation, we analyze the performance of the proposed protocol architecture using the 6LoWPAN over BLE technology.
This paper is organized as follows. In Section II, we describe the related works such as BLE, 6LoWPAN, CoAP and ISO/IEEE 11073 DIM. Section III describes the proposed protocol architecture for healthcare services. In Section IV, we discuss a testbed implementation over oneM2M-based IoT platform and healthcare devices together with experimental analysis. Finally, Section V concludes this paper.
II. RELATED WORKS
Bluetooth is a Wireless Personal Area Network (WPAN) technology that connects among mobile smart phones, laptops, earphones or headphones each other. Bluetooth can be used for novel applications in the healthcare, fitness, beacons, security, and home entertainment industries. BLE can reduce power consumption, compared to the previous version of Bluetooth. The work in [7], describes IPv6 communication over the BLE network using 6LoWPAN.
6LoWPAN defines the utilization of IP for small devices that have low battery and limited processing capacity. The 6LoWPAN allows IPv6 packets to be sent and received over IEEE 802.15.4 based networks. In [8], the authors argue that 6LoWPAN is light-weight and it takes a little bit smaller time to send and receive packets, compared to the raw IEEE 802.15.4 network. In addition, 6LoWPAN is quite scalable enough to expand its network size to 264. It also reduces the power consumption and enables the connection with legacy IP networks. Therefore, 6LoWPAN is very suitable for IoT environment.
CoAP is the web transfer protocol that is intended to use in the constrained nodes and networks. The Constrained RESTful Environments (CoRE) working group of IETF has progressed standardization of CoAP. The CoAP is similar to
2016 International Conference on Networking and Network Applications
978-1-4673-9803-9/15 $31.00 © 2015 IEEE DOI 10.1109/NaNA.2016.26
HTTP, which is a client/server model. Like HTTP, the CoAP manages the resources using the same method such as GET, PUT, POST and DELETE. On the other hand, CoAP is lightweight and consumes less electric power than HTTP.
CoAP consists of two sub-layers: the messaging layer and the request/response layer. The CoAP defines the four types of messages: Confirmable (CON), Non-confirmable (NON), Acknowledgement (ACK) and Reset. CON and ACK messages are used to provide reliable message exchange. On the contrary, NON message provides the best-effort message exchange. Request/response layer gives the piggy-backed response, separate response and non-confirmable response. The works in [9] gives a surveys on technologies and techniques for using CoAP-based Wireless Sensor Networks (WSN) for connecting and monitoring the medical sensors.
ISO/IEEE 11073 defines the communication standards for exchanging the healthcare information in medical, healthcare and wellness devices. The ISO/IEEE 11073 system model are classified into Domain Information Model (DIM), service model and communication model. Each models defines the presentation, access and transmission of healthcare data. ISO/IEEE 11073-20601 also defines agent and manager. The agent is a node that transmits the health data, and the manager is a node that receives the health data from the agent such as smart phone, health care devices and computer systems. Especially, ISO/IEEE 11073 DIM is an object-oriented model containing vital-sign data in the domain of medical devices. However, it is difficult to provide healthcare services in the IoT environments. This is because ISO/IEEE 11073 does not support the IP protocol. In [10], the authors describes the process to develop a new standard for Personal Health Data (PHD) based on the existing ISO/IEEE 11073 for small medical devices. They also describe how the existing components can be used to create the new standard.
III. PROTOCOL ARCHITECTURE FOR IOT-BASED
HEALTHCARE SERVICES
In order to support the communication for healthcare services based on IoT, we design a protocol stack using the oneM2M and ISO/IEEE 11073 PHD standards.
Fig. 1 Protocol stack for IoT-based healthcare services
Fig. 1 shows the communication protocol stack for IoT-based healthcare services. Since our services should be interoperable with the existing BLE-based healthcare devices, the BLE technology is used for layer 2 communication. To provide IoT-based healthcare services, the proposed protocol stack uses IP communication by utilizing 6LoWPAN, HTTP, and CoAP. For exchange of health data between the server and devices, we use the ISO/IEEE 11073 DIM messages through CoAP.
As shown in Fig. 2, the components of the architecture consist of healthcare devices, oneM2M-based server platform and web client or application. The healthcare device is connected to an oneM2M-based healthcare server via 6LoWPAN gateway. When the 6LoWPAN gateway (GW) has received healthcare data, the gateway performs the packet conversion between Bluetooth interface and Ethernet interface to communicate with Internet. The server provides the functions such as device management, device control and healthcare data storage. The data communication between device and server uses the ISO/IEEE 11073 DIM-based healthcare data.
Fig. 2 Proposed protocol layer and overall architecture
Fig. 3 shows the overall signaling flows for IoT-based healthcare services. For IP communication and ISO/IEEE 11073-based healthcare data transmissions, we use ‘&Cube’ platform as the IoT-based device. &Cube is an oneM2M-based device platform, and we will discuss more in detail in Section IV. In this figure, healthcare device sends the simple numerical information about healthcare data over BLE network. &Cube in the healthcare device builds the ISO/IEEE 11073-baed healthcare data and activates 6LoWPAN for IP communication. In order to communicate between the Bluetooth-based device and the healthcare server, the healthcare data must pass the gateway for protocol conversion. By protocol conversion, 6LoWPAN gateway forwards healthcare data to healthcare server using CoAP. The healthcare server stores the ISO/IEEE 11073 DIM-based healthcare data. When a user requests the IoT-based healthcare service, the healthcare server will provide the services based on the stored data.
Healthcare Device &Cube 6LoWPAN GW Healthcare Server Healthcare Device Domain
(BLE network) Application Sending healthcare data (HR) over BLE network Activate 6LoWPAN on device and build
11073 DIM Sending ISO/IEEE 11073 DIM-based
healthcare data Protocol conversion (BLE Æ Ethernet)
Forwarding healthcare data
(using CoAP) Store received data Request healthcare data (using HTTP) Response (using
HTTP)
Fig. 3 Overall signaling flow diagram
IV. IMPLEMENTATION AND PERFORMANCE ANALYSIS
The Bluetooth Special Interest Group (SIG) provides the IP Support Profile (IPSP) for IP communication. This profile requires higher version of Bluetooth 4.1. 6LoWPAN is supported in the Linux kernel version 3.18 or later. Fig. 4 shows the command so as to activate 6LoWPAN on Linux.
Fig. 4 Command to activate 6LoWPAN on Linux
We use the Raspberry Pi to implement 6LoWPAN in the constrained node. Fig. 5 shows that activated 6LoWPAN on Raspberry Pi platform.
Fig. 5 Activated 6LoWPAN on Raspberry Pi In Fig. 6, we can see that the 6LoWPAN address is assigned to the Bluetooth interface. By executing the command, the Bluetooth_6lowpan can be enabled in the Linux kernel, and the ready operation for 6LoWPAN communication is now completed.
Fig. 6 6LoWPAN address assigned to Bluetooth interface
IP communication over BLE network should be provided in the IPSP profile. Thus, we must set the Protocol Service Multiplexer (PSM) number to identify the profile in Linux. Fig. 7 shows the command for setting the PSM number in Linux. The PSM number used in IPSP is 35.
Fig. 7 Command for setting the PSM number in Linux
Fig. 8 shows the command to create the 6LoWPAN communication link. By executing the command in Figure, we can create the 6LoWPAN link between Bluetooth device and 6LoWPAN gateway.
Fig. 8 Command for creating 6LoWPAN link
In order to communicate between the healthcare device and the healthcare server through Internet, the 6LoWPAN gateway should configure the packet forwarding function. Fig. 9 shows the command to enable the packet forwarding at 6LoWPAN gateway.
Fig. 9 Command for packet forwarding at gateway
By executing the command, as shown in Fig. 10, we can transmit the incoming packet from the Bluetooth interface to the healthcare server through Internet. Fig. 10 shows the command to modify the routing table.
Fig. 10 Command to modify the routing table
For validation of the proposed protocol architecture, we build a testbed. Fig. 11 shows the testbed configuration, in which the healthcare device, healthcare server and gateway are used. The device and the server were configured by using the oneM2M-based open platform made by the OCEAN project in Korea [11]. The OCEAN project provides the Mobius and &Cube platforms. The Mobius platform is a server side platform that connects to device and application.
It supports the HTTP, CoAP and MQTT protocols for data communication with IoT devices. &Cube is a device platform for IoT devices, which is designed for interworking with the IoT server platform. Sensors or small devices transmits the measured data to &Cube using the Things Adaptation S/W (TAS). The TAS software is responsible for creating the connection path between real object and &Cube. The API for the device that we use is determined by the TAS. &Cube sends the data collected from the sensors or small devices to the Mobius server. Then, &Cube receives the control commands from the Mobius.
Fig. 11 Testbed Configuration
A commercial healthcare product ‘RE:FIT’ was used as healthcare device that supports the Bluetooth communication. The healthcare device can measure the Heart Rate (HR), ECG and stress level. We used the HR values to generate data which follows the ISO/IEEE 11073 DIM format. The ISO/IEEE 11073 DIM was implemented by using XML.
Fig. 12 shows the implementation of ISO/IEEE 11073 DIM using XML. We implemented ISO/IEE 11073 DIM by referring to the open-source Antidote of Signove [12].
Fig. 12 Implemented ISO/IEEE 11073 DIM using XML
For IP communication using 6LoWPAN, we used the Raspberry Pi (&Cube) and Bluetooth dongle and implemented the 6LoWPAN stack. That is, the healthcare device transmits the healthcare data to &Cube, and &Cube acts as a device.
The 6LoWPAN gateway is responsible for protocol conversion between BLE network and Ethernet network.
6LoWPAN gateway was also implemented in Raspberry Pi. The Mobius-based Healthcare server manages the health data of various healthcare devices. To use this health data, the healthcare server needs to provide advanced IoT-based healthcare services. All health data stored in the healthcare server were represented by the ISO/IEEE 11073 DIM format. Using the data stored in the healthcare server, the application provides the IoT-based healthcare services.
The communication between 6LoWPAN gateway and healthcare server uses the CoAP protocol. Application uses the HTTP methods such as GET, PUT, POST and DELETE.
To validate our implementations, we have conducted several testing works among the testbed components. By using the ICMPv6 ping test, we can confirm that the 6LoWPAN device and the gateway can be reachable using IPv6 global address over BLE network. Fig. 13 shows the packets exchanged between the healthcare device and the 6LoWPAN gateway. To confirm the communication utilizing the IPv6 address over BLE network, we performed the ICMPv6 Ping test. In this figure, healthcare device can communicate with 6LoWPAN gateway by using IPv6 address.
Fig. 13 Ping packets between device and gateway
Fig. 14 shows the packets between 6LoWPAN gateway and healthcare server. In this figure, we can see that the 6LoWPAN packets over BLE network are converted to the Ethernet packets over Internet network. This implies that 6LoWPAN devices in BLE network can communicate with the devices in another network through Internet.
Fig. 14 Ping packets between gateway and server
Fig. 15 Captured packets at 6LoWPAN gateway
Fig. 15 shows the captured packets at 6LoWPAN gateway which are sent from healthcare device to the healthcare server. The packet sent from healthcare device is delivered to the healthcare server via 6LoWPAN gateway for packet conversion. In this figure, we see that the gateway performs the packet conversion between BLE interface and Ethernet interface, and forwards the packets to the healthcare server.
The above test results show that the Bluetooth devices can communicate with another network by using IP protocol. Fig. 16 shows the enrollment process from healthcare device to healthcare server. From the figure, the healthcare device is registered to the healthcare server by using HTTP.
Fig. 16 Registration packet between device and server
The healthcare server supports HTTP and CoAP. In Fig. 17, we use the CoAP for communication between the 6LoWPAN gateway and the server. In this figure, we can see that the healthcare server receives CON message for request, and it sends ACK message as a response.
Fig. 17 CoAP communication between device and server
By using the GET method, the application can retrieve the value of resources in the healthcare server. Fig. 18 shows the process to get a resource that is saved in the server. In this figure, we can see that the application requests resources
in the container to the healthcare server. In the healthcare server, the resources are stored in container as a
contentInstance.
Fig. 18 Process to get a resource stored in the server
In the proposed architecture, we use CoAP and HTTP in application layer. In general, however, the constrained devices are suitable to CoAP than HTTP. To verify the suitability of the protocols used in constrained devices, we conducted the performance analysis between CoAP and HTTP in testbed. Fig. 19 shows the average transmission time between application and healthcare server by using GET method. We repeated the experiments 200 times.
Fig. 19 Average transmission time (GET)
In the figure, we can see that CoAP gives much faster transmission times than HTTP by 30ms, on the average. This is because the size of CoAP packet is smaller than that of HTTP. That is, CoAP provides higher packet transmission performance than HTTP in the constrained nodes.
V. CONCLUSIONS
In this paper, we presented a new architecture for ISO/IEEE 11073-based healthcare services over IoT platform. The existing Bluetooth device is not suitable to provide IoT-based healthcare services, since the Bluetooth technology do not support the IP protocol. The proposed architecture satisfies the oneM2M and ISO/IEEE 11073
standards. We propose a protocol stack for the constrained healthcare devices over BLE network. In the proposed protocol stack, we designed 6LoWPAN as an IP layer protocol for IP communication over BLE network and CoAP as an application layer protocol for constrained nodes. We represented the healthcare data by using the ISO/IEEE 11073 DIM format so as to follow the healthcare standard. Hence, the proposed architecture is ideal for providing IoT-based healthcare services.
For verification of the proposed architecture, we implemented the ISO/IEEE 11073-based 6LoWPAN communication over BLE network using oneM2M-based platform. From the experimental results, we can see that the proposed architecture operates correctly. In order to compare the protocol efficiency in the constrained devices, we conducted the performance analysis using HTTP and CoAP in testbed. From the results, we see that the CoAP can give better performance than HTTP in terms of data transmission throughputs.
ACKNOWLEDGMENT
This research was supported by the MSIP (Ministry of Science, ICT and Future Planning), Korea, under the SW-Centered University Program (IITP-2015-R2215-15-1004) supervised by the IITP (Institute for Information & Communications Technology Promotion).
REFERENCES
[1] Amendola, Sara, et al. "RFID technology for IoT-based personal healthcare in smart spaces." Internet of Things Journal, IEEE 1.2 (2014): 144-152.
[2] Doukas, Charalampos, and Ilias Maglogiannis. "Bringing IoT and cloud computing towards pervasive healthcare." Innovative Mobile and Internet Services in Ubiquitous Computing (IMIS), 2012 Sixth International Conference on. IEEE, 2012.
[3] Rohokale, Vandana Milind, Neeli Rashmi Prasad, and Ramjee Prasad. "A cooperative Internet of Things (IoT) for rural healthcare monitoring and control." Wireless Communication, Vehicular Technology, Information Theory and Aerospace & Electronic Systems Technology (Wireless VITAE), 2011 2nd International Conference on. IEEE, 2011.
[4] Swetina, Jorg, et al. "Toward a standardized common M2M service layer platform: Introduction to oneM2M." Wireless Communications, IEEE 21.3 (2014): 20-26.
[5] Datta, Soumya Kanti, and Christian Bonnet. "A lightweight framework for efficient M2M device management in oneM2M architecture." Recent Advances in Internet of Things (RIoT), 2015 International Conference on. IEEE, 2015.
[6] Datta, Soumya Kanti, et al. "oneM2M architecture based user centric IoT application development." Future Internet of Things and Cloud (FiCloud), 2015 3rd International Conference on. IEEE, 2015. [7] Isomaki, Markus, et al. “IPv6 over BLUETOOTH (R) Low Energy.”,
IEFT, 2015
[8] Mulligan, Geoff. "The 6LoWPAN architecture." Proceedings of the 4th workshop on Embedded networked sensors. ACM, 2007. [9] Khattak, Hasan Ali, Michele Ruta, and Eugenio Di Sciascio.
“CoAP-basedd healthcare sensor networks: A survey.” Applied Sciences and Technology (IBCAST), 2014 11th International Bhurban Conference
on IEEE, 2014.
[10] Clarke Malcolm, et al. “Developing a Standard for Personal Health Devices based on 11073”, Engineering in Medicine and Biology Society, 2007. EMBS 2007. 29th Annual Internation Conference of
the IEEE. IEEE, 2007.
[11] OCEAN project, http://www.iotocean.org
[12] Santos, Danilo FS, et al. "Integrating IEEE 11073 and constrained application protocol for personal health devices." Proceedings of the 29th Annual ACM Symposium on Applied Computing. ACM, 2014.
