Abstract

It is common to find multiple network interfaces connected to different Internet Service Providers (ISPs) in devices such as smartphones. Multipath TCP (MPTCP) enables TCP connections to use all these network interfaces in a single TCP connection in an application transparent manner. MPTCP schedules traffic of one TCP connection over subflows created over these network interfaces. It is evident that this requires some scheduling policy. There have been some attempts to allow applications to decide on the scheduling policy. However, this violates the application transparency of MPTCP, and applications do not have all the information required to decide on such a policy. In addition, this allows the applications to monopolize the network connection thus posing a security threat as well. We argue that only the owner of the device (the user) has the right to make that policy decision and only the user can make an informed decision on the scheduling policy. For example, the user has the information on the monetary cost of the connections through different interfaces. In this paper we present a mechanism that allows the user to provide hints to the TCP scheduler to alter its scheduling policy. While this is not a mechanism to implement generic scheduling policies, it demonstrates how a user can guide the scheduling policies. As a proof of the concept, we demonstrate how MPTCP scheduler can be influenced to select a less stable and lossy path over a stable path based on a user preference.

Highlights

  • Consider a smartphone with two network interfaces; cellular and WiFi

  • Multipath TCP (MPTCP) Scheduler is responsible for segmentation/integration of data into/from multiple subflows and making the decision on selecting a subflow

  • We believe that the MPTCP Scheduler does not possess or cannot discover all the metrics required to make such a decision independently

Read more

Summary

Introduction

Consider a smartphone with two network interfaces; cellular and WiFi. This device is multihomed - i.e it is connected to the Internet through two different ISPs via the two network interfaces. Assume that a device with two network interfaces. In such a device, it is possible for an application to be aware of both the interfaces and open two TCP connections to a destination through those interfaces. Most mobile devices are equipped with multiple communication interfaces, such as WiFi, Cellular, and Bluetooth. Using an Ad-hoc network can make communication more cost-effective, evading expensive communication via ISPs. Using an Ad-hoc network can make communication more cost-effective, evading expensive communication via ISPs This introduces several challenges, such as prioritizing network packets' flow through the Ad-hoc connection by using the MPTCP and giving the authority to choose when to prioritize the Ad-hoc connection to the user's mobile device. This study aims to combine the infrastructure and Ad-hoc network connections to prioritize the flow of network packets through the Ad-hoc network and obtain the user's hint in deciding when to prioritize the Ad-hoc connection

Objectives
Methods
Results
Discussion
Conclusion
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