Military Communications and Information Technology: A Trusted ...
Share Embed Flag
Download ePaper

Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...

wil.waw.pl
22.01.2015 Views

242 Military Communications and Information Technology... Figure 1. Model of the notification service components. Abbreviations: CM – Communications Module, SAS – SIP Application Server, ER – Events Repository The detailed structure of message was defined in [3] and consists of: • type of event (based on high level ontology), • time of event (based on real-time clock in the user terminal or manually entered by a user), • geo-localisation of event (acquired from embedded GPS receiver or set manually by a user on the touchable background map), • optional information about the event, such as a number of injured persons, • optional information about observed results of event, • the user or equipment identifier. The message with event information is encoded using eXtensible Markup Language (XML). The XML data is then put into the SIP MESSAGE protocol data unit as a payload. The encoding of information has a following structure: . . . The notification module (server part) consists of the SIP proxy server used to receive messages from the client, Communications Module (CM) that invokes

Chapter 3: Information Technology for Interoperability and Decision... 243 the RM responsible for reasoning about the event and MD that forwards the notifications to subscribed public safety services. The implementation of SIP server for ENS is based on the SIP Express Router software (SER) [7] and its capability to interface with external software modules through the inter-process communication mechanisms. The SER was used because of its flexibility due to its high modularization and programmability of core functions. The developed CM provides the interface between SER and RM. It basically works as a translator of SIMPLE messages to the remote procedure calls based on Web Service technology. The translator was needed because of requirements of RM software, which provides Web Service interface only. Additionally the CM processes data about events and feeds them to the ER. The CM was implemented as a standalone program linked with “libpq” library available in the PostgreSQL package [8]. ER uses PostgreSQL 8.4.1 relational database system. The system environment for notification module is provided by Slackware Linux 12.0 operating system. The more detailed description of ENS service can be found in [3]. Event reports are prepared on a mobile terminal running dedicated client application. The client software provides graphical user interface (see Fig. 2) which helps to describe the event by assigning observed circumstances to the predefined types (e.g. event results like leakage of dangerous substance, person jammed in the vehicle, etc.). Figure 2. Graphical user interface view ENS client was created as an application dedicated for the Android platform. User with the graphical interface indicates: event location, its type and time of occurrence.

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

Figure 1. Model of the notification service components. Abbreviations:<br />

CM – <strong>Communications</strong> Module, SAS – SIP Application Server, ER – Events Repository<br />

The detailed structure of message was defined in [3] <strong>and</strong> consists of:<br />

• type of event (based on high level ontology),<br />

• time of event (based on real-time clock in the user terminal or manually<br />

entered by a user),<br />

• geo-localisation of event (acquired from embedded GPS receiver or set<br />

manually by a user on the touchable background map),<br />

• optional information about the event, such as a number of injured persons,<br />

• optional information about observed results of event,<br />

• the user or equipment identifier.<br />

The message with event information is encoded using eXtensible Markup<br />

Language (XML). The XML data is then put into the SIP MESSAGE protocol data<br />

unit as a payload. The encoding of information has a following structure:<br />

<br />

<br />

<br />

<br />

<br />

. . .<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

The notification module (server part) consists of the SIP proxy server used<br />

to receive messages from the client, <strong>Communications</strong> Module (CM) that invokes

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!