Data captured from the physical world through receptor devices such as wireless sensor networks and RFID readers tend to be low-level, device-specific, inconsistent, and unreliable. Meanwhile, data management and query processing techniques in the digital world rely on understandable, consistent, and complete data. This paper aims to bridge this physical-digital divide by introducing Virtual devICEs (VICEs): extensible wrappers that transform the data captured from the physical world into data that can be operated upon by today's data management systems. In this sense, VICEs provide what we term metaphysical data independence by shielding the above data processing system from the complexity of real-world data. This paper introduces the specific challenges to implementing VICEs, the functionality required of them, and outlines the VICE architecture. To validate the VICE approach, we demonstrate three real-world use cases that illustrate the empirical benefits of using VICEs to provide metaphysical data independence.
Title
Virtual Devices: An Extensible Architecture for Bridging the Physical-Digital Divide
Published
2005-03-01
Full Collection Name
Electrical Engineering & Computer Sciences Technical Reports
Other Identifiers
CSD-05-1375
Type
Text
Extent
13 p
Archive
The Engineering Library
Usage Statement
Researchers may make free and open use of the UC Berkeley Library’s digitized public domain materials. However, some materials in our online collections may be protected by U.S. copyright law (Title 17, U.S.C.). Use or reproduction of materials protected by copyright beyond that allowed by fair use (Title 17, U.S.C. § 107) requires permission from the copyright owners. The use or reproduction of some materials may also be restricted by terms of University of California gift or purchase agreements, privacy and publicity rights, or trademark law. Responsibility for determining rights status and permissibility of any use or reproduction rests exclusively with the researcher. To learn more or make inquiries, please see our permissions policies (https://www.lib.berkeley.edu/about/permissions-policies).