Outline
End-to-End Mobility Architecture
for Ubiquitous Computing

Background Related works of mobile Internet protocols
 Objective
 End-to-End Association-Based Architecture Experimental results
 Conclusions


Hiroyuki Koga
koga@is.naist.jp
May 27, 2004

1

Background (1)Background (2)Future ubiquitous networks

Future ubiquitous serviceMany wireless devicesMany services in ubiquitous networks

Cellular phone, PDA, sophisticated watch, etc.

Web browsing, Radio, TV
Medical information including the pulse Location information of children and agedpeopleMany kind of wireless access providers



Their coverage area will overlap with eachother.
 Their networks have quite different features.
Many scenes that services will be useful

Cellular service, Wireless LAN serviceTraveling, Commuting

2

3

Background (3)Related work

Requirements

mobile Internet protocols (1)Mobility management with multi-homing
functions becomes a key technology.

Mobile IPv4 and Mobile IPv6


QoS (Quality of Service) control
 Security
 Lightweight Easy deployment

Mobility extension of IP
Provide the transparency and backward
compatibility to the transport layer
There is a difficulty about multi-homing support.
This difficulty comes from layer 3 nature of Mobile IP.
L.4
L.3
L.2

4

Transport
Mobile IP
Data link
51

Related work

Objective

mobile Internet protocols (2)Mobile SCTP (Stream Control TransmissionProtocol)Novel transport protocol
Natively supports multi-homing function

To provide suitable mobility architecture
and protocols with multi-homing function
QoS control
Security
 Lightweight Easy deployment

It is difficult to provide QoS control.
Transport layer has many functions, so mobility
function should be separated.
L.4
L.3
L.2

Mobile SCTP
NetworkData link
6

Proposed Architecture (EABA)
7

Association layer

End-to-End Association-Based Architecture
EABA hostAssociation protocol

Manages the association between each end hostconnection identifier

EABA hostIP address at connection establishment
Transport

L. 4

Association layer
association
a set of routes constructed by multiple
network interfaces of each end hostnetwork
interface

L. 3.5 Association
Network

L. 3translate
host identifier
IP address list
selectnormal IP manner

Source and destination IP
addresses actually used
non-EABA host8Association protocolEvaluation of Prototype implementation

Exchanges IP address list currently used witheach other.
 The control information is embedded between L.3
and L.4 header as L.3.5 header.
IPheader

Associationheader

TCPheader9

Prototype

Association layer and protocol
Linux-2.4 (IPv4)

Experimental evaluation
Effectiveness of our architecture in multihoming environment Availability of existing applications

data

source host identifier
destination host identifier
IP address [0]Priority: address [0] > [n]IP address [n]10112Experimental results (1)Experimental environment

effectiveness of EABA
4e+06

RTT (Round Trip Time) : 40 ms
Linuxwith EABAa

10Mb/sb192.168.1.1/24

PC router

192.168.2.1/24

sequence number

192.168.0.1/24

Linuxwith EABA

10Mb/sInterface aInterface b

3.5e+06

192.168.3.1/24

3e+06
2.5e+06
2e+06
1.5e+06
1e+06

Each network is separate segment LAN.
 Link a and b are disconnected andconnected at the interval of 1 second.

500000



03

4

5

678

910time[s]Each host continues communication by using theconnected link effectively even if links are
disconnected and connected frequently.

12

Experimental results (2)availability of existing applications
Application

AvailabilityHTTP○POP3○

NFS○ssh○telnet○FTP

×13Problem on FTP

FTP uses 2 connections.

The direction of each flow is important.

control flow
PC routerLinuxwith EABA

AB

Linuxwith EABA

data flow

control connection, data connection

Most main applications except FTP can be used.
14

Plan to solve this problem
manage all connections between same hosts by oneassociation

15Conclusions
End-to-End Association-Based Architecture(EABA) for ubiquitous computingThis architecture is effective in the multihoming environment

Future work

improve this architecture
perform evaluation in many cases

163