Programming Pervasive and Versatile Processing Applications: The TOTA Approach

Presentation Transcript

Programming Pervasive and Mobile Computing Applications: The TOTA Approach Presented By: Hector M Lugo-Cordero, MS EEL 6883

Full Citation Authors: Marco Mamei and Franco Zambonelli From: Universit à di Modena e Reggio Emilia Title: Programming unavoidable and portable processing applications: The TOTA approach Published at: ACM Transactions on Software Engineering and Methodology (TOSEM), vol. 18, issue 4, July 2009

Agenda Introduction Essentials Programming Evaluation Conclusions References

Agenda Introduction Essentials Programming Evaluation Conclusions References

The Problem Information preparing is consolidated into ordinary items Agents can come and leave whenever Information is setting (environment) subordinate Need for a straightforward programming structure

TOTA A tupple situated middleware Tuples are infused into the system No focal regular space

Case Study Scenario Imagine a gigantic exhibition hall like Le Louver on France Many vacationers come every day Makes hard for the administration of administrations and data Assume each client has a remote empowered PC Museum format can change after some time and individuals travel every which way as they need

Current Approaches Direct correspondence Communicate with different specialists is immediate (i.e. hardcoded) Not exceptionally dynamic Shared information space Hard coordination Event base Notifications required These are general (no setting mindfulness)

Agenda Introduction Essentials Programming Evaluation Conclusions References

The TOTA Approach Gathers components from both tuple-based and occasion base models Distributed tuples infused to the system are cloned and proliferated over the system A shared system, every hub running TOTA is the space with restricted neighbors Tuples structure: T = (C, P, M) C = content, P = spread, M = support

TOTA Example (Information)

TOTA in Le Louver Assumption that there is a vast remote system, with a spine How to give data and wanting to stay away from lines ArtPiece C = (depiction, area, separate) P = Propagate to all companions expanding separation M = upgrade if topology changes

Solutions (Information) Solution 1 Art pieces engender tuples Tourists question for the one with lower remove esteem Solution 2 Art pieces don't proliferate tuples Users inquiry for data Art pieces answer

TOTA Example (Meeting)

Solution (Meeting) Meeting C = (tourist_name, separate) P = spread to all associates, increment remove by one M = overhaul the separation tuple upon traveler move Tourist are guided with a GUI to a similar place utilizing the most noteworthy separation recursive process No coordination is indicated by TOTA

TOTA Architecture

Agenda Introduction Essentials Programming Evaluation Conclusions References

TOTA Implementation Java based Using 802.11b communicate Avoid unicast handshake Deployed emulator to build organize estimate Only 16 PDAs and a few portable PCs were utilized a similar code of the emulator could be utilized on gadgets Emulator kept running as a part of blended modes (genuine and copied gadgets)

TOTA Requirements What are the primitives that interface with the middleware? How to determine tuples T = (C, P, M)? How to code composed and setting mindful exercises?

TotaTuple open class MyTuple broadens TotaTuple, actualizes ReactiveComponent {/ReactiveComponent uncovered the respond() technique } TotaTuple myTuple = new MyTuple(new Object[]{"Hello"});

Tota API

TOTA Predefined Tuples

Programming ArtAgent1

Programming TouristAgent1

Programming ArtAgent2

Programming TouristAgent2

Programming MeetingAgent

Agenda Introduction Essentials Programming Evaluation Conclusions References

Software Engineering Analysis Context data makes TOTA general yet more troublesome for operators to respond Separation of tuples (setting) and specialists (rationale) however streamline this Incorporation of summon and layout outline designs encourage tuple programming

Tuple Propagation/Deletion Evaluation Highly adaptable since just engender to its quick neighbors Tu = Trcv + Tprop + Tsend + Ttravel Propagation Time on a WiFi PDA (IPAQ 400 MHz) Tprop 99.7 ms Tsend 67.2 ms Ttravel 0 ms Trcv 21.2 ms Tu 188.1 ms

Tuple Propagation/Deletion Evaluation (cont.) For X bounces T XU = X*T U practically speaking is somewhat more (10–20% from mean) Only HotTuples/MetricTuples and SpaceTuples were influenced by topology

Load and Memory Evaluation Load is accounted to nearby specialist execution and proliferation/upkeep rules Storage is sufficiently little for small scale sensors, yet requires every one to store it Java usage leaves TOTA opened for enhancements in an improved C form

Agenda Introduction Essentials Programming Evaluation Conclusions References

Conclusions TOTA bolster unavoidable and versatile applications By utilizing dispersed tuples so specialists can Extract relevant data Coordinate each other Dynamically modifies as topology changes TOTA shortcomings Strict structure (hard mapping) Security and protection issues Complex operations aren't exceptionally upheld

My Thoughts Strengths: TOTA appears like a capable, convenient API Weaknesses: Authors guaranteed that it is setting free yet just the gallery situation was utilized Unclear mapping on the most proficient method to change genuine issues to TOTA tuples Suggestions: Adding stream of movement by layer to perceive how to translate the pool of tuples over the system Demonstrate the application on various areas, and give a clearer mapping Implementation in C for gadgets that don't gangs a JVM Include wired spine

Agenda Introduction Essentials Programming Evaluation Conclusions References

References http://www.wikipedia.org http://www.agentgroup.unimo.it/wiki/index.php/TOTA http://www.agentgroup.unimo.it/wiki/pictures/2/21/Tutorial.pdf http://www.agentgroup.unimo.it/wiki/pictures/8/8b/Tota.zip

Questions