1

UHF TRUNKING RADIO COMMUNICATIONS SYSTEM

(TETRA-STANDARD-BASED)

SAA TECHNICAL

ANALOGUE TO DIGITAL MIGRATION

2

TABLE OF CONTENTS

1 INTRODUCTION 5

3 STANDARDS 8

4 SYSTEM SERVICES 9

Voice Services 9

4.1.1 Private Call / Individual Call 9

4.1.2 Group Call 9

4.1.3 Late Entry Into Existing Group 9

4.1.4 TETRA subscriber joins active group call 9

4.1.5 Dynamic Group Number Assignment (DGNA) 10

4.1.6 Broadcast Call 10

4.1.7 Dynamic Group Area (Area-Tied Group Call) 10

4.2 Priority Functions 10

4.2.1 General 10

4.2.2 Emergency Call 10

4.2.3 Pre-Emptive Priorities 10

4.2.4 Priority Group Scanning 11

4.2.5 Default Call Priority 11

A default call priority per subscriber shall be provided. 11

4.2.6 Priority Open Channel 11

4.3 Presence Indication for group calls 11

4.4 Call Forwarding / Call Diversion 11

4.4.1 Unconditional 11

4.4.2 On busy subscriber 11

4.4.3 On subscriber not reachable or no reply 11

4.5 Call Line Indication 11

4.5.1 Call Line Indication Presentation (CLIP) 11

4.5.2 Call Line Indication Restriction (CLIR) 11

4.5.3 Forced CLIP and CLIR 12

4.5.4 CLIR Override 12

4.6 Talking Party Identification (TPI) 12

4.7 Call Barring of Calls from/to PBX/PSTN 12

4.7.1 Barring of Outgoing Calls 12

4.7.2 Barring of Incoming Calls 12

4.8 Data Services 12

3

4.8.1 STATUS and SDS Messages 12

4.8.2 Packet Data Service 13

4.8.4 Time synchronization 13

4.9 Application Interface Services 13

4.10 Cell Reselection 13

4.11 Interference Detection 14

NUMBERING & DIALING 15

5 SECURITY FUNCTIONS 15

5.1 Air Interface Encryption 15

5.2 TETRA Authentication 15

5.3 Enable and disable of radio terminals 16

5.4 System Security Functions 16

5.5 Authentication of network operator personnel 16

NETWORK NODES AND GATEWAYS 17

5.6 System Controller Nodes 17

5.7 System Controller Node Gateways and Interfaces 18

5.8 Base Stations 19

5.9 Base Station Gateways and Interfaces 21

5.10 Availability of Network Nodes (optional) 22

6 NETWORK CAPACITY AND OPTIMIZATION 23

7 NETWORK ADMINISTRATION 24

7.1 General Requirements 24

7.2 Subscriber Administration 24

7.3 Component Monitoring and Fault Diagnostics 25

7.4 Software and Configuration Provisioning 25

7.5 Access Control 25

7.6 Remote Diagnostic 26

7.7 Key Generation & Management 26

7.8 Security 26

8 IN-BUILDING COVERAGE 26

9 DISPATCHER SYSTEM 26

GENERAL & FEATURES 26

4

9.1 User Interface Error! Bookmark not defined.

9.2 User Selection Window 27

Selected group 27

Group membership 27

Group properties 28

Status of attachment 28

Group members 28

List of attached groups 28

List of disabled terminals 28

Monitoring results 28

9.2.1 Call Setup Window 28

9.2.2 Event Window 28

Date and time 28

Subscriber identification 28

Type of event 28

9.2.3. Graphical Information System (GIS) and 28

Automatic Vehicle Location System (AVLS) 28

Display mobile stations (subscribers) in their last locations 29

Request location update by the dispatcher 29

Store the position of mobile users (subscribers) 29

Track and store the movement of mobile users (subscribers), e.g. in a form of closed curve (continuous line) representing the route of the user 29

Measure polygon distance, e.g. for evaluating tracks 29

Find subscriber on map 29

Jump to subscriber on map, i.e. incoming call or status message initiator 29

Follow subscriber on map 29

Zoom and pan the map 29

9.2.4 Security 29

9.2.5 Alarming 29

10 VOICE RECORDER SYSTEM 30

General & Features 30

All group calls 30

All emergency calls 30

All telephone interconnected calls 30

All status messages and short data messages 30

5

All system wide calls 30

11 TRANSMISSION NETWORK 31

12 SYNCHRONIZATION ERROR! BOOKMARK NOT DEFINED.

13 SUBSCRIBER TERMINALS 33

13.1 General Requirements 33

13.2 Handheld radio terminals 33

13.3 Vehicular radio terminal (TETRA) 34

13.4 Base Set Radio Terminals 35

14 TRAINING and SUPPLIER DEVELOPMENT 36

15 SERVICE LEVEL AGREEMENT and REFERENCES 36

16 FINANCING OPTIONS 36

6

1 INTRODUCTION The mobile communication system based on the high-performance TETRA technology is intended to be used for mission critical voice and data communication at OR Tambo International Precinct for SAA Group. The ensuing concepts must be explained in detail taking into account the described minimum requirements, which shall be fulfilled by the bidder. Each requirement shall be answered with a written reference and Documentation. The proposed TETRA system is to replace the existing two site, IP linked MPT 1327 radio trunking system presently in use.

2 General Requirements For the TETRA Radio System

The UHF radio system (TETRA) shall be in compliance with the essential requirements and other relevant provisions of relevant European Council Directives. This comprises CE marking for the goods. Especially for the radio terminals the Directive 1995/5/EC or latest Directive shall apply. The TETRA system shall have full conformity to the specifications of the Air Interface according to EN 300 392-2 (TETRA V+D). The TETRA system shall have full conformity to the test specifications of the air interface according to EN 300 394-1. The mobile radio system shall comprise a full IP-based architecture, in detail including IP-based call processing and switching functions (soft-switching) as well as IP-connected base stations, applications (e.g. dispatchers) and network administration facilities. The mobile radio system shall not comprise any circuit switching components. Recommended list of spare parts for the proposed TETRA system to be supplied. The bidder shall provide a project plan to show timelines of execution from date of order. The mobile radio system shall not use any circuit switched transmission networks for voice streams, data transmission, signaling and administration data. The mobile radio communications system must feature flexible and resilient network architecture with distributed TETRA switching functionality and call processing without comprise to any other back-up TETRA switching units. The TETRA system shall transport voice and data services. A roaming function shall be provided to enable radio terminals to automatically roam throughout the system across base stations without the need for mobile user’s intervention. An open radio infrastructure application interface shall be provided to access the TETRA system’s services and features and thus provide enhanced functionality (value add) by the connected applications, e.g. dispatcher, voice recorder, telemetry systems or smart metering.

7

The TETRA network shall easily be expandable in terms of coverage (increasing the number of base stations), capacity (increasing the number of carrier frequencies per base station) and gateway interfaces at a later stage to be determined by SAAT. The proposed TETRA system should support TETRA Enhanced Data Services (TEDS) and Over-The-Air-Programming (OATP). Expansions of the TETRA network shall be possible without removal of present base stations or network management facilities. A long lasting, cost-efficient maintenance of the network and of its components as well as the supply with spare parts must be ensured with in-house repair capability at SAAT. The OEM shall be the manufacturer of the TETRA communications infrastructure provided in the offer. The OEM shall be a member of the TETRA Critical Communications Association (TCCA). The OEM shall have at least 10 years of proven experience developing and supplying TETRA infrastructure products to customers worldwide. SAAT reserves the right to have its representatives visit and evaluate the supplied referenced customers TETRA systems. SAAT reserves the right to have its representatives present when the TETRA system has final testing and commissioning at the factory. The OEM shall have proven experience supplying TETRA systems to the Airline/MRO (Maintenance Repair Organisation) Industry. Similar or bigger sized Network projects as reference within South Africa or Internationally would be advantageous. The bidder may offer proposals for the entirety of the tender or Part One (TETRA System Infrastructure) only or Part Two (TETRA Radio Terminals) or any of the three types of radio terminals requested in Part Two.

8

3 STANDARDS

The TETRA system shall be in compliance with the essential requirements of the Independent Communications Authority of South Africa (ICASA), as well as below. The Radio Communication Network shall use the latest generation of digital trunked mobile radio system complying with TETRA (Terrestrial Trunked Radio) V+D (Voice +Data) Standard developed by ETSI (European Telecommunication Standard Institute) for Private Mobile Radio (PMR). This especially comprises CE marking for the goods. Especially for the radio equipment the Directive 1995/5/EC or latest Directive shall apply. Documentation in this regard to be provided. Proof of latest Compliance to be supplied. The conformity of all TETRA base stations shall be according to…

ETSI EN 300 394-1 Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 1: Radio

ETSI EN 300 392-2 Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI).

The electromagnetic compatibility of all TETRA base stations shall be according to…

ETSI EN 301 489-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Electro-Magnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements

ETSI EN 301 489-18 Electromagnetic compatibility and Radio spectrum Matters (ERM); Electro-Magnetic Compatibility (EMC) standard for radio equipment and services; Part 18: Specific conditions for Terrestrial Trunked Radio (TETRA) equipment

EN 55022 Information technology equipment - Radio disturbance characteristics – Limits and methods of measurement.

The safety classification of all TETRA base stations shall be according to EN 60950-1 Information technology equipment – Safety – Part 1: General requirements.

9

4 SYSTEM SERVICES (FUNTIONALITY)

Voice Services

To ensure mission-critical yet user-friendly operation, the voice call set-up time shall be less than 500 milliseconds, not to exceed 700 milliseconds at peak-times, within the operational area of base stations controlled by one system controller node.

4.1.1 Private Call / Individual Call

It is required that each mobile terminal shall be able to make individual calls of one of the following modes.

The half duplex individual call between TETRA terminals shall be supported.

The full duplex individual call between TETRA terminals shall be supported.

The full duplex individual call to PABX/PSTN shall be supported.

4.1.2 Group Call

Users shall have the possibility of joining group communication by selecting a talk group via a group selector switch on the mobile terminal. Users shall talk to the group by simply pressing the push-to-talk button (PTT). The group calling mode shall be provided as half-duplex group call between TETRA terminals. Group calls from PABX/PSTN to TETRA terminals shall be supported. The group call to a closed group shall only be setup by terminals, which are members of the group. The identity of the talking party (mobile terminal ID or alias) is to be displayed to all the members of the group. To save system resources it shall be possible to set up group calls only in radio cells where members of the group have attached this group.

4.1.3 Late Entry Into Existing Group

The TETRA system shall send Late Entry indications for ongoing group calls in the radio cells involved in the call to provide the possibility that the radio terminal subscriber can join the ongoing group call. The network administration system shall provide configuration of the function. The late entry indication shall be sent for all ongoing group calls. The late entry indication shall be sent on the control channels and on the traffic channels where group members are assumed.

4.1.4 TETRA subscriber joins active group call

A TETRA subscriber shall automatically join an ongoing group calls if he calls a group, which already has an active call in the cell in which the subscriber is located.

10

4.1.5 Dynamic Group Number Assignment (DGNA)

Line-connected dispatchers shall be able to set up group calls with varying member structure. These dynamic groups can be modified within runtime to cater for changing group members and set up new group addresses in the radio terminal via the TETRA air interface.

4.1.6 Broadcast Call

The broadcast call initiated by the line dispatcher shall be call of an authorized subscriber to several radio subscribers with automatic call acceptance (direct call setup). The initiator (line-dispatcher) has permanent authorization to talk (no talk back).

4.1.7 Dynamic Group Area (Area-Tied Group Call)

The system shall allow for dynamically assigning areas to specific groups. Resources (voice channels) may thus only be occupied only in areas where these groups operate. The area-tied group call thus shall be restricted to a certain location area (number of radio cells).

4.2 Priority Functions

4.2.1 General

The system must feature a priority management that assigns the air interface resources (voice channels) depending on the priority of a call. The priorities of the various calls and mobile terminals must be configurable. At least three priority levels must be provided for:

Emergency call

Privileged call (Pre-emptive priority)

Standard call Emergency calls must have the highest priority and are able to suppress ongoing communication with a lower priority in the case of a lack of resources.

4.2.2 Emergency Call

The Emergency Call shall be a pre-emptive priority call with highest priority level (15) overruling ongoing call of busy destination subscribers and releasing occupied resources. The setup time of an emergency call must not exceed 500 ms.

4.2.3 Pre-Emptive Priorities

The Priority Individual and Priority Group Call shall be calls which allocate resources depending on their level. The resource allocation by the TETRA system shall be handled in accordance with the call priority. For calls with the highest priorities (level 12-15) in the system calls of less priority of busy destination subscribers shall be cancelled and resources shall be released. The calls shall be only interrupted by calls of higher priority (e.g. priority 13 interrupts priority 12).

11

4.2.4 Priority Group Scanning

The Late Entry indication shall be sent also on the traffic channels where group members are assumed in addition to the control channels. It enables priority group scanning for the radio terminals.

4.2.5 Default Call Priority

A default call priority per subscriber shall be provided.

4.2.6 Priority Open Channel

The Priority Open Channel shall be a group call with extended call time. The extended call time shall be at configurable with up to at least 3 hours. The Priority Open Channel shall only be opened by authorized users (e.g. in emergency situation). All other voice calls in that base station site shall be interrupted to allow users to join the Priority Open Channel.

4.3 Presence Indication for group calls

Group calls shall be only setup in cells of the group call area where members of the group are available.

4.4 Call Forwarding / Call Diversion

Call diversion for individual calls to another mobile terminal, telephone or dispatcher workstation must be possible, initiated by a dispatcher workstation.

4.4.1 Unconditional

Unconditional call diversion shall be configured in the network management for a subscriber.

4.4.2 On busy subscriber

Call diversion on busy subscriber shall be configured in the network management for a subscriber.

4.4.3 On subscriber not reachable or no reply

Call diversion on “not available” subscriber shall be configured in the network management for a subscriber.

4.5 Call Line Indication

4.5.1 Call Line Indication Presentation (CLIP)

The called subscriber shall be provided with the identity of the calling subscriber.

4.5.2 Call Line Indication Restriction (CLIR)

There shall be the possibility to restrict the CLI presentation by entries in the subscriber management. CLIR shall be applied for all calls, for calls to members of other fleets and for calls to ISDN.

12

4.5.3 Forced CLIP and CLIR

There shall be the possibility for calls to special identities to force CLIP or CLIR of the calling subscriber by the subscriber management entries for this special identity.

4.5.4 CLIR Override

There shall be the possibility to configure a forced provision of the calling subscriber's identity to the called subscriber, overriding calling subscriber's active CLIR.

4.6 Talking Party Identification (TPI)

The identification of the talking party shall b provided to the subscribers of a call.

4.7 Call Barring of Calls from/to PBX/PSTN

The permission to receive/initiate calls from/to PBX/PSTN shall be configurable for each individual subscriber, group and application subscriber.

4.7.1 Barring of Outgoing Calls

Call initiating addresses shall be restricted by entries in the subscriber management. The permission to initiate certain calls shall be set for individual calls, group calls, PBX calls, PSTN calls, duplex calls, status calls, SDS calls, calls to members of other fleets within a possible VPN.

4.7.2 Barring of Incoming Calls

Call receiving addresses shall be restricted by entries in the subscriber management. The permission to receive certain calls shall be set for circuit mode calls, PSTN calls, status calls, SDS calls, calls from members of other fleets within a possible VPN.

4.8 Data Services

4.8.1 STATUS and SDS Messages

It shall be possible to select predefined STATUS messages (values) during a call and transmit them to a destination (individual, dispatcher or group) in the TETRA network without impairing the communication. The following text message (Short Data Service, SDS) types 1 to 4 and TL shall be supported by the radio infrastructure. The system shall support SDS type 4 with up to 2046 bits. The sending of SDS and STATUS messages both on the control channel and on traffic channels in the uplink shall be supported. The system shall support transmission of SDS and STATUS messages to radio terminals in ongoing group and individual voice calls for both individual and group addressed messages.

13

All ongoing voice calls shall not be interrupted during the receiving of STATUS and SDS message in parallel to voice transmission. .

The system shall support optional configuration of TETRA radio base stations with up to 3 Secondary Control Channels (SCCH) in addition to the Main Control Channel (MCCH).

4.8.2 Packet Data Service The TETRA system shall support single slot Packet Data transmission between radio terminals or a radio terminal and a customer IP network. The TETRA system shall multi-slot Packet Data transmission between radio terminals or a radio terminal and a customer IP network. The system shall provide a Packet Data interface using Dynamic Host Configuration Protocol (DHCP) according to RFC 2131 and RFC 2132 so that IP addresses for mobile subscribers & radio connected applications can be dynamically assigned by the connected provider network. The connection shall be made via a system IP gateway provided in the System Controller Node or Base Station.

4.8.4 Time synchronization

Alignment via Satellite times

4.9 Application Interface Services

The offered TETRA system shall provide an interface for application integration, especially to be used for 3rd party application integration eg. RFID Tagging This interface shall enable an extensive access to communication services and other functions of the TETRA system by the application (e.g. command & control system, automatic vehicle location system, dispatcher etc.). The application interface shall support all communication services like voice and data (SDS) Short data Service via a single interface based on Voice-over-IP methods. The application interface shall provide call control functions and support call setup and management, Dynamic Group Number Assignment (DGNA), voice call monitoring, ambience listening and authorization services. The interface shall be an open interface where protocols are provided to user.

4.10 Cell Reselection

A radio terminal shall scan the new radio cell in the background during a call. It shall inform the TETRA radio infrastructure that it intends to select another radio cell.

14

Then, it shall switch over to the control channel of the new cell and then requests the call to be re-established. If a Mobile Station (MS) involved in a group call roams into a cell, where the group call does not exist, the group call will be established in this cell.

4.11 Interference Detection

The system shall provide continuous interference (jamming) measurement / detection during TETRA operation. Long time recording of interference detection measurements and visualization shall be featured in the network management. The base station shall trigger an alarm if it recognizes an unspecific interferer (low Received Signal Strength Indication (RSSI), bad Signal-to-Noise-Ratio (SNR)) on one or more of its receiving frequencies. When affected by interference, the main carrier shall be taken out of service automatically and a replacing carrier frequency (one of the traffic carrier frequencies) shall be used if available.

15

NUMBERING & DIALING

The numbering scheme concept for the new TETRA network shall consider relevant ETSI and ITU-T regulations. The bidder shall explain the numbering concept. Dialing Modes specific to radio terminals and their benefits must be described by the bidder.

5 SECURITY FUNCTIONS

5.1 Air Interface Encryption

The Air Interface Encryption feature shall secure the radio link set up between the mobile stations / radio subscribers and the TETRA base stations within the SAA Group Network such that no external monitoring by any party other than SAAT is possible. The system must activate this feature for all ongoing calls and data transmission. A dedicated and secured key management application shall be used to create the parameters required for Air Interface Encryption on the basis of the authentication key (K), the TETRA equipment ID (TEI), and the TETRA encryption algorithms (TEA). All parameters used for TETRA Air Interface Encryption shall be automatically exported by the network administration software and distributed to all system components. No manual download or distribution handling and no external media shall be used. The system shall provide TETRA Air Interface Encryption Class using Static Cipher Keys (SCK) according to ETSI standard. Class possibilities to be presented by Bidder.

5.2 TETRA Authentication

Procedures for mutual authentication implemented in compliance with the TETRA standard shall be provided. Mutual authentication shall be used to prove the authenticity of a radio terminal or the radio infrastructure, allowing the radio terminal to verify itself towards the radio infrastructure and vice versa. Both sides shall verify a “secret” authentication key “K”. A party shall be deemed authenticated if “K” is identical. The verification shall be not achieved directly by comparing the authentication keys but by using various encryption algorithms and comparing the resulting data. All parameters used for TETRA authentication shall be automatically exported by the network administration software and distributed to all system components. No manual download or distribution handling and no external media shall be used.

16

5.3 Enable and disable of radio terminals

The system shall support temporary and permanent disabling of terminals in accordance with TIP specification TTR 001-13 v2.0.0 and ETSI EN 300392-2. The system shall support enabling of temporary disabled terminals in accordance with TIP specification TTR 001-13 v2.0.0 and ETSI EN 300392-2. To support tracing of stolen or lost radio terminals the system shall provide Ambience Listening to be used by dispatching applications on temporarily disabled terminals. To support tracing of stolen or lost radio terminals the system shall provide possibility to track temporary disabled terminals (transmission of GPS positioning data) by dispatching applications of the same VPN as the target subscriber.

5.4 System Security Functions

A VLAN (Virtual Local Area Network) secured network administration client interfaces shall be used. This will primarily deter “hacking”. The Packet Data access point shall comprise a fire wall function. A VLAN (VPN tunnel) between the Packet Data interface and external application shall be used. The PAP or CHAP authentication protocol between the terminals Packet. The bidder shall explain the procedures used. The VLAN (VPN tunnel) between application server and application shall be used. The application interface shall support authentication at the interface validating the permission of all connected applications to use system services like Monitoring, group activation or Call Setup.

5.5 Authentication of network operator personnel

The access to the network administration facilities and functions shall be at any time limited to authorized users only. Authorization shall be verified by the network administration software and carried out by using login/password combination together with a personalized physical token. An individual set of token and login/password shall represent a user role and restrict the access to specific network administration functions.

17

PART 1

TETRA SYSTEM INFRASTRUCTURE SPECIFICATIONS

NETWORK NODE AND GATEWAYS

6.0 System Controller Node

The offered System Controller Node shall be of complete modular design and must allow customization to match capacity and performance required for this project and to provide all necessary functions to operate the system-wide trunking radio communications. All System Controller Node’s software and operational SW configuration shall be updateable remotely. The System Controller Node shall be capable to contain customer-specific components in the same housing/cabinet as the server components used for IP soft-switching and gateways. The System Controller Node shall be scalable to allow later network extension in capacity and coverage by adding server platforms and software licenses.

The System Controller Node shall be powered by 230 V AC. The operating temperature of the System Controller Node shall at least range from +5°C to +40°C. The storage temperature of the SCN shall at least range from -10 °C to +70 °C. It shall be possible to deploy the System Controller Node on a floor space not larger than 1 meter square. The offered System Controller Node shall be capable to host full IP-based TETRA switching and call processing (call processing of the TETRA upper protocol layers). The switching functionality shall include - but not be limited to - Call Control for TETRA V+D and Mobility Management. The System Controller Node shall use full IP-based Soft-Switching = Call Processing and Voice Routing functions. The System Controller Node shall not comprise any circuit switching components. The System Controller Node shall not require any circuit switched transmission networks for voice streams, data transmission, and signaling and administration data. The System Controller Node shall use commercially available server platforms to host all system functions. The platforms shall not use any proprietary hardware modules.

18

The server platforms of the System Controller Node shall be NEBS-3 / ETSI compliant. The server platforms of the System Controller Node shall use commercially available processors and chipset within a processor performance of at least 2,33GHz and four (4) processors cores e.g. Intel Quad-Core. The server platforms of the System Controller Node shall use hot-swap Hard-drives with RAID1 or RAID5 technology. The server platforms of the System Controller Node shall be NEBS-3 / ETSI compliant. An Uninterruptible Power Supply (UPS) shall be offered for each radio base station to back up power for at least 4 hours.

6.1 System Controller Node Gateways and Interfaces

The offered System Controller Node shall be capable to provide optional line gateway connectivity and voice transcoding to telephony networks without any additional components other than the server platform used for IP soft-switching functionality. The offered System Controller Node shall provide at least one Voice-over-IP (VoIP) interface without any additional components other than the server platform used for IP soft-switching functionality. It shall utilize signalization according to Session Initiation Protocol (SIP; RFC 3261), Session Description Protocol (SDP; RFC 4566), Real Time Protocol (RTP) voice transmission in accordance with RFC 3550 as well as encoding with ITU Standard G.711 Laws for voice data transmission. The offered System Controller Node shall be capable to provide optional line gateway connectivity to dispatcher applications without any additional components other than the server platform used for IP soft-switching functionality. The offered System Controller Node shall be capable to provide optional line gateway connectivity to customer IP networks and databases (e.g. Intranet) without any additional components other than the server platform used for IP soft-switching functionality. This interface shall use LAN according Ethernet 100BaseT specification and provide interface for IP Packet Data transmission. A maintenance interface for remote service shall be integrated part of the System Controller Node. All mentioned interfaces (VoIP/SIP, telephony, IP Packet Data, applications and maintenance) shall be provided by a single one server platform type. No different server platforms shall be used in order to provide different functionality or capacity. A flexible interface to conventional analogue radio networks in terms of functionality and protocols shall be provided. The Analogue / Digital TETRA gateway shall use the application interface of the TETRA system in order to provide call functions between the TETRA radio system and current MPT 1327 radio systems in use, in order to allow a migration

19

from the analogue MPT 1327 radio system, Cellular devices, Dispatcher platforms e.g. Zetron, PABX/PSTN platforms & smart devices to the TETRA radio system. The configuration shall be carried out via an Internet Protocol interface as Analogue / TETRA gateway programming interface.

6.2 Base Stations

Base Station System Layout at SAAT The TETRA system will comprise of 3 sites being: • Avionics site with 5 modulated carriers (20 radio channels), • Bravo site with 5 modulated carriers (20 radio channels) and • Delta site with 2 modulated carriers (8 radio channels) allowing for future

expansion. The bidder shall certify that the base stations have been developed directly by the bidder and are manufactured in the bidder’s factory. The bidder may be requested to facilitate a factory visit to prove this. The TETRA base stations shall be expandable from 1 TETRA carrier up to 4 TETRA carriers (maximum of 16 radio channels) within one 19” system cabinet without replacing or removing present cabinets. The TETRA base stations shall support extension up to 8 TETRA modulated carriers (32 radio channels) in a single radio cell without replacing or removing present cabinets. The base station software and operational SW configuration shall be updateable remotely. The frequency band is 410-430MHz. The power consumption of the offered TETRA Base Stations shall not exceed 550 Watts for a 2 carrier base station whilst still maintaining the maximum output power and the stated environmental conditions/specifications. The TETRA base stations shall be powered by 230 V AC. A base station variant without any combiner shall be available in the standard portfolio in addition to any hybrid and cavity combiner variants. It shall be possible to deploy the TETRA Base Stations on a floor space not larger than 1 square meters. The nominal power of the TETRA transceiver, referring to the ETSI EN 300 392-2 V3.2.1 (2007-09) standard, shall at least be power class 2. The TETRA Base Stations shall have a static sensitivity (4% BER; TCH 7.2) of at least -119dBm as a guaranteed value (not typical sensitivity) without any diversity gain included.

20

The TETRA Base Stations shall have a dynamic sensitivity (4% BER; TCH 7.2; TU 50) of at least -113dBm as a guaranteed value (not typical sensitivity) without any diversity gain included. The base station shall have a dynamic sensitivity according to EN 300 392-2 class A conditions of at least -108dBm. The TETRA Base Stations shall have a dynamic sensitivity according to EN 300 392-2 class B conditions of at least -110dBm. The TETRA base station shall have a RF output of up to 25 Watts available after the combiner. The TETRA base station should have a 3 antenna diversity system. Bidder to supply documentation on proposed antenna system.

An Uninterruptible Power Supply shall be offered for each radio base station to back up power for at least 4 hours.

The TETRA Base Station shall provide detection of interfering carriers as well fault reporting (logging) of those to the network administration system. The base station shall automatically enter autonomous local site trunking operation in case of connection loss to the network. The base station shall provide this local site trunking operation as a standard feature without any additions in hardware or software or any optional modules. Especially no additional server or computer units shall be used to provide this functionality at the base station site. All base stations shall continuously send air interface signaling to the mobile stations (terminals), whether they provide net-wide trunking services or local trunking services to the users. All of the following features must be available within the radio coverage area of the TETRA Base Stations in local site trunking mode for mobile communication:

Group calls with all group definitions, parameters and permission as defined and set-up for net-wide trunking mode

Individual calls (half-duplex/Simplex and full Duplex calls) with all individual subscriber definitions, parameters and permission as defined and set-up for net-wide trunking mode

Call queuing, dependent on the call priority level

Pre emptive priority calls

Configurable call time limitation

Individual-addressed and group-addressed Short Data messaging (SDS) and STATUS message transmission

Communication services secured by Air Interface Encryption of Class 2 (if used in net-wide trunking mode) with the same encryption keys as used in net-wide trunking mode

Communication services secured by TETRA Authentication of mobile stations (terminals) (if used in net-wide trunking mode) with the same authentication keys as used in net-wide trunking mode

Rejection of a call of an unknown subscriber

Providing call services to subscribers not being registered in this radio cell

21

Call rejection with cause “busy”, if subscriber is already in a call or there is a pre-emptive priority call

Inactivity timer according to TETRA protocol stack If the TETRA Base Station’s main carrier (carrying the Main Control Channel, MCCH) fails, one of the traffic channel (TCH) providing carriers automatically takes over and provides the control channel signaling.

6.3 Base Station Gateways and Interfaces

The offered base stations shall be capable to host full IP-based TETRA switching and call processing without any additional components other than transceiver (Rx/Tx), BS controller (site controller) and filter components and without losing performance on the Air Interface. Base stations with integrated IP-based switching shall allow operating the network without any System Controller Node or switch. The base-station-integrated switching functionality shall include - but not be limited to - Call Control for TETRA V+D, the Location Register for all subscribers in the network, the validation of call requests, routing of calls and Mobility Management. The offered base stations shall be capable to provide optional line gateway connectivity and voice transcoding to telephony networks. This interface shall be integrated part of the base station(s) without any additional components other than transceiver (Rx/Tx), BS controller (site controller) and filter components and without losing performance on the Air Interface. The system shall provide at least one Voice-over-IP (VoIP) telephony interface with signalization / Session Initiation Protocol (SIP) according RFC 3261, Session Description Protocol (SDP) according to RFC 4566, Real Time Protocol (RTP) voice transmission in accordance with RFC 3550 as well as encoding with ITU Standard G.711 µ-law or G.711 a-law for voice data transmission. This interface shall be integrated part of one base station. The offered base stations shall be capable to provide at least one ISDN S0 interface (with 2xB, 1xD-channel) to connect to PBX/PSTN. The offered base stations shall be capable to provide optional line gateway connectivity to dispatcher applications. This interface shall be integrated part of the base station(s) without any additional components other than transceiver (Rx/Tx), BS controller (site controller) and filter components and without losing performance on the Air Interface. The offered base stations shall be capable to provide optional line gateway connectivity to customer IP networks and databases (e.g. Intranet) according Ethernet 100BaseT). This interface shall be integrated part of the base station(s) without any additional components other than transceiver (Rx/Tx), BS controller (site controller) and filter components and without losing performance on the Air Interface. The offered base stations shall be capable to provide all the mentioned gateway options at the same time on one base station site.

A maintenance interface for remote service shall be integrated part of all base stations.

22

Each base station shall feature an alarm panel providing at least 6 digital alarm inputs (active/open) and 6 digital alarm outputs (relay contact switch) with load capacity 0.1 A at 60 V. The alarm panel shall be used to locally connect to external alarming units such as door opening contacts or a fire alarm system. The operational statuses of these units shall be displayed in the network monitoring application. The base station shall be capable to provide an additional set of up to 10 digital external alarm inputs (active/open) as an option.

6.4 Availability of Network Nodes (optional)

The TETRA mobile radio system shall feature several availability-enhancing options, described in the following. It shall be possible to use capacity of several neighboring TETRA System Controller Nodes in case of a SCN failure. This concept shall ensure that in case of SCN failure, full system functionality is still available at basic capacity and performance. The bidder shall describe the redundancy concept in detail. The system shall feature distributed intelligence with a number of independent fault tolerant System Controller Nodes. This is to ensure the network to be fully operational, without degradation of service, should any of the SCN fail. All base stations which lose connection to a primary System Controller Node - due to connection line failure or failure of Node - must be re-routed automatically to secondary System Controller Nodes. The secondary System Controller Node has to be established at a different geographical location to ensure maximum resilience against external threats. A base station which loses connection to the System Controller Node shall autonomously enter Local Site Trunking mode only when re-routing fails. Both the base station as well as the System Controller Nodes shall automatically switch back to normal operation after failure recovery. The system shall use a network database in redundant mode of operation, co-located with the redundant System Controller Nodes. All network administration requests shall automatically be routed to in case when primary System Controller Nodes fail. The redundant network database shall continuously receive a replica of the master network database. Thus, in case of failure or damage of the master System Controller Node or the database itself the redundant DB will have the updated replica to operate the network. The redundant network database has to be established at a different geographical location to ensure maximum resilience against external threats. In the event of a System Controller Node failure or the connection line failure, the secondary SCN shall automatically provide the PBX interface.

23

If one System Controller Node fails the network administration workstations shall be automatically switched to secondary SCN in order to still use the network administration facilities to its full extend, e.g. modifying subscriber authorizations or get actual component status data. The connected line dispatchers shall be automatically switched over to the other System Controller Node if one gateway-providing SCN or the connection line fails.

7.0 NETWORK CAPACITY AND OPTIMIZATION

The bidder shall provide a traffic calculation based on Erlang C taking into account the Grade of Service, suitable queuing times and appropriate Erlang figures for each user and service. The TETRA system shall comprise an analysis tooling for network communication traffic, performance of the call service provision and Call Detail Record (CDR) analyzing application to plan eventual network expansions. The TETRA system shall graphically visualize TETRA network traffic, performance and load characteristics. A TETRA-specific analysis tooling shall generate reports on that data. It shall be possible to export these reports. The TETRA-specific analysis tooling shall provide display and analysis of the utilization of the air interfaces. The TETRA-specific analysis tooling shall provide display and analysis of the load of the network’s connection lines. The TETRA-specific analysis tooling shall provide display and analysis of Key Performance Indicators (KPI). KPI functionality shall provide essential performance figures of call setup times, call setup success rate, SDS transfer rate and call drop rate. These figures shall be derived from continuous net-wide measurement on all calls. KPI functionality shall support archiving of performance data. The network administration tooling shall also feature functions for call-specific performance management (evaluation of call scenarios, busy hours etc.). The TETRA network shall easily be expandable in terms of coverage (increasing the number of base stations), capacity (increasing the number of carrier frequencies per base station) and gateway interfaces. Expansions of the TETRA network shall be possible without removal of present Base Station, System Controller Node or network administration facilities.

24

8.0 NETWORK ADMINISTRATION

8.1 General Requirements

The network management system shall feature a modular structure which allows flexible deployment according to scope of functions required. The network management system shall feature client applications for fault, configuration, performance and security management as well as subscriber administration (management layers according ITU-T M.3010; “FCAPS" (fault management configuration accounting performance & security). For effective management of all system functions, all network management applications (management layers according ITU-T M.3010; “FCAPS") shall be from the same manufacturer as the TETRA infrastructure. 3rd party products shall not be used for any of the “FCAPS” network administration functions. It shall be possible to perform configurations, create or modify subscriber records, enable functions, monitor the system operation and perform software updates via remote access. The network management system shall support supervision and fault diagnostics of all network components used in the TETRA system. The network management system shall support a tool-based, automated configuration (provisioning of software and configuration data) of all network components used in the TETRA system. Operation of the TETRA system shall be completely independent of the network management functions and network databases. This especially means that a working connection of the management facilities and databases to the TETRA system must not be required for TETRA V+D operation.

8.2 Subscriber Administration

Dedicated client software shall be used for administrating subscriber data. This shall comprise the creation of subscribers and subscriber groups as well as managing authorizations and other data related to subscriber data (call zones, authorizations, special identities, fleets…). All the subscriber records shall be stored on a master data repository and retrieved by subscriber management client for processing.

25

8.3 Component Monitoring and Fault Diagnostics

Fault management functions shall be convenient for rapidly detecting and localizing faults in the TETRA network and monitoring the operational status of all system components including in-building coverage. All TETRA network components shall be permanently monitored via these functions. This monitoring application shall display the operational states and faults in an alarm status list based on the corresponding network element in the respective network infrastructure. The Fault Management shall display operational status of system-attached external devices like uninterruptible power supplies, router equipment, etc. using SNMP transmission.

8.4 Software and Configuration Provisioning

The network configuration for the TETRA infrastructure components shall be generated by a graphical software suite based on the network design model. The required parameters of the software components used shall be calculated and corresponding configuration files shall be generated, transmitted and remotely deployed on the components with minimum user interaction. No local manual software download or installation shall be used to commission base stations. All configuration files and data shall be stored one central repository for easy-to-use and consistent transfer to respective components remotely with minimum user interaction. No local manual software download or installation shall be used to commission base stations. In addition, the configuration software suite shall automatically create reports (also graphical) based on configuration data (e.g. frequency lists).

8.5 Access Control

The network administration software suite shall facilitate administration of authentication information (permissions) for users of the network administration software suite. The very same application shall store user data and user rights and generate authentication keys with personalization. Personalized authentication keys shall be generated in the form of Smartcards that are required for logging in at the network administration workstation as well as using any of the administration functions. The access to the following areas shall be restricted and access shall be configured as required for:

Network administration functions / facilities (clients),

User organizations and sub-organizations. All the user permissions stored shall be configurable independent of each other for different periods of validity.

26

8.6 Remote Diagnostic

Remote diagnostic with secure connection shall be provided using VPN or ISDN router.

8.7 Key Generation & Management

A dedicated network administration application shall manage and generate secure authentication parameters and Cipher Keys for secure voice transmission within TETRA network. This application shall include keys for mutual TETRA Authentication and TETRA Air Interface Encryption.

8.8 Security

Authorization shall be verified by the network management system and carried out by using login/password combination together with a personalized physical token.

8 IN-BUILDING COVERAGE

The bidder shall provide coverage for the TETRA radio system terminals within all terminal buildings, top floor through to the baggage basements, at OR Tambo Intl., the SAA & OR Tambo Cargo warehouses, In-flight Services building and Hangars at SAA Technical.

9 DISPATCHER SYSTEM

GENERAL AND FEATURES

A dispatcher system shall be used for communication and management of individual users and groups of subscribers. The bidder shall provide a fully operation distributed IP-based architecture dispatching system in either of the configurations to be announced by the tenderer:

Dispatching server and clients in client-server architecture used in control centers e.g. Maintenance and Operational, for maximum availability with servers in redundant configuration

Standalone single line-connected dispatching workstations used in local control centers

The overall audio and data quality shall not be degraded in the dispatching system. The voice communication between the dispatcher and TETRA infrastructure must be realized directly in the TETRA coded format, it means no encoding/decoding between TETRA systems and dispatching system should be done. The dispatching system shall reflect the individual subscriber’s, groups, fleets and settings defined in the subscriber management of the network.

27

The offered dispatching system should have access to air band radios, installed at Avionics site, for both transmitting and receiving. Access to the air band radios by individual dispatchers to be enabled/disabled remotely by the Network Administrator. The offered dispatcher shall support the following features. The line-connected dispatcher shall allow supporting all listed features:

Call Control Single Call (duplex or semi-duplex) Priority call (duplex or semi-duplex) Group Call (semi-duplex) PABX/PSTN Call (duplex) Broadcast Call (semi-duplex)

Short Data Service (SDS) messaging functions (individual/group) Send Receive Create Modify Store

Handling of predefined STATUS Messages (Individual/group)

Group Attach/Detach (Late entry on Group Calls)

History panel for voice calls, SDS, STATUS and individual notes

Local voice recording and instant replay from the dispatcher

Dialing via dial pads for TETRA and ISDN

Call hold

Dynamic Group Number Assignment (DGNA)

Call forwarding

Conference Call / Call include (Single-, Group- and PABX/PSTN call)

Monitoring of subscriber activities Call Signalling (Single- and Group Call) Registration / Deregistration of TETRA Terminals Active voice interaction / Call interception / Listening In (Single-

and Group-Call) Radio users’ status and availability Termination of ongoing calls / Forced call end

Ambience Listening

Discreet Listening

9.1 User Selection Window

The dispatcher shall allow selecting individuals, static groups, dynamic groups, other dispatchers and external users on the GUI (general user interface). The dispatching system shall allow assignment of additional tags to the users for special operational procedures. As example users to be contacted in emergency situations shall be tagged.

The minimal information for individual user selection shall include:

User properties Selected group

Group membership

The minimal information for group selection shall include:

28

Group properties

Status of attachment

Group members

The minimal information for own dispatcher selection shall include:

List of attached groups

List of disabled terminals

Monitoring results

9.1.1 Call Setup Window

The user interface shall support very fast call setup for emergency calls (by two “click” – user selection and call setup button). Each active call to/from dispatcher shall be indicated in an independent call window with audio-visual indication The offered dispatcher unit shall be able to change the volume and mute audio of each call separately. It must be possible to select a call and actively participate in the communication. The active call (with microphone focus) must be clearly identified.

9.1.2 Event Window

The event window shall display all incoming and outgoing events of the dispatcher. The minimal information for each event shall include:

Date and time

Subscriber identification

Type of event

It shall be possible to filter the events based on defined criteria. Indication of missed events must be provided as well.

9.2.2. Graphical Information System (GIS) and

Automatic Vehicle Location System (AVLS)

The GIS system shall enable dispatchers to be in a position knowing the map location of the mobile users under their guidance so that in the event of emergencies, rapid response to emergency situations will be greatly enhanced.

The GPS positions shall be stored and evaluated by the dispatching application.

29

The GIS application shall support NMEA and LIP protocol for positioning messages. The GIS extension shall provide following possibilities as minimum:

Display mobile stations (subscribers) in their last locations

Request location update by the dispatcher

Store the position of mobile users (subscribers)

Track and store the movement of mobile users (subscribers), e.g. in a form of closed curve (continuous line) representing the route of the user

Measure polygon distance, e.g. for evaluating tracks

Find subscriber on map

Jump to subscriber on map, i.e. incoming call or status message initiator

Follow subscriber on map

Zoom and pan the map

It shall support state of the art vector maps via OGC interface standard and have integrated GIS/Mapping support. The maps shall be stored in the MAP server (i.e. Geo-Server) and provide an interface to the dispatching system. The GIS shall support Geo-fencing. It shall be possible to define several areas of interests and conditions to be met whereas case-specific actions take place. With resources (mobile users) moving outside/inside the predefined area, specific alarms shall be generated automatically.

9.2.4 Security

The dispatcher/workstation users shall be identified by their user names and passwords, not the physical workstation. It shall be possible to restrict dispatcher access rights only to manage a defined sub part of TETRA network users active in the system.

9.2.5 Alarming

All central server elements of the dispatcher solution shall be integrated into the fault and alarm management system of the TETRA infrastructure. The received alarm information of dispatcher server system should be centrally stored in the loggings of network management systems.

30

10 VOICE RECORDER SYSTEM

General and Features

The recording system is required to record and archive all radio communications and telephone interconnect communications as outlined in this chapter and to provide a search and replay facility. The digital recording system shall operate continuously for 24/7. The recording system must feature full IP-based interconnection to the UHF radio communications system. All signaling, voice and data shall be transmitted using IP transmission networks / protocols. The recording system must have a modular design. The bidder shall provide a fully operation distributed IP based client-server architecture. The record and replay function shall not degrade the overall audio and data quality. The voice must be recorded directly in the TETRA coded format, it means no encoding/decoding between TETRA system and recording system shall be done. The offered recording system must include all licenses to ensure recording of all voice and data (SDS, status) communication routed through the TETRA infrastructure between terminals, terminals and dispatchers and between terminals or dispatchers and external ISDN users. In addition, recording of registration events of TETRA users shall be provided. The voice recording system, including the Player Client, shall log and replay as a minimum the following communication which is transmitted via the radio infrastructure:

All individual calls

All group calls

All emergency calls

All telephone interconnected calls

All status messages and short data messages

All system wide calls The recorded information must include but not be limited to:

Identification of the source and destination subscriber

Type of communication (voice, data, type of voice communication)

Indication for call

Source and destination user base station indication

Time and duration of each connection. The recording system must be capable to record communication from all base stations / radio cells in the network.

31

The recording system must be flexible and scalable in design in order to allow for adding capacity to support possible increase in the traffic load at any time in the future. The recording system must include all licenses to support recording of all user agencies / user organizations of the network. The offered recording system must include licenses for recording at least 64 voice channels in parallel and be expandable by simple license update. Depending of hardware setup of the recording system, various recording storage size is to be provided by simple extension of the available storage space. The recording system shall have scalable client-server architecture. Connectivity of several replay clients has to be provided. The client server communication must be realized via TCP/IP protocol (LAN or WAN).

TRANSMISSION NETWORK (IP) The connections between base stations and system controller nodes shall be realized solely by IP networks and protocols like MPLS. The Link Budgets according international standard must be provided for reference. The TETRA communication system shall use Diff-Serv capability of the transmission network. The TETRA communication system shall use at least IPv4 capability of the transmission network. The interconnection of base stations and system controller nodes must feature highest availability through redundancy with automatic traffic re-routing in case of connection failure. Primary IP link between the base stations shall be via microwave links to be proposed and installed by the bidder. IP Link redundancy to be the existing SAA IP link between the current MPT sites. Bidder to propose how this will be accomplished. The bidder shall specify the interlinking topology of all nodes in the network, including but not limited to base stations and system controller nodes. Bidder shall indicate the following Parameters/Specification:

Data speeds, losses, delays, fault or error rates etc

Quantity of Carriers the IP is capable of handling

Recording transmission ability

Switch Nodes capability, speed & options

Microwave interfacing

Bandwidth consumption

Redundancy

32

11 SYNCHRONIZATION

The TETRA network shall operate in a synchronized mode to ensure optimum cell reselection.

33

PART 2

12 SUBSCRIBER TETRA RADIO TERMINALS

12.1 General Requirements

Bidder to price-break on all terminals. All radio terminal equipment shall have a CE marking according to latest ETSI standard. Proof of latest standard to be supplied. The radio terminals shall operate in frequency band range with 410MHz – 430 MHz The offered radio terminals shall be fully interoperable with the proposed TETRA system infrastructure. Documentation in this regards to be provided. The radio terminals shall support Secondary Control Channel (SCCH) in order to increase the SDS throughput, e.g. to send radio terminals GPS position update in shorter time on SCCH. The radio programming software on a single PC shall program multiple radios simultaneously by using multiple templates to implement configuration changes. The bidder shall supply the necessary programming software and multiple programming leads for the offered radio terminals.

12.2 Handheld radio terminals

The offered radio terminal shall be complete with full keypad, large resolution display, spare battery, belt clip, stubby antenna and compatible battery charger. Different options on terminals to be offered e.g. IS, ATEX, Non-IS, Compact type, etc. The TETRA handheld radio terminal shall be protected according at least IP67. The radio terminal shall be End-to-End-Encryption (E2EE) ready and shall be enabled simply with a software license when required. The radio terminal shall be Smart card interface ready to support customized E2EE encryption The display shall be optimized to support readability even in sunlight environment. The radio terminal shall support Direct Mode Operation (DMO). The radio terminal should support a programmable minimum RF Output of 1.8W in TMO mode. The radio shall have a dedicated emergency button. The radio shall have a full keypad. The radio should support Over-The-Air-Programming.

34

The radio should support Man-down Alarm The radio shall have built-in and fully integrated GPS The radio support Location information reporting (LIP) triggered by: Emergency call/Man-down Time Distance The radio terminal should support MIL-STD-810G The radio Terminal should support configuration protection. Bidder to describe if the offered radio terminals support devices eg RFID readers, bar code scanners. Multi-chargers and options on battery types to be proposed.

12.3 Mobile radio terminal (TETRA)

All mobile radios offered must be complete with: On-glass antenna including co-axial cable and required connector, full keypad, microphone, internal speaker, power cable and mounting bracket with installation kit. GPS antenna either integrated into mobile radio’s antenna or a separate antenna. Connector for GPS to be supplied.(Bidder to specify antenna/antennas offered). The RF output power of the mobile radio shall be up to 10 Watts programmable. The mobile radio should have internal speaker and the audio output power support up to 4 Watts. The mobile radio shall support Direct Mode Operation (DMO). The mobile radio shall have a large resolution LCD display. The mobile radio should support split installation, connecting cable can support up to 15 meters.

The front console of split installed Mobile radio can support IP67.

The main unit of split installed Mobile radio can support IP54.

The mobile radio should have a built-in and fully integrated GPS module. The mobile radio should support Over-The-Air programming. 24 VDC- to-12 VDC convertor to be offered. (Price-break quantity)

The mobile radio should support Location information reporting (LIP) triggered by: Emergency call Time Distance

35

12.4 Desk Top Radio Terminals

All proposed desk top radios with microphones, both hand and desk-top microphones to be offered. Desk top radios to be integrated into the required power supply or mounted on a base tray with separate power supply. Base radio antenna with applicable co-axial connectors to be offered. GPS antenna options including applicable co-axial connectors to be offered. The RF output power shall be up to 10 Watts programmable.

The radio shall have a full keypad available. The radio shall support Direct Mode Operation (DMO). The radio shall have a large resolution LCD display. The radio should support over-the-air programming.

Speaker shall have an audio output of up to 4 Watts.

The base set radio shall have a built-in and fully integrated GPS module.