MCU_Configuration messages: The MCU must
be able to modify sensor subsystem operative
parameters in order to adapt the SENSNET
performance to a changing environment, or to
carry out system updates.
MCU_Management messages: For fulfilling the
second level classifier input constrains, S-MCU
must be able to ask the IR, the Ku-band
radar, and the radiometric SAR sub-systems for
additional information about specific targets.
SENSOR_Data Fusion messages: Detection and
tracking messages will be generated in each of
the nodes belonging to sensor networks
responsible of surveillance tasks for target
detection and tracking: PBR, NOISE RADAR,
Ku-band radar, and RFID. These data will be fed
to the data-fusion and/other first classifier stages,
following the architecture presented in Figure 6.
A common data format must be defined for this
type of messages in order to facilitate the data
fusion process
.
SENSOR_2LClass messages: As answers to the
MCU requests, IR and Ku-band radar
subsystems must provide additional information
related to detections classified as possible
humans.
In order to reduce the required communication
network bandwidth, the direct transmission of the
signals acquired by each node must be avoided. The
use of array antennas and digital beamforming
techniques, impose the use of a dedicated data link
for each single radiating element of each antenna
array, giving rise to an unaffordable transmission
bandwidth if raw data is transmitted to the S-MCU
or to central nodes designed for the processing of
raw data acquired by the nodes of a specific sub-
system (sensor network). Local processing also
enhances the robustness of the SENSNET, because
if one node is attacked, the rest of the nodes will
continue working, and could be reconfigured for
guaranteeing the physical protection of the
infrastructure. So SENSNET will be a distributed
sensor network.
Nodes belonging to sensor networks responsible
for target detection and tracking will perform
detection and tracking tasks and will generate local
SENSOR_DATA_Fusion messages that will be sent
to the S-MCU, more specifically, to the multisensor
detector and tracker. This architecture also improves
real time processing capabilities. As an answer to
MCU_Management messages, the nodes belonging
to sensor networks responsible of providing
additional information to the second level classifier,
will generate local SENSOR_2LClass messages.
6.2 Sensors Data Format
The multisensor detector and tracker module uses
the detection and tracking data generated by each
sensor that belongs to GB-SAR, PBR, and NOISE
radar sensor networks. As additional information,
data provided by the RFID network, mainly
consisting of identification and locations tags, are
also analysed in this data fusion stage in order to
improve system surveillance capabilities.
To facilitate the fusion task, a common data
format shall be defined for monostatic sensors, as
well as for bi/multi-static ones in the Cartesian
domain.
In Table 2-Table 6, data fields of the
SENSOR_Data_Fusion messages are defined:
TypeID defines the type of message.
sourceID identifies the sensor network to which
the node belongs to (the type of node).
rxUid identifies each single node.
trackID. Each SENSNET node is capable of
performing radar observations in either the
Range/Doppler or Cartesian plane. By
associating consecutive observations the node
assigns unique track ID's to target detections.
timeStamp. All nodes are required to give a time
stamp in epoch time, associated to each track ID,
making necessary a clock signal distribution
among the all SENSET nodes.
To accommodate outputs from many different
types of systems, a selection of possible fields is
proposed. The column titled Optional indicates
fields that might not be strictly needed for the fusion
task, or that are redundant if other measurement
fields can be provided, indicating for which sub-
systems that field is required.
IR and Ku-band radar nodes must perform local
classification tasks to distinguish between persons,
animals and others. SENSOR_2LClass messages
will contain the fields defined in Table 2, and
specific fields related to image quality and
classification accuracy (Table3) and target features.
The final data fields will be defined when the signal
processing solutions for classification will be
designed. Specific fields could be defined for IR
nodes, because the transmission payload associated
to IR images is clearly lower than radar ones.