Справочник Пользователя для E F Johnson Company 2425311
SECURE COMMUNICATION (ENCRYPTION)
62
programming can be overridden on the channel
screen (see Section 11.3.3). 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 chan-
nels because the AES/DES mode is determined
by the key type loaded, not by PCConfigure
programming.
screen (see Section 11.3.3). 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 chan-
nels because the AES/DES mode is determined
by the key type loaded, not by PCConfigure
programming.
Currently, EFJohnson 5100 portables and 5300
mobiles that meet the following requirements support
OTAR:
OTAR:
Software Version Number - The 5100 must have
firmware (operating software) version number 1.5.0/
2.0/3/0 or higher, and the 5300 must have firmware
2.0/3.0 or higher or ARM code 1.16.0 or higher and
DSP code 1.32.0 or higher. The software version
number is briefly displayed when power is turned on.
It can also be determined using the PCConfigure
programming software by selecting the Transfer >
Read Version Info from Radio menu parameter.
firmware (operating software) version number 1.5.0/
2.0/3/0 or higher, and the 5300 must have firmware
2.0/3.0 or higher or ARM code 1.16.0 or higher and
DSP code 1.32.0 or higher. The software version
number is briefly displayed when power is turned on.
It can also be determined using the PCConfigure
programming software by selecting the Transfer >
Read Version Info from Radio menu parameter.
Programming - An RSI and UKEK and other infor-
mation must be programmed as described in the next
section.
mation must be programmed as described in the next
section.
11.5.2 ADDITIONAL SETUP FOR OTAR
Additional PCConfigure Programming For OTAR
The following parameters must be programmed
for OTAR operation in addition to those in Section
11.5.1 (PCConfigure Version 1.17 or later is required).
11.5.1 (PCConfigure Version 1.17 or later is required).
1. On the Radio Wide Conventional screen, program
the Digital Unit and Unit RSI IDs. The Unit RSI
ID can be set to the Digital Unit ID only, but later
can be changed by the KMF or keyloader if desired.
Note these two numbers.
ID can be set to the Digital Unit ID only, but later
can be changed by the KMF or keyloader if desired.
Note these two numbers.
2. On the Per System Conventional screen, select
OTAR Enabled = On and Data Registration
Enabled = On. When data registration is enabled,
the radio registers with the data system on a channel
change.
Enabled = On. When data registration is enabled,
the radio registers with the data system on a channel
change.
3. Also on the Per System Conventional screen, set the
OTAR Time Out Time. When rekeying is
requested by the radio (OTAR Rekey option button
pressed or menu selected), this setting determines
how long the radio waits for a response from the
KMF. Times of 20-180 seconds can be programmed,
and the default is 30 seconds.
pressed or menu selected), this setting determines
how long the radio waits for a response from the
KMF. Times of 20-180 seconds can be programmed,
and the default is 30 seconds.
Motorola RNC Registration (If Required)
The 5100/5300 may not support Motorola
dynamic data registration. Therefore, each radio may
need to be manually registered on the Motorola RNC
Console by entering the following command:
need to 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 the PCConfigure software. Refer to
the console documentation for the value of “yy” or use
“00”. This registration needs to be done only once.
the console documentation for the value of “yy” or use
“00”. This registration needs to be done only once.
Programming By Keyloader
The following are the minimum parameters that
need to be programmed in the radio to perform OTAR.
It is not necessary to program a TEK to perform
OTAR. If the radio does not contain a TEK, the KMF
initiates a warm start-up sequence in which a tempo-
rary TEK is transferred to the radio to perform the key
transfer.
It is not necessary to program a TEK to perform
OTAR. If the radio does not contain a TEK, the KMF
initiates a warm start-up sequence in which a tempo-
rary TEK is transferred to the radio to perform the key
transfer.
1. UKEK - This key normally has SLN (CKR) 61440
and Key ID 62880 (F5A0 hex). Create a key (either
AES or DES type as required) and download it to
the radio.
AES or DES type as required) and download it to
the radio.
2. RSI - This is normally initially the same as the P25
Unit ID and is programmed by the PCConfigure
software as described in Section 11.5.1. Therefore,
the RSI should not need to be loaded if it is the first
time the radio is being set up for OTAR or if the
radio dumps keys due to long-term battery discon-
nect. However, it may need to be loaded if the radio
is manually deleted from the KMF and then recre-
ated since the message number must be reset to 0
(the Load Target RSI command resets the message
number to 0).
software as described in Section 11.5.1. Therefore,
the RSI should not need to be loaded if it is the first
time the radio is being set up for OTAR or if the
radio dumps keys due to long-term battery discon-
nect. However, it may need to be loaded if the radio
is manually deleted from the KMF and then recre-
ated since the message number must be reset to 0
(the Load Target RSI command resets the message
number to 0).
3. KMF RSI - This RSI is normally 9,999,999 and
should not need to be loaded since it defaults to this
number.
number.