110 likes | 233 Vues
This paper by Heeyoung Jung from ETRI explores the HINLO architecture, a novel Host Identifier and Network Locator (ID/LOC) split solution tailored for mobile environments. With the global mobile user base expected to surpass 1.6 billion, traditional internet designs face limitations in addressing mobility and routing scalability. HINLO addresses these challenges by separating Host IDs from Location IDs, enabling efficient mobility support and enhancing security. The paper highlights requirements, procedures, and expected performance improvements in mobile networking.
E N D
HINLO: An ID/LOC Split Scheme for Mobile Oriented Future Internet Heeyoung JUNG ETRI (Electronics & Telecommunications Research Institute) Republic of KOREA
Background • Mobile trends • Wide popularity of smart phones and emergence of various wireless/mobile networks • “The number of mobile users will be more than 1.6 billion in around 2014 and thus exceed the number of desktop users” [Morgan Stanley report 2010] • The mobile trend was not considered in the design of original Internet • Many (possible) limitations in mobile environment • Typical one is overloaded semantic of IP address • Major source of mobility and routing scalability • ID/LOC split is being recognized as a promising solution • HINLO (Host Id and Network LOcator) is an ID/LOC split solution for mobile environment
ID Requirements for Mobile Environment • Mobile host is mandatory and fixed host is special • Mobile hosts will be dominant • Host ID and LOC should be separated • LOC for routing and ID for upper layers • ID for host itself is necessary • To efficiently support mobility and multi-homing • Support of hosts with multiple interfaces • LOC does not need to be allocated to host • Static LOC allocation for moving hosts is meaningless • Network based control to support lightweight host • More secure ID structure • Mobile environment is more vulnerable for attack
HINLO Architecture IP address is allocated to network i/f and used as both ID and LOC Internet • IP address is allocated to host itself and ID and LOC is separated • LBS provides the mapping information AN: Access Network AR: Access Router LBS: Location Binding Server HINLO
How to Bind HID and LOC • LBS is responsible for the binding between HID and LOC • Distributed LBS is preferred for scalability • Procedures • HID is informed to AR during attachment • Implicitly or Explicitly • If an AR realizes that a new host is attached, it registers the information (HID:LOC of AR) to LBS by sending LOC Binding Request, on behalf of the host • LBS confirms this binding by replying with a LOC Binding ACK • When the host moves into another AR region, the same procedure will be repeated
Packet Delivery AN specific delivery AN specific delivery LOC based routing
Characteristics Comparison Note: 1) Detail format is for further study
Packet Delivery Cost (a) Impact of transmission delay b/w AR and LBS (b) Impact of transmission delay b/w MH and AR
Conclusions • This paper • Identified a set of requirements for mobile oriented ID/LOC split scheme • Proposed the architecture of HINLO that satisfies the requirements • Notable features of HINLO • Allocates LOC to a AR, not a host, whereas a host has only its ID • Can be a incremental approach to allow AN heterogeneity and the use of IPv4/v6 in core • Expected to show much better handover performance than existing ones because of its address-free feature in host • HINLO is being developed as a part of a Korea government funded project on Future Internet • For more information, please visit “www.mofi.re.kr”