Mobility Management in HIMALIS Architecture

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

2. • Introduction
• HIMALIS Architecture
• Verification of Architectural Functions
• Conclusion

4. 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

6.  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
 Host movement leads to session
termination

7. • 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:
 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

9. • Host name:
 Variable-length character sets
• Host ID:
 Fixed-length bit strings
 Control information and packet headers to
identify sessions or packets

11. • 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

13. • 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

14. • Unified Logical Control Network
Unified Logical Network Unified Control Network
Domain
Name
Registries
ID
Registries
Maintains and distributes
information of AAA, QoS,
network configuration…

16. • 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

17. Stores and distributes bindings
between IDs and locators of all
active hosts by propagating to the
correspondent gateways and hosts
-Detects the binding update
due to mobility
-Uploads the update to IDR.

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

19. • Relates:
Host ID used in the transport and upper layers
Locators 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

21. 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

23. carries out ID/locator
mapping 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, …

24. - 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

25. The header is used in both signaling and data
packets.

27. • 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

29. • 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.

30. THANK YOU