Search for: All records

Recent years have seen the rapid deployment of low-cost CubeSats in low-Earth orbit, many of which experience significant latency (several hours) from the time information is gathered to the time it is communicated to the ground. This is primarily due to the limited availability of ground infrastructure that is bulky to deploy and expensive to rent. This article explores the opportunity in leveraging the extensive terrestrial LoRa infrastructure as a solution. However, the limited bandwidth and large amount of Doppler on CubeSats precludes these LoRa links to communicate rich satellite Earth images—instead, the CubeSats can at best send short messages. This article details our experience in designing LoRa-based satellite ground infrastructure that requires software-only modifications to receive packets from LoRa-enabled CubeSats recently launched by our team. We present Vista, a communication system that adapts encoding onboard the CubeSat and decoding configuration on commercial LoRa ground stations to allow images to be communicated. We perform a detailed evaluation of Vista by leveraging wireless channel measurements from a recent CubeSat (2021), and show that Vista can achieve 55.55% lower latency in retrieving data with 12.02 dB improvement in packet retrieval in the presence of terrestrial interference. We then evaluate Vista on a case study on land-use classification over images transmitted over the CubeSat link to further demonstrate a 4.56 dB improvement in image PSNR and 1.38× increase in classification accuracy over baseline approaches.

 

We present Peekaboo, a new privacy-sensitive architecture for smart homes that leverages an in-home hub to pre-process and minimize outgoing data in a structured and enforceable manner before sending it to external cloud servers. Peekaboo’s key innovations are (1) abstracting common data preprocessing functionality into a small and fixed set of chainable operators, and (2) requiring that developers explicitly declare desired data collection behaviors (e.g., data granularity, destinations, conditions) in an application manifest, which also specifies how the operators are chained together. Given a manifest, Peekaboo assembles and executes a pre-processing pipeline using operators pre-loaded on the hub. In doing so, developers can collect smart home data on a need-to-know basis; third-party auditors can verify data collection behaviors; and the hub itself can offer a number of centralized privacy features to users across apps and devices, without additional effort from app developers. We present the design and implementation of Peekaboo, along with an evaluation of its coverage of smart home scenarios, system performance, data minimization, and example built-in privacy features. 

In this paper, we studied people’s smart home privacy-protective behaviors (SH-PPBs), to gain a better understanding of their privacy management do’s and don’ts in this context. We first surveyed 159 participants and elicited 33 unique SH-PPB practices, revealing that users heavily rely on ad hoc approaches at the physical layer (e.g., physical blocking, manual powering off). We also characterized the types of privacy concerns users wanted to address through SH-PPBs, the reasons preventing users from doing SH-PPBs, and privacy features they wished they had to support SH-PPBs. We then storyboarded 11 privacy protection concepts to explore opportunities to better support users’ needs, and asked another 227 participants to criticize and rank these design concepts. Among the 11 concepts, Privacy Diagnostics, which is similar to security diagnostics in anti-virus software, was far preferred over the rest. We also witnessed rich evidence of four important factors in designing SH-PPB tools, as users prefer (1) simple, (2) proactive, (3) preventative solutions that can (4) offer more control.