アドホックネットワーク超入門

(1)

1

Protocol design for All-IP Computer Framework

ICOIN 2008 23 - 25, Jan, 08

Kouji Okada, Keisuke Muda, Yoshifuji, Nishida Hideaki Yoshifuji, Ryuji Wakikawa, Jun Murai

Keio University

(2)

2

Research Objectives



Human Centric Computer Network



Unbundle users from the restriction of “terminals”



The existing computers are bounded by their physical box es



Independent of both of the “location” and the “terminals”, u sers continue to use same application environments



Users don’t have to construct several computer environme nt in their home and office.



According to users’ application usage scenarios, computer systems are re-configured dynamically



In the office



Display + Mouse + Keyboard



At home, watching movies



Display + Remote control device + S

peaker

(3)

3

All-IP Computer Architecture

 Replace the peripheral buses with IP networks



computer devices directly connected to the IP network s

 virtual computers consisting of IP networked co mputer devices

 Flexible computer environment utilizes computin

g resources on the global IP network

(4)

4

IP Network s

CPU Memory

Display Keyboard Mouse

Input/Output devices

Host OS

HDD

Home Network

Visited Network

Computing Resource Network

Overview of

All-IP Computer Architecture

Home Rendezvous

Manager (Home RM)

Local Rendezvous

Manager (Local RM)

User Tag

User Data

(5)

Scope of this paper

 An All-IP Computer consists of



I/O devices located around user’s current location



Storage devices in the user’s home



Computational resources allocated somewhere in the n etwork



Operating Systems running on the host computers

 The main focus of this paper



As the first step, the method to realize dynamic I/O

device allocation and the performance evaluation of

IP networking I/O devices

(6)

6

Rendezvous Manager (RM)



The device management server for each local networks



Functionalities



Device list management



Resource allocation



User authentication



Types of RMs



Local RM



The RM located on the user’s current network



Responsible for All-IP computers construction



I/O devices, host computer



Home RM



The RM located on the user’s home



HDD



Remote RM



The RM located on the user’s previous network (migration)

(7)

7

Host OS

Device

Device Driver

IP Networ ks

Operating System

(OS)

Device

Device Driver

Computer device analysis

Host Computer

Device Control OS Existing Computer Architecture All-IP Computer Architecture

Device dependent

data/control messages

over IP networks

(8)

8

Existing Approaches



iSCSI (Internet Small Computer System Interface)



The protocols to handle SCSI command set on the TCP/IP protocol stack



RFC 3720, RFC 3783



USB/IP



Deliver the USB data encapsulated as TCP segments on I P networks



draft-muda-iusb-ps-00



For additional history on network-attached peripherals



Van Meter, Operating Systems Review (OSR), Jan. 1996

“A Brief Survey of Current Network Attached Peripherals”

(9)

9

All-IP Computer Initialization

IP Network s

Input/Output devices

Host Computer

HDD

Home Network

Visited Network

Home Rendezvous

Manager (Home RM)

Local Rendezvous

Manager (Local RM)

User Tag

1) A user tag search for the

local RM by RM request messages which contains the authentication

information RM Discovery

/Resource Request

2) The local RM

authenticate the user

(10)

10

IP Network s

Input/Output devices

Host Computer

Home Network

Visited Network

Local Rendezvous

Manager (Local RM)

User Tag

3) The local RM intermediates the user authentication to

the home RM Authentication information/

Device Request

4) The local RM

send a device request for the devices specified in the resource request

HDD

Home Rendezvous

Manager (Home RM)

(11)

11

IP Network s

Input/Output devices

Host Computer

HDD

Home Network

Visited Network

Home Rendezvous

Manager (Home RM)

Local Rendezvous

Manager (Local RM)

User Tag

5) The local RM

Allocates I/O devices

and host computer

to the user

(12)

12

IP Network s

Input/Output devices

Host Computer

HDD

Home Network

Visited Network

Home Rendezvous

Manager (Home RM)

Local Rendezvous

Manager (Local RM)

User Tag 6) The local RM

triggers the host computer to connect devices

by the device notification message

Device Notification

(13)

13

IP Network s

Input/Output devices

Host Computer

HDD

Home Network

Visited Network

Home Rendezvous

Manager (Home RM)

Local Rendezvous

Manager (Local RM)

User Tag 7) The local RM

send to the user a resource reply

message which indicates the physical location

of the I/O devices

Resource Reply

(14)

14

Evaluation



Objectives



To understand allowable network delay for IP networked comput er devices



Evaluation Environment



3 nodes on the testbed network



USB/IP server, USB/IP client, Dummynet bridge



Evaluation overview



We Evaluated the time gaps between “pressed” and “released” k eyboards events on the USB/IP client PC



Dummynet bridge used to vary network latency in 10msec in crements

USB/IP server (Device) USB/IP client

(Host Computer)

Dummynet Bridge

(15)

15

Evaluation results

0 100 200 300 400 500 600 700

0 50 100 150 200 250 300

Dummynet delay (msec) RTT (msec)

USB-IP ICMP

The gaps were increased according to the network delay

→ The network delay is beyond the USB’s assumed latency

The Keyboard events began to be lost

Dummynet Delay (msec)

R T T ( m se c)

(16)

16

Conclusion

 All-IP based computer architecture design



We defined a new computer architecture called “All-IP computer architecture”



Protocol design for dynamic All-IP computer configura tion

 Evaluation of devices interconnection protocols



We have obtained an allowable network delay

(17)

17

Future Plans

 Latency management



Network storage/file systems



The protocol for the OS migration

(18)

18

Acknowledgement

 Keio University

 Dr. Rodney Doyle Van Meter III

 Tokyo University

 Dr. Kei Hiraki

 Dr. Mari Inaba

(19)

19

Thank You