Motorola V186 User Manual - Page 142

Encryption in the STS/ToolBox MDLC Driver, MDLC Encryption Tool.

Get Motorola V186 - Cell Phone - GSM PDF manuals and user guides View all Motorola V186 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 142 highlights

Communications When an RTU is first configured and stars up (cold start in MOSCAD and MOSCAD-L RTUs), the key index is set to '0' (non-encrypted mode). Encryption is then activated by changing the Active Key index to a number other than '0' (1-9). This is done using the MDLC Encryption Tool. The replacement of the encryption key is initiated by the MDLC Encryption tool. Successful replacement of the active key requires that all RTUs in the system be timesynchronized by the IP Gateway. To compensate for possible time drifts during a transition from one encryption key to another, there is a configurable time interval where both the old and new keys are valid. Accept old and new keys for RX. Switch to new key Uses old key for TX. TE1 Uses new key for TX. TE2 Uses new key for TX. Accept new key for RX. time TE1 is the interval, in seconds, which represents the possible time drift. Note: It is recommended that at least one non-encrypted IP Gateway (FIU) will be connected to the system to enable communication with non-encrypted RTUs when necessary Encryption in the STS/ToolBox MDLC Driver Once KF is defined in the MDLC Encryption Tool, it can be set as the Active File in the STS/ToolBox MDLC driver The Active Key Index is then set to the same index (1-9) of the Active Key of the system. This enables the STS or ToolBox to exchange data with encrypted RTUs. In the event that the STS/ToolBox must send a non-encrypted message, (to an RTU that performed a cold restart), the encryption should be deactivated by setting the MDLC driver Key Index to 0. 138

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
Communications
When an RTU is first configured and stars up (cold start in MOSCAD and MOSCAD-L
RTUs), the key index is set to ‘0’ (non-encrypted mode). Encryption is then activated by
changing the Active Key index to a number other than ‘0’ (1-9). This is done using the
MDLC Encryption Tool.
The replacement of the encryption key is initiated by the MDLC Encryption tool.
Successful replacement of the active key requires that all RTUs in the system be time-
synchronized by the IP Gateway.
To compensate for possible time drifts during a transition from one encryption key to
another, there is a configurable time interval where both the old and new keys are valid.
TE1
TE2
time
Switch to
new key
Uses old
key for TX.
Uses new
key for TX.
Uses new key for
TX.
Accept new
key for RX.
Accept old and
new keys for
RX.
TE1 is the interval, in seconds, which represents the possible time drift.
Note: It is recommended that at least one non-encrypted IP Gateway (FIU) will be
connected to the system to enable communication with non-encrypted RTUs when
necessary
Encryption in the STS/ToolBox MDLC Driver
Once KF is defined in the MDLC Encryption Tool, it can be set as the Active File in the
STS/ToolBox MDLC driver The Active Key Index is then set to the same index (1-9) of
the Active Key of the system.
This enables the STS or ToolBox to exchange data with
encrypted RTUs.
In the event that the STS/ToolBox must send a non-encrypted message, (to an RTU that
performed a cold restart), the encryption should be deactivated by setting the MDLC
driver Key Index to 0.
138