Sponsored by KIISE Information Networking Society

Technically Co-sponsored by IEEE Computer Society

20192019

January 9 (Wed.) - 11 (Fri.), 2019Renaissance Kuala Lumpur Hotel, Kuala Lumpur, Malaysia

www.icoin.org

The 33rd International Conference on Information Networking (ICOIN 2019)

Conference Program

20192019Oral Sessions

January 9, 2019 (Wednesday)

[Oral Sessions 1] IoT and CPS13:30-15:30 Chair : Debasis Das (BITS Pilani, India)

[O-1-1] Secure and Fast Multiple Nodes Join Mechanism for IPv6-based Industrial Wireless Network Yuan Zhuang, Qiaoyue Pang and Min Wei (Chongqing University of Posts and Telecommunications, P.R. China)

[O-1-2] Mobility Management for Healthcare Services in CoAP-based IoT Networks Joong-Hwa Jung and Dong-Kyu Choi (Kyungpook National University, Korea); Ji-in Kim (Research Institude, silla System, Korea); Seok-Joo Koh (Kyungpook National University & College of IT Engineering, Korea)

[O-1-3] Experimental Evaluation of Mobile Core Networks on Simultaneous Access from M2M/IoT Terminals Masaki Ueno, Go Hasegawa and Masayuki Murata (Osaka University, Japan)

[O-1-4 ] Accurate Position Estimation of a Drifting Wireless LAN Communication Device in a 200Mm-Diameter Small Sewer PipeYuki Takei and Zhi Liu (Shizuoka University, Japan); Hiroaki Sawano (Aichi Institute of Technology, Japan); Susumu Ishihara (Shizuoka University, Japan)

[Oral Session 2] Machine Learning and AI13:30-15:30Chair : Joongheon Kim (Chung-Ang University, Korea)

[O-2-1] Resource Centric Characterization and Classification of Applications Using KMeans for Multicores Preeti Jain (Mumbai University, India); Sunil Surve (FrCRCE, India)

[O-2-2] Route Cache Based SVM Classifier for Intrusion Detection of Control Packet Attacks in Mobile Ad-hoc NetworksRobert Basomingera and Young-June Choi (Ajou University, Korea)

[O-2-3] Imbalanced Internet Traffic Classification Using Ensemble Fr amework Phuylai Oeung and Fuke Shen (East China Normal University, P.R. China)

[O-2-4] Binarized Multi-factor Cognitive Detection of Bio-modality Spoofing in Fog Based Medical Cyber- Physical SystemNishat Mowla, Inshil Doh and Kijoon Chae (Ewha Womans University, Korea)

[O-2-5] Self-Driving Car Meets Multi-access Edge Computing for Deep Learning-Based CachingAnselme Ndikumana and Choong Seon Hong (Kyung Hee University, Korea)

[Oral Session 3] Network Security16:00-18:00 Chair : Robert Basomingera (Ajou University)

[O-3-1] Stochastic Heuristic Approach to Addition Chain Problem in PKC for Efficiency and Security EffectivenessAdamu Muhammad Noma (Bauchi State University Gadau, Nigeria); Abdullah Muhammed (Universiti Putra Malaysia, Malaysia)

[O-3-2] Unified Cloud Access Control Model for Cloud Storage BrokerMuhammad Ihsan Haikal Sukmana (Hasso Plattner Institut University Potsdam, Germany); Kennedy A Torkura and Hendrik Graupner (Hasso Plattner Institute, University of Potsdam, Germany); Feng Cheng (University of Potsdam, Germany); Christoph Meinel (Hasso Plattner Institute, University of Potsdam, Germany)

[O-3-3] Trustless Two-Factor Authentication Using Smart Contracts in BlockchainsVarun Amrutiya, Siddhant Jhamb and Pranjal Priyadarsh (BITS, Pilani, India); Ashutosh Bhatia (Birla Institute of Technology and Science, Pilani, India)

[O-3-4] A Lightweight Authentication and Communication Protocol in Vehicular Cloud ComputingHarsha Vasudev (BITS Pilani Goa Campus, Goa, India); Debasis Das (BITS Pilani Goa Campus, India)

[O-3-5] Privacy in the Internet of Vehicles: Models, Algorithms, and ApplicationsMadhur Poddar, Swathi Ganta, Swaraj K. R and Debasis Das (BITS Pilani Goa Campus, India)

[Oral Session 4] Vehicle Network16:00-18:00 Chair : Abdullah Muhammed (UPM, Malaysia)

[O-4-1] Reservation-based Intersection Crossing Scheme for Autonomous Vehicles Traveling in a Speed RangeMyungwhan Choi and Areeya Rubenecia (Sogang University, Korea); Hyo Hyun Choi (Inha Technical College, Korea)

[O-4-2] In-Vehicle Infotainment Management System in Internet-of-Things NetworksDong-Kyu Choi and Joong-Hwa Jung (Kyungpook National University, Korea); Seok-Joo Koh (Kyungpook National University & College of IT Engineering, Korea); Ji-in Kim (Research Institude, silla System, Korea); Juyoung Park (ETRI, Korea)

[O-4-3] Cell Association in Energy-Constrained Unmanned Aerial Vehicle Communications Under Altitude ConsiderationNway Nway Ei, Choong Seon Hong, Chit Wutyee Zaw and Min Kyung Lee (Kyung Hee University, Korea)

12 The 33rd International Conference on Information Networking

XXX-X-XXXX-XXXX-X/XX/$XX.00 ©20XX IEEE

In-Vehicle Infotainment Management System in Internet-of-Things Networks

Dong-Kyu Choi, Joong-Hwa Jung, Seok-Joo Koh* School of Computer Science and Engineering

Kyungpook National University Daegu, Korea

supergint@gmail.com, sjkoh@knu.ac.kr*

Ji-In Kim Silla System Corporation

Daegu, Korea jikim@sillasystem.com

Juyoung Park Protocol Engineering Center

ETRI Daejeon, Korea

jypark@etri.re.kr

Abstract—Recently automobiles have become a part of living space, and researches on in-vehicle infotainment (IVI) for automobiles have been actively made. Even though many automobile manufacturers and software companies have launched the IVI Platform business, there is a lack of research on how to control IVI devices. In addition, there is a problem that many communication methods of IVI device cannot be handled by the IVI master device alone. To solve these problems, in this paper, we propose an IVI management system based on the light-weight machine-to-machine (LWM2M) technology so that it can be used in the Internet-of-Things (IoT) networks. We implemented the proposed system over a simple testbed and verified the proposed efficient management method.

Keywords—In-Vehicle Infotainment, IVI, IVI-Agent, LWM2M, CoAP

I. INTRODUCTION Recent development of ICT convergence technology has been actively promoting the research on smart car [1]. In the early days of the smart car industry, people focused on driving safety and driver supporting using various sensors. Recently, however, they have focused on smart car with the Internet-of-Things (IoT), which involves connected cars, autonomous driving, V2X (Vehicle-to-Things), V2V (Vehicle-to-Vehicle), and driver interaction services. Research on human-friendly IT technology in vehicles has been actively conducted using IoT technology [2]. The development of smart car or autonomous vehicles has transformed the automobile into a living space.

Automobile manufacturers have a variety of convenience and entertainment features in their cars, which is referred to as In-Vehicle Infotainment (IVI) systems for automobiles [3, 4]. Infotainment is a new compound word of information and entertainment. Information means necessary information for driving and guidance, and entertainment includes various entertainments and cultural life functions. The IVI system is an integrated system that supports automobile navigation, connection with DMB, instrument panel, radio, multimedia, various sensors, and external devices. Not only automakers like Mercedes-Benz and BMW, but also software companies such as Google, Apple, Microsoft, and Naver are providing IVI systems for developing these services.

However, there are some problems in the current IVI system. Since each company uses its own proprietary system, it does not support devices other than each company, and there is a lack of research on a standard system for connecting various IVI devices. Next, the current IVI system does not consider the various communication interfaces of each device. Therefore, the Central Processing Unit of IVI (IVI-CPU) needs to include the communication interface of all devices included in the IVI system. This complicates the structure of the IVI-CPU. In addition, the lack of device management techniques is also a problem for users to add/remove the required devices.

To overcome these problems, we propose the IVI management system in the IoT networks. The IVI management system is an IVI device management system based on LWM2M (Lightweight M2M) [5] that can add and remove devices according to user's preference. The LWM2M, which is one of the standard protocols of the IoT, is used in case the added device is the lightweight device as the sensor. We also propose an IVI-Agent node for a flexible extension to other IVI devices, supporting various communication methods of the device. The IVI-Agent node manages each device according to the communication method of the IVI device such as Bluetooth, 6LoWPAN, and Wi-Fi of the IVI device. The IVI management system based on LWM2M can enhance scalability and versatility and lowers entry barriers to small device manufacturers' IVI business by utilizing standard technology.

This paper is organized as follows. Section 2 presents a related works about In-Vehicle infotainment and LWM2M. In Section 3, we discuss the In-Vehicle management system for system architecture, operation flow. In Section 4, we describe the implementation of the IVI management system, and analyze the testbed implementation results, packets, and so on. Finally, we conclude this paper and discuss future works.

II. RELATED WORKS

A. In-Vehicle Infotainment (IVI) In-Vehicle Infotainment is a collective term for entertainment and information system that can be enjoyed in a car. IVI devices or technologies can provide entertainment services

88978-1-5386-8350-7/19/$31.00 ©2019 IEEE ICOIN 2019

such as movies, games, TV, SNS, navigation, and various services that are linked with mobile devices.

In recent years, IVI has been accelerating as convergence of voice recognition and the IoT with automobiles. When a driver gives a voice command, information such as weather, music, and schedule can be checked from the route guide. When a user interacts with the Internet, he/she can operate the home appliance while driving through the IoT networks.

Fig. 1. In-Vehicle infotainment platform

Figure 1 shows an overview of the IVI platform that is currently being developed. Google and Apple have the most technological impacts in the IVI platform market. Google's Android Auto and Apple's Car Play are mounted on a number of automotive brands, which are connected with smartphones that support their operating system (OS) to provide a variety of services including artificial intelligence (AI), voice recognition, contents.

B. Lightweight M2M (LWM2M) LWM2M defines the application layer communication protocol between LWM2M server and LWM2M client for M2M (Machine-to-Machine) or IoT device management which is made by OMA (Open Mobile Alliance). The LWM2M uses CoAP (Constrained Application Protocol) as a communication protocol, which requires a small message size and low execution bandwidth to support a constrained devices. The architecture of the LWM2M consists of M2M devices, called clients and a server that manages them as shown in Figure 2.

As shown in the figure, LWM2M has the four interfaces for device management, which are defined between the server and the client. The clients have objects to manage, and each object has a resource with actual data. An object can be managed as multiple object instances. A resource can have its subordinate resources and is managed as a resource instance.

The bootstrap interface is a process in which a client obtains server information and a security key. It obtains LWM2M server information or security key information through a bootstrap server in a smart card or internal memory at boot time. Usually, the client makes the request first, but sometimes the server does it first.

The registration interface is used when the client registers a resource to the server. The client registers the end-point name, lifetime, queue mode, and supporting object information and instance to the server. The server, receiving the registration

request message, stores the IP address and port of the client. Since the LWM2M supports a plurality of servers, the client performs the registration operation with each server and manages access objects. The objects are defined by the client and used to access control, device connection, monitoring, and firmware.

The device management and service enablement interface is used by the server to monitor and control object instances and resources on the client. Its actions include create, read, write, delete, change properties, perform, and search.

The information reporting interface is used when we want to receive new data from a client object instance or resource. It operates in the form of an asynchronous notification. The server performs an observe operation, when it tries to observe any resource changes of the client, and ends with a cancel observation operation. The notify operation is used by the client to send new data to the server.

Fig. 2. LWM2M system architecture

III. PROPOSED IN-VEHICLE MANAGEMENT SYSTEM In the near future, automobiles are expected to have many additional devices and sensors. As the number of in-vehicle sensors increases, the research will be needed to efficiently use and manage these sensors and sensing information. In this paper, we propose the In-Vehicle infotainment management system in IoT networks.

A. System Architecure The proposed system consists of the master gateway, IVI-Agent, and IVI devices. The master gateway processes information and contents of in-vehicle devices and provides services to the user. The IVI-Agent is used to assist the communication and management operations between the master gateway and in-vehicle devices. The IVI device includes not only devices with the characteristics of contents such as navigation, black box, media player, and Bluetooth speaker, but also devices with the characteristics of information such as temperature and humidity sensor, tire air pressure sensor.

Figure 3 shows the architecture of the proposed IVI management system. The master gateway (Master-GW) stores

89

and manages the information of in-vehicle devices and IVI-Agent, and interacts with user to provide services. The Master-GW manages the information of the IVI devices but does not directly control the IVI devices, delegates it to the IVI-Agent. The IVI-Agent actually manages IVI devices and transmits the command received from the Master-GW to the appropriate device. The IVI-Agent could reduce the load of Master-GW by providing services through direct communication with users in the case of IVI devices that need to provide streaming service to a large amount of data such as a black box.

Fig. 3. Architecture of the proposed system

B. Manageemnt Operations In this section, we discuss the management procedures for IVI devices through the scenario that can occur on the bus. We can see the overview of the scenarios in Figure 4. First of all, we address the process by which a bus driver registers and deregisters new IVI-Agents and IVI devices.

Fig. 4. Outline of IVI service scenario in a bus

1) Registration and Deregistration

The bus driver (a car owner) should be able to register new IVI-Agents or IVI devices to the car. Also, if the new IVI devices to be added uses a communication protocol that cannot be managed by the IVI-Agent, or if there is no IVI-Agent to be connected, the user should register first the IVI-Agent with the Master-GW. IVI devices should also be registered to Master-GW.

Figure 5 shows the operation flows for the registration process of both IVI-Agent and IVI device.

Fig. 5. Operation flow of registration procedure

The process ① means the registration procedure of IVI-Agent. The IVI-Agent makes a registration request to the Master-GW using the POST method which is one of the CoAP methods. When the Master-GW receives a registration request from the IVI-Agent, it verifies whether the same IVI-Agent exists and validity of the information of the IVI-Agent, and sends the 2.01 CREATED message to IVI-Agent.

The process ② shows the registration procedure of IVI devices to IVI-Agent. The IVI device connects with IVI-Agent using Bluetooth, Wi-Fi, serial, and so on. When the IVI device is connected to the IVI-Agent, the IVI-Agent sends the information of the connected device to the Master-GW. This is the process of registering an IVI device.

Fig. 6. Operation flow of deregistration procedure

The deregistration procedure is performed, as shown in Figure 6. The communication between IVI device and IVI-Agent is disconnected. IVI-Agent requests deregistration with Master-GW by using DELETE method to remove the managed device. After receiving this message, the Master-GW clears the information of the corresponding IVI device and sends an ACK message to the IVI-Agent. This completes the disconnection process of the IVI device.

90

In the case of ②, IVI-Agent which does not have any IVI device will now request the deregistration to the Master-GW by using DELETE method. When the IVI-Agent requests removal of the IVI-Agent information, the Master-GW checks the IVI-device connected to the corresponding IVI-Agent and determines whether the IVI-Agent is no longer needed. Then, IVI-Agent deregistration is completed.

2) Direct Control for IVI Devices

In this paper, we use the two control schemes for the devices: direct control and indirect control. In the direct control, the user (car owner) will control the devices directly. In the indirect control, the device control is made via the Master-GW.

Direct control is a control for executing commands that require a large amount of data transmission/reception, such as receiving video from a black box. In this case, the user obtains the rights through the Master-GW and receives services through direct communication with the IVI-Agent. This can reduce more overload on Master-GW. Figure 7 describes the operation flows for direct control.

Fig. 7. Operation flow of Direct Control

3) Indirect Control for IVI Devices

Indirect Control is a control for performing a one-time command such as heated seat operation and reading the sensing value of a specific sensor. This command is transmitted via Master-GW.

Fig. 8. Operation flow of indirect control in case of car owner

Figure 8 shows the indirect control operation flow in the case of the car owner. The owner requests the IVI device list from the Master-GW and receives the IVI device list. The owner will select the device from the list and send the command to the device via Master-GW. In the figure, a heated seat was used for IVI device. The Master-GW forwards the command received from the owner to the IVI-Agent to which the corresponding IVI device is connected. Then, the Master-GW transmits the command through the IVI Agent using the communication method appropriate to the IVI devices.

Figure 9 shows the operation flow of indirect control for non-owner. When the non-owner requests an IVI device list, the Master-GW requests permission to the car owner using the MQTT protocol. If the car owner allows s the non-owner access, then the non-owner can receive the list of IVI devices. The non-owner sends a request message to the Master-GW after selecting the IVI device to use. The Master-GW gives the car owner a non-owner request to use the IVI device. With the owner's approval, the user's command is passed to the IVI device via IVI-Agent.

Fig. 9. Operation flow of indirect control in case of non-owner

IV. IMPLEMENTATION AND EXPERIMENTATION For validation of the proposed system protocol and operation procedure, we implement the proposed IVI management system over a simple testbed. We used the Latte-panda board to implement Master-GW, and Raspberry pi for IVI-Agent. Figure 10 shows the testbed configuration.

Fig. 10. Testbed configuration

91

There are a Master-GW and three IVI-Agents that support Wi-Fi, BLE and serial communication respectively [6, 7]. Wi-Fi is basically used for communication between Master-GW and IVI-Agent, but BLE can also be used for low-power IVI-Agent. In this case, 6LoWPAN has to be used because IVI-Agent communicates with Master-GW using CoAP. It communicates with its own IVI devices via Wi-Fi, BLE and serial communication, respectively.

In this paper, the management operations are implemented and experimented by using Wi-Fi and BLE. Figure 11 is the screen capturing result on Master-GW during the registration process of IVI-Agent and IVI device. In this figure, we can see the CoAP messages transferred to process the registration for IVI-Agent and IVI device.

Fig. 11. Packets captured during registration of IVI-Agent and IVI device

In the proposed system, the direct control scheme is used to reduce the load of the Master-GW in the control which requires transmission of large-capacity information such as the video of the black box. In this scheme, IVI-Agent must support Wi-Fi because the user device does not support 6LoWPAN generally. IVI-Agent and user device will directly communicate with each other, not via Master-GW. Therefore, the IVI-Agent supporting direct control needs to be a high-performance device, not a low-power device.

Figure 12 shows the testbed screen capture for IVI system that was implemented to verify the operation procedure of the proposed system [8- 10]. In the figure, the left part shows the screen of the user's mobile phone application, the middle part shows the screen of the Master-GW, and the right part shows the screen of IVI devices.

Fig. 12. Testbed program screen capture

V. CONCLUSIONS AND FUTURE WORKS Cars have become a mobile platform with the growth of autonomous driving and V2X technologies. Accordingly, a variety of devices for cars are being made, and the system for efficient management of this device are needed. In this paper, we proposed the In-Vehicle Infotainment management system to control and manage these IVI devices. In this system, we proposed IVI-Agent to control various devices with different protocols and defined the operation procedure and method for the effective management and control of IVI devices. The proposed IVI management scheme was verified by implementation and testbed experimentation.

For future works, we will conduct research on resource profiling for a flexible combination of existing devices and IVI-Agents and on optimization of operations.

ACKNOWLEDGMENT This work was supported by BK21 Plus project funded by the Ministry of Education, School of Computer Science and Engineering, Kyungpook National University, Korea (21A20131600005) , and by the Technology Innovation Program on National Standard (20002214), funded by the Ministry of Trade, Industry & Energy.

REFERENCES [1] H. J. Yun, Y. S. Song, J. D. Choi, and J. C. Sohn, “Smart car network

technology and standardization trends,” Electron. And Telecommun. Trends, vol. 30, no. 5, pp. 39-48, oct. 2015.

[2] Jayavardhana Gubbi, Rajkumar Buyya, Slaven Marusic, and Marimuthu Palaniswami, “Internet of Things (IoT): A vision, architectural elements, and future directions,” Future Generation Computer Systems., vol. 29, pp. 1645-1660, Sept. 2013.

[3] J. Kim and T. Han, “Trends of the standard open platform for in-vehicle infotainment and GENIVI based human machine interface,” J. KISS, vol. 36, no. 6, pp. 444-452, Jun. 2012.

[4] S. H. Han, J. H. Jeong, and S. H. Seo, “Developed touch screen vehicle air conditioning control system using GENIVI platform,” in Proc. The Korean Soc. Automotive Eng. Conf. 2017, pp. 722-726, Nov. 2017.

[5] Open Mobile Alliance, “Lightweight Machine-to-Machine Technical Specification v1.0,” Dec. 2015.

[6] A. Mourad, S. Muhammad, M. O. AI Kalaa, Hazem H. Refai, and P. A. Hoeher, “On the performance of WLAN and bluetooth for in-car infotainment systems,” Veh. Commun, vol. 10, pp. 1-12, Oct. 2017.

[7] A. Mourad, S. Muhammad, M. O. AI Kalaa, P. A. Hoecher, and Hazem H. Refai, “Bluetooth and IEEE 820.11n system coexistence in the automotive domain,” in Proc. WCNC Conf. 2017, pp. 19-22, San Francisco CA, USA, May 2017.

[8] B. Kovacevic, M. Kovacevic, T. Maruna, and I. Papp, “Java application programming interface for in-vehicle infotainment device,” IEEE Trans. Consumer Electron., vol. 63, no. 1, pp. 68-76, May 2017.

[9] G. Macario, M. Torchiano, and M. Violante, “An in-vehicle infotainment software architecture based on google android,” in Proc. IEEE International Symposium on Industrial Embedded Systems, Lausanne, Switzerland, July 2009, pp. 257-260, Aug. 2009.

[10] Y. Lee, H. Yoo, and Y. Pan, “Content guidelines for multi-display user experience in autonomous vehicles,” JESK, vol. 36, no. 6, Dec. 2017.

92