In RISEN, the HTTP protocol is used, including the
methods described below (as per RFC7231
5
):
GET can be used to request transfer of a current
selected representation for the target resource. It
is the primary mechanism of information
retrieval.
POST requests that the target resource processes
the representation enclosed in the request. It is
typically used as a mechanism to upload
information.
PUT requests that the state of the target resource
be created or replaced with the state defined by the
representation enclosed in the request message
payload.
DELETE requests that the origin server removes
the association between the target resource and its
current functionality.
Each HTTP request produces a status code indicating
if the request was successful or if an error occurred.
The status codes are categorised as follows:
1xx (Informational): The request was received,
continuing process.
2xx (Successful): The request was successfully
received, understood, and accepted.
3xx (Redirection): Further action needs to be
taken in order to complete the request (i.e., the
operation should be retried).
4xx (Client Error): The request contains bad
syntax or cannot be fulfilled (e.g., bad request or
unauthorised request).
5xx (Server Error): The server failed to fulfil an
apparently valid request.
3.3 Message Broker for on-Event
Processing
The publish-subscribe paradigm enables on-event
processing as a result of its capability to push
messages to clients, meeting known criteria. The
publish-subscribe paradigm implies the existence of
different roles:
a publisher, which produces messages,
a subscriber, which consumes messages, and
a message broker, which gathers and distributes
the messages from publishers to subscribers.
The protocol is well suited to disseminate sensor
information, so it is a widely-used protocol in
network-enabled environments. Within the RISEN
Sensor API, the publish-subscribe paradigm
complements the REST architecture in the sense that
the latter is reactive (responds to the client or server
requests) while the former is proactive (on event,
notifies subscribers of new messages).
5
https://tools.ietf.org/html/rfc7231
The lightweight Message Queuing Telemetry
Transport (MQTT), standardised as ISO/IEC PRF
20922 (ISO, 2016), was selected as the message
broker for the Sensor API.
3.4 Sensor Data Model
The RISEN Sensor API also defines the necessary
data models used in information exchange. The data
model includes the “Sensor” group that contains
entities representing sensors and sensor-generated
data. The sensor entity together with other relevant
entities are presented in Fig. 2.
A sensor is represented in the “Sensor” entity.
The "SensorEvent" entity represents the basic
information structure related to dynamic sensor data.
It is extended by: “SensorStatusEvent” entity, that
refers to sensor status information, usually
operational status and battery level; and
“BaseMeasurementEvent” that includes the various
supported sensor measurements (e.g., detection,
category, timeseries data). Thus, two entities, with
several sub-entities associated, "extend" the
SensorEvent, inheriting its fields and adding new
ones to address needed specificities. Thus, a sensor
can generate multiple SensorEvents.
3.5 Deployment Options
The network-enabled architecture selected for the
RISEN System and the Sensor API, supported by
widely adopted and open web-standards, delivers a
high degree of flexibility concerning the deployment
options for the RISEN System in operational
environments.
This subsection presents the deployment options
for the RISEN System, allowing to meet most end-
user scenarios.
3.5.1 RISEN Deployment at the Crime
Scene
In this setting, the RISEN System is transported and
installed at the crime scene. This includes all RISEN
sensors and the 3DA-CSI System. A local network
(wired or wireless) is established to connect all
RISEN modules. The RISEN sensors send
measurements to the 3DA-CSI System. The
investigator accesses the 3DA-CSI System locally,
using a computer or a mobile App. All information is
locally stored in the 3DA-CSI System.