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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3: <strong>Information</strong> <strong>Technology</strong> for Interoperability <strong>and</strong> Decision...<br />

241<br />

sors. It allows reporting of accidents <strong>and</strong> other events directly from users located<br />

outside the monitoring area.<br />

The idea of ENS was to apply the IEO for automatic classification of events<br />

<strong>and</strong> threats. On the basis of the A-Box ontology model <strong>and</strong> description of the event<br />

delivered by the reporting module, the server module is able to automatically<br />

classify the event to a certain type <strong>and</strong> generate notification for necessary public<br />

safety services. ENS is also useful as a source of dynamic data that, further on,<br />

can be presented on the road map as potential traffic difficulties or obstacles (e.g.<br />

information about the accidents) <strong>and</strong> used to compute routes taking into account<br />

threats <strong>and</strong> dangers <strong>and</strong> alerting of INSIGMA users.<br />

Application of the IEO in the ENS is well suited to the system exploitation<br />

phase when ontology is used to provide reasoning <strong>and</strong> automation of the processes.<br />

It is very important to get rid of “the man in the loop” <strong>and</strong> support decision process<br />

in terms of defining necessary actions in case of an accident or other dangerous<br />

situation. On the basis of the event description the reasoning module defines threats<br />

related to the observed situation <strong>and</strong> necessary actions to be taken by emergence<br />

services (e.g. calling the ambulance, calling the fire brigade, etc.).<br />

III. Event Notification Service<br />

The ENS was implemented as a set of functional software modules in the C<br />

ommunications&<strong>Information</strong> Infrastructure Laboratory of <strong>Military</strong> Communication<br />

Institute. The ENS allows creation, relaying <strong>and</strong> processing of short messages<br />

containing formatted information about events spotted by a user. The results<br />

of processing the messages is stored in Events Repository (ER) for further use [3].<br />

The ENS infrastructure is composed of the notification module <strong>and</strong> reporting<br />

module (see Fig. 1). Notification module is used to collect <strong>and</strong> process messages from<br />

users, extract appropriate information <strong>and</strong> pass it to the Reasoning Module (RM).<br />

The output from RM is then fed into Message Dispatcher (MD) which notifies users<br />

specified in the subscription list. The client modules provide graphical user interface<br />

with formatted fields to fill in information about an event. The client module also<br />

allows creating of structured messages <strong>and</strong> it h<strong>and</strong>les authentication of the user.<br />

The high level view of ENS model is presented in the Figure 1. The implementation<br />

of ENS is based on the Session Initiation Protocol enhancements for Instant<br />

Messaging – SIMPLE [4]. The SIMPLE messages are used as an application level<br />

transport protocol for relaying user generated information about observed <strong>and</strong><br />

reported events. The information is structured according to high-level ontology<br />

dedicated for INSIGMA system [5]. The main reason behind the use of SIMPLE were<br />

requirements for identification, registration <strong>and</strong> authentication of users. The SIP<br />

Uniform Resource Identifier are used as an identification whereas mechanisms<br />

for registration <strong>and</strong> authentication are defined in the SIP RFC [6]. Localisation<br />

of a user is an additional benefit from using SIP architecture.

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

Saved successfully!

Ooh no, something went wrong!