Overview of Researchat UNL-TDU

October 16, 2003Yoshito Tobe

Ubiquitous Networking LaboratoryTokyo Denki University

Goal

To establish the most suitable networking technology for ubiquitous computing

To establish a unified view and discipline of networking (particles, devices, people, society etc.)

Core: NETWORK-ING

History Apr. 1, 2002. Bootstrapping Dec. 2002 First students. Welcome! Dec. 20, 2003. First Event: Visiting SONY CSL Feb. 25, 2003. Visiting Todai-STONE Mar. 17, 2003. 　 Visiting Tokuda-lab Apr. 1, 2003. One-year anniversary Apr. 26, 2003. Sight-seeing with Al Krohn May 31, 2003. Joint workshop with Todai, Keio, UEC Aug. 4, 2003. Visiting Taki-lab, TDU Aug. 25- Sep. 5, 2003. ACM SIGCOMM etc. Sep. 26, 3003. Visiting TRL. IBM [Planned] Nov. 4-9 Los Angeles Tour

Members

Faculty members 　 ２ Bachelor's students 3 Joint Researchers 4 Total 5 (9 in a wider sense)

Faculty members

Yoshito Tobe (Sensor Maps)

Hiroki Saito (HTTP/TCP Analysis)

へ のへのもへ

Bachelor's Students

Kazunori Makimura (Net Mgt for Sensor Networks)

Ken'ichiro Kanehana (Computing Resource Mgt. considering Physical Env.)

Yasufumi Yamauchi (Service Cooperation Using Multi-hop Wireless Networks)

Joint Researchers (1)

Koichi Katayama (Sasaki Lab) Intrusion Detection

Niwat Thepvilojanapong (Univ. of Tokyo) Robust and Secure Multicast ?

Joint Researchers (2)

Hiroto (Keio Tokuda Lab.) Group Management of Wireless Nodes

Makoto Takizawa (Keio Tokuda Lab.)

Member of RT project

Research Topics

Network Management for Sensor Networks

Public-Private Association Human-Assisted Ad hoc

Networks

Network Management for Distributed Sensors

1

Problems on Sensor-Network Management

？？"Which sensor ?"

Sensors

Sensors

Sensors

1. Specifying nodes is difficult.

2. Performance such as delay is unpredictable because network is self-configured.

3. When failures occur, identification of the failed nodes is difficult.

4. Replacing batteries is required before they run out.

Why is conventional network management not sufficient ?

3

Simple Network Management Protocol (SNMP)

Manager

Agents

Sensor-specific failures arenot handled.Physical connections are notutilized.

SNAC Objectives Notification of Sensor-Specific Failures Utilization of Physical Views Identification of Constructed Topology Statistical Management

4

Early Notification

5

Noderemaining amount of

battery

Alive Node above threshold

Weakened Node below threshold

Depleted Node none

It is desirable to replace the battery of the sensor nodebefore it is depleted . Each node is equipped with battery, and NMN(Network-Management Node) is warned when the amount of the battery at a node falls below a certain threshold.

An event is transmitted to NMN to notify that a node becomesweakened. In some case, nodes surrounding a weakened nodesend events to NMN.

Geographical Management

6

(0, 0)

Area-cast : specified in some range in geographical area.

Y1

Alive Node

Weakened Node

Depleted Node

Healthiness of an area is obtained using area-cast.

Area-cast is independent of the underlyingrouting protocol. However, if the routing protocol supports geographical information, the area-cast utilizes the information.

1

0

10

(0, 1)

(1, 0)

(1, 1)

10

1

0

(1, 11)(1, 01)

(1, 00) (1, 10)

… (1, 11)

… (1, 111)

Location addr

Performance Management

7

Sensor network is self-configured. Therefore, a route that is undesirable in terms of delay could be created. To diagnosesuch performance, NMN can identify a route between nodes.NMN can indicate to reconfigure a routedepending on the reported performance.

A1

A2A3

A4

NMN

?

?×

×Route is recorded.

Visual Enhancement

8

Nodes can be equipped with indicators such as LEDs. Network management can be enhanced with the aid of suchindicators.Commands: show-route-to-node show-congested-nodes

Example: find weakened nodes

Weakened NodeThe route from NMNto a target node is indicatedwith LEDs.

Alive Node

<green>LEDs blinks.

<Red>LEDs blinks

SNAC Prototype20 MICA Motes

Implementation built on TinyOS

Commands: (1) Show-route-to-node

(2) Light-all-alive-nodes

Event Notification

weakened node

9

SAPEA: Secure Management of Public-Private-Device Association

Background Personal Computing Devices are

equipped with short-distance radio functionality. Short-distance radio technology

IrDA IEEE802.11 Bluetooth

The increase of Hot Spot that can use a public computer equipment is forecast.

Problem when public equipment is used

Secret information protect when equipment is used When communicating with the equipment is not

information stolen? Does the secret information remain in the use

equipment, and do not it leak? Is not information transmitted to the equipment not

intended when there are two or more equipment? Are not you peeped at from the outsider?

The access control using physical space information is done between a public equipment and personal device.

SAPEA: Secure Ad-hoc Personalization Alliance

SAPEA: Secure Ad-hoc Personalization Alliance

Want to use the equipment secure in not only on the network but also the real world. Neither information nor signs remain in the

equipment after used. Use limitation only within the district zone. The secret information protect from outsider

whom does not want to be known. Grouping

Approach Secure use of public equipment by limitatio

n of using authority by distance from equipment, and grouping. Distance judgment by radio devices such

as RFID and Bluetooth. Grouping and communication by Bluetooth. Authentication and encryption communication by

SSL. Level of Accessible Zone (AZ) is divide.

Related WorksThe Resurrecting Duckling [1]

Computer equipment

Association

Ad-hoc Filesystem [2]

Personal DevicePersonal Device

Personal Device

Trust for Ubiquitous, Transparent Collaboration [3]

Personal Device Personal Device Personal Device

Phone Number

Recommendation+

Phone Number

Recommendation’+

Personal Device

SAPEA: System Architecture

Personal DevicePersonal Device Access StationAccess Station

SSL

Wireless Device

AssociationManager

User Interface DeviceManager

AreaManager

AssociationManager

SSL

Wireless Device

LocationDetector

Device #1

Device #2

Device #3

AZ2 AZ1

Only the user Can be detected and inquired

Can be used

User and Associate Can be detected and inquired

Can be used

User, Associate and Outsider

Can be detected and inquired

Not can be used

AZ

Group

SAPEA ： Basic action

Distancejudgment

Cannot use

Demand

State inquiry

Outside of AZ Inside of AZ2

Inside of AZ1

Use state

Others are usingNo others

Notifies the user

Groupjudgment

Only the same group

Other groups are detected

Notifies all

Use or Stop

Can be used Stop

Do not useUseDistancejudgment

Distance judgment

AZ2: AS is detectable

AZ1: AScan be used

AccessStation

Accessible ZoneAccessible Zone

Grouping

A

A

A

AZ1

A

A

A

B

AccessStation

AccessStation

101 110001010

101

＋

－

！？

Z

A

Implementation Implement environment

Access Station IBM Think Pad X30

socket Bluetooth Connection Kit Red Hat Linux kernel-2.4.18

bluez-kernel-2.3 OpenSSL 0.97b

Personal Device SHARP Zaurus SL-C700

socket Bluetooth Connection Kit bluez-kernel-2.3

RFID Printer

Concluding Remarks:

Networking Technologies are evolving.