MTP8500Ex Product Information Manual

Intellectual Property and Regulatory Notices

Copyrights

Motorola Solutions products described in this document may include copyrighted Motorola Solutions computer programs. Laws in the United States and other countries preserve for Motorola Solutions certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola Solutions computer programs contained in Motorola Solutions products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola Solutions. No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without the prior written permission of Motorola Solutions, Inc.

Trademarks

MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners.

License Rights

The purchase of Motorola Solutions products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola Solutions, except for the normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a product.

Open Source Content

This product may contain Open Source software used under license. Refer to the product installation media for full Open Source Legal Notices and Attribution content.

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive

The European Union's WEEE directive requires that products sold into EU countries must have the crossed out trash bin label ?️ on the product (or the package in some cases). As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries should not dispose of electronic and electrical equipment or accessories in household waste. Customers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection system in their country.

Disclaimer

Please note that certain features, facilities, and capabilities described in this document may not be applicable to or licensed for use on a specific system, or may be dependent upon the characteristics of a specific mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola Solutions contact for further information. © 2021 Motorola Solutions, Inc. All Rights Reserved

Chapter 1: Product Overview

1.1 MTP8000Ex Series Overview

The MTP8500Ex radio sets a new standard in TETRA ATEX radios by providing safe, reliable, and efficient communications in hazardous environments. The radio allows users to work in areas with potentially explosive gases or chemical vapors, flammable liquids, or combustible dust. The MTP8000Ex Series TETRA ATEX radios deliver powerful audio, enhanced coverage, extended battery life, greater ruggedness, advanced ergonomics and increased usability.

Figure 1: MTP8500Ex - An image displaying the MTP8500Ex radio.

The MTP8500Ex portable radio delivers powerful features and user benefits in a simplified keypad design suited for operation while wearing heavy gloves. Its ergonomic design enables easy operation by offering innovative features such as a top display, a T-Bar shaped grip, and a color display. The intuitive user interface with dual displays makes it easier to see emergency notifications, talkgroup status, or battery condition. The battery life of 16 hours ensures that the radio is ready for a longer shift in the event of emergencies or unplanned situations. With a receiver sensitivity of -109 dBm (typical) as well as Class 3L and Class 4 power output options, the MTP8000Ex Series radios provide greater coverage and enhanced in-building performance. The LED coverage indicator at the base of the antenna alerts the user when coverage is poor. Secure Bluetooth Wireless technology is integrated into the radios, ensuring that a range of wireless accessories and collaborative devices can be securely and reliably paired with the radios.

The MTP8000Ex Series radios are optimized for excellent audio performance in all types of noisy environments. Audio through both the speaker and accessories is clear against the loudest background noise, even at full volume. The MTP8000Ex Series radio specifications are available at https://www.motorolasolutions.com/mtp8000ex.

1.2 Customer Programming Software

For information about Customer Programming Software, refer to the TETRA Terminals CPS Plus Start-up User Guide.

Chapter 2: Services and Features

Motorola Solutions offers a wide range of services and features to meet the requirements of mission-critical communications.

2.1 System Support

The radio operates on Dimetra IP 5.x, 6.x, 7.x and 8.x releases, and Dimetra IP Compact. It also operates on previous versions of Dimetra from Release 3.8 onwards. The radio is designed to operate optimally on the Dimetra IP system. It operates properly on all SwMIs that comply with the list of IOP features defined by the TETRA And Critical Communications Association (TANDCCA). Official IOP certificates can be downloaded from the TANDCCA web page at http://www.tandcca.com/interoperability/interoperability-certificates-and-testreports/.

TMO TIP:

• TIP Core TTR 001-01, TIP – Part 1: Core
• TIP SDS TTR 001-02, TIP – Part 2: Short Data Service
• TIP DGNA TTR 001-03, TIP – Part 3: Dynamic Group Number Assignment
• TIP Auth TTR 001-04, TIP – Part 4: Authentication
• TIP PD TTR 001-05, TIP – Part 5: Packet Data
• TIP AI Migration TTR 001-06, TIP – Part 6: Air Interface Migration
• TIP FSSN TTR 001-07, TIP – Part 7: Fleet Specific Short Number
• TIP SS-AL TTR 001-09 TIP – Part 9: Ambience Listening
• TIP E2EE TTR 001-10, TIP – Part 10: End to End Encryption (Selling option)
• TIP AIE TTR 001-11 TIP – Part 11: Air Interface Encryption
• TIP SI TTR 001-12, TIP – Part 12: Service Interaction
• TIP Enable/Disable TTR 001-13 TIP – Part 13: Enable or Disable
• TIP LIP TTR 001-19, TIP – Part 19: Location Information Protocol
• TIP CF TTR 001-20, TIP – Part 20: Call Forwarding
• TIP Callout TTR 001-21, TIP – Part 21: Call Out

DMO TIP:

• TIP DCore TTR 002-01, DMO TIP – Part 1: DMO Core
• TIP DGate TTR 002-02, DMO TIP – Part 2: DMO Gateway
• TIP DRep TTR 002-03, DMO TIP – Part 3: DMO Repeater Type 1
• TIP DE2EE TTR 002-04, DMO TIP – Part 4: DMO End to End Encryption
• TIP DAIE TTR 002-05, DMO TIP – Part 5: DMO Air Interface Encryption

2.2 Trunked Mode Operation

Trunked Mode Operation (TMO) requires switching and management infrastructure. TMO enables various voice and data communication types, such as group calls and short data service messages. TMO also enables access to infrastructure-related features like packet data.

Figure 2: Trunked Mode Operation - A diagram illustrating Trunked Mode Operation.

2.3 Direct Mode Operation

Direct Mode Operation (DMO) is a mode of simplex operation where radios communicate directly without the need for a network.

Note: For users of DMO mode, it is recommended to apply DMO SCK for data confidentiality.

Figure 3: Direct Mode Operation - A diagram illustrating Direct Mode Operation.

2.4 Repeater Mode

Note: This is a Software Selling Feature.

The Repeater Mode provides repeater connectivity between radios operating in DMO Mode. Only radios on the same talkgroup can communicate with each other through the repeater. Only one repeater can be used in one setup; chain repeaters are not allowed.

Figure 4: Repeater Mode Operation - A diagram illustrating Repeater Mode Operation.

A DMO repeater extends the DMO range by retransmitting received information from one radio to another, including group calls, private calls, and data on a given frequency. The repeater sends a presence signal periodically on a free channel to allow other radios to synchronize on a given frequency. Communication between radios and the DMO repeater is logically divided into two links: the "master link" for communication between the Master radio and the DMO repeater, and the "slave link" for communication between the slave radio and the DMO repeater. The master is the radio initiating and transmitting the voice or data, and the slave is the radio receiving it. Users can enable Call Monitoring to hear transmissions and Interactive Repeater to hear and participate in transmitted calls. For more information, refer to DMO Gateway and Repeater Communication on page 18.

2.5 Gateway Mode

Note: This is a Software Selling Feature.

The Gateway Mode allows a radio to function as a gateway, providing connectivity among radios operating in DMO and TMO Modes.

Note: Only one gateway can be used in one setup. A gateway and a repeater cannot coexist in the same setup.

Figure 5: Gateway Mode Operation - A diagram illustrating Gateway Mode Operation.

A DMO/TMO gateway provides gateway connectivity between radio operations in DMO and the TETRA TMO network, acting as the interface between TETRA DMO and TMO modes. The gateway has two air interfaces: on the TMO network connection, it operates as a normal TMO radio, registering and authenticating to the SwMI using its own ITSI and security keys. On the DMO side, it uses the air interface specified in ETSI DMO Gateway Air Interface on the frequency selected for the current DMO talkgroup. The gateway generates a Gateway Presence Signal after successful registration and authentication to the SwMI, informing any DMO radio monitoring the RF carrier that the gateway is present and available. Individual and group calls are supported. When the gateway receives an individual or group call addressed to its current selected TMO talkgroup, it forwards the call to the respective mapped DMO talkgroup. If the DMO channel is not free and the incoming call has Emergency priority, a preemption request is sent. When the gateway receives an individual or group call addressed to its current selected DMO talkgroup, it forwards the call to the respective mapped TMO talkgroup. The DMO radio initiating the call requires correct setup for gateway calls. The gateway enters Background Mode if it receives TETRA signaling not addressed to it that is stronger than the Gateway RSSI Threshold, ceasing to send presence signals or transfer traffic. To re-enter Gateway Mode, the gateway surveys the DMO channel for TETRA signals, re-entering Gateway Mode if no signal stronger than the Gateway RSSI Threshold is detected, or after a period determined by the Gateway Background Survey Time or Gateway Background Monitor Time. Gateways roam between TMO sites, with site switches delayed to prevent call disconnection. Note: While in gateway mode, individual and group calls cannot be initiated, and any active TMO scanning is suspended.

2.6 DMO Gateway and Repeater Communication

The radio allows communication in Direct Mode Operation (DMO) with a Trunked Mode Operation (TMO) group through Interoperability (IOP) certified gateways. A DMO repeater retransmits information received from one DMO radio to other DMO radios over the DMO air interface. For each DMO talkgroup, the radio allows operating in one of the following modes: Radio to radio only, Specific gateway, Auto gateway, Repeater, Specific gateway and repeater, or Automatic gateway and repeater. All outgoing communication is placed through the gateway if a specific or auto gateway mode is chosen and a suitable gateway is found. The radio attempts to set up communication directly if gateway setup fails or a suitable gateway is not found. When operating on a gateway and/or repeater, the radio indicates the communication mode.

2.6.1 Communication through Repeaters

Radios out of range in DMO can communicate through a repeater, which repeats all communication on a chosen channel to increase DMO range.

Figure 6: Communication through Repeaters - A diagram showing communication through repeaters in DMO.

When the radio connects to a repeater, it plays a tone, displays "Repeater available", and shows an appropriate icon. When connection is lost, it plays a tone, displays "Repeater not available", and the repeater icon blinks.

2.6.2 Communication Through Gateways

Gateways provide connectivity between radios in DMO and the TETRA network, enabling DMO radios to communicate with TMO radios.

Figure 7: Communication Through Gateways - A diagram showing communication through gateways between DMO and TMO.

Radio behavior when connecting to a gateway: a tone is sounded, "Gateway available" message is displayed, and an appropriate icon is shown. When connection is lost: a tone is sounded, "Gateway not available" message is displayed, and the gateway icon blinks.

2.6.3 SDS through DMO Gateways or Repeaters

Radios in DMO can send SDS Status, SDS User-Defined Data Types 1, 2, 3, SDS User-Defined Data Type 4 (with or without SDS Transport Layer), and GNSS/GPS LIP messages to other radios through DMO Gateways or Repeaters. Both DMO Gateways and Repeaters can forward messages in Reservation and Idle mode, supporting directions from DMO group address to TMO group address, TMO group address to DMO group address, DMO individual address to TMO group address, and TMO individual address to DMO individual address.

2.6.4 Gateway and Repeater Synchronization

To communicate using gateways or repeaters, the radio requires synchronization. A gateway or repeater sends presence signals; if received, the radio stays synchronized. If a radio fails to receive a presence signal, it waits for another successful presence for a time defined by the service provider. If a gateway or repeater is unavailable or the radio is not synchronized, the radio may fall back to DMO or prompt the user to override gateway/repeater operation. In the latter scenario, individual and group calls are received, individual calls can be replied to, but group calls cannot.

2.7 Numbering and Addressing

Each radio has an Individual TETRA Subscriber Identity (ITSI) for addressing. Short number schemes can be used for easier addressing. The radio can be provisioned to treat a short number as a Short Subscriber Identity (SSI), combining the entered number with the radio's own SSI to form an Individual Short Subscriber Identity (ISSI). This ISSI can comprise a fleet number and a member part. The radio's ISSI determines leading digits for omitted digits. This scheme is used for duplex private calls, simplex private calls, group calls, mobile status, short data bearer service, and text message service. Entering a seven-digit number is interpreted as a real TETRA ISSI regardless of the short addressing scheme.

2.8 Dialing Methods

The radio supports multiple dialing methods: using predefined One-Touch Buttons, dialing from favorite folders, the address book, the Recent Calls list, direct dialing, embedded numbers in Short Data Service messages, speed dialing, and talkgroup dialing by index.

2.8.1 Individual Dialing

The Individual Call feature includes Telephone Interconnect and Private Call. The Phone or PABX feature allows making phone or PABX calls by dialing a shortened number (up to three digits) instead of the full number. Phone or PABX speed dial numbers are assigned when the dialed number is added to the contact list. Users can redial numbers from the call history list. The private ID number is up to 16 digits; if fewer are entered, the ISSI part is added with leading zeros. The private ID number consists of Mobile Country Code (MCC), Mobile Network Code (MNC), and ISSI. The Migration mode supports three types of relative dialing (relative to SwMI, radio MNI, or current MNI). Two dialing options are available: Fixed (up to 16 digits) and Automatic (up to eight digits, switching to fixed if more are entered). If the One-Touch Button is provisioned, an individual can be called by pressing and holding a programmable button.

2.9 Unified Address Book

The radio offers an address book facility where multiple numbers are associated with a single name tag, allowing calls to individuals contacted in different ways. Each individual can have up to six associated numbers: Private (TETRA ISSI or ITSI), Home (phone), Mobile (phone), Work (phone), PABX (local short number), and Other (phone). The Contact List has a maximum capacity of 2,000 Contacts, with up to 1,000 associated Private and up to 1,000 associated Phone or PABX numbers. The radio provides editing capabilities for adding or deleting entries and viewing used/free entries. The address book is also accessible via PEI using AT commands.

2.10 Call History

A call history list includes last dialed numbers, missed call numbers, and answered call numbers, along with call establishment time and duration. Pressing the down scroll key displays the call history. The stack holds private TETRA IDs and phone/PABX numbers. Numbers can be viewed, selected, and called, though outgoing duplex calls from the Recent Calls list in DMO are not allowed. Entries appear in reverse order (most recent first). Numbers from the call history stack can be saved to the address book.

2.11 Group Call

The group call service enables point-to-multi-point communication with other TETRA radios in both TMO and DMO. Users can initiate a new group call or talk back to an existing group call by pressing the PTT button.

2.11.1 Programmable Talkgroups

The radio offers a talkgroup list facility where each entry contains a TETRA group address and may be associated with a name tag. Talkgroups are configured separately for TMO (name and Group Short Subscriber Identity - GSSI) and DMO (name, Group TETRA Subscriber Identity - GTSI, and frequency). The radio operator can select a talkgroup with an associated TMO or DMO frequency depending on the mode. When switching modes, the last active talkgroup is selected, or a corresponding talkgroup is automatically selected if mapped in CPS. Neither the group name nor the group address can be edited via the radio MMI. A talkgroup linked to several networks creates unique talkgroups per network. The GTSI indicates talkgroup uniqueness, combining GSSI and network.

2.11.2 Talkgroup Folders

Talkgroups are organized in folders, allowing selection by first choosing a folder and then the talkgroup within it. Folder size is flexible. Talkgroup folders are organized in a tree structure: Level 1 Folders (can contain level 2 folders and talkgroups) and Level 2 Folders (placed in level 1 folders).

Figure 8: Talkgroup Tree - A diagram illustrating the hierarchical structure of talkgroup folders.

2.11.3 Talkgroup Selection

Talkgroup selection from the idle mode list can be done by scrolling using scroll keys or the Talkgroup Knob. Talkgroup scrolling can be provisioned to scroll within a folder only or continuously through folders. The radio does not allow direct dialing of a group Short Subscriber Identity (SSI).

2.11.4 Favorite Folders

Frequently used talkgroups and phone book contacts can be added to the Favorite folder for quick access, allowing inclusion in up to three favorite talkgroup ranges, stored separately. This feature operates in both TMO and DMO modes, with favorite ranges shared between modes. Pressing the Up scroll key allows selection, viewing, and editing of "My Groups" ranges.

2.11.5 Talkgroup Blind Operation

The radio can be provisioned with a virtual scrolling end-stop option for blind operation. When scrolling to the beginning or end of the list, the first or last talkgroup is displayed even if scrolling continues. A tone indicates reaching the virtual end-stop. The "Wrap around Rotary Knob Group Scrolling" option in CPS can change this setting for the Rotary Knob and Talkgroup Selector button.

2.11.6 Receive-only Talkgroups

Talkgroups can be provisioned as receive-only, meaning calls can be received but not initiated to them. This setting depends on the talkgroup's folder settings.

2.11.7 Non-Selectable Talkgroups

A talkgroup can be provisioned as non-selectable, meaning it is not visible when scrolling through the talkgroup list and cannot be selected. The group name is displayed only upon receiving a call for the group, such as an announcement talkgroup or a scanned one. Users cannot edit the scan list.

2.11.8 Transmission Timeout Timer

The radio limits continuous talk time in a group call according to a provisioned value, with a warning before the time expires. The timer is provisioned per talkgroup folder.

2.11.9 Group Call Reception

In most situations, group calls are received without intervention, alerted by a short tone (configurable to be disabled). Speech follows. Calls ended by the call owner (normally the SwMI) require no user action. Users can leave a group call, which continues for other radios.

2.11.10 Talkgroup Scanning

Talkgroup scanning allows monitoring multiple talkgroups simultaneously. Users can define a user-activated scan list (up to 20 talkgroups) to monitor in addition to the selected group. Up to 40 scan lists can be defined. If the SwMI instructs a radio to detach a scanned group, monitoring stops, but the group remains in the list. Subsequent attachment causes monitoring to resume. The radio may passively monitor the selected talkgroup, associated Announcement Talkgroups (ATGs), talkgroups associated with ATGs, talkgroups in user-activated scan lists, SwMI-controlled scan lists, and groups set to "Always Scanned".

2.11.11 Priority Monitor

While in a group call, if a call setup for a different group is received, the radio decides whether to accept it based on call priority. If the new call has higher priority, it may be joined, dropping the current call. Priority is determined by call setup signaling and the group's Class of Usage (CoU) priority. If call priorities are equal, CoU priority decides. The radio can be set to present the new higher priority call to the user before joining. A selected group call can be treated as higher priority than a scan group call, regardless of actual call or group priorities.

2.11.12 Network Monitor

Note: This is a Software Selling Feature.

This feature allows the radio to monitor TMO individual calls while maintaining DMO services. When Network Monitor is active, the radio receives direct calls addressed to the selected DMO talkgroup, private DMO calls, SDS messages, and private TMO calls. Initiated calls are configured in DMO, with only responses to private TMO calls sent in TMO.

A diagram illustrates TMO Private Call and DMO interaction.

2.11.13 Announcement Talkgroups

The radio supports a group hierarchy concept where an Announcement Talkgroup (ATG) consists of up to 20 talkgroups, with one master group monitoring ATG traffic. Users of subgroups cannot monitor other subgroups. Selecting an ATG allows the radio to monitor signals addressed to the ATG in addition to its selected talkgroup. The radio does not support active scan lists while attached to an ATG. Depending on codeplug settings, the radio can initiate an announcement call or an emergency call to the ATG. A talkgroup can be associated with only one ATG, and an ATG cannot be associated with another ATG. An ATG has a higher priority than other group calls within the same call priority.

2.11.14 Broadcast Call Initiated by User

This feature allows making a Broadcast Call from the radio on a predefined talkgroup. The alias, call priority, and destination address can be configured in the codeplug. This feature is TMO mode only. During Broadcast Call, other services (except emergency) are disallowed, Hot Mic functionality is unavailable, and ongoing services are terminated. If the BSI feature defines encryption, the Broadcast Call is clear; otherwise, it uses the encryption settings of the service. Not all infrastructures support this feature.

2.11.15 Timed Talkgroup Change

This feature allows switching between original and predefined TMO or DMO talkgroups using a One-Touch Button for a specified time (Functional Timer). After the timer expires, the radio returns to the original talkgroup. Returning to the original talkgroup can also be assigned to the second press of the button. An example scenario is provided involving campus university buildings and emergency talkgroups.

2.11.16 Broadcast Call

Broadcast Call enables the dispatcher to transmit to all radios in a specific area, available only on GMOI networks. The radio joins calls received with a broadcast communication type and displays a notification. This call type is typically addressed to the broadcast address (ISSI) and takes precedence over calls with the same or lower priority. The radio cannot initiate a broadcast call but can initiate a "broadcast-type" call restricted to a particular talkgroup using the Announcement Call feature.

2.11.17 Announcement Call

This feature allows making a Broadcast Call from the radio on a predefined talkgroup. The alias, call priority, and destination address can be configured in the codeplug. This feature is TMO mode and GMOI network only. During Announcement Call, other services (except emergency) are disallowed, Hot Mic functionality is unavailable, and ongoing services are terminated. If the BSI feature defines encryption, the Broadcast Call is clear; otherwise, it uses the encryption settings of the service. Not all infrastructures support this feature.

2.11.18 D-PTT Tone

The PTT double push (D-PTT) feature enables the radio to generate a specific tone sent to other radios in the talkgroup. The radio can support either D-PTT Tone or D-PTT Preempt Group Call, but not both. To send the tone, press the preconfigured One-Touch Button once or PTT twice within a defined period. D-PTT triggers in idle or group call mode. The tone is not audible on the sending radio. After the tone, pressing PTT again grants permission to talk; otherwise, the press is ignored. The D-PTT tone is sent as voice, so receiving radios play the sound regardless of feature enablement. Tone volume can be adjusted. D-PTT tone can be single, double, or triple, and the tone type can be changed in the codeplug.

2.11.19 D-PTT Preempt Group Call

Note: This is a Software Selling Feature.

The D-PTT Preempt Group Call allows superiors to take over and speak in an ongoing group call by making preemptive priority calls. By pressing the PTT button twice, a preemptive request is made to interrupt an ongoing group call and gain permission to speak. If a group call is preempted and the PTT button is still pressed, "PTT Denied" is displayed. If visual notification is enabled, "PTT Interrupted" is displayed. If audio notification is enabled, the "PTT Denied Tone" plays until the PTT button is released.

2.11.20 PTT Queue

PTT Queue configures the response to releasing PTT of the call originating radio and cancels waiting for a call when the infrastructure is busy and the call is queued.

2.11.21 Talking Party Identification

Radios in a group call receive the ID of the transmitting party, found in the call setup message.

2.11.22 Call Ownership

The radio can be given call ownership of a talkgroup call, sending appropriate TETRA signaling to end the call. The SwMI decides call ownership.

2.11.23 Transmission During Group Call

While receiving a group call with "PTT during received Group Call" enabled, pressing and holding PTT requests to transmit, with the request queued. Releasing PTT withdraws the request.

2.11.24 Call Restoration

If the radio roams to a new cell during a call, it attempts to continue the call. Announced cell reselection is used if transmitting; unannounced cell reselection if not transmitting, followed by call restoration procedures.

2.11.25 Temporary Group Address

The radio supports temporary group addresses assigned by the SwMI, valid only for the call lifetime. The radio monitors signaling addressed to the temporary group when initiating a group call on the selected group and the SwMI assigns the call to a temporary group. It also supports assignment of an incoming group call to a temporary group address.

2.11.26 Late Entry

A radio can join a group call even if it did not participate from the beginning. For example, turning on the TETRA terminal and selecting a talkgroup with an ongoing call automatically joins the call. Similarly, if the radio was outside coverage (e.g., in a tunnel), the control channel continues to divert the terminal to a talkgroup call if one is in progress. Note: For TMO, this feature must be configured on SwMI. Acknowledged late entry and late entry paging are not supported.

2.11.27 User Initiated Group Attachment

A radio must attach to a talkgroup to participate in a group call. The radio initiates a group attachment request to the SwMI upon power-up, registration on a new site, user-initiated group change, or scan list activation. When a group change is requested, the radio detaches the old group and attaches to the new one. Attachments are sent with "Amendment" or "Detach all..." modes to minimize air interface signaling. Scanning activation or ATG selection also triggers group attachment requests. The TETRA TIP allows radios to send status messages to turn scanning off/on to save signaling. If enabled, turning scanning off sends TETRA signaling, and the radio monitors only the selected group. Turning scanning on resumes monitoring all scanned groups. If not provisioned, users can only deselect the active scan list, not turn off scanning. Deselection detaches scan list groups, but other groups like ATG associations continue to be scanned. If the radio is not provisioned to turn scanning off/on via signaling, users can only deselect the active scan list.

2.12 Private Call

Private call, also known as point-to-point call, enables communication between two individuals, unheard by others. This call type can be Duplex (TMO only, both parties speak simultaneously) or Simplex (TMO or DMO, only one party speaks at a time). In TMO, private calls can be answered via Hook (default, requires answer to transmit), Direct (automatic answer and immediate transmission), or As Received (according to transmitting party's setup). Table 1 details call answering rules, with receiving radio setup taking precedence. In DMO, radios not involved in a private call receive a channel busy indication. Radios are identified by their numbers.

2.12.1 Transmission Timeout Timer

In a simplex call, the radio limits continuous talk time according to a provisioned value, with a warning before expiration. The timer is provisioned per talkgroup folder.

2.12.2 Call Restoration in Private Call

If the radio roams during a private call, announced cell reselection (if possible) is employed, followed by call restoration procedures. If not transmitting, unannounced cell reselection is used, followed by call restoration.

2.12.3 Call Modification

Call Modification allows service providers to adjust calls for current situations, covering call priority, call type, and call encryption (during ongoing calls, not transmission). When a call is modified, "Call Modified" is displayed. If the modified call requires PTT, "Call Modified Use PTT" is shown. Modifications are made by the service provider; the radio only follows them. If a call priority changes to emergency, the display indicates "Emergency Group Call Received" and plays a special audio alert. Note: Group Call modification to Emergency Group Call does not trigger emergency-related features. If the radio cannot follow a modification due to its settings, it rejects it and displays "Service Not Available".

2.12.4 Assistance Call

The Assistance Call feature helps users call for assistance in normal, non-critical situations. It initiates a private call to a configured ISSI number. Assistance Call destination address and priority can be configured in the codeplug. This feature is TMO and GMOI network only. Assistance Call can be simplex or duplex depending on service provider settings. Full-duplex calls are initiated via the radio menu; typing the number and pressing PTT starts a half-duplex call; typing the number and pressing SEND initiates a duplex call.

2.12.5 DMO Individual Call Presence Check

If the other party is listening, the Presence Check feature confirms to the user making a DMO private call that the message will get through. If the other party does not answer, "Party not available" is displayed. Both radios must support this feature. Radios can be configured to "Accept DMO Individual Calls with Presence Check", accepting calls with or without the check, or only accepting private calls without the check if disabled.

2.12.6 DMO Individual Only Talkgroups

Some or all DMO talkgroups can be configured to allow only individual calls, optimizing frequency allocation in DMO.

2.12.7 Private Calls through DMO Gateway

Note: This is a Software Selling Feature.

The DMO Gateway can relay clear and non-BSI encrypted private calls from a TMO radio to a DMO radio, and vice versa. A DMO radio can establish a private call directly with another TMO radio using its ISSI. A TMO radio initiating a private call with a DMO radio first establishes a private call with a DMO Gateway, which then establishes a private call with the target DMO radio address. The DMO forwarding address is configurable via CPS, iTM, Gateway MMI, or remotely using AT commands or TMO SDS Remote Control.

2.12.8 Individual Call Supplementary Services

Individual Call supplementary services in TMO provide functions similar to telephony networks, including Call Hold, Call Transfer, Call Waiting, and Call Forwarding.

2.12.8.1 Call Hold

A console operator can interrupt an individual call by putting it on hold, allowing other actions like searching for information. Voice communication stops but is not terminated, resuming when the call is no longer on hold.

2.12.8.2 Call Transfer

Call Transfer allows a console operator to transfer an active individual call to another party, useful when the caller cannot dial directly or lacks the number. The caller is put on hold while the operator initiates a call with the new party, then transfers the call to connect both parties.

2.12.8.3 Call Waiting

Call Waiting allows a radio engaged in a call to acknowledge an incoming individual call, with options to Accept, Reject, or Ignore the waiting call. Accepting ends the ongoing call and connects to the new one. Rejecting rejects the waiting call, and the ongoing call resumes. Ignoring starts the "Waiting Call Ignoring Duration" timer; the ongoing call must end before the timer expires to connect to the new call, otherwise it is rejected.

2.12.8.4 Call Forwarding

Call Forwarding allows the SwMI to redirect an individual call based on pre-configurations: Call Forwarding Unconditional (CFU), Call Forwarding on Busy (CFB), Call Forwarding on No Reply (CFNRy), and Call Forwarding on Not Reachable (CFNRc).

2.13 Phone Call

The phone call service enables a TMO radio to communicate one-on-one (simplex or duplex) with a phone (e.g., landline or another TETRA radio) using a telephone switch. The radio supports individual call service to an external identity. Two phone call types are available: Public Switched Telephone Network (PSTN) calls to a defined PSTN gateway address, and internal Private Automatic Branch Exchange (PABX) calls to a defined PABX gateway address. Note: PSTN phone calls require the PSTN/PABX feature to be enabled in the codeplug and supported by the SwMI. Only one PSTN/PABX gateway ID and one PABX/PABX gateway ID are available per radio.

2.13.1 Phone Call Initiation

The radio can initiate PSTN or PABX phone calls with duplex speech capability, using TETRA individual call signaling with single-stage dialing and hook setup. Hook signaling generates feedback tones internally until a traffic channel is allocated, but the SwMI can modify setup to direct, enabling infrastructure progress tones. Phone calls can also be made between TETRA radios using the Mobile Station International Subscriber Directory Number (MSISDN) as the called party number, sharing the same gateway as phone calls. MSISDN calls can be simplex or duplex based on the assigned ISDN number. Note: Dimetra Infrastructure does not support private calls and SDS through MSISDN.

2.13.2 Phone Call Reception

Incoming phone calls from the land gateway use on-off hook signaling. The radio extracts the gateway ID from the call setup signaling to determine whether to initiate a phone or PABX call.

2.13.3 Call Restoration in Phone Call

If the radio roams during an active phone call, and announced cell reselection is possible, it is employed, followed by call restoration procedures.

2.14 Emergency Operations

Emergency Operations are used in critical situations. Pressing the Emergency button or entering an Emergency number and pressing Send activates services based on service provider settings. Note: The radio can be powered up by pressing the Emergency Button. Emergency Operations bypass PIN lock (except SIM PIN) if configured. During Emergency Operations, the radio rejects phone, PABX, and private calls, and does not monitor scan lists, but monitors subgroups associated with an ATG if it is the selected group. Any ongoing voice call or packet data transfer is aborted or cleared down, though the session remains open.

2.14.1 Emergency Group Call

The Emergency Group Call has the highest communication priority, making it a pre-emptive call available in both TMO and DMO. During Emergency Operations, it can be started by pressing PTT or via Hot Microphone operation. Incoming emergency priority group calls trigger an emergency call received notification and a special audio alert. The Emergency Group Call Termination feature allows users to attempt terminating an Emergency Group Call by pressing the End key. Termination conditions depend on the radio's call owner status. The SwMI may reject termination requests. Emergency group calls can be non-tactical (on a designated Emergency talkgroup) or tactical (on the currently selected talkgroup). In TMO, if an emergency broadcast call is active upon entering emergency operations, the radio continues on the call without initiating new ones and sends an emergency alarm.

2.14.2 Non-Tactical Emergency

In Non-Tactical Emergency, the radio switches to a designated Emergency talkgroup for the duration of the operation, disallowing talkgroup changes. In TMO, Emergency Non-Tactical Group Calls can be made without sending attachments, assuming implicit attachments after receiving a temporary address if configured. In DMO, Non-Tactical Emergency proceeds on the same frequency as the previously selected talkgroup. Any ITSI address can be designated for Emergency Operations, including an Open Group broadcast address. After exiting Non-Tactical Emergency, the radio returns to the previously selected talkgroup.

2.14.3 Emergency Individual Calls (Private or MSISDN)

Emergency Individual Calls are simplex or duplex calls with emergency priority. Pressing the Emergency button initiates an individual call to a provisioned private or MSISDN address, supporting direct or hook dialing. For full duplex Emergency Individual Calls to MSISDN, the default dialing method is hook, which cannot be modified. During Emergency Individual Calls, the radio rejects all incoming non-emergency priority individual calls, which are shown as missed calls after the emergency calls end. Emergency Full Duplex Private Calls support high/low audio states, configurable during incoming or outgoing calls.

2.14.4 Emergency Alarm

The emergency alarm is a special status message sent to the infrastructure upon starting Emergency Operations, with retries and acknowledgments. Each entry into Emergency Operation sends an alarm, with an audible tone upon successful dispatch. An extra alarm is sent upon pressing the Emergency button during Emergency Operation, except during Hot Microphone transmission. The message can be dispatched in both TMO and DMO.

2.14.5 SDS in Emergency Mode

Short Data Service (SDS) in Emergency Mode enables Status and/or SDS functionality during emergency mode or an emergency call. If enabled, the Message menu is accessible for composing, sending, and viewing Status and/or SDS messages.

2.14.6 Emergency SDS Status

Emergency Short Data Service (SDS) Status allows sending a status message with a pre-programmed value to a destination address set in the codeplug. This feature is TMO only. If no acknowledgment is received, the radio retries sending the message. Status is not sent if Emergency Alarm or Hot Microphone is configured.

2.14.7 Emergency Hot Microphone

The Hot Microphone allows talking without pressing the PTT button during Emergency Operation for a provisioned time. Pressing PTT before the time expires ends Hot Microphone operation, reverting to normal PTT for the duration the button is held. Subsequent Emergency button presses restart Hot Microphone transmission. If a talk permit is granted to another member, the Emergency Call received tone plays, and the radio may attempt to get talk permit again. Pressing the End soft key or End key ends Hot Microphone operation.

2.14.8 Alternating Hot Microphone

Alternating Hot Microphone, an enhancement of Hot Microphone, allows it to be switched on and off alternately. Initiated by pressing the Emergency button, it terminates when the radio exits Emergency Mode, the timer expires, PTT is pressed (if configured), or the right Soft key is pressed (during transmission timeslot). Pressing the End key skips the transmission timeslot for a receiving timeslot. Note: When the radio goes out of service, it enters receiving mode, and Alternating Hot Microphone is on hold, resuming upon return. Pressing the Emergency button in Emergency Mode restarts Alternating Hot Microphone.

2.14.9 Silent Emergency Mode

Silent Emergency Mode provides emergency services with no audible indications or keypad tones, with display indications as in home mode. Services are limited to receiving Ambience Listening, sending Silent Emergency Alarms, and sending GNSS location reports. Any other attempted feature activation is blocked. If enabled, pressing the Emergency button enters Silent Emergency Mode, staying in or switching to TMO, and sending a Silent Emergency Alarm. Note: If the radio is in a private or group call, it waits for the call to end before entering Silent Emergency Mode. The alarm is re-sent until successful delivery. The radio exits Silent Emergency Mode via Menu + Right Navigation key, failed alarm sending after retries, control room termination of Ambience Listening, or disconnection due to other reasons. Powering off in Silent Emergency Mode enters Pseudo Power-Off state, remaining operational. Powering on resumes Silent Emergency Mode.

2.14.10 Invisible Emergency

Invisible Emergency disables visual and audible indications on the radio during Emergency Operation, providing an extra layer of safety in critical situations like direct attacks.

2.14.11 Disaster Alert

Disaster Alert is a broadcast emergency call initiated by the radio with emergency pre-emptive priority, audible to everyone in a broadcast area. Designed for catastrophic situations like earthquakes, it has the highest priority. All radios under Disaster Alert display an emergency notification. The alert message, duration, and destination talkgroup are configurable. Initiating Disaster Alert involves switching to Disaster Alert mode and pressing PTT. The radio exits Disaster Alert state when the call ends. During Disaster Alert, other services are terminated, no other services can interrupt it, Hot Mic is unavailable, and speech is only in Clear mode, except for E2E Encryption. Note: Not all infrastructures support this feature.

2.14.12 Emergency Alert

Note: This is a Software Selling Feature.

This feature allows the radio to send emergency alerts to other radios within its DMO coverage by pressing the Emergency button. Even in TMO, the radio monitors a special DMO emergency frequency for alerts and responds by automatically joining the emergency call. To initiate an alert, the radio must be in MS-MS DMO mode or out of coverage in TMO mode; the alert is not sent to the dispatch console. To receive an alert, the radio must be in DMO or TMO, within RF range, and not in a call. Upon receiving an alert, it automatically joins the call. Table 2 illustrates dependencies between radio mode and emergency operation type.

2.14.13 Emergency Destination in Local Site Trunking

Note: This is a Software Selling Feature.

This feature allows the radio to send emergency requests to a different destination while in local site trunking mode. Supported emergency services include Emergency Alarm, Emergency Call, Emergency Short Data Service (SDS) Status, and Location Information Protocol reports.

2.15 Short Data Services

The radio supports SDS message types: SDS Status, SDS User Defined Data Types 1, 2, 3, and SDS User Defined Data Type 4 (with or without SDS Transport Layer - SDS-TL). It supports addressing modes: radio to radio, radio to talkgroup, and radio to external subscriber number (gateway address). Note: For SDS-TL, messages can be sent via the service center. The radio provides a short data bearer service for internal and external applications. SDS-TL services offer end-to-end acknowledgments, delivery report requests, and message numbering for SDS user-defined data type 4. The TL also provides SDS access for applications not requesting these services but using a Protocol Identifier (PI). The radio can send delivery reports automatically or manually. It supports legacy SDS-TL standards and other SwMIs. Externally connected devices can access SDS services via AT commands and TNP1 protocol. Downlink SDS messages type 4 with a PI are delivered to registered target applications. Retransmitted messages are not displayed, stored, or sent to external applications.

2.15.1 Status Messages

Users can select from up to 4000 preprogrammed alphanumeric aliases, each corresponding to a status value. Uplink status values are provisioned parameters. If targeted status is not enabled, the status value is sent to the selected group address. The radio recognizes general status acknowledgments and negative acknowledgments from the SwMI. In TMO, if no acknowledgment is received, the radio retries sending the message, with retry count and wait time provisioned. Users are notified of delivery status. DMO status messages have no acknowledgment, only sending notification. Status messages are not initiated on a traffic channel. If targeted status is provisioned, the status value is sent by default to the last sent target, or a different individual/group can be specified. SDS status messages can be sent to directly entered IDs. If targeted status is not provisioned, the default address type (Private, Phone, or Group) determines the address used. "Dynamic" status messages are sent to the address configured for dynamic statuses or defined by a dispatcher. The radio accepts status messages from monitored addresses and can be preprogrammed with associated text. Receiving a status triggers a notification and displays the message mail screen for quick access. Received statuses can be stored in the radio's text message buffer. PEI provides access for external applications to send and receive status messages. Note: Dimetra Infrastructure does not support the targeted status feature.

2.15.2 Shadow Groups (Address Bundle)

Note: This is a Software Selling Feature. Shadow Groups (Address Bundle) is not available on Gateway mode.

Shadow Groups offer a way to send statuses to multiple destinations simultaneously. Each radio can store up to 255 Address Bundles of four types: Status Addressing (including emergency alarm), GNSS/GPS LIP Addressing, RMS/FMS Addressing, and Bluetooth Sensor Addressing. In TMO, each Address Bundle may contain up to four target addresses (ISSI or GSSI). Each talkgroup can be configured to send statuses, GNSS/GPS LIP reports, or RMS/FMS messages to a specific Address Bundle. The "Additional Address" feature allows sending RMS messages and LIP reports to additionally defined recipients. Service providers define default addresses, but users can create, edit, and delete Additional Addresses via the radio menu, unless disabled by the provider. In DMO, Address Bundles contain one target address. Shadow Groups may slightly elongate Emergency Calls setup time.

2.15.3 Text Messages

The radio supports an internal text messaging application using TETRA SDS-TL. Supported encoding schemes are ISO 8859-1 (Latin-1) and 2-byte Universal Character Set (UCS-2) Unicode. Table 3 shows maximum SDS characters with various encryption options. The radio supports Smart 8-16 and Smart 7-8-16 encoding schemes, auto-selected for mixed character inputs. Note: Special characters or multilingual texts may reduce the maximum character count. The radio provides an edit facility for composing and sending text messages with a request for a delivery report. Incoming messages are stored in the Inbox, outgoing in the Outbox. When store and forward is enabled, messages are stored regardless of delivery status; long messages are stored only if delivered. Note: Message protection is enabled in Inbox and Call Out Inbox folders; users can only delete unprotected messages. Delivery reports are saved in Inbox and Outbox, but deleted from Inbox after viewing. Inbox and Outbox share memory; capacity depends on stored messages. If Inbox is empty, Outbox can store up to 100 short or 20 full-size long messages. If Outbox is empty, Inbox can store up to 100 short or 10 full-size long messages. Message counts are displayed next to Inbox and Outbox.

2.15.3.1 Buffer Full Overwrite Policy

Upon receiving a text message, the radio places it into a circular buffer, notifying the user and providing quick access to read it. If a delivery report is requested, it's sent upon receipt by SDSTL. If a consumed report is requested, it's sent when the user reads the message. Note: If the radio is out of service when the message is read, the report may not be sent. Incoming or edited outgoing text messages can be saved, edited, and sent, or protected from deletion or overwriting. Message timestamps are verified from the SDS TL PDU, generated and inserted by the SwMI.

2.15.3.2 SDS Messages Concatenation

This feature allows sending long text messages up to 1000 characters, divided and sent separately. When all parts are received, the message displays as one. If the Inbox/Outbox is full upon receiving an SDS message, the radio follows the Buffer Full, Overwrite Policy settings. Upon acceptance, the radio retrieves time information from its internal clock. It can reconstruct long messages (up to 1000 characters) from up to ten short messages, regardless of reception order, provided message reference numbers are correct and the segmented receiver timer is valid. Long text messages can be sent to individual destinations but not to groups. During group or broadcast calls, the radio allows receipt of text messages, displaying a "New mail arrived" icon and tone. In Emergency Mode, SDS messages can be received but require leaving emergency mode to read; sending SDS messages in emergency mode is prohibited. A timer is activated for sending long, segmented text messages; if not all segments are received before expiry, the sending process fails. The service provider sets the timer value.

2.15.4 Immediate Text Messages

Note: This is a Software Selling Feature.

The Immediate Text Messaging feature enables the radio to receive and display text messages immediately, used for sending high-importance information from the console. Upon receiving an immediate text message, it is stored in the Inbox, its content is displayed, and a relevant audio tone is played. If periodic alerting is enabled, it remains active until the Soft key is pressed. Note: If disabled, immediate text messages are processed as normal text messages. Replying or forwarding an immediate text message sends it as a normal text message. If multiple immediate text messages are received, the latest one is displayed, and previous ones in the Inbox are not prompted.

Enhanced Immediate Text Messaging

Note: This is a Software Selling Feature.

When receiving an immediate text message, Enhanced Immediate Text Messaging prioritizes displaying private calls, group calls, talkgroup changes, or volume changes before the immediate text message. Upon receiving an immediate text message, users can send group status messages via OTB, initiate Private Calls via OTB, select groups using the rotary knob, or adjust volume. Performing an action via OTB displays a notification. If OTB function is not supported during an immediate text message, "Service Restricted" is displayed.

2.15.5 Home Mode Display Text Message

The radio allows service providers to send special text messages (up to 24 characters) to the display, which remain on the home screen until a new message is received. Power cycling the radio replaces the Home Display message with the predefined one.

2.15.6 Predefined Templates (ATS Entry Prompt)

This feature assists in sending formatted messages with predefined destination addresses (MSISDN, SSI, or TSI) for computer applications. Users select an entry prompt defining a message format, including read-only areas, editable areas, and allowed character types (numeric, alphanumeric, phone digits). The prompt definition, including the destination address, is set in the codeplug. When sent, the message uses SDS Transport Layer with the PI provisioned in the codeplug, requesting a receipt report. Multiple predefined templates with the same Prompt ID are chained into a single multifield template. The Predefined menu stores both predefined and multifield templates, distinguishable by their displayed names.

2.15.7 SDS Air Interface Aspects

Available delivery reports are standard and short form. The radio can be provisioned to send a short-form SDS-TL receive report if the originator allows it, using a designated 16-bit SDS status value. The radio can respond to delivery response requests automatically or manually. It supports SwMIs employing store and forward services and service centers. Store and forward operation is supported, but the radio only notifies on successful sending, not waiting for a report from the service center. Downlink SDS messages types 1, 2, and 3 are routed to the PEI if an AT application is registered; otherwise, they are discarded. Note: DMO SDS does not support type 1, 2, and 3 user-defined short messages.

2.15.8 SDS Encryption

Short data messages stored in the radio (Inbox, Outbox, Call Out messages) are protected against unauthorized access through encryption of stored messages and user authentication (using the radio's PIN). Protected messages require valid authentication to be read. SDS messages are encrypted before storage. If enabled, the radio prompts for PIN entry when accessing Messages Inbox, Outbox, or CO Box. After successful PIN entry, further access does not require PIN unless exiting the menu, turning off the radio, or changing the PIN. Disabling or changing the PIN through MMI prompts for confirmation and deletes protected messages. Changing the PIN via PEI deletes all protected messages. Permanent radio disable results in loss of access to protected messages.

2.15.9 SDS End-to-End Encryption

Note: This is a Software Selling Feature. End-to-end Encryption (E2EE) offers higher confidentiality than TETRA air interface data encryption, securing the entire transport path through the infrastructure. The source and destinations encrypt and decrypt data. Note: 260–275 MHz radios do not support SDS end-to-end encryption. In air interface encryption, the Base Station decrypts data, leaving it unprotected within the system. E2EE encrypts data at the source and decrypts it at the destination or an E2E terminator. E2EE protects SDS/SDS-TL data services in both TMO and DMO. Protected TETRA data types include SDS type 4 with SDS-TL and SDS type 4 without TL. Source data can come from external applications or internal tasks (text messages, GPS). The radio passes internal text messages and GPS data for encryption. Encrypted short data service is established between two endpoints, one in the radio and the other in an SDEG or another radio. The destination address specifies encryption type (encrypted, clear, or dropped). Figure 9 and Figure 10 illustrate SDS and Voice/Data End-to-End Encryption data services. Key Management Facility (KMF) supports only one short data association and key at a time. The radio selects E2EE mode based on address association and High Security Mode requirements. Users can override address association via MMI to send SDS as clear or encrypted. High security mode requires mandatory cryptogroup associations; if none exist, keys are not loaded, and encrypted messages are discarded. This feature can only be disabled using the Key Variable Loader (KVL).

2.15.10 Store and Forward

This feature allows communication between users who are not available simultaneously. If the destination is unreachable, the message is stored in the system (if supported) until it becomes available or the expiration time is exceeded. The system is configured to delete messages after a predefined time, not configurable via the radio. Store and forward messages can be sent to an individual address or a group. Depending on codeplug settings, sending to a group may switch the message status from Store and Forward to Immediate. When "Sending group message to Store and Forward Server" is enabled, SDS messages sent to a group are conveyed with the store and forward service's assistance. The radio sends Store and Forward SDS to groups only with Delivery Report Request set to None by the service provider. For Store and Forward SDS to an individual address, the radio can send SDS with any Delivery Report Request (None, Received, Consumed, Received and Consumed) set by the user. The radio does not request a delivery report, so users are not notified of the delivery status. Note: Verify infrastructure system support for this functionality.

2.15.11 SDS Receive Failure Notification

When a radio fails to decrypt a received SDS message, it displays a notification including the ISSI of the sender and the reason for failure.

2.15.12 DMO SDS Transmit Traffic Stealing

DMO SDS Transmit Traffic Stealing enables sending status or SDS during a voice call transmission in DMO by replacing audio frames with status or SDS payload.

2.16 Collaborative Messaging

This feature allows external devices to send/receive messages when the radio application is enabled, mutually exclusive with Secure SDS Storage and EtE High Security Mode. External devices can connect via Bluetooth or wired cable. Functions include Inbox/Outbox synchronization and notification synchronization. Note: This feature does not support Call Out/RMS/Home Display.

2.17 Security Services

The radio provides TETRA security features as described in the TETRA Security ETS 300 392-7 standard, TTR 001-11 TIP, and TTR 001-13 TIP.

2.17.1 Terminal Equipment Identity

The Terminal Equipment Identity (TEI) is a unique identification number programmed at the factory and cannot be modified.

2.17.2 PIN/PUK User Authentication

The radio supports Personal Identification Number (PIN) and PIN Unblocking Key (PUK) mechanisms for authentication, preventing unauthorized access. PIN/PUK operations are available via MMI and PEI (using AT commands). A valid 4-digit PIN (defined in the codeplug) is required to access services. Reaching the maximum number of failed attempts blocks the radio until unblocked, a state sustained through power cycles or battery removal. PIN-locked radios have limited access. The radio is unblocked by entering the PUK or using CPS. The PUK is defined in the codeplug. BSI PIN/PUK Authentication requires a valid BSI PIN (up to 8 digits, configurable) before accessing services. Failed attempts block the radio. BSI PIN/PUK codes are provider-defined and cannot be changed by the user. Note: The radio supports either PIN/PUK or BSI PIN/PUK mechanism at a time.

2.17.3 Authentication

Authentication establishes trust between a radio and SwMI via a challenge-response protocol using a shared secret key (K). The SwMI Authentication Centre (AuC) provides a single K. The SwMI always initiates Authentication; the radio can also authenticate the SwMI if configured.

2.17.4 Air Interface Encryption

Note: This is a Software Selling Feature.

Enhanced Security includes TMO Air Interface Encryption class 3G and DMO class 2. The radio supports TETRA Air Interface Encryption (AIE) using standard algorithms (TEA1, TEA2, TEA3) with 12,000+ key combinations. TMO has three encryption classes: Class 1 (clear), Class 2 (static key encryption - SCK), and Class 3 (derived key encryption - DCK, Common Cipher Key - CCK, Group Cipher Key - GCK). DMO has two classes: Class 1 and Class 2. Table 4 lists security features required per security class. Note: Current release does not support radio-initiated authentication, TEA4, explicit authentication during DGNA, OTAR in foreign networks, or GCK AIE in foreign networks.

2.17.4.1 Clear Radios (Class 1)

A clear radio identifies itself as Security Class 1 during registration and does not support encryption, lacking encryption algorithms in its software.

2.17.4.2 Static Cipher Key Encryption (Class 2)

The radio supports static AIE using up to 32 Static Cipher Keys (SCK) shared between SwMI and authorized radios. The radio determines which SCKs to use based on SCK Number (SCKN) and SCK version number (SCK-VN) broadcast by the SwMI. Radios configured for static key encryption identify as Security Class 2 and attempt to negotiate it, using either TEA1 or TEA2 (TEA3 for Asia/Pacific) Key Stream Generator (KSG) algorithms. Encrypted PDUs use SCK. In DMO, the system manager can choose SCK, distributed via Over-the-Air Rekeying (OTAR) or provided manually via Key Variable Loader (KVL).

2.17.4.3 Derived Cipher Key and Common Cipher Keys Encryption (Class 3)

DCK/CCK encryption prevents overexposure of key material, unlike SCK which uses one key for all radios and communications. DCK is used for individually addressed TM-SDUs, while CCK is used for downlink group communication. DCK is derived from authentication processes, and CCK is received during registry. Class 3 radios identify as such during registry and attempt to negotiate Class 3 encryption. They support group addressed signaling and traffic encryption using CCKs, and individual signaling and traffic encryption using DCKs. The system supports OTAR of CCK. Clear radios can communicate with encrypted radios; the system informs encrypted radios to switch to clear operation. Class 2 and 3 radios can operate in lower classes if permitted.

2.17.4.4 Group Cipher Keys Encryption (Class 3G)

For Security Class 3G, the system allows grouping addressed signaling and dedicated group call traffic encryption using Group Cipher Keys (GCK) to cryptographically isolate talkgroups. Downlink signaling uses Modified Group Cipher Key (MGCK), derived from the CCK associated with the serving cell and the GCK associated with a talkgroup. SwMI does not change GCK and CCK simultaneously. GCK is received via OTAR; DCK is derived from authentication. The radio supports over-the-air and manual provisioning of key associations linking GCK to TMO talkgroups, and Key Association Group (KAG) to DMO talkgroups. The system can group TMO SSIs using Key Association Ranges (KAR) to convey TMO talkgroup and GCK relationships.

2.17.4.5 Over-the-Air-Rekeying

TETRA systems support GCK encryption for specific talkgroups via Group OTAR of GCK, fallback TM-SCK, and DM-SCK. Group OTAR requires a Group Session Key for OTAR (GSKO), delivered via individual OTAR and Session Key for OTAR (KSO). Sites regularly broadcast security class and key information. They transmit future key versions to cryptographic management groups (CMGs), which radios acquire before activation. Sites also broadcast current keys, retrievable by radio request. Note: If a radio has not received a new key before activation, it requests missing keys. Some systems use individual OTAR for SCK/GCK delivery (GSKO not used); others use a mix. The radio supports individual OTAR (KSO) of SCK/GCK, Group OTAR (GSKO) of SCK/GCK, individual OTAR (KSO) of GSKO, Secure DMO Key Management, CMG, storage of 10 KAGs (30 DM-SCKs), 16 GCKs, 2 TM-SCKs, Group Association attribute per Talkgroup, GCK AIE, seamless key changes, and seamless security class changes to SC3G. SwMI can support group OTAR by grouping radios sharing cryptographic key material into CMGs, addressed via CMG GTSI for transmitting OTAR messages. Each CMG has a designated GSKO, deployed over the air. SwMI schedules transmissions of future TM-SCKs and GCKs addressed to CMGs or individual ITSI. SwMI also schedules background transmissions of current and future DM-SCKs.

2.17.4.6 Encryption Mobility

Class 2 or Class 3 radios can operate on lower class SwMIs (if configured). Radios not permitted to operate on lower classes do not register on such cells. A Class 2 or 3 radio moving to a cell with a possessed SCK/CCK/GCK applies AIE to the registration PDU. If no acknowledgment is received, registration is sent in clear.

2.17.4.7 Encryption MMI

Class 2 or Class 3 radios involved in clear communication provide visual and audible indications if enabled by the service provider, signifying that communication is not encrypted.

2.17.4.8 Air Interface Encryption Key Storage

The radio stores all keys (SCK/CCK/DCK/GCK) securely in non-volatile memory, not in the codeplug. SCK keys can be loaded manually using KVL. A special key combination can delete cipher keys, either all keys or only short-term keys.

2.17.5 Secure DMO

Secure DMO guarantees key ciphered transmission in DMO. If DM-SCKs are provided by OTAR, users are informed if the radio lacks the complete set. Upon entering DMO without past/present DM-SCKs for all provisioned KAGs or successful reception of SCK Subset Grouping Type, SCK Subset Number, and SCK-VN information from SwMI, the radio plays a reject tone and prompts "OTAR incomplete". SDMO status is available via the MMI Security menu (DMOSCK Validity submenu). DMO SCK is Valid if OTAR is disabled and DM-SCKs are provided by KVL, or if OTAR is enabled and the radio knows current SCK info and has all corresponding past/present DM-SCKs. It is Invalid in all other cases. The radio supports system management of SDMO keys, requiring DM-SCK structures, current SCK Subset Number, and Version Number for key schedule coordination. The last received variant of this information PDU is considered the most accurate indication of SDMO key configuration. DMO SCK is usable only if Enhanced Security feature is purchased.

2.17.6 End-to-End Encryption

TETRA standard supports air encryption. The radio encrypts the PDU before transmission; the Base Station decrypts it. E2EE encrypts voice information before PDU packing, and it is also encrypted via TETRA over-the-air encryption. When the Base Station decrypts the PDU, the voice part remains protected until the called radio receives and decrypts it. The Micro-CRYTPR (uCRYPTR) encrypts the voice stream using keys. Voice and data encryption can use a dedicated SIM card reader. The radio notifies if a call is voice-encrypted. It supports BSI encryption in full duplex calls, relevant for group calls in TMO and DMO. Figure 10 illustrates Voice and Data End to End Encryption.

2.17.7 SIM Security

The SIM card holds a filing system and application, with security features available only on the GMOI network. Allowed SIM/SD cards include specific Industrial Grade MicroSD/MicroSDHC Cards and TETRA CRYPTR Miro cards. SIM security is ensured via Voice E2EE and key management, network access parameters and authentication, AIE key management, OPTA modification/encryption/transfer, and AES for E2EE of SIM Interface and SIM-Terminal Authentication. The application generates Key Stream Segments (KSS), synchronizes for E2EE, performs TETRA authentication, and manages E2EE keys. The filing system contains network access parameters (ITSI), security class definition, authentication definition, ICC identifier, SIM version number, and OPTA. E2EE keys are on the SIM, accessible only by the SIM application, making E2EE key management transparent to the radio. AIE keys remain on the radio, with the SIM application handling their management.

2.17.8 Radio Disable or Enable

A dispatcher can remotely disable or enable the radio. When disabled, the radio does not participate in voice calls, SDS, or packet data, ignoring all downlink supplementary services. Visible and audible indications are disabled, making the radio appear off. User inputs are ignored, and the PEI interface is closed. The radio continues mobility management functions for subsequent enabling/disabling. The disabled/enabled state is stored in the codeplug. If disabled, receiving appropriate TETRA signaling for subscription enablement with correct SSI and MNI restores normal operation. The TEI Query feature provides TEI information for disabling by TEI. Replacing the SIM card does not activate the radio. TEI Query is GMOI network only. If disabled, receiving appropriate TETRA signaling with the correct TEI restores normal state if subscription is also enabled.

2.17.9 Radio Permanent Disable

Note: This is a Software Selling Feature. Radio Permanent Disable and Radio Permanent Disable v2 are mutually exclusive.

Permanent disabling protects the network from compromised or faulty radios. It is a one-way function with no equivalent enable; the radio requires recovery and reprogramming. When permanently disabled, the radio becomes inoperable: MMI interfaces are disabled, all security key material (GCK, GSKO, DMO SCKs, Ks, DCK, CCK, TMO SCKs) is deleted, codeplug is deleted, and software is deleted. Permanent disable should be invoked for unrecoverable radios. For lost or stolen radios, the first step is temporary disable (stun). Permanent disable requires deletion of the user radio record in the User Configuration Server and K-REF association in the Provisioning Center and Authentication Center to prevent subscriber information download upon UCS restore. System operators must also remove the radio K-REF association from other Authentication Centers.

2.17.10 Radio Permanent Disable v2

Note: This is a Software Selling Feature. Radio Permanent Disable and Radio Permanent Disable v2 are mutually exclusive.

When disabled via permanent disable v2, the radio cannot be recovered over the air. It appears inoperable if it accepts the command and the v2 flag is enabled in the codeplug. Inoperable characteristics include disabled MMI interfaces, deleted security key materials (GCK, GSKO, DMO SCKs, Ks, DCK, CCK, TMO SCKs, and End-to-End), automatic entry into programming mode upon power attempts, and the permanent disable flag set in the codeplug. Unlike permanent disable, v2 can be re-enabled using the software selling dongle to read the codeplug and clear the flag. Note: To restore a radio disabled via permanent disable v2, refer to the TETRA Terminals CPS Start-up User Guide.

2.17.11 High Assurance Boot

The radio ensures code and data authenticity via High Assurance Boot (HAB) module at boot time. The module checks if software originates from a trusted source using public/private key mechanisms. If HAB authentication fails, the radio software does not run.

2.17.12 Covert Mode

Note: This is a Software Selling Feature.

This feature allows complete shutdown of all visible and audible alerts, making the radio unnoticeable. When in Covert Mode, certain Setup menu items (Set Volume, Tones, Backlight) are inaccessible. When Covert Mode is turned on: all tones are set to Off, group audio to Spkr Cntrl, private speaker to Off (calls routed through earpiece), backlight to Disabled, and the LED indicator is switched off. The radio powers up in the mode set before turning off. Covert Mode can be used as a One-Touch Button. When Covert Mode is turned off, previous settings are reverted.

2.18 Packet Data

In TMO, the radio provides a TETRA bearer service for IP applications via the PEI. It operates on single-slot or multi-slot packet data channels (multi-slot is a Software Selling Feature). The radio supports TETRA standard multi-slot packet data using IP network layer protocol via PPP and TETRA SNDCP protocol. IP connection is established between Terminal Equipment and Mobile Terminal, allowing external applications to communicate using predefined IP addresses. Note: This IP connection is the "local link"; the link between radio and SwMI is the "wide link". When a wide link is established, the radio is in wide mode. Packet data applications reside internally over UDP or in an external device connected via RS232 or USB. Communication to external devices is initialized using AT commands. The system provides point-to-point IP connectivity for datagram exchanges between Radio <> External Equipment and External Equipment <> Network. The radio supports IP version 4 packets and routes datagrams independently of the protocol above IP. It has an MTU of 1500 bytes and provides best-effort delivery. Delivery may fail due to no radio coverage, transmission failure, or service interaction. Packet Data Channel (PDCH) access signaling has the same priority as circuit mode setup. The radio uses an advanced link for packet data transmission and supports advanced link flow control, including advanced link roaming if the link does not disconnect between cells. The radio does not support data compression; negotiation attempts are rejected, and compressed IP packets are discarded. It supports negotiation of IP header compression transparently transferring packets between Terminal Equipment and SwMI. Packet data service suspends during cell reselection, resuming afterward. Note: Cell reselection is undeclared in strict TETRA, but SNDCP protocol defines a reconnection procedure resembling unannounced cell reselection.

2.18.1 Voice and Data Support

The radio can alternate voice and packet data service but not run them in parallel (Packet Data Type B - IP dual mode). If context activation is rejected due to PD MS type not supported, the radio re-initiates with Type C support for legacy SwMIs. The radio supports transmitting and receiving SDS on the Packet Data Channel (PDCH), allowing parallel operation. It operates in one of three voice-data interaction modes: Voice Only (PD service disabled, local PEI mode only), Data Only (normal voice calls not permitted, emergency calls allowed), or Voice and Data (voice takes priority over data, suspending PD sessions until voice activity ends; voice priority is default). Mode choice is stored in non-volatile memory. In Voice and Data mode, voice service on a traffic channel suspends packet data transmission/reception, resuming after voice service ends. The radio accepts downlink SDS on PDCH and can send uplink SDS on PDCH. PEI, GNSS/GPS, and WAP packet data applications can activate and use the packet data context simultaneously. The first application initiates context activation; subsequent activations result in a reply indicating the context is active. When WAP, GNSS/GPS, and PEI PD applications are active, the radio filters downlink IP packets based on TCP/UDP port, routing them to respective applications or PEI via PPP. Note: When activating another PD context, use the same settings in both.

2.18.2 Packet Data IP Addressing

Table 5 details Packet Data IP Addressing modes: Wide IP Address (assigned by SwMI during PD context activation), Local IP Address (default, used for local datagram transmissions between TE and MT, not passed to SwMI), and Static or Dynamic IP Address Assignment (dynamic requested for internal PD applications or PEI PD applications requesting it).

2.18.3 Packet Data User Authentication

Packet Data (PD) user authentication verifies the Terminal Equipment user before allowing PD link activation. A PD Authentication server authenticates the user. The terminal sends messages between TE and SwMI. In wide mode, the terminal offers PPP user authentication between MT and TE using PAP or CHAP, always attempting CHAP negotiation but agreeing to PAP if insisted by the TE application. If PD user authentication is not required, the terminal operates without it. If required and not met, PD context activation is rejected. Note: SwMI can reject authentication methods like PAP.

2.19 TETRA Network Protocol 1

TETRA Network Protocol type 1 (TNP1) is a bridge protocol based on TETRA layer 3 over the air protocol, supporting all TETRA dispatch functionality. In TMO, TNP1 specifies a protocol for PEI use, allowing TE control over TETRA services: mobility management, call control, short data service, and supplementary services (sending GNSS/GPS reports, software info, battery state). Commands for radio configuration and storage parameters are also available. The radio supports TETRA standard packet data using IP network layer protocol, operating on single-slot or multi-slot packet data channels. Packet data applications reside internally (GNSS/GPS, WAP) or in external devices connected via RS232 or USB, initialized using AT commands. The system provides point-to-point IP connectivity for datagram exchanges. The radio supports IP version 4 packets. TNP1 services can use PPP methods: local mode (all TNP1 services except packet data transfer to SwMI, using static TE IP: 10.0.0.101 and MT IP: 10.0.0.100) and wide mode (all TNP1 services including packet data transfer to SwMI, using dynamic MS IP or configured static address). Port Addressing uses a fixed port address (4024) for TNP1 packet reception/transmission. TNP1 should be used in wide-mode for parallel operation of TNP1-SDS and packet data services. If transmit inhibit is entered, the wide mode connection drops, PEI returns to AT mode, and the TNP1 client reinitiates PPP in local mode. The radio disables TNP1 session in DMO. AT commands initiate PPP service for TNP1; once PPP is running, AT commands are blocked until PPP session closes.

2.19.1 TETRA Network Protocol 1 IP Addressing

Table 6 outlines TETRA Network Protocol 1 (TNP1) IP Addressing: Wide Mode (all TNP1 services including packet data transfer towards SwMI, using dynamic MS IP or configured static address), Local Mode (all TNP1 services except packet data transfer, using static TE IP: 10.0.0.101 and MT IP: 10.0.0.100), and Port Addressing (fixed port 4024 for TNP1 packets).

2.20 Over The Air Programming

Note: This is a Software Selling Feature.

Over The Air Programming (OTAP) enables remote radio reconfiguration, eliminating the need for grounding or sending radios to service centers for updates. The OTAP tool allows operators to create and prepare an update package for sending to destination radios. Upon receiving the package, the recipient radio prompts for acceptance, enabling the update. Progress guidance and status are provided. Radio self-recovery is available for update failures. Contact your radio administrator or service provider for support if the new configuration is not working. Note: OTAP operates on TMO only.

2.21 Mobility Services

Terminal mobility is the ability of terminals to acquire, register, and operate on an appropriate TETRA network, changing cells with minimal service interruption. The radio maintains stored lists of carrier frequencies scanned in order: last 32 control channels used, up to 32 preprovisioned discrete frequencies, a frequency range specification with offset, and an extra frequency range specification. These lists speed up registration after power cycle or TMO coverage loss.

2.21.1 Main Control Channel Frequencies

The radio can find a wide range of main control channels, maintaining stored lists of carrier frequencies scanned in order: last 32 control channels used, a static list of up to 32 preprovisioned discrete frequencies, a frequency range specification using a specific offset, and an extra frequency range specification. These lists help speed up registration after power cycle or TMO coverage loss.

2.11.2 Channel Selection

Each TDMA frame comprises four time slots, usable as physical channels: Traffic physical (TP), Control physical (CP), Packet Data Control (PDCH), and Unallocated physical (UP). Control channels include Main Control Channel (MCCH) on the first slot of the main carrier, and Secondary Control Channels (SCCHs) which can extend control channel capacity. Note: SCCH is a Software Selling Feature. A cell can have up to three common SCCHs, distributing population across up to four channels to increase control channel capacity at the expense of traffic channel capacity. The radio uses MCCH until receiving a specific parameter, then maps to a particular common SCCH which acts as MCCH.

2.21.3 Multi-System Operation

The radio holds a list of up to 100 allowed network identities (MCC/MNC combinations), considered friendly networks, with the first entry being the home network. Each network can have an associated name. The radio can perform initial cell selection and registration on these networks using its ISSI without migration signaling. Registration can be limited to the home network, a selected network, or any network. If the Base Transceiver Station (BTS) does not support ETSI migration, multi-system operation is limited. Users can change network mode via MMI (Networks Sel: Home Only, Select Net, Any Net). "Select Net" displays a list of provisioned network names. The network alias or MNI of the current network is shown on the idle display. "Any Net" automatically selects an available network from the codeplug list if the home network is unavailable. Network selection to another network occurs at initial cell selection after a link failure if the home network is unavailable. The radio operates in all networks as it does in its home network; SwMI rejects communications for unreachable subscribers or groups. Note: The telephone gateway interprets telephone numbers with the country code of the local country.

2.21.4 Registration

Upon camping on a cell, the radio sends a registration request PDU to the SwMI, including an attachment request for the selected talkgroup. Successful registration and attachment initiate normal operation. If registration times out or is temporarily rejected, another attempt is made. If both fail, the radio tries a different cell. If SwMI denies registration due to location area rejection, the radio does not attempt registration at that cell until next power-on. The radio supports modification of its subscriber class upon receiving a new class from SwMI in the registration acknowledgment PDU, which remains active until power-off or next ITSI attach. The radio does not send registration signaling during certain scenarios like roaming failure before random access acknowledgment, or short link failures on the serving cell (unless in transmit inhibit mode). If a link failure occurs and persists beyond a timer, normal link failure procedures apply. If the failure ends before the timer expires, the radio returns to the serving cell without registration. This avoids unnecessary registrations. If the radio is out of serving cell range for less than a configured time, it does not register upon return.

2.21.5 Cell Roaming

The radio continuously monitors neighbor cells, scanning the highest ranked one. When a neighbor cell's state is significantly better than the serving cell, or the serving cell is lost, cell reselection procedures are employed: undeclared for non-calls, unannounced for calls without transmission or link failure, and announced type-1/type-2 or type-3 for calls with transmission. The radio can be provisioned to never perform type-1 or type-2 reselections for compatibility. Cell reselection decisions are based on signal strength and service level criteria: System Wide Services, Subscriber Class, relinquishing criteria, Preferred MNI, congestion level, Security Class, QAM availability, Home Location Area, Location Area Boundary, Cell Load, and Local Site Trunking (LST) Services. The radio prefers cells with higher service levels. If operating on a lower service level cell than a neighbor, it roams to the neighbor, even during a call. During network reconfiguration, widespread roaming can cause congestion; roaming times are randomized to distribute registration attempts. Link failures and related scenarios are not randomized to avoid delays.

2.21.6 Seamless Handover

Seamless handover eliminates voice interruption during calls by enabling faster roaming between cells while transmitting. The radio requests the serving cell to perform reselection, and the SwMI handles roaming signaling. The radio then moves directly to the traffic channel on the new cell, continuing the call without restoration.

2.17 Networks

The radio holds a list of 101 allowed network identities (MCC/MNC combinations), including one home network and 100 foreign networks. Each network can have an associated name. The radio can perform initial cell selection and registration on these networks. Registration can be limited to the home network only, a selected network, or any network. The radio selects the network registration method based on CPS configurations: Migration Signaling (registers using migration signaling, allowing talkgroup attachment in foreign networks), ITSI Attach (registers using regular ITSI attachment), or Automatic (uses migration signaling or ITSI attachment based on network capabilities). The radio operates in all networks similarly to its home network, with configurable behavior. Group calls use SSI addresses; SwMI rejects calls for unreachable groups or connects them to foreign systems. Individual calls use SSI for intra-network and TSI for internetwork calls. If ITSI Attach or Migration Encryption is enabled, foreign network features like Authentication, Air Interface Encryption (AIE), and Encryption are configurable in CPS. Note: The telephone gateway interprets telephone numbers with the local country code.

2.21.7.1 Migration

Note: This is a Software Selling Feature.

The Migration feature enables the radio to migrate and register to a foreign network using migration signaling, allowing attachment to talkgroups in that network. Key functions include automatic migration to an available network if talkgroup changes to one on a different network or if signal is lost (useful for establishing communication with any available network). Service providers must preconfigure the codeplug with networks before assigning them to talkgroups. The service provider can set registration methods per network or use an automatic method based on network broadcast. Migration supports individual calls, group calls, and individually addressed SDS or Status messages. To receive group calls or group-addressed SDS/Status messages from other networks, the attached talkgroup must be configured as an ISI talkgroup in the SwMI. The radio cannot migrate to a foreign network during an active call.

2.21.7.2 Network Selection

Users can select one or multiple preprogrammed networks for radio registration. These options are available in TMO or Gateway mode: Network Sel (allows selecting the registration network), Home Only (registers only to home network), Select Net (manually selects a preferred network), and Any Network (automatically selects an available network if home network is unavailable). TG Net Sel is available for Any Net or Inter-System Interface (ISI) talkgroups, allowing selection or priority definition of networks associated with the talkgroup. Options include Home Only, Select TG Net (displays available networks for a selected talkgroup), Prefer TG Net (displays available networks with priority), and Any TG Net (registers to any available networks of a selected talkgroup). If the radio selects a different network, it may force initial cell selection. Network names correspond to provisioned MNIs.

2.21.8 Congested Cell Handling

This feature applies only during initial registration and roaming. When a cell being registered to is congested, a level-based algorithm waits for registration or rejects it. The terminal recognizes cell congestion (Control Channel Congestion) and prioritizes non-congested cells for roaming. Congested cells are ranked secondary. Cells that are the last suitable cell or the serving cell are never marked as congested. The feature is configurable via CPS.

2.11.9 Subscriber Class

Upon power-up, registration, or roaming, the radio uses its provisioned Subscriber Class (SC). If it registers on a cell not supporting its SCs, it operates only in emergency priority services. If the radio's SC does not match the cell's SC (configurable), it uses normal ranking procedures or does not roam to the cell.

2.21.10 Subscriber Class by Talkgroup

Note: This is a Software Selling Feature.

Up to 16 Subscriber Classes can be configured via CPS by assigning talkgroups. Talkgroups can be assigned to multiple Subscriber Classes via GSSI or folder (excluding Favorite). If assigned to multiple classes, the first assigned is used. A radio's Subscriber Class changes when the user switches to a talkgroup with a different SC. An SC received over-the-air from SwMI has higher priority than SC by Groups. This feature is useful for preserving traffic channel capacity and distributing radios across cells, preventing roaming to mismatched cells. It does not apply to supergroups, considered scanned groups.

2.21.11 RF Power Class Toggle

Note: This is a Software Selling Feature.

The RF power toggle allows transmission with Class 3L power. CPS allows setting transmission power to Class 3L or Class 4. Depending on codeplug settings, users can toggle between high and normal RF power via the interface. The radio can be configured to automatically switch to Class 3L in DMO and Class 4 in TMO. Changes are immediate and may drop communication if the selected power class is insufficient.

2.21.12 Local Site Trunking

Note: This is a Software Selling Feature.

Local Site Trunking (LST) enables a Base Station to operate stand-alone when the link to the central switch fails. The radio limits functionality in this mode. Note: Radio registration on LST cells depends on codeplug settings. If system broadcasts indicate LST (system-wide services unavailable), the radio registers only if no system-wide cells are available. Depending on infrastructure settings, LST mode may prevent services like Private call, Phone call, PABX call, Packet data, and SDS data. LST notification can be visible/audible, visible only, audible only, or none. The Local Site Trunking Ignoring feature can be enabled to temporarily ignore LST/WST parameters during site selection, while still considering RSSI levels.

2.21.13 Cell Surveillance and Monitoring Threshold

The radio constantly calculates a normalized signal strength value for a cell to determine usability and when to leave it. By default, if this value falls below zero while camped on a cell, link failure procedures are initiated. However, CPS allows configuring this value below zero (up to -5 dB) to maintain service on weak cells where roaming to better cells is not possible.

2.22 Supplementary Services

This section describes TETRA Supplementary Services (SS) supported in TMO.

2.22.1 Dynamic Group Number Assignment

The radio supports dynamic addition and removal of talkgroups via TETRA DGNA and De-assignment signaling (SS-DGNA). It responds to DGNA directed to it or to a group it is attached to, even if the talkgroup is not programmed. Upon receiving a DGNA request to add a talkgroup, it's added to the first available spot in the talkgroup list. The codeplug determines DGNA operations allowed per group: Static (selection only), Semi-Static (selection and reassignment), and Dynamic (selection, de-assignment, reassignment). Groups can be assigned as not attached, attached as scanned (added to SwMI Controlled scan list), or attached as selected (becomes the radio's selected group). If the talkgroup list is full, assignment is rejected. If the SwMI controlled list is full, attachment as scanned is rejected. Upon de-assignment, depending on codeplug settings (DGNA Operations field), the radio leaves the talkgroup, removes it from folders, and sends an acknowledgment. If the talkgroup is deleted or does not exist, the acknowledgment still confirms removal. Even if de-assigned, the radio can receive group calls or emergency group calls for assigned scan lists. De-assignment of a scan list group means it remains in the list but is not monitored. De-assignment from SwMI controlled list removes it. If the de-assigned group was the selected group, the radio may notify "no group attached", attach to the previously selected talkgroup, or attach to a default talkgroup. Each talkgroup change shows a notification. De-assignment of an announcement group removes it and its associated groups' announcement association. If the currently selected talkgroup was associated, scanning of the announcement group stops. DGNA user notification can be provisioned. Viewing an assigned talkgroup notification allows making that group the selected group. The radio supports DGNA assignments addressed to its selected talkgroup as a supergroup, monitoring all signaling addressed to it. When the selected group is unselected, processing of supergroup signaling stops. The radio receives the supergroup lifetime and stops monitoring if a subsequent assignment is not received within that lifetime. It also supports supergroups of scanned groups. The following DGNA functions are not supported: Call-related DGNA, authorized user functionality, and network authentication before DGNA acceptance.

2.22.2 Ambience Listening

The Ambience Listening (AL) feature allows a console operator to monitor audio near a specific radio without indication to the radio. Upon receiving an AL call setup message, the radio accepts it, opens the microphone, and transmits without indication. Call acceptance/rejection follows PPC rules. No time limit is imposed; transmission continues until SwMI ends the call or the user performs a call-releasing action. Attempting to start a service during an AL call disconnects the call and initiates the service. Actions not requiring call release (menu access, scan list activation/deactivation, talkgroup changes) are allowed. Talkgroup changes appear as successful attachments, with actual signaling performed after AL call termination. If the radio is powered down during an active AL call, it enters Pseudo Power-Off state.

2.22.3 Pseudo Power-Off

If a user attempts to power down the radio during an active Ambience Listening (AL) call, the radio appears to turn off but remains fully operational below Layer-3. The screen is blank, and all LEDs are off. When the AL call ends in this state, the radio automatically turns off. Powering up from pseudo power-off state resumes normal operation.

2.22.4 Auto Power-On

The radio can be configured via CPS to turn on automatically after battery insertion. If emergency mode was active before battery removal, the radio enters this mode upon power-on if the power-off period was short (approx. 3 seconds). This applies to normal and silent emergency modes.

2.22.5 Preemptive Priority Call

If, during a call, a call setup for a higher priority call is received (Preemptive Priority 3 or 4 - Emergency), the radio disconnects from the present call and joins the new one. For Preemptive Priority 1 or 2, the radio accepts or rejects based on configuration. Acceptance triggers a special tone and notification. When initiating a private call and receiving a "Called party busy" rejection, users can interrupt the existing call or initiate a new one with preemptive priority.

2.22.6 Transmit Inhibit Mode

Transmit Inhibit (TXI) Mode prevents radio transmissions, suitable for RF sensitive areas like hospitals or airplanes. Activate via Menu > Networks > TXI Mode > Activate. In this mode, transmissions are prevented except for Emergency Calls. Functions causing transmission (registration, talkgroup/folder change, SDS sending, PTT press) are disabled. Transmission attempts display "Not Allowed In TXI Mode" and play a tone. The radio can still receive group calls, messages (stored in Inbox), and private call attempts (stored in Missed Calls list, without response option). Deactivate TXI Mode via Menu > Networks > TXI Mode > Deactivate, a One-Touch Button, or implicitly by initiating an Emergency Call. Note: RF transmissions are prevented if TXI Mode is activated, battery is removed, or the radio is turned off. Entering or exiting TXI mode sends an SDS status message to the SwMI. Mobility procedures not requiring uplink transmission are performed.

2.23 Man Down

Details the Man Down operation.

2.24 Vibrate Mode

Details the Vibrate Mode functionality.

2.25 SDS Remote Control

Provides information on SDS Remote Control functionality.

Figure 11: SDS Remote Control Overview - A diagram showing the overview of SDS Remote Control.

2.26 Status Remote Control

Provides information on Status Remote Control functionality.

2.27 Call-Out

Details Call-Out interactions and templates.

2.28 Radio Messaging System

Provides information on the Radio Messaging System.

Figure 12: RMS Flow Model with SDS TL - A diagram showing the RMS flow model with SDS TL.

Figure 13: RMS Flow Model with STS TL - A diagram showing the RMS flow model with STS TL.

2.29 Global Navigation Satellite System (GNSS) Location Service

The radio supports GNSS location services, including GNSS over Packet Data, Military Grid Reference System, different Location Displays, Accuracy, and Location Report Backlog. Tables 7 and 8 provide further details.

2.30 Side Connector

Details the functionality of the side connector.

2.31 Wireless Application Protocol (WAP)

The radio supports WAP, including WAP Browser and WAP Push (Framework, Service Indication, Service Load). Figure 14 illustrates the Push Framework.

2.32 Radio User Assignment and Radio User Identity

Details Radio User Assignment and Radio User Identity (RUA/RUI) functions: Log On, Behavior, and Interactions.

2.33 Radio Mass Storage

Details the Radio Mass Storage capabilities.

2.34 Bluetooth

Details Bluetooth functionality: Interactions, Restrictions, Sensor Data, Proximity Pairing, and Low Energy Indoor Location.

Chapter 3: Man-Machine Interface

3.1 LED Indications

Details LED Indications. Tables 9 and 10 provide specific information.

3.2 Battery Charging Indications

Details Battery Charging Indications. Table 11 and Figure 15 (Charger Mode Screen) provide details.

3.3 MTP8000Ex Series Controls and Indicators

Details the controls and indicators of the MTP8000Ex Series. Table 12 lists these components.

3.4 Software Keypad

Describes the software keypad functionality.

3.5 Keypad Lock

Describes the Keypad Lock feature.

3.6 Automatic Keypad Lock

Describes the Automatic Keypad Lock feature.

3.7 One-Touch Buttons

Details the functionality of One-Touch Buttons. Table 13 lists their features.

3.8 Display

Describes the radio's display. Tables 14, 15, and 16 provide details on display elements, soft key areas, and status icons. Figure 16 shows the Default Home Screen with Icons.

3.8.1 Status Icons

Details the various status icons displayed on the radio. Table 16 lists these icons.

3.8.2 Idle Display

Describes the Idle Display screen.

3.8.3 Configurable Idle Screen

Describes the ability to configure the Idle Screen.

3.8.4 Display Features

Details general display features.

3.8.5 Languages Supported

Lists the languages supported by the radio. Table 17 provides details.

3.9 Tones

Details the radio's tones. Table 18 lists the radio tones.

3.10 Description of Tones

Provides descriptions of the radio's tones. Table 19 categorizes these tones.

3.11 Dual Microphones

Describes the functionality of the dual microphones.

3.12 Audio Toggle

Describes the Audio Toggle feature.

3.13 Volume Control

Describes the volume control functionality.

3.14 Volume Adjustment Mode

Describes the Volume Adjustment Mode.

3.15 Accessory (Accry) Setup

Details the setup for accessories.

3.16 Audio Features

Details various audio features: Audio Profiles, Transmit Automatic Gain Control, and Howling Suppression.

3.17 Test Page

Describes the Test Page functionality.

3.18 Radio Info

Describes how to access Radio Information.

3.19 Hardware Test

Describes the Hardware Test functionality.

Appendices

Appendix A: Service Information – EMEA

Provides service information for EMEA.

Appendix B: Service Information for APAC

Provides service information for APAC. Table 20 lists telephone numbers and addresses of Motorola Solutions Centers.

Appendix C: Service Information – Americas

Provides service information for the Americas. Tables 21 and 22 list telephone numbers and addresses of Motorola Solutions Centers.

Glossary

Provides definitions for terms used in the manual.