Eads Tetra System Release 6.0: Dxtip and Dxttip Product Description

DXTip and DXTTip Product Description
EADS TETRA System Release 6.0

DN0531796-6-2en
(TRADXTAPP00088) 01/2012
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 Airbus Defence and Space.
Airbus Defence and Space 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 Airbus
Defence and Space and are used as part of the continuous development and improvement of Airbus Defence and Space’s products,
services and the document.
Airbus Defence and Space 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. Airbus Defence
and Space’ total liability for any errors in the document is limited to the documentary correction of errors. Airbus Defence and Space will
not be liable for any direct or indirect damages arising from the use of the document or otherwise relating to the document.
Airbus Defence and Space® is a registered trademark of Airbus Defence and Space. 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 © 2014–2015 Airbus DS SAS, all rights reserved.
DN0531796-6-2en EADS TETRA System Release 6.0
2/91 This document and its contents are the property of Airbus DS SAS and must not be copied or circulated without authorisation
Contents
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 Introduction to the DXTip and the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Different mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 DXTip and DXTTip in the EADS TETRA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 Basic architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 Independent computer units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.2 Distributed architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4.1 Digital switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4.2 Call services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4.3 Speech item allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.4 Database services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.5 Signalling services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.6 Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.7 Resource management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.8 Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4.9 Charging services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.10 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.10.1 MTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.10.2 Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.10.3 Load observation measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.10.4 Field reporting measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.11 IP Packet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.12 ISDN PRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4.13 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1 DXTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 SIPU dimensioning guidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4 System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
EADS TETRA System Release 6.0 DN0531796-6-2en
This document and its contents are the property of Airbus DS SAS and must not be copied or circulated without authorisation. 3/91
4.1 Internal communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1.1 The Message Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1.2 LAPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1.3 SCBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.1.4 Changeovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2 Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.1 DXTip - TETRA Base Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.2 DXT - Dispatcher Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.3 DXT - PSTN/PABX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.4 DXT - conventional PMR systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.5 DXT - other TETRA exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.6 DXT - network management system (NetAct™ for TETRA) . . . . . . . . . . . . . . . . . . . . . . 35
4.2.7 DXT - other systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.8 DXT - TCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.9 DXT - CDD server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3.1 LAPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3.2 TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3.3 Q3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.4 MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.5 FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.6 OSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.7 EMT / EMT v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.8 TELNET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.9 FTAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.1 Implementation system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.2 Semipermanent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.3 Several databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.3 Programming languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1 DXT HW principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.1 Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.2 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.3 Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2 Description of DXT cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2.1 DXTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2.1.1 Functional units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2.1.2 Cabinet mechanics and cabling modules of DXTip/DXTA . . . . . . . . . . . . . . . . . 47
6.2.2 DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2.2.1 Functional units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.2.2.2 Cabinet mechanics and cabling modules of DXTB. . . . . . . . . . . . . . . . . . . . . . 50
6.3 Basic HW configuration and optional equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.3.1 Basic HW configuration and optional equipment of the DXTip . . . . . . . . . . . . . . . . . . . . 51
6.3.2 Basic HW configuration and optional equipment of the DXTTip . . . . . . . . . . . . . . . . . . . 52
7 Resilience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1 Modularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2 Duplication (redundancy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.1 2n redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.2 Replaceable n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.2.3 Complementary n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.2.4 No redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.1 Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.1.1 Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.1.2 Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.1.3 Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.1.4 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1.5 Diagnostic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.2 Network maintenance functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.2.1 Network supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.2.2 Supervision of 2-Mbit/s circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.2.3 Compilation of disturbance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.3 Network management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.4 Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.4.1 Network synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.4.2 The clock system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.4.3 Real time clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
9 Technical data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1 Basic technical features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.2 Equipment room requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.3 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.4 Functional units and plug-in units of the DXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.4.1 OMU, Operation and Maintenance Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.4.2 CLSU, Clock and Synchronization Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.4.3 CLAB, Clock and Alarm Buffer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.4.4 GSW1KB, Switching Network Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.4.5 CM, Central Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
9.4.6 CCC, Call Control Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.4.7 ACU, Authentication Centre Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9.4.8 STU, Statistical Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
9.4.9 CCSU, Common Channel Signalling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
9.4.10 EDU, PDCU, SIPU and CCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
9.4.11 ET, Exchange Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.5 Basic HW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
A Restriction of Hazardous Substances in the PRC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
List of Tables.
Table 1 The different mechanics of the DXTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 2 Capacity of the DXTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 3 Capacity of the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 4 The supported SIPU configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 5 Plug-in unit sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 6 Basic HW configuration of the DXTip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 7 Optional HW of the DXTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 8 Basic HW configuration of the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 9 Optional HW of the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 10 Classification of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 11 Technical data of the DXTip/DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 12 Plug-in units of OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 13 Plug-in units of CLSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 14 Plug-in units of CLAB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 15 Plug-in units of GSW1KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 16 Plug-in units of CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 17 Plug-in units of CCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 18 Plug-in units of ACU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 19 Plug-in units of STU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 20 Plug-in units of CCSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 21 Plug-in units of EDU, PDCU, SIPU and CCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 22 The basic HW of the DXTip (Functional units set and equipment) . . . . . . . . . . . . . . . . . . . . 78
Table 23 The basic HW of the DXTTip (Functional units set and equipment) . . . . . . . . . . . . . . . . . . . 79
List of Figures.
Figure 1 DXTip with doors closed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 2 The DXTTip with doors closed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3 A single-DXT network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 4 DXT network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 5 DXTip exchanges connected to ISDN/PSTN via an ISDN exchange . . . . . . . . . . . . . . . . . . 22
Figure 6 DXTip exchanges connected to a private network with ISDN PRA . . . . . . . . . . . . . . . . . . . 23
Figure 7 DXTip - TBS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 8 DXT - Dispatcher System Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 9 Functional units of the DXTip/DXTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 10 Layout of the DXTip/DXTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 11 Functional units of the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 12 Layout of the DXTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 13 2n redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 14 Replaceable n+1 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 15 Configuration of the DXT cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 16 Operation and Maintenance Unit (OMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 17 Clock and Synchronization Unit (CLSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 18 Clock and Alarm Buffer (CLAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 19 Group Switch (GSW1KB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 20 Central Memory (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 21 Call Control Computer (CCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 22 Authentication Centre Unit (ACU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 23 Statistical Unit (STU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 24 Common Channel Signalling Unit (CCSU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 25 Dual Computer Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 26 ET4C cartridge within the DXTip/DXTA cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 27 Material declaration for the PRC markets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
DOCUMENT AMENDMENTS
VERSION DATE COMMENTS CHAPTER

UPDATED
6-2 01/2012 Table 2: a note has been added concerning Dispatcher 3.1
workstations and TCS clients.
6-1 03/2011 The EMT v2 procotol has been added. 2.4.5 , 4.3 ,
4.3.7
06 03/2010 Release 6.0 version. Amount of traffic channels and 3.1
packet data channels corrected.
5-2 03/2010 A disclaimer about the upper capacity limit for dynamic 3.1
load has been added after Table 2.
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 and DXTTip, dn064171
13. Environmental Requirements for B12 HW Platform Release M98 DX 200 product Family (CAU
109266/3.0 en)
PAGE INTENTIONALLY LEFT BLANK
1 About this document
This document describes the EADS DXTip and DXTTip digital exchanges.
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.
Note
In this document, the acronym DXT is used to refer to both the DXTip and DXTTip. The product names DXTip
and DXTTip are used when describing functions specific to either product.
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@cassidian.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 DXTip and DXTTip and explains their role in the EADS
TETRA System.
• Chapter 3 describes the capacity of the DXTip and DXTTip.
• 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 DXT software.
• Chapter 6 describes the DXT hardware.
• Chapter 7 lists the resilience mechanisms of the DXT.
• Chapter 8 describes the management of the DXT.
• Chapter 9 lists the basic technical data.
• 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.
2 Introduction to the DXTip and the DXTTip
This chapter introduces the DXTip and DXTTip as follows:
• general
• DXTip and DXTTip in the EADS TETRA System
• basic architecture
• functions
2.1 General
The DXTip is an access-layer switch in the EADS TETRA System. The DXTip 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 DXTTip is a high capacity, two-cabinet transit exchange in the EADS TETRA System. The DXTTip
is used in the EADS TETRA System as the switching element to which dispatching systems, network
management centres, CDD Server and external network interfaces can be connected. Base stations cannot
be connected to the DXTTip.
The DXTip and DXTTip are built on the generic DX 200 fault-tolerant computing platform developed by Nokia
Siemens Networks. The DXTip and the DXTTip comply 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.
Figure 1 : DXTip with doors closed
Figure 2 : The DXTTip with doors closed.
2.1.1 Different mechanics

The table below introduces the different 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
DXT256 with M92 mechanics

DXTip basic with M98F mechanics
DXTip with extension cabinet 1 based on M98F mechanics
DXTip with extension cabinets 1 and 2 based on M98F mechanics
DXTTip with M98F mechanics
DXTip with M98F2 mechanics
DXTTip with M98F2 mechanics
2.2 DXTip and DXTTip in the EADS TETRA System

In the EADS TETRA System, the DXTip is the centre of communications, supporting fast call set-up and high
traffic throughput. The DXTTip 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 DXTip and DXTTip have 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
DXTip 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 DXTip. Base stations cannot be connected to the DXTTip.
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.
TB3-7
PSTN
TB3-6
ISDN PRA
TB3-5 (optional )
DXT
TB3-4
TB3-3 DWS
TB3-2
TB3-1 dn 03474824 x2x0xen
Figure 3 : A single-DXT network
Figure 4 illustrates a more complex DXT network architecture.
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 Message Bus (MB) 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.
2.4 Functions
The DXT provides the following functions:
• digital switching
• call services
• speech item allocation
• database services
• signalling services
• trunking (DXTip only)
• resource management
• numbering
• charging services
• statistics
• data services
• IP packet data
• ISDN PRA connection to PSTN/PABX
• digital R2 connection to PSTN/PABX
• authentication
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.
The DXTTip provides the same functions as the DXTip, except for trunking, radio channel management
and TBS management.
2.4.1 Digital switching

The Switching Network Unit (GSW1KB) 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 Call Control
Computer, CCC). 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.
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 (DXTip only),
– for connecting to Dispatcher Systems for TETRA
– for internal communication CL3TG and ET units.
• RS232 for connecting to MML terminals and line printers.
• EMT / EMT v2 signalling
– the EMT protocol is used for TCP/IP connections to the CDD and the TCS.
– the EMT v2 protocol is used for TCP/IP connections to 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).
2.4.6 Trunking
The DXTip 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 (DXTip)
• 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 (GSW1KB) of the DXT via PCM circuits,
and the resource management software allocates resources to them as subslots of the PCM time slots.
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 EADS TETRA System, 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:
• Statistical Unit (STU): Integrated part of Statistics.
• Call Control Computer (CCC): If the STU is not in use, also the integrated part of Statistics is handled
by the CCC.
• Operation and Maintenance Unit (OMU): Statistics (generation of reports).
• Common Channel Signalling Unit (CCSU): MTP statistics (distributed processing).
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 (in the DXTip only)
• individual call
• group call
• group management
• roaming (in the DXTip only)
• 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.
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. There are no packet data instances
implemented in the DXTTip because there are no direct connections between DXTTip exchanges and base
stations. The DXTTip acts only as transmission equipment for packet data. 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.
DXTip
DXTip
PRA PUP
ISDN exchange
PUP DXTip
PRA
DXTip
PRA PUP
PRA
PSTN
ISDN
Exchange
Key:
DXTip = Digital Exhange for TETRA
ISDN = Integrated Services Data Network
PRA = Primary Rate Access
dn 0572319 x2x0xen
PSTN = Public Switched Telephone Network
PUP = PMR User Part
Figure 5 : DXTip exchanges connected to ISDN/PSTN via an ISDN exchange
DXTip
PABX
DXTip PRA
PUP
PABX
DXTip PUP PABX QSIG
or PRA
QSIG ISDN exchange
PUP or PRA QSIG
PRA QSIG
or PRA or PRA
QSIG PABX
or PRA
PSTN
Key:
DXTip = 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 x2x0xen
QSIG = Symmetric access signalling system , modified from ISDN PRA
Figure 6 : DXTip exchanges connected to a private network with ISDN PRA
2.4.13 Authentication
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 unauthorised recipients.
• Tampering: the unauthorised alteration of information (including programs).
• Resource stealing: the use of facilities without authorisation.
• 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.
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 Authentication Centre Units (ACUs) of the DXT. In the basic
DXTip, the SECMO units are installed in the CM.
Note
SECMO plug-in units may not be available in some countries because of national export control classification
restrictions.
3 Capacity
3.1 DXTip
The following table presents the maximum capacity available for the user organisation and the maximum
connection capacity of the DXTip.
Table 2 : Capacity of the DXTip
Capacity with external Capacity with Integrated

CDD server Data Distribution
functionality
Subscribers (HLR/VLR) 40000/40000 30000/30000
Groups 10000 10000
Organisation blocks 5600 5600
Dispatcher workstations and TCS 256/128 64/64
clients *)
Altogether/with voice
*) One DXT can handle simultaneously up to 3 000 audio
and event monitored groups which can be divided among
the clients.
TCS servers 12 6
ISDN PRA (30B+D), see note below 16 (480 lines) 16 (480 lines)
Carriers and base stations • 320 TETRA radio carriers, 1240 channels (M98F2)
• equipped in max 128 TBSs

PSTN and PABX connections, see • 240 interfaces for PSTN and PABX exchanges through
note below ECE2–NT(C) plug-in units.
Conventional PMR systems and • 240 interfaces through ECE2–NT(C) plug-in units.
other systems, see note below
Connections between DXTip and • 960 8 kbit/s speech channels per DXT
other DXT exchanges
• 160 MTP signalling links
Exchange Terminals (ET) • 64 + 16 PCM/2Mbit interfaces
Exchange Terminal Types, see the • 16 ET4E(-C)
second note below
• 8 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.
Note
The maximum capacity of the DXTip/DXTA 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.11 . 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.
Note
The DXTip HLR max size can be 70 000, if there are no TBSs connected on the exchance (acting as HLR).
3.2 DXTTip
The following table presents the maximum capacity available for the user organisation and the maximum
connection capacity of the DXTTip.
Table 3 : Capacity of the DXTTip
Capacity
Subscribers (HLR/VLR) 70000/-
Groups 10000
Organisation blocks 5600
Dispatcher workstations 256/128
Altogether/with voice
TCS servers 16
PSTN and PABX connections, see • 240 interfaces for PSTN and PABX exchanges
note below through ECE2–NT(C) plug-in units.
Conventional PMR systems and • 240 interfaces through ECE2–NT(C) plug-in units.
other systems, see note below
Table 3: Capacity of the DXTTip (cont'd.)
Capacity
Connections between DXTip and • 320 MTP signalling links
other 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 • 128 + 32 PCM/2Mbit interfaces
second note below
ISDN PRA (30B+D) • 32 ISDN 30B+D connections
Exchange Terminal Types • 32 ET4E(-C)
• 16 ECE2–NT(C)
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.
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
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/DXTip) 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.
• 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.
Note
If a DXTip 1–cabinet with M98F mechanics is used, some of the clients need to be connected via E1/ISDN to
reach the maximum number of clients.
System without CDD:
• DXT with Integrated Data Distribution can connect 64 clients.
M98F2 mechanics
SIPU dimensioning for M98F2 (DXTip):
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.
SIPU dimensioning for M98F2 (DXTTip):
The client capacity is the same as shown above for the DXTip with M98F2 mechanics. However, the greater
number of SIPU pairs in the DXTTip provides more possibilities for load sharing and redundancy.
4 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 a Message Bus (MB) as the route for internal communication. The MB 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 The Message Bus

The Message Bus (MB) is a synchronous parallel bus with 2n redundancy (see Chapter 7 ). Each computer
unit contains two separate Message Bus Interface (MBIF) plug-in units, one for each bus. The computer units
communicate with each other by exchanging messages via the Message Bus.
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)
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 Call Control Computer (CCC) by serial 64
kbit/s links and the LAPD protocol. These links are maintained during a possible changeover of the CCC,
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) (DXTip)
• 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
• other systems
The DXTTip has no interfaces to base stations.
4.2.1 DXTip - TETRA Base Station
The DXTip - TBS connections use the E1 interfaces included in the ET4E(-C) 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 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.
DXTip TB3
G.703/G.704
2 Mbit/s
8 Mbit/s FXC
GSW1KB ET4E
TB3
FXC
Key: DXTip = Digital Exchange for TETRA

GSW1KB = Switching Network Unit
ET4E = Exchange Terminal plug-in unit
TB3 = TETRA Base Station
dn0572334 x1x0xen
FXC = Flexible Cross Connect unit
Figure 7 : DXTip - TBS interface
Note
One TBS does not reserve the whole 2-Mbit/s line. TBSs can be looped and chained.
The number of carriers in a TBS determines the required transmission capacity between the DXTip 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 DXTip and the TETRA
Base Station Controller (TBC). The messages between the DXTip and the TBC are transferred through the
TETRA Transceiver (TTRX) unit with optional 64-kbit/s link messages.
DXTip — 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.
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 DWSx 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 ET4E(-C) 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 ET4E(-C) plug-in unit to the ISDN Primary Rate Interface.
• The DWSr is connected to the DXTip 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.
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
dn0572346x2x0xen
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.
Maximum number of CCSU units:
• DXTip: 4.
• DXTTip: 4 + 2.
™ 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 ET4E 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:
• LAPD
• TCP/IP
• Q3
• MTP
• FTP
• EMT / EMT v2
• TELNET
• FTAM
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.
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
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 / EMT v2

External Message Transfer (EMT) and EMT v2 are EADS proprietary communication protocols.
EMT 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.
EMT v2 provides increased capacity and reliability by enabling the TCS server to use services implemented
by the DXT applications. The TCS servers are connected to the DXT through a TCP/IP connection, but
they access the services by using DMX messages.
4.3.8 TELNET
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.
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.
5 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 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 Several databases
The DXT contains several databases :
• TXDATA
– Exchange database.
– Organisation 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 (in DXTip only).
– 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
– 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.
6 Hardware
This chapter describes the DXT hardware: functional units, cartridges, racks, and cabling. At the end of the
chapter are included tables listing the contects of the basic HW configuration and the optional equipment
available for the DXTip and the DXTTip. The DXTip consists of a single cabinet, the DXTA. The DXTTip
consists of two cabinets: the DXTA and the DXTB.
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.
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 DXTA), 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.1.2 and 6.2.2.2 .
6.2 Description of DXT cabinets

The following sections describe the DXT cabinets for the DXTip and the DXTTip. The DXTip consists of a
single cabinet, the DXTA. The DXTTip consists of two cabinets: the DXTA and the DXTB.
6.2.1 DXTip
6.2.1.1 Functional units
The DXT 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 DXTip.
CPETS -C CLAB CPEA
CPETC -C Ext.
ISDN PRA to P ABX, PSTN 2 Mbit/s CLSU sync .
(To R 2 and G 4WIF 2 Mbit/s ECE 2
interfaces )
To DWS , NMWS, TBS , 2 Mbit/s
DXT
2 Mbit/s ET4
CPLAN-A GSW 1KB

CPLC 18
OMU LAN
O&M LAN CCC LAN
ESB 26 PDCU LAN
User plane LAN Switch SIPU LAN
LAN
LAN to LAN to LAN to
ESB 26 ESB 26 ESB 26
NTDU NTDU
NTDU
SIPU NTDU
PDCU CCC CCSU
MB
LAN to OMU
CM ESB 26 CPRS -A
VDU/
dn 0532362 x1x0xen LPT
Figure 9 : Functional units of the DXTip/DXTA
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 and also
MMI interface to the DWS Management) and the billing system and towards other exchanges to
provide remote sessions and remote file transfer.
• CM
Central Memory.
In the DXTip, CM contains all data except group and workstation home location data (this data is in
the CCC). The role of the CM is to act as the main data management unit of the exchange. The
CM is 2N redundant.
• CCC
Call Control Computer.
The CCC controls the switching unit and manages call handling and traffic administration functions,
network resource management, and communication with other EADS TETRA network elements and
with other networks. The CCC 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
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.
• ET; ET4E(-C) 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.
• GSW1KB
Switching Network Unit.
The GSW1KB is a digital, non-blocking switch for switching voice and data, and for the connections of
signalling circuits. The GSW1KB is 2N redundant.
• CLSU
Clock and Synchronisation Unit.
CLSU contains inputs for external synchronisation signals fed through the OMU through a LAPD
channel. The CLSU generates the clock signals necessary for synchronising 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 synchronised to four inputs. It has also two external synchronisation inputs. The
CLSU collects the wired alarms from other units in the DXTip, 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.
• ESB26
An Ethernet switch connected to the CM. It is used as a switch between different units and can also be
used as a switch for units outside the exchange.
Location of the functional units
Figure 10 shows the location of the functional units in the DXTip/DXTA.
DXTA CABLING
CABINET
PDFU-B PDFU-B
PDFU 0 PDFU 1
0
CPBP 0
CLAB 0, 1
DC3C-A DC3C-A
CLS 0, 1
CLOC-B
CLAC-B
SIPU 0 PDCU 0 SIPU 1 PDCU 1
CPEA 1
1 0 2 4 6 8 10 CPRS-A 2
SW10C-A SW10C-A
CM2C-A
CPLC18 3
GSWB GSWB
0 1 OMU
CPLAN-
FTRB-A 0 FTRB-A 1 4
2 0 3 6 A
CC4C-A CC4C-A CC4C-A CC4C-A CPLAN- 5

A
CCC CCC CM CM
0 1 0 1 CPETS/
6
CPETC
3 0 3 6 9
CPETS/
CC4C-A CC4C-A CC4C-A CC4C-A CPETC 7
CCSU CCSU CCSU CCSU CPETS/ 8

0 1 2 3 CPETC
FTRB-A 2 FTRB-A 3
4 0 3 6 9 CPETS/
9
CPETC
DC3C-A
ET4C-B
SIPU 2 SIPU 3 CPETS/
CPLAN 10
ET4C 0 CPETC
5 0 2 6
dn0532635x1x0xen
FRONT SIDE
Figure 10 : Layout of the DXTip/DXTA
6.2.1.2 Cabinet mechanics and cabling modules of DXTip/DXTA
• Cabinet type set

– mechanics
– cables
– setting modules
– panels
• Cabinet location set
– cables
– setting modules
– markings
• Alternative set, E1 balanced
– panels
– cables
• Alternative set, E1 unbalanced
– panels
– cables
6.2.2 DXTTip
6.2.2.1 Functional units
The DXT 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 11 shows the
functional units, their connections, and the resilience mechanisms of a fully equipped DXTTip exchange.
CLAB
CPEA
CPETS -C or Ext.
CLSU
CPETC -C sync .
2 Mbit/s
ISDN PRA to P ABX,
2 Mbit/s ECE 2
PSTN (To R 2 and
G4WIF interfaces ) 2 Mbit/s
To DWS , NMWS, 2 Mbit/s ET4
TBS , DXT GSW 1KB
CPLAN-A or OMU LAN
CPLC 18 STU LAN
SIPU LAN
O&M LAN ESB 26 PDCU LAN
User plane LAN Switch CCC LAN
LAN to LAN to EDU LAN
LAN LAN to
ESB 26 ESB 26 ESB 26
NTD NTD
NTD U
SIPU
U PDCUU CCC CCSU
MB
CPRS -A
VDU/
EDU CCM CM ACU STU OMU
LPT
LAN to LAN to LAN to

ESB 26 ESB 26 ESB 26 dn 0532432 x2x0xen
Figure 11 : Functional units of the DXTTip
The functional units are briefly described in Section 6.2.1.1 and 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
• Extensions
– 4 SIPU computer pairs (2 + 2 = 4).
– 4 CCSU computer units (4 + 2 = 6).
The following list includes the functional units that are included in the DXTB but not in the DXTip/DXTA.
• ACU
Authentication Centre Unit. In the DXTTip it is also the HLR database.
The ACU is designed to store authentication data, generate random numbers and execute security
algorithms. The ACU is 2N redundant.
• STU
Statistical Unit.
The Statistical Unit is designed to handle tasks related to call charging and statistics. The STU is 2N
redundant.
• CCM
The Common Channel Management Unit is designed to increase the processing capacity of the
centralised functions of the Message Transfer Part (MTP). The CCM is 2N redundant.
• EDU
Enhanced Data Unit. Status and SDS application.
The EDU is needed to reduce the computer load of the CM and/or CCC computer units. EDU is used
for processing status and SDS messages and for digit analysis. It also contains numbering data.
The EDU is 2N redundant.
Location of the functional units
Figure 12 shows the location of the functional units in the DXTB cabinet.
DXTB
PDFU-B PDFU-B
PDFU 0 PDFU 1
0
CLAB 2, 3
CLAB 4, 5
DC3C-A DC3C-A
CLAC-B
CLAC-B
SIPU SIPU SIPU SIPU
4 5 6 7
1 0 1
2 4 6 8
0
CM2C-A CM2C-A
ACU 0 ACU 1
SD 0 ACU SD 1 ACU
FTRB-A 0 FTRB-A 1
2 0 6
CC3C-A CC3C-A DC3C-A
STU 0 STU 1 CCM 0

SD 0 STU SD 1 STU
3 0 4 8 10
DC3C-A DC3C-A DC3C-A

EDU EDU CCM
0 1 1
FTRB-A 2 FTRB-A 3
4 0 2 4 6 8 10
CC4C-A CC4C-A
ET4C-B
CCSU CCSU
4 5 ET4C 1
5 0 3 6
dn0532662x2x0xen
FRONT SIDE
Figure 12 : Layout of the DXTB
6.2.2.2 Cabinet mechanics and cabling modules of DXTB
• Cabinet type set
– mechanics
– cables
– setting modules
• Cabinet location set
– cables
– setting modules
– markings
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 DXTip and the DXTTip, respectively.
6.3.1 Basic HW configuration and optional equipment of the DXTip

Table 6 : Basic HW configuration of the DXTip
DXTip Basic HW Rel. 4.5/5.0/5.5 Quantity

Object name
Rack: cartridges, Cabling rack and internal
cabling.
Assembly to cabinet
MMI Terminal VT5530 1 pcs
PRINTER LPT38–U 1 pcs
Alarm Panel EXAU-A 1 pcs
Basic SW for DXT 1 pcs
Functional unit OMU 1 pcs
Functional unit CM 2 pcs
Functional unit CCC 2 pcs
Functional unit CCSU 3 pcs
Functional unit ET; ET4E 4 pcs
Functional unit GSWB 2 pcs
Functional unit CLOC 1 pcs
Functional unit CLAC (CLAB) 1 pcs
Functional unit (SWU) ESB26 2 pcs
Table 7 : Optional HW of the DXTip
DXTip optional HW Rel. 4.5/5.0/5.5 Quantity

Object name
Functional unit SIPU 2 pairs
Functional unit PDCU 1 pair
Echo Cancelling Plug-in Unit max 8 pcs
(ECE2-NT/ECE2-NTC)
Functional unit ET; ET2E max 8 pcs
6.3.2 Basic HW configuration and optional equipment of the DXTTip
Table 8 : Basic HW configuration of the DXTTip
DXTTip Basic HW Rel. 4.5/5.0/5.5 Quantity

Object name
Rack: cartridges, Cabling rack and internal
cabling.
Assembly to cabinet
MMI Terminal VT5530 1 pcs
PRINTER LPT38–U 1 pcs
Alarm Panel EXAU-A 1 pcs
Basic SW for DXT 1 pcs
Functional unit OMU 1 pcs
Functional unit CM 2 pcs
Functional unit CCC 2 pcs
Functional unit GSWB 2 pcs
Functional unit CLOC 1 pcs
Functional unit CLAC 3 pcs
Functional unit ACU 2 pcs
Functional unit STU 2 pcs
Functional unit EDU 2 pcs
Functional unit CLAC (CLAB) 6 pcs
Functional unit ESB26 4 pcs
Functional unit CCM 1 pair
Functional unit SIPU 1 pair
Table 9 : Optional HW of the DXTTip
DXTTip optional HW Rel. 4.5/5.0/5.5 Quantity

Object name
Functional unit SIPU 3 pairs
Echo Cancelling Plug-in Unit
(ECE2-NT/ECE2-NTC)
Functional unit ET; ET4E
Functional unit ET; ET2E
7 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 13 .
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.
dn00115541 x1x0xen
Figure 13 : 2n redundancy
2n redundant units in the DXT are:

• Call Control Computer (CCC)
• Clock and Tone Generator (CL3TG)
• Clock and Alarm Buffer (CLAB)
• Clock and Synchronisation unit (CLSU)
• Central Memory (CM)
• MO disk
• Hard Disk Unit (HDU)
• Switching Network Unit (GSW1KB)
• Statistical Unit (STU)
• Enhanced Data Unit (EDU)
• Authentication Centre Unit (ACU)
• Common Channel Signalling Management Unit (CCM).
Even though not a functional unit, the 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 14 .
dn0572361x1x0xen
Figure 14 : Replaceable n+1 redundancy
CCSU and PDCU (with basic IP packet data service) are units with replaceable n+1 redundancy.
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.
8 Management
This chapter describes the management of the DXT as follows:
• operation and maintenance
• network maintenance functions
• synchronisation
• 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 MO disk.
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
• 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 10 .
Table 10 : 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.
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.
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 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 ET4E 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.
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 synchronisation
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
synchronisation is achieved by synchronising 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 synchronised to the master clock in hierarchical order. The synchronisation signals are
carried by 2 Mbit/s circuits, from which the clock frequency is derived for synchronisation in the receiving end.
Synchronisation of the network is usually based on a synchronisation plan. The plan defines the hierarchical
levels and takes into account the ITU-T stability requirements and the interfaces of the synchronising
2-Mbit/s circuits.
Network elements connected to a fully analogue network operate plesiochronously. In that case, there is no
external synchronisation signal. All the clocks run independently of each other. Both the equipment of the
network element and the PCM multiplex equipment are then synchronised to the fundamental frequency
created by the exchange.
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 synchronisation information is lost.
In normal network conditions, the synchronisation information is carried by selected 2-Mbit trunk circuits from
upper to lower hierarchical levels according to the synchronisation plan. The clock system selects the active
synchronisation 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, synchronisation signal or synchronisation 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 synchronisation 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.
9 Technical data
This chapter gives the basic technical data on the DXT, briefly lists the requirements for the equipment
room, and describes the main environmental conditions. For dimensions and configuration of the DXT, see
also Figure 15 .
9.1 Basic technical features

Table 11 lists the basic technical data of the DXT exchange.
Table 11 : Technical data of the DXTip/DXTTip
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
2 racks 210 cm
Depth 60 cm
Weight DXTA with cabling cabinet: 375–450 kg.
DXTB: 275–350 kg.
Power supply -40 to -72 V
Power consumption (maximum) Total 3,9 kW:
DXTA: 2,0 kW
DXTB: 1,9 kW
Maximum number of 2 Mbit interfaces DXTip: 64 PCMs for TBSs and DWSs or max. 16pcs.
PCM/30B+D 30B+D interfaces or a combination of these.
DXTTip: 128 PCMs or max. 32 pcs. 30B+D interfaces
or a combination of these.
LEFT TO RIGHT
WIDTH 2100 mm
WIDTH 1200 mm
Cabling DEPTH
DXTA cabinet DXTB 600 mm
1A 1B
FRONT SIDE OF CABINETS
Cabinet's side plates (SCP) are ready-assembled in DXTA.

In case of the DXTTip (DXTA+DXTB), SCP
from DXTA is moved to DXTB.
Cabinet's top cover plates:

Cabinet's top cover plates (TCCP) are ready-assembled in
DXTA and DXTB.
In case of the DXTTip (DXTA+DXTB), TCCPs are in ready-
assembled places. dn0542231x3x0xen
Figure 15 : Configuration of the DXT cabinets
For more details, refer to the document Installing the DXTip and DXTTip, 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
• 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.
The degree of protection provided by the enclosure (IP code) according to the standard IEC 60529 is IP 20.
The DXT complies 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 the document Environmental Requirements for B12
HW Platform Release M98 DX 200 product Family (CAU 109266/3.0 en).
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 DXT

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.
The plug-in units are the same for both the DXTip and the DXTTip with the following exceptions:
• The CCM is part of the standard equipment in the DXTTip.
9.4.1 OMU, Operation and Maintenance Unit
POWER
DBG OFF
RST
MBIF 0
MBIF 1
POWER POWER
HWAT
OFF OFF
AS7-C
SERO
PSC6
J
7
CPU
J
6
MO-disk
OPR OPR OPR
WO
RUN
RS
LF
T
OL
HDU 0
HDU 1
T
E
SW0 AP
DRAM
SW1
SB
CPCI
SCSI
ON ETx
0 OF
ERx 0 OFF
F
OFF ETx
AP 1 OF
ERx 1
F
1 2 3 4 5 6 7 8 9 10 12 13 14
dn0533673x1x0xen
Figure 16 : Operation and Maintenance Unit (OMU)
Table 12 : Plug-in units of OMU
Position Plug-in unit Use Optionality

01 PSC6–A Power supply
03 AS7–C LAPD Interface
06 SERO-B Serial interface: V.11, V.24
07 HWAT-A Hardware Alarm Terminal
08 MBIF-C MB 0
09 MBIF-C MB 1
10–11 CP816-A Central Processor Unit
(memory size 512 MB)
12 MO91 + ODPU-A MO disk unit with adapter
13 WDW73 + HDPU-A Hard Disk Unit with adapter
14 WDW73 + HDPU-A Hard Disk Unit with adapter
9.4.2 CLSU, Clock and Synchronization Unit
CL3TG 0
CL3TG 1
00 03
dn0534115 x1x0xen
Figure 17 : Clock and Synchronization Unit (CLSU)
Table 13 : Plug-in units of CLSU

00 CL3TG-S CLSU
03 CL3TG-S CLSU
9.4.3 CLAB, Clock and Alarm Buffer

CLBU
CLAB 1
CLAB 0
03 04
CLBU dn0534181 x1x0xen
Figure 18 : Clock and Alarm Buffer (CLAB)
Table 14 : Plug-in units of CLAB

03 CLAB-S CLBU
04 CLAB-S CLBU
9.4.4 GSW1KB, Switching Network Unit

SW10C-A
SW128B 2
SW128B 0
SW128B 1
SW128B 3
01 02 03 04 05 06 07 08 09
SW128B can not be equipped to slot 09.
Available slots for SW128B are 01 ... 08.
dn0533985 x1x0xen
Figure 19 : Group Switch (GSW1KB)
Table 15 : Plug-in units of GSW1KB

01 SW128B Switching
02 SW128B Switching
03 SW128B Switching
04 SW128B Switching
9.4.5 CM, Central Memory
DB
ETH
G
3
RS
T
SECMO
MBIF 0
MBIF 1
ETH
PSC6
J
CPU
7
ESB26
J
ETH
6
5
ETH
6
OPR OPR OPR WO
RU
OPR LN
F
O
RS L
T T
E
A
P
ETH
1 DRA
SM
B
CPC
I
ETH
SCS
2
O I
ETx
N 0
ERx
0
OFF ETx
SER
1
1
ERx
1
1 2 3 4 5 6 7
dn05111525x1x0xen
Figure 20 : Central Memory (CM)
Table 16 : Plug-in units of CM

02 ESB26 Ethernet switch
04 SECMO-CP Security module Optional
05 MBIF-C/-CR Message Bus 0
07 CP816-A CPU
(memory size 2 GB)
9.4.6 CCC, Call Control Computer
DBG
RST
SWCOP
MBIF 0
MBIF 1
AS7-C
J7
PSC6
CPU
J6
OPR OPR OPR WO

RUN
LF
OL
TE
AP
DRAM
SB
CPCI
SCSI
ON ETx0
ERx0
OFF ETx1
AP
ERx1
1 2 3 4 5 6 7
dn0534057x1x0xen
Figure 21 : Call Control Computer (CCC)
Table 17 : Plug-in units of CCC

02 AS7–C AS7 0
04 SWCOP-A Switch Control
05 MBIF-C Message Bus 0
07 CP816-A CPU
(memory size 1 GB)
9.4.7 ACU, Authentication Centre Unit
POWER OFF
DBG
RS
T
POWER
S ECMO
OFF
MBIF 0
MBIF 1
J
P S C6
CP U
ES B26
J
6
OPR OPR OPR
MO-dis k
WO
RU
OPR LN
F
O
RS L
HDU 0
T T
E
A
P
DRA
SM
B
CPC
I
SCS
O I
ETx
N 0
ERx OFF
0
OFF ETx
1
ERx OFF
1
1 2 3 4 5 6 7 8 9 10 12 13 14
dn 05111501 x2x0xen
Figure 22 : Authentication Centre Unit (ACU)
Table 18 : Plug-in units of ACU

05 ESB26 Ethernet switch
07 SECMO-CP Security module 1) Optional
10 CP816-A CPU
(memory size 2 GB)
12 MO91 + ODPU-A MO Disk unit with adapter
13 WDW73 + HDPU-A Hard Disk unit with adapter
1) SECMO-CP is equipped in the DXTTip when authentication is in use.
9.4.8 STU, Statistical Unit
POWER OFF
DBG
RST
POWER
OFF
MBIF 1
MBIF 0
PSC6
J7
CPU
J6
OP
OPR OPR
MO-disk
R WO
RUN
L
F
OL
TE
HDU
AP
DRAM
SB
CPCI
SCSI
ON ETx0
OFF
ERx0
OF
F ETx1
OFF
ERx1
1 2 3 4 5 6 7 8 9 10
dn0534084 x1x0xen
Figure 23 : Statistical Unit (STU)
Table 19 : Plug-in units of STU

02 WDW73 + HDPU-A Hard Disk unit with adapter
04–06 MO91 + ODPU-A MO Disk unit with adapter
10 CP816-A CPU
(memory size 1 GB)
9.4.9 CCSU, Common Channel Signalling Unit
DBG
RST
MBIF 0
MBIF 1
AS7-C
AS7-C
PSC6
J7
CPU
J6
OP
OPR OPR WO
R
RUN
L
F
OL
TE
AP
DRAM
SB
CPCI
SCSI
ON ETx0
ERx0
OFF ETx1
AP AP
ERx1
1 2 3 4 5 6 7
dn05123801x1x0xen
Figure 24 : Common Channel Signalling Unit (CCSU)
Table 20 : Plug-in units of CCSU

02 AS7–C AS7 0
03 AS7–C AS7 1
07 CP816-A CPU
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.
9.4.10 EDU, PDCU, SIPU and CCM
DBG DBG
RST RST
MBIF 0
MBIF 1
MBIF 1
MBIF 0
PSC6
J7 J7
PSC6
CPU
CPU
J6 J6
OPR OPR OPR WO OPR OPR OPR WO

RUN RUN
L L
F F
OL OL
TE TE
AP AP
DRAM DRAM
SB SB
CPCI CPCI
SCSI SCSI
ON ETx0 ON ETx0
ERx0 ERx0
OFF ETx1 OFF ETx1
ERx1 ERx1
1 2 3 4 6 7 8 9
dn0534103x1x0xen
Figure 25 : Dual Computer Unit
Table 21 : Plug-in units of EDU, PDCU, SIPU and CCM

04 CP816-A CPU
09 CP816-A CPU
9.4.11 ET, Exchange Terminals
Figure 26 : ET4C cartridge within the DXTip/DXTA cabinet
There are two kinds of ET plug-in units available for DXTip/DXTTip: ET4E(-C) 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 ET4 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.
The ET plug-in units are installed in the ET4C-B cartridges. The DXTip has one and the DXTTip two ET4C-B
cartridges, 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 16 ET4E/ET4E-C and 8 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 DXTip is 16 ET4E/ET4E-C and
8 ECE2-NT/ECE2-NTC and so the maximum capacity is 64 PCM and 16 ISDN 30B+D connections. The
DXTTip can be equipped with a maximum of 32 ET4E/ET4E-C and 16 ECE2-NT/ECE2-NTC plug-in units and
so the maximum capacity is 128 PCM and 32 ISDN 30B+D connections.
9.5 Basic HW
The following tables list the basic HW of the DXTip and the DXTTip.
Table 22 : The basic HW of the DXTip (Functional units set and equipment)

Object Name
DXTA0E-A Cabinet Alternative Set 1
DXTA0–D Cabinet Location Set 1
DXTA-B Cabinet Type Set 1
CLBU Functional Unit Set 1
-CLAB-S Clock and Alarm Buffer 2
GSWB (pair)
-SHIM4T Shim 4T (dummy front panel) 10
-SW128B Switching Network for 128 PCMs 8
CCSU Functional Unit Set 3
-AS7–C Preprocessing Unit for Multichannel 2
-MRD512A 1GB Registered DDR DIMM 1
-CP816–A Pentium M Central Processing 1
-MBIF-C Message Bus Interface 2
CM Functional Unit Set (pair) 1
-SHI4T Shim 4T (dummy front panel) 4
-MRD1GBA 1GB Registered DDR DIMM 2
-PSC6–A Power Supply for Cartridge 2
-ESB26 Ethernet Switch for B-series 26 2
-MBIF-CR Message Bus Interface 2
CCC Functional Unit Set (pair) 1
Table 22: The basic HW of the DXTip (Functional units set and equipment) (cont'd.)

Object Name
-MRD1GB1 1GB Registered DDR DIMM 2
-SWCOP-A Switch Control Processor 2
OMU Functional Unit Set 1
-MO91 Optical Disk Drive 9.1 GB 1
-MRD512A 512MB Registered DDR DIMM 1
-SERO-B Serial Output Buffered Interface 1
-ODPU-A Optical Drive Plug-in Unit 1
-PSC6–A Power supply for Cartridge 1
-WDW73 Hard Disk Drive 73GB 2
-HWAT-A Hardware Alarm Terminal 1
-HDPU-A Hard Disk Plug-in Unit 1
CLSU Functional Unit Set 1
-TON-SXC Tone Product 2
-CL3TG-S CLock and Tone Generator 3 2
ET4E(-C) E1 Exchange Terminal 4 Interface 4
LPT38–U Serial Printer 1
EXAU-A Lamp panel for alarms 1
VT5530 Visual Display Terminal 1
Table 23 : The basic HW of the DXTTip (Functional units set and equipment)

Object Name
DXTA0E-A Cabinet Alternative Set 1
DXTA0–D Cabinet Location Set 1
Table 23: The basic HW of the DXTTip (Functional units set and equipment) (cont'd.)

Object Name
DXTA-B Cabinet Type Set 1
CLBU Functional Unit Set 2
-CLAB-S Clock and Alarm Buffer 2
GSWB (pair)
-SW128B Switching Network for 128 PCMs 8
CCSU Functional Unit Set 4
-MRD512A 1GB Registered DDR DIMM 1
CM Functional Unit Set (pair) 1
-SHI4T Shim 4T (dummy front panel) 4
-MRD1GBA 1GB Registered DDR DIMM 2
-MBIF-CR Message Bus Interface 2
CCC Functional Unit Set (pair) 1
-MRD1GB1 1GB Registered DDR DIMM 2
OMU Functional Unit Set 1

Object Name
-MRD512A 512MB Registered DDR DIMM 1
-SERO-B Serial Output Buffered Interface 1
-PSC6–A Power supply for Cartridge 1
-HWAT-A Hardware Alarm Terminal 1
CLSU Functional Unit Set 1
-TON-SXC Tone Product 2
-CL3TG-S CLock and Tone Generator 3 2
ACU Functional Unit Set 2
STU Functional Unit Set 2
-MBIF-C/—CR Message Bus Interface 2
EDU Functional Unit Set 2

Object Name
CCM Functional Unit Set 2
ET4E(-C) E1 Exchange Terminal 4 Interface 4
LPT38–U Serial Printer 1
EXAU-A Lamp panel for alarms 1
VT5530 Visual Display Terminal 1
A
PRC
Restriction of Hazardous Substances in the
In this appendix, information is provided with respect to the restriction of hazardous substances applied in
the People’s Republic of China.
Figure 27 : Material declaration for the PRC markets.
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

ACU Authentication Centre Unit
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
CCC Call Control Computer
CCM Common Channel Signalling Management Unit
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
CM Central Memory
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
DXTip Digital Exchange for TETRA
DXTTip Digital Exchange for TETRA, transit type
ECE2 Exchange Terminal
EDU Enhanced Data Unit
EMC Electromagnetic Compatibility
EMT External Message Transfer
EPCO Enhanced Protocol Converter
EQUIPM Equipment Database
ESB26 Ethernet switch
ET Exchange Terminal
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
GSW1KB 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
MB Message Bus
MBIF Message Bus Interface Unit
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
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
STU Statistical Unit
SW1C-C Switching Cartridge 1
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
VLR Visitor Location Register
WAN Wide Area Network
INDEX
A methods of ................................................... 53
DWS ................................................................ 34
alarm data DWSx .............................................................. 33
storage of ..................................................... 58 DXTB
alarm printer .................................................... 58 cabinet location set ..................................... 50
alarms cabinet type set............................................ 50
classification................................................. 58 CCSU........................................................... 48
authentication .................................................. 23 functional unit ACU ...................................... 48
functional unit CCM...................................... 49
C functional unit EDU ...................................... 49
functional unit STU....................................... 49
call services
SIPU............................................................. 48
main tasks.................................................... 17
DXTip
capacity ........................................................... 25
number of CCSU units ................................. 35
CDD Server ..................................................... 15
DXTip/DXTA
charging........................................................... 20
alternative set, E1 balanced......................... 47
clock system .................................................... 63
alternative set, E1 unbalanced..................... 48
Common Channel Signalling Unit.................... 35
cabinet location set ..................................... 47
computer units
cabinet type set............................................ 47
means of communication between .............. 31
ESB26.......................................................... 46
configuration management and
functional unit CCC ...................................... 45
maintenance
functional unit CCSU.................................... 46
functions of................................................... 57
functional unit CLAB .................................... 46
configurations
functional unit CLSU .................................... 46
changing of .................................................. 57
functional unit CM ........................................ 45
connections
functional unit ET; ET4E(-C) and
between DXT exchanges............................. 35
ECE”-NT(C)................................................ 46
continuous numbering model .......................... 19
functional unit GSW1KB .............................. 46
cyclic redundancy check
functional unit OMU ..................................... 45
for network supervision ................................ 60
functional unit PDCU.................................... 46
functional unit SIPU ..................................... 45
D DXTTip
number of CCSU units ................................. 35
databases
list of............................................................. 40
maintaining copies of ................................... 39 E
means of implementation............................. 39 EADS TETRA Dispatcher Workstation
use of semipermanent files .......................... 39 (DWS) ............................................................ 15
diagnostics electromagnetic environment .......................... 67
task of .......................................................... 59 Enhanced Protocol Converter (EPCO)............ 34
duplication environmental conditions................................. 67
External Message Transfer (EMT) .................. 37 network
frequency ..................................................... 62
F synchronising of clocks ................................ 62
network architecture ........................................ 15
fault detection
network supervision
through alarms ............................................. 58
tasks and actions ......................................... 60
through supervision...................................... 58
fault location
principles of.................................................. 59 O
faults Open Systems Interconnection (OSI)
statistics ....................................................... 61 use of ........................................................... 37
frame alignment output reports .................................................. 57
monitoring of for network supervision .......... 60
FTAM Protocol................................................. 38 P
FTP (File Transfer Protocol)
plug-in units ............................................... 43, 67
use of ........................................................... 37
processes
functional units................................................. 67
means of communication ............................. 39
protocols
G FTAM ........................................................... 35
group calls IP.................................................................. 35
speech item allocation of ............................. 18 OSI............................................................... 35
GSW1KB ......................................................... 17 Q3 ................................................................ 35
I Q
integrated data distribution function................. 36 Q3 interface
integrated data distribution functionality .......... 15 use of ........................................................... 37
ISDN-connected EADS DWSi ......................... 33
L R
Radio Data Dispatcher Workstation
lamp panel
(DWSr)........................................................... 33
for alarm indication....................................... 58
real time clock.................................................. 63
LAPD protocol
recovery
use of ........................................................... 36
distribution of recovery software .................. 59
logical addresses
task of .......................................................... 59
of computer units ......................................... 16
redundancy
schemes....................................................... 53
M
Message Bus (MB) .......................................... 16 S
monitoring the bit error rate SECMO ........................................................... 23
for network supervision ................................ 60 signalling
MTP (Message Transfer Part) types in use.................................................. 18
use of ........................................................... 37 single-DXT network ......................................... 15
slip calculation
N for network supervision ................................ 60
NetAct........................................................ 35, 61 software
advantages of modularity............................. 53
programming language ................................ 41
T
software blocks TCP/IP protocol
hierarchy of .................................................. 39 use of ........................................................... 36
speech item allocation ..................................... 18 technical data .................................................. 65
subscriber management .................................. 57 TELNET........................................................... 38
supervision TETRA Base Station (TBS) ............................. 15
task of .......................................................... 58 TETRA Connectivity Server (TCS) .................. 15

Eads Tetra System Release 6.0: Dxtip and Dxttip Product Description

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eads Tetra System Release 6.0: Dxtip and Dxttip Product Description

Uploaded by

Copyright:

Available Formats

DXTip and DXTTip Product Description

EADS TETRA System Release 6.0

Copyright © 2014–2015 Airbus DS SAS, all rights reserved.

DN0531796-6-2en EADS TETRA System Release 6.0

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

2 Introduction to the DXTip and the DXTTip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

EADS TETRA System Release 6.0 DN0531796-6-2en

DN0531796-6-2en EADS TETRA System Release 6.0

EADS TETRA System Release 6.0 DN0531796-6-2en

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

DN0531796-6-2en EADS TETRA System Release 6.0

EADS TETRA System Release 6.0 DN0531796-6-2en

DN0531796-6-2en EADS TETRA System Release 6.0

VERSION DATE COMMENTS CHAPTER

2. Basic IP Packet Data Service, dn05221832

3. Enhanced IP Packet Data Service, dn05222516

4. TCS Product Description, dn0116031

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.

12. Installing the DXTip and DXTTip, dn064171

EADS TETRA System Release 6.0 DN0531796-6-2en

DN0531796-6-2en EADS TETRA System Release 6.0

How to use this document

EADS TETRA System Release 6.0 DN0531796-6-2en

DN0531796-6-2en EADS TETRA System Release 6.0

Figure 1 : DXTip with doors closed

EADS TETRA System Release 6.0 DN0531796-6-2en

2.1.1 Different mechanics

Table 1 : The different mechanics of the DXTs

DXT256 with M92 mechanics

2.2 DXTip and DXTTip in the EADS TETRA System

DN0531796-6-2en EADS TETRA System Release 6.0

• easy and low-cost maintenance

• new features easy to implement by updating the software

• low power consumption.

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

Figure 3 : A single-DXT network

Figure 4 illustrates a more complex DXT network architecture.

EADS TETRA System Release 6.0 DN0531796-6-2en

2.3 Basic architecture

2.3.1 Independent computer units

2.3.2 Distributed architecture

DN0531796-6-2en EADS TETRA System Release 6.0

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

2.4.1 Digital switching

2.4.2 Call services

EADS TETRA System Release 6.0 DN0531796-6-2en

2.4.3 Speech item allocation

2.4.4 Database services

2.4.5 Signalling services

DN0531796-6-2en EADS TETRA System Release 6.0

2.4.7 Resource management

EADS TETRA System Release 6.0 DN0531796-6-2en

2.4.9 Charging services

Statistics are handled by the following hardware units:

• Statistical Unit (STU): Integrated part of Statistics.

• Operation and Maintenance Unit (OMU): Statistics (generation of reports).

• Common Channel Signalling Unit (CCSU): MTP statistics (distributed processing).

Statistics can be divided into the following subcategories: