Bio-OS Data Processing: data server

The Bio-OS Server allows remotely measured bio signal data to be uploaded into a database. The server supports multiple sensing devices (data inputs) and so allows aggregation of bio data from many different sources (users, devices etc). It has a ‘Trigger Logic Editor’ which allows system administrators (including artist and scientific end-users) to edit the set of rules held in the trigger database. These triggers cause actions to automatically occur when changing bio data values meet particular predefined conditions. For example, an action might occur if a person’s heart rate is above 90 bpm and they are in a particular location.

The Server also has a ‘Data Injector’ which allows bio data readings to be manually inserted into the Data Storage Server through a simple web page. This might be for testing and experimentation purposes, for real time intervention during a live study/activity or simply for the manual storage of non-sensed bio values.

The Data Storage Server allows remotely measured bio signal data to be uploaded into the Subject Bio Database. The server supports multiple sensing devices and so allows aggregation of bio data from many different sources (users, devices etc). An open webservice mechanism has been used to create the Data Storage Server so that additional data sources can be easily integrated. In order to store a bio data value in the system, a request must be made to the server for the “store-data.php” page, passing as parameters:- The id of the subject (person) being sensed- The name of the bio signal being uploaded- The millisecond timestamp at which the bio signal reading was taken- The value of that bio signal

This should take the form of:  http://server/store-data.php?id=<subject>&<biosignal>@<timestamp>=<value>

For example, the following request stores the BPM of the subject “dave” at timestamp 1316510004461 as the value 70 bpm:• http://server/store-data.php?id=dave&BPM@1316510004461=70

In the interests of efficiency, multiple data values can uploaded to the server in a single request by chaining values together with &• http://server/store-data.php?id=<subject>&<biosignal>@<timestamp>=<value>&<biosignal>@<timestamp>=<value>…
For editing triggers:• http://79.170.44.128/i-dat.org/datalab/mediator/list-triggers.php
For storing data value:• http://79.170.44.128/i-dat.org/datalab/mediator/store-data.php
Log of changed data values:• http://79.170.44.128/i-dat.org/datalab/mediator/data/username/log.txtFor example• http://79.170.44.128/i-dat.org/datalab/mediator/data/leesphone/log.txt

The server is now common for all users, but we will look into replicating the system for each users.

Trigger Logic Editor:

The Trigger Logic Editor allows system administrators (including artist and scientific end-users) to edit the set of rules held in the trigger database. These triggers cause actions to automatically occur when changing bio data values meet particular predefined conditions. For example, an action might occur if a person’s heart rate is above 90 bpm and they are in a particular location. Each trigger has:- Conditions: when to fire the trigger- Trigger Actions: what to do when the conditions are met- Detrigger Actions: what to do when the conditions are no longer being met.

Guide to writing triggers conditions
The conditions for the trigger are logical triples consisting of:    parameter comparator value
For example:  BPM > 70  GSR <= 15

The current list of available parameters are:- TMP: the subject’s temperature- BPM: the subject’s pulse rate- GSR: the subject’s galvanic skin response- lat: the subject’s current latitude- long: the subject’s current longitude- BR: the subject’s current breathing rate- id: the subject’s unique identifier

The id parameter allows us to create user specific triggers, so that actions can be triggered by the bio data parameters of a particular individual. The id parameter is of the form:  Usersphone
For example:  Hannahsphone  Simonsphone  etc

For further information see the Bio-OS Help Guide.