Realization of Multiple Access Interface Management and Flow Mobility in IPv6

Abstract

Internet capable mobile or portable devices are already a modern commodity while it is becoming more and more common that such devices are hosts to more than one wireless network interface. The aim of this work is to show from a user's perspective how such a portable device may make best use of this property by using multiple wireless and wired network interfaces simultaneously. This would incline that the intelligent control logic can distribute active flows across the available network interfaces and that it is also able to seamlessly transfer them between the network interfaces in mid-session without interruption. Focus of this work is on the inclusion of user preferences in the decision process, recognizing that future telecommunication systems may include also network conditions and operator preferences.

Multihoming: A Comprehensive Review

“…The specification of flow bindings [4,89] extends MIPv6 and MCoA specifications defining how multiple flows can be exchanged between two nodes, in a multihoming context. This enables to bind a particular flow to a Care of Address and use another address to receive information from other flows.…”

Multihoming aware optimization mechanism

“…The mobile node is always reachable at a unique permanent IPv6 address (employed as an identifier) while several temporary addresses (Care of Addresses) are used as locators to reveal the current network location of the node. The specification of flow bindings [Tsirtsis et al, 2011a;Toseef et al, 2008] …”

“…Multiple Care of Address (MCoA) [Pan et al, 2008a] The specification of flow bindings [Tsirtsis et al, 2011a;Toseef et al, 2008] extends MCoA specification defining how multiple flows can be exchanged between two nodes, in a multihoming context. This enables to bind a particular flow to a Care…”

“…The flow bindings specification conveys policies between the mobile node and other mobility agents (e.g. home agents) [Toseef et al, 2008]. Whilst the flow bindings specification deals with the transfer of policies, the way they can be generated or mapped to user preferences (e.g.…”

The “Always Best Packet Switching” architecture for SIP-based mobile multimedia services

“…The Flow Mobility technique (FlowMob) described in [32] uses this extension to allow the MN to separate its outgoing traffic in different flows based on the protocols, port numbers and IP addresses, and forward each given flow using a selected NIC. This technique allows a flow-based switching through the MN's NICs.…”