Controlling the handover mechanism in wireless mobile nodes using game theory

This paper proposes a novel network selection mechanism as an extension to the FMIPv6 [2] protocol, which improves handover latency in the MIPv6 [1] in the case where the Mobile Nodes (MN) have a single wireless interface with multiple Care-of-Addresses (CoA’s). Moreover, this paper proposes a novel interface/network selection mechanism, which is an extension to the MFMIPv6 [5], which work when the mobile node has more than one wireless interface. Generally, the previous access router (PAR) in the FMIPv6 protocol forwards all the arrived packets to the new access router (NAR) by setting up a tunnel to it in order to prevent packet losses incurred by latency during handover procedure. However, there is no protocol which offers the user and/or the application to dynamically choose the right NAR (i.e. the one offers a better service). What’s more, one of the main objectives of the next generation networks will be heterogeneity in the wireless access environment in which a mobile terminal will be able to connect to multiple radio networks simultaneously. For these reasons, network selection and efficient load balancing mechanisms among different networks will be required to achieve high-speed connectivity with seamless mobility. To this end; Game Theory [3], naturally becomes a useful and powerful tool to research this kind of problems. Game theory is a mathematical tool developed to understand competitive situations in which rational decision makers interact to achieve their objectives. The mechanism improves the handover latency, the user ability to choose the right interface/network and controls when to force the MN to make the handover

High-speed, in-band performance measurement instrumentation for next generation IP networks

Facilitating always-on instrumentation of Internet traffic for the purposes of performance measurement is crucial in order to enable accountability of resource usage and automated network control, management and optimisation. This has proven infeasible to date due to the lack of native measurement mechanisms that can form an integral part of the network‟s main forwarding operation. However, Internet Protocol version 6 (IPv6) specification enables the efficient encoding and processing of optional per-packet information as a native part of the network layer, and this constitutes a strong reason for IPv6 to be adopted as the ubiquitous next generation Internet transport. In this paper we present a very high-speed hardware implementation of in-line measurement, a truly native traffic instrumentation mechanism for the next generation Internet, which facilitates performance measurement of the actual data-carrying traffic at small timescales between two points in the network. This system is designed to operate as part of the routers' fast path and to incur an absolutely minimal impact on the network operation even while instrumenting traffic between the edges of very high capacity links. Our results show that the implementation can be easily accommodated by current FPGA technology, and real Internet traffic traces verify that the overhead incurred by instrumenting every packet over a 10 Gb/s operational backbone link carrying a typical workload is indeed negligible

MeshRouter Primitives: Messages, Interest, and Interpreters

The MeshRouter architecture provides a general framework for interest-limited message ex- changes among client processes. There are two general areas in which the MeshRouter im- plementation depends on specics of the associated clients: i) the lowest level inter-processor communications model and ii) the nature/content of exchanged messages and \interest". This note describes the hierarchical object design (C++ sense) used to implement the basic Message and Interest objects of the MeshRouter. Interfaces are dened in terms of abstract base classes, and specific inherited objects appropriate for the RTI-s/JSAF application are presented as concrete examples. The MeshRouter system includes a substantial memory management com- ponent for efficient use of the basic Message objects. This system is summarized and plausible near-term extensions are noted

Fast emergency paths schema to overcome transient link failures in ospf routing

A reliable network infrastructure must be able to sustain traffic flows, even when a failure occurs and changes the network topology. During the occurrence of a failure, routing protocols, like OSPF, take from hundreds of milliseconds to various seconds in order to converge. During this convergence period, packets might traverse a longer path or even a loop. An even worse transient behaviour is that packets are dropped even though destinations are reachable. In this context, this paper describes a proactive fast rerouting approach, named Fast Emergency Paths Schema (FEP-S), to overcome problems originating from transient link failures in OSPF routing. Extensive experiments were done using several network topologies with different dimensionality degrees. Results show that the recovery paths, obtained by FEPS, are shorter than those from other rerouting approaches and can improve the network reliability by reducing the packet loss rate during the routing protocols convergence caused by a failure.Comment: 18 page

Preserving Established Communications in IPv6 Multi-homed Sites with MEX

This research was supported by the SAM (Advanced Mobility Services) project, funded by the Spanish National R&D Programme under contract MCYT TIC2002-04531-C04-03.A proper support for multimedia communications transport has to provide fault tolerance capabilities such as the preservation of established connections in case of failures. While multi-homing addresses this issue, the currently available solution based in massive BGP route injection presents serious scalability limitations, since it contributes to the exponential growth of the BGP table size. Alternative solutions proposed for IPv6 fail to provide equivalent facilities to the current BGP based solution. In this paper we present MEX (Muti-homing through EXtension header) a novel proposal for the provision of IPv6 multi-homing capabilities. MEX preserves overall scalability by storing alternative route information in end-hosts while at the same time reduces packet loss by allowing routers to re-route in-course packets. This behavior is enabled by conveying alternative route information within packets inside a newly defined Extension Header. The resulting system provides fault tolerance capabilities and preserves scalability, while the incurred costs, namely deployment and packet overhead, are only imposed to those that benefit from it. An implementation of the MEX host and router components is also presented.Publicad

Mobile IP: state of the art report

Due to roaming, a mobile device may change its network attachment each time it moves to a new link. This might cause a disruption for the Internet data packets that have to reach the mobile node. Mobile IP is a protocol, developed by the Mobile IP Internet Engineering Task Force (IETF) working group, that is able to inform the network about this change in network attachment such that the Internet data packets will be delivered in a seamless way to the new point of attachment. This document presents current developments and research activities in the Mobile IP area

Future wireless applications for a networked city: services for visitors and residents

Future wireless networks will offer near-ubiquitous high-bandwidth communications to mobile users. In addition, the accurate position of users will be known, either through network services or via additional sensing devices such as GPS. These characteristics of future mobile environments will enable the development of location-aware and, more generally, context-sensitive applications. In an attempt to explore the system, application, and user issues associated with the development and deployment of such applications, we began to develop the Lancaster GUIDE system in early 1997, finishing the first phase of the project in 1999. In its entirety, GUIDE comprises a citywide wireless network based on 802.11, a context-sensitive tour guide application with, crucially, significant content, and a set of supporting distributed systems services. Uniquely in the field, GUIDE has been evaluated using members of the general public, and we have gained significant experience in the design of usable context-sensitive applications. We focus on the applications and supporting infrastructure that will form part of GUIDE II, the successor to the GUIDE system. These developments are designed to expand GUIDE outside the tour guide domain, and to provide applications and services for residents of the city of Lancaster, offering a vision of the future mobile environments that will emerge once ubiquitous high-bandwidth coverage is available in most cities

Deliverable DJRA1.2. Solutions and protocols proposal for the network control, management and monitoring in a virtualized network context

This deliverable presents several research proposals for the FEDERICA network, in different subjects, such as monitoring, routing, signalling, resource discovery, and isolation. For each topic one or more possible solutions are elaborated, explaining the background, functioning and the implications of the proposed solutions.This deliverable goes further on the research aspects within FEDERICA. First of all the architecture of the control plane for the FEDERICA infrastructure will be defined. Several possibilities could be implemented, using the basic FEDERICA infrastructure as a starting point. The focus on this document is the intra-domain aspects of the control plane and their properties. Also some inter-domain aspects are addressed. The main objective of this deliverable is to lay great stress on creating and implementing the prototype/tool for the FEDERICA slice-oriented control system using the appropriate framework. This deliverable goes deeply into the definition of the containers between entities and their syntax, preparing this tool for the future implementation of any kind of algorithm related to the control plane, for both to apply UPB policies or to configure it by hand. We opt for an open solution despite the real time limitations that we could have (for instance, opening web services connexions or applying fast recovering mechanisms). The application being developed is the central element in the control plane, and additional features must be added to this application. This control plane, from the functionality point of view, is composed by several procedures that provide a reliable application and that include some mechanisms or algorithms to be able to discover and assign resources to the user. To achieve this, several topics must be researched in order to propose new protocols for the virtual infrastructure. The topics and necessary features covered in this document include resource discovery, resource allocation, signalling, routing, isolation and monitoring. All these topics must be researched in order to find a good solution for the FEDERICA network. Some of these algorithms have started to be analyzed and will be expanded in the next deliverable. Current standardization and existing solutions have been investigated in order to find a good solution for FEDERICA. Resource discovery is an important issue within the FEDERICA network, as manual resource discovery is no option, due to scalability requirement. Furthermore, no standardization exists, so knowledge must be obtained from related work. Ideally, the proposed solutions for these topics should not only be adequate specifically for this infrastructure, but could also be applied to other virtualized networks.Postprint (published version

Requirements of a middleware for managing a large, heterogeneous programmable network

Programmable networking is an increasingly popular area of research in both industry and academia. Although most programmable network research projects seem to focus on the router architecture rather than on issues relating to the management of programmable networks, there are numerous research groups that have incorporated management middleware into the programmable network router software. However, none seem to be concerned with the effective management of a large heterogeneous programmable network. The requirements of such a middleware are outlined in this paper. There are a number of fundamental middleware principles that are addressed in this paper; these include management paradigms, configuration delivery, scalability and transactions. Security, fault tolerance and usability are also examined—although these are not essential parts of the middleware, they must be addressed if the programmable network management middleware is to be accepted by industry and adopted by other research projects