Figure 2 - uploaded by Armando Fox
Content may be subject to copyright.
Source publication
Digital appliances designed to simplify everyday tasks are readily available to end consumers. For example, mobile users can retrieve Web content using handheld devices since content retrieval is well-supported by infrastructure services such as transformational proxies. However, the same type of support is lacking for input-centric devices, those...
Context in source publication
Similar publications
This study focuses on network configurations to accommodate automated vehicles (AVs) on road networks during the transition period to full automation. The literature suggests that dedicated infrastructure for AVs and enhanced infrastructure for mixed traffic (i.e., AVs on the same lanes with conventional vehicles) are the main alternatives so far....
Citations
... Bring the devices to the forefront [1]: The current revolution on handheld devices allowed this research to propose an On-Device Development (ODD) approach so as to develop and execute stand-alone applications altogether from within handheld devices without the need of any external tool such as desktop computer. This provides more resource utilization for current and prospective mobile devices, and a better online development environment within the real context anywhere, at anytime for real time applications independent of emulation tools. ...
... taps, pads, and boards) to the forefront and set the traditional devices (e.g. PC) to the background as encouraged by some researchers [1][2][3]. ...
Ubiquitous Control Modeling Language (UCML) is an XML-based language aiming at utilizing the local resources of smart handheld devices and making mobile phone users aware and involved in contributing to the technology that exists in their hands. UCML focuses on developing and executing ubiquitous control applications within smart mobile devices by typing specific predefined XML elements in UCML modules directly on the device. The module function is to acquire data from mobile phone built-in sensors, apply conditions on these data, and trigger a response when these conditions are satisfied. The user can identify which sensor, condition and response to be used. UCML application has been designed to be friendly, easy-to-use, natural-understanding language that is suitable for sensor-interested mobile phone users. Google's Android is the chosen platform to be the underlying operating system for UCML. This paper proposes the On-Device Development approach (ODD) and discusses some technologies and tools that have influenced the development of UCML. The current UCML version represents basic prototype software with sample conditions and responses. Therefore, it has the potential to be extended and upgraded, allowing integration with other applications and to work with remote sensors and actuators to mimic a complete Ubiquitous Computing environment.
... The iRoom [Johanson et al. 2002] and Appliance Data Services [Huang et al. 2001] projects at Stanford provide ad hoc interoperation of loosely coupled services by allowing them to share data through tuplespaces (a concept first described by Gelernter [1985] in which arbitrary data tuples can be written onto a blackboard, and detected and consumed by other services). Such systems can provide far greater flexibility than agreement on fixed protocols, since the set of tuple types is easily evolvable; new tuple formats can coexist with old ones, for example. ...
This article describes an infrastructure that supports the creation of interoperable systems while requiring only limited prior agreements about the specific forms of communication between these systems. Conceptually, our approach uses a set of “meta-interfaces”—agreements on how to exchange new behaviors necessary to achieve compatibility at runtime, rather than requiring that communication specifics be built in at development time—to allow devices on the network to interact with one another. While this approach to interoperability can remove many of the system-imposed constraints that prevent fluid, ad hoc use of devices now, it imposes its own limitations on the user experience of systems that use it. Most importantly, since devices may be expected to work with peers about which they have no detailed semantic knowledge, it is impossible to achieve the sort of tight semantic integration that can be obtained using other approaches today, despite the fact that these other approaches limit interoperability. Instead, under our model, users must be tasked with performing the sense-making and semantic arbitration necessary to determine how any set of devices will be used together. This article describes the motivation and details of our infrastructure, its implications on the user experience, and our experience in creating, deploying, and using applications built with it over a period of several years.
... The designers of ADS [60] recognized that the use of distributed services and devices such as those supported by Jini or UPnP often revolves around moving data from one to another. Unfortunately, in some cases, this task can be unexpectedly difficult. ...
Ubiquitous computing (ubicomp) is a compelling vision for how people will interact
with multiple computer systems in the course of their daily lives. To date,
practitioners have created a variety of infrastructures, middleware and toolkits to
provide the flexibility, ease of programming and the necessary coordination of distributed
software and hardware components in physical spaces.
However, to-date no one approach has been adopted as a default or de-facto
standard. Consequently the field risks losing momentum as fragmentation occurs.
In particular, the goal of ubiquitous deployments may stall as groups deploy and
trial incompatible point solutions in specific locations. In their defense, researchers
in the field argue that it is too early to standardize and that room is needed to explore
specialized domain-specific solutions.
In the absence of an agreed upon set of standards, we argue that the community
must consider a methodology that allows systems to evolve and specialize, while
at the same time allowing the development of portable applications and integrated
deployments that work between between sites.
To address this we studied the programming models of many commercial and
research ubicomp systems. Through this survey we gained an understanding of
the shared abstractions required in a core programming model suitable for both
application portability and systems integration.
Based on this study we designed an extensible core model called the Ubicomp
Common Model (UCM) to describe a representative sample of ubiquitous systems
to date. The UCM is instantiated in a flexible and extensible platform called the
Ubicomp Integration Framework (UIF) to adapt ubicomp systems to this model.
Through application development and integration experience with a composite
campus environment, we provide strong evidence that this model is adequate for
application development and that the complexity of developing adapters to several
representative systems is not onerous. The performance overhead introduced by
introducing the centralized UIF between applications and an integrated system is
reasonable. Through careful analysis and the use of well understood approaches
to integration, this thesis demonstrates the value of our methodology that directly
leverages the significant contributions of past research in our quest for ubicomp
application and systems interoperability.
... On the other hand, there is work that addresses the infrastructures that will make ubiquitous computing feasible [8,17]. This latter category depends, in large part, on the existence of application developers or at least technically sophisticated systems administrators to wire together the available resources into applications that meet the needs of users. ...
The future world of ubiquitous computing is one in which we will be surrounded by an ever-richer set of networked devices and services. In such a world, we cannot expect to have available to us specific applications that allow us to accomplish every conceivable combination of devices that we might wish. Instead, we believe that many of our interactions will be through highly generic tools that allow end-user discovery, configuration, interconnection, and control of the devices around us. This paper presents a design study of such an environment, intended to support serendipitous, opportunistic use of discovered network resources. We present an examination of a generic browser-style application built on top of an infrastructure developed to support arbitrary recombination of devices and services, as well as a number of challenges we believe to be inherent in such settings.
... In this paper we describe UbiWise, a software framework for researchers to simulate hardware and low-level software so that more work can be done on the other dimensions of ubiquitous computing. UbiWise was born out of a desire to make progress on systems for devices [3] without waiting for the devices themselves. Ultimately we hope this leads to more ideas for hardware and more refined requirements for it. ...
simulation, mobile, ubiquitous, handheld We describe UbiWise, a simulator for ubiquitous computing. The simulator concentrates on computation and communications devices situated within their physical environments. It presents two views, each in a separate window on the desktop of the users' PC. One of the views provides a three dimensional world, built on the Quake III Arena graphics engine and serves to simulate a first-person view of the physical environment of a user. The other view, built using Java, shows a close-up view of devices and objects the user may manipulate. These views act as one unified whole by maintaining a client-server model with a central server. Multiple users can attach to the same server to create interactive ubiquitous computing scenarios. We describe how UbiWise looks to researchers and examples of its use as tool for ubiquitous computing research. Abstract. We describe UbiWise, a simulator for ubiquitous computing. The simulator concentrates on computation and communications devices situated within their physical environments. It presents two views, each in a separate window on the desktop of the users' PC. One of the views provides a three dimensional world, built on the Quake III Arena graphics engine and serves to simulate a first-person view of the physical environment of a user. The other view, built using Java, shows a close-up view of devices and objects the user may manipulate. These views act as one unified whole by maintaining a client-server model with a central server. Multiple users can attach to the same server to create interactive ubiquitous computing scenarios. We describe how UbiWise looks to researchers and examples of its use as tool for ubiquitous computing research.
... • The Appliance Data Services (ADS) project at Stanford University [10,11] has similar goals to Omnisphere. It explores a vision of an appliance computing world in which users move data seamlessly among various devices. ...
will become future Internet appliances. To support them, communication networks must evolve to seamlessly assist appliances and provide advanced functionalities. We present a personal communication environment called Omnisphere that provides a communication and information universe surrounding wireless appliances. It is based on a high level concept called ambient services that allows to construct complex services out of primitive ones by connecting them with typed data flows. A typed data flow is an abstract view of communication between ambient services. It encapsulates three elements: channels, control, and metadata. Omnisphere provides a predefined service for discovery of component services and binding them together with data flows. Our strategy for service discovery is to delegate most of the operations to the network infrastructure and to automate them as much as possible. Based on the User ID and Appliance ID, Omnisphere retrieves the information that restricts the set of possible services: User Preferences, Device Capabilities, and Context. It then makes use of existing discovery protocols such as SLP, Jini, or UPnP to discover relevant services and matches them with the required characteristics. Such a discovery process relieves appliances, which may have limited resources, from the operation that may consume scarce resources and may require the availability of different discovery protocols on the appliance.
... Portolano [Esler et al., 1999] and Appliance Data Services [Huang et al., 2001] are projects that investigate ways to integrate input-centric appliances, such as digital cameras and PDAs, into the existing computing environment, making it easier to move data seamlessly among heterogeneous devices. Our work also deals with input-centric devices. ...
Capture and access applications automate the capture of and the ac-cess to live experiences and are a main theme in the ubiquitous computing re-search area. Examples of such applications have been built in the educational, office and meeting domains, and most of them make extensive use of network communication, multimedia streaming and storage systems. Despite their com-mon needs and architectural similarities, there is a lack of middleware support for building capture and access applications. The literature reports on efforts towards providing network abstractions that make communication between ap-plications transparent. Leveraging off that work, we present in this paper a set of component-based infrastructures and services providing capture and access ap-plications with abstractions for functionality and distributed data management. To illustrate the utility of our approach, we detail its use in the implementation of a live lecture capture system.
... Also, communication protocols are statically fixed within them. For example, ADS[11] adopts Ninja[7][8], the Document-based framework[10] exploits a remote method invocation mechanism, and UPnP[27][13] are based on SOAP/HTTP. They cannot be substituted by other S2S communication mechanisms, such as HTTPbased , RTP-based, nor SMTP-based ones. ...
This paper proposes a pluggable service-to-service (S2S) communication mechanism in a middleware for home networks, called Virtual Networked Appliance (VNA) architecture. In the architecture, service description method and the plug-gable S2S communication mechanism are separated in an orthogonal way. Through the separation, VNA architecture solved problems of home networks on which users have to operate multiple heterogeneous middleware technologies simultaneously: middleware fragmentation problem, due to complexity of realizing heterogeneous services on one middle-ware technology: aspect realization violation problem. The pluggable S2S communication mechanism provides service programmers with a simple aspect representation method to define a service-specific protocol concern apart from the service's implementation. It also provides off-the-shelf protocol modules of such well-known communication protocols as RTP, RTSP, HTTP, and SMTP for an inter-service communication, and dynamically loads them based on the aspects defined by the programmer. This reduces the complexity of implementing heterogeneous services on the VNA architecture, thereby addressing the problems. In this paper, we first clarify the two problems. Then, we describe the proposed mechanism with an overview of the middleware architecture referring to a composite service: "Follow-You-and-Me Video."
... In the BARWAN project [15] a network of workstations was used as a middleware tier to provide transcoding for multiple WWW clients. Finally, Application Data Services [42] allows users to transfer data from non-traditional network appliances, such as digital cameras, through a network infrastructure. ...
submitted to MED-HOC-NET Workshop.
... The use of a software architecture to assist applications in general has been explored by many other groups. Other work producing related software support for heterogeneous or mobile computing include Rover [Joseph+95], Active Networks [Tennenhouse+96], Odyssey [Noble+97], Wireless Andrew [Bennington+97], Possession [Mochizuki+99], Mobile People Architecture [Swierk+00], and Appliance Data Services [Huang+01]. ...
OF THE DISSERTATION Utilising Application Session Handoff to Support the Pervasive Computing Vision in the Nascent Millennium by Thomas Phan Doctor of Philosophy in Computer Science University of California, Los Angeles, 2002 Professor Rajive Bagrodia, Chair Pervasive computing, also known as ubiquitous or nomadic computing, is an emerging field that suggests the capability for users to perform daily computer activities on any device, at any time, and at any location. In this dissertation we suggest a particular instance of this vision involving the utilisation of a pervasive application that seamlessly and xii automatically follows the user over the network between heterogeneous client devices, a capability we term application session handoff. To the user, all interactivity appears to be part of one single continuous application even when running on heterogeneous clients, such as desktop PCs, laptops, and PDAs. Such a program maintains a session state which we define as a minimal set of application-level data structures, files, and network connections required to encapsulate the current temporal and spatial location of the executing program. While other researchers have investigated application migration, we further focus on realistic contemporary scenarios involving mobile Internet-connected programs running on heterogeneous platforms participating within legacy systems. We posit that with this capability, users will become accustomed to data availability rather than aware of its conspicuous absence among different devices. To demonstrate the utility and relevance of our work, we provide a variety of case studies.
