Download Some Activities in Crisis Management The RUNES and U

Some Activities in Crisis
Management
The RUNES and U-2010 Projects
Peter T. Kirstein, UCL
RUNES 2006 and U-2010
• The EC IST Framework Programme (FP) has
many themes. Three are:
– Research Infrastructure
– Embedded Sensors
– Crisis Management
• 6NET and other talks in this session from
research infrastructures
– FP5 and FP6 had strong IPv6 track
– 6NET FP5 2002 - 2005
• RUNES is in embedded sensors track
– RUNES FP6 2004 - 2007
• U-2010 is in Crisis management track
– U-2010 FP6 2006 - 2009
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
2
The RUNES Project
• The project aims and objectives
– Technology development for embedded networked
Sensors
• The work-packages
– Architecture, sensors, networks, control, middleware,
sensor networks, demonstrations
• Could have chosen many targets for project, but
chose one on “fire in a tunnel”
• Mainly IPv4, though some IPv6 near the end
• Is same as one of the targets in U-2010
– Partners are different, but allows technology of
RUNES to be exploited in U-2010
– Allows much more extensive components to be
introduced into U-2010
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
3
The U-2010 Project
• The project aims and objectives
– Crisis management in different in different scenarios
– Scenarios mountain rescue, bird flu, “fire in a tunnel”,
nuclear emergency
• Will concentrate on IPv6, though some
interworking with legacy IPv4 services
• One application same as RUNES
– Partners are different, will use some RUNES
technology, but additional gateways
– Much more emphasis on variety of networks
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
4
Emergency in a road tunnel
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
5
Reconfigurable Ubiquitous
Networked Embedded Systems
RUNES
To provide a standardised architecture that
enables the creation of large-scale, widelydistributed, heterogeneous networked
embedded systems that inter-operate and
adapt to their environments
RUNES Partners
Industrial
Academic
Non-profit research
institutes
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
7
RUNES
• Reconfigurable Ubiquitous Networked
Embedded Systems
• To provide a standardised architecture enabling
the creation of large-scale, widely-distributed,
heterogeneous networked embedded systems
that inter-operate and adapt to their environment
• Mainly IPv4 based through 2005/2006
– IPv6 capability added in 2007 to some
– Although only some demonstrated, almost all will
move over simply to IPv6
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
8
A network of embedded devices
• Tunnel wall
– Sensor devices
– Multi-radio routing
devices
• Tunnel opening
– Multi-radio routing
gateways
• Vehicles
– devices
– Sensor devices
– Multi-radio routing
devices
• Emergency Services
– Sensor devices
– PDAs
– Multi-radio routing
28 August, 2007
Tmote Sky
Sensor
Device
connectBlue
multi-radio
gateway
RUNES and U-2010, APAN-24, Xian, China
Lippert
multi-radio
gateway
9
A lightweight solution
• Platforms
– Contiki Operating System - using lightweight
stackless threads
– FreeRTOS - open source, mini Real Time Kernel
– DENX Embedded Linux Development Kit (ELDK)
– Communication protocol stack
– µIP, µAODV
– Compatible with existing protocol stacks
• Middleware kernel
– Component model and associated API
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
10
Middleware architecture
Environment
Application/Middleware Components
Component-based
Middleware
Middleware Kernel API
Platform-specific
Kernel Implem.
Platform-specific
Kernel Impl.
Platform-specific
Kernel Implem.
Contiki
FreeRTOS
Linux
Sensor device Gateway deviceGateway device
Hardware and RF
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
11
The RUNES middleware
• Component Model Design
– Defines components as basic run-time units
– Enables components to be instantiated at run-time
– Functionality provided by components through
interfaces
– Dependancies expressed through receptacles
– Receptacle/Interface binding made with connector
components
• Component Run-time Kernel Implementations
– Java, C/Unix, C/Contiki
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
12
Middleware components
• Data acquisition
– Measurement component
• Obtain environmental readings on sensor
devices
– Data dissemination
– Notification component
• Disseminate sensor readings to control centre
– Publish-Subscribe infrastructure
• Component to disseminate sensor readings
through broadcast
• Mechanism to enable broadcast sensor
readings to be shared
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
13
Application of the middleware
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
14
Network-Level Reconfiguration
• µIP and µAODV for ad
hoc networks
• Overcome transience,
damage and loss
– Must auto-configure
• Routing
reconfiguration
– Re-route data around
broken sensor devices
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
15
Extracting information
• Environmental
conditions
– Temperature
– Humidity
– Visibility
• Data dissemination
• Reporting
conditions to
control centre
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
16
Communicating to co-ordinate
rescue efforts
• Publish relevant
data to emergency
services
• Share and
propagate data
among firefighters
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
17
IST 2006
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
18
IPv6
• 6LoWPAN
– IPv6 over Low-powered Wireless Personal Area
Networks
• Network protocol stack-level implementation
• Middleware is agnostic
– Pass data down to Operating System for transmission
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
19
Summary
• A component-based middleware architecture
• Addresses fundamental challenges through
– Lightweight platform and protocol implementations
– Dynamically reconfigurable middleware architecture
• Incorporates capabilities to
– Cope with the failure of devices and communication
links
– Reconfigure automatically to deal with a changing
environment
– Discover available resources and communication
paths
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
20
Tunnel infrastructure – Reqs.
•
•
•
•
Tunnel Local Control Room
Remote “Control Rooms”
Firemen Control Centre
Static wireless sensor network
– Sensors part of the tunnel fixed infrastructure
– Collect humidity, light, temperature readings and
send back to Tunnel Control Room
– Via fixed 802.15.4 gateway in tunnel
• Dynamic wireless sensors network
– Fire fighters have motes attached to uniform
– Fire fighters deploy more motes upon arrival
– Via 802.15.4 gateway on a mobile van
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
21
IPv6 in the RUNES Final Demo
• 6LoWPAN
– 802.15.4 MTU=125 bytes, IPv6 min MTU=1280 bytes
=> Fragment & Reassemble, Compress Headers
• NEMO
– WSN attached to firemen moves with them in tunnel,
van equipped with 802.15.4 g/w => need to change
point of network attachment => sensor network is
now mobile
• Auto-configuration
– New motes fired up => need IPv6 addresses
– Many WSN in tunnel => which PAN coordinator?
– Some motes may fail => re-route
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
22
RUNES IPv6 Final Demo
Control Station
Wireless Sensor
Network 2
172.16.0.2
Remote Cont Room
wpan0
Internet
eth2
lowpan2 wpan wpan1
2001:630:13:1
RUNES LocaL 2
06::1
Control Room
lowpan1
Control Station
runeslocal.net
eth0
28 August, 2007
eth0
Tunnel
Gateway
RUNES and U-2010, APAN-24, Xian, China
2001:630:13:1
06::10
wpan
0
(Mobile) Wireless
Sensor Network 1
23
Network-Level Reconfiguration
• µIP and µAODV
• Overcome transience,
damage and loss
• Routing reconfiguration
– Re-route data around
broken sensor devices
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
24
Current Status
• RUNES Completed and Demonstrated
– Full IPv4 Testbed with tunnel and many sensors
– Important IPv6-sensitive components shown
• IPv6 Components demonstrated
– Cross-development environment set-up
– WPAN driver IPv6 enabled
– NEMO “ported” to gateway
• Some further work to be done
– Auto-configuration: stateless, dynamic
– “6-to-4 adaptation” layer or tunnelling over v4 for
failure scenario?
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
25
The U-2010 Project
•
•
•
•
•
Integrated EC-project
3 years duration
€6.5 Mio Budget - €4M EC Contribution
Start May 2006
16 Partners
– including major players in the IP business
– The governments of Luxembourg and Slovenia
participate to support the emergency service
trials
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
26
u-2010 - Key Data
Industry
Players
Government
Best-in Class
Research
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
27
U-2010 Motivation – A Study
• Current comms equipment of security and rescue
services does not match up to the requirements
• Absence of protected and confidential comms
does not allow for a silent mobilisation
– use of public GSM phones provides the only
possibility of a minimum of confidentiality
• Public communications are the only alternative
– To reach the complete government structure
– To connect to subscribers of public networks
– BUT: Lack of government owned capacity
• The crisis scenarios required confidential and
redundant communication services
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
28
Project Vision
• To provide the most capable communication tools
• To provide the most effective access to
information…
• …to all required to swiftly act in case of accident,
incident, catastrophe or crisis
• …whilst using existing and/or future (tele)
communication infrastructures
• Trial and validation activities will show the
application of the results in real life crisis scenarios
• Results of u-2010 as showcase for other Countries
• Base all on IPv6 – with IPv4 only for interworking
with legacy systems
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
29
Goals of the Project u-2010
• Enhance the availability of the collection of
services by use of all existing networks
• Leverage redundant communication channels
• Use of automatic redirection and/or transformation
of communications in case of network failures
• Use of new research results in the area of wireless
ad hoc networks and IPv6.
• Use of existing technology and networks
• Create solutions that are as universal as possible
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
30
Tunnel Fire Scenario
SES
Inclined
Video Stream Orbit
Satellite
Satellite dish
Video Stream
Internet
GSM/G
PRS
IP/CITA GW
CITA
Network
UMTS
WiMax
Video Stream
WiFi
mobile router
Tunnel Fire Vehicle
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
31
Mountain Rescue Scenario
Satellite
Wireless
terrestrial
Wireless
terrestrial
Internet
WLAN
Headquarters
mobile router
Search Teams
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
Rescue Vehicle
32
Principal U-2010 Components
• Are configuring many available components
–
–
–
–
–
–
Cisco MARS G/w
ASTRA2Connect Mobile Satellite Earth Station
Most RUNES Components
Video system in real tunnel
Video cameras
Emergency Personal Vests
• Are interfacing parts to interwork
– Often need extra programmable components to run
adaptation middleware
• Are ensuring most can be IPv6-enabled
– Or can work via IPv4 G/w
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
33
Cisco Mobile Access Router
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
34
Examples of MARS Uses
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
35
Astra Emergency Terminal
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
36
RUNES Components + Additions
• In U-2010 will connect Lippert G/w to
CISCO mobile access router (MARS)
– MARS will connect to other WAN devices
• Will add audio and video sub-systems VIC,
RAT
– Can operate over IPv6 with and without multicast
– Can be modified to operate without a GUI into same
environment in embedded form
– May be added to either G/w for camera over U2010, or
low frame rate over sensor network
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
37
Nokia-Siemens Study of IMS
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
38
Interconnections Achieved
• ASTRA terminal intended to interface to PC
– Has been interfaced to Cisco MARS
• LIPPERT RUNES G/w was controlled by PC
– Now being interfaced to Cisco MARS
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
39
Conclusions
• RUNES project showed how complex IPv4
applications can be put together for the
emergency environment
– That real advantages accrue from IPv6 in mobility,
reconfiguration and security
– Move to IPv6 fairly straightforward
• U-2010 is tackling a much more complex situation
– Is starting by ensuring most components can be IPv6enabled or can interwork with legacy systems
• Involves real customers in several governments
• Should point the way to important deployments
28 August, 2007
RUNES and U-2010, APAN-24, Xian, China
40