22.01.2015 Views

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

244 <strong>Military</strong> <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> <strong>Technology</strong>...<br />

The event location is determined on the basis of data received from the GPS module<br />

or by indicating the exact place of the event on an embedded map. Selected<br />

events are grouped into three categories: traffic incidents, traffic difficulties <strong>and</strong><br />

weather difficulties. For events of the first category there is also an opportunity to<br />

submit information about injured people <strong>and</strong> event results.<br />

The application is written in Java, based on the following libraries: Android<br />

SDK, Jain-SIP – SIP protocol implementation for Android [9], Google APIs Addon<br />

[10]– APIs providing the possibility of identify the events location on the builtin<br />

Google map.<br />

The DM receives messages about events from the CM <strong>and</strong> passes them to<br />

suitable subscribed customers. These are public safety services (i.e. the police,<br />

fire brigade, ambulance, etc.) that are called in emergency situations to minimize<br />

the risk of the danger that has been reported.<br />

For the purpose of subscription management the endpoints of the customers<br />

will be stored in a database. They are divided into notification groups which<br />

consist of customers interested in particular event types. For example, information<br />

about the traffic accident with injured persons will be passed to the police, disposer<br />

of rescue ambulance service or emergency call center. When the reported event<br />

is a factory fire <strong>and</strong> the terrain contamination, notification will be passed to the fire<br />

brigade, police, disposer of rescue ambulance <strong>and</strong> sanitary <strong>and</strong> epidemiological<br />

station. The message coming from the CM contains the event description as well<br />

as the name of notification group. This allows the dispatcher to send notification<br />

to group members. The notification message also includes the geographical coordinates<br />

of the event as well as essential information about it.<br />

IV. INSIGMA event ontology<br />

Ontologies at the run-time are used in the situations where the domain model<br />

cannot be fully elaborated during the system development (some domain aspects<br />

are unknown or uncertain) or a kind of reasoning is required. In case of ENS<br />

there is a need to reason about threats <strong>and</strong> dangers related to the traffic detected<br />

in the INSIGMA monitoring subsystem on the basis of the event description. In case<br />

of ENS IEO is used in the RM.<br />

IEO is typical example of run-time ontology model describes specific domain<br />

of knowledge: road events (like car collision, knocking down a pedestrian,<br />

damaged road surface, leakage of dangerous substance, etc.), weather events (like<br />

rain, snow, below freezing temperature) <strong>and</strong> threats related to occurred incident on<br />

traffic (like wet surface danger in case of rain precipitation). On the basis of the event<br />

description (provided by the reporting module) the reasoning mechanism supported<br />

by the event ontology <strong>and</strong> a set of rules enables to classify the event, define required<br />

action of the system <strong>and</strong> then generate notification to public safety services.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!