E F Johnson Company 2425M70 Benutzerhandbuch
8-15
Secure Communication (Encryption)
8.6
Radio Setup For Encryption
The following radio setup is required for encryption regardless of whether OTAR is used:
Options Enabled - The desired encryption type must have been enabled at the factory
(DES, DES-OFB, AES). To determine what options are enabled, use Armada.
(DES, DES-OFB, AES). To determine what options are enabled, use Armada.
The following are set through Armada. Please refer to the Armada Programming Manual
or Help for more information.
or Help for more information.
PID/SLN Mode - If the SLN mode is used, the Keys Table must be programmed also.
Infinite Key Retention - This parameter enables the option to store keys permanently
in memory (see Section 8.2.3).
in memory (see Section 8.2.3).
Erase Keys On Keyset Change - This parameter to erase keys when changing keysets
if the SLN mode is selected and more than one keyset is used (see Section 8.2.5).
if the SLN mode is selected and more than one keyset is used (see Section 8.2.5).
Program Channel/Group PIDs and Encryption Type - With conventional analog
calls, this information is programmed on the channel screen. With other types, it is
programmed in the talkgroup list selected on the system screen. In addition, with
conventional digital calls, the group programming can be overridden on the channel
screen (see Section 8.4.1). Additional PIDs for special calls can also be specified on the
system screen for digital and trunked calls.
calls, this information is programmed on the channel screen. With other types, it is
programmed in the talkgroup list selected on the system screen. In addition, with
conventional digital calls, the group programming can be overridden on the channel
screen (see Section 8.4.1). Additional PIDs for special calls can also be specified on the
system screen for digital and trunked calls.
Note
The encryption type is not selectable on digital channels because the AES/DES mode is
determined by the key type loaded, not by Armada.
determined by the key type loaded, not by Armada.
Note
Key Loss Key (KLK), offered by Motorola, does not erase the UKEK which allows the
radio to be rekeyed by the KMF remotely. By not erasing the UKEK, the KLK does not
meet TIA standards and is no longer FIPS 140-2 certified.
radio to be rekeyed by the KMF remotely. By not erasing the UKEK, the KLK does not
meet TIA standards and is no longer FIPS 140-2 certified.
The current EFJohnson Technologies Viking VM600 mobile radios support OTAR.
However, an RSI, UKEK and other information must be programmed as described in the
next section.
However, an RSI, UKEK and other information must be programmed as described in the
next section.
8.6.0.1
Motorola Third Party RNC Registration
The Viking VM600 supports dynamic data registration. However, if desired, the radio can
be programmed to perform Third Party data registration instead of dynamic registration on
the OTAR and Data parameters page. If Third Party registration is selected, the radio may
must be manually registered on the Motorola RNC Console by entering the following
command:
be programmed to perform Third Party data registration instead of dynamic registration on
the OTAR and Data parameters page. If Third Party registration is selected, the radio may
must be manually registered on the Motorola RNC Console by entering the following
command:
LCRD 03 06 00 1234 7F xx xx xx 0A 0A 00 07 00 yy
Where, “xx xx xx” is the hex value of the Digital Unit ID entered by Armada. Refer to the
console documentation for the value of “yy” or use “00”. This registration needs to be
done only once.
console documentation for the value of “yy” or use “00”. This registration needs to be
done only once.
Draft 4/29/2014