An Integrated Resource Management Architecture for Wireless Smart Environments
Paolo Bellavista, Antonio Corradi, Silvia Vecchi {pbellavista, acorradi, svecchi}@deis.unibo.it Dept. of Electronics, Computer Science and Systems University of Bologna - Italy
Outline Smart Environment Scenario and Management Requirements Enabling technologies: JMX and Mobile Agents Resource Management Architecture: - System Architecture - Implementation Guidelines Conclusion and Future Work 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
2
Smart Environment Scenario
Room A
Room B
FTP server #1 Lab 1
Room E
Room F
FTP server #3 Lab 3
Assistance of software download in a wireless environment 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
3
Management Requirements First goal: goal to overcome heterogeneity in
• resources at different layers of the system • sensing mechanisms • monitoring data representation formats
The Java Management eXtensions (JMX)
and granularity Second goal: goal to provide
• aggregated rough data translating it to an application-understandable format
• knowledge when and where needed by applications 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
The Mobile Agent Technology 4
Enabling Technologies: Management Solutions Dominant management technologies • Telecommunication area: Common Management Information Protocol (CMIP)
Telecommunication Management Network (TMN)
• Device and Network area: Simple Network Management Protocol (SNMP) • Enterprise Computing Environments area: Web-Based Enterprise Management (WBEM) • Application area: ??? application running on only one platform -> vendor preferences application running on different platforms -> need of interoperability JMX to fulfill the manageability requirements of Java-based applications 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
Enabling Technologies: JMX Components JMX Manageable Resource: MBeans represent • management interface of managed resources • management services MBean Server: MBean registry provides services • to access MBean info • to manipulate the MBeans Protocol Adaptors and Connectors: MBeans can represent of a JMX resource in another protocol (HTTP, SNMP) an other protocol resource in JMX manageable resource JMX Agent: one MBean Server + several MBeans + at least one adaptor/connector “required services”: monitoring, timer, relation, Mlet 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
7
Enabling Technologies: Mobile Agents Mobile Agents to exploit: Mobility • to provide knowledge to interested applications when and where needed • to operate locally without need of centralized interactions Autonomy to operate even in case of network partitioning Location-awareness and personalization to adapt services to access locality and user characteristics Dynamicity to modify environment behavior at provisioning time SOMA mobile agent platform 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
The Resource Description Level MBeans representing resources at different level of abstraction: • •
network/system hardware devices (hosts, printers, WiFi and Bluetooth SAPs) service software components (HTTP and FTP servers)
Remote wrapping mechanism JVM JMX Application
Remote Non Java SNMP compliant
SNMP SNMP Peer Manager
device
integration in the management architecture of devices with very limited computing capabilities 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
SNMP Agent
10
The Resource Management Level Resource Manager Agent (RMA) JMX Agent composed of • one MBean Server • one HTTP Adapter Basic Management Services: Network Service => Network MBean service MBean collecting information about the network bandwidth from MBeans representing network devices Download Service => Download MBean service MBean collecting information about the software available from MBeans representing HTTP and FTP servers 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
11
The Environment Management Level Application-specific Services Environment MAs coordinate management information and act as care-of of the users requesting the services Es. FTP Download Session Agent Web Monitoring Service by exploiting the HTTP Adapter asks the RMA of the target locality about the managed resources 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)
12
Deployment Scenario: Discovery of Best Download Source RML #2
Conclusion and future work Main advantages of the proposed architecture: Capability of facing the heterogeneity of the environment: JMX
- unifying interface - modular architecture of pluggable components
Dynamic extensibility and adaptability Mobile Agents
mobile, location-aware, customizable service components
We are currently working to: new applications to fully exploit the implemented resource management support 11/09/2003 WOA’03 (Villasimus (Villasimus – Italy)