310 likes | 422 Views
Overview of Research at UNL-TDU. October 16, 2003 Yoshito Tobe Ubiquitous Networking Laboratory Tokyo Denki University. Goal. To establish the most suitable networking technology for ubiquitous computing
E N D
Overview of Researchat UNL-TDU October 16, 2003 Yoshito Tobe Ubiquitous Networking Laboratory Tokyo 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 2 • 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
Problems on Sensor-Network Management Sensors 1. Specifying nodes is difficult. 2. Performance such as delay is unpredictable because network is self-configured. Sensors Sensors 3. When failures occur, identification of the failed nodes is difficult. 4. Replacing batteries is required before they run out. ? "Which sensor ?" ?
Why is conventional network management not sufficient ? Simple Network Management Protocol (SNMP) Manager Agents Sensor-specific failures are not handled. Physical connections are not utilized. 3
SNAC Objectives • Notification of Sensor-Specific Failures • Utilization of Physical Views • Identification of Constructed Topology • Statistical Management 4
Early Notification It is desirable to replace the battery of the sensor node before 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 becomes weakened. In some case, nodes surrounding a weakened node send events to NMN. 5
Geographical Management Area-cast : specified in some range in geographical area. Healthiness of an area is obtained using area-cast. 0 1 0 1 Location addr … (1, 11) 1 … (1, 111) (1, 11) (1, 01) (1, 00) (1, 10) Y1 0 1 (0, 1) (1, 1) (0, 0) (1, 0) 0 Area-cast is independent of the underlying routing protocol. However, if the routing protocol supports geographical information, the area-cast utilizes the information. Alive Node Weakened Node Depleted Node 6
Performance Management Sensor network is self-configured. Therefore, a route that is undesirable in terms of delay could be created. To diagnose such performance, NMN can identify a route between nodes. NMN can indicate to reconfigure a route depending on the reported performance. × ? A4 A2 A3 A1 ? × Route is recorded. NMN 7
Visual Enhancement Nodes can be equipped with indicators such as LEDs. Network management can be enhanced with the aid of such indicators. Commands: show-route-to-node show-congested-nodes <green>LEDs blinks. The route from NMN to a target node is indicated with LEDs. Weakened Node <Red>LEDs blinks Alive Node Example: find weakened nodes 8
SNAC Prototype 20 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? SAPEA: Secure Ad-hoc Personalization Alliance The access control using physical space information is done between a public equipment and personal device.
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 limitation 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.
Phone Number Phone Number Personal Device + + Personal Device Personal Device Personal Device Recommendation Recommendation’ Personal Device Personal Device Personal Device Related Works The Resurrecting Duckling [1] Ad-hoc Filesystem [2] Association Computer equipment Trust for Ubiquitous, Transparent Collaboration [3]
Location Detector Association Manager Device #1 Device #2 Device #3 SSL SSL SAPEA: System Architecture Personal Device Access Station User Interface Device Manager Association Manager Area Manager Wireless Device Wireless Device
AZ Group
SAPEA:Basic action Distance judgment Group judgment Outside of AZ Inside of AZ2 Other groups are detected Cannot use State inquiry Only the same group Notifies all Use state Others are using Use or Stop No others Notifies the user Distance judgment Do not use Use Can be used Stop Inside of AZ1 Demand
Distance judgment Accessible Zone AZ2: AS is detectable AZ1: AS can be used Access Station
A A !? A A A 101 110 101 010 001 Access Station Access Station A A + - Z B Grouping AZ1
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.