<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage 3.0">
<meta name="keywords"
content="Ubiquitous Computing, smart environments, cooperation, HCI, communication, cognition, ad-hoc networks">
<meta name="Template" content="E:\users\michael\doc\paper\huc\sv-lncs97.dot">
<title>AIDE: Point &amp; Click - Interaction in Smart Environments</title>
</head>

<body LINK="#0000ff" VLINK="#800080">
<font FACE="TIMES" SIZE="4"><b>

<table border="0" cellpadding="5" cellspacing="10" width="100%">
  <tr>
    <td align="center" bgcolor="#CFCF9E"><font color="#000000" size="2"
    face="Arial, Helvetica"><a href="http://www.teco.edu/~michael/" style="color: rgb(0,0,0)"><strong>michaels
    home</strong></a></font></td>
    <td align="center" bgcolor="#CFCF9E"><a
    href="http://www.teco.uni-karlsruhe.de/~michael/publications.html"
    style="color: rgb(0,0,0)"><font color="#000000" size="2" face="Arial, Helvetica"><strong>publications</strong></font></a></td>
    <td align="center" bgcolor="#CFCF9E"><a href="http://ms-aic.teco.uni-karlsruhe.de"><font
    color="#000000" size="2" face="Arial, Helvetica"><strong>mib</strong></font></a></td>
    <td align="center" bgcolor="#CFCF9E"><a href="../../contact.html"><font color="#000000"
    size="2" face="Arial, Helvetica"><strong>contact me</strong></font></a></td>
  </tr>
  <tr>
    <td align="center" bgcolor="#CFCF9E"><a href="http://mediacup.teco.edu/"
    style="color: rgb(0,0,0)"><font color="#000000" size="2" face="Arial, Helvetica"><strong>mediacup</strong></font></a></td>
    <td align="center" bgcolor="#CFCF9E"><a href="http://ubicomp.teco.edu"
    style="color: rgb(0,0,0)"><font color="#000000" size="2" face="Arial, Helvetica"><strong>ubicomp</strong></font></a></td>
    <td align="center" bgcolor="#CFCF9E"><a href="http://handheld.teco.edu"
    style="color: rgb(0,0,0)"><font color="#000000" size="2" face="Arial, Helvetica"><strong>handheld
    virtual library</strong></font></a></td>
    <td align="center" bgcolor="#CFCF9E"><a href="../../pgpkey.asc"><font color="#000000"
    size="2" face="Arial, Helvetica"><strong>PGP</strong></font></a></td>
  </tr>
</table>

<p ALIGN="CENTER">&nbsp;</p>

<h1 ALIGN="CENTER">Point &amp; Click - Interaction in Smart Environments</h1>
</b></font><font FACE="TIMES" SIZE="2">

<p ALIGN="JUSTIFY">&nbsp;</p>

<p ALIGN="CENTER">Michael Beigl</p>
</font><div align="center"><center>

<address>
  Telecooperation Office (TecO), University of Karlsruhe, Vincenz-Prießnitz-Str. 1, <br>
  D-76131 Karlsruhe, Germany 
</address>
</center></div>

<p ALIGN="CENTER"><a HREF="mailto:michael@teco.edu">michael@teco.edu</a></p>

<p ALIGN="CENTER"><font FACE="TIMES" size="3">Handheld &amp; Ubiqutious Computing, Lecture
notes in computer science; Vol 1707, ISBN 3-540-66550-1;&nbsp; H-W Gellersen ed.,
Springer, 1999, pp 311-314</font></p>

<dir>
  <dir>
    <font FACE="TIMES" SIZE="1"><b><p ALIGN="JUSTIFY">Abstract.</b> A problem in smart
    environments is the interaction with a myriad of different devices, in particular the
    selection which of the devices should be controlled. Typically, different devices require
    different control tools. In contrast, a generic Point &amp; Click appliance is proposed.
    To interact with a device in the environment this generic control appliance is pointed at
    devices for selection providing visual feedback to the user, obtains control information
    from the device, and allows control with the help of a simple user interface. </p>
  </dir>
</dir>
</font>

<ol>
  <font FACE="TIMES"><b>
  <li>Introduction</li>
  </b></font><font FACE="TIMES" SIZE="2"><p ALIGN="JUSTIFY">An important issue in smart
  environments is how to interact with a wide diversity of devices, and one interesting but
  little explored aspect is how to select devices for interaction. Typical approaches are
  the use of separate controls for different devices (e.g. separate remote controls for TV
  and video), selection based on profiling of user action [1], and selection based on
  context-awareness technology [3]. As an alternative approach we propose the use of a
  generic Point &amp; Click appliance. We call this appliance AIDE (Appliance for
  Interacting with Devices in the Environment)</p>
  <p ALIGN="JUSTIFY">Our Point &amp; Click system consists of a control appliance, the AIDE
  device, for Ubicomp environments and a small extension for devices in such environments.
  We suggest a generic control appliance is useful in particular for interaction with
  devices, which possess <i>no own user interface</i>, or whose function is to be controlled
  although they are <i>in spatial distance</i>, but within visual proximity, and their <i>use
  is not familiar</i>. The following paragraph will present such a device and the belonging
  infrastructure.</p>
  </font><font FACE="TIMES"><b>
  <li>AIDE: A Point &amp; Click Appliance</li>
  </b></font><font FACE="TIMES" SIZE="2"><p ALIGN="JUSTIFY">&quot;Pointing&quot; is an
  important way of communication for humans, if (indirect) control over objects is to be
  executed: Pointing refers to things, which are of interest, both to inform about the
  things and to arrange control. Humans transfer this metaphor to the operation of technical
  devices: Although modern remote controls do not require pointing to the controlled device
  humans tend to direct them directly towards the device. The action of pointing is used to
  select an object for the following command (i.e. the device, which should be controlled).
  Pressing a key or the articulation of a command causes the selection to be performed.
  Therefore, the call of a function can be split into two phases: The pointing-phase where
  you select a device and the phase where a command is selected and send to the device by
  clicking. </p>
  <p ALIGN="JUSTIFY">&nbsp;</p>
  <b><p ALIGN="JUSTIFY">2.1 Pointing-Phase</p>
  </b></font><blockquote>
    <blockquote>
      <blockquote>
        <p ALIGN="JUSTIFY"><img SRC="Image26.gif" WIDTH="265" HEIGHT="174"><img SRC="Image27.gif"
        WIDTH="175" HEIGHT="179"></p>
      </blockquote>
    </blockquote>
  </blockquote>
  <font FACE="TIMES" SIZE="1"><b><p ALIGN="JUSTIFY">Fig. 1.</b> The control appliance (a): A
  human selects a device in the environment (the controlled device (b)) with the help of a
  controlling device through a laser (1). After selection, commands are transmitted to the
  controlling device (2). A human chooses one of the displayed commands with the associated
  button at the Point &amp; Select AIDE device (right figure).</p>
  </font><font FACE="TIMES" SIZE="2"><p ALIGN="JUSTIFY">An important principle for the
  structure of user interfaces is feedback [2], which prescribes a response of the selected
  function to humans. If there are several devices located near to each other, no decision
  can be made which device should be controlled by simply pointing. Optical feedback has to
  be provided during the pointing phase before the selection itself is triggered. When
  pointing to a device which should be controlled the selected device has to be recognized
  by the human as selected. The system presented below simplifies the selection of a device
  by an optical feedback in form of a red laser-point. This phase of selecting a device by
  pointing at it and the optical feedback which device is selected are the major difference
  between the Point &amp; Click appliance and universal remote control applications e.g.
  [4].</p>
  <b><p ALIGN="JUSTIFY">2.2 Click</p>
  </b><p ALIGN="JUSTIFY">For pointing and selecting the device function we have developed a
  small control appliance (Figure 1, right), the AIDE device. AIDE has a LCD screen to
  display available commands that can be sent to the controlled device. The entire process
  of control can be described schematically as follows. First, the AIDE device (a) is
  directed towards the controlled device (b) and the activation key is pressed (pointing
  phase, 1). A laser beam gives an optical feedback, showing which device is selected. When
  the controlled device detects the laser beam, it transfers the control description to AIDE
  using infrared communication (2). This description containing all possible commands is
  shown on the AIDE&#146;s display. The user selects one of the displayed commands using the
  keys at the side of AIDE (click). The selected command is transferred to the controlled
  device and the action is carried out at the device (3). </p>
  </font><font FACE="TIMES"><b>
  <li>Implementation </li>
  </b></font><font FACE="TIMES" SIZE="2"><p ALIGN="JUSTIFY">In order to designate the device
  for everyday usage it should be so small that it fits into a trouser pocket without
  problems. Handheld Computers as PalmPilot are still too big for the proposed usage
  scenario. Since no special requests regarding flexibility for communication and command
  display exist, we refrain from using standard markup languages and protocols as HTML/HTTP
  or WML/WAP. Plain text was used to describe the commands that are shown at the display.
  Each line of the display contains one instruction. </p>
  <p ALIGN="JUSTIFY">The AIDE system consists of two components: the AIDE control appliance
  and an extension for controlled devices, which can be attached to existing switching
  inputs (e.g. buttons). The AIDE device consists of 5 buttons, which are arranged around
  the LCD display, and a laser pointer, an IrDA (Infrared Data Association) communication
  unit and a processor. The LCD display operates in upright mode to support the handling of
  the AIDE device as a pointing device. The button on the right side is used as the
  activation key, the 4 buttons present at the left side as selection keys. The device is
  controlled by a PIC 16F84 microprocessor; communication is performed through an IrDA
  transmitter. The module used at the controlled device uses similar hardware, but without
  laser diode and LCD display. </p>
  </font><font FACE="TIMES"><b>
  <li>Conclusion</li>
  </b></font><font FACE="TIMES" SIZE="2"><p ALIGN="JUSTIFY">We demonstrated advantage of
  generic control appliances as one possibility to control the diversity of devices in a
  smart environment. A major difference between the presented control appliance and
  universal remote controls is the split of interaction with devices in the environment into
  two phases: Point and Click, where in the pointing phase the control appliance provides a
  optical feedback to the user.</p>
  <p ALIGN="JUSTIFY">Further usability tests must show specific strengths of such a system.
  A further reduction of the dimensions of the AIDE device as well as an increase of the
  display resolution will widen the application possibilities.</p>
  </font><font FACE="TIMES"><b>
  <li>References</li>
</ol>

<ol>
  <li><a NAME="_Ref440915240"></a><a NAME="UbicompBrowser"></a></b></font><font SIZE="1">Maes,
    Pattie: Agents that Reduce Work and Information Overload, Communications of the ACM,
    Vol37, No7, July (1994)</li>
  </font><font FACE="TIMES" SIZE="1">
  <li>Norman, Donald A: The Design of Everyday Things, Doubleday (1988)</li>
  </font><font SIZE="1">
  <li>Schmidt, A., Beigl, M., Gellersen, H.-W.:<i> </i><em>There is more to context than
    location</em>: Intl. Workshop on Interactive Applications of Mobile Computing, Rostock,
    Germany (1998)</li>
  <li>Spinellis, D.: Palmtop Programmable Appliance Controls: Personal Technolgies, Vol 2, pp
    11-17 (1998)</li>
</ol>
</font>
</body>
</html>
