Abstract

In this paper, we propose an enhanced file transfer mechanism for a communication framework (CM) for Internet of Things (IoT) applications. Our previous file transfer method uses a basic non-blocking communication channel and thread for the CM (non-blocking method), but this method has a cost of adding additional bytes to each original file block. Therefore, it is not suitable for the transfer of large-sized files. Other existing file transfer methods use a separate channel to transfer large-sized files. However, the creation of a separate channel increases the total transmission delay as the transfer frequency increases. The proposed method uses a dedicated blocking communication channel in a separate thread (blocking method). The blocking method uses a separate channel and thread which are dedicated to transferring file blocks. As it creates the separate channel in advance before the file transfer task, the proposed method does not have an additional channel creation cost at the moment of the file transfer. Through file transfer experiments, the blocking method showed a shorter file transfer time than the non-blocking method, and the transmission delay was increased as the file size grew. By supporting both non-blocking and blocking methods, an application can flexibly select the desirable method according to its requirement. If the application requires the transfer of small-sized files infrequently, it can use the non-blocking method. If the application needs to transfer small-sized or large-sized files frequently, a good alternative is to use the blocking method.

Highlights

  • Many of today’s multiuser-based distributed applications such as online games, social networking systems (SNS), and file sharing systems provide various communication functions for efficient interaction among users

  • We proposed a communication framework (CM) that selectively provides a file transfer service according to the requirements of Internet of Things (IoT) applications

  • The CM file transfer service consists of two methods: non-blocking and blocking methods

Read more

Summary

Introduction

Many of today’s multiuser-based distributed applications such as online games, social networking systems (SNS), and file sharing systems provide various communication functions for efficient interaction among users. Existing file transfer methods specialized for large-scale file transfer are not suitable for transferring relatively small-sized files at a high frequency because each file transfer requires the creation of additional communication channels which are separate from the control channel. Our previous file transfer mechanism of CMSNS, which is called the non-blocking method, uses a control channel (a basic non-blocking communication channel) to transfer a file, and it does not need the cost of additional channel management. The transmission of a CM event required for the preprocessing and postprocessing of the file transfer between the transmitting node and the receiving node uses the basic non-blocking channel, and the transmission of the file block generates and uses the dedicated blocking channel and the thread separately This method is suitable for frequently transferring small-sized or large-sized files because the file block is directly transferred without being converted into a CM event. When the server performs the requested service, the server CM creates a response event and sends it back to the client

Event-Based Asynchronous Communication
Communication
Concept
The server
Experimental Results
Related Work
Conclusions
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call