Mobility First : Multihoming Extension


Mobility First

MobilityFirst (MF) is an emerging proposal for the new standard of the 5G networking! Mobility first takes a new approach to the Internet by focusing on increasingly dominating communications of mobile devices. The new architecture will pave the ground for a variety of new features including improved scalability, robust wireless signals, enhanced security, a context-sensitive network among other goodies. More information about MobilityFirst? can be found on their (website). A brief introduction of the relevant concepts are summarized below.

This diagram illustrates a projection with increased dominance of mobile devices present in the network. Gone is the dominance of the server-client model - awaken mobile devices''

The old TCP/IP model worked great with servers and desktops that staid put for most of the time. A desktop computers' identity is closely attached to its network address. With MF, identities of machines (ID) are separated from their network address (NA). Instead of using static IPs to identify machines, all devices now have Dynamic Name Address Bindings. These bindings are called Global Unique Identifiers (GUID). In such a way, a group a devices owned by a single user can share the same GUID. Hence, all machines must go through a Global Name Resolution Service (GNRS) which indicates the routing needed to reach said address. The GNRS uses a Distributed Hash Table (DHT) to store routing information in a loosely decentralized way. Unlike the current routing methods of DNS, GNRS stores tons of metadata within the network to make context-dependent situations. Some examples include performing multihoming or allow for geolocation.


Multihoming is a concept that allows for a single device to use multiple interfaces at once. In practice, this means using different physical networks. This is useful for smart phones with two radios that can communicate with wifi and LTE signals simultaneously. Current devices only support the automatice switching between interfaces which is slow (takes a second to restart) and *not* multihoming.

Here is an illustration of what multihoming in practice''


Our goal is to implement multihoming in the MF framework and create improvements to the the efficient division of work between hosts as well as proper lead balancing throughout the network said data is routed through.


Our project used the orbit nodes. We used several nodes on sandbox4 to create a topology of our own. The client and server endpoints were equipped with several network interfaces that supported two ethernet connections, one wifi/wimax card. Additional usb dongles can provide connectivity to the LTE base stations also available in sb4. The intermediate routers ran on CLICK-based software which turned the nodes into live routers. The endpoints ran on a custom stack for the MF network and an additional node was used for the GNRS server which was connected to all nodes.

Bifurcation was performed by adjusting the router code to divide the chunks of data into two streams and forwarding these packets along different routes. Different routing policies are built into the system that adjust the ratio of data based on link quality and path length. A study done on the performance of this round robin routing showed that this technique can actually impede performance when the connection quality vary too much. TODO add citation


TODO Elaborate + screenshots

We have successfully conducted multihoming by adjusting the router code on the bifurcation end. We were able to use the sender and receiver.


You can view our weekly presentations in the presentations below:


Brian Qiu
Electrical and Computer Engineering

Rutgers University
Ramya Tadepalli
Electrical and Computer Engineering

Rutgers University

Project guided by Ivan Seskar & Dipankar Raychaudhuri
With thanks to WINLAB Staff and Faculty for hosting the 2017 Intern Program program for which the project would not exist without.

External References

Last modified 6 weeks ago Last modified on 08/11/17 10:55:25

Attachments (8)

Download all attachments as: .zip