IP mobility with high speed access and network intelligence

Abstract

The original idea of Mobile IP (MIP) is to provide mobile users the ability to access the Internet anywhere, with an identical IP address. With rapid changes in both technology and the communication environment, wide bandwidth and low cost wireless LAN (WLAN) have emerged as a competitive choice not only for wireless high speed Internet access but also for wireless voice network access. To support mobility with Quality of Service (QoS), MIP has been found to be inefficient for both data and time sensitive services, such as Voiceover-IP (VoIP). In our paper, we first focus on the deficiencies of the MIP and other micro-mobility approaches found in the literature. We then propose an architecture for network layer mobility support, using always on high speed access and a network-based mobility manager, termed as network server or gateway. We believe that the proposed architecture obviates the need of MIP for IP mobility.

Gateway performance for network‐controlled WLAN IP mobility

“…Both analytical and simulation results show that WIP handoff message processing delay at WIP GW has negligible impact on the overall system delay. The paper compliments the previous works published [1,[3][4][5].…”

“…Thus, all the BCPs, provisioned and connected to the GW over a PVC, would be under the same virtual network, regardless of the BCPs' geographic locations. This broadband-facilitated WIP network model mobility [3] has gone beyond the traditional WLAN mobility. When the GW receives the registration message, it updates the location management and routing table, by associating the MN's IP address with the BCP IP address.…”

“…Here, a configurable processor is used to achieve fast IP route lookup (66 million lookups per second (MLPS)) for the processor at 200 MHz: Depending on the traffic size, a service provider needs to assess the given MLPS capability. In WIP architecture [3], all the incoming packets are routed through the GW to facilitate mobility management. Packet forwarding requires routing table lookup based on the IP destination field in the IP header.…”