Content uploaded by Hyeongchoel Park
Author content
All content in this area was uploaded by Hyeongchoel Park on Jan 13, 2024
Content may be subject to copyright.
An Open DDNS based IoT Platform for Providing Home IoT Service in Dynamic IP
Address Environment
Hyeongcheol Park, Sungwon Lee, Eunbae Moon1, Tae-Young Byun2 And Dongkyun Kim1
1School of Computer Science and Engineering
Kyungpook National University, Daegu, Republic of Korea
2School of Computer and Information Communications Engineering,
Catholic University of Daegu, Gyeongsan, Gyeongbuk, Republic of Korea
{hcpark, swlee, ebmoon}@monet.knu.ac.kr, tybyun@cu.ac.kr, dongkyun@knu.ac.kr
Abstract
Nowadays, Internet of Things is a promising solution for
supporting various applications. Among them, a home IoT
service becomes one of the most important application in
future lives. The home IoT services have low robustness in
common networks since not only user but also home
gateway have IP addresses which can be changed
dynamically. For providing robustness to home IoT
services, many companies provide home IoT network
platforms. However, customers of the platform are limited
because these companies receive usage fee from service
users,. Therefore, in this paper, we propose an open DDNS
(Dynamic Domain Name Service) based home IoT
platform which allows customers to use the home IoT
services.
Keywords-component; Internet of Things; Home IoT platform;
Dynamic IP; DDNS
I. Introduction
Due to the rapid growth of smart devices, the market of IoT
(Internet of Things) have increased. IoT is an internetworking
tehchnology to allow things (smartphone, vehicle, bulb,
building and so on) to transmit their information [1]. The
paradigm of IoT can be applied to home, wearable healthcare,
smart car, and factor. Among them, in Home IoT service (such
as fire preventing, gas leak, crime detection and efficient
energy consumption), devices in a house communicate with
not only another home devices but also Internet [2]. Therefore,
home IoT users can control home devices remotely for
managing the home via Internet.
However, if all things in the house are connected to Internet
directly, network overhead can be increased. Hence, in
common houses, only a gateway called home gateway is
connected to Internet and other devices are connected to the
home gateway.
In this home IoT environment, if a user know an IP address
of its home gateway, it can send a control request message
towards the home gateway. However, the IP address of the
home gateway might be changed because of the limitation of
IP addresses. When IP address of the home gateway was
changed and the user did not know the updated IP address, a
control message transmitted from the user would be delivered
to wrong device which has the previous home gateway’s IP
address as shown in figure 1. In other words, the user should
know the updated IP address of home gateway when it
generates the control message to peform correct home IoT
services.
To support IoT services in dynamic IP address environment,
mobile IP (MIP) protocol is proposed [3]. In MIP, when a
mobile device changes its IP address from Home Address
(HA) to Care-of Address (CoA), it notifies the CoA of its
home agent. If the home agent receives packets which include
HA as the destination IP address, it chages the destination IP
address to CoA. After then, the home agent transmits the
packet to the mobile device correctly. In home IoT service
scenario, a home gateway becomes a home agent.
MIP assumes that IP address of the home agent is fixed.
However, in home IoT service sceanario, the home gateway
also has dynamic IP address since some technique proposed to
overcome IP address exhaustion problem such as network
address translation (NAT). In this situation, MIP is not able to
operate correctly. Hence, various telecommunications
company provide home IoT service platform to maintain
connectivity between the home gateway and the mobile
device.
However, to use the home IoT service platform, platform
users should pay extra charges. It cause limitation such as
application diversity, service coverage, and business model.
Furthermore, Home IoT can be difficult to use for vulnerable
group because of the extra charge.
Therfore, in this paper, we propose a new IoT platform
which can provide a connectivity between a home gateway and
mobile devices without additional cost. In the proposed
platform, both of home gateway and mobile device exchange
and update their current IP address using open DDNS
(Dynamic Domain Name Service) [4].
The rest of the paper is organized as follows. Section II
details proposed platform. In Section III, we present a result of
a test based performance evaluation of our solution. Finally,
Section IV concludes this paper.
II. Proposed Platform
As mentioned above, a user can know the home gateway’s IP
address in real time using an open DDNS platform in proposed
architecture. The home gateway saves its own domain name
and IP address into an open DDNS server. The user get the
ICCT 2017
International Conference o n Cultural Technology
- 20 -
home gateway’s IP address from the open DDNS server. The
detail process will be followed.
A. Open Platform
An open platform provides free services and tools which are
related with own function and information through APIs
(Application Programming Interface). Therefore, a mobile
device can know the home gateway’s IP address in real time
via an open platform if the home gateway sends or saves IP
address to the open platform. The open platform can be DDNS,
e-mail, and Push Message Service. In proposed architecture,
using e-mail or Push Message Service for getting a home
gateway’s IP address in real time is not appropriate because it
needs more processing time compared to DDNS. Therefore, in
proposed architecture, home gateway and user utilize open
DDNS platform to update and to get the home gateway’s IP
address.
B. Home Gateway
There are two ways to get a home gateway’s IP address for
users in real time. One is the home gateway sending a changed
IP address directly to users. The other is utilizing a device
which is in static IP address as a broker. In the former one, it is
appropriate if the user device is in a static IP address. But user
device is also in dynamic IP address. Therefore the former one
is not appropriate. In the latter one, the home gateway update
its own IP address to a device which is in static IP address and
a user gets the home gateway’s IP address from the broker
device. In this case, the user device in static or dynamic IP
address environment can get the home gateway’s IP address
from the broker device. We have selected latter one in
proposed architecture.
In proposed architecture, the home gateway update its own IP
address to an open DDNS server when it wakes up. After that,
the home gateway does same process periodically. If the home
gateway’s IP address is changed, it updates its new IP address
to the open DDNS server immediately.
C. User Device
A user device requests a home gateway’s IP address to an
open DDNS server when it needs home IoT service. After the
open DDNS server receives the request, the open DDNS
server replys the IP address and the user device receives it.
After receiving the IP address, the user device set the
destination using received current IP address, and request
home IoT service to the destination. The home gateway
provides the user device with home IoT service when it
receives the home IoT service request. If the user device can’t
receive the service from the home gateway, it tries to request
the home gateway’s IP address to the open DDNS server
again.
III. Performance Evaluation and Analysis
To analyze our proposed scheme between the user and the
home gateway, we used Redbearlab (RBL) TI CC3200 as a
home gateway, Samsung Galaxy S6 Edge 5.0.2 as a user
device, and freeDNS as open DDNS platform. Figure 2 shows
the testbed diagram. A home gateway is located in room 404-2
which have 8m*6m in Engineering Building 9 at Kyungpook
National University. The home gateway gets temperature and
humidity from sensors via BLE (Bluetooth Low Energy) in
every 30 seconds and controsl an air conditioner when the user
requests an air conditioner control service. The home gateway
updates its own current IP in every 5 minutes. A user device is
located 1 kilometer outside the Engineering Building 9. The
user device tries to get the temperature and humidity from the
home gateway via LTE (Long Term Evolution). The user
manages the home temperature using controlling the air
conditioner.
Fig. 2. Experimental testbed
Fi
g
. 1. Flow overview
Oral Presentation (Session A, B, C, D)
- 21 -
Fig. 3. Test result
Figure 3 shows 20 runs that the user device got home
temperature and humidity from home gateway. The home
gateway’s IP address were changed between run 9 and run 10.
Even though IP address was changed, the user device has
succeeded for all of 20 executions. . In this experimental result
indicates the minimum delay is 86ms, maximum delay is
427ms and average delay is 262ms. This result of delay
indicates that it is eligible to use home IoT service. It proves
our proposed scheme can allow user to know the home
gateway’s IP address in dynamic IP address in real time.
IV. Conclusion
We proposed an architecture of providing Home IoT in
dynamic IP address using open DDNS platform without extra
service charges. We have proved that the operation works
successfully. However, there is dependency problem because
this proposed architecture depends on an open DDNS platform.
Therefore, researches are needed, related to providing Home
IoT in dynamic IP address without a broker which we will be
discussing in near future.
Acknowledgment
This study was supported by the BK21 Plus project (SW
Human Resource Development Program for Supporting Smart
Life) funded by the Ministry of Education, School of
Computer Science and Engineering, Kyungpook National
University, Korea (21A20131600005).
References
[1] Luigi Atzoria, Antonio Ierab, Giacomo Morabitoc, “The Internet
of Things: A survey,” Computer Networks, vol. 54, no. 15, pp.
2787–2805, 2010.
[2] Jayavardhana Gubbi, Rajkumar Buyya, Slaven Marusic,
Marimuthu Palaniswami, “Internet of Things (IoT): A vision,
architectural elements, and future directions,” Future Generation
Computer Systems, Volume 29, Issue 7, September 2013, Pages
1645–1660, 2013.
[3] D. Johnson, C. Perkins, J. Arkko, “Mobility Support in IPv6,”
RFC 3775, 2004.
[4] P. Vixie, S. Thomson, Y. Rekhter, J. Bound, “Dynamic Updates
in the Domain Name System (DNS UPDATE),” RFC 2136, 1997.
ICCT 2017
International Conference o n Cultural Technology
- 22 -
