Robocop

1
Robocop Space4U
2
Outline

• Consortium
• Problem domain
• Scope
• Highlights of Robocop
• Research topics in Space4U

3
Consortium

• Space4u
• CSEM
• FAGOR ELECTRODOMESTICOS
• IKERLAN
• Nokia
• Philips Electronics Nederland B.V.,
• Technical University Eindhoven
• Technical University of Madrid
• Visual Tools

• Robocop
• CSEM
• ESI
• FAGOR ELECTRODOMESTICOS
• IKERLAN
• Nokia
• Philips Electronics Nederland B.V.,
• SAIA Burgess Electronics
• Technical University Eindhoven
• Technical University of Madrid
• Visual Tools

4
Problem domain

• High Volume Consumer Electronics

5
(No Transcript)
6
Highlights of Robocop

• Aim
• Component Model
• Executable Model
• Resource Model
• Component Life Cycle
• Download Framework
• QoS Framework

7
Robocop aim

• Aim
• Define an open, component-based framework for
  the middle-ware layer in high-volume consumer
  devices
• that enables
• robust and reliable operation
• upgrading and extension
• component trading

8
(No Transcript)
9
(No Transcript)
10
Resource Model
Resource estimation based on annotated MSC's
11
Component Life-cycle
12
Download Framework

• Within Robocop a download framework was developed
  responsible for
• Locating components
• Deciding whether component is suitable for a
  device,
• Downloading to the device

13
QoS Framework

• Services can run on different quality levels.
  Each quality level has its own resource profile.
  The QoS Framework is responsible for
• Negotiation of quality levels
• Setting resource budgets
• Monitoring resource usage
• When necessary negotiation of quality levels

14
(No Transcript)
15
Space4u

• Research Topics
• Power Management
• Fault Management
• Terminal management
• Integration with current framework
• Scenarios
• Some Initial Ideas

16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
Fault Management Scenario
We consider a dvd-player. One of the service
instances of the dvd-player has crashed (crash
failure). The terminal manager notices the
hearth beat of the specific service has stopped.
The terminal manager will create a new instance
and will take care of the binding with the other
service instances.
20
Fault Management Scenario
We consider a mobile telephone. Recently the
telephone isn't working properly. Therefore the
user presses the maintenance button. The
terminal contacts the supplier, who will examin
the terminal, make a diagnosis and execute a
repair plan.
21
(No Transcript)
22
Prevention

• Maintain a healthy configuration of services
• Keep configuration compliant with a self model
• Only use certified services in your system
• Protect services from bad input

23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
Follow the progress

• http//www.win.tue.nl/space4u