Mobile Terminal

Module description/purpose

The main purpose with Mobile Terminal module is provide possibility to administrate and store information of a mobile terminal.

A mobile terminal is a telematics which can be installed on e.g. a watercraft or a vehicle to keep track of these position, speed, course and status. A mobile terminal sends its position data by transmit the data to an addressed Land Earth Station (LES), via a satellite. Because it can be different types of telematics installed in the vessels, therefore requires different types of plugins to communicate with the LES.

In UVMS-project, two plugins are completed implemented. One is support a mobile terminal type of Imarsat C and the other is for type of Iridium. All position data that comes from the plugin goes first via the Exchange module then sends it forward to the Rules module to verify the position data, and if the position data is valid, it will be sent to Movement module. Otherwise an alarm will be created by the Rule module to notify an error has occurred. See figure 1 below for information about the communication and data flow.

A mobile terminal of type INMARSAT C must have at least one channel configured to be able to communicate with LES. And the channel must have a unique combination of DNID (Data Network ID) and Member number, which defines exactly where the information should be sent to or retrieve from LES.

From Mobile Terminal module you can send three different types of poll; manual poll, configuration poll and sampling poll to the mobile terminal.

  • Manual poll is a command sends to the mobile terminal to request its latest position.
  • Configuration poll is a command send to mobile terminal to update the configuration of a mobile terminal.

Sampling poll is a command sends to the mobile terminal to request it to send a set of positions which have been saved in the mobile terminal.

Nexus artifacts and dependencies

Main moduleDatabase module
<!-- Integration dependency -->

Github App:
QA Summary App:
CI location App:
Project Site reports App:
Tattletale report :

Module dependencies

AuditLog all operations which have been executed in all UVMS-modulesAudit
UserAuthentication operations and access managementUser
ExchangeGateway provides communication ability with other modules or artifacts beside UVMSExchange

JMS Queue Dependencies

NameJNDI name exampleDescription
UVMSMobileTerminalEventjava:/jms/queue/UVMSMobileTerminalEventRequest queue to MobileTerminal service module
UVMSMobileTerminaljava:/jms/queue/UVMSMobileTerminalResponse queue to MobileTerminal module
UVMSAuditEventjava:/jms/queue/UVMSAuditEventRequest queue to Audit service module
UVMSUserEventjava:/jms/queue/UVMSUserEventRequest queue to User service module
UVMSExchangeEventjava:/jms/queue/UVMSExchangeEventRequest queue to Exchange service module


NameJNDI name example

Liquibase scripts

Related Repositories