Click to edit Master subtitle style Mobility Management in HIMALIS Architecture Authors: Ved P.

Kafle & Masugi Inoue Presenter: SOK, Phearin MBC Lab. Konkuk University 5/14/12

Contents

Introduction HIMALIS Architecture Mobility Support Verification of Architectural Functions Conclusion

5/14/12

Introduction

5/14/12

Introduction

IP address is used as:

Host Identifier (ID) identify communication session in transport and upper layer protocol Locator locate the destination host and forward packets in network layer protocol

5/14/12

Introduction

Heterogeneity Inclusion and Mobility Adaptation through Locator ID Separation (HIMALIS) architecture is proposed for a new naming scheme for generating host names and IDs by separating namespaces for host ID and locator. Three binding registries:
5/14/12

resolve host names to IDs and locators initialization phase

Domain Name

distribute host ID to locator binding Registry in the network updates

HIMALIS Architecture

5/14/12

Host Name and Identifier Configuration Scheme

Host name:

Variable-length character sets Find locators and authenticate and authorize hosts in initialization process

Host ID:

Fixed-length bit strings

Control information and packet headers to identify sessions or packets 5/14/12

Host Name and Identifier Configuration Scheme

5/14/12

Host Name and Identifier Configuration Scheme

Global Hostname:

Ex. mbc-pc-1009#mbclab.com

Host ID = concatenation(prefix, scope, version, hash function(global hostname, parameter))

5/14/12 Prefix

field: aggregate host

Architectural Layout

5/14/12

Architectural Layout Main Components

Local Edge ( or access) Network can be wireless sensor networks, ad-hoc networks, vehicle networks Global Transit Network a collection of service providers backbone networks, provides stable configuration and connection.
5/14/12

Architectural Layout Main Components

Unified Logical Control Network

Unified Logical Network

Domain Name Registri es ID Registrie s

Unified Control Network

Maintains and distributes information of AAA, QoS, network configuration

5/14/12

Architectural Layout
Name Registries

Domain

Stores binding information between domain names and locators of Host Name Registries (HNR) Binding record does not change frequently A hierarchical structure like the DNS The smaller DNR mapping table size,

5/14/12

Architectural Layout
Registries

ID

Stores and distributes bindings between IDs and locators of all active hosts by propagating to the correspondent gateways and hosts

5/14/12

Detects the binding update due to mobility

Architectural Layout
Registries

Hostname

Dynamically stores the bindings between host names and IDs, locators, and security keys of the hosts when hosts physically move to a new network or activate different interfaces. Host registration

Hosts register their names, IDs, locators, with HNR when first connecting

Hosts send registration update request to HNR when changing their IDs, locators, 5/14/12

Identity Sublayer in Protocol Stack

An identity sublayer was inserted between the transport and network layers. Relates:

Host ID used in the transport and upper layers Locators used in the network layer

5/14/12

Hides the protocol or locator changes

Hostname Registration and Resolution Process

5/14/12

Hostname Registration and Resolution Process

q

Communication Types:

Light-weight Communication

MN and CN start their data communicate directly

Secure Communication

MN and CN start data communication after exchanging control messages

5/14/12

Mobility Support

5/14/12

Mobility Support

5/14/12

Mobility Support
q

Two features of the HIMALIS architecture for mobility management:

Network layer protocols change locators without the need of changing host IDs in upper layer protocols

The distributed IDR logical control 5/14/12 network supports faster location

Verficiation of Architectural Functions

5/14/12

Functional Components maintains session

states such as host IDs, locators, security keys, hash functions,

carries out ID/locator mapping functions: -create and append an identity header to the packet -send the packet to an appropriate network layer protocol

5/14/12

Functional Components
- resolve global host names into host IDs/locators - Initiate communication with peer hosts - manage mobility and multihoming - monitors status of network interfaces (i.e., locators) - signals the State Manager to update the currently active locators or protocols

5/14/12

The header is used in both signaling and data packets.

Identity Header Structure

5/14/12

Experimental Layout

5/14/12

Experimental Layout

IDR Gatewa y

implemented in the same node implemented in the separated node

HNR PCs support L2 handover for the Linux device driver of linux Time in use

5/14/12

Host 1 : 8ms for configuration IDR : 4ms for locator request and response

Conclusion

5/14/12

Conclusion

For efficiency in future dynamic network, HIMALIS architecture provides

A new naming system Two-layered resolution system

HIMALIS can be a common platform to provide:

5/14/12

Mobility management

Thank you
5/14/12