Osmocom TETRA PHY/MAC implementation https://osmocom.org/projects/tetra
Go to file
wbokslag c0956b968f Added crypto support
Added TETRA cryptographic primitives (TEA1-3, TAA1 minus TA61).
If a keyfile is loaded (using -k flag), matching signalling frames
will be decrypted. No support for traffic or identity encryption
yet. Based on https://github.com/MidnightBlueLabs/TETRA_crypto

Change-Id: I0c0227cf5b747bd5032602390175b898173f6ae6
2023-09-02 08:54:40 +00:00
contrib jenkins: use common osmo-build-dep.sh and osmo-clean-workspace.sh 2017-10-30 05:01:41 +01:00
etsi_codec-patches Fix typos 2019-07-17 22:50:49 +02:00
src Added crypto support 2023-09-02 08:54:40 +00:00
AUTHORS add AUTHORS file 2011-01-22 12:26:27 +01:00
COPYING add COPYING (AGPLv3) and README file 2011-01-19 10:40:19 +01:00
README.md update git URLs (git -> https; gitea) 2022-06-18 13:50:02 +02:00
TODO add TODO file 2011-01-22 12:46:33 +01:00


TETRA MAC/PHY layer experimentation code

(C) 2010-2016 by Harald Welte laforge@gnumonks.org and contributors

This code aims to implement the sending and receiving part of the TETRA MAC/PHY layer.

If you read the ETSI EN 300 392-2 (TETRA V+D Air Interface), you will find this code implementing the parts between the MAC-blocks (called type-1 bits) and the bits that go to the DQPSK-modulator (type-5 bits).

It is most useful to look at Figure 8.5, 8.6, 9.3 and 19.12 in conjunction with this program.

You will need libosmocore to build this softwar


The official homepage of the project is https://osmocom.org/projects/tetra/wiki/OsmocomTETRA

GIT Repository

You can clone from the official osmo-tetra.git repository using

git clone https://gitea.osmocom.org/tetra/osmo-tetra

There is a web interface at https://gitea.osmocom.org/tetra/osmo-tetra

Mailing List

Discussions related to osmo-tetra are happening on the tetra@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/tetra for subscription options and the list archive.

Please observe the Osmocom Mailing List Rules when posting.


Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards

We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details

The current patch queue for osmo-tetra can be seen at https://gerrit.osmocom.org/#/q/project:osmo-tetra+status:open



  • contains a gnuradio based pi4/DQPSK demodulator, courtesy of KA1RBI


  • call demodulator on any source supported by gr-osmosdr (uhd, fcd, hackrf, blaerf, etc.)


  • call demodulator on a 'cfile' containing complex baseband samples


  • use demodulator directly with UHd or FCDP hadware (no gr-osmosdr)

The output of the demodulator is a file containing one float value for each symbol, containing the phase shift (in units of pi/4) relative to the previous symbol.

You can use the "float_to_bits" program to convert the float values to unpacked bits, i.e. 1-bit-per-byte

PHY/MAC layer

library code

Specifically, it implements: lower_mac/crc_simple.[ch]

  • CRC16-CCITT (currently defunct/broken as we need it for non-octet-aligned bitfields) lower_mac/tetra_conv_enc.[ch]
  • 16-state Rate-Compatible Punctured Convolutional (RCPC) coder lower_mac/tetra_interleave.[ch]
  • Block interleaving (over a single block only) lower_mac/tetra_rm3014.[ch]
  • (30, 14) Reed-Muller code for the ACCH (broadcast block of each downlink burst) lower_mac/tetra_scramb.[ch]
  • Scrambling lower_mac/viterbi*.[ch]
  • Convolutional decoder for signalling and voice channels phy/tetra_burst.[ch]
  • Routines to encode continuous normal and sync bursts phy/tetra_burst_sync.[ch]

Receiver Program

The main receiver program 'tetra-rx' expects an input file containing a stream of unpacked bits, i.e. 1-bit-per-byte.

Transmitter Program

The main program conv_enc_test.c generates a single continuous downlinc sync burst (SB), contining: * a SYNC-PDU as block 1 * a ACCESS-ASSIGN PDU as broadcast block * a SYSINFO-PDU as block 2

Scrambling is set to 0 (no scrambling) for all elements of the burst.

It does not actually modulate and/or transmit yet.

Quick example

# assuming you have generated a file samples.cfile at a sample rate of
# 195.312kHz (100MHz/512 == USRP2 at decimation 512)
src/demod/python/tetra-demod.py -i /tmp/samples.cfile -o /tmp/out.float -s 195312 -c 0
src/float_to_bits /tmp/out.float /tmp/out.bits
src/tetra-rx /tmp/out.bits