Enabling multi-hop remote method invocation in device-to-device networks

Abstract

IntroductionResource sharing or computation offloading on mobile networks can bring a lot of benefits, the approaches in this domain if possible, can be widely applied to IoT networks or ubiquitous cities. In this section, we will go through the several limitations of current technologies, as well as our motivation to build a middleware that overcomes these obstacles by extending Remote Method Invocation method and multi-hop capability to enable resource sharing over mobile networks.Low-end devices always have trouble running intensive resource-consuming applications such as image or video processing, which remarkably slow down its speed and drain energy. One well-known solution is having the device participate in a collaboration in which it can offload or migrate intensive code portions [1-3] onto another device or cloud server with copious resource capacity, have them execute the code and wait for responses [4,5]. Although the idea is straightforward, code offloading has not been widely applied in the mobile industry due to several issues: it requires AbstractTo avoid shrinking down the performance and preserve energy, low-end mobile devices can collaborate with the nearby ones by offloading computation intensive code. However, despite the long research history, code offloading is dilatory and unfit for applications that require rapidly consecutive requests per short period. Even though Remote Procedure Call (RPC) is apparently one possible approach that can address this problem, the RPC-based or message queue-based techniques are obsolete or unwieldy for mobile platforms. Moreover, the need of accessibility beyond the limit reach of the device-to-device (D2D) networks originates another problem. This article introduces a new software framework to overcome these shortcomings by enabling routing RPC architecture on multiple group device-to-device networks. Our framework provides annotations for declaring distribution decision and out-of-box components that enable peer-to-peer offloading, even when a client app and the service provider do not have a direct network link or Internet connectivity. This article also discusses the two typical mobile applications that built on top of the framework for chatting and remote browsing services, as well as the empirical experiments with actual test-bed devices to unveil the low overhead conduct and similar performance as RPC in reality. which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.

Extending Wi-Fi Direct Single-Group Network to Multi-Group Network Based on Android Smartphone

“…There are two limitations in Wi-Fi Direct technology that restrict the groups to connect and create an ad hoc network. The limitations are [15]: 1-The smartphone cannot be a P2P client of more than one group at the same time. 2-The GO of a group cannot be a P2P client of another group at the same time.…”

A Mini Review of Peer-to-Peer (P2P) for Vehicular Communication

“…Through technological advancement, computer systems can be designed which allow an individual to operate remotely without any necessity. In addition, any individual could share data and link printers to one another with the help of P2P computing [13].…”

A systematic review of IoT communication strategies for an efficient smart environment

“…15 CoAP, constrained application protocol; D2A, device-to-application; D2C, device-to-cloud; D2D, device-to-device; D2G, device-to-gateway; IoT, Internet of Things; IP, Internet protocol; MQTT, message queuing telemetry transport; RFID, radio-frequency identification technologies such as sensor technology, cloud-based technology, messaging technology, IP technology, and wireless technology. 18,19 In order to connect the smart devices in IoT environment, some key technologies are applied such as wireless technology, sensor technology, messaging technology, gateway technology, and IP technology. [20][21][22] Besides, the communication types can have two main characteristics including application-wise or topology-wise.…”

“… Device-to-Cloud (D2C) communication: presents a directional interconnection between IoT devices and cloud service providers to transfer information and resources with controlling messages and sensors using existing communication technologies such as sensor technology, cloud-based technology, messaging technology, IP technology, and wireless technology [17]:…”