TY - JOUR
T1 - The swarm at the edge of the cloud
AU - Lee, Edward A.
AU - Rabaey, Jan
AU - Hartmann, Björn
AU - Kubiatowicz, John
AU - Pister, Kris
AU - Simunic Rosing, Tajana
AU - Wawrzynek, John
AU - Wessel, David
AU - Sangiovanni-Vincentelli, Alberto
AU - Seshia, Sanjit A.
AU - Blaauw, David
AU - Dutta, Prabal
AU - Fu, Kevin
AU - Guestrin, Carlos
AU - Taskar, Ben
AU - Jafari, Roozbeh
AU - Jones, Douglas
AU - Kumar, Vijay
AU - Mangharam, Rahul
AU - Pappas, George J.
AU - Murray, Richard M.
AU - Rowe, Anthony
PY - 2014/6
Y1 - 2014/6
N2 - TerraSwarm applications, or swarmlets, are characterized by their ability to dynamically recruit resources such as sensors, communication networks, computation, and information from the cloud; to aggregate and use that information to make or aid decisions; and then to dynamically recruit actuation resources. The TerraSwarm vision cannot be achieved by a single vendor providing the components as an integrated system. What is needed instead is the swarm equivalent of the common, general framework that has recently enabled smartphones and similar devices to rapidly deploy and serve a vast range of often unanticipated applications by recruiting resources and composing services. The SwarmOS must support continual reconfiguration of applications and of its own service definitions without ever having the luxury of a clean restart. It must also support richly heterogeneous computing. TerraSwarm protocols will need to detect compromises, distinguish trusted from untrusted data and resources, and be robust to the presence of a certain number of malicious nodes.
AB - TerraSwarm applications, or swarmlets, are characterized by their ability to dynamically recruit resources such as sensors, communication networks, computation, and information from the cloud; to aggregate and use that information to make or aid decisions; and then to dynamically recruit actuation resources. The TerraSwarm vision cannot be achieved by a single vendor providing the components as an integrated system. What is needed instead is the swarm equivalent of the common, general framework that has recently enabled smartphones and similar devices to rapidly deploy and serve a vast range of often unanticipated applications by recruiting resources and composing services. The SwarmOS must support continual reconfiguration of applications and of its own service definitions without ever having the luxury of a clean restart. It must also support richly heterogeneous computing. TerraSwarm protocols will need to detect compromises, distinguish trusted from untrusted data and resources, and be robust to the presence of a certain number of malicious nodes.
UR - http://www.scopus.com/inward/record.url?scp=84905224451&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84905224451&partnerID=8YFLogxK
U2 - 10.1109/MDAT.2014.2314600
DO - 10.1109/MDAT.2014.2314600
M3 - Review article
AN - SCOPUS:84905224451
VL - 31
SP - 8
EP - 20
JO - IEEE Design and Test of Computers
JF - IEEE Design and Test of Computers
SN - 2168-2356
IS - 3
M1 - 6781658
ER -