170 likes | 195 Views
Explore the proposal on Appliance Aggregation within the P2P technical domain, bridging communities and advancing access to data and services through interconnected IT devices.
E N D
BoF on A3 Appliance Aggregation Architecture Dejan Milojicic Hewlett Packard Global Grid Forum 5, Edinburgh, July 23, 2002
Purpose of This BoF • Evaluate a proposal for a Research Group on Appliance Aggregation within P2P technical area • Bring GGF and P2P communities closer together
Introduction • IT appliances are penetrating daily life • cell phone, digital camera, watch, PDA, laptop, … • Rather than helping, IT is becoming more complex • distributed data, resources, and I/O • hard to manage, use • privacy and security concerns • IT appliances designed & used like traditional ones • one function, isolated state, resources • however, IT appliances are connected, introducing:distributed state, shared resources, apps & functionality • Wearables: battle for the belt
Motivation • Ownership of devices, appliances work only for me • Access any data/resource from any appliance • Use apps from any appliance • Perform tasks unaware of appliances, applications • Appliance ensemble • Levels of aggregation • Ways of using it • interaction of existing appliances • compose new appliances • performance
Scenario 1 I still haven’t finished that report?!
Scenario 1 Ensemble Written notes Aggregation Data Storage Your appliances work together to help you achieve your task Spoken notes/commands
Internet/NW input storage application output Scenario 2, Mix & Match
Outline • Terms and requirements • Vision, Mission, Purpose, Goals • Related Work • Summary • Open Floor
Definition of Terms • Appliance: a (network) device able to aggregate with other devices; a smallest unit of aggregation • example: camera, PDA, laptop, watch, hotspot, etc. • !example: no communication • Ensemble: a group of appliances aggregated to perform a function greater than their parts • example: camera & PDA capture & annotate pictures • !example: fixed relationships (!ad hoc) • Appliance aggregation: multiple appliances operating as a single entity for a period of time • example: use another device’s screen; ensemble-wide app • !example: using predefined clusters
Requirements • Appliance discovery, identity, and communication • Secure communication channels between appliances • No trust boundaries within an ensemble • Access to aggregated resources of personal and environment appliances • Illusion of a “bigger” virtual appliance, consisting of aggregated sum of resources of individual appliances • Tolerance to temporary and permanent failures and disconnection of appliances in an ensemble
Vision (where to) • Perform any function using any IT appliance anywhere
Mission(what and by when) • Devise an architecture of appliance aggregation in the next 2 years
Purpose(why and for whom) • To improve access to data and services from any location using available IT appliances by wide population of people (enterprise, home..)
Tentative Goals • Devise • best practices (6 months) • staged architecture (12, 24, 36 months) • standards (36 months) • working prototypes (6-36 months)
Related Work • Pervasive computing visions • Academia: Weiser, Thackara, Oxygen, Norman, Satya, … • Industry: Digital Jewelry, wearable computing, storage • Platforms • UPnP, Jini, one.world, other academic/industry efforts • Architectures • IBM mainframe, PC • Standards • IEEE 488, IEEE 1394
Summary • Many separate technical solutions already exist • Extraordinary opportunity for innovation, standards • Orthogonal to traditional GGF topics • Potential interest by academia and various industries • Bringing P2P closer to GGF
Open Floor • For contacts, please email to dejan@hpl.hp.com • See also www.ati2002.org on related workshopon critical and pervasive applications