Mobility Management in HIMALIS Architecture

30
Authors: Ved P. Kafle & Masugi Inoue Presenter: SOK, Phearin MBC Lab. Konkuk University

description

Mobility Management in HIMALIS Architecture

Transcript of Mobility Management in HIMALIS Architecture

Page 1: Mobility Management in HIMALIS Architecture

Authors: Ved P. Kafle & Masugi InouePresenter: SOK, Phearin

MBC Lab.Konkuk University

Page 2: Mobility Management in HIMALIS Architecture

• Introduction

• HIMALIS Architecture

• Verification of Architectural Functions

• Conclusion

Page 3: Mobility Management in HIMALIS Architecture
Page 4: Mobility Management in HIMALIS Architecture

Many researches on Future Internet or Next Generation Network: FIND and GENI – United States AKARI – Japan FIF – Korea EIFFEL – Europe

Researches focus on new designs of: Routing/Addressing architectures Mobility Security

Page 5: Mobility Management in HIMALIS Architecture
Page 6: Mobility Management in HIMALIS Architecture

IP address is used as:

• Host Identifier (ID) – identify communication session in transportand upper layer protocol

• Locator – locate the destination host and forward packets in network layer protocol

Host movement leads to session termination

Page 7: Mobility Management in HIMALIS Architecture

• Heterogeneity Inclusion and Mobility Adaptation through Locator ID Separation (HIMALIS) architecture is proposed for a new naming schemefor generating host names and IDs by separating namespaces for host ID and locator.

• Three binding registries: Domain Name Registry

Host Name Registry

ID Registry

resolve host names to IDs and locators initialization phase

distribute host ID to locator binding updates in the network

Page 8: Mobility Management in HIMALIS Architecture
Page 9: Mobility Management in HIMALIS Architecture

• Host name:

Variable-length character sets

• Host ID:

Fixed-length bit strings

Control information and packet headers to identify sessions or packets

Page 10: Mobility Management in HIMALIS Architecture
Page 11: Mobility Management in HIMALIS Architecture

• Global Hostname:Ex. mbc-pc-1009#mbclab.com

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

– Prefix field: aggregate host

– Version field: derivation of host ID by using different parameters of hash function – MD5 or SHA-1

– Scope field: private, public, local or global

Page 12: Mobility Management in HIMALIS Architecture
Page 13: Mobility Management in HIMALIS Architecture

• Local Edge ( or Access) Network can be wireless sensor networks, ad-hoc networks…

• Global Transit Network – a collection of service provider’s backbone networks, provides stable configuration and connection

Page 14: Mobility Management in HIMALIS Architecture

• Unified Logical Control Network

Unified Logical Network Unified Control Network

Domain Name

Registries

ID Registries

Maintains and distributesinformation of AAA, QoS, network configuration…

Page 15: Mobility Management in HIMALIS Architecture
Page 16: Mobility Management in HIMALIS Architecture

• Stores binding information between domain names and locators of Host Name Registries (HNR) of each Edge Network

• Binding record does NOT change frequently

• A hierarchical structure like the

DNS

Page 17: Mobility Management in HIMALIS Architecture

-Detects the binding update due to mobility

-Uploads the update to IDR.

Stores and distributes bindings between IDs and locators of all

active hosts by propagating to the correspondent gateways and hosts

Page 18: Mobility Management in HIMALIS Architecture

• 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, …

Page 19: Mobility Management in HIMALIS Architecture

• Relates:Host ID used in the transport and upper layersLocators used in the network layer

• Hides the protocol or locator changes from transport layer to application layer.Ex. IPv4 to IPv6 changes in Network layer protocol

Page 20: Mobility Management in HIMALIS Architecture
Page 21: Mobility Management in HIMALIS Architecture

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

Page 22: Mobility Management in HIMALIS Architecture
Page 23: Mobility Management in HIMALIS Architecture

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

header to the packet-send the packet to an

appropriate network layer protocol

maintains session states such as host IDs, locators, security keys, hash functions, …

Page 24: Mobility Management in HIMALIS Architecture

- resolve global host names into host IDs/locators

- Initiate communication with peer hosts

- manage mobility and multihoming

- monitors statusof network interfaces (i.e., locators)

- signals the State Manager to update the currently activelocators or protocols

Page 25: Mobility Management in HIMALIS Architecture

The header is used in both signaling and data packets.

Page 26: Mobility Management in HIMALIS Architecture
Page 27: Mobility Management in HIMALIS Architecture

• IDR

• Gateway

• HNR

implemented in the same node

implemented in the separated node

• Linux PCs – support L2 handover for the device driver of linux

• Time in use

• Host 1 : 8ms for configuration

• IDR : 4ms for locator request and response

Page 28: Mobility Management in HIMALIS Architecture
Page 29: Mobility Management in HIMALIS Architecture

• 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:– Mobility management

– Resource discovery

Future work: network management and control.

Page 30: Mobility Management in HIMALIS Architecture

THANK YOU