CIn Institucional Portugus

1
(No Transcript)
2
Context-Aware Middleware for Power Saving CAMPS
Plataformas de Distribuição CIn / UFPE 2008.1
Ana Paula Alves (apba_at_cin.ufpe.br) Gustavo
Carvalho (ghpc_at_cin.ufpe.br) May 20th 2008
3
Context-Awareness

• Context definition (Anind Dey)
• Most used
• Location (where)
• Identity (who)
• Time (when)
• Activity (what)

Context is any information that can be used to
characterize the situation of entities (person,
place, object) that are considered relevant to
the interaction between a user and an
application, including the user and the
application themselves.
3
4
Power Saving
can lead
CAMPS

allow
4
5
Agenda

• Objectives
• Requirements
• Architecture
• Scenarios
• Design
• Implementation
• Assessment
• Conclusion

5
6
Objectives

• CAMPS
• Context-aware
• Middleware
• Power
• Saving
• Services provided
• Context manager
• Event notifier
• Naming service
• Log service
• Monitor

Develop a context-aware middleware capable of
controlling electrical power spending in
environments
6
7
Agenda

• Objectives
• Requirements
• Architecture
• Scenarios
• Design
• Implementation
• Assessment
• Conclusion

7
8
Requirements

• 1. Communication type
• Asynchronous
• 2. Execution environment
• Desktop (PC)
• 3. Heterogeneity
• Operating system
• 4. Programming interface
• API
• 5. Network infrastructure
• Wired

8
9
Requirements

• 6. Inter-process communication
• Level of service guaranteed
• Publish/Subscribe operations
• Asynchronous, Sync with server, Timeout
• Topics (e.g. one for each laboratory)
• Dynamic publish/subscribe
• Message 1N
• 7. JMS-based (Message Oriented Middleware)
• 8. Marshalling
• Variable message size
• 9. Operation and Management
• Message monitor
• Power monitor

9
10
Requirements

• 10. Transaction services
• Not supported
• 11. Events service
• 12. Naming service for topics
• 13. Performance requirements
• Not supported
• 14. Language support
• Java
• 15. Scalability
• Not supported
• But expansibility is supported

10
11
Requirements

• 16. Reliability
• Not supported
• 17. Security
• 18. Invocation policy
• One thread per client
• 19. Dispatching
• Not applicable
• 20. Transport layer
• TCP, SMTP, HTTP
• 21. Interoperability protocol
• Not applicable
• 22. Logger

11
12
Agenda

• Objectives
• Requirements
• Architecture
• Scenarios
• Design
• Implementation
• Assessment
• Conclusion

12
13
Architecture
GeoVision
Agenda
Door Controller
Light Controller
Computer Controller
Display
Agenda Controller
GeoVision Controller
MIDDLEWARE
MIDDLEWARE
ContextManager
PowerManager
NamingService
Power Configurator
Power Monitor
Queue Manager
Logger
Transport Layer TCP
JAVA VIRTUAL MACHINE
OPERATIONAL SYSTEM
13
14
Components - Apps

• GeoVision
• Captures approximately how many people there are
  in an environment
• Sends an email to a previously specified account
• GeoVision Controller
• Communicates with GeoVision
• Sends messages to middleware with environments
  usage information
• Agenda
• Keeps control of environments usage
• Agenda Controller
• Communicates with a specific agenda
• Sends messages to middleware with environments
  usage information
• Door/Light/Computer/Air Conditioner Controller
• Subscribes in middleware to receive messages
  about energy power reduction
• Display

14
15
Components - Midd

• Power Manager
• Analysis the current environment contexts
• Identifies opportunities of power energy saving
• Context Manager
• Builds a context with the environment usage and
  agenda data
• Power Configurator
• It is used to configure middleware properties
• Amount of monitored environments
• Power energy consumption goal
• Naming Service
• Keeps a mapping between topic names and its
  references

15
16
Components - Midd

• Queue Manager
• Manages the middleware topics
• Topics
• Stores messages with related contents
• Topics categories
• Environment ones
• Middleware ones
• Transport Layer
• Responsible for accessing SO communication API
• Sends and receives data through the network
• Power Monitor
• Monitors the recent power consumption regarding
  the environments
• Logger
• Persists power consumption data in a local data
  base

16
17
Agenda

• Objectives
• Requirements
• Architecture
• Scenarios
• Design
• Implementation
• Assessment
• Conclusion

17
18
Scenarios
GeoVision
Agenda
Accesses the Agenda periodically
1
Agenda Controller
1
Sends an email
2
Sends a message to Agenda topic
MIDDLEWARE
New email? Sends a message to GeoVision topic
Queue Manager
Reads the email periodically
2
GeoVision Controller
3
18
19
Scenarios
MIDDLEWARE
Notifies Context Manager
ContextManager
1
Reads messages from GeoVision and Agenda topics
New message in GeoVision or Agenda topics
Send a new context to Environment N topic
2
3
Queue Manager
Environment N
19
20
Scenarios
MIDDLEWARE
Notifies Power Manager
Gets power consumption goal
PowerManager
1
PowerConfigurator
0
4
New context in Environment N topic
Reads contexts
2
3
Analyses contexts
Sends a message about power saving possibility
Queue Manager
Environment N
20
21
Scenarios
Computer Controller (or any other power saving
application controller, e.g. Light Controller,
Printer Controller, etc.)
Subscribes in Environment I, K and N topics
Informs entering on power saving mode
Reads message
1
3
4
5
6
Analyses context
Enters on power saving mode
MIDDLEWARE
Notifies Application(s)
New power saving possibility
2
Queue Manager
Environment N
21
22
Scenarios
Display
Subscribes in Environment I, K and N topics
Reads message
1
3
4
Displays information
MIDDLEWARE
Notifies Display
Some application has entered on power saving mode
2
Queue Manager
Environment N
22
23
Scenarios
DB
Power Consumption Monitors (display graphics,
reports, etc.)
Reads message
Accesses logger data
Subscribes in Power Monitor topic
1
2
2
3
Displays information
MIDDLEWARE
z
Sends data do DB
Power Monitor
Logger
Sends metrics to Power Monitor topic
Reads environments power consumption
Reads metrics from Power Manager topic
a
b
c
d
Generates power consumption metrics
Queue Manager
Power Monitor
Environment N
23
24
Agenda

• Objectives
• Requirements
• Architecture
• Scenarios
• Design
• Implementation
• Assessment
• Conclusion

24
25
Design
To be defined
25
26
Context-Aware Middleware for Power Saving CAMPS
Plataformas de Distribuição CIn / UFPE 2008.1
Ana Paula Alves (apba_at_cin.ufpe.br) Gustavo
Carvalho (ghpc_at_cin.ufpe.br) May 20th 2008
27
(No Transcript)