OTAK

Over-The-Air-Key Management (TETRA)

Security →
Introduced in Rel-15

OTAK is a TETRA security mechanism for the over-the-air management, distribution, and updating of cryptographic keys to ensure communication confidentiality and integrity.

Category
Security
Introduced
Rel-15
Where
Services › IMS
Specifications
3 specs
OTAK Description Purpose Related Classification Detected Changes Specifications

Description

Over-The-Air-Key Management (OTAK) is a standardized security procedure defined within 3GPP specifications for Terrestrial Trunked Radio (TETRA) systems. TETRA is a digital mobile radio standard widely used by public safety organizations, transportation services, and utilities for mission-critical voice and data communications. OTAK operates within the TETRA security architecture, specifically addressing the lifecycle management of cryptographic keys used for air interface encryption (AIE) and end-to-end encryption (E2EE). The core function is to securely deliver new or updated encryption keys from a Key Management Facility (KMF) to TETRA mobile stations (MS) or terminals without requiring physical access to the device.

The architecture involves several key entities: the Key Management Facility (KMF), which is the trusted authority generating and distributing keys; the TETRA infrastructure, including base stations (TBS) and switching and management infrastructure (SwMI); and the TETRA Mobile Station (MS). The KMF uses the existing TETRA signaling channels to transmit key management messages. These messages are themselves protected using existing keys or a hierarchy of keys, ensuring that new key material is delivered securely. The process typically involves the KMF encrypting the new traffic encryption key (TEK) or group key using a key encryption key (KEK) that is already securely stored on the mobile station.

OTAK procedures are defined to handle various scenarios, including initial key provisioning, periodic key updates for enhanced security (rekeying), and emergency key revocation in case a key is compromised. The protocol ensures that only authorized devices receive the keys, often using identifiers like the TETRA Subscriber Identity (TSI) and group identifiers. The successful delivery and activation of a new key are acknowledged by the mobile station back to the KMF, providing assurance of the key management process. This over-the-air capability is crucial for large fleets of devices where manual key loading is impractical, enabling scalable and responsive security management for critical communication networks.

Purpose & Motivation

OTAK was created to address the significant operational and security challenges of manual key management in large-scale, professional mobile radio systems like TETRA. Prior to OTAK, cryptographic keys were often loaded into radios via physical connections (e.g., key fill devices or cables), a process that is time-consuming, logistically difficult, and prone to error for organizations with hundreds or thousands of deployed devices. For public safety and critical infrastructure operators, the inability to quickly change encryption keys across an entire fleet represented a major security vulnerability, especially if a device was lost, stolen, or a key was suspected to be compromised.

The motivation for OTAK stems from the need for dynamic, remote security management that matches the operational tempo of modern critical communications. It solves the problem of maintaining cryptographic agility—the ability to change encryption algorithms or keys rapidly in response to evolving threats. By enabling over-the-air updates, OTAK allows network operators to enforce security policies, perform regular key rotations to limit the impact of potential cryptanalysis, and instantly invalidate keys across the network during security incidents. This capability is foundational for maintaining the long-term confidentiality of sensitive communications in government, emergency services, and industrial applications that rely on TETRA technology.

Classification

Part ofTETRA

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-15, normative work from Rel-16.

Rel-16 2 changes

In Release 16, the new OTAK function introduced Functional Alias management for interworking between the MC service system and LMR system. This enhancement specifically defined group management procedures and information flows over the IWF-3 reference point, such as IWF group information provision and subscription requests. These procedures enable the secure synchronization of group configurations and affiliation statuses between the systems.

  • Functional Alias management for interworking between MC service system and LMR system TS 23.283CR0035
  • Functional Alias management for interworking between MC service system and LMR system TS 23.783CR0035
Rel-20 1 change

In Release 20, a key change for OTAK was a correction to ensure that Land Mobile Radio (LMR) Key Management messages apply exclusively to the MCData service. This refinement specifically targeted the interworking procedures, focusing the key management mechanisms on securing encrypted interworking for that particular mission-critical service rather than a broader application.

  • Correction for LMR Key Management Messages to apply only to MCData service TS 23.283CR0101

Explore further

Broader topics and technologies where OTAK plays a role.

Defining Specifications

3GPP specifications that define or reference OTAK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.283 vk00 Mission Critical Communication Interworking Rel-20
TR 23.783 vi00 Technical Report on Mission Critical Services over 5GS Rel-18
TS 24.883 vg00 MCPTT Interworking with LMR Systems Rel-16