20120220-SOK Phearin-Mobility Management in HIMALIS Architecture

7/31/2019 20120220-SOK Phearin-Mobility Management in HIMALIS Architecture

1/30

Click to edit Master subtitle style

5/14/12

Mobility Management in

HIMALIS ArchitectureAuthors: Ved P. Kafle & Masugi InouePresenter: SOK, PhearinMBC Lab.Konkuk University


2/30

5/14/12

Contents

Introduction

HIMALIS Architecture

Mobility Support

Verification of Architectural Functions

Conclusion


3/30

5/14/12

Introduction


4/30

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 layerprotocol


5/30

5/14/12

Introduction

Heterogeneity Inclusion and MobilityAdaptation through Locator IDSeparation (HIMALIS) architecture is

proposed for a new naming scheme forgenerating host names and IDs byseparating namespaces for host ID andlocator.

Three binding registries:

Domain Name Registry

resolve host names to IDs andlocators initialization phase

distribute host ID to locator binding

updates in the network


6/30

5/14/12

HIMALIS Architecture


7/30

5/14/12

Host Name and IdentifierConfiguration Scheme

Host name:

Variable-length character sets

Find locators and authenticate andauthorize hosts in initialization process

Host ID: Fixed-length bit strings

Control information and packet headers

to identify sessions or packets


8/30

5/14/12



9/30

5/14/12

Global Hostname:

Ex. mbc-pc-1009#mbclab.com

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

hostname, parameter))

Prefix field: aggregate host



10/30

5/14/12

Architectural Layout


11/30

5/14/12

Architectural Layout MainComponents

Local Edge ( or access) Network can bewireless sensor networks, ad-hocnetworks, vehicle networks

Global Transit Network a collection of

service providers backbone networks,provides stable configuration andconnection.


12/30

5/14/12

Architectural Layout MainComponents

Unified Logical ControlNetwork

Unified LogicalNetwork

Unified ControlNetwork

DomainName

Registries

IDRegistrie

s

Maintains and distributesinformation of AAA, QoS,network configuration


13/30

5/14/12

Architectural Layout DomainName Registries

Stores binding information betweendomain names and locators of HostName Registries (HNR)

Binding record does not changefrequently

A hierarchical structurelike theDNS

The smaller DNR mapping table size,


14/30

5/14/12

Architectural Layout IDRegistries

- Detects the binding

update due to mobility

Stores and distributes

bindings between IDs andlocators of all active hostsby propagating to the

correspondent gatewaysand hosts


15/30

5/14/12

Dynamically stores the bindingsbetween host names and IDs, locators,and security keys of the hosts when

hosts physically move to a newnetwork 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,

Architectural Layout HostnameRegistries


16/30

5/14/12

Identity Sublayer in ProtocolStack

An identity sublayer was insertedbetween the transport andnetworklayers.

Relates:

Host ID used in the transport and upperlayers

Locators used in the network layer

Hides the protocol or locator changes


17/30

5/14/12

Hostname Registration and ResolutionProcess


18/30

5/14/12

Hostname Registration andResolution Process

q Communication Types:

Light-weight Communication

MN and CN start their data communicate directly

Secure Communication

MN and CN start data communication afterexchanging control messages


19/30

5/14/12

Mobility Support


20/30

5/14/12

Mobility Support


21/30

5/14/12

Mobility Supportq Two features of the HIMALIS

architecture for mobilitymanagement:

Network layer protocols changelocators without the need ofchanging host IDs in upper layer

protocols

The distributed IDR logical control

network supports faster location


22/30

5/14/12

Verficiation of ArchitecturalFunctions


23/30

5/14/12

Components carries out ID/locatormapping functions:-create and append an

identityheader to thepacket

-send the packet to anappropriate networklayer protocol

maintains sessionstates such as host IDs,

locators, security keys,hash functions,


24/30

5/14/12

Components

- resolve global

host namesinto hostIDs/locators

- Initiatecommunication

with peerhosts

- managemobility andmultihoming

- monitorsstatus ofnetworkinterfaces (i.e.,locators)

- signals theStateManager toupdate thecurrentlyactive locatorsor protocols

Identity Header


25/30

5/14/12

Identity HeaderStructure

The header is used in both signalingand data packets.


26/30

5/14/12

Experimental Layout


27/30

5/14/12

Experimental Layout

IDR

Gateway

HNR

implemented in thesame node

implemented in theseparated node

Linux PCs support L2 handover for thedevice driver of linux

Time in use Host 1 : 8ms for configuration IDR : 4ms for locator request and

response


28/30

5/14/12

Conclusion


29/30

5/14/12

Conclusion

For efficiency in future dynamicnetwork, HIMALIS architectureprovides

A new naming system

Two-layered resolution system

HIMALIS can be a common platform toprovide:

Mobility management


30/30

5/14/12

Thank you

20120220-SOK Phearin-Mobility Management in HIMALIS Architecture

Documents

Transcript of 20120220-SOK Phearin-Mobility Management in HIMALIS Architecture