70 likes | 254 Views
CACI: Context-Aware Component Infrastructure. “Putting components into context” Tom Broens. Introduction. Higher capacity, lower cost computer systems. Ubiquitous computing: Disappearing computers. Helping anywhere, anytime! How to integrate all into something “smart”?? Context-awareness:
E N D
CACI: Context-Aware Component Infrastructure “Putting components into context” Tom Broens
Introduction • Higher capacity, lower cost computer systems. • Ubiquitous computing: • Disappearing computers. • Helping anywhere, anytime! • How to integrate all intosomething “smart”?? • Context-awareness: • Adapt functionality basedon contextual information. • Developing CA applications is difficult: • Distributed, heterogeneous and dynamic context sources. • Mobility user increases changes in (availability of) context. • Substantial development effort (complexity, costs, time).
Context Consumer Context Producer binding Problem domain (1/2) • Roles in a context-Aware system: • Context consumer & Context producer. • 1st generation CA systems: • No supporting infrastructure • Local context sources (tight coupling) • Binding on design time • Static binding • Example: • TomTom (NMEA GPS) • HS24 (Buffersize)
Context Consumer Context Producer binding Supporting Infrastructure Problem domain (2/2) • 2nd generation: • Infrastructure support • Distributed context sources • Binding at run-time (discovery) • Static binding • Pro’s: • Relieve from recurring issues. • Flexibility improves. • Con’s: • Still binding through programming • Flexibility & robustness needs extensive programming
CACI CACI: Solution direction • Extended infrastructure support. • Abstract from programming bindingstatements • Specify binding in abstract concepts (e.g. Entity, QoC) • Offer binding transparency • Declarative binding specification. • (e.g. location, accuracy>0.7) • Continues monitoring and evaluation of binding with possiblere-binding. • Robustness and flexibility of application.
CACI model • Component-based approach • Context ports • Component descriptor • Proof-of-concept prototype • OSGi based
Conclusion • Goal: support CA application developers with a generic infrastructure that facilitates the easy and quick construction of flexible and robust CA applications by offering binding transparencies. • Abstract binding specification • Run-time evaluation and re-binding. • Evaluation: prototyping a telemedicine case with analysis of software quality (metrics, cost estimations). • Hopefully done somewhere summer 2008 ;-)!