Abstract

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.

Status
Published
Publication Date
31-Mar-2006
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Apr-2006
Due Date
01-Apr-2006
Completion Date
01-Apr-2006

Buy Documents

Standard

SIST EN 300 392-12-22 V1.2.1:2006

English language (60 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 392-12-22 V1.2.1:2006 is the Slovenian adoption of ETSI EN 300 392-12-22 Version 1.2.1 for Terrestrial Trunked Radio (TETRA) Voice plus Data (V+D). It specifies the stage 3, implementation-level procedures for the Supplementary Service Dynamic Group Number Assignment (SS-DGNA), including how group definitions are created, modified, deleted and interrogated in the Switching and Management Infrastructure (SwMI) and the Mobile Station (MS). The document is aimed at implementers of TETRA network and terminal functions who need the protocol and encoding details for dynamic group handling.

What does SIST EN 300 392-12-22 V1.2.1:2006 specify?

SIST EN 300 392-12-22 V1.2.1:2006 specifies SS-DGNA for TETRA V+D at stage 3, which means the protocol behaviour, information coding and entity interactions needed to implement the service. It covers dynamic definition of group identities and group-related parameters so that group calls can be set up for groups that are created on demand.

The standard is organized into scope, references, definitions and abbreviations, functional model, service description, signalling protocol, and interworking considerations. It also has two informative annexes.

AnnexWhat it covers
Annex ABibliography
Annex BChange Requests

The scope also makes clear what is outside the document: access priority and call priority handling, Man-Machine Interface (MMI), and charging principles.

What are the key requirements of SIST EN 300 392-12-22 V1.2.1:2006?

SIST EN 300 392-12-22 V1.2.1:2006 defines the service from the implementation point of view. Clause 5 gives the service primitives at the TNSS-SAP boundary, and clause 6 gives the signalling protocol, coded elements, state handling and interworking rules.

  • The service purpose is dynamic group management. SS-DGNA lets a user define group identities and group-related parameters so the system can invoke group calls to those groups. In practice, this is the mechanism for creating operational groups without pre-programming every case in advance.

  • The service is split across three functional entities. FE1 is the affected user MS, FE2 is the SwMI, and FE3 is the authorized user MS. The mapping to the Circuit Mode Control Entity (CMCE) matters because implementers must place the supplementary service logic in the correct MS and network sub-entities.

  • Clause 5 defines the service primitives exchanged at the TNSS-SAP. For FE1, the main primitives are ASSIGN, DEASSIGN and interrogation-related primitives. For FE3, the main primitives are DEFINE, DELETE, INTERROGATE GROUP, INTERROGATE GROUP MEMBERS, MODIFY and INTERROGATE MS GROUPS. This tells an implementer what application-layer actions the MS and SwMI must support.

  • Clause 5.4 defines the service parameters that carry the meaning of each operation. These include affected user identities, group identity or identities, group identity attachment mode, class of usage, security related information, additional group information, mnemonic group name, and several result values. In practice, these parameters are what the implementation must encode, store and return when a group is assigned, modified or queried.

  • The standard allows the SwMI to allocate the group identity when it is not given. The DEFINE PDU can carry a given group identity, but the group identity may also be omitted so the SwMI assigns one. This matters when the network, not the user, controls numbering.

  • Assignment and deassignment handling is defined separately for the affected user and the authorized user. Clause 6.5 describes how FE1 and FE2 react to ASSIGN and DEASSIGN, including whether acknowledgements are requested and how attachment results are reported. For MS and network vendors, this is the core of interoperability.

  • The document defines result codes for each operation. It specifies outcomes for assignment, attachment, deassignment, definition, deletion, interrogation and modification, including cases such as security rejection, invalid group identity, insufficient information, or capacity exceeded. This is important for user interface logic, logging and troubleshooting.

  • No SS-DGNA timers are defined, but the document recommends waiting times for acknowledgements. The protocol section recommends at least 5 seconds for an operation involving only the current SwMI and at least 10 seconds when several SwMIs are involved. That affects timeout handling in applications and test tools.

What terms does SIST EN 300 392-12-22 V1.2.1:2006 define?

  • Affected user - the identified MS user to whom a group is assigned or from whom it is deassigned.
  • Authorized user - the user who can define, modify, delete and interrogate group information based on group numbers or affected user identities.
  • Call related SS-DGNA - group creation based on the participants of a referenced call, possibly plus given affected user identities.
  • Call unrelated SS-DGNA - group creation based only on given affected user identities.
  • Group Short Subscriber Identity (GSSI) - the short identity used to identify a group in the TETRA system.
  • Group TETRA Subscriber Identity (GTSI) - the group identity format based on TETRA subscriber identity structure.
  • Visitor's Group Short Subscriber Identity ((V)GSSI) - the group identity used in a visited context.
  • Switching and Management Infrastructure (SwMI) - the TETRA network infrastructure that controls switching and management functions.

Who uses SIST EN 300 392-12-22 V1.2.1:2006?

SIST EN 300 392-12-22 V1.2.1:2006 is used by TETRA network operators, SwMI vendors, MS manufacturers and system integrators that implement supplementary services. It is also relevant to test and conformance teams that need to verify group assignment, modification, deletion, interrogation and interworking behaviour. Anyone implementing group-call control in TETRA V+D needs these protocol details.

What changed in SIST EN 300 392-12-22 V1.2.1:2006 from the previous edition?

This publication follows ETS 300 392-12-22, first published in April 2000, and the history shows a later V1.2.0 publication before V1.2.1 in February 2004. Annex B records four change requests, including editorial corrections, clarification that Short Number Addressing is not applicable to SS-DGNA, a correction linked to DGNA deassignment rejection handling, and other update changes from the regime revision.

Which standards are used with SIST EN 300 392-12-22 V1.2.1:2006?

The references and companion parts provide the underlying TETRA model, air interface, security and supplementary-service framework.

  • ISO/IEC 8859-1 - provides the Latin-1 character set used for mnemonic group names.
  • ETSI ETS 300 392-11-22 - defines the stage 2 model and functional entities for SS-DGNA.
  • ETSI EN 300 392-2 - provides the air interface, protocol stack and attachment/detachment behaviour.
  • ETSI EN 300 392-1 - provides the general network design and TETRA identity structure.
  • ETSI EN 300 392-7 - provides security material referenced by SS-DGNA security-related information.
  • ETSI EN 300 392-9 - gives the general rules for supplementary services and PDU routing.
  • ETSI EN 300 392-3-5 - supports inter-system mobility management interworking.
  • ETSI EN 300 392-3-3 - supports inter-system group call interworking.

What does the SIST EN 300 392-12-22 V1.2.1:2006 document contain?

The document contains service primitive definitions, PDU layouts, field coding rules, state descriptions and signalling procedures for SS-DGNA. Clause 6 gives the detailed PDU descriptions for ASSIGN, DEASSIGN, DEFINE, DELETE, INTERROGATE GROUP, INTERROGATE GROUP MEMBERS, INTERROGATE MS GROUPS and MODIFY, along with their acknowledgement forms. It also codes key elements such as group identity attachment mode, class of usage, result values, security related information, mnemonic group name and SS-DGNA PDU type. The protocol state sections describe FE1, FE2, FE3 and FE2 in a visited SwMI, which is what implementers use to build interoperable network and terminal behaviour.

Buy Documents

Standard

SIST EN 300 392-12-22 V1.2.1:2006

English language (60 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 392-12-22 V1.2.1:2006 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary services stage 3; Sub-part 22: Dynamic Group Number Assignment (DGNA)". This standard covers: 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 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.

SIST EN 300 392-12-22 V1.2.1:2006 is classified under the following ICS (International Classification for Standards) categories: 33.070.10 - Terrestrial Trunked Radio (TETRA). The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 392-12-22 V1.2.1:2006 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-april-2006
3UL]HPQLVQRSRYQLUDGLR 7(75$ ±*RYRULQSRGDWNL 9' ±GHO'RSROQLOQH
VWRULWYHVWRSQMH±SRGGHO'LQDPLþQRGRGHOMHYDQMHVNXSLQVNLKãWHYLON '*1$
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary
services stage 3; Sub-part 22: Dynamic Group Number Assignment (DGNA)
Ta slovenski standard je istoveten z: EN 300 392-12-22 Version 1.2.1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 12: Supplementary services stage 3;
Sub-part 22: Dynamic Group Number Assignment (DGNA)

2 ETSI EN 300 392-12-22 V1.2.1 (2004-02)

Reference
REN/TETRA-03101
Keywords
data, radio, speech, stage 3, supplementary
services, TETRA, V+D
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2004.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.8
2 References.8
3 Definitions and abbreviations.9
3.1 Definitions.9
3.2 Abbreviations.9
4 Functional model.10
4.1 Functional entities.10
4.2 Mapping of functional entities to Circuit Mode Control Entities (CMCE) .10
4.3 Protocol structure and protocol stack .10
5 SS-DGNA service description.10
5.1 General.10
5.2 SS-DGNA services offered over the TNSS-SAP .11
5.3 SS-DGNA primitives.11
5.3.1 ASSIGN indication.12
5.3.2 ASSIGN response.12
5.3.3 DEASSIGN indication.12
5.3.4 DEASSIGN response.13
5.3.5 DEFINE indication.13
5.3.6 DEFINE request.14
5.3.7 DELETE indication.14
5.3.8 DELETE request.14
5.3.9 INTERROGATE GROUP request .15
5.3.10 INTERROGATE GROUP indication .15
5.3.11 INTERROGATE GROUP MEMBERS request .15
5.3.12 INTERROGATE GROUP MEMBERS indication.16
5.3.13 INTERROGATE MS GROUPS indication .16
5.3.14 INTERROGATE MS GROUPs response/confirm .16
5.3.15 INTERROGATE MS GROUPS request.17
5.3.16 MODIFY request.17
5.3.17 MODIFY indication.17
5.4 Primitive parameter descriptions.18
6 Signalling protocol for support of SS-DGNA .21
6.1 Operational requirements.21
6.1.1 Affected user MS.21
6.1.2 Group home SwMI .21
6.1.3 Home SwMI of the affected user .21
6.1.4 Affected user SwMI.21
6.1.5 Authorized user MS.22
6.1.6 Authorized user SwMI.22
6.2 PDU descriptions.22
6.2.1 General on PDU descriptions.22
6.2.2 ASSIGN.22
6.2.3 ASSIGN ACK.23
6.2.4 DEASSIGN.23
6.2.5 DEASSIGN ACK.24
6.2.6 DEFINE.25
6.2.7 DEFINE ACK.26
6.2.8 DELETE.27
6.2.9 DELETE ACK.27
6.2.10 INTERROGATE GROUP.28
6.2.11 INTERROGATE GROUP ACK.28
ETSI
4 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
6.2.12 INTERROGATE GROUP MEMBERS.29
6.2.13 INTERROGATE GROUP MEMBERS ACK .29
6.2.14 INTERROGATE MS GROUPS.30
6.2.15 INTERROGATE MS GROUPS ACK.30
6.2.16 MODIFY.31
6.2.17 MODIFY ACK.32
6.2.18 General DGNA not supported .32
6.2.19 Requested SS-DGNA action not supported .32
6.3 Element coding.33
6.3.1 Acknowledgement complete.33
6.3.2 Acknowledgement requested from affected user(s).33
6.3.3 Additional group information.33
6.3.4 Affected user extension .33
6.3.5 Affected user identity.34
6.3.6 Affected user identity range type.34
6.3.7 Affected user SSI.34
6.3.8 Assigned user identity range type .34
6.3.9 Call identifier.34
6.3.10 Call related DGNA creation.35
6.3.11 Class of usage .35
6.3.12 Deassigned user identity range type.35
6.3.13 Group assignment.36
6.3.14 Group assignment ack.36
6.3.15 Group deassignment.37
6.3.16 Group deassignment ack.37
6.3.17 Group extension.37
6.3.18 Group extension present .37
6.3.19 Group identity attachment mode.38
6.3.20 Group information.38
6.3.21 Group SSI.38
6.3.22 Group status.39
6.3.23 Interrogation type for group.39
6.3.24 Interrogation type for group members .39
6.3.25 Interrogation type for MS groups .40
6.3.26 Length of additional group information element .40
6.3.27 Length of security related information element.40
6.3.28 Mnemonic group name.41
6.3.29 Number of affected user identities.41
6.3.30 Number of groups.41
6.3.31 Number of groups in deassign ack.41
6.3.32 Number of groups in deassign request.42
6.3.33 Result of assignment.42
6.3.34 Result of attachment .42
6.3.35 Result of deassignment .43
6.3.36 Result of definition .43
6.3.37 Result of deletion.44
6.3.38 Result of interrogation .44
6.3.39 Result of modification.45
6.3.40 Result of MS group interrogation .45
6.3.41 Security related information .46
6.3.42 Set reference.46
6.3.43 SS-DGNA PDU type .46
6.3.44 Visitor Group Short Subscriber Identity (V)GSSI .47
6.4 SS-DGNA protocol states .47
6.4.1 Protocol states of FE1 .47
6.4.2 Protocol states of FE2 .47
6.4.3 Protocol states of FE3 .47
6.4.4 Protocol states of FE2 in visited SwMI .47
6.5 SS-DGNA signalling procedures .47
6.5.1 PDU addressing.47
6.5.2 Signalling procedures of FE1 (affected user).47
6.5.2.1 Assignment.47
ETSI
5 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
6.5.2.2 Deassignment.48
6.5.2.3 Interrogation of group parameters.49
6.5.2.4 Interrogation of MS groups by SwMI .49
6.5.3 Signalling procedures of FE2 (SwMI).49
6.5.3.1 General on procedures for FE2 .49
6.5.3.2 Definition.50
6.5.3.3 Deletion.50
6.5.3.4 Modification.51
6.5.3.5 Assignment.51
6.5.3.6 Deassignment.52
6.5.3.7 Interrogation of group information .52
6.5.3.8 Interrogation of group members.52
6.5.3.9 Interrogation of MS groups from affected user.53
6.5.3.10 Interrogation of MS groups request from authorized user .53
6.5.4 Signalling procedures of FE3.53
6.5.4.1 Definition.53
6.5.4.2 Modification.54
6.5.4.3 Deletion.54
6.5.4.4 Interrogation of group members.54
6.5.4.5 Interrogation of MS groups.55
6.5.4.6 Interrogation of group information .55
6.5.5 Signalling procedures of FE2 in a visited SwMI .55
6.6 Protocol timers.55
6.7 Inter-working considerations.55
6.7.1 Inter system interface.55
6.7.1.1 Basic requirements to ISI support .55
6.7.1.2 Assignment.56
6.7.1.3 Deassignment.56
6.7.1.4 Definition, deletion, modification.56
6.7.1.5 Interrogation.56
6.7.2 Gateways.57
Annex A (informative): Bibliography.58
Annex B (informative): Change Requests .59
History .60

ETSI
6 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Project Terrestrial Trunked Radio
(TETRA).
The present document is part 12 sub-part 22 of a multi-part deliverable covering the Voice plus Data (V+D), as
identified below:
EN 300 392-1: "General network design";
EN 300 392-2: "Air Interface (AI)";
EN 300 392-3: "Interworking at the Inter-System Interface (ISI)";
ETS 300 392-4: "Gateways basic operation";
EN 300 392-5: "Peripheral Equipment Interface (PEI)";
EN 300 392-7: "Security";
EN 300 392-9: "General requirements for supplementary services";
EN 300 392-10: "Supplementary services stage 1";
EN 300 392-11: "Supplementary services stage 2";
EN 300 392-12: "Supplementary services stage 3";
EN 300 392-12-1: "Call Identification (CI)";
ETS 300 392-12-2: "Call Report (CR)";
EN 300 392-12-3: "Talking Party Identification (TPI)";
EN 300 392-12-4: "Call Forwarding (CF)";
ETS 300 392-12-5: "List Search Call (LSC)";
EN 300 392-12-6: "Call Authorized by Dispatcher (CAD)";
ETS 300 392-12-7: "Short Number Addressing (SNA)";
EN 300 392-12-8: "Area Selection (AS)";
ETS 300 392-12-9: "Access Priority (AP)";
EN 300 392-12-10: "Priority Call (PC)";
ETS 300 392-12-11: "Call Waiting (CW)";
EN 300 392-12-12: "Call Hold (HOLD)";
ETSI
7 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
ETS 300 392-12-13: "Call Completion to Busy Subscriber (CCBS)";
EN 300 392-12-14: "Late Entry (LE)";
ETS 300 392-12-16: "Pre-emptive Priority Call (PPC)";
EN 300 392-12-17: "Include Call (IC)";
EN 300 392-12-18: "Barring of Outgoing Calls (BOC)";
EN 300 392-12-19: "Barring of Incoming Calls (BIC)";
ETS 300 392-12-20: "Discreet Listening (DL)";
EN 300 392-12-21: "Ambience Listening (AL)";
EN 300 392-12-22: "Dynamic Group Number Assignment (DGNA)";
ETS 300 392-12-23: "Call Completion on No Reply (CCNR)";
ETS 300 392-12-24: "Call Retention (CRT)";
ETS 300 392-13: "SDL model of the Air Interface (AI)";
ETS 300 392-14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
TS 100 392-15: "TETRA frequency bands, duplex spacings and channel numbering";
TS 100 392-16: "Network Performance Metrics";
TS 100 392-17: "TETRA V+D and DMO Release 1.1 specifications".

National transposition dates
Date of adoption of this EN: 6 February 2004
Date of latest announcement of this EN (doa): 31 May 2004
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 November 2004
Date of withdrawal of any conflicting National Standard (dow): 30 November 2004

ETSI
8 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
1 Scope
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.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ISO/IEC 8859-1: "Information technology - 8-bit single-byte coded graphic character sets -
Part 1: Latin alphabet No. 1".
[2] ETSI ETS 300 392-11-22: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 11: Supplementary services stage 2; Sub-part 22: Dynamic Group Number Assignment
(DGNA)".
[3] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[4] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[5] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[6] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 9: General requirements for supplementary services".
ETSI
9 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
[7] ETSI EN 300 392-3-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 5: Additional Network Feature
for Mobility Management (ANF-ISIMM)".
[8] ETSI EN 300 392-3-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 3: Additional Network Feature
Group Call (ANF-ISIGC)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
affected user: identified MS user to whom the group is assigned (added to) or deassigned (removed from)
NOTE: Affected user can also interrogate group information based on group numbers. Also SwMI can interrogate
group information from affected user
authorized user: user who is able to define, modify and delete a group and interrogate group information based on
group numbers/affected user identities
call related SS-DGNA: creation of a group whose members (affected users) are based on the participants of a
referenced call and possibly also based on given affected user identities
call unrelated SS-DGNA: creation of a group whose members (affected users) are solely based on given affected user
identities
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CC Call Control
CMCE Circuit Mode Control Entity
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
ISI Inter System Interface
ITSI Individual TETRA Subscriber Identity
PC Protocol Control
SS Supplementary Service
SSI Short Subscriber Identity
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SS-AP Access Priority
SS-DGNA Dynamic Group Number Assignment
SS-PC Priority Call
SS-PPC Pre-emptive Priority Call
SwMI Switching and Management Infrastructure
(V)GSSI Visitor's Group Short Subscriber Identity

ETSI
10 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
4 Functional model
4.1 Functional entities
The functional model for SS-DGNA consists of Functional Entities FE1 to FE3 as defined in ETS 300 392-11-22 [2]
clause 4.1. Refer to EN 300 392-9 [6] for Inter-System Interface model (ISI).
These functional entities can, for one action, be located in different TETRA SwMIs as defined in
ETS 300 392-11-22 [2] clause 4.
4.2 Mapping of functional entities to Circuit Mode Control
Entities (CMCE)
FEs, CCs and PCs correspond to sub-entities in the Circuit Mode Control Entity (CMCE) described in
EN 300 392-2 [3] according to the following definitions:
- FE1: Supplementary Service (SS) sub-entity in CMCE in affected user's MS;
- FE2: SS sub-entity in CMCE in SwMI;
- FE3: SS sub-entity in CMCE in authorized user's MS;
- CC: Call Control (CC) sub-entity in CMCE in SwMI or in MS;
- PC: Protocol Control (PC) sub-entity in CMCE in MS.
4.3 Protocol structure and protocol stack
The MS protocol stack is defined in EN 300 392-2 [3].
SS-DGNA PDUs shall be routed as specified in EN 300 392-9 [6], at the air interface in U/D-FACILITY PDUs and
using ANF-ISISS for conveying SS-DGNA PDUs over the ISI.
5 SS-DGNA service description
5.1 General
Clauses 5.2 to 5.4 describe SS-DGNA specific services offered by the CMCE at the supplementary services service
access point (TNSS-SAP) to application, or vice versa, of the TETRA Voice plus Data (V+D) layer 3 service boundary.
NOTE: As the present document only deals with the SS-DGNA all the service primitives has been shown without
a TNSS-DGNA-prefix e.g. the TNSS-DGNA-DEFINE request is shorten into a DEFINE request.
Refer EN 300 392-9 [6] for general information on supplementary services.
In this protocol model the application is considered to manage group information in the MS. The management
mechanisms and a detailed information exchange between MS protocol layers are outside the scope of the present
document.
ETSI
11 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
5.2 SS-DGNA services offered over the TNSS-SAP
The services offered to users of SS-DGNA are defined as service primitives containing service parameters. The service
primitives are defined in clause 5.3 and the parameter in the service primitives are defined in clause 5.4.
In addition to the defined service primitives a SwMI/MS may response by a supplementary service not supported or an
action not supported primitives as appropriate, refer EN 300 392-9 [6] and clauses 6.2.18 and 6.2.19.
NOTE: As the man-machine interface or user application are outside the scope of the present document service
primitives are used to define information exchange to and from the standardized part of the MS. Those
primitives may be only indirectly accessible.
5.3 SS-DGNA primitives
The SS-DGNA service primitives at the Affected user MS (FE1) TNSS-SAP are:
a) ASSIGN indication;
b) ASSING response;
c) DEASSIGN indication;
d) DEASSING response;
e) INTERROGATE GROUP request;
f) INTERROGATE GROUP indication;
g) INTERROGATE MS GROUPS indication;
h) INTERROGATE MS GROUPS response.
The SS-DGNA service primitives at the authorized user MS (FE3) TNSS-SAP are:
a) DEFINE request;
b) DEFINE indication;
c) DELETE request;
d) DELETE indication;
e) INTERROGATE GROUP request;
f) INTERROGATE GROUP indication;
g) INTERROGATE GROUP MEMBERS request;
h) INTERROGATE GROUP MEMBERS indication;
i) MODIFY request;
j) MODIFY indication;
k) INTERROGATE MS GROUPS request;
l) INTERROGATE MS GROUPS confirm.
The service primitives such as MODIFY request and MODIFY indication are related to each other by the group
identity, if available. There can be more than one indication primitive related to a single request primitive.
ETSI
12 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
5.3.1 ASSIGN indication
ASSIGN indication primitive shall be offered from FE1 to application over TNSS-SAP in order to assign group
identities and/or parameters related to the group to the database in the affected user's MS. The primitive shall contain
the SS-DGNA parameters listed in table 1.
Table 1: ASSIGN indication contents
Parameter Indication Remark
Group identity/identities M
Acknowledgement requested M
Group identity attachment mode O
Class of usage O
Mnemonic group name O
Security related information O
Additional group information O

5.3.2 ASSIGN response
ASSIGN response primitive shall be offered from application to FE1 over TNSS-SAP. The primitive shall be used to
acknowledge one or more group assignments made to affected user. The primitive shall contain the SS-DGNA
parameters listed in table 2. The primitive shall be used only, if the acknowledgement was requested in an ASSIGN
request.
The acknowledgement shall be valid for all given group identities in ASSIGN response and the application shall send
independent responses for each result of assignment value.
Table 2: ASSIGN response contents
Parameter Response Remark
Group identity/identities M
Result of assignment M See note
Result of attachment M See note
NOTE: The result may be different to each assigned group identity.

5.3.3 DEASSIGN indication
DEASSIGN indication primitive shall be offered from FE1 to application over TNSS-SAP. The primitive shall be used
to remove group assignments from the affected user. The primitive shall contain the SS-DGNA parameters listed in
table 3.
Table 3: DEASSIGN indication contents
Parameter Indication Remark
Group identity/identities O See note
Acknowledgement requested O
NOTE: All group identities of the MS are indicated by having no specific group
identity in the indication primitive.

ETSI
13 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
5.3.4 DEASSIGN response
DEASSIGN response primitive shall be offered from application to FE1 over TNSS-SAP. The primitive shall contain
the SS-DGNA parameters listed in table 4. The primitive shall be used to acknowledge requested group deassignments
and it is used only, if the acknowledgement was requested in the DEASSIGN request.
The Acknowledgement parameter shall be valid for all deassigned group identities given in DEASSIGN response and
the application shall send independent responses for each result of deassignment value.
Table 4: DEASSIGN response contents
Parameter Response Remark
Group identity/identities O See note 1
Result of deassignment M See note 2
NOTE 1: If MS deassigned all groups as a response to a "deassign all" then no
group number will be present.
NOTE 2: The result may be different for each group identity.

5.3.5 DEFINE indication
DEFINE indication primitive shall be offered from FE3 to application over TNSS-SAP. The primitive shall be used to
acknowledge a previously requested group definition. The primitive shall contain the SS-DGNA parameters listed in
table 5.
The DEFINE indication shall refer to the corresponding DEFINE request in a call related definition by the call
identifier. In the case of a call un-related definition the relationship is determined by the group identity, if used in the
DEFINE request. If there were no group identity in the DEFINE request, then the relationship is based on the sequence
of events, and the user should not request another definition without a group identity before receiving at least one
DEFINE indication to the previous request.
Table 5: DEFINE indication contents
Parameter Indication Remark
Call related or call unrelated M
Call identifier O see note
Group identity M
Acknowledgement complete M
Result of definition M
Affected user identity/identities O
NOTE: Shall be present in case of call related DGNA definition.

ETSI
14 ETSI EN 300 392-12-22 V1.2.1 (2004-02)
5.3.6 DEFINE request
DEFINE request primitive shall be offered from application to FE3 over TNSS-SAP. The primitive shall be used to
define one group to SwMI. The primitive can be used to define group related parameters and to assign groups to
affected users. The primitive shall contain the SS-DGNA parameters listed in table 6.
Table 6: DEFINE request contents
Parameter Request Remark
Call related or call unrelated M
Call identifier C See note 1
Group identity O See note 2
Set reference O
Mnemonic group name O
Security related information O
Additional group information O
Group identity attachment mode O See EN 300 392-2 [3],
clause 16
Class of usage O
Acknowledgement requested O
Affected user identity/identities O
NOTE 1: This parameter shall be present in case o
...