<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Situation-Aware Mobility</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marko Luther</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Bohm</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DOCOMO Communications Laboratory Europe GmbH</institution>
          ,
          <addr-line>Munich</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We consider situation-aware mobile services as applications that could bene t considerably from advances in stream reasoning technology. Our initial realization of a situation-aware mobile service infrastructure combines streams of context information gained from mobile sensors and various Web resources and applies expressive reasoning. With the availability of stream reasoners, this distributed computing infrastructure could be made considerably simpler and more powerful. Recent ndings in applying and evaluating existing reasoning engines are taken into account to highlight essential requirements and potential directions for future research on stream reasoning.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In the recent past, the mobile phone has seen a dramatic shift in its perception
from a plain communication device to an intelligent source of relevant
information for the very moment. Location-based services, rst introduced a couple of
years ago, paved the way for much more useful mobile services that assist the
user in his spatial surrounding. Foreseen as the successor of these mere location
centric services, context-aware applications are meant to enable a multiplicity
of intelligent agents, capable to interpret heterogenous data sources and thus
enabling truly intelligent services.</p>
      <p>
        With IYOUIT1, a framework for novel mobile applications, we recently
introduced a mobile community service in the eld of context-awareness [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Taking
into account various types of context data, including spatial, temporal, social
and environmental information, IYOUIT aims at automatically identifying the
user's current situation (e.g., \sitting in a moving vehicle while commuting to
work") [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Depending on the quality and con dence of the derived information,
sophisticated new mobile services can be built and existing applications may be
enriched to adapt to the user's needs. To give an example, future life-logging
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and real-time social-networking services [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] could become even more versatile
in processing complex requests like \what has been the name of that hotel we
used to stay last summer together with our friends from Rome" or \is my friend
already at home or still on his way".
      </p>
    </sec>
    <sec id="sec-2">
      <title>1 http://www.iyouit.eu</title>
      <p>
        IYOUIT has been realized as a light-weight mobile client application that
connects to a distributed server infrastructure [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Various types of sensory
inputs are recorded on the mobile handset, amongst others including cell tower
information, people and other devices in proximity as well as accelerometer data,
to be sent to the corresponding component in the network. This data either
changes periodically (eg. the accelerator sensor data is measured every minute)
or event driven (eg. location updates triggered by the mobile phone connecting
to another base station). Based on the aggregation, abstraction and the
subsequent combination of this context information with external data sources from
the Web, qualitative and highly valuable data is derived and in turn provided as
input to the mobile client application to adapt to the user's current situation.
      </p>
      <p>
        We see a high potential in the application of semantic technologies, in
particular the deployment of the Web Ontology Language (OWL) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and expressive
inference engines, to classify the wealth of collected context information. Due
to the nature of this constantly changing set of information from heterogeneous
data sources, the concept of stream reasoning [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] could solve a number of issues
that are not addressed satisfactory by semantic technologies available today.
2
      </p>
      <sec id="sec-2-1">
        <title>Architectural Considerations</title>
        <p>To deploy a situation-aware service infrastructure with already existing
semantic technology involves a couple of architectural design decisions, as depicted on
the left-hand side of Figure 1. With mobile handsets becoming more and more
powerful in terms of the number of built in sensors, the client application has
been designed to gather and combine various sensor outputs. For further
processing, lower-level sensor data is sent (approximately every 2 to 20 minutes) to
the network infrastructure via a permanent mobile data connection. The
realtime constraints for the situation computation limit the maximum classi cation
time to not more than a second.</p>
        <p>
          Due to the limitations of current reasoning engines in e ciently dealing with
large data sets in expressive knowledge representations, further abstractions have
to be derived before the actual reasoning can be applied. In our current
architecture, the client server communication follows a standard request reply pattern,
in which the mobile client triggers the actual situation detection as soon as any
of the sensory inputs registers a change in its state. However, only two minimal
snapshots can be compared to decide whether or not a new computation of the
current situation is meaningful or not. With regard to the fact that the
underlying data is often noisy, uncertain or even inconsistent, this decision is hard to
make in the given setting. For example, in case no GPS x is available, IYOUIT
computes the phone's position by mapping the connected base station identi er
to an estimation of its location (latitude, longitude and range) based on previous
measurements that have been stored in a DB [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>Here, stream reasoning could improve the detection of meaningful classi
cation attempts in relocating the event driven evaluation of state changes to the
networked components (cf. right-hand side of Figure 1). With far more
com</p>
        <p>Reasoner</p>
        <p>Sensors
Mobile handset</p>
        <p>Mobile network
Network infrastructure</p>
        <p>SR SR SR SR</p>
        <p>CP</p>
        <p>SR: StreamReasoner
CP: ContextProvider
SP: SituationProvider
External
data
source
publish &amp; subscribe
+
n
to n
i
taup itago
om reg
tac ag
l
e
D
CP</p>
        <p>CP</p>
        <p>External
data
source</p>
        <p>SR</p>
        <p>SP</p>
        <p>DB
puting power available and the possibility to e ciently persist data, larger
timeframes could be taken into consideration. For example, the error rate of detecting
a driving event based on the current speed computed by taking the delta of two
location estimations is far too high, in case no GPS speed is available. If a series
of geo coordinates and their estimated ranges are considered, a driving event can
be detected reliably with simple geometrical calculations that assume a directed
move. Furthermore, a subscription based model of interconnected components
might distribute the previously centralized reasoning task.
3</p>
      </sec>
      <sec id="sec-2-2">
        <title>Performance Considerations</title>
        <p>
          To nd the optimal selection of an OWL reasoner and service interface for our
application that comply with the real-time constraints we conducted extensive
performance evaluations with knowledge bases of di erent size and complexity
[
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. These results con rm earlier ndings [
          <xref ref-type="bibr" rid="ref10 ref11">10,11</xref>
          ] that there is still no reasoner
available, capable to deal with large and complex extensional knowledge in a
robust manner and that the currently available OWL reasoners still fail to answer
a number of small or trivial test cases correctly. As a consequence, we designed
our knowledge bases to be as small and light-weight as possible, only using
language constructs that are strictly needed, to keep the inference complexity
low. A drawback of this is that our knowledge bases do not link to standard
ontologies to avoid an increase in complexity and therefore do not pro t from a
well-de ned cross domain vocabulary.
        </p>
        <p>
          It became also apparent in our study [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] that the utilized reasoner connection
and the amount of data that needs to be transferred may have an enormous
impact on the overall performance. One recent trend to improve this are in-memory
interfaces of reasoners that clearly outperform networked connections via TCP
or HTTP, resulting in a less exible distribution of components. Another way to
reduce the communication overhead is to avoid the retransmission of the same
axioms over and over again. In our application it is possible to clearly separate
the (small set of) changing data from the (larger body of mostly) invariable world
knowledge. Therefore, we may transmit the world knowledge only once and
transmit the limited amount of changing axioms separately, using axiom-retraction to
clean up the reasoner state after having retrieved the inference result. Of course,
both the reasoner and its communication protocol need to support axiom-level
transmission and retraction. To the best of our knowledge, RacerPro [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] is
currently the only OWL engine that supports retraction via all its interfaces,
including its OWLAPI2 connector as well as the standard OWLlink3 protocol [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
Interestingly, RacerPro communicating verbose OWL XML syntax via HTTP
using OWLlink's retraction mechanism outperformed the faster Pellet reasoner
[
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] connected in-memory via the OWLAPI.
        </p>
        <p>Most OWL reasoning algorithms have been designed and optimized for
relative static knowledge bases.</p>
        <p>
          For applications with frequently changing data like expressive syndication
[
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], incremental query answering and incremental reasoning algorithms using
model-caching techniques were developed [
          <xref ref-type="bibr" rid="ref15 ref16">15,16</xref>
          ].
        </p>
        <p>Todays incremental query answering algorithms are limited to theories with
only simple roles whereas our examples rely on transitive rules. Here, the
incremental reasoning algorithms under syntactic addition and removal of extensional
knowledge implemented as part of the incremental consistency checker of newer
Pellet version should be able to considerable speed up our use case. However, we
could not detect any speci c performance gain of this implementation. Still, in
case the actual reasoning task can be computed very fast and the necessary
axioms representing the changing data can be transmitted e ciently, the retrieval
of large inference results back to the application accounts for a time critical task
in the overall process.
4</p>
      </sec>
      <sec id="sec-2-3">
        <title>Discussion</title>
        <p>
          We introduced an application scenario that could bene t from advances in the
eld of stream reasoning. Especially, the use of stream reasoners following the
revolutionary approach [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], communicating data directly as axioms expressed in
OWL or less expressive representation languages, would considerably simplify
and improve our current system architecture.
        </p>
        <p>Our recent performance results clearly demonstrate the need for reasoning
support in modular theories, fast standard axiom level communication protocols
supporting retraction (such as OWLlink), and incremental inference algorithms
as enabling technologies for stream reasoning. At the same time we want to</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>2 http://owlapi.sourceforge.net 3 http://www.owllink.org</title>
      <p>raise our concerns regarding the correctness of even more sophisticated inference
engines, especially, if inference results are used in critical ways (e.g., for
contextdependent access control mechanisms).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Bohm,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Koolwaaij</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Luther</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Souville</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Wagner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Wibbels</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Introducing IYOUIT</article-title>
          .
          <source>In: Int. Semantic Web Conf. (ISWC'08)</source>
          ,
          <source>October</source>
          <volume>27</volume>
          {
          <fpage>29</fpage>
          ,
          <year>2008</year>
          . Volume 5318 of LNCS., Springer (
          <year>2008</year>
          )
          <volume>804</volume>
          {
          <fpage>817</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fukazawa</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kurakake</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Situational reasoning for task-oriented mobile service recommendation</article-title>
          .
          <source>The Knowledge Engineering Review</source>
          <volume>23</volume>
          (
          <year>2008</year>
          )
          <volume>7</volume>
          {
          <fpage>19</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gemmell</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bell</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lueder</surname>
          </string-name>
          , R.:
          <article-title>MyLifeBits: a personal database for everything</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>49</volume>
          (
          <year>2006</year>
          )
          <volume>88</volume>
          {
          <fpage>95</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Koolwaaij</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tarlano</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nurmi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mrohs</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Battestini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vaidya</surname>
          </string-name>
          , R.:
          <article-title>ContextWatcher { sharing context information in everyday life</article-title>
          .
          <source>In: Proc. of the IASTED International Conference on Web Technologies, Applications, and Services (WTAS'06)</source>
          . (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Bohm,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Koolwaaij</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Luther</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Share whatever you like</article-title>
          .
          <source>In: Proceedings of the First International DisCoTeC Workshop on Context-aware Adaptation Mechanisms for Pervasive and Ubiquitous Services (CAMPUS'08)</source>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Patel-Schneider</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hayes</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horrocks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>OWL Web Ontology Language: Semantics and Abstract Syntax</article-title>
          .
          <source>W3C Recommendation, 10 February</source>
          <year>2004</year>
          , World Wide Web Consortium (
          <year>2004</year>
          ) &lt;http://www.w3.org/TR/owl-semantics/&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>Della</given-names>
            <surname>Valle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Ceri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Barbieri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Braga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Campi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <article-title>A First step towards Stream Reasoning</article-title>
          .
          <source>In: Proceedings of the Future Internet Symposium</source>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Koolwaaij</surname>
          </string-name>
          , J.:
          <article-title>Mapping the GSM landscape</article-title>
          .
          <source>In: Proceedings of the SVG Open</source>
          .
          <article-title>(</article-title>
          <year>2005</year>
          ) &lt;http://www.svgopen.org/2005/proceedings.html&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          , Bohm,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Noppens</surname>
          </string-name>
          ,
          <string-name>
            <surname>O.</surname>
          </string-name>
          :
          <article-title>Who the Heck is the Father of Bob?</article-title>
          <source>In: Proc. of the European Semantic Web Conference (ESWC'09)</source>
          . Volume 5554 of LNCS., Springer, Heidelberg (
          <year>2009</year>
          )
          <volume>66</volume>
          {
          <fpage>80</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. Weithoner, T.,
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Bohm, S.,
          <string-name>
            <surname>von Henke</surname>
            ,
            <given-names>F.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noppens</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Real-world reasoning with OWL</article-title>
          .
          <source>In: Proceedings of the 4th European Semantic Web Conference (ESWC'07)</source>
          , Innsbruck, Austria (
          <year>2007</year>
          )
          <volume>296</volume>
          {
          <fpage>310</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Reasoning with OWL: System Support and Insights</article-title>
          .
          <source>Technical Report TR-2006-04</source>
          , Ulm University, Germany (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Haarslev</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          , Moller, R.:
          <article-title>Description of the RACER system and its applications</article-title>
          .
          <source>In: Proc. of the Int. Workshop on Description Logics</source>
          . (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Liebig</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luther</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Noppens</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodriguez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvanese</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wessel</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tsarkov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
          </string-name>
          , E.:
          <article-title>OWLlink: DIG for OWL 2</article-title>
          .
          <source>In: Proc. of the OWL Experiences and Directions Workshop</source>
          at the ISWC'
          <fpage>08</fpage>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalyanpur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Pellet: A practical OWL-DL reasoner</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>5</volume>
          (
          <year>2007</year>
          )
          <volume>51</volume>
          {
          <fpage>53</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Halaschek-Wiener</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolovski</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Syndication on the Web using a Description Logic approach</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>6</volume>
          (
          <year>2008</year>
          )
          <volume>171</volume>
          {
          <fpage>190</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Halaschek-Wiener</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sirin</surname>
          </string-name>
          , E.:
          <article-title>Description Logic reasoning with syntactic updates</article-title>
          . In Meersman, R.,
          <string-name>
            <surname>Tari</surname>
            ,
            <given-names>Z</given-names>
          </string-name>
          ., eds.
          <source>: OTM Conferences</source>
          . Volume
          <volume>4275</volume>
          of LNCS., Springer (
          <year>2006</year>
          )
          <volume>722</volume>
          {
          <fpage>737</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>