Real Space Networking Real Space Networking Keisuke UEHARA, Ph. D - - PowerPoint PPT Presentation

2004/09/22

• 1

Real Space Networking Real Space Networking

Keisuke UEHARA, Ph. D kei@wide.ad.jp

Keio University/WIDE Project

2004/09/22

• 2
• “Real Space Networking” means

– System supporting Real Life using computer network (aka The Internet)

• Key Technologies

– Part1: Connect Everything – Part2: Interface with the real space – Part3: Support systems

• WIDE Project has several activities related to “Real Space Networking”.

– iCAR: Internet Connected Automobile Research – Spears: Realspace Networking – Auto-ID: Auto-ID – GLI: Geographical Location information – GNSS: Global Navigation Satellite System etc.

• Today’s contents

– Application examples – System overview – Future and Conclusion

Overview Overview

Digital world Real Space Input Output Processing

2004/09/22

• 3

Traffic Information and Rain condition made by “Probe Car System” Traffic Information and Rain condition made by “Probe Car System”

2004/09/22

• 4

Taxi control system using the Internet Taxi control system using the Internet

2002/01/28 Nagoya Press Conference

2004/09/22

• 5

Business Card less Service Business Card less Service

By touching visitor's own badge

• ver the RFID reader at a exhibitor

booth, visitor can provide contact information to the exhibitor

Companies attended this experiment:

• Cisco
• NEC
• NTT Communications
• Matsushita Electric works
• Hitachi
• IRI
• Panasonic Communications
• JPNIC

IPv6 business summit

2004/09/22

• 6

Real-time monitoring Service Real-time monitoring Service

Number of attendee of each seminar is counted real time manner at every entrance, then information is gathered to let participants know

• ccupancy.

IPv6 business summit

2004/09/22

• 7

Jabber conference : bof1-1 room invited user Jabber Bot Location based invitation system: Jabber Bot Location based invitation system: Jabber Bot

When you come into bof1-1 room, you would be invited “conversation room” automatically.

Come into bof1-1

2004/09/22

• 8

Connecting to the Internet Anywhere, Anytime, Anybody Connecting to the Internet Anywhere, Anytime, Anybody

2004/09/22

• 9

Connect Everything Connect Everything

• Connect to the Internet anytime, anywhere, anybody
• Mobile Internet technology

– Base technologies

• Mobile IP
• NEMO
• MANET

– Extended technologies

• Route optimization (Reducing the latency)
• Fast Handover (Reducing loss of packet)
• Security
• Robustness
• Flexibility

Thierry and Ryuji mentioned these research.

2004/09/22

• 10

Internet CAR’s Internet Connectivity model Internet CAR’s Internet Connectivity model

MR WiFi Cellular MR WiFi Cellular MR WiFi Cellular

Internet

• Connected via cellular phone using NEMO

MR WiFi Cellular

AP Car-A Car-B Car-C Car-D

• Connected via WiFi (direct) using NEMO
• Connected via WiFi (L2 MANET) using NEMO
• Can communicate with Car-D as a short cut path

(L3 MANET)

• Connected via cellular phone using NEMO
• Can communicate with Car-C as a short cut path

(L3 MANET)

2004/09/22

• 11

Internet

NEMO: Connect IVN to the Internet NEMO: Connect IVN to the Internet

Proposition: A vehicle uses any communication media seamlessly. Solution: iCAR introduces NEMO to connect IVN to the Internet.

• Movement: CoA, which vehicle want to use, is changed.
• When a vehicle moves, it report it to its HA.
• Packet will be delivered via a HA.

Internet

• Connected via cellular phone using NEMO

• Connected via WiFi (direct) using NEMO
• Connected via WiFi (L2 MANET) using NEMO
• Can communicate with Car-D as a short cut path

• Connected via cellular phone using NEMO
• Can communicate with Car-C as a short cut path

MR WiFi Cellular

CN HA

MR

AP CN assume that the vehicle is always located behind of HA.

MR WiFi Cellular

AP

2004/09/22

• 12

L2.5 MANET: Infrastructureless communication L2.5 MANET: Infrastructureless communication

Proposition: Vehicles prefer to connect via a wideband media. Solution: iCAR introduces L2.5 MANET to expand BB media coverage.

• Global MANET segment is constructed with AP as a center.
• Local MANET segment is constructed with a vehicle as a center.
• Local MANET segment is twice bigger than Global MANET segment to

follow general IPv6 manner.

• Reactive MANET algorithm can be applied to L2.5 MANET.
• MANET segment acts as “segment”.

Internet

• Connected via cellular phone using NEMO

• Connected via WiFi (direct) using NEMO
• Connected via WiFi (L2 MANET) using NEMO
• Can communicate with Car-D as a short cut path

• Connected via cellular phone using NEMO
• Can communicate with Car-C as a short cut path

AP

Internet

Expand

2004/09/22

• 13

L3 MANET: Expands coverage L3 MANET: Expands coverage

Proposition: Vehicles connect each other without any infrastructure. Solution: iCAR introduces L3 MANET to establish a shortcut routing path.

• By default, a vehicle supports NEMO.
• When two vehicles know routes which can reach each other, it can be “shortcut” paths.
• Any dynamic routing protocol can be use to make shortcuts. But MANET protocols work

well than others due to dynamicity.

• Proactive MANET algorithm can be applied.
• Bidirectional path is necessary.
• MANET have to have hop limitation. In addition, route information must not redistribute.

Internet

• Connected via cellular phone using NEMO

• Connected via WiFi (direct) using NEMO
• Connected via WiFi (L2 MANET) using NEMO
• Can communicate with Car-D as a short cut path

• Connected via cellular phone using NEMO
• Can communicate with Car-C as a short cut path

AP AP

Internet

CN Shortcut

2004/09/22

• 14

MANET Integration point

Conclusion: Multiplain routing table is necessary. Conclusion: Multiplain routing table is necessary.

Mobile Network Egress IF1 Virtual IF Pseudo IF Ingress IF Egress IF2 Physical IF1 Physical IF2 Physical IF4 Physical IF3 Egress IF

Mobile (HoA) Plain

• This plain maintains Home addresses and Mobile

Networks.

• If multiple Mobile Network here, we need to

introduce multiple routing table in this plain.

• Tunnel interface (Pseudo IF) can be introduced.
• Egress interface is used for shortcut routes. L3

MANET is supported on egress interfaces. Fixed (CoA) Plain

• This plain is the basic IP routing plain.
• Application which uses this plain cannot support

mobility. L2.5 Plain

• This plain is independent from IP layer.
• L2.5 MANET is supported in this plain.

2004/09/22

• 15

Interface with the real space Input to the virtual space from the real space Output to the real space from the virtual space Interface with the real space Input to the virtual space from the real space Output to the real space from the virtual space

2004/09/22

• 16

Overview of Interface with the real space Overview of Interface with the real space

• To realize “Real Space Networking”, real space information

have to be retrieved.

• We categorized real space information into following three

categories.

– Object Identification

• Object have to be identified by Identification number (including label).
• Indirect system:

Auto-ID system is using EPC (Electronic Product Code) as object ID.

• Direct system:

InternetCAR system is using IP address as object ID.

– Position and Time

• Position and Time (4th Dimensional information) is biggest difference

between real space and virtual space.

– The other data

• We need to investigate how we can output the data to the real
• space. But unfortunately we have very few activities about
• utput.

2004/09/22

• 17

EPC tag

Tag reader network Tag reader network

EPC tag EPC tag

• Event
• Set
• Polling

Read / Write

Tag reader system Information system based on EPC Application Application Application

Internet Intranet Internet Intranet

Name system (EPC-DS) EPC information service (EPC-IS)

Existing / Local System Application Interface

Data collection Filtering EPC-IS EPC-IS EPC-IS

Indirect system: Auto-ID system architecture Indirect system: Auto-ID system architecture

• EPC based system

– EPC=> ONS) => NAPTR

• NAPTR contains both of server address and services.
• Information system is not depend on Tag types
• Function of Tag reader system is read object ID form tag

Name system (ONS)

Resolver

Reader Reader Reader

Completely Separated

2004/09/22

• 18

Direct system: InternetCAR system architecture Direct system: InternetCAR system architecture

• Sensor ID = IPv6 Address
• DNS can be used to convert form NAME to ID.

– Object’s FQDN=>DNS) =>IP Address

• Step “ONS lookup” in Auto-ID system is omitted.

MR WiFi Cellular

Sensor Sensor Sensor

(1) Speed.Car.Jun.wide.ad.jp

DNS Application

(2) 2001::1 (3) snmpget 2001::1 oid (4) 60km/h

DB

(if necessary)

2004/09/22

• 19

Comparison Indirect system and Direct system Comparison Indirect system and Direct system

• Indirect system

– This have to be event driven system. – System and Object are not necessary to be same place.

• Direct system

– Both of event driven and server driven system can be achieved.

2004/09/22

• 20

Positioning Positioning

• Observation form outside

– Ex. Tag reader in the room – These systems need Real Space Network.

• Self observation

– Ex. GPS – Basically Real Space Network is not necessary. – But Real Space Network can assist the

• bservation.

2004/09/22

• 21

GNSS: Internet-Based Augmentation System GNSS: Internet-Based Augmentation System

• GNSS can get more accuracy, if there are

augmentation system.

• Augmentation system requirements:

– [Location awareness] Closer base station is useful. – [Delivery Delay] Not so time critical, but the information must be arrive to rover station less than

• 1 second (RTK mode)
• 30 seconds (Differential mode)

Base station Rover station

Correction information (RTCM Message)

2004/09/22

• 22

Getting other information Getting other information

• To get environmental information, Network

Management model is very useful.

– Data: MIB, XML Abstraction of Status of real space – Protocol: SNMP, SOAP Method to retrieve the status

• We made IPv6 Sensors as testbed.

Getting data using net-snmp Script started on Fri Sep 5 20:01:16 2003 kei@rokko-freebsd5:~[106]> snmpwalk -v 1 -c public udp6:2001:0:0:0:0:0:0:1 1.3.6.1.4.1.282.16.109.1.1.1.3.0 SNMPv2-SMI::enterprises.282.16.109.1.1.1.3.0 = INTEGER: 250 kei@rokko-freebsd5:~[107]> snmpwalk -v 1 -c public udp6:2001:0:0:0:0:0:0:1 1.3.6.1.4.1.282.16.109.1.1.1.4.0 SNMPv2-SMI::enterprises.282.16.109.1.1.1.4.0 = INTEGER: 392 kei@rokko-freebsd5:~[108]> exit

2004/09/22

• 23

Support systems to make applications Recognize and Polish the real space information Support systems to make applications Recognize and Polish the real space information

2004/09/22

• 24

Overview of Recognize and Process the real space information Overview of Recognize and Process the real space information

• We have two types of Location support

systems

– Area Daemon – GLI system

2004/09/22

• 25

user laptop PC RFID

Middleware part Physical sensor part Application part

Conference Room

location based services communication rendezvous user’s moving events

RF Reader

Observation form outside Observation form outside

2004/09/22

• 26

Implementation: Physical sensor part Implementation: Physical sensor part

Ethernet Antenna, RFID Reader (Spider Reader), Computer (Tini RS6) RS-232C User carrying this RFID Tag (Spider Tag version3)

2004/09/22

• 27

1 1 2 2 … … n-1 n-1 n n 2

Data Structure : Hash table for sessions / linked list for users structure mnode

2 2

structure unode structure mnode

User ID User ID 2 2

structure unode

Implementation: middleware part “AreaD” Implementation: middleware part “AreaD”

2004/09/22

• 28

meeting ID: AUTO-ID meeting ID: CII User IDs in CII User IDs in AUTO-ID Screen Shot: AreaD Screen Shot: AreaD

2004/09/22

• 29

Screen Shot: telnet to AreaD Screen Shot: telnet to AreaD

MGET UGET LGET

2004/09/22

• 30

Implementation: application, trial Implementation: application, trial

• 2 Sample Applications

– Jabber Bot provides

• Location based tentative Jabber conference
• Automatic Invitation for users related with the room

– WebDAV Proxy provides

• Location based tentative File Space (Web Folder)
• Automatic Redirection for the users
• Trial

– at WIDE Project Camp – about 300 monitor with note PC – prototype implementation

2004/09/22

• 31

Jabber conference : bof1-1 room invited user Jabber Bot Screen Shot: Jabber Bot Screen Shot: Jabber Bot

2004/09/22

• 32

Personal Server Personal Server AreaD AreaD Jabber Bot Jabber Bot Jabber Server Jabber Server Jabber Client Jabber Client

1) Jabber Bot requests User IDs to AreaD. 2) Jabber Bot requests a Jabber ID related the User ID to Personal Server. 3) Jabber Bot requests to create or update Jabber conference to Jabber Sever. 4) Jabber Server invites user’s Jabber client to the Jabber conference.

Detail: Jabber Bot Detail: Jabber Bot

Personal Server maintain each user’s Communication capability and its ID. The system is our former activity.

2004/09/22

• 33

GLI servers Internet

Threat: wiretapping Mobile node Look up client w/ confidential relation

Assumption: reliable

Look up client w/o confidential relation Look up client Look up client Threat: specifying and tracking an mobile nodes by the third person Threat: spoofing

Threat of GLI system Threat of GLI system

2004/09/22

• 34

Confidential relation Confidential relation

• Confidential relation in GLI system

– To share parameters to generate HID for registration

• Generate HID (Hashed ID)

– Using hash function – Parameters: real identifier, timestamp, interval, random values – Only look-up client in confidential relation can generate – As time value is included in parameters, HID changes with time, HID can prevent mobile nodes from being tracked.

2004/09/22

• 35

Future and Conclusion Future and Conclusion

2004/09/22

• 36

Future plan and Conclusion Future plan and Conclusion

• We have several testbed already.
• We need to discuss “Support systems” more.

– Infraless system – Data sharing and polishing system

• We want to make combined model and share

it in all applications.

2004/09/22

• 37