Main Categories

The present document defines the stage 3 specifications of the Supplementary Service Dynamic Group Number 
Assignment (SS-DGNA) for the Terrestrial Trunked Radio (TETRA). 
The SS-DGNA enables a user to dynamically define group identities and group related parameters to the TETRA 
system and to the subscribers in the system. These definitions are used to enable group call invocations to dynamically 
defined groups. The SS-DGNA specification defines the creation, modification, deletion and interrogation of group 
definitions in the Switching and Management Infrastructure (SwMI), in the Mobile Station (MS). 
The present document does not include the specification for access priority used for random access in uplink and call 
priority used by SwMI for resource allocation in a group call. Access priority and call priority can be specified and 
applied for groups using Supplementary Services Access Priority (SS-AP), Priority Call (SS-PC) and Pre-emptive 
Priority Call (SS-PPC). Thus, the definition procedure of these priorities is outside the scope of the present document. 
Man Machine Interface (MMI) and charging principles are also outside the scope of the present document. 
Supplementary service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of the service. 
Stage 1 describes the functional capabilities from the user's point of view. Stage 2 defines the functional behaviour in 
terms of functional entities and information flows. Stage 3 gives the precise description of the supplementary service 
from the implementation point of view. It defines the protocols for the service and the encoding rules for the 
information flows. It defines the processes for the functional entities and their behaviour. The described protocols and 
their behaviour apply for the SwMI and for the MS and can be applied over the Inter-System Interface (ISI) between 
TETRA systems.

The present document defines the Terrestrial Trunked Radio (TETRA) system supporting Voice plus Data (V+D). It 
specifies: 
• the interworking of individual calls between TETRA networks; 
• the supplementary services interaction with individual calls between TETRA networks. 
The TETRA V+D interworking - basic operation part defines the interworking between TETRA networks over the 
corresponding interface: the Inter-System Interface (ISI). It comprises the following sub-parts: 
• Transport layer independent General design [2]; 
• General Design, PSS1 over E.1 [i.10]; 
• General Design, SIP/IP [i.11]; 
• Transport layer independent Additional Network Feature - ISI Individual Call (ANF-ISIIC) (the present 
document); 
• Transport layer independent Additional Network Feature - ISI Group Call (ANF-ISIGC) [5]; 
• Transport layer independent Additional Network Feature - ISI Short Data service (ANF-ISISDS) [i.8]; 
• Transport layer independent Additional Network Feature - ISI Mobility Management (ANF-ISIMM) [6]; 
• Generic Speech Format Implementation [i.7]. 
The present document is the ANF-ISIIC sub-part. 
Like all other Additional Network Feature (ANF) specifications, those of ANF-ISIIC are produced in three stages, 
according to the method described in Recommendation ITU-T I.130 [i.4]. The present document contains the stage 1 
and 2 descriptions of ANF-ISIIC, and stage 3 description. The stage 1 description specifies the ANF as seen by its 
users, which are essentially the individual call control entities in both TETRA networks. The stage 2 description 
identifies the functional entities involved in the ANF and the information flows between them. And the stage 3 
description of ANF-ISIIC specifies its protocol. 
NOTE 1: According to Recommendation ITU-T I.130 [i.4], the stage 3 description of a bearer or tele-service 
addresses the network implementation aspects. Consequently, it comprises two steps: the specifications of 
all protocols at the various reference points involved in any of the service procedures (notably the service 
operation) are the first step of the stage 3 description, and the specifications of the functions of the 
corresponding network entities are its second step. 
NOTE 2: The SDL diagrams have not been provided since they can be derived from the specification of the 
functional entity actions in the stage 2 description. 
The present document applies to TETRA networks which support inter-TETRA individual calls. More specifically, it 
applies to their Circuit Mode Control Entities (CMCE), as defined in clause 14.2 of ETSI EN 300 392-2 [1], and to their 
ANF-ISIIC entities defined in the stage 2 description. 
The relation between the ANF-ISIIC and the transport layer protocol is described in the General Design documents [2], 

i.10] and [i.11]. 

The present document defines the general aspects of interworking at the Inter-System Interface (ISI) for Terrestrial 
Trunked Radio (TETRA) system supporting Voice plus Data (V+D). Those specify the general concepts which are the 
basis of the ISI operation between TETRA systems. It introduces the Additional Network Features (ANFs) used at 
the ISI, and specifies: 
• the general protocol mechanism upon which the definition of each ANF is based; and 
• the security related functions over the ISI. 
The specification of the general transport layer independent protocol mechanism applies to any TETRA Switching and 
Management Infrastructure (SwMI) which supports the ISI. The security requirements for the ISI only apply to SwMIs 
which support authentication or end-to-end encryption over the ISI. 
Besides the ISI general design, the present sub-part, interworking at the Inter-System Interface comprises the following 
other sub-parts: 
• General design, PSS1 over E.1 [3]; 
• General design, SIP/IP [4]; 
• Transport layer independent Additional Network Feature Individual Call (ANF-ISIIC) [5]; 
• Transport layer independent Additional Network Feature Group Call (ANF-ISIGC) [6]; 
• Transport layer independent Additional Network Feature Short Data Service (ANF-ISISDS) [7]; 
• Transport layer independent Additional Network Feature, Mobility Management (ANF-ISIMM) [8]; and 
• Generic Speech Format Implementation [9]