<!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>Demonstration: Sensapp ⎯ An Application Development Platform for OGC-based Sensor Services</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dumitru Roman</string-name>
          <email>dumitru.roman@sintef.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Xiaoxin Gao</string-name>
          <email>gao1738@qq.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arne-Jørgen Berre</string-name>
          <email>arne.j.berre@sintef.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>SINTEF</institution>
          ,
          <addr-line>Oslo</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper introduces the Sensapp platform, a semantic and OGCbased sensor application platform to enable users to register, annotate, search, visualize, and compose OGC-based sensors and services for creating addedvalue services and applications. Functionalities of Sensapp such as sensor registration, sensor data visualization, visual composition and generation of executable service compositions are presented through the demo.</p>
      </abstract>
      <kwd-group>
        <kwd>OGC services</kwd>
        <kwd>service annotation</kwd>
        <kwd>discovery</kwd>
        <kwd>and composition</kwd>
        <kwd>sensor Web application</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>With the dramatic increase of sensor devices, large scale management of real-time
data from such devices has become a real issue. Abstracting, selecting, and presenting
real-time sensor data to end-users and decision makers in a suitable manner is a key
requirement for enabling better decision making when dealing with processes
involving real-time sensor data. Moreover, the need for supporting application
developers in making sense of the huge amounts of real-time sensor data and using
the data for creation of added-value applications and services implies development of
novel platforms enabling faster and smarter development of added-value services.
Sensapp (short for “Sensor application platform”) is being developed as a platform
addressing such needs. Focusing on the use of open standards such as those developed
by the Open Geospatial Consortium (OGC)1 and World Wide Web Consortium
(W3C),2 Sensapp aims to deliver a semantic and OGC-based sensor Web application
platform to enable users to register, search, visualize, and compose OGC-based
sensors and services for creating added-value services and applications on the Web.</p>
      <p>
        Figure 1 provides an overview of the platform and its main components. The
major stakeholders/roles in a Sensapp environment are resource providers,
app/service developers, and application consumers (typically decision makers).
Resource providers provide different kinds of resources such as sensors and data and
1 http://www.opengeospatial.org/
2 http://www.w3.org/
processing services. Data formats and protocols for accessing such resources are
usually proprietary. The app/service developer is the main stakeholder interacting
directly with all Sensapp components. Through the registration facility, the app
developer will package and provide the sensor, data, and processing services as
standardized OGC interfaces (e.g., Sensor Observation Services (SOS) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], Web
Feature Services (WFS) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Web Processing Services (WPS) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Sensor Event
Services (SES) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], etc). These OGC service interfaces are then semantically
annotated through the annotation functionality of the platform. The Resource
Description Framework (RDF) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] annotations are used in the discovery and
composition components. The discovery functionality enables enhanced search for
services, which in turn will be used in the composition process where new
addedvalue services are created. Composition is done by the app developer in a visual
manner, based on the Business Process Modeling Notation (BPMN) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The
composition component contains facilities for data mapping, where semantic
annotations of services are used. Once a composition is created, an executable
representation of the composition is generated in Web Service Business Process
Execution Language (WS-BPEL) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and a service interface (typically in WSDL) is
created for the newly developed service. Based on portlets technologies (in particular
Java Portlet Specification [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]), the platform can generate graphical components
(scenario websites) corresponding to the developed services. The end user (typically
decision makers) can consume the added-value services through the generated
scenario websites.
      </p>
      <p>Sensapp</p>
      <p>Application/service developers
Search f or services</p>
      <p>Discovery</p>
      <p>Annotation of
standardized interf aces</p>
      <p>(RDF)
Semantic
Annotation</p>
      <p>Creation of
standardized interf aces
(SOS, SES, WFS, WMS, WPS)</p>
      <p>Registration</p>
      <p>Creation of new services</p>
      <p>(BPMN)</p>
      <p>Composition</p>
      <p>Generation of executable
compositions and deployment
(BPEL, WSDL)</p>
      <p>Execution
Sensors Processing Services Data Services</p>
      <p>Resource providers</p>
      <p>Fig. 1. Sensapp overview</p>
      <p>Generation of
Scenario Websites</p>
      <p>(Portlets)
Visualization</p>
      <p>End-users,
decision makers</p>
      <p>By supporting abstraction of sensor data and services to standardized OGC
interfaces/services, semantic annotation of such interfaces, enhanced discovery and
composition of services, and data visualization on maps and charts, Sensapp aims to
enable better access to sensor data and to create opportunities for faster and smarter
development of added-value services based on real-time sensor data.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Demonstration</title>
      <p>The demo will present some of the functionalities of Sensapp in particular related to
sensor registration and visualization, visual composition and generation of executable
compositions:
1. Registration of OGC services: Demonstrates how OGC services are registered to
the Sensapp platform.
2. Registration of individual sensors: Demonstrates the registration steps for
individual sensors, including editing configuration files and registration through a
Web browser.
3. Search for and listing of registered services and sensors: Demonstrates the
search and display functionalities for locating and listing services and individual
sensors.
4. Visualization of sensors locations on maps: Demonstrates the map localization of
registered sensors.
5. Visualization of historical sensor data on charts: Demonstrates the use of charts
for visualizing historical observation data from individual sensors. The user can
zoom in the chart and select a duration.
6. Visualization of sensor event data on charts: Demonstrates real-time
visualization of events from individual sensors on charts.
7. Composition of services: Demonstrates the BPMN-based composition of
registered SOS, WFS and WPS services.
8. Data mediation: Demonstrates how to specify data flow mapping for the
composed SOS, WFS and WPS.
9. Generation of WSDL and BPEL files for composed services: Demonstrates the
generation of WSDL and BPEL files for the composed BPMN model in the
composition process.
10. Publishing the composed model as a new resource: Demonstrates the registration
of the added-value service as a new resource in the platform, which can then be
further used in compositions or for end-user applications.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Related Work, Summary, and Outlook</title>
      <p>The huge amount of data generated by the increasing number of available sensor
devices requires proper management in terms of abstraction, selection, and
presentation in order to enable better decision making based on real-time sensor data.
Furthermore, development of added-value services based on such data needs to be
faster and smarter. Sensapp aims to address these challenges by providing a sensor
data/service management platform that combines open standards for abstracting
interfaces from proprietary data and protocols, semantic technologies for better search
and discovery, visual composition of services, and different data visualization
techniques.</p>
      <p>A working prototype of Sensapp with the functionalities presented in the
demonstration section has been developed and is currently under performance
evaluation. Some of the components such as the annotation, discovery, and execution
components do not come with a graphical interface yet, but these are planned to be
developed, possible with a close collaboration with the ENVISION project.3 The
source code of Sensapp is planned to be released as open source in the near future. As
part of future work, the platform is planned to be deployed on the cloud and made
available as a service for the wider community.</p>
      <p>
        In enabling better access to real-time sensor data, Sensapp shares some of the
ambitious of other initiatives such as HP Central Nervous System for the Earth
(CeNSE) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], Geospatial Cyberinfrastructure for Environmental Sensing (GeoCENS)
[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], Nimbits [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], Pachube [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], Service Buss [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], or Hourglass [14]. Sensapp’s
focus on open standards as well as both on service developers and end-users, makes it
a sensor integration platform that goes beyond the functionalities and scope of some
of these approaches. Nevertheless, a detailed comparison with these existing
approaches and possible synergies are part of future work.
      </p>
      <p>Acknowledgments. This work is partly funded by the EU projects ENVISION
(FP7249120), ENVIROFI, REMICS, and the Norwegian national project Semicolon II.
3 http://www.envision-project.eu/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>OGC</given-names>
            <surname>Sensor Observation</surname>
          </string-name>
          <article-title>Service (SOS)</article-title>
          , http://www.opengeospatial.org/standards/sos.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>OGC</given-names>
            <surname>Web Feature</surname>
          </string-name>
          <article-title>Service (WFS)</article-title>
          , http://www.opengeospatial.org/standards/wfs.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>OGC</given-names>
            <surname>Web Processing Service</surname>
          </string-name>
          (WPS), http://www.opengeospatial.org/standards/wps.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>OGC</given-names>
            <surname>Sensor Event</surname>
          </string-name>
          <article-title>Service (SES)</article-title>
          , Position paper available at http://portal.opengeospatial.org/files/?artifact_id=
          <fpage>29576</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>W3C</given-names>
            <surname>Resource Description Framework</surname>
          </string-name>
          (RDF), Available at http://www.w3.org/RDF/.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>OMG</given-names>
            <surname>Business Process Modeling Notation</surname>
          </string-name>
          (BPMN), Available at http://www.omg.org/spec/BPMN/2.0/.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <source>OASIS Web Services Business Process Execution Language Version</source>
          <volume>2</volume>
          .0, Available at http://docs.oasis-open.
          <source>org/wsbpel/2</source>
          .0/OS/wsbpel-v2.
          <fpage>0</fpage>
          -OS.html.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. JSR 286:
          <issue>Portlet Specification 2</issue>
          .0, http://www.jcp.org/en/jsr/detail?id=
          <fpage>286</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>HP</given-names>
            <surname>Central</surname>
          </string-name>
          <article-title>Nervous System for the Earth (CeNSE)</article-title>
          , Information available via http://www.hpl.hp.com/news/2009/oct-dec/cense.html.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>Geospatial Cyberinfrastructure for Environmental Sensing (GeoCENS)</article-title>
          , Information available via http://www.geocens.ca/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Nimbits</surname>
          </string-name>
          , Information available via http://www.nimbits.com/.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Pachube</surname>
          </string-name>
          , Information available via https://pachube.com/.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. The Sensor Bus,
          <volume>52</volume>
          North, Information available via http://52north.org/communities/sensorweb/incubation/sensorBus/.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>