Hytera TETRA Solution For

Beacon Red Project

 CONTENTS

1. Executive Summary ................................................................................................................................... 9

1.1. Project Back ground .......................................................................................................................... 9

1.2. Hytera Proposed Solution Summary ................................................................................................. 9

1.2.1. BOQ Of Proposed Solution ...................................................................................................... 10

1.2.2. Hytera TETRA Solution Advantages ......................................................................................... 11

1.3. Conclusion ....................................................................................................................................... 12

2. Hytera TETRA Solution ............................................................................................................................. 13

2.1. System Architecture ........................................................................................................................ 13

2.1.1. Centralized Switching Architecture ......................................................................................... 14

2.2. Hytera TETRA Feature ..................................................................................................................... 16

2.2.1. Voice Services .......................................................................................................................... 16

2.2.2. Priority Functions..................................................................................................................... 18

2.2.3. Call Forwarding / Call Diversion............................................................................................... 19

2.2.4. Call Line Indication................................................................................................................... 20

2.2.5. Talking Party Identification (TPI) ............................................................................................. 20

2.2.6. Call Barring............................................................................................................................... 20

2.2.7. STATUS and SDS Messages ...................................................................................................... 21

2.2.8. Packet Data Services ................................................................................................................ 22

2.2.9. Cell Reselection........................................................................................................................ 24

2.2.10. Interference Detection ............................................................................................................ 24

2.2.11. Application Interface Services ................................................................................................. 24

2.2.12. Security Functions ................................................................................................................... 25

2.3. Hytera TETRA Network Elements .................................................................................................... 26

2.3.1. IPN (Switch Center).................................................................................................................. 26

2.3.2. IPN Server (including software modules) ................................................................................ 27

2.3.3. TETRA iBS ................................................................................................................................. 33

2.3.4. Network Management System（B/S Architecture） ............................................................ 36

2.4. Hytera TETRA Application Elements................................................................................................ 52

2.4.1. TETRA Smartone Dispatch ....................................................................................................... 52

2.4.2. Multimedia Recording & Playing System ................................................................................ 63

2.4.3. MCS-TETRA convergent solution ............................................................................................. 68

2.5. Hytera TETRA Radio......................................................................................................................... 71

2.5.1. Hytera TETRA Portable Radio PT580H Plus ............................................................................. 71

2.5.2. Hytera TETRA Mobile Radio MT680 Plus ................................................................................. 73

2.6. Planning Software ........................................................................................................................... 76

2.7. Assumptions For Planning ............................................................................................................... 76

2.8. Maps ................................................................................................................................................ 76

2.9. Antenna Pattern .............................................................................................................................. 76

2.10. Propagation Model ..................................................................................................................... 78

2.11. Coverage Predication ................................................................................................................. 78

3. Transmission Link Bandwidth Requirement ............................................................................................ 79

3.1. Quality Requirements on the IP Transport Network....................................................................... 79

3.2. Requirements on Data Transfer Rate (PSK) .................................................................................... 80

3.3. Requirements on VoIP Telephone Systems .................................................................................... 81

List of Abbreviations
The following table lists the ACCESSNET-T IP relevant abbreviations.

A-CAPI ACCESSNET-T Common Application Programming Interface

AC Authentication Center

ACS Antenna Coupling System

AGW Application Gateway

AIE Air Interface Encryption

AL Ambience Listening

APG Access Point Gateway

ASN.1 Abstract Syntax Notation One

ASR ACCESSNET System Registry

AVL Automatic Vehicle Location

BIC Barring of Incoming Calls

BOC Barring of Outgoing Calls

BSF Base Station Function

CCK Common Cipher Key

CDB Configuration Database

CDR Call Detail Record

CLIP Calling Line Identification Presentation

CLIR Calling Line Identification Restriction

CMC Circuit Mode Call

COLP Connected Line Identification Presentation

COS Core Operation Server

CXD Call Exchange by Dispatcher

DCK Derived Cipher Key

DGNA Dynamic Group Number Assignment

DHCP Dynamic Host Configuration Protocol

DIB Digital Indoor Base Station

DSS1 Digital Subscriber Signalling System No.1

DWS Dispatcher Work Station

DTMF Dual-tone multi-frequency

E2EE End-to-end encryption

EMB Event Message Broker

EMI Event Monitoring Interface

FCAPS Fault Configuration Administration Performance Security

GIS Geographic information system

GSSI Group Short Subscriber Identity

HTTPS HyperText Transfer Protocol Secure

IP Internet Protocol

IPN IP Node

IPS IP switch

ISDN Integrated Services Digital Network

ISSI Individual Short Subscriber Identity

ITCS Intermodal Transport Control System

ITSI Individual TETRA Subscriber ID

KMC Key Management Center

KPI Key Performance Indicator

LDAP Lightweight Directory Access Protocol

LogDB Logging Database

MCC Mobile Country Code

MCCH Main Control Channel

MNC Mobile Network Code

MPU Main Processing Unit

MQTT Message Queuing Telemetry Transport

MRPS Multimedia Recording & Playing System

MS Mobile Station

MTU Master Terminal Unit

NDB Network Database Node

NCM Network Capacity Manager

NMC Network Management-Client

NMN Network Management Node

NMS Network Management-System

NTE Network Termination Equipment

OOCA Object Oriented Call Addressing

OSPF Open Shortest Path First

PABX Private Automatic Branch Exchange

PDCH Packet Data Channel

PDS Packet Data Server

PGW Packet Data Gateway

PSTN Public Switched Telecommunications Network

PTT Push to Talk

RBS Radio Base Station

RRD Round Robin Database

RTP Real-time Transport Protocol

RTU Remote Terminal Unit

SAN Storage Area Network

SCADA Supervisory Control and Data Acquisition

SCCH Secondary Control Channel

SCF Switching Controller Function

SCK Static Cipher Key

SDS Short Data Service

SFPG Security Fraud Prevention Group

SIP Session Initiation Protocol

SMG SIP Media Gateway

SNMP Simple Network Management Protocol

SSCK Sealed Static Cipher Key

SSI Short Subscriber Identity

SwMI Switching and Management Infrastructure

TAP TETRA Application Platform

TCH Traffic Channel

TE Terminal Equipment

TEA TETRA Encryption Algorithm

TEI TETRA Equipment Identity

TETRA TETRA Terrestrial Trunked Radio

TL Transport Layer

TLS Transport Layer Security

TGW Telephony Gateway

TIB TETRA Indoor Base Transceiver

TPI Talking Party Identification

TVF TETRA Vocoder Function

VM Virtual Machine Monitor

VoIP Voice over IP

VPN Virtual Private Network

XGN eXchange Gateway Node

XML Extensible Mark-up Language

1. Executive Summary
1.1. Project Background
Emirates Advanced Research & Technology Holding LLC (hereby referred to also as “EARTH”) has
requested Beacon Red to provide integrated communications system(henceforth referred to also
as “The Project”). Beacon Red is looking for certified official vendors who will support Beacon
Red in the requirements.

With headquarters in Abu Dhabi, Beacon Red has gained an unmatched insight into the kinds of
operational, cultural and security issues affecting our customers in the region. Beacon Red’s
service and solutions portfolio addresses concerns across the National Security landscape, the
Beacon Red team can draw on other specialists to enhance the proposed offering or to provide a
comprehensive solution that integrates a range of technologies and systems.

Beacon Red brings state-of-the-art passive and active cyber-defense expertise that is designed
and deployed with surgical precision to deal with any risk and threat. Beacon Red has established
an elite team of specialists, providing a wide range of cyber security services with the aim to
protect classified and sensitive information assets, critical infrastructure, and all functional
components against cyber threats that may adversely impact availability.

1.2. Hytera Proposed Solution Summary

With deep understanding of Beacon red requirements, the following points are the key
requirements for this wireless communication system.

---Rapid response

---Privacy and safety

---High level security

---Versatile features

Therefore, for this project, Hytera proposes TETRA voice solution. Hytera TETRA professional
mobile radio network has been playing an important role for public security in dispatching,
disaster relief, accident disposal, mass incidents, emergency spy, national defence and country
security. Many counties have chose Hyterta TETRA to support this communication due to it has
highly security communication solution, larger users

Hytera Confidential Proprietary 9 / 82

capacity, versatile features, easy to expand, short communication established time and so on.

In this way, Hytera TETRA solution is equipped with the ability to handle the functions of unified
and visualized dispatching, rapid response. It can greatly improve capabilities to handle
emergency incidents in a much more scientific way, it allows them to reactive faster and more
accurate and more effectively than ever before.

1.2.1. BOQ Of Proposed Solution

The proposed solution shall be composed of the following components:

TETRA System Infrastructure

The TETRA system infrastructure consisting of TETRA core network, networkmanagement

system and base stations.

TETRA Application Systems

TETRA Smartone Dispatch

Multimedia Recording & Playing System TETRA Terminals

The TETRA terminals will include portable terminals and mobile terminals.

The BoQ of proposed products is summarized in the following table as shown below

Category Item Quantity Comments

2-carriers Including antenna
2 Set
Base Station system
TETRA System
IPN 1 Set Switching server

TETRA Network
NMS 1 set NMS Client
Management System

Dispatching Dispatch server and

TETRA Applications 1 Set
system client Software

PT580H Plus 20 Pcs Portable Radio

TETRA Radio
Terminal
MT680 Plus 3 Pcs Mobile Radio
1.2.2. Hytera TETRA Solution Advantages

For the benefits, a list of the most relevant user benefits is summarized herewith for aquick
appreciation on how the Hytera TETRA solution could meet your needs very well.

1.2.2.1. Open and Mature Solution

a) Hytera TETRA is mature and well-designed and widely used in various industries over the
world.
b) Hytera TETRA is well compatible with the other TETRA mainstream vendors.
c) Hytera TETRA design philosophy allows the customer to enjoy a multi-vendor supply and
development environment; to better protect investments and have product obsolescence
protection.

1.2.2.1. One Stop Solution

a) Hytera can provide a complete TETRA product portfolio; including infrastructure, radio
terminals and various applications.
b) Hytera has gained much experience to deliver turn-key projects, especially for the large-
scale networks, e.g. Netherlands MOI nationwide network.

1.2.2.2. Good User Experience

a) Hytera 3W portable terminals can give you wider communication coverage.

b) Hands-free full duplex call let you talk freely when engaged in work.
c) Seamless roaming function supports the radio terminals to roam from site to site.
d) Highest quality of voice communication lets users understand clearly even in noisy
environments.

1.2.2.3. High Availability and Reliability

a) The system configuration proposed provides high availability of Switching Center and
Base Stations on the perspective of system resilience and integrity.
b) Hytera TETRA can support multiple redundancy features to ensure a system most
reliable.
c) In “Fall-back” mode, the base station maintains the Base Station Function (BSF), all the
wireless service including voice, data, applications and others are still ensured since the
corresponding subscriber data are stored in the base station.

1.2.2.4. Flexible Network Architecture

Hytera TETRA system can support two types of switching architecture: centralized
architecture and distributed architecture.
 a) Distributed architecture is suitable for small-scale networks, self-sustaining regional
multi-site networks as well as flexible network topologies like used e.g. with rapid
deployment scenarios.
b) Centralized architecture is suitable for the large network structures like used for
nationwide networks.

1.2.2.5. Modular Design and Easy System Expansion

a) Hytera TETRA system is of modular design.

b) Protection of investments and future system expansion can be easily achieved at
optimum costs.

1.2.2.6. IP-based System

a) Hytera TETRA system is a full IP-based infrastructure.

b) Such proposed IP-based architecture is proven and easily configuration as full
redundancy system and suitable for flexible network.
c) Potential services is commercially available from third party
d) Cost-effective solution.

1.2.2.7. Open Application Interface

a) SIP is an open protocol

b) Easily connect to any PABX/PSTN system
c) IP-connected dispatching system
d) IP-connected voice recording system
e) Application interface easy to be integrated with the third part applications.

1.2.2.8. Interconnection solution

Hytera can provide different system interconnection solutions to ensure the

communications between TETRA and DMR, analogue and etc.

1.3. Conclusion
We appreciate the opportunity to submit this proposal to Beacon Red. The TETRA solution
proposed by Hytera is proven, reliable, and compliant solutions.

We would also like to emphasize that we place great importance on after sales service and would
strive to achieve this through support contracts or any other mutually acceptable service support
methodology that will best suit your needs.

Last but not least, we would like to take this opportunity to thank you again, and to state that we
want your business and are ready to serve.
2. Hytera TETRA Solution
TETRA is the acronym of Terrestrial Trunked Radio, it is a global Standard for the digital trunked
radio. As a digital method of transmitting mobile radio signals, TETRA is characterised by high
voice quality and improved spectrum efficiency.

This standard was developed by the European Telecommunications Standards Institute (ETSI) in
partnership with leading manufacturers, operators and user organisations. Secure voice and data
transmission, excellent functionality and a wide range of performance features guarantee the
adaptability needed to meet the challenging requirements of professional mobile radio and its
usage-critical applications.

As a system platform, TETRA is able to bring together the services for trunked radio and mobile
data transmission that were previously confined to isolated infrastructures. This increases
flexibility and helps to relieve cost pressures on network operators and users.

The proposed Hytera TETRA trunking system was developed in compliance with the
specifications of the ETSI and meets all the requirements of ETSI standard that is recognised on
an international basis and compliant frequency band to provide secure two-way voice and data
communications.

2.1. System Architecture

The unique, modular system design of the ACCESSNET-T IP (Hytera TETRA brand) of Hytera
permits the configuration of the TETRA systems exactly according to the customer-specific
requirements.

The system technology of ACCESSNET-T IP is scalable so that the availability, capacity and
network size can grow over time. The integrated voice and data communication avoid the
differentiation of different networks. Mostly, new requirements can be met with software
expansions. This enables the system technology of ACCESSNET-T IP to represent a future-proof
and cost-efficient solution for PMR networks.

The system design facilitates distributed and centralized switching architectures as well as the
combination of the two switching architectures. With centralized systems, switching of voice
and data as well as the transition to external networks such as PABX/PSTN is implemented at a
central point in the system. The distributed switching variant of the ACCESSNET-T IP permits
increased flexibility in configuring the system due to the possibility of implementing routing
functions and gateways at any points in the system; this happens by distributing the operative
function blocks to the various network
elements. Apart from the increased flexibility, the distributed architecture offers an increased
robustness of the systems against the failure of individual locations.

The following chapter describes the various architecture models.

2.1.1. Centralized Switching Architecture

The centralized switching architecture is the classical model in the world of telecommunications.
All the switching tasks for voice and data as well as the gateways to external systems such as
PABX/PSTN are implemented at a centralized point in the system. This/these switching node(s),
however, should be redundant at geographically different locations in the system, if possible, to
be able to maintain the functions of the radio system when one location fails.

The classic model of the centralized switching architecture supports the following advantages,
among other things:

• Highest availability of the centralized node (IPN) by means of redundant server

architecture (geographical redundancy possible)

• Redundant connection of PABX and applications at the same location

• Interfaces with a high capacity, software functions and function blocks can be
combined on one powerful server

• Minimum bandwidth demand to base station locations

The central equipment can feature enhanced availability by several redundancy options. To
provide highest reliability, even against natural disaster, terrorist attack or site take- down,
geographically separated switching centers can be provided with this network design. The
alternative switching center permanently replicates data with the primary one to keep the whole
communication running when the primary switching center fails or is taken out.
Figure 2-1 Example of a network with centralized, redundant switching architecture
2.2. Hytera TETRA Feature
Hytera TETRA system allows the following radio services and functionalities:

2.2.1. Voice Services

2.2.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.

2.2.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 identity of the talking party (mobile terminal ID or alias) is to be displayed to all the members
of the group.

Group call conditions:

Differentiates between the conditions "Minimum queueing time" and "Full group" for
connecting a group call:

• "Minimum queueing time"

The group call is set up as soon as a radio resource (traffic channel) in the base stationof the
source subscriber is available.

If no radio resource is available in one of the involved base stations, the subscribersin this

radio cell are not involved in the group call.

• "Full group"
The group call is only set up after a radio resource (traffic channel) in each involved basestation
is available.

If no radio resource is available in one of the involved base stations, the group call is
queued.

2.2.1.3. Late Entry

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 channelswhere
group members are assumed.

2.2.1.4. 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.

2.2.1.5. 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).

2.2.1.6. 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 ofradio cells).

2.2.1.7. Member-Tied Group Call

The system shall allow for dynamically assigning members to specific groups. Resources (voice
channels) may thus only be set up and maintained only in radio cells in which subscribers or their
terminals are registered, who belong to the group and who attached them.
2.2.1.8. Closed group call

Group calls to a closed group can only be set up by terminals that are member of the group. This
can achieve confidentiality in the group communication. For example, application or telephony
subscribers cannot establish calls to this group.

2.2.1.9. Group patching

Allows dispatchers to select a number of existing talk groups and to combine them to one
patched group. This allows the collaboration and communication between talk groups and their
members, even if this was originally not planned and considered.

2.2.1.10. Multiple Call-Setup (Multiple Selection)

Allows dispatchers to initiate calls simultaneously to multiple destinations.This allows a

broadcast call from a dispatcher to all addressed subscribers and talk groups with their members,
even if this was originally not planned and considered.

2.2.2. Priority Functions

2.2.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 andmobile
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 ongoingcommunication
with a lower priority in the case of a lack of resources.

2.2.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.

2.2.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 thecall
priority.

For calls with the highest priorities (level 12-14) 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 8).

2.2.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.

2.2.2.5. Default Call Priority

A default call priority per subscriber shall be provided.

2.2.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 emergencysituation).

All other voice calls in that base station site shall be interrupted to allow users to join thePriority
Open Channel.

2.2.3. 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.

2.2.3.1. Unconditional

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

subscriber.
2.2.3.2. On busy subscriber

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

2.2.3.3. On subscriber not reachable or no reply

Call diversion on “not available” subscriber shall be configured in the network

management for a subscriber.

2.2.4. Call Line Indication

2.2.4.1. Call Line Indication Presentation (CLIP)

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

2.2.4.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 toISDN.

2.2.4.3. Forced CLIP and CLIR

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

2.2.4.4. CLIR Override

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

2.2.5. Talking Party Identification (TPI)

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

2.2.6. Call Barring

The permission to receive/initiate calls shall be configurable for each individual

subscriber, group，PABX/PSTN and application subscriber.

2.2.6.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, PABX/PSTN calls,
duplex calls, status calls, SDS calls, calls to members of other fleets.

2.2.6.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 individual calls, group calls, PBXcalls,
PSTN calls, duplex calls, status calls, SDS calls, calls to members of other fleets.

2.2.7. 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 2039 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.

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).

The system shall provide a SDS Store and Forward function. This shall improve messaging
convenience for the user by temporarily storing SDS which cannot be delivered immediately and
re-attempting delivery at a later time, when the recipient is available again.

The system shall be configurable with different retention times (maximum storage durations).

The system shall automatically detect availability of mobile users and upon this initiate
forwarding of SDS.
The sender of the original message shall be notified upon storing of SDS (delayed

Messages) as well as upon final time of delivery or rejection.

2.2.8. Packet Data Services

The TETRA system shall support single-slot Packet Data transmission. The

TETRA system shall support multi-slot Packet Data transmission.

The system shall provide a Packet Data interface using Dynamic Host Configuration Protocol
(DHCP) so that IP addresses for mobile radio units can be dynamically assigned by the connected
provider network.

The system shall support assignment of static IP addresses to TETRA mobile radio unit’s
/ user identities as an alternative to DHCP (IP addresses to be statically assigned by network
operator using the network administration tooling).

The connection shall be made via a system IP gateway provided in the System ControllerNode or
Base Station.

The system shall support the dynamic routing protocol OSPF (Open Shortest PathFirst).

The Packet Data service shall support sharing of a Packet Data channel (PCH; air interface
resource) between several TETRA radio units requesting Packet Data service inparallel.

The maximum number of Packet Data users per air interface channel used for Packet Data shall
be configurable in the network administration tooling. A maximum number of 99 users per
channel shall be supported.

The maximum number of Packet Data users in the TETRA system shall not be limited to a
number smaller than the maximum number of users in the TETRA system. That means that
basically every TETRA subscriber can be approved by the network operator to use Packet Data
service.

The sharing of Packet Data channel (PCH; air interface resource) shall be possible for single-slot
Packet Data resources as well as multi-slot Packet Data resources.

The system shall allow dynamically assigning unused traffic channels to either voice
communication or Packet Data transfer.

The system shall allow to configure a maximum percentage of air interface channel resources
(time slots) to be used for Packet Data service as a percentage of the total
number of air interface channel resources (time slots). The maximum percentage of channel use
shall be configurable for each base station separately.

The system shall allow to configure a maximum percentage of air interface channel resources
(time slots) to be used for voice service as a percentage of the total number of air interface
channel resources (time slots). The maximum percentage of channel use shall be configurable for
each base station separately.

The system shall support the configuration of exclusive channels only to be used for Packet Data
transfer. The number of exclusive Packet Data channels shall be configurable for each base
station separately. Even with traffic channels (TCH) occupied by voice communication and voice
calls queued the base station shall not assign those exclusive channels for voice communication.
The exclusive channel configuration shall be possible for single-slot Packet Data resources as
well as multi-slot Packet Dataresources.

The system shall support the configuration of a guaranteed minimum number of Packet Data
channels in case when the base station has reduced air interface resources. This shall allow a
guaranteed minimum utilization of the Packet Data service even when parts of the regular TETRA
carriers fail. The number of guaranteed minimum Packet Data channels shall be configurable for
each base station separately.

The system shall support the configuration of a guaranteed minimum number of voice channels
in case when the base station has reduced air interface resources. This shall allow a guaranteed
minimum utilization of the voice services even when parts of the regular TETRA carriers fail. The
number of guaranteed minimum voice channels shall be configurable for each base station
separately.

The base station shall support configuration of channel assignment strategy “maximum
bandwidth for each Packet Data user“. With that configuration the base station assigns new air
interface resources (time slots) for each radio terminal requesting air interface resources for
Packet Data transfer as long as the maximum number of Packet Data channels on the base
station has not been reached.

The base station shall support configuration of channel assignment strategy “maximum
utilization of Packet Data channels “. With that configuration the base station does assign already
used air interface resources (time slots) for new radio terminals requesting air interface
resources for Packet Data transfer as long as the maximum number of Packet Data users per
channel has not been reached.
2.2.9. Cell Reselection

The following cell reselection types shall be supported:

• Undeclared,
• Announced Type 2 & 3 as well as
• Unannounced.
Undeclared

A terminal change to another cell without an existing call. The terminal automaticallyregisters in
the new radio coverage area.

Announced Type 2 & 3 as well as

If a Mobile Station (MS) involved in a group call roams into a cell, where the group calldoes not
exist, the group call will be established in this cell.

Unannounced

A terminal leaves the topical radio cell during a call without informing the system. Thismay
happen if all of a sudden the connection to the base station is interrupted.

2.2.10. Interference Detection

The system shall provide continuous interference (jamming) measurement / detectionduring

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 interference on one or more of itsreceiving
frequencies.

2.2.11. Application Interface Services

The offered TETRA system shall provide an interface for application integration, especially to be
used for 3rd party application integration.

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) via a
single interface based on TCP/IP and Voice-over-IP methods.

The application interface shall provide call control functions and at least support DGNA call setup
and management, voice call monitoring, ambience listening and authorization services.
The interface shall be an open interface, meaning that the interface specification and
communication protocols are provided to application vendors or the costumer for usage.

The system shall support provision of this application interface on all types of network nodes,
especially on Base Stations and System Controller Nodes.

2.2.12. Security Functions

2.2.12.1. Air Interface Encryption (AIE)

Air interface encryption (AIE) is the encryption of signaling, data and voice on the air interface.
The purpose of this encryption is to render the air interface transmission interception-proof.

The Air Interface Encryption feature secure the radio link set up between the mobile stations /
radio subscribers and the TETRA base stations within the MATS Network such that no external
monitoring by any party other than MATS is possible.

This system can activate this feature for all ongoing calls and data transmission.

Our infrastructure provides two different encryption classes – TETRA AIE Class2 and Class3.
Class3 provides a higher level of security by using different keys for each individual subscriber
and in each radio cell for group communication but at higher costs.

2.2.12.2. TETRA Authentication

Authentication is an effective means of protection against the illegal utilization of the radio
network. The authentication takes place while the mobile stations register (initial registration or
cell re-selection) and serves for verifying the authenticity of a mobile station or the radio
infrastructure. In this way, only successfully authenticated mobile stations are admitted in the
radio network and are able to use voice and data services. Authentication makes it impossible to
use falsified or cloned mobile stations in the radio network.

Hytera TETRA supports two types of authentication, in which either the infrastructure
authenticates the mobile station or the infrastructure and the mobile station authenticate each
other ("Mutual Authentication").

These authentication mechanisms can be initiated by the system or mobile station in each case.

This feature is optional and can be added to the scope of functions of Hytera TETRA using
corresponding licenses.
2.2.12.3. End-to-End-Encryption (E2EE)

The transport of End-to-End (E2E) encrypted speech between radio terminals shall be supported
by the TETRA infrastructure.

The radio system shall be transparent to E2E-encrypted communications.

The transport of E2E-encrypted speech between radio terminals and wireless dispatchers shall be
supported.

The transport of E2E-encrypted speech between radio terminals and wireless dispatchers shall
use the same E2EE as between radio terminals.

The transport of E2E-encrypted speech between radio terminals and line-connected dispatchers
shall be supported.

An indigenous End-to-End-Encryption (E2EE) algorithm, meaning customer specific encryption

algorithm, shall be supported by the system and the mobile radio equipment as well as and
wireless and wire connected dispatchers.

2.2.12.4. Enable And Disable Of Radio Terminals

The system shall support temporary and permanent disabling of terminals according to ETSI
standard ETSI EN 300392-2 and TETRA TTR 001-13.

The system shall support enabling of temporary disabled terminals according to ETSI
standard ETSI EN 300392-2 and TETRA TTR 001-13.

To support tracing of stolen or lost radio terminals the system shall provide AmbienceListening to
be used by dispatching applications on temporarily disabled terminals.

To support tracing of stolen or lost radio terminals the system shall provide possibility totrack
temporary disabled terminals (transmission of GPS positioning data).

2.3. Hytera TETRA Network Elements

2.3.1. IPN (Switch Center)

In TETRA system, the IPN (IP Node) is used as a network element of the TETRA ACCESSNET-T IP
(Hytera TETRA Brand) radio system and serves for providing the switching function. The IPN can
be scaled according to the performance requirements
and network capacity. In this way, the IPN is flexible and can be customized for the
respective requirements.

Figure 2-2 IPN Cabinet

IPN Cabinet Specification

DESCRIPTION SPECIFICATION
Width 600 mm
Height 1245 mm (24U)
Depth 1000 mm

Remark: Other dimensions on request and/or according to project-specific offer

Table 2-1 IPN Cabinet Specification

2.3.2. IPN Server (including software modules)

The functions are implemented by the IPN server in the form of a MPU hardware compo- nent,
which may be integrated multiple times in the equipment rack and which provides the
corresponding software components. Apart from the Switching Controller Function (SCF), the IPN
server can provide additional functions e.g. the Telephony Gateway (TGW) for connection to
telephone networks.

In addition, hardware components e.g. a VoIP private automatic branch exchange (Voice over IP,
VoIP) may have been incorporated into the IPN cabinet as shown above. Furthermore,
depending on the range of functions required, additional qualified hardware components can be
added to this IPN cabinet.
2.3.2.1. IPN Server Hardware and Specification

Figure 2-3 IPN Server - Lenovo ThinkSystem SR250

Hytera uses high performance Lenovo ThinkSystem SR250 as the system central switch
server.The Lenovo ThinkSystem SR250 single-socket 1U rack server is designed for small
businesses and first-time server buyers looking for a solution to improve business efficiency. It
delivers several innovative features in a compact 1U form factor with a competitive price. The
ThinkSystem SR250 provides next-generation performance in an innovative and compact design
with flexible configuration options, built-in security, and systems management capabilities.

Lenovo ThinkSystem SR250 main specification:

Item Specification
Model ThinkSystem SR250
CPU E-2134 4C/8 3.5GHz
Memory 8GB 2666MHz TruDDR4
Hard Disk 2*600GB 10K 12Gbps SAS 2.5
RAID Controller RAID 530-8i SAS RAID Controller
Ethernet Port 2x1G Base-T Network Card
PowerSupply 2*450W
Optical Drives
DVD-RW(External ）

Operation System ACCESSNET-T IP AEOS

Table 2-2 Lenovo ThinkSystem SR250 Specification

2.3.2.2. IPN Server Function Blocks

ACCESSNET-T IP profits from a lean software architecture by combining the respective

software components in modular software nodes. These software nodes are typically
operated in a virtualized runtime environment. Depending on the project requirements, the
software components can be operated of course also natively on respective platforms.
The following software nodes are available:
eXchange and Gateway Node (XGN)
Network Management Node (NMN)
Network Database Node (NDB)
1. eXchange and Gateway Node (XGN)
The eXchange and Gateway Node (XGN) is the operative node type in the ACCESSNET-T IP
Switching and Management Infrastructure (SwMI). This node type contains multiple
mandatory as well as optional software components. Thus, the XGNrepresents the functional
set of switching and gateway functions.

Typically, these software components are deployed and hosted as a common VirtualMachine (VM)
appliance.

The following operative components can be installed on the eXchange and GatewayNode (XGN):

◼ Core Operation Server (COS)

◼ IP Switch (IPS)

◼ TETRA Application Platform (TAP) - optional

◼ SIP Media Gateway (SMG) - optional

◼ Packet Data Server (PDS) - optional

The following figure shows the eXchange and Gateway Node (XGN) and its components.
Core Operation Server (COS)

The Core Operation Server (COS) is a software component which performs all calcula- tions and
control for exchange processes of higher protocol layers. Apart from the switching process, this
includes the call administration and the authorization validation. In addition the COS uses and
controls the software component IP Switch (IPS) and, if nec- essary, the SIP Media Gateway
(SMG) to switch the voice streams.

IP Switch (IPS)

The IP Switch (IPS) is a software component and serves for distributing TETRA voice data
between software components and to external applications (optional) and is thus a central
control component of the network element. The IPS is controlled by the Core Operation Server
(COS).

The TETRA voice data are transferred in the form of IP data packages which contain both the
TETRA voice data and additional routing data. The IP data packages aretransferred by the IPS via
point-to-point connections ("Unicast").

TETRA Application Platform (TAP)

The TETRA Application Platform (TAP) is a software component and acts as the gateway between
software applications and the ACCESSNET-T IP. The TAP is responsible for logging in/authentication of
the relevant software applications and connecting them to the radio network.

Software applications can be connected to the TAP via the ACCESSNET ®-T Common Application
Programming Interface (A-CAPI). For call-related and short data services the TAP forwards the data
e.g. to the Core Operation Server (COS), thereby providing the connection between software
applications and the radio network. Via the connection with the TAP, the respective software
application can be fully integrated into the ACCESSNET-T IP.

Depending on the type of software application it can act like a radio subscriber and, e.g., send
short messages (SDS), establish and answer calls, etc (dispatcher). Other types of software
applications may be used for monitoring services or recording the networkcommunications.

SIP Media Gateway (SMG)

The SIP Media Gateway (SMG) is a software component and used for connecting SIP- based
PABX. The SMG converts TETRA-coded voice data to G.711 and back to facilitate the
communication between TETRA subscribers and private branch exchange sub- scribers. For the
communication with PABX, the SMG uses the standardized Session Ini- tiation Protocol (SIP). In
this function, the SMG is used as SIP trunk.
Packet Data Server (PDS)

The Packet Data Server (PDS) is a software component and provides the Packet Data service. The
Packet Data service allows the efficient transmission of IP-based packet data between
terminals within the ACCESSNET-T IP mobile radio system and to exter- nally connected IT
customer systems (e.g. databases). In this case, the PDS is the access point to the IT
customer system of the respective user organization for the termi- nals registered in the
ACCESSNET-T IP. To this end, the PDS provides an IP gateway (access point gateway, APG) for
every user network, which is identified by a unique access point name index (APNI).

2. Network Management Node (NMN)

This software nodes comprises administrative software components of the network man- agement
system (NMS) and is therefore described in chapter 2.3.6.1 Network Management Node(NMN).

3. Network Database Node (NDB)

This software nodes comprises administrative software components of the network management
system (NMS) and is therefore described in chapter 2.3.6.2 Network Database Node (NDB).

2.3.2.3. PABX/PSTN Gateway

PABX/PSTN gateway for medium and large businesses and enterprise branch users to launch the
industry's first integration of PBX, IP PBX, unified communications applications such as
converged network communication system for 50-1000 users of the enterprise.PABX/PSTN
gateway series modular design concept, in a unified hardware platform integrates voice
communications, real-time communications and other functions and operations. IPPBX series of
products using the industry's popular chip technology to support E1,FXO\FXS, SIP, IMS interface,
supports maximum four E1\T1,208 FXO\FXS, 128 SIP trunk,1000 IP extension.

PABX/PSTN call to TETRA subscribers

ACCESSNET-T IP supports calls from telephone subscribers (PABX/PSTN) to TETRA individual

subscribers (prefix+ISSI).

PABX/PSTN call to TETRA group

ACCESSNET-T IP supports calls from telephone subscribers (PABX/PSTN) to TETRA groups

(prefix+GSSI). Hence, a telephone subscriber can not only participate in group calls (listen and
talk) but also initiate group calls.
PABX/PSTN Hardware and Specification

Figure 2-4 PABX/PSTN Gateway

Hytera will provide CENTNET X6 (2.1) as the PABX/PSTN gateway for this project.

CENTNET X6 (2.1) Specification:

Item Specification
SIP Extension 50-1000

IP Channels 32-128

Analog Port 32FXO\FXS(RJ45)

E1 Trunk 0-4E1

GSM port 0–8

Ethernet Interface 2 (10/100/1000M Base-T)

Console 1 (RS232 PORT)

CISCO、Siemens、AVAYA、
Compatibility
Huawei、ZTE

Input voltage DC -48V or AC 110-240V

Power 40W

Telephone line transmission <10KM

distance

Dimension 480mm*286mm*44mm (1U)

Weight 4KG

Environment 0℃～50℃, Less 80%

Table 2-3 : CENTNET X6 (2.1) Specification

2.3.3. TETRA iBS

The TETRA iBS is Hytera new generation base station with the integrated one box design to
allow the flexible deployment. Compared with the traditional PMR BS, TETRA iBS features the
highly integrated design, multiple carriers, SDR technologies. The excellent RF power
performance and eco-friendly technology adoption aim to provide superior flexibility and
efficiency of radio communication solution for the customer.

Figure 2-5 TETRA iBS

The TETRA integrated Base Station (iBS) is a base station suitable for outdoor and indoor
operation. Due to its small size, the TETRA iBS is easily transported, flexibly mounted, and quickly
deployed, which reduces the networking cost. The TETRA iBS can be mounted on walls and the
top of antenna masts. In temporary networking scenarios, the TETRA iBS can be deployed to
build emergent radio coverage, offering abundant solutions to command and dispatch.

Flexible Deployment

Compare with traditional PMS base station which request the shelter and technical room housing
for conditioning and operation, TETRA iBS with IP66 protection degree greatly reduce the
requirement of the deploy conditions. The site deployment can be realized just with a mast or a
wall.

Multi Carriers Technology

TETRA iBS adopt the state-of –art SDR technology which allows more than one carrier in a single-
box unit. Users can configure carrier capacity up to 4 carriers with one unit. For
one site, two iBS units combine to provide up to 32 radio channels. It is flexible to adaptto the
expected traffic load.

Wide Coverage

TETRA iBS the RF output power is up to 40W/carrier @ 2-carrier, 20W/carrier@4-carrier which

ensure large downlink coverage. Moreover, together with 4-diversity to improve uplink coverage,
single TETRA iBS coverage expand at least 30%. Less base station cancover the certain area, the
cost of the TETRA infrastructure got reduction.

Eco-friendly

TETRA iBS adopts high-conductivity aluminum alloy material for heat dissipation, and nofan is
needed inside the base station. The maximum power consumption is less than 400W, which
saves up to 50% of the power compared with the traditional 4-carrier base station (a single site
can save nearly 5,000 KWH a year), greatly reducing the network operation cost.
TETRA iBS Base Station Datasheet

Item Specification

 380 to 390, 410 to 420 MHz (Rx)

Frequency Range
 390 to 400, 420 to 430 MHz (Tx)
Transmitting Power ▪ 40 W @ 1 carrier per path with π/4-DQPSK modulation
(Antenna socket) ▪ 20 W @ 2 carriers per path with π/4-DQPSK modulation

Max. number of
 8 Carrier(two units)
transceivers

 -120 dBm (Static) (BER 4%)

Sensitivity
 -113 dBm (Dynamic) (TU 50 [TCH 7.2, BER 4%])
Size(Height x Width x
 435 x 157.5 x 340mm
Depth)

Weight  ≤ 26.5 kg
Temperature Range
 -40℃ ~ 60℃
Power supply  –48 VDC

 Mast
Mounting options
 Wall
Power consumption  400W @ 40W Tx TOC
Protection class  IP66

Reception  Four diversity

Table 2-13 : TETRA iBS Base Station Specification

2.3.4. Network Management System（B/S Architecture）

The network management system (NMS) can be used to manage and monitor infrastruc- ture
and various services of ACCESSNET-T IP.

It is a distributed multi-client and multi-server system with integrated databases, whose modular
design can be scaled according to the respective requirements and size of the network.

The NMS is made up of the following components/layers:

◼ Network management software (web) servers and software tools –

presentation layer and business layer

◼ Databases – persistence layer

◼ Network management interfaces – for linking external systems e.g.

umbrella and billing systems

The following table describes the function areas and the associated NMS tools.

Function area NMS tools

Fault management Infrastructure Monitoring and Maintenance
Network Element Manager
Proxy Agent
Configuration management Network Manager
Network Element Manager
NMC-515 ConfigurationManager
Subscriber/user management Subscriber Manager
Performance management Admin Log Viewer (ALV2)
Network Capacity Manager
Security management NMC-514
Subscriber Manager

The two major network topology elements are of the node types Network Management Node
(NMN) and Network Database Node (NDB).
2.3.5.1 Network Management Node (NMN)

The Network Management Node (NMN) is one of the administrative node types in the ACCESSNET-T
IP Switching and Management Infrastructure (SwMI). This node type contains multiple mandatory as
well as optional software components of the network management system (NMS). Thus, the NMN
represents a certain functional set of NMS functions.

Typically, these NMS components are deployed and hosted as a common Virtual Machine (VM)
appliance.

The Network Management Node (NMN) is a virtual machine (VM) and comprises the components of
the network management system (NMS). The Network Management Node (NMN) is fully integrated
and by using the Network Element Manager software updates can be easily performed. The VM is
based on the ACCESSNET®-T Embedded Operating System (AEOS).

The following components can be installed on the Network Management Node (NMN):

◼ ACCESSNET System Registry (ASR)

◼ Infrastructure Monitoring and Maintenance
◼ Network Capacity Manager
◼ Network Element Manager
◼ Network Manager
◼ Proxy Agent
◼ REST-ASR
◼ Store and Forward Center (SFC)
◼ Subscriber Manager
◼ Umbrella Agent

The following figure shows the Network Management Node (NMN) and its components.
2.3.5.1.1 Infrastructure Monitoring and Maintenance

The Infrastructure Monitoring and Maintenance offers a graphical and tabular overview of the entire
ACCESSNET-T IP TETRA radio network. The network elements are displayed as icons according to their
geographical position on the map. All alarm states and service states of the network elements and
devices are shown. For a detailed fault analysis the Network Element Manager and the Proxy Agent
can be opened directly from the status window.

The Infrastructure Monitoring and Maintenance is a web-based tool which is easily acces- sible with a
common web browser. State-of-the-art WebSocket technology ensures that status changes are
displayed instantly on the user interface without the need of any user interaction.

Access to the Infrastructure Monitoring and Maintenance is secured by authentication with user
accounts.

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas, sub-areas and tabs in an easy way to use. State- of- the-art WebSocket
technology ensures that status changes are displayed instantly on the user interface without the
need of any user interaction. In the Infrastructure Monitoring and Maintenance software tool the
following views are provided:

Map view: geographical overview of all network elements with

-summary status of the operational part of the system
-summary status of devices and platforms

Figure 2-6 Infrastructure Monitoring and Maintenance GUI - Map view (example)
 Tabular network view: tabular view containing all network elements with their alarm status and
details

Figure 2-7 Infrastructure Monitoring and Maintenance GUI - Table view (example)

Site view: overview of all supervised network element functions and services with theirstatus
Figure 2-8 Infrastructure Monitoring and Maintenance GUI - Site view (example)

Alarm history view: alarm events can be filtered and displayed in chronological order
 Figure 2-9 Infrastructure Monitoring and Maintenance GUI - Alarm history view (example)

Possibility to quickly access the respective Network Element Manager or Proxy Agent for
detailed alarm status.

2.3.5.1.2 Network Manager

The Network Manager is a server application for central configuration and software updates in
ACCESSNET-T IP. The Network Manager provides a web-based user inter- face which is easily
accessible with a common web browser. With the Network Manager, software updates to already
existing or newly added network elements can be initiated and specific network- wide configuration
parameters for the network elements (base sta- tions and switching nodes) and hardware
components can be edited directly via the user interface of the Network Manager.

For a bulk configuration of the entire radio network or subsets of network elements the configuration
can be exported as CSV files (Comma-separated values, CSV) for base stations and XGNs (eXchange
and Gateway Nodes, XGN), edited in a spreadsheet tool and imported back into the Network Manager
for easy configuration updates. During the editing in a spreadsheet tool, lists of e.g. updated
frequencies can be integrated in the CSV file.

Newly added base stations can be assigned to XGNs. The number of unassigned base stations is
highlighted on the user interface of the Network Manager.

The Network Manager stores all configuration data in a central Configuration Database (CDB).

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas, sub-areas and tabs in an easy way to use.
State-of-the-art WebSocket technology ensures that status changes are displayed instantly on the
user interface without the need of any user interaction.

Figure 2-10 Network Manager GUI main screen ‒ OVERVIEW tab (example)

2.3.5.1.3 Network Element Manager

The Network Element Manager is a server application for managing network elements in an
ACCESSNET-T IP TETRA radio network. The Network Element Manager provides a web- based user
interface which is easily accessible with a common web browser.

The tool is running on the network element itself and can be accessed directly on site without
connection to the IP transport network or from a control room. State-of-the-art WebSocket
technology ensures that status changes are displayed instantly on the user interface without the need
of any user interaction.

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas, sub-areas and tabs in an easy way to use.

State-of-the-art WebSocket technology ensures that status changes are displayed instantly on the
user interface without the need of any user interaction.
 Figure 2-11 Network Element Manager GUI main screen - OVERVIEW tab, example of a DIB-R5 basestation node

2.3.5.1.4 Proxy Agent

The Proxy Agent is a server application for monitoring external equipment like e.g. routers, switches,
sensors and visualizing them in the network management system (NMS). The so- called "southbound
interface" queries and monitors any equipment used in the ACCESSNET- T IP TETRA radio network.
The Proxy Agent is highly flexible and capable of monitoring any relevant parameters of connected
equipment and fully inte- grates in the fault management. The status of the equipment is visualized in
the Infra- structure Monitoring and Maintenance, offering a comprehensive overview of the radio
network and its components. For a detailed fault analysis the Proxy Agent can be opened directly
from the status window of the Infrastructure Monitoring and Maintenance.

The Proxy Agent is a web-based tool which is easily accessible with a common web browser. It is
running centralized on eXchange and Gateway Node (XGN), distributed on base stations or on any
servers. State-of-the-art WebSocket technology ensures that status changes are displayed instantly on
the user interface without the need of any user interaction.

Access to the Proxy Agent is secured by authentication with user accounts.

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas, sub-areas and tabs in an easy way to use.

State-of-the-art WebSocket technology ensures that status changes are displayed instantly on the
user interface without the need of any user interaction.
 Figure 2-12 Proxy Agent GUI main screen (example)

2.3.5.1.5 Subscriber Manager

The network management tool Subscriber Manager is the web-based tool for conven- iently and
efficiently administrating subscriber data and all subscriber-related data like

e.g. talk groups and group profiles. Furthermore, the Subscriber Manager is used for managing users
of other network management tools.

To provide each user group with the matching functional scope, the Subscriber Manager supports
role-based access.

Changed subscriber data are instantly distributed throughout the ACCESSNET-T IP. The Subscriber
Manager is connected via a REST interface to the ASRD master node and the subscriber data are
stored in the integrated SQLite database.

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas, sub-areas and tabs in an easy way to use.

The following graphic shows an examples of the Subscriber Manager GUI.

Figure 2-13 Subscriber Manager) GUI main screen ‒ SUBSCRIBERS area

2.3.5.1.6 Network Capacity Manager

The Network Capacity Manager is a server application for capacity management of ACCESSNET-T IP
mobile radio networks and is used for monitoring and managing the radio capacity and load data of
base stations. The Network Capacity Manager allows to adjust the ratio between traffic channels
(TCHs) and secondary control channels (SCCHs) to manage the capacity and optimize the channel
usage.

Furthermore, by means of the Network Capacity Manager additional transceiver modules (TETRA
Channel Unit, CHU) can be activated for enhanced capacity.

All required information is presented in a web-based graphical user interface (GUI).

State-of-the-art web technology ensures that status changes are displayed in the Network Capacity
Manager automatically in near real-time and without user interactions to enable quick responses and
to maintain the operational readiness.

Figure 2-14 Network Capacity Manager GUI main screen – Real-time dashboard of BS performance -Overview

2.3.5.2 Network Database Node (NDB)

The Network Database Node (NDB) is one of the administrative node types in the ACCESSNET-T IP
Switching and Management Infrastructure (SwMI). This node type contains multiple mandatory as
well as optional software components of the network management system (NMS). Thus, the Network
Database Node (NDB) represents a cer- tain functional set of NMS functions.

Typically, these NMS components are deployed and hosted as a common Virtual Machine (VM)
appliance.

The Network Database Node (NDB) is a virtual machine (VM) and comprises multiple mandatory as
well as optional software components of the network management system (NMS). Thus, the Network
Database Node (NDB) represents a certain functional set of NMS functions. The VM is based on Linux
CentOS.

The following components can be installed on the Network Database Node (NDB):
 ◼ Event Message Broker
◼ Logging Database
◼ Configuration Database (CDB)
◼ Admin Log Viewer (ALV2)
◼ acntdns
◼ EMI Bridge
◼ DNS-Server
◼ Certificate Authority (CA)
The following figure shows the Network Database Node (NDB) and its components.

2.3.5.2.1 Admin Log Viewer (ALV2)

The network management tool Admin Log Viewer (ALV2) is used for conveniently and efficiently
generating reports in order to analyze ACCESSNET-T IP mobile radio net- works. It provides several
standard reports and charts, offering detailed insight into the radio network and its condition and
capacity utilization.

Beside the provided reports, customized reports can be commissioned on a project-spe- cific basis.

The Admin Log Viewer (ALV2) backend is connected to the Logging Database (LogDB), which
provides all required data for report generation. The frontend is web-based and allows conveniently
generating and displaying reports.

All required information is presented in a web-based graphical user interface (GUI). It dis- plays the
information in multiple areas in an easy way to use.

The following figure shows an example report.

2.3.5.2.2 Centralized database - Logging Database (LogDB)

ACCESSNET-T IP features a central logging function, storing different types of information (e.g. status
changes of terminals, call activities, SDS transmissions, alarm events, operator activities/audit trailing)
and providing them for analysis.

All logged information is distributed via the Event Monitoring Interface to the central Event Message
Broker and stored centrally in the Logging Database in a structured manner.

The database structure is designed in a way that it is possible to store all types of information
mentioned above effectively.

The design of the data storage (DB) and data analytics modules is highly scalable, can serve highest
availability demands and can process a high number of data streams in parallel, both for archiving
data as well as analytics purpose. The data storage can be scaled to various network sizes, including
nationwide TETRA system installations. By using traditional redundancy setups, the system operator
benefits from a fault-tolerant nature of the data storage design. The data storage is not limited to
store just the TETRA- generated event logging and audit trailing messages but also data from any
network- attached sensor as a data source.

Data reports can be created by an NMS analytics module, e.g. for display in the ACCESSNET-T IP NMS
software suite. Thus, the network operator is informed about status changes in the TETRA network
and can react in a fast and efficient way. The Logging Database overall table structure relates to call
activities, site configurations / configuration changes, site status, activities of subscriber and
talkgroups, alarm status and alarm status changes, utilization of the TETRA Packet Data (PD) service,
messaging (Short Data Service, SDS), resource and capacity information as well as maintenance
activities (cf. audit trailing feature). Especially, information about the channel utilization can be
derived from the site status tables. The number and duration of calls can also be derived from the
tables related to call activities.
2.3.5.2.3 Logging Interface - Event Monitoring Interface (EMI)

Within the ACCESSNET-T IP TETRA radio system there may occur the following events:
◼ originated from activities of radio system users and operators or
◼ detected or caused by the components of the system infrastructure. Information on
all events is provided in form of event messages, centrally provided by theEvent Monitoring
Interface (EMI). Some event messages are monitored during system operation in near real-time
by connected applications and tools (EMI clients).
Examples of EMI clients are:
◼ Network Capacity Manager
◼ Network Manager
The Event Monitoring Interface (EMI) provides information about all kinds of events, activ- ities etc.
in an ACCESSNET-T IP TETRA radio system. To analyze the behaviour of the radionetwork, the EMI
clients (applications, services) receive messages from the EMI on certain topics automatically.
Monitoring information is collected and provided as a sequence of monitoring messages by the
Event Message Broker (EMB). All base stations and XGNs and their hardware and software
components are monitored and deliver information to the EMB. The EMB is the central message
broker for EMI messages for all applications and network management tools, which either publish
messages of a certain topic or subscribe to those messages.
Optionally, the EMI can be designed redundantly to increase reliability.
The TETRA infrastructure solution of Hytera Mobilfunk GmbH features an optional log- ginginterface
which does not only serve to provide real-time data to the system-internal logging processes and
databases, it also provides all that data to any 3rd party or cus- tomized network management
software application.
The benefits of using the ACCESSNET-T IP logging interface are:
◼ Future-proof: Customized NMS developments use latest IoT protocols
◼ Saves investments (CAPEX): Able to integrate with existing NMS software
◼ Maximum availability: Clustered software deployment of interface software
◼ Full security: Option to transfer encrypted logging data
The Event Monitoring Interface provides, among others, the real-time data about:
◼ Technical status data of all network nodes (includes alarm and event messages)
◼ Performance data (load-related data; e.g. air interface utilization)
◼ NMS audit trail data
◼ Call meta data (call-related data; might be used for external generation of CallDetail
Records [CDR]).
Hytera uses the state-of-the-art Message Queuing Telemetry Transport IP protocol (MQTT),which is
an open standard protocol (ISO/IEC). MQTT is defined as publish-sub- scribe protocol (message
pattern) on top of TCP/IP protocol layers. So, this interoperates with all standard TCP/IP transmission
networks and does not require any proprietary router or transmission line technology or products.
MQTT has become very common for telemetry applications and machine-to-machine (M2M)
communication. It may become a de facto standard in Internet-of-Things (IoT) environments. It can
be considered compact- bible to modern common sensor protocols.
The following figure shows the basic MQTT software architecture including central MQTT broker,
data publishing clients (e.g., sensor sending data) as well as subscribing clients to receive and
process data.

Figure 2-15 Basic MQTT software architecture

MQTT is used by all components of the ACCESSNET-T IP for event monitoring (EMI) as well as audit
trailing. All operative and maintenance events and the audit trailing messages will be pushed to the
Event Monitoring Interface broker component.
The number and platform type of storage systems is not limited with this software archi-tecture.
The following figure shows an example of a network using the MQTT software architecture.
 Figure 2-16 Example of a network using the MQTT software architecture

2.3.5.2.4 Certificate Authority (CA) server

Within ACCESSNET-T IP the security of services is ensured in order to provide reliable

communication while avoiding potential security risks. Certificates are required for the
communication security and are used for access control and encryption in ACCESSNET-T IP.
The certificate authority (CA) server is the trust center entity of the system. A full dynamic
certification procedure is to be used, operating on customer- and project-specific validity times
of the certificates.

2.3.5.2.5 Download repository

The download repository serves as the main software repository for the ACCESSNET-T IP
network.
2.3.5.3 NMS Hardware Specification

2.3.5.3.1 NMS Server Hardware and Specification

Hytera adopts high performance Lenovo Think System SR250 as network manager
server (network management system server).

Figure 2-17 NMS Server - Lenovo ThinkSystem SR250

Lenovo ThinkSystem SR250 main specification:

Item Specification
Model ThinkSystem SR250
CPU E-2134 4C/8 3.5GHz
Memory 2*16GB 2666MHz TruDDR4
HDD 3*900GB 10K 12Gbps SAS 2.5
RAID Controller RAID 530-8i SAS RAID Controller
Ethernet Port 2x1G Base-T Network Card
PowerSupply 2*450W
Optical Drives
DVD-RW（External ）

Operation System Windows Server 2019 Standard

Database software Windows SQL server 2016 Standard

Table 2-16 : Lenovo ThinkSystem SR250 Specification

2.3.5.3.2 NMS Client Hardware and Specification

Hytera will provide DELL OptiPlex 5090 Workstation as the NMS client.
 Figure 2-18 NMS Client- DELL OptiPlex 5090 Workstation

3 NMS Client Specification

Item Specification
Model DELL OptiPlex 5090
CPU Intel® Core™ i5-11500
Memory 8GB
HDD 1T
Ethernet Port 1*1Gb/s
Optical Drives DVD-RW
Accessory Mouse and keyboard
Operation System Windows 10 64bit
Monitor 21.5 inch
Table 2-17 : NMS Client Specification
2.4. Hytera TETRA Application Elements

2.4.1. TETRA Smartone Dispatch

The Hytera SmartOne is a digital dispatch system featuring plug-in design and providing
remote dispatch and management capabilities. It is applicable for industries and sectors
such as manufacture, energy, public security, transport, finance, water conservancy, and
social work. Via SmartOne, the urgent notice and command can be sent quickly and
effectively to the target, whose status is displayed in SmartOne.
Characterized by all IP structure, SmartOne offers you an advanced dispatching and
deployment platform with abundant functions, not only as conventional functions of
trunking dispatching system like group call, individual call and text message, but also
including dynamic group numbering assignment (DGNA), group patch, multi-party call,
visualized dispatching, multi-way voice call monitoring and terminal status monitoring,
etc.

2.4.1.1 System Architecture

As you can see from the system architecture example in the figure below, the SmartOne
Dispatch sytem mainly consists of server, client and gateway.

SmartOne SmartOne SmartOne

Client 1 Client 2 Client N

⋯⋯

Ethernet
Switch SmartOne
Server

Wired
Gateway

Tetra Trunking System

IPN
Server
BS

⋯
Mobile Portable Portable
Radio Radio 1 Radio N
⚫ SmartOne Server
The SmartOne Server provides the basic service, dispatch service, interworking service,
and media service for the SmartOne. Its main propose is to realize the exchange of
information, including media and control signaling information between networks. It is
also the essential part of the SmartOne Dispatch and connected to other wireless
communication systems via the gateway, for data and voice communications, so as to
provide the SmartOne client with integrated access services and information storage.

⚫ SmartOne Client

The PC client provides the most powerful and extensive functions, including voice
and multimedia dispatch, GPS location, and multimedia message. It is designed for
dispatchers who work at the command and dispatch center. The SmartOne Client is designed
with user-friendly interface, facilitating your operations through mouse or screen touching. Its
main interface is shown below.

No. Name Description

Allows you to do the following:

1 Title Bar  Mute or unmute the microphone and speaker.

 Check unread messages and ongoing calls.
No. Name Description
 Handle callback requests and emergency alarms.
 Use the keypad and the push-to-talk (PTT) key.
Ongoing Call
2 Displays information about ongoing calls.
Pane
Call History Displays recent calls
3
Pane Allows you to play back call recordings.
Provides the area where you perform various operations. A
4 Workspace maximum of six
workspaces are supported
Provides the following tabs:
Navigation
5  Contact
Pane
 Toolbox, which contains access to various functions.

⚫ Gateway
The gateway provides such functions as user access, protocol conversion, and routing
selection. The gateway includes wired gateway and wireless gateway.

✓ Wired Gateway
Wired gateway that can communicate with other systems through IP access.
Wired gateway can be deployed in a separate computer or share the same server
hardware with SmartOne server based on the quantity of system accesses and
concurrent calls.

To access the TETRA system via a wired gateway, the SmartOne Dispatch is connected
to the control server of the TETRA system via the wired access gateway.

SmartOne Wired access

platform gateway

Wired gateway is proposed in this project.

2.4.1.2 Service

2.4.1.3.1 Voice Services

Individual Call
Half-duplex Individual Call
Half-duplex individual call allows you to initiate or receive a call to/from a radio subscriber.
During the call, only one of you can speak while the other one can only listen at the same
time.

Full-duplex Individual Call

Full-duplex call allows you to initiate or receive a call to/from a radio subscriber. During the
call, both parties can simultaneously speak while listening.

Group Call
Group call allows you to initiate a half-duplex call to a group of radio subscribers. During the
call, only one can talk at a time. The group call can only be terminated by the call initiator or
another SmartOne client which is monitoring the call.

Broadcast Call
Broadcast call allows you to initiate a special group call to the specified radio subscribers.
During the call, only you can talk while others can only listen.

Emergency Call
Emergency call allows you to initiate an emergency call to a radio subscriber or a group once
the emergency happens. With the preemptive privilege, the emergency call can terminate any
ongoing normal call.

Priority call
Priority call allows you to make a call which can obtain the channel depending on the call
priority.

Ambience listening
Ambience listening allows you to listen to the ambient sound of an idle radio without the
knowledge of the radio user. It is conducive to enhancing the radio user’s safety.

Crosspatch
Crosspatch allows you to bring multiple groups into one temporary group for a special
communication purpose. The radio in this group can make or receive a call to/from this group.

Simul-select Call
Simul-select call allows you to create a new group which contains multiple online radios and
groups. When you can make a call to this group, the called parties can only listen.

Dispatcher Intercom
All online dispatchers can make a full-duplex call to each other by default.

Telephone Call
Telephone call allows you to make a call to the telephone user.

Call Display
During call, the call-related information including calling party ID, called party ID, talking party
ID, and call type is displayed on the dispatch client user interface.

2.4.1.3.2 Supplementary Service

Monitor
Monitor allows you to perform a real-time monitor on all voice calls and messages of the
designated radio or group. You can interrupt or override the call which is being monitored.

Dynamic Group Number Assignment

Dynamic group number assignment (DGNA) allows you to create and delete temporary
groups in the radio over air interface without re-programming the radio.

Override
Override allows you to forcibly terminate the ongoing call and release the channel resources.
Calls including half-duplex individual call, group call and full-duplex individual call can be
overridden.

Interrupt
Interrupt allows you to forcedly break into an active call involving the radio and start speaking.

Call Hold
This feature allows you to place the ongoing half-duplex individual call on hold and continue
with it later without terminating it.

Call Transferring
This feature allows you to transfer an ongoing half-duplex individual call to another terminal
user, dispatcher.

Override
Override allows you to forcibly terminate the ongoing call and release the channel resources.
Calls including half-duplex individual call, telephone call, group call and full-duplex individual
call can be overridden.
Interrupt
Interrupt allows you to forcedly break into an active call involving the radio and start speaking.

Local Record
This feature allows you to record the incoming all, outgoing call, and call monitored by the
dispatcher. The recordings voice and message information can be locally saved and replayed
as required.

2.4.1.3.3 Security Services

Stun
Stun allows you to remotely disable partial functions of a radio which is lost, so as to
guarantee communication security. The stunned radio cannot make the voice and data
service. However, its registration and GPS position services are still available to help you get
the radio back.

Revive
Revive allows you to re-activated the stunned radio for normal use.

Kill
Kill allows you to kill a radio. The killed radio will be incapable of all operations permanently,
unless it is reprogrammed by a qualified dealer.

End-to-end Encryption
This feature allows voice or data to be transferred from the sending party to the reception
party in the encrypted form. The voice or data will not be decrypted until they arrive at the
reception party, so as to ensure data safety during transfer. Both the sending party and
reception party encrypt and decrypt the voice or data by means of respective internal
encryption algorithm.

2.4.1.3.4 Message Service

Short message
Short message allows you to send messages to groups or individuals, or receive messages
from individuals. It includes text message and status message.

⚫ Text message is a text message including the template-based message.

⚫ Status message consists of text and status code. For such message, only the code will be
transferred so as to reduce channel occupation duration.
Online/Offline Presence

Online/offline presence allows you to view the status of the portable radio and mobile radio by
icons with different colors. Via these icons, you can easily know whether the radio is online or
not, facilitating dispatching work.

Emergency Alarm
When the radio subscriber makes the emergency alarm by pressing the appropriate button in
case of emergency, a predefined status message will be sent to the dispatch client.

Call back Message

If the radio subscriber cannot make a call to the dispatch client for some reason or misses
the call from the dispatch client, he/she can send a status message to the dispatch client.
After the dispatch client receives this message, it will directly call this radio subscriber.

2.4.1.3.5 AVL

GPS Polling
GPS polling allows you to view the radio location and other information including radio ID,
alias, and GPS time on the map. Such information on the map can be updated according to
the following modes.

⚫ Periodic GPS Polling: The GPS data of the radio on the map is automatically updated
according to the specified time interval.

⚫ Single GPS Polling: The GPS data of the designated radio on the map is displayed after
you poll it.
Real-time Track
Real-time track allows you to track the designated radio on the map in a real time way.

Map-based Individual Call

Map-based individual call allows you to make an individual call to the selected radio on the
map.

Map-based DGNA
This feature allows you to draw a circle or polygon on the map and select all radio subscribers
within this area at the same time. Then you can add these subscribers to a certain dynamic
group and call them simultaneously.
Geo-fencing Alarm
Geo-fencing alarms allow you to draw zones on the map and set triggering rules. When radio
users across the zone and specified triggering rules are met, geo-fencing alarms will be
triggered and reported to the client.

POI (Point of interest)

If you find some locations important or useful, such as a school or police station, you can add
them as points of interest (POIs) on the map. This helps you quickly and precisely locate
events or objectives around the POIs.

Track Playback
Track playback allows you to retrieve the radio user’s moving track and replay it in
accordance with the radio ID and time period.

2.4.1.3.6 Management Service

Report Query
Report query allows you to easily query the call log and message log by multiple query
criterion. The query results will appear on the table. The call recording can be played back.
Log Management

Log View: This feature allows dispatcher to view the log involving the call, message,
emergency alarm and geo-fencing alarm.

Log Export: This feature allows dispatcher to export the queried log to a file with .csv
extension which can be opened with Excel.

Authority Management

The administrator can configure the authority for the dispatcher and license.

The dispatcher authorities include resetting the dispatcher password,

adding/deleting/modifying the contact and editing the predefined message. Different
dispatch client can be configured to manage different radio terminals.

The license is used to install and operate the dispatcher.

2.4.1.3 Reliability

SmartOne Dispatch takes some measures to ward off the potential risk and enhance
reliability.

2.4.1.4.1 System Reliability

Hot Standby
The SmartOne Server(business server) supports local and remote backup. The master
business server synchronizes with the standby business server in real time. When the master
business server becomes faulty, the standby one automatically takes over the services to
prevent service interruption. The faulty business server can perform fault detection and
initialization for self-recovery.

2.4.1.4.2 Hardware Reliability

The self-developed gateway undergoes rigorous test involving high/low temperature,

vibration, ESD and salt fog, to ensure the stability and reliability.

2.4.1.4.3 Software Reliability

Both the server application and gateway application can restart automatically in a short time if
they does not run properly.

➢ Fault-diagnosing based on logs

Logs are recorded to help diagnose faults and address problems.

➢ Automatic restart

If an error occurs during the software running, the software will automatically
restart for quick recovery.

➢ Retransmission upon packet loss

If Real-time Transport Protocol (RTP) data packet loss is detected, the lost
packet will be retransmitted.

➢ Task re-establishment

If a running task stops due to software errors, the task will be re-established
after the service is restarted.

➢ Data backup

Database data and multimedia messages can be backed up to prevent data

loss.
2.4.1.4 Standard Compliance

SmartOne Dispatch conforms to the following standards and protocols:

⚫ Telnet TCP/IP

⚫ RTP

⚫ SIP
⚫ HTTP

⚫ UDP

2.4.1.5 Dispatcher Hardware And Specification

◼ Dispatcher Server Hardware and Specification

Figure 2-19 Dispatcher Server - Dell PowerEdge R550

Hytera will provide DELL PowerEdge R550 as Dispatcher Server for this project.

DELL PowerEdge R550 Specification

Item Specification
Form factor/height 2U rack-mount
Processor Intel 4310 2.1Ghz 12C
Memory 16GB
Power supply 2*800W
Storage 5*600GB 10K SAS 2.5
Operating systems
Windows 2016 Server
supported
Limited warranty 3 Years warranty
Table 2-18 Dispatch Server Dell PowerEdge R550 Specification

◼ Dispatcher Client Hardware

Hytera will provide Dell OptiPlex 7090 as the dispatcher client.

 Figure 2-20 Dispatcher Client- Dell OptiPlex 7090

NMS Client Specification

Item Specification

Model Dell OptiPlex 7090

CPU Intel® Core™ i7-11700
Memory 16GB
HDD 1TB
Optical Drives DVD-RW
Power Consumption 260w
Operation System Windows 10 64bit
Monitor 21.5 inch
Table 2-19 : Dispatch Client Specification
2.4.2. Multimedia Recording & Playing System
In the public security industry, the Multimedia Recording and Playback System (MRPS) is an
indispensable subsystem which provides a reliable basis for tracing and reviewing all kinds of
events. Hytera MRPS is a high-performance system that can collect and store voice, short
message, and radio’s registration information in systems with different modes, frequency
bands, and architectures. Adopting the browser/server architecture, the MRPS provides data
query, playback, and statistical analysis, which facilitates restoring the entire process of
events and provides strong support for event analysis.
With flexible networking modes, the MRPS can be deployed in centralized or distributed mode
where backup can be enabled or disabled according to your requirements.

2.4.2.1 Typical Networking

The MRPS can connect to the TETRA system,DMR trunking system and Hytera HyTalk
system directly or through the Multimedia Unified Communication (MUC).
The following figures show typical networking of the MRPS.

Figure 2-21 Networking in Centralized Mode without Backup

 Figure 2-44 Networking in Centralized Mode with Backup

2.4.2.2 Functions

2.4.2.2.1 Recording

The MRPS can record all voice calls, and store messages and registration information of
different systems. What's more, the MRPS can also record end-to-end (E2E) voice calls,
which are encrypted by software and hardware.

2.4.2.2.2 Data Collection Policy

The MRPS collects data based on time or range to meet customers' tailored requirements.

⚫ Based on time

Anytime (default setting): The MRPS collects data at any time.

Specified time: The MRPS collects data only during specified time period (in hours) each day.

⚫ Based on range

Network (default setting): The MRPS collects data of the entire network.
Specified organization: The MRPS collects data of specified organizations.

2.4.2.2.3 Data Archiving and Restoration

Data Archiving
 The MRPS archives data to a specified path according to the preset interval (in days)
and time. The archived data will be retained for 1 to 999 days in the original path
before being deleted. By default, the archived up data will be retained for 180 days.

Data Restoration
Users can restore archived data to the local disk for further processing, such as
playing back recordings.

2.4.2.2.4 Query and Playback

Adopting the browser/server architecture, the MRPS provides data query, playback, and
statistical ana- lysis. Users can query data based on various criteria, such as the MRPS
ID, caller, or call type. After searching for wanted data, users can play back audio call
recordings, download multimedia messages, and so on.

2.4.2.2.5 Log Management

The system records all user activities, including login, logout, and other operations.
Users can query and analyze logs to locate and diagnose arisen problems, such as
illegal login.

2.4.2.2.6 System Maintenance

Performance and Status

The system can monitor servers' performance, such as the CPU, memory, and disk
usage, as well as connection status of servers. Users can view the real-time
performance and status on the web-based client.

Alarm

When detecting faults, the system generates alarms helping users handle faults. Alarms
can be divided into the following types:

⚫ Major: indicates that a service-affecting condition has developed and an urgent

correction action is required.

⚫ Minor: indicates that a condition affecting service stability has developed. It is

recommended to handle it immediately before any significant effects occur.

⚫ Warning: indicates a non-service-affecting condition has developed. It is

recommended to handle it to eliminate potential issues.
2.4.2.2.7 User Management

Users consist of the MRPS users and the third-party users. The users will be granted
with different per- missions for security reasons.

⚫ MRPS users: The users have permissions to operate the MRPS, such as configuring
the system, view- ing historical alarms, or managing organizations.

⚫ Third-party users: The users, who are granted with different system, interface, and
data permissions, are used by the third-party systems to access the MRPS.

➢ System permission: indicates permissions of the MRPS web-based client, such

as querying messages playing back call recordings.
➢ Interface permission: indicates permissions of the interfaces authorized to the
users, including querying call records, Visual Command System (VCS)
interface, or CTHS interface.
➢ Data permission: indicates the range of data that users can query. The data
range is determined by time and organization.

• By time: Users can query data only within specified time period, which
ranges from 1 to 36 months. By default, users can query data within any
time period.

• By organization: Users can query data of only specified organizations. By

default, users can query data of all organizations.

2.4.2.2.8 High Reliability

Each MRPS service features high reliability. If the master MRPS service becomes faulty,
the slave MRPS service takes over all services to ensure continuity.

The collection server of the MRPS works in master/slave mode. In normal conditions, only
the master col- lection server works. If the master collection server encounters an error, the
slave collection server becomes the master one and takes over all services.

The recording server, RTP server, and replay server of the MRPS work in load balancing
mode. In normal conditions, all servers work properly. If one server encounters an error,
services processed by the server are distributed to other servers that work properly.

2.4.2.2.9 License Control

Users' permissions to use the MRPS can be controlled by the license from the following
aspects:

⚫ Time
 ⚫ PC

⚫ Super dog

⚫ Number of systems that can access the MRPS

⚫ Number of concurrent voice calls

⚫ Number of concurrent video calls

⚫ Number of short messages

⚫ Number of pieces of registration information

⚫ Number of clients

⚫ Function

2.4.2.3 Recorder Hardware And Specification

◼ MRPS Server

Hytera will provide Lenovo ThinkSystem SR650 as MRPS Server for this project.

Figure 2-45 MRPS Server –Lenovo ThinkSystem SR650

Lenovo ThinkSystem SR650 Specification

Item Specification
Form factor/height 2U rack-mount
Processor Xeon4208 8C 2.1GHz
Memory 16GB
Power supply 2*750W
Storage 5*600GB 10K SAS 2.5
Operating systems
Windows 2016 Server
supported
Limited warranty 3 Years warranty
Table 2-20 : MRPS Hardware Specification
2.4.3. MCS-TETRA convergent solution(For Future

Expansion)
The Hytera HyTalk MC solution is a broadband-narrowband convergent communication
solution featuring wide coverage and high reliability. With this solution, customers can
build an independent P-PoC system or build a MCS system based on the existing TETRA
system for coverage expansion. Compared with traditional narrowband solutions, this
solution delivers richer services and broader coverage.
The Hytera HyTalk MC solution integrates a series of components, including the MCS
system, DMR system, trunking radios, Evolved Network Management System (EMS),
SmartOne Dispatch, Smart Mobile Device Management (MDM), Unified Location
Provider (ULP), and Multimedia Recording and Playing System (MRPS). Interconnecting
all of the components, this solution provides diversified services, such as instant voice
and multi-media communication, unified dispatch and management, and voice and video
recording services.

2.4.2.4 Solution Architecture

⚫ L1 application layer: SmartOne Dispatch, EMS, MRPS, ULP, and MDM.

⚫ L2 platform layer: MCS system, TETRA system, access network, and security devices.
⚫ L3 terminal layer: Broadband terminals, multi-mode advanced radios, Android phones, and
narrowband terminals.
The application layer, including multiple subsystems, realizes unified dispatch and
management over narrowband and broadband networks. The platform layer
interconnects the Hytera HyTalk MC system with the DMR system. The terminal layer
consists of PoC radios, narrowband radios, and multi-mode advanced radios for both
broadband and narrowband communications. The three-layer architecture provides
customers with a broadband-narrowband convergent solution that can meet actual
needs.
To help upgrade to the trendy broadband trunking system and protecting the investment,
Hytera offers MCS solution that deep integrated to HMF tetra, so that customer could
enjoy communicating across systems, including all the services stated in chapter 2.4.2.5
2.4.2.5 Implement Service of Hytera MCS & Hytera TETRA

2.4.2.5.1 Voice Services

Full-duplex Voice Private Call

It is a full-duplex voice call between MCS and TETRA terminal users. After the call is
established, both parties can simultaneously talk while listening.

Half-duplex Voice Private Call

It is a half-duplex voice call between MCS and TETRA terminal users. After the call is
established, only one party can talk at a time.

Voice Group Call

It is a half-duplex voice call between one user and other users in a group. After the MCS
group is associated with the TETRA group, when an MCS terminal user initiates a call to the
MCS group, the associated TETRA group members can also join the call, and vice versa.

Emergency Private Call

It allows a MCS terminal user to initiate a voice call to a TETRA terminal user to seek help in
case of emergencies, and vice versa.
It has the highest priority and can interrupt other low priority calls.

Emergency Group Call

It allows a MCS or TETRA terminal user to initiate a voice call to a preset group to seek help
in case of emergencies.
It has the highest priority and can interrupt other low priority calls.

ID Display
The MCS and TETRA terminals display the identity of the caller or callee in a voice call.

2.4.2.5.2 Data Services

One-to-One SDS
It is text-based communication between MCS and TETRA terminal users.

One-to-multi SDS
It is a one-to-many messaging service that allows one MCS or TETRA terminal user to send a
message to other users in the same group and associated group.

Message Sender ID Display

The MCS and TETRA terminals display the identity of the message sender.
2.5. Hytera TETRA Radio

2.5.1. Hytera TETRA Portable Radio PT580H Plus

PT580H Plus is available in basic, advanced, professional, and anti-tamper versions from
which you can select as per your requirements. It uses unique noise-cancelling
technology. It complies with IP68 protection against water and dust. Besides, its standby
time is more than 22 hours.

Highlights

Figure 2-47 Hytera TETRA Portable Radio PT580H Plus

 Reliable Through Design

PT580H Plus is designed to comply with TETRA ETSI Standard, MIL-STD- 810G, IP68
Dust &Water Protection and Hytera ALT Test simulating over years’ usage. These tests
ensure PT580H Plus will stand up to the toughest conditions and environment.

 High RF output power

PT580H Plus gets a RF output power up to 3W; effectively enlarges signal coverage.

 Exceptional Audio

New added noise canceller chip brings PT580H Plus unprecedented clear audio quality.
Voice can be broadcasted clearly even in very noisy environment to assure the key
message received accurately.

 Comprehensive safety protection

Tamper proof protection makes PT580H Plus more secure. All the key data which stored
in PT580H Plus avoid the leak by malicious terminal damage.
 Multi-satellite location service

Multi-satellite system location service let PT580H Plus can be used globally. PT580H
Plus support GPS, Glonass and Beidou location.

Specification
380-430MHZ
Frequency Bands 405-475MHZ
General Specifications

806-870MHZ
Dimensions (HxWxD) mm 127.5 × 55 × 36.5mm

Weight 374g（with battery and antenna）

Battery PT580H Plus: Li-lon 1800mAh and 2500mAh

>20 Hours (1800mAh)
Battery Life (5-5-90)
>27 Hours (2500mAh)
Operating Voltage 7.4V

LCD Color Display 1.8inch，160*128pixels，262144colors

Talk Group-TMO 6000

Talk Group-DMO 4000
User Interface

Telephone book 2000

Inbox 400
Outbox 50
Drafts 50
Scan Lists-TMO 200
Scan Lists-DMO 50
State Message 200
RF Channel Bandwidth 25KHz
RF Power Output 3W (1.8W For 806-870MHz)
RF Power Level Accuracy ±2dB
RF Specifications

Receiver Class ETSI EN 392-2/396-2 Class A and Class B

-116dBm(min); -118dBm(typical)
RX Static Sensitivity
800MHz: -115dBm (min); -116dBM (typical)

-107dBm(min); -109dBm(typical)
RX Dynamic Sensitivity
800MHz: -106dBm (min); -107dBM (typical)

Audio Power Output 2W (Peak 3W)

Sensitivity ≤-146dBm Acquisition Sensitivity
eci
fic
 ≤-165dBm Tracking Sensitivity
Accuracy <2.5m
Cold Start (Time to First Fix) <35s
Hot Start (Time to First Fix) <1s
Operating Temperature -30℃ ~ +60℃

Storage Temperature -40℃ ~ +85℃

Environmental

Humidity ETS 300 019 (95%)

Water and Dust Protection IEC60529，IP68

MIL-STD-810 F/G
Drop, Shock & Vibration ETS 300 019-1-7 5M3
GJB150A-2009

Table 2-22 : Hytera TETRA Portable Radio PT580 Plus Specification

2.5.2. Hytera TETRA Mobile Radio MT680 Plus

The large 260K color transflective TFT LCD enables you to access your desired
information with ease even under bright sunlight. User-friendly interface, keypad entry,
and powerful internal speaker (4W) can give you excellent operation and communication
experience. MT680 Plus allows you much installation flexibility. The front panel is IP67
compliant, capable of delivering you exceptional performance in various harsh conditions.
High transmit power (10W) enables you to reach a further team member.

Figure 2-51 Hytera TETRA Mobile Radio Terminal MT680 Plus

Highlights
 Rugged, Durable Design and Easy Operation

The MT680 Plus rugged design is enhanced with a large 260K colour TFT LCD enabling
the access of pertinent information with ease, even under bright sunlight. User-friendly
interface, keypad entry, and powerful (4W) speaker provides excellent operation and
communication experience.

 Exceptional Quality and Flexible Installation

The MT680 Plus flexibility allows for virtually any install location. You may integrate the
front panel with the main unit, or install it separately at a place where you can easily
access operation controls. The front panel is IP67 compliant, capable of delivering you
exceptional performance in extreme conditions.

 Versatile Services and Functions

The MT680 Plus supports all TETRA voice and data services. With its built-in GPS
feature, information about your location will no longer be an issue. Optional encryption
and recording features will bring you more benefits. The expansion port is another
advantage, enabling you to customize your radios feature.

 Instant and Seamless Communication

High transmit power (10W) enables you to reach team members long distances. The
MT680 Plus enables quick access to TETRA networks and roaming services. Additionally,
the MT680 Plus provides powerful interoperability with base stations and terminals of
different manufacturers.

Specification

MT680 Plus
380-430MHz
806-870MHz
Frequency Bands
405-475MHz
320-380MHz
Standard Dimensions(H×W×D) 70× 184 × 186 (mm×mm×mm)
Remote Mount RCP : 70 × 184 × 66 (mm×mm×mm)
Gel Spec

Dimensions(H×W×D) RT : 70 × 184 × 177.6 (mm×mm×mm)

Standard Weight 1853g
RCP : 395g
Remote Mount Weight
RT : 1655g
Rated Audio Power Output（
4W
Built-in SPK）
Operating Voltage 10.8-15.6(VDC)
LCD Display 2.8", 320×240 pixels, 260K colors
Int
 TalkGroup-TMO 6000
TalkGroup-DMO 4000
Phonebook 1000
Missed Call 20
Received Call 20
Dialed Call 20
Inbox 400
Outbox 50
Draft 50
Folder-TMO 200×200 (200 groups in each list)
Folder-DMO 50×200 (200 groups in each list)
RF Channel Bandwidth 25KHz
RF Power Output 10W
RF Power Accuracy ±2dB
RF Spec

RF Power Automatic Control 5dB Per Step, 5 Steps in total

Receiver Class ETSI EN 392-2/396-2 Class A & B
RX Static Sensitivity -116dBm (Typical: -118dBm)
RX Dynamic Sensitivity -106dBm (Typical:-108dBm)
Acquisition Sensitivity -146dBm(Typical)
RX Sensitivity
Tracking Sensitivity -165dBm(Typical)
GPS Spec

Location Accuracy ≤2.5m CEP

Cold Start (TTFF) <35S
Hot Start (TTFF) <1S
Operating Temperature Range -30℃ ~ +60℃

Storage Temperature Range -40℃ ~ +85℃

Environment Spec

Humidity ETS 300 019 (95%)

IEC60529
Water and Dust Protection
IP54/IP67(Remote Control Panel Only)
MIL-STD-810 F/G
Drop\Shock\Vibration ETS 300 019-1-5 5M3
GJB150A

Table 2-26 : Hytera TETRA Mobile Radio Terminal MT680 Plus Specification
2.6. Planning Software
The design of radio access network was done with the program Atoll which is developed
by Forsk. The software is professional and credible tool in the PMR industry and it is
designed to set up cellular mobile radio network. The software includes sophisticated
functions, ranging from the definition of transceiver locations, displaying coverage of
transmitters, logistics planning to frequency allocation, calculation of interferences and
the display of measurement data.

Atoll uniquely combines architectural and functional features that provide operators with a
powerful, scalable and flexible framework for streamlining their network design and
optimization processes.

2.7. Assumptions For Planning

➢ Portable radio receiver antenna has a height of 1.5 m and 0dBi gain.

➢ Mobile radio receiver with an antenna 2.5 meters from the ground.

➢ Frequency range is 400 MHz.

➢ BS antenna type: Omni-directional antenna with gain 8.1dbi

➢ The planning is based on the link budget and transmitter power detailed in link
budgets tables and site list

➢ Outdoor coverage tower heights are based on the real situation, it is shown in the
table as below

2.8. Maps
To design the radio access network digital database with following contents were used
for planning:

• A resolution of 50m Digital Terrain Model.

• Projection: UTM 50N/WGS84 .

Calculations were carried out without clutter information.

2.9. Antenna Pattern

Simulation assumed the base station antenna model was SC346-HT2LDF(D00)

Antenna gain is 8.1dBi and it is an Omni antenn.

Its pattern in horizontal and vertical used in simulation are shown as below:
The SC346 series of heavy duty, omni-directional antenna that cover the 410-430 MHz
frequency range, designed with 8.1 dBi gain.
2.10. Propagation Model
To predict the radio coverage, the Okumura-Hata propagation model was used. It is an
analytical model and calculates the diffraction losses in path-profile, which includes
topographical and morphographical data (terrain height and land usage). This model
realizes the effects of diffraction, reflection and scattering caused by city structures. This
model also has two more varieties for transmission in Suburban Areas and Open Areas.

To identify the prediction error and the standard deviation, the prediction results are
validated. Therefore, data from different measurement campaigns are collected and
analysed. Measurements have been carried out in different regions of the world.

2.11. Coverage Predication

The following diagrams show the coverage prediction map for ground base station by
special network planning software based on necessary parameter including frequency
band, base station site location , base station RF power, antenna tower height and
antenna gain, etc. Different color block means signal coverage quality.

The following picitures display sample coverage under professional simulation software
with regard to specific cities. Acccording to the simulation, we will be able to know the
exact range that the wileless signal can propogate in those cities.

Even though there are numermous poll boxes in the iland of Male and its adjacent iland
of Hulhule Male, two TETRA base stations can guarantee a good coverage to its
neighboring areas. For example, the boats around the shore can also have a very good
radio sigal if they are moving inside the green circles. The yellow areas mean that the
radio sigal is still ok and the communication is still provdied but the quality is not that
good.

Besides the two base stions will be deployed in the capital island, the core network will
aslo be placed in the area so that the transmission link and power supply can be provided
with the highest level. To make sure the whole network will work for better reliablity and
stability, two switching centers are supposed to have bake up. Actually, for better
redundancy, the back up IPN node could also be deployed in some site far away from the
capital island in order to have higher performance of disaster recovery, only if the
transmission link of IP packet is available.
3. Transmission Link Bandwidth Requirement
In the following chapters, the requirements on the transport network are differentiated by quality
requirements and requirements on the necessary data transfer rates. Via the transport network, the
network elements as well as applications such as dispatchers and voice recorders are connected.

The quality and availability of the IP transport network has a direct impact on the provided
services of ACCESSNET-T IP.

For microwave transmission network, Each Tetra base station need at least 384kbit/s transmission
bandwidth connect to control center, beside this, more several requirements of IP transmission
network as below.

3.1. Quality Requirements on the IP Transport Network

Communication using the IP-based transport network requires following technical
prerequisites to ensure the transmission of voice, signaling and payload.

The requirements on the IP-based transport network are described below:

➢ Prioritized transmission of IP packets according to DiffServ (Differentiated Service in

accordance with QoS (Quality of Service)).

➢ Transmission of IP packets – (payload and voice [Voice over IP, VoIP]) according to ITU-T
Rec. Y.1541, Class 0.

➢ The network elements support Internet Protocol version 4 (IPv4)

➢ IP connection via: For base stations DIB-R5 a switch or router on site

➢ The following network protocols are supported at the site the network elements:

▪ Spanning Tree Protocol (STP) in compliance with IEEE 802.1d or

▪ Rapid Spanning Tree Protocol (RSTP) in compliance with IEEE 802.1w

▪ Multiple Spanning Tree Protocol (MSTP) in compliance with IEEE 802.1Q The use of
MSTP is required only for connecting the base station to a layer-3 switch if redundant
Packet Data Gateways (PGW) are used on redundant transceiver modules or Base
Station Controller Units (BSCU).
Parameter Meaning Value
IP data transfer delay Describes the average transfer time of IP Max. 20 ms
(IPTD) packets.
between two nodes
IP packet delay variation Describes the delay variation of the transmission. Max. 10 ms
(IPDV) time when transmitting IP packets
 IP Packet Loss Ratio Describes the probability that Packets are not 1*10-3
(IPLR) transmitted within the network
IP Packet Error Ratio Describes the probability that received IP packets 1*10-4
(IPER) deviate from the transmitted IP packets

3.2. Requirements on Data Transfer Rate (PSK)

The data transfer rates required for the IP switched voice (Voice over IP, VoIP) in an
ACCESSNET-T IP, depend on the network constituents used and the variants (number of carriers,
networking). Each base station DIB-R5 always has one carrier with PSK modulation to form the
control channel ("Conventional Access").

Required data transfer rates

The data transfer rates mentioned must be made available for every network constituent upon
networking.

Connection of Variant No. of channels Data transfer rate Data transfer rate
/control channels Base station Base station with
without SCF SCF
Base stations (only 1 carrier 3/1 144 kbit/s 145 kbit/s
PSK carriers) 2 carrier 7/1 224 kbit/s 226 kbit/s

3 carriers 11 / 1 304 kbit/s 307 kbit/s

4 carriers 15 / 1 384 kbit/s 388 kbit/s

5 carriers 19 / 1 464 kbit/s 469 kbit/s

6 carriers 23/1 544 kbit/s 550 kbit/s
7 carriers 27/1 624 kbit/s 631 kbit/s
8 carriers 31/1 704 kbit/s 712 kbit/s
9 carriers 35/1 784 kbit/s 793 kbit/s
10 carriers 39/1 864 kbit/s 874 kbit/s
11 carriers 43/1 944 kbit/s 955 kbit/s
12 carriers 47/1 1024 kbit/s 1036 kbit/s
 Connection of Variant Number of channels/ Data rate Data rate Data rate
control channels BS without SCF BS with SCF BS with SCF
CDR msges. for LIP CDR msges. for
LIP

MQTT Connection --- --- 32 kbit/s per base 32 kbit/s per BS

broker to network station plus plus 1 kbit/s per
elements 1 kbit/s per carrier carrier plus 16
kbit/s per BS.
TETRA dispatchers 3 + A-CAPI ~200 kbit/s per --- ---
calculated with dispatcher client
128 kbit/s
TETRA TETRA- dependent on the 20 kbit/s per --- ---
voice recorders coded number of licensed channel
channels
POC apps dependent on the min. 20 kbit/s --- ---
number of POC apps per client

Telephone networks (TETRA- dependent on the 80 kbit/s per --- ---

coded to PCM/ G.711-coded number of channels channel

3.3. Requirements on VoIP Telephone Systems

For connectivity to VoIP telephone systems via an IP network using the available SIP (Session
Initiation Protocol) interface, the requirements for VoIP telephone systems must be met.

The requirements on VoIP telephone systems are detailed below:

➢ Support for the following VoIP protocols in accordance with RFC (Requests for Comments):

⚫ SIP (Session Initiation Protocol) for establishing a communication session, as per RFC
3261

⚫ SDP (Session Description Protocol) for controlling the voice connection, as per RFC 4566

⚫ RTP (Real Time Protocol) for transmitting voice data, as per RFC 3550

⚫ Coding in accordance with ITU standard G.711 μ-law or G.711 A-law for the
transmission of voice data

⚫ DTMF (Dual-tone multi-frequency) for the transmission of numeric characters in the

service channel, as per RFC 2833
➢ Number based addressing for the use of:

⚫ Call forwarding of common prefix numbers for the replication of private automatic.
 branch exchanges and Special number conversion
➢ Gateway registration requirements

⚫ Support for continuous connection verification through the use of a proxy number on the
SIP server (SIP registrar)

⚫ Alarm activation in the case of failed registration.