Radio Disable/Enable

From MOTOTRBO
(Redirected from Radio Disable)
Jump to navigation Jump to search

Radio Disable and Enable allows a supervisor to disable a lost or stolen radio. A radio that has been disabled will not complete power-up but will still respond to Radio Enable.

In all systems except Capacity Max

Radio Disable

In MOTOTRBO systems, Radio Disable is configured in the portable and mobile radio CPS. To allow a radio the ability to initiate this function, this option must be enabled in the CPS Menu settings. To permit (or prevent) a given radio from decoding and responding to this command, this option must be configured in the CPS Signaling Systems settings.

Since the ability to disable a user could be misused, it is suggested that only supervisors be granted the ability to initiate a Radio Disable.

Radio Enable

Radio Enable is also configured in the portable and mobile radio CPS. To allow a radio the ability to initiate this function, this option must also be enabled in the CPS Menu settings.

Since the ability to disable a user could be misused, it is suggested that only supervisors be granted the ability to initiate a Radio Disable.

In Capacity Max

Stun and Revive

A dispatch application[1][2] connected to the system or a radio, with the capability enabled in the SAC, can initiate a Stun or Revive command. The Capacity Max infrastructure executes the Stun and Revive procedures on the control channel. The target radio must be on the control channel and be within RF range for this action to be completed successfully. The Capacity Max system supports Stun/Revive with or without Authentication.

A dispatch application or radio (with the capability enabled in the SAC) can also deny a radio the access to services by sending an Over-The-Air command to the radio. A stunned radio does not request or receive any user-initiated services on a Capacity Max system, where it was stunned. However, a stunned radio does roam from one site to another, register, authenticate (if required), and execute a received revive command. A stunned radio continues to send the location updates, receive location request, and can be remotely monitored.

Stunning a radio on a system does not change the radio’s behavior on other systems hence Stun is a system wide and not a radio wide.

Disabling a radio using SAC and stunning a radio has a very similar effect. The radio cannot initiate or receive a call. The main advantage of Stun is that the radio continues to send location updates and therefore a lost radio can be tracked. Another main advantage of Stun is the radio’s access to the system is disabled immediately. The main disadvantage of Stun is that a radio can be stunned only if the radio is powered on and is in coverage area of the system.

When Stun/Revive authentication option is enabled, on reception of Stun/Revive command, the infrastructure authenticates the initiating radio and the target radio authenticates the infrastructure. Authentication is supported in the system by sending a Challenge, receiving a response and validating the response before executing the command. The authentication Key used for Stun/Revive of a radio is the same Key used for the authentication of the radio during registration.

A radio is denied access to all user-initiated services for the system on which it was stunned. However, roaming, registration, authentication, stun/revive services remain active. The radio can be remotely monitored, and continues to send the location updates while stunned. The radio can also receive new LRRP requests while stunned.

A radio can be revived by doing the following:

  • Either sending (Over-The-Air) a “Revive” command to the radio
  • Reprogramming the radio over USB connection using Radio Management

The radio cannot be revived by power cycling or by Over-The-Air Programming (OTAP).

Kill

Only a dispatch application can Kill a radio. A radio cannot initiate a request to kill another radio. Radio Kill is intended to make the radio unusable when it is lost or stolen. A killed radio disables all its functionalities across all its personalities, except that the radio can be powered on and off. In terms of programming via a cable, the radio accepts only those commands, which are essential for unkilling the radio. This implies that a code-plug or firmware cannot be programmed into a killed radio unless it is unkilled first.

While powered on, the radio indicates its Killed state, however it does not respond to the keypad, channel knob and does not make over-the-air transmission and reception. A killed radio cannot be revived from the Kill state by any over-the-air message.

On receiving the Kill command, the radio always authenticates the network using the provisioned Authentication Key. The same Authentication key is used for registration, Stun/Revive, and Kill. Authentication is not optional for Kill and if an Authentication Key is not provisioned, then the default Authentication Key is used. On successful authentication, the radio gets permanently disabled (Killed). When a Killed radio is powered on, it provides an indication. From the indication, radio user/dealer can easily know that the radio is killed.

A killed radio can be unkilled by Motorola.

The authentication key belongs to the owner of the radio. This means that only the owner can un-kill a killed radio. This rule does not apply if the default Authentication Key is used, therefore it is recommended to provision a Authentication Key when enabling Kill functionality.

See Also

Radio Management

References

  1. https://www.motorolasolutions.com/en_xu/application-catalog/trbonet-plus.html
  2. https://www.motorolasolutions.com/en_xu/application-catalog/smartptt-plus.html