<!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>How to build a Context-aware Architecture for Ubiquitous VR</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Yoosoo Oh</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Woontack Woo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>[2005-S-069-02, Development of Technologies for Unifying and Fusing Context]. Yoosoo Oh is with the Gwangju Institute of Science and Technology</institution>
          ,
          <addr-line>Gwangju 500-712, S.</addr-line>
          <country country="KR">Korea</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2007</year>
      </pub-date>
      <abstract>
        <p>- There are no general context-aware architectures to be useful which could be applied to full life cycle in ubiquitous VR, even though many context-aware architectures or middleware are proposed. In this paper, we propose a general approach of a context-aware architecture for ubiquitous virtual reality. We would discuss how to improve the intelligence ability in a context-aware architecture.</p>
      </abstract>
      <kwd-group>
        <kwd>Context Interpretation</kwd>
        <kwd>Context Learning</kwd>
        <kwd>Context Reasoning</kwd>
        <kwd>Social Relationship</kwd>
        <kwd>Ubiquitous VR</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>
        UVR(virtual reality) environments which make VR
biquitous VR is a concept of creating ubiquitous
pervasive into our daily lives and ubiquitous by allowing VR to
meet UbiComp(ubiquitous computing) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. To make seamless
connection between human beings and VR and UbiComp
environments, we need to have an infrastructure which is
specified by sensors and services for the collaboration of those
environments. In different domains like human, real and virtual
environment, a context-aware architecture for Ubiquitous VR
is necessary to be established.
      </p>
      <p>
        There are many previous works related to a context-aware
architecture. CAMidO is a Context-Aware Middleware based
on an Ontology meta-model [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. CAMidO Compiler generates
Inference rule file and controller source code. However,
CAMidO has the sophisticated path in architecture and has the
weak relationship among context sources. JCAF is the Java
Context Awareness Framework [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. JCAF cooperates with
context services and supports for adding, deleting, modifying,
or varying functionality, capacity, or platform at runtime. JCAF
should solve synchronizing data used in many systems.
SOCAM is a Service-Oriented Context-Aware Middleware [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
SOCAM supports context reasoning and knowledge sharing
process by using common context model. SOCAM depends on
OWL, and so it’s not easy to be used widely. Besides these
architectures, there are many related works.
      </p>
      <p>However there is still a need for a generic solution for
seamless connection among users and real/virtual
environments. Previous context-aware architectures are not
proper to use and apply to real and virtual environments. Those
should be considered more about connection among
domain-free entities. Thus, more general approach to
context-aware architecture should be developed. In this paper,
we propose a general approach of a context-aware architecture
for ubiquitous virtual reality. Also, we want to discuss some
issues which are how to improve the intelligence ability in a
context-aware architecture.</p>
      <p>There are no general context-aware architectures to be useful
which could be applied to full life cycle in ubiquitous VR, even
though many context-aware architectures or middleware are
proposed. Also, it’s hard to apply the working architectures or
middleware to a new domain that is not mentioned in their
original works. Thus, we should discuss how to build
standardized and generalized context-aware architectures for
various environments.</p>
    </sec>
    <sec id="sec-2">
      <title>II. CONTEXT-AWARE ARCHITECTURE: UCAM</title>
      <sec id="sec-2-1">
        <title>A. UCAM architecture</title>
        <p>
          UCAM is a Unified Context-aware Application Model for
seamless human-content-environment interaction in ubiquitous
computing environment [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Figure 1 shows UCAM
architecture. For the general approach, we modified previous
UCAM. Our proposed UCAM particularly supports
intelligence like context reasoning, learning, interpretation, and
social relationship management. The proposed UCAM
architecture used context model which describes context as a
form of 5W1H (Who, What, Where, When, How, and Why) [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
The context model also maintains context history as context
repository.
        </p>
        <p>The proposed architecture can improve the awareness ability
of context because the architecture can interpret, reason out,
and learn contexts. The architecture can connect any tool for
the awareness ability as an add-on feature. Also, the
architecture manages social relationship among human, real
objects, and virtual objects. For these aspects, our architecture
is generalized as an open source code which is a library for
basic features. An application developer can simply use our
architecture by inheriting the library code.</p>
        <p>UCAM (Service)</p>
        <p>Context Manager</p>
        <p>Application</p>
      </sec>
      <sec id="sec-2-2">
        <title>B. Core technology</title>
      </sec>
      <sec id="sec-2-3">
        <title>1) Context Model</title>
        <p>Context Model in UCAM is defined a set of user contexts
that supports ontological structure and reasoning operations. It
has to know what kinds of operations are needed in each
component in UCAM. It is related to all components in UCAM
and generates and saves contexts.</p>
      </sec>
      <sec id="sec-2-4">
        <title>2) Context Reasoning</title>
        <p>Context Reasoning in UCAM is a logical process which
extracts high-level(implicit) context from low-level(explicit)
context and maintains context consistency in processing
context modeling. For context reasoning, it is necessary to
various kinds of sensors and information sources. Context
reasoning process reuses context (context history) and adapts
reconfigurable rules to the diverse environment. It is related to
sensor part of UCAM and Context Integrator in UAM service.</p>
      </sec>
      <sec id="sec-2-5">
        <title>3) Context Learning</title>
        <p>Whether the context-aware application obtains its context
information from environmental sensors, user input, VR
applications, or some combination of these, it must perform a
good deal of processing on the long-term context in order to be
able to accurately evaluate the state of the environment, the
intensions of the user, and avatar’s intelligent reaction. Thus,
Context Learning in UCAM is required to context-aware
applications. Context learning is related to Context Manager in
UCAM, and uses classified learning mechanisms according to
the characteristics of them.</p>
      </sec>
      <sec id="sec-2-6">
        <title>4) Context Interpretation</title>
        <p>Context Interpretation in UCAM is the way the entity
generates conditional context for performing certain task, and
the way the entity presents current context to the
entity-readable way. It generates conditional context from
user's direct input (Feedback) and do context-to-service
parameter mapping (Domain Change). Context interpreter
maps elements in context format to each application domain,
and one application to another application. It requires
knowledge about both context format and application
parameters for interpretation.</p>
      </sec>
      <sec id="sec-2-7">
        <title>5) Social Relationship Management</title>
        <p>Social Relationship Management in UCAM determines
relationships among sensors and services which participating in
ubiquitous VR environment (human, real/virtual env.). To
manage social relationship among entities in ubiquitous VR
environment, those entities (users, services and sensors) should
collaborate each another in the created community. This
process is done by Communicator in UCAM which takes
charge of network configuration and sends messages to
community members.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>III. DISCUSSION</title>
      <p>The proposed architecture can improve the awareness ability
and extend to diverse application domains. Also, the
architecture, UCAM, is generalized as a library in order to be
used easily by application developers. However we still have
many issues to be discussed. First issue is how to predict user’s
behavior and connect to the other objects in real/virtual
environment. Basically, UCAM can support the reasoning
aspect, not prediction for user’s behavior. For more
generalization, this issue should be considered. Second issue is
full life cycle support for context-aware applications. Adding,
deleting, replacing, modifying, and debugging entities should
be supported. These functionalities are already supported by
UCAM, but need to be improved for ubiquitous VR
environment. Last issue is how to evaluate a context-aware
architecture. There are good evaluation methods in HCI field.
Thus, those methods should be applied to our UCAM with
some evaluation factors, such as architecture structure,
scalability, accountability, reconfiguration, reusability,
debugging, openness, flexibility, etc. These evaluation factors
could be useful to verify the general approach and intelligence
ability of our UCAM.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Suh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lee</surname>
          </string-name>
          , W.Woo, “
          <article-title>Toward ubiquitous VR: When VR Meets ubiComp</article-title>
          ,
          <source>” ISUVR</source>
          <year>2006</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>4</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Nabiha</given-names>
            <surname>Belhanafi</surname>
          </string-name>
          <string-name>
            <surname>Behlouli</surname>
          </string-name>
          ,
          <article-title>Chantal Taconet and Guy Bernard, “An Architecture for supporting Development and Execution of Context-Aware Component applications</article-title>
          ,” In IEEE International Conference on Pervasive Services,
          <string-name>
            <surname>ICPS</surname>
          </string-name>
          <year>2006</year>
          , Lyon, France,
          <fpage>26</fpage>
          -
          <lpage>29</lpage>
          June,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Jakob</surname>
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Bardram</surname>
          </string-name>
          , “
          <article-title>The Java Context Awareness Framework (JCAF) - A Service Infrastructure and Programming Framework for Context-Aware Applications,”</article-title>
          <source>In Proceedings of the 3rd International Conference on Pervasive Computing (Pervasive</source>
          <year>2005</year>
          ),
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Tao</given-names>
            <surname>Gu</surname>
          </string-name>
          , Hung Keng Pung, Da Qing Zhang, “
          <article-title>Toward an OSGi-Based Infrastructure for Context-Aware Applications,” IEEE Pervasive Computing</article-title>
          , vol.
          <volume>03</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>66</fpage>
          -
          <lpage>74</lpage>
          , Oct-Dec,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D.</given-names>
            <surname>Hong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Shin</surname>
          </string-name>
          , Sj.Oh,
          <string-name>
            <given-names>W.</given-names>
            <surname>Woo</surname>
          </string-name>
          , “
          <article-title>A New Paradigm for User Interaction in Ubiquitous Computing Environment</article-title>
          ,
          <source>” ISUVR</source>
          <year>2006</year>
          , pp.
          <fpage>41</fpage>
          -
          <lpage>44</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>