DXT3TM Product Description

EADS TETRA System

Release 5.5 with DXT3TM

DXT3TM Product Description

TRADXTAPP00028-01en

09/2009
 The content of this document and its appendices and any information provided (all together
"document") is for information purposes only and is subject to change without notice.
The document only specifies the products and services identified in the document. The
document is confidential and contains legally privileged information.

The document is only intended for the use of the recipient and the customer whose
representative the recipient is, and may only be used for the purposes for which the
document is submitted. The document or any part of it may not be reproduced, disclosed
or transmitted without the prior written permission of EADS Secure Networks.

EADS Secure Networks will reasonably ensure that the information provided in the document is
free from material errors and omissions. However, the suggestions, directions, comments and
statements made in the document (e.g. regarding the compatibility, performance and functionality
of mentioned hardware and software) are not intended to be and cannot be considered as binding.
The customer assumes full responsibility for using the document or any part of it. All comments
and feedback are welcomed by EADS Secure Networks and are used as part of the continuous
development and improvement of EADS Secure Networks’s products, services and the document.

EADS Secure Networks disclaim and exclude all representations, warranties and conditions
whether express, implied or statutory, including but not limited to the correctness, accuracy
or reliability of the document, or otherwise relating to the document. EADS Secure Networks’
total liability for any errors in the document is limited to the documentary correction of
errors. EADS Secure Networks will not be liable for any direct or indirect damages arising
from the use of the document or otherwise relating to the document.

EADS logo is a registered trademark of EADS. Other product names, trademarks or

other identifiers mentioned in the document may be trademarks of their respective
companies and are mentioned for information purposes only.

Copyright © EADS Security Networks, all rights reserved.

EADS Defence and Security

1 boulevard Jean Moulin
CS40001
78996 Elancourt Cedex - FRANCE
tel. +33 (0)1 61 38 50 00
fax : +33 (0)1 61 38 70 70
Email : TetraInfra.Helpdesk@eads.com

TRADXTAPP00028-01en DXT3TM Product Description

2(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Contents

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Introduction to the DXT3TM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Mechanics of various DXT versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 DXT3 in the EADS TETRA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Basic architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.1 Independent computer units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.2 Distributed architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.1 Digital switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.2 Call services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.3 Speech item allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.4 Database services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.5 Signalling services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.6 Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.7 Resource management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.8 Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.9 Charging services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.10 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.10.1 MTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.10.2 Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.10.3 Load observation measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.10.4 Field reporting measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.11 IP Packet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.12 ISDN PRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4.13 Authentication and Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1 DXT3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 DXT3 (HLR only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 SIPU dimensioning guidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 3(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 4.1 Internal communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1.1 Ethernet Message Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1.2 LAPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1.3 SCBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1.4 Changeovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2 Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.1 DXT3 - TETRA Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.2 DXT - Dispatcher Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2.3 DXT - PSTN/PABX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.4 DXT - conventional PMR systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.5 DXT - other TETRA exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.6 DXT - network management system (NetAct™ for TETRA) . . . . . . . . . . . . . . . . . . 38
4.2.7 DXT - other systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.8 DXT - TCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.9 DXT - CDD server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.1 LAPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.2 TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.3 Q3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.4 MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.5 FTP/SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.6 OSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.7 EMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.8 Telnet/SSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.9 FTAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.1 Implementation system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.2 Semipermanent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.3 DXT3 databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3 Programming languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1 DXT HW principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.1.1 Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.1.2 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.1.3 Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2 Description of DXT3 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

TRADXTAPP00028-01en DXT3TM Product Description

4(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 6.2.1 Functional units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.2.2 Cabinet mechanics and cabling modules of DXT3. . . . . . . . . . . . . . . . . . . . . . . . . 52
6.3 Basic HW configuration and optional equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7 Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.1 Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2 Duplication (redundancy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.1 2n redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.2 Replaceable n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.2.3 Complementary n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.2.4 No redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

8 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1 Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1.1 Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.1.2 Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.1.3 Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.1.4 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.1.5 Diagnostic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.2 Network maintenance functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.2.1 Network supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.2.2 Supervision of 2-Mbit/s circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.2.3 Compilation of disturbance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.3 Network management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.4 Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.4.1 Network synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.4.2 The clock system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.4.3 Real time clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

9 Technical data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.1 Basic technical features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.2 Equipment room requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.3 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.4 Functional units and plug-in units of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.4.1 OMU, Operation and Maintenance Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.4.2 CLSU, Clock and Synchronization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
9.4.3 CLAB, Clock and Alarm Buffer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.4.4 GSW05KB, Switching Network Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9.4.5 CMM, Central Memory and Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.4.6 CCSU, Common Channel Signalling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.4.7 PDCU and SIPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 5(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 9.4.8 ET16 and ECE2-NT(C), Exchange Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
9.5 Basic hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

A Restriction of Hazardous Substances in the PRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

TRADXTAPP00028-01en DXT3TM Product Description

6(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
List of Tables.
Table 1 The different mechanics of the DXTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2 Capacity of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 3 Capacity of the DXT3 (HLR only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4 The supported SIPU configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 5 Plug-in unit sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 6 Basic HW configuration of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 7 Optional HW of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 8 Classification of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 9 Technical data of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 10 Plug-in units of OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 11 Plug-in units of CLSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 12 Plug-in units of CLAB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 13 512 PCM Bit Group Switch (GSWB) in SW05C-A cartridge . . . . . . . . . . . . . . . . . . . . 73
Table 14 Plug-in units of CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 15 Plug-in units of CCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 16 Plug-in units of PDCU and SIPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 17 Server IP Unit (SIPU 2) in CC4C-B cartridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 18 The basic hardware of the DXT3 (Functional units set and equipment) . . . . . . . . . . . . 80

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 7(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
List of Figures.
Figure 1 DXT3 with doors closed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 2 DXT3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 3 A single-DXT network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 4 DXT network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 5 DXT3 exchanges connected to ISDN/PSTN via an ISDN exchange . . . . . . . . . . . . . . 25
Figure 6 DXT3 exchanges connected to a private network with ISDN PRA . . . . . . . . . . . . . . . . 25
Figure 7 DXT3 - TBS interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 8 DXT - Dispatcher System Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 9 Functional units of the DXT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 10 Layout of the DXT3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 11 2n redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 12 Replaceable n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 13 Configuration of the DXT cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 14 Operation and Maintenance Unit (OMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 15 Clock and Synchronization Unit (CLSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 16 Clock and Alarm Buffer (CLAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 17 Group Switch (GSW05KB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 18 Central Memory and Marker (CMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 19 Common Channel Signalling Unit (CCSU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 20 SIPU and PDCU Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 21 Dual SIPU unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 22 SIPU 2 in CC4C-B cartridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 23 ET4C-B cartridge within the DXT3 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 24 Material declaration for the PRC markets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

TRADXTAPP00028-01en DXT3TM Product Description

8(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 DOCUMENT AMENDMENTS

VERSION DATE COMMENTS CHAPTER

UPDATED
01 08/2009 This is the first version of the document.

References

1. Numbering, dn00126527

2. Basic IP Packet Data Service, dn05221832

3. Enhanced IP Packet Data Service, dn05222516

4. TCS Product Description, dn0116031

5. Glossary, dn00126469

6. Charging Services, dn00126554

7. Charging Services DXT-Billing Centre Interface Description, dn00126566

8. Authentication in the EADS TETRA System, TRASYSAPP00003

9. Integrating the EADS TETRA System, dn05225513

10. Time Management in the EADS TETRA System, dn0484132.

11. Product Description for the EADS TETRA Dispatcher Workstation (DWS), dn05221844

12. Installing the DXTip, DXTTip and DXT3, dn064171

13. Environmental Requirements for B13 HW Platform Release, PI 364956. Version 3.0 en

14. ETSI EN 300 132-2, V2.1.2 (2003-09), Environmental Engineering (EE); Power supply interface
at the input to telecommunications equipment; Part 2: Operated by direct current (dc)

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 9(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

10(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

About this document

This document describes the EADS DXT3TM digital exchange.
The document gives the key technical data, comprising the hardware, software, capacity, and
management of the exchanges.
Some of the features, functions, and equipment of the EADS TETRA System described in this
document may not be available in all market areas or are separately priced commercial options. Please
contact your local EADS representative for further information.
We welcome any suggestions for further improvement of this document. Also, should you find any
errors or omissions in this document, please forward your comments to the local EADS representative
or send them via e-mail to tetra.cudo@eads.com.

How to use this document

This document is intended for anyone who wishes to receive the essential information on the
operation of the DXT exchange. The reader is expected to be familiar with the general principles of
telecommunications.
The document is organised as follows:
• Chapter 1 introduces the structure of the document.
• Chapter 2 gives an overall description of the DXT3 and explains its role in the EADS TETRA
System.
• Chapter 3 describes the capacity of the DXT3.
• Chapter 4 describes the internal communication of the DXT and its interfaces to the EADS
TETRA System and to external systems.
• Chapter 5 describes the DXT3 software.
• Chapter 6 describes the DXT3 hardware.
• Chapter 7 lists the resilience mechanisms of the DX3.
• Chapter 8 describes the management of the DX3.
• Chapter 9 lists the basic technical data.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 11(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 • The Appendix A provides information about the restriction of hazardous substances in the
People’s Republic of China.

The References section gives guidance to related documents. Abbreviations used in this document are
explained in the Glossary section. An Index is also provided at the end of the document.

TRADXTAPP00028-01en DXT3TM Product Description

12(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Introduction to the DXT3TM

This chapter introduces the DXT3TM as follows:

• general

• DXT3 in the EADS TETRA System

• basic architecture

• functions

2.1 General
The DXT3 is an access-layer and a transit-layer switch in the EADS TETRA System. The DXT3
is used in the EADS TETRA System as the switching element to which base stations, other DXT
exchanges, dispatching systems, network management centres, the CDD Server and external network
interfaces can be connected.

The DXT3 is built on the generic DX 200 fault-tolerant computing platform developed by Nokia Siemens
Networks. The DXT3 complies with the European Union RoHS Directive 2002/95/EC on the restriction
of the use of certain hazardous substances in electrical and electronic equipment to the extent
mandatory and applicable.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 13(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Figure 1 : DXT3 with doors closed

TRADXTAPP00028-01en DXT3TM Product Description

14(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Figure 2 : DXT3 block diagram

2.1.1 Mechanics of various DXT versions

The table below describes the mechanics of the DXTs. The mechanics currently in use are the M98F2.
Unless stated otherwise, the information in this document concerns these mechanics.

Table 1 : The different mechanics of the DXTs

DXT3 access or transit layer switch (1–cabinet, M98F2 mechanics)

DXTip access layer switch (1–cabinet, M98F2 mechanics)
DXTTip transit layer switch (2 cabinets, M98F2 mechanics)
DXTip access layer switch (1–3 cabinets, M98F mechanics)
DXTTip transit layer switch (3 cabinets, M98F mechanics)
DXT256 access layer switch (4 cabinets, M92 mechanics)
DXTT transit layer switch (4 cabinets, M92 mechanics)

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 15(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.2 DXT3 in the EADS TETRA System
In the EADS TETRA System, the DXT3 is the centre of communications, supporting fast call set-up and
high traffic throughput. It serves as a transit level exchange in a hierarchical network. There is typically
one transit level exchange for each 6 to 10 access level exchanges in the network.

The DXT3 has the following advantages:

• high reliability

• compact design

• easy installation

• scalability

• flexibility

• easy and low-cost maintenance

• new features easy to implement by updating the software

• low power consumption.

TETRA Base Stations (TBS) and EADS TETRA Dispatcher Workstations (DWS) can be connected to
the DXT3 via Exchange Terminal (ET) units. The TETRA Base Station family of the EADS TETRA
System has variants for different frequency bands. The TETRA Connectivity Server (TCS) is connected
with a TCP/IP LAN segment to the Server IP Unit (SIPU) of the DXT3.

The CDD Server acts as a data replicator and a data cache. The CDD Server is connected to the
SIPU of the DXT.

A network can consist of just one DXT with the required amount of TBSs. Figure 3 shows a network
with one DXT. In single-DXT networks, it is possible to use the Integrated data distribution function
instead of the CDD Server. Integrated data distribution functionality enables the distribution of
information, for example radio subscriber tracking data, from the system to the dispatchers. The CDD
server is always required in networks with more than one DXT exchange.

In addition, the DXT contains interfaces to several other systems.

TRADXTAPP00028-01en DXT3TM Product Description

16(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 TB3-7
PSTN
TB3-6
ISDN PRA
TB3-5 (optional)

DXT

TB3-4

DWS
TB3-3

TB3-2 dn03474824 x2x0xen

TB3-1

Figure 3 : A single-DXT network

Figure 4 illustrates a more complex DXT network architecture, containing various DXT versions.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 17(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 TB3 64 /128 cells
64/320 carriers

DXTip
DXT3

MTP 64 kbit/s, (OEM 64 kbit/s) DXTTip

Voice line 8 kbit/s, (O&M 64 kbit/s)

PSTN line 64 kbit/s DXTTip DXTTip

DXT3
DXTip DXTip

TB3 TB3
DXTTip DXTTip

DXT3 DXTip DXTip DXT3

TB3 TB3

Dn0571814x3x0xen

Figure 4 : DXT network architecture

2.3 Basic architecture

2.3.1 Independent computer units

The DXT consists of computer units that communicate via message interchange. The computer units
are loosely coupled and independent.

A duplicated Ethernet Message Bus (EMB) supports the loose coupling of the computer units.

One of the computer units, the Operation and Maintenance Unit (OMU) is dedicated for operation
and maintenance tasks.

2.3.2 Distributed architecture

The distributed architecture of the DXT allows a process to communicate with another process in any
computer unit. In this way, the computer capacity allocation can be optimised. In other words, parts of
the capacity can be dimensioned for specific needs without affecting the whole system.

Each computer unit has a logical address, so it is easy to reconfigure functions to different computers.

TRADXTAPP00028-01en DXT3TM Product Description

18(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.4 Functions
The DXT provides the following functions:
• digital switching
• call services
• speech item allocation
• database services
• signalling services
• trunking
• resource management
• numbering
• charging services
• statistics
• data services
• IP packet data
• ISDN PRA connection to PSTN/PABX
• digital R2 connection to PSTN/PABX
• authentication
• connections to conventional base stations
• connections to recording systems.

These functions are described in more detail in the sections below.

In addition, the DXT participates in some of the EADS TETRA System’s general functions. These
include group management, subscriber management, mobility management, security management,
radio channel management, TBS management, DWS management, connection management between
the exchange and PSTN/PABX, and between the exchange and conventional PMR systems, system
maintenance, and configuration management.

2.4.1 Digital switching

The Switching Network Unit (GSW05KB) switches the 8-kbit/s subslots of the incoming PCM circuits
to the time slots of the outgoing PCM circuits determined by the computer which controls the switch
(the Central Memory and Marker, CMM). One 8-kbit/s subslot is always provided with one TETRA
speech frame.
The advantage of this type of operation is unambiguity: when the time slots to be switched are
known, the switching is always possible and always takes place in the same way without a special
path search procedure.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 19(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.4.2 Call services
Call services handle the traffic in the DXT. The main tasks are:
• checking the subscriber’s call rights
• starting and termination of calls
• time supervision during different call phases
• network resource reservation and release
• collection of charging data and statistical information.

Call services handle all these functions based on where the subscribers are located and what type
of calls they request.

2.4.3 Speech item allocation

Speech item allocation means giving speech turns within a group call and a semiduplex individual
call. This function
• detects incoming speech item requests
• finds the priorities of the requests
• decides who receives the next speech item based on the priorities and the order in which the
call requests have come.

Speech item allocation prevents two or more users from sending simultaneous speech items, because
there can only be one speaker at a time in a semiduplex call. In duplex calls, both parties can speak
simultaneously, without having to wait for a speech item.
In addition, speech item allocation supervises the inactivity times of calls and maintains the speech
item allocation timers.

2.4.4 Database services

The DXT contains several databases. For more information, refer to Section 5.2 .

2.4.5 Signalling services

The DXT uses signalling services for the following purposes:
• TCP/IP
– for connecting to the CDD Server and IP Packet Data Service
– for connecting to the TETRA connectivity server for third party applications.
• LAPD
– for connecting to TETRA Base Stations,

TRADXTAPP00028-01en DXT3TM Product Description

20(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 – for connecting to Dispatcher Systems for TETRA
– for internal communication CL3TG and ET units.
• RS232 for connecting to MML terminals and line printers.
• EMT signalling
– the EMT protocol is used for TCP/IP connections to the CDD and the TCS.
• Digital R2 signalling for connecting to the PSTN/PABX.
• Digital ISDN PRA signalling for connecting to the PSTN/PABX.
• Digital interface (G4WIF) for connecting to conventional analog PMR systems and other similar
equipment.
• Operation and Maintenance links for remote MML and other sessions over an IP network using
Telnet.
• Programs within the DXT interchange external messages via a EADS-specific PMR User Part
(PUP), which in turn uses the services of the Message Transfer Part (MTP).
• PCM (A-law) signalling for connecting to the Recorder/ Command and Control room.

2.4.6 Trunking
The DXT3 supports the trunking system in which traffic channels are allocated from a pool of channels
when a call is established. When the call is released, the channels are returned to the pool. A trunked
network uses radio channels efficiently: the number of subscribers can be much higher than the
number of channels.

2.4.7 Resource management

Resource management makes the necessary physical connections for the transfer of speech or data
and controls the use and maintenance of resources.
The resources controlled by resource management vary widely. They include, for example, the
following:
• traffic channels
• speech channels between the DXT and DWSs
• PSTN/PABX connections
• connections to conventional base stations and systems
• speech channels between two DXT exchanges.

These connections are connected to the Switching Network Units (GSW05KB) of the DXT via PCM
circuits, and the resource management software allocates resources to them as subslots of the PCM
time slots.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 21(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.4.8 Numbering
The numbering system ensures that the numbers are used to address calls to the correct recipients.
Radio subscribers, Dispatcher Workstations and groups are all identified with a number. The
called/calling party number is analysed to determine its home or gateway DXT.
The EADS TETRA System uses the continuous numbering model. There are practically no restrictions
as to how numbers are used, so users can define and use their own numbering plans. For more
information, refer to the document Numbering, dn00126527.
The EADS TETRA System supports three independent numbering systems for radio subscribers and
customer applications. These systems can be linked to each other and are listed below:
• ITSI (Individual TETRA Subscriber Identity) based numbering.
• MSISDN (Mobile Station Integrated Services Data Network) numbering.
• FSSN (fleet specific short number) numbering.

2.4.9 Charging services

The charging services operation of the Customer Care and Billing System makes it possible to transfer
charging data electronically to a remote computer, using a direct data network interface to the DXT.
The data operation of the billing system is transferred using the Open Systems Interconnection (OSI)
protocol with the File Transfer Access and Management (FTAM) application or TCP/IP with File
Transfer Protocol (FTP). Physically, the data is transferred by Ethernet Local Area Network (LAN) and
Wide Area Network (WAN) connections between the DXT and the remote computer.
A device called the Virtual Data Storage (VDS), together with the OSI FTAM or TCP/IP FTP protocol, is
used for transferring the data generated by the DXT exchange to a remote computer. The VDS also
performs the necessary buffering and acknowledgements. All data can be directed to I/O devices by
using logical files. In addition, the VDS is used for transferring data to remote systems. The VDS can
be managed in the same way as any other I/O device. If the operator requires data to be directed to a
remote computer, the logical files are connected to the VDS using MML commands.
The Call Detail Record (CDR) includes all information required for the billing of a call, excluding price
information. Charging gives the possibility to optimise the contents of the CDRs, which decreases
the need for hard disk capacity. For more information, refer to the documents Charging Services,
dn00126554, and Charging Services DXT-Billing Centre Interface Description, dn00126566.

2.4.10 Statistics
The operator can activate and access the Statistics function in the DXT exchange with MML commands.
Statistics are handled by the following hardware units:
• Central Memory and Marker (CMM).
• Operation and Maintenance Unit (OMU): Statistics (generation of reports).
• Common Channel Signalling Unit (CCSU): MTP statistics (distributed processing).

TRADXTAPP00028-01en DXT3TM Product Description

22(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Statistics can be divided into the following subcategories:

2.4.10.1 MTP statistics

The MTP statistics function enables the network operator to receive availability, performance, utilisation,
and status reports on the signalling links between DXT exchanges. The following reports are available:

• signalling link reports

• signalling point reports

• traffic measurement reports.

2.4.10.2 Traffic measurements

Traffic measurements can be divided into the following subcategories:

• radio network

• individual call

• group call

• group management

• roaming

• packet data

• status and SDS messages

• speech line reservations between DXT exchanges

• mobility management

• ISDN resource management of the DXT

• FNIM resource management of the DXT.

2.4.10.3 Load observation measurements

Load observation measurements can be divided into the following subcategories:

• computer units load

• message bus load.

2.4.10.4 Field reporting measurements

Field reporting measurements consist of the following subcategory:

• availability.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 23(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.4.11 IP Packet Data
The Packet Data Communications Unit (PDCU) is used for processing IP packet data and to provide
LAN interfaces for the TCP/IP gateways. In the EADS TETRA System, packet data is used primarily for:

• querying external databases (a vehicle register, for example)

• e-mail and fax (supported by an appropriate server)

• telemetry

• remote control

• information broadcast

• browsing WWW/WAP pages

• authentication.

Currently, the EADS TETRA System IP Packet Data Service supports point-to-point IP data
communication between two MS hosts, or between an MS host and an external host. For more
information on packet data, refer to the documents Basic IP Packet Data Service, dn05221832 and
Enhanced IP Packet Data Service, dn05222516.

2.4.12 ISDN PRA

ISDN Primary Rate Access (ISDN PRA) provided by the DXT enables a digital connection to external
networks. Because ISDN signalling supports an extensive range of bearer services, teleservices, and
supplementary services, ISDN PRA provides a good basis for enlarging the set of EADS TETRA
System services.

The DXT call control has the capacity needed for all ISDN B-channels, EADS TETRA System internal
calls and calls via the R2 interface.

For more information on ISDN PRA, refer to the document Telephony Services through External
Interfaces, dn0217914.

Figures 5 and 6 show examples of DXT exchanges connected to ISDN/PSTN and a Private Network
(PABX) respectively.

TRADXTAPP00028-01en DXT3TM Product Description

24(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 DXT3

DXT3

PRA PUP
ISDN exchange
PUP DXT3

PRA
DXT3

PRA PUP

PRA
PSTN

ISDN
Exchange
Key:
DXT3 = Digital Exhange for TETRA
ISDN = Integrated Services Data Network
PRA = Primary Rate Access
dn 0572319 x3x0xen
PSTN = Public Switched Telephone Network
PUP = PMR User Part

Figure 5 : DXT3 exchanges connected to ISDN/PSTN via an ISDN exchange

DXT3
PABX
DXT3 PRA
PUP
PABX
DXT3 PUP PABX QSIG
or PRA
QSIG ISDN exchange
PUP or PRA QSIG
PRA QSIG
or PRA or PRA
QSIG PABX
or PRA

PSTN
Key:
DXT3 = Digital Exchange for TETRA
ISDN = Integrated Services Data Network
PRA = Primary Rate Access
PABX = Private Automatic Branch Exchange
PSTN = Public Switched Telephone Network
PUP = PMR User Part
dn 0572322 x3x0xen
QSIG = Symmetric access signalling system , modified from ISDN PRA

Figure 6 : DXT3 exchanges connected to a private network with ISDN PRA

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 25(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
2.4.13 Authentication and Encryption
The purpose of the security features in the EADS TETRA System is to restrict access to information
and resources to authorized users and subscribers only. Security threats to a PSS system fall into
four broad classes:

• Leakage: the acquisition of information by unauthorized recipients.

• Tampering: the unauthorized alteration of information (including programs).

• Resource stealing: the use of facilities without authorization.

• Vandalism: interference with the normal operation of the system without gain to the perpetrator.

Authentication is a function that allows the infrastructure to check that a mobile subscriber (MS) is
authorized to access the system. An MS is required to authenticate during registration and after
that within periods defined by the security policy.

TETRA authentication is based on a symmetric-key encryption algorithm. The system requires a key
that is known to the communicating parties, but otherwise kept secret. Authentication is achieved by
the parties proving to each other knowledge of the shared secret. If authentication fails, the user
is not admitted into the EADS TETRA System.

Authentication requires a SECMO security module. The SECMO is an optional unit.

EADS TETRA system supports Air Interface encryption (optional) for voice, data and signalling. Also
end-to-end encryption is supported (optional).

For more information on authentication, see the document Authentication in the EADS TETRA System,
TRASYSAPP00003.

Special consideration

Activating the authentication of an MS has the following requirements for the network configuration:

• One of the DXTs in the network should be connected with the AKES server (Authentication Key
Management Server) or with the AKDC (Authentication Key Distribution Compact).

• Authentication requires that SECMO units are installed in the DXTs of the network. SECMO is
a logically and physically protected security module, in which the encryption algorithms are
executed. The SECMO units are installed in the Central Memory and Markers (CMMs) of the
DXT3.

Note

SECMO plug-in units may not be available in some countries because of national export control
classification restrictions.

TRADXTAPP00028-01en DXT3TM Product Description

26(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Capacity

3.1 DXT3
The following table presents the maximum capacity available for the user organization and the
maximum connection capacity of the DXT3.
Note
The capacity figures with external CDD server are valid only with a certain traffic profile.

Table 2 : Capacity of the DXT3

Capacity with external CDD Capacity with Integrated

server Data Distribution
functionality
Subscribers (HLR/VLR) 100 000 (HLR;150 000 30000/30000
without base station) / 50 000
Groups 30 000 10000
organization blocks 5600 5600
Dispatcher workstations and TCS clients 256 64/64
Altogether/with voice
TCS servers 12 6
ISDN PRA (30B+D), see note below 32 (960 lines) 16 (480 lines)
Carriers and base stations • 320 TETRA radio carriers, 1024 channels

• equipped in max 128 TBSs

PSTN and PABX connections, see note • 240 interfaces for PSTN and PABX exchanges through
below ECE2–NT(C) plug-in units.
Conventional PMR G4WIF/R2 systems • 240 interfaces through ECE2–NT(C) plug-in units.
and other systems, see note below

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 27(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Table 2: Capacity of the DXT3 (cont’d.)

Capacity with external CDD Capacity with Integrated

server Data Distribution
functionality
Connections between DXT3 and other • 960 8 kbit/s speech channels per DXT
DXT exchanges
• 90 MTP signalling links
Exchange Terminals (ET) • 128 + 32 PCM/2Mbit interfaces
Exchange Terminal Types, see the • 8 ET16
second note below
• 16 ECE2–NT(C)
Recording interface 480

The figures in the above table are individual upper limits for each of the values. The upper capacity limit
for the dynamic load depends on a real traffic profile and the size of the network. Traffic engineering
dimensioning is needed to evaluate possible peak values and to plan the values to be used for each
DXT and for the whole TETRA network to reach the best end user satisfaction.
Note
The maximum capacity of the DXT3A cabinet configuration is 64 PCMs for interfaces towards base
stations, dispatcher workstations and other DXTs, and 16 PCMs for ISDN 30B+D connections, PSTN
and PABX connections with R2–signalling and connections to conventional PMR and other systems.
For further details, see section 9.4.8 . Note also that the ECE2– NT(C) plug-in units used with the
R2–signalling or for conventional PMR and other system interfaces are placed in the same positions in
the cartridge as the ECE2– NT(C) plug-in units used for ISDN 30 B+D connections. It is not possible to
have ISDN 30B+D connections and other PSTN, PABX or conventional PMR system connections in
the same plug-in unit.

Note
If no PSTN and PABX connections, conventional PMR systems or other systems are in use, the 16
PCMs reserved for use with them can be used for Exchange Terminals with ET2E plug-in units.

3.2 DXT3 (HLR only)

The following table presents the maximum capacity available for the user organization and the
maximum connection capacity of the DXT3 (HLR only).
Note
The capacity figures with external CDD server are valid only with a certain traffic profile.

TRADXTAPP00028-01en DXT3TM Product Description

28(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Table 3 : Capacity of the DXT3 (HLR only)

Capacity
Subscribers (HLR) 150 000 without base station
Groups 30 000
organization blocks 5600
Dispatcher workstations and TCS clients 256
Altogether
TCS servers 16
PSTN and PABX connections, see note • 240 interfaces for PSTN and PABX exchanges
below through ECE2–NT(C) plug-in units.
Conventional PMR systems and other • 240 interfaces through ECE2–NT(C) plug-in units.
systems, see note below
Connections between DXT3 and other • 320 MTP signalling links
DXT exchanges
Note
The MTP max amount can be 320, only if there
are no LAPD links created in the exchance (No
audio clients).

• 960 8-kbit speech channels

Exchange Terminals (ET), see the second • 128 + 32 PCM/2Mbit interfaces

note below
ISDN PRA (30B+D) • 32 ISDN 30B+D connections
Exchange Terminal Types • 8 ET16

• 16 ECE2–NT(C)

The figures in the above table are individual upper limits for each of the values. The upper capacity limit
for the dynamic load depends on a real traffic profile and the size of the network. Traffic engineering
dimensioning is needed to evaluate possible peak values and to plan the values to be used for each
DXT and for the whole TETRA network to reach the best end user satisfaction.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 29(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Note

The ECE2– NT(C) plug-in units used with the R2-signalling or for conventional PMR and other system
interfaces are placed in the same positions in the cartridge as the ECE2–NT(C) plug-in units used for
ISDN 30 B+D connections. It is not possible to have ISDN 30B+D connections and other PSTN, PABX
or conventional PMR system connections in the same plug-in unit.

Note

If no PSTN and PABX connections, conventional PMR systems or other systems are in use, the 32
PCMs reserved for use with them can be used for Exchange Terminals with ET2E plug-in units.

TRADXTAPP00028-01en DXT3TM Product Description

30(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
3.3 SIPU dimensioning guidance
The following SIPU configurations are supported:

Table 4 : The supported SIPU configurations

DXT256 with M92 mechanics 0–4 SIPU pairs

DXTip basic with M98F mechanics 0–1 SIPU pairs
DXTip with extension cabinet 1 based on M98F 0–3 SIPU pairs
mechanics
DXTip with extension cabinets 1 and 2 based on M98F 0–5 SIPU pairs
mechanics
DXTip with M98F2 mechanics 0–2 SIPU pairs
DXTTip with M98F2 mechanics 0–4 SIPU pairs
DXT3 with M98F2 mechanics 0–2 SIPU pairs

Requirements
The numbers of clients listed below can be served only if the following requirements are fulfilled:
• The third party clients are used to provide the same type of functionalities as the EADS DWS
client.
• Round trip time for voice and data applications:
40 ms during normal operation in every situation to secure reliable communication (meaning up
to 25 messages per second).
• Transit delay:
20 ms (round trip time / 2 <=> QoS).
• Throughput:
64 kbit/s / client applications at minimum: the recommended value is 256 kbit/s / client (round trip
time guideline has to be fulfilled also in this case).
• Every TCS must belong to the TETRA IP Backbone (VPN).

M92/M98F mechanics
SIPU dimensioning for the M92/M98F (DXT256/DXT3) mechanics:
System with CDD:
Note
CDD is connected to only one SIPU in the DXT.

• SIPU which has no CDD connected to it can have a total of 128 third party clients and DWS-M
clients in max. 8 TCS servers.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 31(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 • SIPU which has CDD connected to it can have a total of 20 third party clients and DWS-M
clients in max. 4 TCS servers.

• The total capacity is: in M92 mechanics 256 clients in max. 28 TCS servers; in 3–cabinet M98F
mechanics 256 clients in max. 36 TCS servers.

System without CDD:

• DXT with Integrated Data Distribution can connect 64 clients.

M98F2 mechanics

SIPU dimensioning for M98F2 (DXT3):

System with CDD:

Note

CDD is connected to only one SIPU in the DXT.

• SIPU which has no CDD connected to it can have a total of 192 third party clients and DWS-M
clients in max. 8 TCS servers.

• SIPU which has CDD connected to it can have a total of 64 third party clients and DWS-M
clients in max. 4 TCS servers.

• Consequently, the total capacity is 256 clients in max. 12 TCS servers.

System without CDD:

• DXT with Integrated Data Distribution can connect 64 clients.

TRADXTAPP00028-01en DXT3TM Product Description

32(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

System overview
This chapter describes the internal communication of the DXT and its interfaces to the EADS TETRA
System and external systems.

4.1 Internal communication

The DXT uses an Ethernet Message Bus (EMB) as the route for internal communication. EMB is a
feature which can be activated or de-activated, depending on the user’s needs. EMB can use different
types of addresses, and is prepared for changeovers without losing the essential connections. These
issues are discussed in more detail below.

4.1.1 Ethernet Message Bus

The Ethernet Message Bus (EMB) is a synchronous parallel bus with 2n redundancy (see Chapter 7 ).
Each computer unit contains four separate Ethernet interfaces. Two of them are used for EMB, one for
each bus. The computer units communicate with each other by exchanging messages via the Ethernet
Message Bus. The transmission speed is 1 Gb/s.

4.1.2 LAPD
The Link Access Procedures on the D-channel (LAPD) and the functions of the OSI network layer
together form a D-channel. In the DXT, the applications which use D-channels communicate with each
other through message interchange.
LAPD is used for both internal and external communication. Internal communication includes the
following:
• The preprocessor units inside the DXT using the D-channel are:
– Clock and Tone Generator (CL3TG)
– Exchange Terminal (ET)

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 33(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
The internal channels are connected through the switching matrix.
LAPD is also used when connections are needed from the DXT to external devices, such as the TBS.

4.1.3 SCBUS
The SCBUS is used for collecting alarms from all CLAC cartridges of the DXT and transferring them
to the HWAT plug-in unit of the OMU. The SCBUS is a duplicated serial bus with asynchronous bit
timing and 1 Mbit/s transmission rate.

4.1.4 Changeovers
The preprocessors, such as ET and CL3TG, are connected to the Central Memory and Marker
(CMM) by serial 64 kbit/s links and the LAPD protocol. These links are maintained during a possible
changeover of the CMM, because they are connected through both the active and the spare switching
network units.

4.2 Interfaces
The DXT provides interfaces to:
• TETRA Base Stations (TBS)
• Dispatcher Workstations
• ISDN PRA for connection to PSTN/PABX
• digital R2 connection to PSTN/PABX
• other DXT exchanges
• conventional PMR systems
• TCS Server
• CDD Server
• LAN
• Recorder
• Command and Control rooms
• Enhanced Packet Gateway
• Charging systems.

4.2.1 DXT3 - TETRA Base Station

The DXT3 - TBS connections use the E1 interfaces included in the ET16 plug-in units. The 64-kbit/s
time slots of the 2-Mbit/s circuit are used for both signalling and speech. The 2 Mbit/s interface

TRADXTAPP00028-01en DXT3TM Product Description

34(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
conforms with the ITU-T Recommendations G.703 and G.704. All E1 connections are permanent
connections throughout the transmission network. Figure 7 presents a connection model.

DXT3 TB3

G.703 /G.704
2 Mbit/s
16 * 2 =
32 Mbit/s FXC
GSW05KB ET16

TB3

FXC

Key: DXT3 = Digital Exchange for TETRA

GSW05KB = Switching Network Unit
ET16 = Exchange Terminal plug -in unit
TB3 = TETRA Base Station
Dn0572334x2x0xen
FXC = Flexible Cross Connect unit

Figure 7 : DXT3 - TBS interface

Note

One TBS does not reserve the whole 2-Mbit/s line. TBSs can be looped and chained. Note that looping
requires an external cross connect (for example DN2).

The number of carriers in a TBS determines the required transmission capacity between the DXT3 and
the TBSs.

When the number of carriers in a TBS is one or more, the required transmission capacity is n * 64-kbit/s
links. The optional 64-kbit/s link can be reserved for the message transfer between the DXT3 and the
TETRA Base Station Controller (TBC). The messages between the DXT3 and the TBC are transferred
through the TETRA Transceiver (TTRX) unit with optional 64-kbit/s link messages.

DXT3 — Remote TBS MMI PC

The use of Remote TBS MMI makes it possible to perform various tasks on the TBS (TBC) remotely
from a DXT site with the WinMMI PC tool. The WinMMI PC is connected via an RS-232 cable to
the service terminal interface of the OMU in the DXT. The connection can be made from one active
TBS directly connected to the DXT at a time.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 35(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
4.2.2 DXT - Dispatcher Workstations
The EADS TETRA System supports dispatcher workstations of the following types:

• DWSi (ISDN-connected EADS Dispatcher Workstation)

• DWSr (EADS Radio Data Dispatcher Workstation)

• DWSx (EADS E1– or ISDN-connected Dispatcher Workstation)

• DWSip (TCP/IP-connected EADS Dispatcher Workstation)

The connection types between the DWS variants and DXT are listed below:

• DXT has E1 interfaces (G.703/704) included in the ET16 plug-in units for interfacing to the
DWSx and DWSi workstations.

• In DWSi and DWSx with an ISDN connection, Enhanced Protocol Converter (EPCO) is required
to convert the signalling from the ET16 plug-in unit to the ISDN Primary Rate Interface.

• The DWSr is connected to the DXT3 through a TETRA IP Packet Data or GSM DATA (circuit
switched) connection to the TCS Server.

• The DWSip is connected to a LAN/WAN that provides a TCP/IP connection to the SIPU unit of
the DXT.

The 64–kbits/s time slots of the E1 connection are used for both signalling and speech. The E1
connection interface conforms with the ITU-T Recommendations G.703 and G.704. All E1 connections
are permanent connections throughout the transmission network. The signalling messages are sent
with the bit-oriented LAPD (Link Access Procedure on the D-channel) protocol. The number of
necessary 64–kbit/s time slots between the DXT and the DWS depends on the features the workstation
supports.

For more information about the EADS DWS products, refer to the document Product Description for the
EADS TETRA Dispatcher Workstation (DWS), dn05221844. Figure 8 presents a connection model.

TRADXTAPP00028-01en DXT3TM Product Description

36(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 DWSip

TCP/IP
LAN/WAN

DWSx

E1

E1
E1 Multiplexer E1
E1

TCS EPCO ISDN

BRA DWSx
TETRA IP or
Cellular data

ISDN

ISDN
BRA

DWSi or DWSx
DWSr
Dn0572346x3x0xen

Figure 8 : DXT - Dispatcher System Interface

4.2.3 DXT - PSTN/PABX

The DXT provides 240 analogue interfaces for PSTN and PABX exchanges. The interfaces are
implemented through the ECE2–NT(C) plug-in unit.

The DXT also provides a digital ISDN PRA interface for PSTN and PABX. For more information on
ISDN PRA, refer to Chapter 2.4.12 .

4.2.4 DXT - conventional PMR systems

The DXT provides interfaces for conventional PMR systems via the G4WIF (generic 4-wire interface) of
the ECE2–NT(C) plug-in unit.

4.2.5 DXT - other TETRA exchanges

The Common Channel Signalling Unit (CCSU) is a computer unit which increases the data transmission
capacity (including MTP signalling links) between the DXT exchanges.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 37(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Maximum number of CCSU units:
• DXT3: 4.

™ for TETRA)
4.2.6 DXT - network management system (NetAct™
The DXT has a direct interface to the network management system. The network management system
is described in more detail in Section 8.3 .
The interface uses FTAM, Q3, OSI, and IP protocols.

4.2.7 DXT - other systems

The DXT provides Ethernet/IEEE 802.3 LAN interfaces for connecting to other systems. For the
physical transfer, it uses the File Transfer Access and Management (FTAM) protocol of the OSI stack.

4.2.8 DXT - TCS

The TETRA Connectivity Server (TCS) is a product which provides an application programming
interface (API) for third party administration and dispatching client applications. The TCS API includes
network-wide speech and data management, as well as operational management and control functions.
The TCS is connected to the DXT and optionally to the CDD Server through TCP/IP. This interface
is used for data management signalling. The TCS also offers a direct connection to workstations for
login/logout messaging and call-related signalling. Third party client applications can also use audio
functionality, which uses G.703/G.704 based ET16 interface in the DXT. For more information on the
TCS, refer to the document TCS Product Description, dn0116031.

4.2.9 DXT - CDD server

The Configuration and Data Distribution Server (CDD) provides network-wide services related to data
management (configuration) and distribution. It also handles part of the network load. The CDD server
is connected to the DXT through TCP/IP. Each DXT in a system with more than one DXT is served
by one CDD, but one CDD may serve several DXTs. TETRA networks with more than one DXT
must contain at least one CDD, but it is optional for single-DXT networks. The SIPU unit provides
the actual LAN interface in the DXT.
In single-DXT TETRA Networks, the CDD can be replaced by the Integrated Data Distribution function
in the DXT. In these cases, the capacity figures are different. For details, see chapter 3 .
For more information on the CDD, refer to the document CDD Server, Product Description, dn0115944.

4.3 Protocols
The protocols used by the DXT are:

TRADXTAPP00028-01en DXT3TM Product Description

38(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 • LAPD

• TCP/IP

• Q3

• MTP

• FTP

• EMT

• TELNET

• FTAM

• SSH

• SFTP

These are discussed in more detail below.

4.3.1 LAPD

The Link Access Procedures on the D-channel (LAPD) protocol, compliant with ITU-T Q.920, is used
as a physical interface.

The LAPD and the functions of the OSI network layer together form a D-channel. In the DXT, the
applications which use D-channels communicate with each other through message interchange.

The LAPD is used for both internal and external communication.

4.3.2 TCP/IP

The TCP/IP protocol is used for connecting the DXT to the TETRA Connectivity Server (TCS), CDD
(Configuration and Data Distribution) Server, IP networks of the Packet Data Service, and DWSip.
For more information on the IP packet data, refer to the documents Basic IP Packet Data Service,
dn05221832 and Enhanced IP Packet Data Service, dn05222516.

4.3.3 Q3

The Q3 interface is used for transmitting alarms from the DXT to the network management system
(NetAct™ for TETRA).

The Q3 interface is also used for giving indications to an external charging system when the files
collecting billing information in the DXT are full. The charging system then uses the FTAM protocol to
fetch the billing information from the DXT.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 39(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
4.3.4 MTP
The EADS TETRA System uses the MTP (Message Transfer Part) of the Common Channel Signalling
system for interexchange signalling. Thus, two or more DXT exchanges are connected through an
MTP network.

The Common Channel Signalling Units (CCSU) provide the necessary signalling links. For more
information on creating MTP links, refer to the document Integrating the EADS TETRA System,
dn05225513.

4.3.5 FTP/SFTP
The TCP/IP file transfer protocol (FTP) is used for transferring charging files to a remote billing system.
For more information on configuring the TCP/IP file transfer protocol, refer to the document Integrating
the EADS TETRA System, dn05225513.

4.3.6 OSI

The Open Systems Interconnection (OSI) stack is used for transferring charging data from the DXT to
an external charging system. Physically, the File Transfer Access and Management (FTAM) protocol of
the OSI stack is used for this purpose.

An external system initiates the FTAM transfer in the DXT. The physical connection between the
DXT and the external system operates via the Local Area Network (LAN) which is supported by the
OSI stack.

4.3.7 EMT
External Message Transfer (EMT) is an EADS proprietary protocol that provides the functionality for
sending and receiving messages between a DXT exchange and an external system through TCP/IP
connections. EMT runs between a server process in the exchange and client software in the external
system.

4.3.8 Telnet/SSH
A terminal emulation program for TCP/IP networks such as the Internet. Telnet is a common way to
remotely control DXTs. Using the Telnet program, it is possible to connect the DXT to a server on the
network. MML commands can then be entered through the Telnet program and they will be executed
as if they had been entered directly on the server console. This enables controlling the DXT and
communicating with other DXTs on the same network. To start a Telnet session, a valid username
and password are needed.

TRADXTAPP00028-01en DXT3TM Product Description

40(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CAUTION
Telnet is intended to be used in a trusted private intranet environment only. However, commercial
end-to-end encryption software or similar can be used to protect IP traffic between nodes using Internet.

4.3.9 FTAM

The File Transfer Access and Management protocol (FTAM), an ISO application protocol, offers file
transfer services between client (initiator) and server (responder) systems in an open environment.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 41(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

42(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Software
This chapter describes the software used in the DXT. It also describes briefly the architecture, the
databases, and the programming languages.

5.1 Architecture
The software of the DXT consists of blocks which form a three-level hierarchy.

The system block is the highest level in the hierarchy. It includes several service blocks, each of which
includes one or more program blocks.

Each program block may contain one or more processes. The processes communicate with each other
through asynchronous message interchange controlled by the operating system. The operating system
also offers all the basic services required for the processes. Thus, it provides a uniform operating
environment for them.

The software is easy to maintain due to its hierarchical and modular structure. This makes adding
enhancements to the DXT flexible.

5.2 Databases

5.2.1 Implementation system

The DXT databases are implemented with the Database Management System (TDMS), which is a
highly reliable in-house product designed specifically for the DX200 environment. It forms the basis
for the DXT databases. Telenokia Database Language (TDL) is used as the database language. The
databases of the DXT are fast because they have precompiled transactions.

The TDMS controls that there are consistent copies of each database available in the disk drives and in
the RAM (Random Access Memory) at all times. The TDMS also offers an object-based database
model and a high-level database language. Furthermore, the logical model of the database and its

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 43(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
physical implementation are separated in the database descriptions. These features result in a modern,
application-based database design with a high degree of manageability and flexibility.

5.2.2 Semipermanent files

The databases are semipermanent in the sense that the files are fully in RAM as memory arrays.
Updates are first made to the RAM files which are then continuously updated to the Winchester disk
drives.

5.2.3 DXT3 databases

The DXT3 contains several databases :
• TXDATA
– Exchange database.
– organization database.
– Group database.
– Workstation database.
• RDDATA
– Numbering database.
RDDATA contains the following data of the subscribers: MSISDN, FSSN, and ITSI numbers
of the subscribers and Fleet domain HLR data.
• TNDATA
– Group and workstation home location database.
TNDATA indicates the group’s home DXT and the workstation’s location DXT.
• VUDATA
– Radio subscriber’s VLR database (not in transit layer switch).
– Workstation user’s Session database.
The VUDATA is a RAM based database.
• THSDAT
– Workstation user’s database.
– Radio subscriber’s HLR database.
THSDAT stores the subscriber’s HLR and the workstation user’s data.
• SXDATA
– Authentication database.
SXDATA contains authentication and encryption related data.
• OEDATA

TRADXTAPP00028-01en DXT3TM Product Description

44(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 – Configuration Database of OSI Environment.
OEDATA contains the configuration data of the OSI environment. The database is part of
the DX200 platform.
• EQUIPM
– Equipment Database.
EQUIPM contains the hardware configuration data. The database is a part of the DX200
platform.
• ENGINE
– Terminal Equipment Identity (TEI) database.
ENGINE contains information on the enable/disable state of TEIs. TEIs are stored in only
one of the DXTs in the network.
• ILDATA
– Internal LAN Link Database.
The purpose of the ILDATA is to offer a storing place for the connection data, that is, the
internal LAN link data of a network element. ILDATA contains the following data:
♦ Local area networks (LANs) and virtual LANs (VLANs)
♦ LAN elements, that is, Ethernet switches and computer units, which are connected to
Ethernet switches
♦ Ethernet interfaces
♦ connections between Ethernet interfaces
♦ connections between LANs or VLANs and Ethernet Switches.

5.3 Programming languages

More than 90 % of the program code in the DXT is written in a high-level programming language:
TNSDL, PL/M, or C. Assembly language is used only in critical parts of the software, where real-time
operations have to be executed at a very high speed, close to the hardware.

Description languages
In the design and documentation of the DXT software, readability and visual quality of the programs
have been improved by using special description languages in addition to the actual programming
language. These description languages also facilitate effective software design and enable the use
of automatic tools for development and testing.
The most common description language is Specification and Description Language (SDL). SDL is used
for defining state-automaton-based processes in accordance with the ITU-T recommendations. Also
TDL language is used. TDL language is a database language which is used for defining databases
and their manipulation.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 45(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

46(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Hardware
This chapter describes the DXT hardware: functional units, cartridges, racks, and cabling. At the end
of the chapter are included tables listing the contents of the basic HW configuration and the optional
equipment available for the DXT3. The DXT3 consists of a single cabinet, the DXT3A.

6.1 DXT HW principles

Plug-in units

The DXT is constructed using 20 plug-in unit types, including the DC/DC converters. The sizes of
the plug-in units are listed in Table 5 .

Table 5 : Plug-in unit sizes

Heigth Depth
233.4 mm 160 mm
233.4 mm 220 mm
233.4 mm 280 mm
100.0 mm 220 mm
110.0 mm 220 mm

The widths of the plug-in units vary between 15 and 45 mm.

The printed circuit boards (PCBs) of the plug-in units are multilayered. They are covered with a
protective coating that makes the PCBs easy to handle and protects the foils from scratches.

Both surface-mounted and hole-mounted components are used on the PCBs. The connectors to the
back plane are of the Hard Metric or Euro-connector type.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 47(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
6.1.1 Racks
The frame of a rack consists of side rails, made of plated steel sheets, which support an upper and
a lower shelf. The lower shelf has adjustable legs. The rack is surrounded by side plates, doors, a
cabling rack (in the cabinet DXT3A), and a baseboard. The doors are perforated to facilitate cooling.

The rack is provided with four fans.

6.1.2 Cabling
There are two kinds of cables in the DXT:

• internal cabling inside the DXT cabinets

• external cabling connecting the DXT to the environment.

The DXT uses standard length cables for the internal cabling. These are installed at the factory from
each cartridge to the next.

The external 2-Mbit/s PCM cables and other station cables (for example, external alarm cables,
and power supply cables) of the DXT enter the exchange room via a cable conduit and standard
connectors, usually located on top of the cabinet. Alternatively, the cable conduits can be installed on
the floor of the exchange room.

6.1.3 Sets
Cabinet mechanics and cabling are divided into the following modules (equipping sets):

• Cabinet type set.

Equipping set which includes the generic materials of the cabinet, for example, mechanics and
ready-assembled intracabinet cables.

• Cabinet location set.

Equipping set which includes materials dependent on the location of the cabinet, for example,
pre-assembled intercabinet cables and markings.

• Cabinet alternative set.

Equipping set which includes alternatively usable materials, for example, connector panels.

For a detailed list of cabinet mechanics and cabling modules, see Sections 6.2.2 and .

6.2 Description of DXT3 cabinet

The DXT3 consists of a single cabinet, the DXT3A.

TRADXTAPP00028-01en DXT3TM Product Description

48(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
6.2.1 Functional units
The DXT3 consists of functional units. Each of these units has a specific function, certain connections
to other units, and a specific resilience mechanism. The functions of each unit are listed below. Figure
9 illustrates the functional units, their connections, and the resilience mechanisms of a fully equipped
DXT3.

CLAB CPEA

Ext. sync.
CLS

CPETS or
CPETC
2 Mbit/s
2 Mbit/s
ISDN PRA to P ABX, PSTN 2 Mbit/s
2 Mbit/s
ECET
2 Mbit/s
2 Mbit/s
E1 To DWS, NMWS, 2 Mbit/s

TBS, DXT 2 Mbit/s

ET
TG S -LAN
TAS -LAN
T LS -LAN

CPLAN-A GSWB
CPLC18 EXT-LANs

OMU LAN
LAN to CCM LAN
IP network ESB24 CCSU SIPU LAN
LAN Switch PDCU LAN
LAN to LAN switch CCM LAN

LAN to LAN to LAN to

LAN switch LAN switch LAN switch
SIPU
NTDU
SIPU
SIPU
NTDU SIPU CCSU
NTDU CCSU
SIPU NTDU
PDCU CMM CCSU
ESB24 CCSU
EMB 0 LAN
Switch
EMB
ESB24 CCSU
EMB 1 LAN
Switch

LAN to
LAN switch OMU CPRS-A
LAN to
LAN switch
TGS VDU/LPT

LAN to
LAN switch Hard Disk
LAN to
Drive + USB
Hard Disk LAN switch memory stick
Drive + USB
memory stick

DN0532362x3x0xen

Figure 9 : Functional units of the DXT3

The functional units are briefly described in the section below. A detailed description of the resilience
methods used in the DXT is included in Chapter 7 .

Functional units and their tasks

• OMU

Operation and Maintenance Unit.

The OMU is used to control mass memories (disk and tape drives) and to provide management
interfaces towards the local MMI, the network management system (NetAct™ for TETRA

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 49(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 and also MMI interface to the DWS Management) and the billing system and towards other
exchanges to provide remote sessions and remote file transfer.
• CMM
Central Memory and Marker
In the DXT3, CMM contains all data except group and workstation home location data (this
data is in the CMM). The role of the CMM is to act as the main data management unit of the
exchange. The CMM is 2n redundant.
• SIPU
Server IP Unit. LAN connections to servers.
The Server IP Unit is a 2N redundant computer unit for TCP/IP processing. It is possible to
use several SIPU unit pairs.
• CCSU
Common Channel Signalling Unit.
The CCSU is a computer unit which increases the data-transmission capacity (including MTP
signalling links) between DXT exchanges. The CCSU also handles ISDN PRA signalling and the
signalling between base stations and dispatcher workstations. The CCSU is N+1 redundant.
• PDCU (needed when TEDS is in use)
Packet Data Computer Unit. LAN interface to packet data core network. The PDCU is
complementary N+1 redundant with enhanced IP packet data service, and N+1 redundant
when basic IP packet data service is used.
• ET16 and ECE2–NT(C)
Exchange Terminal.
The Exchange Terminals are 2 Mbit/s E1 digital trunk interface units with 2 E1 interfaces
equipped on each plug-in unit. The ETs are used for connecting to other DXT exchanges,
dispatcher workstations and base stations.
The redundancy of ET units is achieved by distributing the circuits of one destination to multiple
ET plug-in units.
• GSW05KB
Switching Network Unit.
The GSW05KB is a digital, non-blocking switch for switching voice and data, and for the
connections of signalling circuits. The GSW05KB is 2n redundant.
• CLSU
Clock and Synchronisation Unit.
CLSU contains inputs for external synchronization signals fed through the OMU through a LAPD
channel. The CLSU generates the clock signals necessary for synchronizing the functions
of the DXT and transmits them further to the CLAB units in the other cabinets. When using
a hierarchical mode, each unit can be synchronized to four inputs. It has also two external

TRADXTAPP00028-01en DXT3TM Product Description

50(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 synchronization inputs. The CLSU collects the wired alarms from other units in the DXT3, and
sends them to OMU. One CLSU unit can handle the timing and alarm collection functions of
15 cartridges indirectly via CLAB.

• CLAB

The duplicated Clock and Alarm Buffer distributes the reference clock frequency to other racks
and collects wired alarms from these.

• ESB24

An Ethernet switch connected to the CMM. It is used as a switch between different units and can
also be used as a switch for units outside the exchange. ESB24 is located in SIPU 2–0 / 2–1
unit (functional unit SWU).

Location of the functional units

Figure 10 shows the location of the functional units in the DXT3.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 51(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 CABLING
DXT3A CABINET
PDFU -B PDFU -B
PDFU 0 PDFU 1
0

CPBP 0

CLAB0/1
DC3C-B DC3C-B

CLOC-B

CLAC-B
CLS 0/1
CCSU 0 CCSU 2
CCSU 1 CCSU 3
CPEA 1

1 CPRS - A 2

DC4C-B DC4C-B DC4C-B CC4C-B

SIPU 0-0 SIPU 0-0 SIPU 1-0 PU
OMU CPLC 18 3
PDCU 0 PDCU 1 SIPU 1-1

FTRB-A 0 FTRB-A 1 CPLAN -A 4

2
GT6C-A

GT6C-A

CPLAN -A
GS WB

CC 4C-B CC 4C-B 5
0/1

CPETS -E/
CPETS -E 6

3
CPETS -E/
CPETS -E 7
CC 4C-B CC 4C-B ET4C-B
CMM 0 CMM1 ET4C 0
CPETS -E/
8
CPETS -E
FTRB -A 2 FTRB -A 3
4 0 3 6 9 CPBP 9

DC3C-B DC3C-B DC3C-B

CPETS / 10
CPLA
CPETC

dn 091252 x1x0xen

Figure 10 : Layout of the DXT3A

6.2.2 Cabinet mechanics and cabling modules of DXT3

• Cabinet type set
– mechanics
– cables
– setting modules
– panels
• Cabinet location set
– cables

TRADXTAPP00028-01en DXT3TM Product Description

52(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 – setting modules
– markings
• Alternative set, E1 balanced
– panels
– cables
• Alternative set, E1 unbalanced
– panels
– cables

6.3 Basic HW configuration and optional equipment

The following tables list the hardware (functional units and equipment) included in the basic hardware
set of and the optional equipment available for the DXT3.

Table 6 : Basic HW configuration of the DXT3

DXT3 Basic HW Rel. 5.6 Quantity

Object name
Rack: cartridges, Cabling rack and internal
cabling.
Assembly to cabinet
Basic SW for DXT 1 pcs
Functional unit OMU 1 pcs
Functional unit CMM 2 pcs
Functional unit CCSU 2 pcs with one
AS7–C
Functional unit ET 4 pcs
Functional unit ET16 1 pcs
Functional unit GSWB 2 pcs
Functional unit CLOC 1 pcs
Functional unit CLAC (CLAB) 1 pcs
Functional unit (SWU) ESB24 2 pcs

Table 7 : Optional HW of the DXT3

DXT3 optional HW Rel. 5.6 Quantity

Object name
MMI Terminal VT5530 1 pcs

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 53(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Table 7: Optional HW of the DXT3 (cont’d.)

DXT3 optional HW Rel. 5.6 Quantity

Object name
PRINTER LPT38–U 1 pcs
Alarm Panel EXAU-A 1 pcs
Functional unit SIPU 2 pairs
Functional unit PDCU 1 pair
Echo Cancelling Plug-in Unit max 16 pcs
(ECE2-NT/ECE2-NTC)
Functional unit ET; ET16 max 7 pcs
Functional unit CCSU + AS7–C 2 pcs
AS7–C 4 pcs
SECMO-CP 1 pair
Optional adapter set for ESB24–D

TRADXTAPP00028-01en DXT3TM Product Description

54(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Resilience
This chapter deals with the resilience methods of the DXT. Two ways of providing resilience are used
in the DXT:

• modularity

• duplication.

These methods are described below.

7.1 Modularity
The software is divided into logically and functionally distinct modules, which are strictly defined and
coherent, and can be implemented separately. Each element has a well-defined interface to the rest
of the system. This modular structure makes the software easy to understand, maintain, modify,
and extend.

7.2 Duplication (redundancy)

Several hardware duplication methods, or redundancy schemes, are used in the DXT. The redundancy
schemes are described in the sections below.

7.2.1 2n redundancy

2n redundancy (duplication) is used when two units are dedicated to a task for which one is enough at
any given time. One of the units is always active, that is, in the working state. The other unit is kept in
the hot standby state, or the spare state. This scheme is shown in Figure 11 .

If an error occurs in the active side of the 2n unit, an immediate changeover takes place. The spare unit
becomes active, and the exchange starts diagnostics in the faulty unit.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 55(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 dn00115541 x1x0xen

Figure 11 : 2n redundancy

2n redundant units in the DXT3 are:

• Central Memory and Marker (CMM)

• Clock and Tone Generator (CL3TG)

• Clock and Alarm Buffer (CLAB)

• Clock and Synchronisation unit (CLSU)

• USB memory stick

• Hard Disk Unit (HDU)

• Switching Network Unit (GSW05KB).

Even though not a functional unit, the Ethernet Message Bus connecting the functional units within the
exchange is also duplicated.

7.2.2 Replaceable n+1 redundancy

Replaceable n+1 redundancy is used when there is just one or a few spare units for a set of n units of
a given type. The spare unit is not used by the applications and is not permanently bound to any of
the n active units, but can take over the load of any one of them.

When a command-initiated changeover for a replaceable n+1 unit is performed, a pair is made up,
the spare unit is warmed up to the hot stand-by state, and a changeover takes place without major
interruptions. This scheme is shown in Figure 12 .

dn0572361x1x0xen

Figure 12 : Replaceable n+1 redundancy

CCSU and PDCU (with basic IP packet data service) are units with replaceable n+1 redundancy.

TRADXTAPP00028-01en DXT3TM Product Description

56(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
7.2.3 Complementary n+1 redundancy

Complementary n+1 units can be used as redundant units for each other in case one of them is
disabled. Complementary n+1 redundancy works like load sharing. All units of this type are normally
kept in the working state running their normal applications.

PDCU when used with enhanced IP packet data service is a unit with complementary n+1 redundancy.

7.2.4 No redundancy
No redundancy is enough in cases where the redundancy of a unit would not noticeably increase the
overall availability performance of the unit. In DXT, these comprise:

• The 2 Mbit/s exchange terminal (ET) is not duplicated because the probability of failure in the
2 Mbit/s line connecting the ET to, for example, other DXT exchanges is expected to be much
greater than failure in the ET itself.

• The Operation and Maintenance Unit (OMU) is not duplicated because its temporary
unavailability does not affect the call processing capability of the DXT.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 57(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

58(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Management
This chapter describes the management of the DXT as follows:
• operation and maintenance
• network maintenance functions
• synchronization
• real time clock.

8.1 Operation and maintenance

Functions which are related to the MMI are located in the Operation and Maintenance Unit (OMU) of
the exchange. An alphanumeric VDU terminal can also be used to enter MML commands.
The management of subscribers, talk groups and dispatcher workstation users in the EADS TETRA
System is done via EADS Dispatching solutions. The EADS Dispatcher Workstation with Management
application provides an easy-to-use and standard PC-based graphical user interface for these
operations.

Output reports
The output reports of the exchange can be directed to peripheral devices. The peripheral equipment
interfaces of the DXT can be used for connecting alphanumeric VDUs, line printers, the duplicated
hard disk, and the USB.

Configuration management and maintenance

The configuration management and maintenance of the DXT support the high availability of the system.
The functions can be divided into five groups:
• configuration management
• supervision
• alarm handling
• recovery and

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 59(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 • diagnostic functions.

These are discussed in more detail below.

8.1.1 Configuration management

Both hardware and software configurations can be changed with minimum disturbance to the DXT
operation. The equipment configuration data is located in the equipment database (EQUIPM), which
assures integrity of the data required for diagnostic tests and other applications.
Software configuration management enables the operator to:
• deploy a new software build
• update the software in use
• create and control test configurations with new software before its deployment
• make backup copies.

8.1.2 Supervision
The supervision function is responsible for early detection of faults and for generation of test events.
The supervision methods include routine functional tests of the hardware items, watch-dog timers,
and process supervision messages.

8.1.3 Alarm handling

The alarm system detects faults on the basis of fault observations in both hardware and software. It
reports the faults to the operating personnel via alarm printouts and, if a lamp panel is in use, with
lamp panel controls.
The alarm handling uses a rule-driven scheme for the classification and prioritisation of the alarms.
They are classified into three preprogrammable urgency levels and two other groups as presented
in Table 8 .

Table 8 : Classification of alarms

Three-star alarm (***) requires immediate action

Two-star alarm (**) requires action during normal working
hours
One-star alarm (*) check if there are special instructions
Disturbance no action required
Notice no action required

Alarm data is stored in a cyclic buffer file. The alarm system also informs the recovery system about
fault observations, thus allowing automatic start-up of the recovery.

TRADXTAPP00028-01en DXT3TM Product Description

60(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Alarm printer
The alarm data which is stored in a buffer file is printed out to a specific alarm printer. In addition to the
immediate alarm detection printouts, the contents of this buffer can be examined by user commands. It
can also be set so that the information is printed out automatically at predefined intervals.

Lamp panel
An external alarm lamp panel, manufactured by Nokia Siemens Networks, is included. It can be used
as a separate alarm indicator. The alarm cables run to the lamp panel through a distribution frame,
and thus the relay contact outlets of the panel can be further connected to external alarms which the
customer can define.

8.1.4 Recovery
The recovery controls the operating states of the functional units and maintains a high level of service
during fault conditions. Several recovery actions can be executed in the system simultaneously.
The recovery functions are:
• elimination of the effects of faults
• restart control
• user interface commands.

Faults are eliminated by using hardware redundancy and automatic functional unit restarts. Recovery
software is distributed to all the relevant functional units. This guarantees the functionality of the
recovery software in the event of any hardware fault. If a fault is detected in a redundant functional
unit, the recovery function performs a changeover to bring the spare unit into the working state. The
faulty unit resets into a test state for diagnostics.
On the functional unit level, processor and preprocessor restarts are used. The recovery uses real-time
data on the states of the functional units. Thus, the restarts of the functional units in the system are
carried out quickly and reliably in the correct order.
With user interface commands, the user can restart the whole system or one or more of its functional
units, change the states of the functional units and request information on the unit states.

8.1.5 Diagnostic functions

The diagnostics locate and make test reports on faults. It is activated automatically by the recovery
system. The modularity of the equipment, automatic fault detection procedures, and elimination of
downtime by using a hot stand-by unit in the event of a fault improve its operation.
The diagnostics functions are:
• to locate and make test reports indicating faulty items
• to make reports on inconsistencies between the information in the equipment database and
the actual hardware.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 61(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Fault location
The principles of fault location of the DXT are:
• mean active repair time less than half an hour
• fault location with the accuracy of one plug-in unit for 70 % of the cases
• fault location with the accuracy of four plug-in units for 95 % of the cases.

The fault location system complies with the ITU-T requirement for the average active repair time of
30 minutes.

8.2 Network maintenance functions

The network maintenance functions are divided into two groups:
• network supervision
• supervision of 2-Mbit/s circuits.

8.2.1 Network supervision

The switching platform provides real-time supervision of the network to guarantee reliable service at
any time. All 2-Mbit/s circuits are supervised by continuously monitoring the bit error rate and frame
alignment. Cyclic redundancy check (CRC-4) supervision and slip calculation are also available.
Network supervision aims at immediate, automatic actions when disturbances or faults are detected
or they are being cancelled.

Tasks and actions

The task of network supervision is to process the information received from time slot T0 of the 2-Mbit/s
circuits. On the basis of this information, the system does the following:
• sets up alarms
• defines the service capacity of circuits
• compiles statistics on disturbances.

If a disturbance is detected on a 2-Mbit/s circuit, the time slots are isolated from traffic. If a fault is
detected, the circuit is blocked until the fault disappears. An alarm is set, and new traffic is routed
through the non-faulty equipment. The blocking can be automatically removed when the fault
disappears.
A disturbance means a situation where an external phenomenon temporarily prevents the required
function of an item. A fault means inability of an item to perform a required function, excluding the
inability due to preventive maintenance, lack of external resources or planned actions.

Fault prediction
In many cases, the occurrence of faults on 2-Mbit/s circuits can be predicted several days before the
actual fault. This is based on an increasing number of short disturbances. Statistics about disturbances

TRADXTAPP00028-01en DXT3TM Product Description

62(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
and unavailability conditions are collected every day on all 2-Mbit/s circuits. This data may be reported
and processed later in order to discover potential faults.

Support for recovery actions

Recovery actions are supported by short temporary measurements on disturbance characteristics.
The measurements are carried out by means of MML commands. Limits can be set for the number of
circuits that may be removed from a circuit group. If the limit is exceeded, an alarm is generated.

8.2.2 Supervision of 2-Mbit/s circuits

The Exchange Terminal (ET) supervises both the 2 Mbit/s circuit and its own operation. When the ET
detects a failure or an alarm, it reports it further. The filtering and formation of an alarm is performed
on the basis of the data in the alarm work files. The data on changes in the alarm states of the 2
Mbit/s circuits is transferred to the alarm system.
The maintenance of the ET16 and ECE2 plug-in units is non-transparent, which means that each
plug-in unit has a time slot of its own (T0) for the use of supervision.

8.2.3 Compilation of disturbance statistics

Trunk network maintenance compiles statistics on faults detected on each 2 Mbit/s circuit. The
statistics are collected by performing permanent and temporary statistical measurements which are
administered by means of MML commands.
The following statistics are collected:
• distribution of short disturbances
– loss of incoming signal
– loss of frame alignment
– Alarm Indication Signal (AIS) received
– alarms from remote end.
• frame alignment signal errors
• number of positive and negative slips
• CRC-4 errors in compliance with Q.821.

The number of short disturbances of each type is divided into four separate counters according to the
duration of the disturbance. Frame alignment errors are divided into four separate counters according
to their duration. The duration limits can be changed with a MML command.
The permanent statistical measurement is normally in the activated state and runs in the background.
The measurement period is activated at 00.00 hours, and its length is 24 hours. When the measurement
period changes, the collected statistical data is stored into a logical file. All external PCM circuits are
measured simultaneously. The limit values of the statistical counters are circuit-specific.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 63(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Temporary measurement can be set up for a given PCM circuit by means of the MML commands. The
results are collected into a logical file.

8.3 Network management system

The NetAct™for TETRA is a reliable tool for centralised management of the TETRA networks.
Developed to optimise the quality of service and operations, the NetAct™for TETRA combines powerful
functionality and an easy-to-use graphical interface. Using various monitoring tools, NetAct can detect
and locate problems in real time. NetAct collects the performance data from the TETRA network and
stores it into its database for later off-line analysis.

The DXT software configuration as well as the radio network configuration can be visualised with
NetAct applications. Automatic and user-defined uploads give an up-to-date picture of the network
configuration. The radio network parameters can be modified and downloaded to the TETRA network.

8.4 Synchronisation

8.4.1 Network synchronization

Digital telecommunications networks are used increasingly for data and speech transfer. In order that
the digital transfer would function flawlessly, it is necessary to synchronise the whole network. Network
synchronization is achieved by synchronizing the clocks of the network elements with each other.

The frequency of the network is determined by a high-stability reference clock or clocks (master
clocks). Other clocks are synchronized to the master clock in hierarchical order. The synchronization
signals are carried by 2 Mbit/s circuits, from which the clock frequency is derived for synchronization
in the receiving end.

Synchronization of the network is usually based on a synchronization plan. The plan defines the
hierarchical levels and takes into account the ITU-T stability requirements and the interfaces of the
synchronizing 2-Mbit/s circuits.

Network elements connected to a fully analogue network operate plesiochronously. In that case,
there is no external synchronization signal. All the clocks run independently of each other. Both the
equipment of the network element and the PCM multiplex equipment are then synchronized to the
fundamental frequency created by the exchange.

TRADXTAPP00028-01en DXT3TM Product Description

64(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
8.4.2 The clock system
The clock system of the DXT can be used in a master - slave network hierarchy. It can also operate
plesiochronously in case the synchronization information is lost.

In normal network conditions, the synchronization information is carried by selected 2-Mbit trunk
circuits from upper to lower hierarchical levels according to the synchronization plan. The clock
system selects the active synchronization signal as the highest-priority signal acceptable from a group
of preselected digital paths.

The clock system is duplicated. If the 2-Mbit/s circuit, synchronization signal or synchronization unit
fails, the changeover is performed automatically. The changeover can also be performed by means of
MML commands. The changeover is performed under control, and does not cause any disturbances in
either traffic or signal quality.

The functions of the exchange terminal relating to synchronization are frame alignment, jitter and
wander compensation and slip control together with the associated frame buffering. The frame
alignment and cyclic redundancy check procedures are in accordance with the ITU-T Recommendation
Q.511.

The Exchange Terminal is provided with a two-frame buffer, which is used both for jitter and wander
compensation in accordance with the ITU-T Recommendation Q.554 and for controlled frame slip
operation. The frame slip is controlled by removing or repeating one complete frame, when required.
This does not cause a loss of frame alignment. The frame slip controlling mechanism facilitates
trouble-free interworking with asynchronous nodes when required.

8.4.3 Real time clock

Real-time reference in the network is required for:

• Time stamps of status and SDS messages

• Call detail records

• Alarm and history logs.

Real-time management can be performed with the Nokia NetAct time master server, using the
integrated Network Time Protocol (NTP) server within the CDD server or using an external NTP server.
The DXT includes an NTP client. For more information, see document Time Management in the
EADS TETRA System, dn0484132.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 65(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

66(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
CHAPTER

Technical data
This chapter gives the basic technical data on the DXT3, briefly lists the requirements for the equipment
room, and describes the main environmental conditions. For dimensions and configuration of the
DXT3, see also Figure 13 .

9.1 Basic technical features

Table 9 lists the basic technical data of the DXT exchange.

Table 9 : Technical data of the DXT3

Mechanical construction Replaceable plug-in units installed in metal cartridges

which are mounted in three racks.
Electromagnetic compatibility Racks protected by sheet metal doors and side walls,
electromagnetic compatibility performance complies
with European directives.
Cooling Forced air convection boosted by air baffles and
perforated doors.
Racks are provided with four fans.
Height 200 cm
Width 1 rack 120 cm
Depth 60 cm
Weight DXT3 with cabling cabinet: 375–450 kg.
Power supply -40 to -72 V
Power consumption (maximum) Total 2,3 kW:
Maximum number of 2 Mbit interfaces 64 PCMs for TBSs and DWSs or max. 16pcs. 30B+D
PCM/30B+D interfaces or a combination of these.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 67(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 LEFT TO RIGHT

WIDTH 1200 mm

Cabling DEPTH
DXT3A cabinet 600 mm

1A

FRONT SIDE OF CABINET

Cabinet 's side plates (SCP ) are ready -assembled in DXT3A .

Cabinet 's top cover plates : .

Cabinet 's top cover plates (TCCP ) are ready -assembled in
DXT3A.

Dn0542231x4x0xen

Figure 13 : Configuration of the DXT cabinet

For more details, refer to the document Installing the DXTip, DXTTip and DXT3 dn064171.

9.2 Equipment room requirements

The mechanical structure of the DXT does not place any special requirements on the ceiling, the
walls, or the floor. No raised floor is needed. However, the floor covering material should be ESD
protective material.
The DXT cabinets are placed in the exchange room to allow access to the exchange both from the front
and the rear. At least 1000 mm of space is recommended in front of and behind the cabinets, and at
least 900 mm of work space should be left between the end of the cabinet row and the wall.
The cabinets stand on adjustable equipment feet or on rails which are approximately 50 mm high.
The 90 mm high space on top of the cabinets reserved for the lead-through of the cabling and the
terminal blocks for the power supply increases the total height of the cabinets to 2190 mm. An
additional minimum of 300 mm of free space should be provided above the cabinets for the upper
cable feed-throughs.
The following factors must also be taken into account when planning the space usage:
• cabling routes (for subscriber, power supply, and PCM circuits)
• service aisles (passage routes, width over 1000 mm).

The DXT cabinets can be installed in several ways in the equipment room. However, the following
points should be taken into consideration:
• standard lengths of cables between several racks

TRADXTAPP00028-01en DXT3TM Product Description

68(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 • location of other equipment at the same site

• air-conditioning of the equipment room

• sufficient working space around the exchange.

9.3 Environmental conditions

The description of the environmental conditions is covered by the European Telecommunication
Standard ETS 300 019, Equipment Engineering (EE); Environmental conditions and environmental
tests for telecommunications equipment as follows:

ETS 300 019-1-0: Classification of environmental conditions; Introduction.

ETS 300 019-1-1: Classification of environmental conditions; Storage. Class 1.2; Weather-protected,
not temperature-controlled storage locations except the chemically active substances, mechanically
active substances and mechanical conditions (without toppling) which correspond with Class 1.3E.

ETS 300 019-1-2: Classification of environmental conditions; Transportation. Class 2.3; Public
transportation, except temperature range, which is extended down to —50°C.

ETS 300 019-1-3: Classification of environmental conditions; Stationary use at weather-protected

locations. Class 3.1E; Temperature-controlled locations, except the mechanical conditions for vibration
and shock resistance which correspond with Class 3.2. No start-up below 0°C temperature is allowed.

For further information, see ETSI ETS EN 300 132-2, V2.1.2 (2003-09), Environmental Engineering
(EE); Power supply interface at the input to telecommunications equipment; Part 2: Operated by
direct current (dc).

The degree of protection provided by the enclosure (IP code) according to the standard IEC 60529 is
IP 20.

The DXT3 is compliant with the EC Council Directive 2002/95/EC, (“RoHS, Restriction of Hazardous
Substances”) published: OJ L 37/46 of 13.02.2003, and the EC Council Directive 2002/96/EC, (“WEEE,
Waste Electrical and Electronic Equipment”) published: OJ L 37/46 of 13.02.2003. It also complies
with the NEBS (Network Equipment-Building System). For further information, see Environmental
Requirements for B13 HW Platform Release, PI 364956 available from your EADS representative.

Electromagnetic environment

The DXT is compliant with the European EMC directive 89/336/EEC and the standard EN 300 386.

9.4 Functional units and plug-in units of the DXT3

The following chapters describe each functional unit and corresponding plug-in units in the DXT. The
column Position in each table refers to the position of the plug-in unit within the cartridge.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 69(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.1 OMU, Operation and Maintenance Unit

WO RUN P0 P1

AMC0 TE LF P2 P3
DBG

HWAT 0
SERO 0
RST
P S C6

WDU 1
AS 7 0 J7

J6

OPR

CP 816 0
RST

WDU 0
SW0

SW1
USB0

USB1
ON

OFF
AP AMC1

1 2 3 4 5 6 7

dn091258x1x0xen

Figure 14 : Operation and Maintenance Unit (OMU)

Table 10 : Plug-in units of OMU

Position Plug-in unit Use Optionality

01 PSC6–AB Power supply
02 AS7–C LAPD Interface Optional
03 SERO-B Serial interface: V.11, V.24
04 HWAT-B Hardware Alarm Terminal
05–06 DCAR1–A + 2 x HDSAM-A DX200 AMC Carrier + 1 Hard Disk
+ 2 x HDS07–A + 1 x Carrier AMC + Hard Disk SAS 73GB
4334368 + 4GB Memory Stick.
07 CP816–AC Central Processing Unit Memory for
2 x MRD512B / 1 x CP816–AC
MRD1GBB

TRADXTAPP00028-01en DXT3TM Product Description

70(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.2 CLSU, Clock and Synchronization Unit

C L3TG 0

CL3TG 1

00 03

dn091254x1x0xen

Figure 15 : Clock and Synchronization Unit (CLSU)

Table 11 : Plug-in units of CLSU

Position Plug-in unit Use Optionality

00 CL3TG-V CLS 0
03 CL3TG-V CLS 1

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 71(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.3 CLAB, Clock and Alarm Buffer

CLAB 0

CLAB 1
03 04

dn091255x1x0xen

Figure 16 : Clock and Alarm Buffer (CLAB)

Table 12 : Plug-in units of CLAB

Position Plug-in unit Use Optionality

03 CLAB-U CLAB 0
04 CLAB-U CLAB 1

TRADXTAPP00028-01en DXT3TM Product Description

72(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.4 GSW05KB, Switching Network Unit

GSWB 0 GSWB 1

SB1-0 SB1-0 SB1-0 SB1-0

SB1-1 SB1-1 SB1-1 SB1-1

SB2-0 SB2-0 SB2-0 SB2-0

SB2-1 SB2-1 SB2-1 SB2-1

S HIM4T
OPR OPR OPR OPR

SB3-0 SB3-0 SB3-0 SB3-0

SB3-1 SB3-1 SB3-1 SB3-1

SB4-0 SB4-0 SB4-0 SB4-0

SB4-1 SB4-1 SB4-1 SB4-1

SW56B SW56B SW56B SW56B

01 02 03 04 05

dn091259x1x0xen

Figure 17 : Group Switch (GSW05KB)

Table 13 : 512 PCM Bit Group Switch (GSWB) in SW05C-A cartridge

Position SW05C-A Use Optionality

01 SW256B Switching Network (8 kbit/s
channels)
02 SW256B Switching Network (8 kbit/s
channels)
03 SHIM4T Front panel with shim plate
04 SW256B Switching Network (8 kbit/s
channels)
05 SW256B Switching Network (8 kbit/s
channels)

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 73(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.5 CMM, Central Memory and Marker

dn091256x1x0xen

Figure 18 : Central Memory and Marker (CMM)

Table 14 : Plug-in units of CMM

Position Plug-in unit Use Optionality

01 PSC6–AB Power supply
02 AS7–C 0 LAPD
03 SHIM4T Shim plate
04 SWPRO-C Switch Control Processor
05 + 06 SHIM4T Shim plate Security module
SECMO-CP Security Module is optional

TRADXTAPP00028-01en DXT3TM Product Description

74(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.6 CCSU, Common Channel Signalling Unit

CCSU 0 or 2 CCSU 1 or 3

WO RUN P0 P1 WO RUN P0 P1

TE LF P2 P3 TE LF P2 P3

DBG DBG

RST RST

P S C6

P S C6
AS 7 0

AS 7 1

AS 7 0

AS7 1
J7 J7

J6 J6

OPR OPR

CP 816 0

CP 816 0
ON ON

OFF OFF
AP AP AP AP

1 2 3 4 6 7 8 9

dn091253x1x0xen

Figure 19 : Common Channel Signalling Unit (CCSU)

Table 15 : Plug-in units of CCSU

Position Plug-in unit Use Optionality

CCSU 0 / CCSU 2
01 PSC6–AB Power supply
02 AS7–C CCS7 / LAPD
03 AS7–C CCS7 / LAPD *
04 CP816–AC, 2 x MRD512B Central Processing Unit Memory for
/ 1 x MRD1GBB CP816–AC
CCSU 1 / CCSU 3

06 PSC6–AB Power supply

07 AS7–C CCS7 / LAPD
08 AS7–C CCS7 / LAPD *
09 CP816–AC, 2 x MRD512B Central Processing Unit Memory for
/ 1 x MRD1GBB CP816–AC

*) The other ASC-7 is optional.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 75(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
The maximum number of AS7–C plug-in units in the CCSU is two. One AS7–C unit can handle 256
LAPD connections or 64 MTP links. The LAPD and the MTP links can be configured to the same
card, but this is not recommended in TETRA.

9.4.7 PDCU and SIPU

SIPU 0-0 / SIPU 0-1 PDCU 0 / PDCU 1

WO RUN P0 P1 WO RUN P0 P1

TE LF P2 P3 TE LF P2 P3

DBG DBG
S HIM4T

S HIM4T
RST RST
P S C6

P S C6
J7 J7

J6 J6

OPR OPR
CP 816 0

CP 816 0

ON ON

OFF OFF

1 2 3 4 6 7 8 9

dn091260x1x0xen

Figure 20 : SIPU and PDCU Unit

TRADXTAPP00028-01en DXT3TM Product Description

76(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 SIPU 1-0 SIPU 1-1

WO RUN P0 P1 WO RUN P0 P1

TE LF P2 P3 TE LF P2 P3
DBG DBG

S HIM4T

S HIM4T
RST RST

P S C6

P S C6
J7 J7

J6 J6

OPR OPR

CP 816 0

CP 816 0
ON ON

OFF OFF

1 2 3 4 6 7 8 9

dn091261x1x0xen

Figure 21 : Dual SIPU unit

dn091381x1x0xen

Figure 22 : SIPU 2 in CC4C-B cartridge

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 77(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Table 16 : Plug-in units of PDCU and SIPU

Position Name Use Optionality

SIPU 0–0 / SIPU 0–1, SIPU 1–0
01 PSC6–CB Power supply
02 SHIM4T Shim plate
03 CP816–AC, 2 x MRD512B Central Processing Unit for
/ 1 x MRD1GBB CP816–AC
PDCU 0 / PDCU 1, SIPU 1–1

05 PSC6–CB Power supply

06 SHIM4T Shim plate
07 CP816–AC, 2 x MRD512B Central Processing Unit for
/ 1 x MRD1GBB CP816–AC

Table 17 : Server IP Unit (SIPU 2) in CC4C-B cartridge

Position Name Use Optionality

01 PSC6–AB Power Supply Base
02 ESB24–D 24 port LAN switch Base
+ 2 x SFPCS + SFP Transceiver Copper Short Base
+ 2 x SFPCS Range Base *
/ 2 x SFPF2L + SFP Transceiver Copper Short / Optional
Range **
/ SFP FC Transceiver, 2 Gbit/s LC
03 + 04 SHIM4T Shim Plate Base
05 ESB24–D 24 port LAN switch Base
06 SHIM4T Shim Plate Base
07 CP816–AC Central Processor Unit Base,
MRD1GBB Memory for CP816–AC Base

*) These SFPCS connectors to ETH1 & ETH1 ports.

**) SFPCS connectors installed and delivered as default to ETH23 and ETH24 ports. SFPF2L
connectors to ETH23 and ETH24 ports must be ordered separately if 1000Base-Sx interfaces are
needed.

TRADXTAPP00028-01en DXT3TM Product Description

78(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
9.4.8 ET16 and ECE2-NT(C), Exchange Terminals
ET4C 0 (ECE2-NT)
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

ET4C 0 (ECE2-NTC)
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

dn091257x1x0xen

Figure 23 : ET4C-B cartridge within the DXT3 cabinet

There are two kinds of ET plug-in units available for DXT3: ET16 for PCM connections (towards
other DXT exchanges, dispatcher workstations, or base stations) and ECE2-NT(C) for ISDN 30B+D
or R2 or G4WIF connections. One ET16 plug-in unit has always four ports for four PCM connections
and one ECE2 plug-in unit has always two ports for two ISDN 30B+D or R2 or G4WIF connections.
Furthermore, both types of ET plug-in units have their own versions of coaxial and symmetrical cabling.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 79(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
The ET plug-in units are installed in the ET4C-B cartridges. The DXT3 has one ET4C-B cartridge, of
which each have 32 slots available for ET plug-in units. Note however, that ET plug-in units can be
installed in the following way in the ET4C-B cartridges:

A maximum of 4 ET16 plug in units can be equipped to one GT6C-A cartridge. A maximum of 16
ECE2-NT/ECE2-NTC plug in units can be equipped to one ET4C-B cartridge. This means that the
maximum number of ET plug-in units of the DXT3 is 8 ET16 and 16 ECE2-NT/ECE2-NTC and so the
maximum capacity is 64 PCM and 32 ISDN 30B+D connections.

9.5 Basic hardware

The following tables list the basic hardware of the DXT3.

Table 18 : The basic hardware of the DXT3 (Functional units set and equipment)

DXT3 Basic HW Quantity

Object Name
DXT3A0_S Markings Set 1
DXT3A0ET Cabinet Alternative Set 1
DXT3A0ET_C Cable Set 1
DXT3A Cabinet Type Set 1
DXT3A_R Terminator Set 1
DXT3A_C Cable Set 1
DXT3A_M Mechanics Set 1
CMM Functional Unit Set 1
PSC6-AB Power Supply for CPU and Adapter 2
AS7-C Preprocessing Unit for Multichanne 2
SHIM4T Filler Plate 4T 6
SWPRO-C Switch Processor-C 2
CP816-AC Pentium M Central Processing 2
MRD1GBB 1GB registered DDR DIMM 8
Functional Unit Set (LAN Switch) 1
PSC6-AB Power Supply for CPU and Adapter 2
ESB24-A/-D Ethernet Switch for B-series 4
SFPCS Tranceiver Copper Short Range 8
SHIM4T Filler Plate 4T 6
SHIM4T,COP10T Functional Unit Set 1
SHIM4T Filler Plate 4T 2

TRADXTAPP00028-01en DXT3TM Product Description

80(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Table 18: The basic hardware of the DXT3 (Functional units set and equipment) (cont’d.)

DXT3 Basic HW Quantity

Object Name
COP10T Cover Panel 10T 1
OMU Functional Unit Set 1
PSC6-AB Power Supply for CPU and Adapter 1
SHIM4T Filler Plate 4T 1
SERO-B Serial Output Buffered Interface 1
DCAR1-A DX200 AMC Carrier 1 1
HWAT-B Hardware Alarm Terminal 1
HDSAM-A Hard Disk Carrier AMC 2
HDS07-A Hard Disk SAS 73GB 2
CP816-AC Pentium M Central Processing 1

USB FLASH MEMORY STICK 4GB SLC-FLASH 1

MRD1GBB 1GB registered DDR DIMM 1
COP24T Functional Unit Set 1
COP24T Cover Plate 2
GSWB Functional Unit Set 1
SW256B Switching Network for 256 PCMs 4
SHIM4T Filler Plate 4T 1
GTIC Functional Unit Set 1
SHIM4T Filler Plate 4T 9
ET16 Exchange Terminal for 16xE1/T1 1
CLBU Functional Unit Set 1
CLAB-U Clock and Alarm Buffer 2
CLSU Functional Unit Set 1
CL3TG-V Clock and Tone Generator 2
TON-SXCA Tone Product 2
CCSU Functional Unit Set 2
PSC6-AB Power Supply for CPU and Adapter 1
AS7-C Preprocessing Unit for Multichannel 1
SHIM4T Filler Plate 4T 1
MRD1GBB 1GB registered DDR DIMM 1
CP816-AC Pentium M Central Processing 1

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 81(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 PAGE INTENTIONALLY LEFT BLANK

TRADXTAPP00028-01en DXT3TM Product Description

82(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
APPENDIX

Restriction of Hazardous Substances in the

PRC
In this appendix, information is provided with respect to the restriction of hazardous substances applied
in the People’s Republic of China.

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 83(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Figure 24 : Material declaration for the PRC markets.

TRADXTAPP00028-01en DXT3TM Product Description

84(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
Glossary
The meanings of the terms and acronyms used in this document are explained below.

For further information on TETRA definitions, terms and concepts and the meaning of all acronyms
and abbreviations used in EADS TETRA System customer documentation, please see document
EADS TETRA System, Glossary (DN00126469).

Term / acronym Meaning

AIS Alarm Indication Signal
AKD Authentication Key Distribution
AKDC Authentication Key Distribution Compact
AKES Authentication Key Server
CA Client Application
CC4C Common Computer Cartridge 4
CCSU Common Channel Signalling Unit
CDD Configuration and Data Distribution Server
CDR Call Detail Record
CLAB Clock and Alarm Buffer
CLAC Clock and Alarm Buffer Cartridge
CL3TG Clock and Tone Generator
CLOC Clock and Synchronization Cartridge
CLSU Clock and Synchronisation Unit
CMM Central Memory and Marker
CM2C-A Common Computer Cartridge 2
CRC-4 Cyclic Redundancy Check No. 4
DC3C Double Common Computer Cartridge 3
DWS EADS TETRA Dispatcher Workstation
DWSe1 EADS Dispatcher Workstation with E1 Connection
DWSi ISDN-connected EADS Dispatcher Workstation
DWSip TCP/IP-connected EADS Dispatcher Workstation
DWSr EADS Radio Data Dispatcher Workstation
DWSx EADS DWSx Dispatcher Workstation
DXT Digital Exchange for TETRA
DXT3TM Digital Exchange for TETRA
DXTip Digital Exchange for TETRA
DXTTip Digital Exchange for TETRA, transit type

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 85(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 Term / acronym Meaning
ECE2 Exchange Terminal
EMB Ethernet Message Bus
EMC Electromagnetic Compatibility
EMT External Message Transfer
EPCO Enhanced Protocol Converter
EQUIPM Equipment Database
ESB24 Ethernet switch
ET Exchange Terminal
ET16 Exchange Terminal Plug-In Unit
ETS European Telecommunication Standard
FSSN Fleet Specific Short Number
FTAM File Transfer Access and Management Protocol
FTP File Transfer Protocol
G4WIF Generic 4-wire Interface
GPS Global Positioning System
GSW05KB Switching Network Unit
HDU Hard Disk Unit
HLR Home Location Register
IEEE Institute of Electrical and Electronics Engineers
ISDN Integrated Services Digital Network
ITSI Individual TETRA Subscriber Identity
ITU International Telecommunication Union
ITU-T ITU Telecommunication Standardization Sector
LAN Local Area Network
LAPD Link Access Procedure on the D-channel Protocol
LED Light Emitting Diode
LPT Line Printer
MMI Man-Machine Interface
MML Man-Machine Language
MO Magneto-Optical Disk
MS Mobile Station
MTP Message Transfer Part
NMEA National Marine Electronics Association
NTP Network Time Protocol

TRADXTAPP00028-01en DXT3TM Product Description

86(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 Term / acronym Meaning
O&M Operation and Maintenance
OEDATA Configuration Database of OSI Environment
OMU Operation and Maintenance Unit
OSI Open Systems Interconnection
PABX Private Automatic Branch Exchange
PC Professional Cellular Mobile Subscriber
PCB Printed Circuit Board
PCM Pulse Code Modulation
PDCU Packet Data Computer Unit
PDFU Power Distribution Unit
PMR Professional Mobile Radio
PRA Primary Rate Access
PSS Public Safety and Security Mobile Subscriber
PSTN Public Switched Telephone Network
PUP PMR User Part
RAM Random Access Memory
SDL Specification and Description Language
SECMO Security Module
SIPU Server IP Unit
SW05C-A Switching Cartridge 1
SW256B Switch Cartridge for GSWB
SWPRO-C Switch Control Processor
T0 Time Slot 0
TBS TETRA Base Station
TB3 A variant of the TETRA Base Station
TCS Tetra Connectivity Server
TDMS Database Management System
TDL Telenokia Database Language
TETRA Terrestrial Trunked Radio
TRUx Transmission Unit x
TXDATA Database of DXT
UTC Coordinated Universal Time
VDS Virtual Data Storage
VDU Video Display Unit

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 87(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 Term / acronym Meaning
VLR Visitor Location Register
WAN Wide Area Network

TRADXTAPP00028-01en DXT3TM Product Description

88(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
INDEX

A task of .......................................................... 61
duplication
alarm data methods of ................................................... 55
storage of ..................................................... 60 DWS ................................................................ 36
alarm printer .................................................... 61 DWSx .............................................................. 36
alarms DXT3
classification................................................. 60 ESB24.......................................................... 51
authentication .................................................. 26 functional unit CCSU.................................... 50
functional unit CLAB .................................... 51
C functional unit CLSU .................................... 50
functional unit CMM ..................................... 50
call services
functional unit ET; ET16 and
main tasks.................................................... 20
ECE”-NT(C)................................................ 50
capacity ........................................................... 27
functional unit GSW05KB ............................ 50
CDD Server ..................................................... 16
functional unit OMU ..................................... 49
charging........................................................... 22
functional unit PDCU.................................... 50
clock system .................................................... 65
functional unit SIPU ..................................... 50
Common Channel Signalling Unit.................... 37
number of CCSU units ................................. 38
computer units
DXT3/DXTA
means of communication between .............. 33
alternative set, E1 balanced......................... 53
configuration management and
alternative set, E1 unbalanced..................... 53
maintenance
cabinet location set ..................................... 52
functions of................................................... 59
cabinet type set............................................ 52
configurations
changing of .................................................. 60
connections E
between DXT exchanges............................. 37 EADS TETRA Dispatcher Workstation
continuous numbering model .......................... 22 (DWS) ............................................................ 16
cyclic redundancy check electromagnetic environment .......................... 69
for network supervision ................................ 62 Enhanced Protocol Converter (EPCO)............ 36
environmental conditions................................. 69
D Ethernet Message Bus (EMB) ......................... 18
External Message Transfer (EMT) .................. 40
databases
list of............................................................. 44
maintaining copies of ................................... 43 F
means of implementation............................. 43 fault detection
use of semipermanent files .......................... 44 through alarms ............................................. 60
diagnostics through supervision...................................... 60

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 89(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
fault location tasks and actions ......................................... 62
principles of.................................................. 62
faults O
statistics ....................................................... 63
Open Systems Interconnection (OSI)
frame alignment
use of ........................................................... 40
monitoring of for network supervision .......... 62
output reports .................................................. 59
FTAM Protocol................................................. 41
FTP (File Transfer Protocol)
use of ........................................................... 40 P
functional units................................................. 69 plug-in units ............................................... 47, 69
processes
G means of communication ............................. 43
protocols
group calls
FTAM ........................................................... 38
speech item allocation of ............................. 20
IP.................................................................. 38
GSW05KB ....................................................... 19
OSI............................................................... 38
Q3 ................................................................ 38
I
integrated data distribution function................. 38
integrated data distribution functionality .......... 16
Q
Q3 interface
ISDN-connected EADS DWSi ......................... 36
use of ........................................................... 39

L R
lamp panel
Radio Data Dispatcher Workstation
for alarm indication....................................... 61
(DWSr)........................................................... 36
LAPD protocol
real time clock.................................................. 65
use of ........................................................... 39
recovery
logical addresses
distribution of recovery software .................. 61
of computer units ......................................... 18
task of .......................................................... 61
redundancy
M schemes....................................................... 55
monitoring the bit error rate
for network supervision ................................ 62 S
MTP (Message Transfer Part)
SECMO ........................................................... 26
use of ........................................................... 40
signalling
types in use.................................................. 20
N single-DXT network ......................................... 16
NetAct........................................................ 38, 64 slip calculation
network for network supervision ................................ 62
frequency ..................................................... 64 software
synchronizing of clocks ................................ 64 advantages of modularity............................. 55
network architecture ........................................ 17 programming language ................................ 45
network supervision software blocks

TRADXTAPP00028-01en DXT3TM Product Description

90(91) 09/2009

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.
 hierarchy of .................................................. 43 use of ........................................................... 39
speech item allocation ..................................... 20 technical data .................................................. 67
subscriber management .................................. 59 TELNET........................................................... 40
supervision TETRA Base Station (TBS) ............................. 16
task of .......................................................... 60 TETRA Connectivity Server (TCS) .................. 16

T
TCP/IP protocol

DXT3TM Product Description TRADXTAPP00028-01en

09/2009 91(91)

This document is the property of EADS Secure Networks and should not be copied or circulated without permission.