DCT Antares SB, Руководство пользователя

Страница: 58 / 238

3.10. REMOTE HOST SOFTWARE
3.9.3 Interacting
TAIP communication must be driven by a timeout-retry mechanism.
3.10 Remote host software
The Antares SB
TM
is designed to interact with Automated Vehicle
Location (AVL) servers which have the ability of interpreting TAIP
messages.
In this document, AVL server, AVL system, AVL host, AVL appli-
cation, remote peer, all make reference to the same thing: A piece
of server-type software which receives and makes some sense of the
Antares SB
TM
reports. It also may have the capability of sending
queries or commands to the unit(s).
Depending on the communication mechanism the unit uses to com-
municate with the AVL server some requirements have to be fulfilled.
See the next sections for information on this.
3.10.1 Working with TCP
In order for the unit to start connecting to an AVL server an IP-type
Destination has to be configured first. The configuration flag for this
Destination must indicate a TCP host. Refer to the Destinations
section on the Configuration chapter.
These are the general requirements for an AVL server working with
units on TCP:
1. The AVL server has to be able to work as a TCP server, as the
Antares SB
TM
is always going to initiate the TCP connection
acting as TCP client. Technically speaking, for this to happen
the AVL server has to be able to open a TCP socket on listening
mode on an available port.
2. The port number has to be the same port number used on the
unit’s IP-type Destination and it has to be clear of any Firewall,
NAT and/or router restriction.
3. The AVL server has to create a new listening TCP socket when-
ever the actual listening socket passes to open state, this to
assure that a new connection coming from another unit is ac-
cepted.
4. The server should close idle open connections after a minimum
time of 1 hour.
56