ETSI EN 300 392-9 V1.7.1 (2020-04)
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9: General requirements for supplementary services
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9: General requirements for supplementary services
REN/TCCE-03265
Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 9. del: Splošne zahteve za dopolnilne storitve
General Information
Standards Content (Sample)
Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
EUROPEAN STANDARD
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 9: General requirements for supplementary services
2 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
Reference
REN/TCCE-03265
Keywords
supplementary service, 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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols, abbreviations and Functional Entities (FE) . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
3.4 Functional Entities (FE) . 11
4 Supplementary service concepts . 11
4.1 Stage 1, 2 and 3 descriptions . 11
4.1.0 General Description . 11
4.1.1 Stage 1 description . 11
4.1.2 Stage 2 description . 11
4.1.3 Stage 3 description . 12
4.2 Concepts associated with supplementary services . 12
5 Service primitives . 12
5.1 Service primitive general description . 12
5.2 Notification service primitive . 13
6 Supplementary service invocation order . 13
7 Transfer of information related to supplementary service at the MS interface . 13
7.1 Methods of transportation . 13
7.2 Call related service information . 14
7.2.1 Facility information element general construction . 14
7.2.2 Notification indicator information element . 15
7.3 Call unrelated supplementary service information . 15
8 SS PDU contents . 16
8.0 SS PDU contents general . 16
8.1 SS type . 17
8.2 SS PDU type. 17
8.3 Repeated information element or set of information elements . 19
8.3.1 Range type information element . 19
8.3.2 Response to a SS PDU including repeated information elements controlled by a range type
information element . 20
8.3.3 Information element number of XX . 21
8.4 Encoding of other SS PDU ele ments . 22
8.4.0 Encoding of other SS PDU elements general . 22
8.4.1 User identity. 22
8.4.2 Character string . 24
8.4.3 External number . 25
8.4.4 External call restriction . 27
8.4.5 Activation, definition, and interrogation failure values . 27
8.4.6 Manufacturer identifier information element . 28
9 SS PDU routeing . 28
9.1 Actions at the SwMI receiving an SS PDU from a MS registered in this SwMI . 28
9.2 SS PDU sent by a SwMI to a MS . 29
9.2.0 SS PDU sent by a SwMI to a MS general. 29
9.2.1 SS PDU addressed individually by a SwMI to an MS . 29
ETSI
4 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
9.2.2 SS PDU originated by a SwMI using a group address . 30
9.2.3 Sending of SS PDU by the destination SwMI to MS . 30
9.3 SS PDU transport by ANF-ISISS . 30
10 ANF-ISISS . 31
10.1 Service model . 31
10.2 Service primitives . 31
10.3 Protocol . 32
10.3.1 Protocol general . 32
10.3.2 Possible groupings of ISI SS PDUs and of invoked ANF-ISISSs . 34
10.3.3 Void . 34
11 Exceptional cases . 34
11.1 ISI exceptional cases . 34
11.1.0 General . 34
11.1.1 Case a) . 35
11.1.1.1 Call unrelated ANF-ISISS PDU . 35
11.1.1.2 Call related ANF-ISISS PDU . 35
11.1.2 Case b) . 35
11.1.3 Case c) . 36
11.1.3.1 Case c) General . 36
11.1.4 Case d) . 36
11.1.4.0 Case d) general . 36
11.1.4.1 Cases d.1) and d.2) . 36
11.1.4.2 Case d.3) . 37
11.2 Exceptional cases at the air interface . 37
11.2.1 No ISI involved . 37
11.2.2 ISI involved . 38
12 Generic specification of activation/deactivation, definition and interrogation operations . 38
12.1 Stage 2 description . 38
12.2 Stage 3 description . 39
13 Authentication issues . 39
13.1 Authentication requirements for TETRA supplementary services . 39
13.2 The use of security class to meet authentication requirements for TETRA supplementary services . 40
13.2.0 General . 40
13.2.1 Class 1 . 40
13.2.2 Class 2 . 40
13.2.3 Class 3 . 40
13.2.4 Impact of ISI . 40
13.2.5 Security of data within a SwMI . 40
Annex A (informative): Definition of the ISI operation . 41
Annex B: Void . 42
Annex C: Void . 43
Annex D (informative): Change requests . 44
Annex E: Void . 45
History . 46
ETSI
5 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This draft European Standard (EN) has been produced by ETSI Technical Committee TETRA and Critical
Communications Evolution (TCCE), and is now submitted for the combined Public Enquiry and Vote phase of the
ETSI standards EN Approval Procedure.
The present document is part 9 of a multi-part deliverable covering the Terrestrial Trunked Radio (TETRA); Voice plus
Data (V+D) and Direct Mode Operation (DMO), as identified below:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 3: "Interworking at the Inter-System Interface (ISI)":
Part 4: "Gateways basic operation";
Part 5: "Peripheral Equipment Interface (PEI)";
Part 7: "Security";
Part 9: "General requirements for supplementary services";
Part 10: "Supplementary services stage 1";
Part 11: "Supplementary services stage 2";
Part 12: "Supplementary services stage 3";
Part 13: "SDL model of the Air Interface (AI)";
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 15: "TETRA frequency bands, duplex spacings and channel numbering";
Part 16: "Network Performance Metrics";
Part 17: "TETRA V+D and DMO specifications";
Part 18: "Air interface optimized applications";
Part 19: "Interworking between TETRA and Broadband systems".
ETSI
6 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
NOTE 1: Part 3, sub-parts 6 and 7 (Speech format implementation), part 4, sub-part 3 (Data networks gateway),
part 10, sub-part 15 (Transfer of control), part 13 (SDL) and part 14 (PICS) of this multi-part deliverable
are in status "historical" and are not maintained.
NOTE 2: Some parts are also published as Technical Specifications such as ETSI TS 100 392-2 and those may be
the latest version of the document.
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
7 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
1 Scope
The present document is applicable to any TETRA terminal equipment (Mobile Station (MS)) and to any TETRA
network (Switching and Management Infrastructure (SwMI)) which support at least one TETRA Supplementary
Service (SS). In addition, its routeing requirements of supplementary service information are applicable to any TETRA
network with a Voice plus Data (V+D) Inter-System Interface (ISI) to another TETRA network which supports at least
one TETRA SS.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETS EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[2] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[3] ETSI EN 300 392-3-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 9: Transport layer independent,
General design".
[4] Void.
[5] Void.
[6] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[7] ETSI EN 300 392-10-6: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 10: Supplementary services stage 1; Sub-part 6: Call Authorized by Dispatcher (CAD)".
[8] ETSI EN/ETS 300 392-11 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 11: Supplementary services stage 2".
[9] ETSI EN/ETS 300 392-12 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 12: Supplementary services stage 3".
[10] ISO/IEC 11571 (1998): " Information technology -- Telecommunications and information
exchange between systems -- Private Integrated Services Networks -- Addressing".
[11] Void.
[12] Void.
ETSI
8 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
[13] Recommendation ITU-T I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[14] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
[15] Recommendation ITU-T X.121: "International numbering plan for public data networks".
[16] Void.
[17] Void.
[18] Void.
[19] Void.
[20] ETSI ETS 300 392-12-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 12: Supplementary services stage 3; Sub-part 7: Short Number Addressing (SNA)".
[21] ISO/IEC 10646: "Information technology -- Universal Coded Character Set (UCS)".
[22] ETSI TS 100 392-18-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and Direct
Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 3: Direct mode
Over The Air Management protocol (DOTAM)".
[23] ETSI EN 300 392-3-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 10: General design, PSS1
over E.1".
[24] ETSI EN 300 392-3-11: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 11: General design, SIP/IP".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETSI EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Designers'
guide; Part 5: Guidance on Numbering and addressing".
3 Definition of terms, symbols, abbreviations and
Functional Entities (FE)
3.1 Terms
For the purposes of the present document, the terms given in ETSI EN 300 392-2 [2] and the following apply:
affected user: user who is subject to the operation
affected user SwMI: SwMI where the affected user is currently registered
ETSI
9 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
authorized user: user who is responsible for the definition, activation and deactivation of the service
NOTE: The authorized user may also interrogate the service. Affected user and served user may also be
authorized user as defined in each supplementary service.
authorized user SwMI: SwMI where the authorized user is currently registered
call related service: service requested from call set-up initiation until call disconnection and related to that call
NOTE: The call-related service can also be valid a certain short time after disconnection but before next call
set-up is initiated.
call unrelated service: service either requested outside a call or inside a call but not referring to that call
ISI Mediation Function: entity which provides the services that are not supported by the transport layer protocol to
different ANF-ISI entities
served user: user for whom the supplementary service is invoked
served user SwMI: SwMI where the served user is currently registered
user: entity using the services of a telecommunications network via an externally accessible service access point
NOTE: A user may be a person or an application process.
user application: application process which acts as a user
NOTE: See definition of user.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
AI Air Interface
ANF Additional Network Feature
ANF-ISIGC Additional Network Feature - Inter-System Interface Group Call
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
ANF-ISISS Additional Network Feature - Inter-System Interface Supplementary Service
APDU Application Packet Data Unit
APP APProved
CC PDU Call Control Protocol Data Unit
DMO Direct Mode Operation
DOTAM Direct mode Over The Air Management protocol
EPT ETSI Project TETRA
ETS European Telecommunication Standard
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
IP Internet Protocol
ISI SS Inter System Interface Supplementation Service
ISI Inter-System Interface
ISISS Inter-System Interface Supplementary Service
ISSI Individual Short Subscriber Identity
ITSI Individual TETRA Subscriber Identity
ITU International Telecommunication Union
MAC Media Access Control
MCC Mobile Country Code
MLE Mobile Link Entity
ETSI
10 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
MNC Mobile Network Code
MNI Mobile Network Identity
MS Mobile Station
MS-ISDN Mobile Station ISDN number
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PISN Private Integrated Services Network
PSS1 Private Signalling System no. 1
PSTN Public Services Telephone Network
SAP Service Access Point
SDL (Functional) Specification and Description Language
SIP Session Initiation Protocol
SS PDU Supplementary Service Protocol Data Unit
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SSI Short Subscriber Identity
SS-PDU Supplementary Service PDU
SwMI Switching and Management Infrastructure
TNCC-SAP TETRA Network layer Call Control - Service Access Point
TNSS TETRA Network layer Supplementary Service
TNSS-SAP TETRA Network layer Supplementary Service - Service Access Point
TSI TETRA Subscriber Identity
UCS Universal Multiple-Octet Coded Character Set, also known as Universal Character Set
UCS-2 Universal Character Set coded in 2 octets
UTF-16BE Unicode Transformation Format serialized as two bytes in Big-Endian format
V+D Voice plus Data
WG3 TC TETRA Working Group 3
XX generic name of an information element
Supplementary Service abbreviations
For the purposes of the present document, the following abbreviations also apply:
NOTE 1: Supplementary service abbreviations are also used without "SS-" preamble e.g. "SS-AL" and "AL" are
used as appropriate.
NOTE 2: The supplementary services list contains also abbreviations that are not used in the present document.
SS-AL Ambience Listening
SS-AP Access Priority
SS-AS Area Selection
SS-BIC Barring of Incoming Calls
SS-BOC Barring of Outgoing Calls
SS-CAD Call Authorized by Dispatcher
SS-CCBS Call Completion on Busy Subscriber
SS-CCNR Call Completion on No Reply
SS-CF Call Forwarding
SS-CFB Call Forwarding on Busy
SS-CFNR Call Forwarding on No Reply (generic for both CFNRy and CFNRc)
SS-CFNRc Call Forwarding on Mobile Subscriber Not Reachable
SS-CFNRy Call Forwarding on No Reply
SS-CFU Call Forwarding Unconditional
SS-CI Call Identification
SS-CLIP Calling Line Identification Presentation
SS-CLIR Calling Line Identification Restriction
SS-COLP COnnected Line identification Presentation
SS-COLR COnnected Line identification Restriction
SS-CR Call Report
SS-CRT Call Retention
SS-CW Call Waiting
SS-DGNA Dynamic Group Number Assignment
ETSI
11 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
SS-DL Discreet Listening
SS-HOLD call HOLD
SS-IC Include Call
SS-LE Late Entry
SS-LSC List Search Call
SS-PC Priority Call
SS-PPC Pre-emptive Priority Call
SS-SNA Short Number Addressing
SS-TPI Talking Party Identification
3.4 Functional Entities (FE)
The functional model for each supplementary service is comprised of a number of FEs. The FEs below should always
have the following definitions:
• FE1 served user's service agent;
• FE2 SwMI service control functional entity;
• FE3 authorized user's service agent;
• FE5 service agent of the user affected by service operation;
• FE6 service agent of second listening party;
• FE7 service agent of dispatcher (in the case of SS-CAD) or of monitoring user (in the case of SS-DL);
• FE8 service agent of user removed from a call during a pre-emptive priority call;
• FE9 service agent of user informed that another user has been removed from a call during a pre-emptive
priority call;
• FE10 service agent of user affected by management functions.
FE2, the SwMI functional entity, may be split into secondary FEs when needed for a given supplementary service.
These FEs are called FE2x in the corresponding stage 2 description (in the related ETSI EN/ETS 300 392-11 [8]).
4 Supplementary service concepts
4.1 Stage 1, 2 and 3 descriptions
4.1.0 General Description
Supplementary service descriptions are covered in 3 stages according to the method described in Recommendation
ITU-T I.130 [13], each stage in a separate document. The contents of each stage description are described in the
following clauses.
4.1.1 Stage 1 description
This stage is the overall service description from the user viewpoint and also details the interaction of the service with
other supplementary services.
4.1.2 Stage 2 description
Stage 2 identifies the functional capabilities and the information flows needed to support the supplementary service as
specified in its stage 1 description. It defines the FEs, the information flow between these entities, the FE actions and
the allocation of FEs to physical locations.
ETSI
12 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
4.1.3 Stage 3 description
The stage 3 description specifies the signalling protocols needed to implement the service. The present document
addresses the encoding of the service Protocol Data Units (PDU) and of the related information elements, the protocol
procedures and the corresponding SDL diagrams.
NOTE: According to Recommendation ITU-T I.130 [13], the stage 3 description of any telecommunication
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. The latter have not been provided
since they can be derived from the specification of the FE actions in the stage 2 description.
Service management procedures specified in the above stages (e.g. activation or interrogation) are optional unless
otherwise stated in the specific supplementary service stage documents.
4.2 Concepts associated with supplementary services
The terms used to define the procedures associated with supplementary services are given in ETSI EN 300 392-1 [1],
clause 14.3.1.
5 Service primitives
5.1 Service primitive general description
Primitives are specified for each supplementary service at the TNSS Service Access Point (TNSS-SAP), in a specific
clause of the corresponding stage 3 description in ETSI EN/ETS 300 392-12 [9].
Primitive names shall take the form of TNSS-service-name type where:
• service - supplementary service identifier;
• name - indicates the type of function this primitive is performing (e.g. DEFINE);
• type - indicates whether the primitive is a request, confirm, indication or response.
For example, an INTERROGATE request primitive for the supplementary service Ambience Listening (SS-AL) would
be specified as TNSS-AL-INTERROGATE request, when primitives of more than one supplementary service are used
in the same document. When a document refers only to one supplementary service the short form such as
INTERROGATE request may be used.
Parameters are listed with mandatory and conditional parameters first, followed by optional parameters. Repeatable
parameters are identified by a comment in the remarks column in the table specifying the primitive's parameters.
Following the specifications of a service's primitives, there is a parameter description section listing alphabetically all
primitive parameters used in this service and the values allowed.
Among those parameters, special mention is to be made of the parameter access priority. This parameter has to be
included in every service primitive request or response, since the priority defined for the corresponding air interface
(uplink) PDUs is set according to the its value (i.e. low, high or emergency priority as seen by the user application of
"0" to "7" as defined in the lower layer service primitives).
NOTE: For call related services the TNSS-SAP and TNCC-SAP logically form a combined SAP defining access
to the total service. Some of the supplementary service parameters are actually defined as TNCC-SAP
parameters.
ETSI
13 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
5.2 Notification service primitive
Many of the air interface PDUs can carry supplementary service-related information in special information element
notification. The notification information element values are used by many supplementary services to carry information
to the equipment not supporting the specific supplementary service. The information in the notification information
element may be displayed to the user in some format, e.g. in natural language or as a number code.
The information is presented to the user application via TNSS-SAP using service primitive NOTIFICATION indication.
The notification information element values are defined in clause 7.2.2. The same values are used as parameter values
in the NOTIFICATION indication primitive.
6 Supplementary service invocation order
Before allowing an outgoing call from a calling user to proceed towards the called user, or before offering an incoming
call to the called user, the SwMI shall search through the user supplementary service database for supplementary
services activated and proceed with their invocation in the order detailed in table 1. Due to the interactions specified
between supplementary services, the invocation of some of those listed in table 1 may result in the invocation of others
further below in that list being overridden although they have been activated, e.g. SS-CAD overrides SS-BIC.
Table 1: Supplementary service invocation order
Incoming calls Outgoing calls
PPC SNA
PC PPC
CAD CAD (see note 1)
BIC BOC
CFU AS
CW PC (see note 1)
CFB
CFNRy (see note 2)
CFNRc
NOTE 1: If SS-PC has been invoked for a call and if SS-CAD for outgoing call is
invoked for that call and operated with diversion towards a dispatcher
registered in another SwMI, SS-PC shall also be invoked for this diversion.
NOTE 2: If the called user is busy, SS-CFNRy may only be invoked if SS-CW has been
previously invoked. But the SS-CFNRy operation shall take precedence over
further SS-CW operation when the CFNRy no-reply timer has elapsed.
7 Transfer of information related to supplementary
service at the MS interface
7.1 Methods of transportation
There are 4 methods by which information related to supplementary service may be transferred at the MS interface:
• using the facility information element in a basic service PDU;
• using specific elements in a basic service PDU (e.g. Area Selection (SS-AS) in a U-SETUP PDU);
• using the Notification indicator information element in a basic service PDU;
• using a U/D-FACILITY PDU.
The first 3 methods may be used to send call related SS PDUs. The forth method is used to send call unrelated
SS PDUs.
NOTE: See definition of call related and call services unrelated in clause 3.1.
ETSI
14 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
7.2 Call related service information
7.2.1 Facility information element general construction
The facility information element is a type 3 CC PDU element as defined in clause 14.7 of ETSI EN 300 392-2 [2]. It is
used to convey call related supplementary service PDUs (SS PDUs) across the air interface and is present in all
CC PDU definitions (except U/D-FACILITY). Each SS PDU is encoded as stated in clause 8.
The encoding rules defined in annex E of ETSI EN 300 392-2 [2] shall apply for the definition of the facility
information element. Notably according to clause 14.8.48 of ETSI EN 300 392-2 [2], the value of the corresponding
type 3 element identifier will be equal to the binary value 0011 .
The contents of the facility information element in an uplink CC PDU shall be as defined in table 2.
Table 2: Uplink facility information element contents
Information sub-element Length C/O/M Remarks
Routeing 2 M See note 1
MNI 24 C See note 2
SS PDU Variable M See note 3
NOTE 1: The meaning of the information sub-element routeing shall be the following:
- same SwMI, if its binary value is equal to 00 ;
- end SwMI, if its binary value is equal to 01 ;
- home SwMI of called ITSI/GTSI, if its binary value is equal to 10 ;
- other SwMI indicated by its MNI value, if its binary value is equal to 11 .
NOTE 2: Shall be present if the binary value of the information sub-element routeing is equal to 11 .
NOTE 3: See clause 8.
NOTE: Since SS PDUs are not specified in table 2 as being repeatable, this means that as many different facility
information elements will be needed in a CC PDU as there are SS PDUs to be conveyed.
The contents of a facility information element in a downlink CC PDU shall be the same as that defined in table 2 except
for that there shall be no information sub-element routeing and no information sub-element MNI.
ETSI
15 Draft ETSI EN 300 392-9 V1.7.0 (2019-08)
7.2.2 Notification indicator information element
The notification indicator information element values that may be used shall be as shown in table 3. When, in a
situation, more than one notification indicator value is applicable the SwMI may choose the most appropriate and reject
the other values or it may send additional PDUs containing the other notification indicator values.
Table 3: Notification indicator information element contents
Information element Length Value Remarks
Notification indicator 6 0 LE broadcast
1 LE acknowledgement
2 LE paging
3 AL operation (see note 1)
4 Call barred by SS-BIC
5 Call barred by SS-BOC
6 Call is forwarded (diverting)
7 Forwarding (diversion) activated
8 Identity presentation restricted
9 Presentation restriction overridden
10 Call waiting invoked
11 Call put on hold (remote hold)
12 Call on hold retrieved (remote retrieval)
13 Include call (see note 2)
14 Multiparty call (see note 3)
15 LSC invoked
16 Call rejected due to SS-AS
17 SS-AS not invoked/supported
18 Called user alerted
19 Called user connected
20 Call proceeding
21 SS-CFU invoked
22 SS-CFB invoked
23 SS-CFNRy invoked
24 SS-CFNRc invoked
25 AL-call or speech item (see note 4)
26 Notice of imminent call disconnection
27 Limited group coverage
28 Reserved
etc. etc.
63 Reserved
NOTE 1: Not to be presented to the user.
NOTE 2: Refer to SS-IC.
NOTE 3: Any other than TETRA group call comprising multiple participants.
NOTE 4: This notification information element value is intended to be presented to the user.
NOTE: According to the definition of this information element in clause 14.8.27 of ETSI EN 300 392-2 [2], when
an SwMI receives such information element in a (call related) ISI PDU, it may relay it to the MS.
7.3 Call unrelated supplementary service information
All call unrelated SS PDUs are transported using a U/D-FACILITY PDU.
The U/D-FACILITY PDU is used to convey only call unrelated SS PDUs across the air interface. Each SS PDU is
encoded as stated in clause 8. The U/D-FACILITY PDU may contain more than one SS PDU. It may contain also, or
instead, one or more proprietary information elements.
The encoding rules def
...
EUROPEAN STANDARD
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 9: General requirements for supplementary services
2 ETSI EN 300 392-9 V1.7.1 (2020-04)
Reference
REN/TCCE-03265
Keywords
supplementary service, 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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI EN 300 392-9 V1.7.1 (2020-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols, abbreviations and Functional Entities (FE) . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
3.4 Functional Entities (FE) . 11
4 Supplementary service concepts . 11
4.1 Stage 1, 2 and 3 descriptions . 11
4.1.0 General Description . 11
4.1.1 Stage 1 description . 11
4.1.2 Stage 2 description . 11
4.1.3 Stage 3 description . 12
4.2 Concepts associated with supplementary services . 12
5 Service primitives . 12
5.1 Service primitive general description . 12
5.2 Notification service primitive . 13
6 Supplementary service invocation order . 13
7 Transfer of information related to supplementary service at the MS interface . 13
7.1 Methods of transportation . 13
7.2 Call related service information . 14
7.2.1 Facility information element general construction . 14
7.2.2 Notification indicator information element . 15
7.3 Call unrelated supplementary service information . 15
8 SS PDU contents . 16
8.0 SS PDU contents general . 16
8.1 SS type . 17
8.2 SS PDU type. 17
8.3 Repeated information element or set of information elements . 19
8.3.1 Range type information element . 19
8.3.2 Response to a SS PDU including repeated information elements controlled by a range type
information element . 20
8.3.3 Information element number of XX . 21
8.4 Encoding of other SS PDU ele ments . 21
8.4.0 Encoding of other SS PDU elements general . 21
8.4.1 User identity. 22
8.4.2 Character string . 23
8.4.3 External number . 25
8.4.4 External call restriction . 27
8.4.5 Activation, definition, and interrogation failure values . 27
8.4.6 Manufacturer identifier information element . 28
9 SS PDU routeing . 28
9.1 Actions at the SwMI receiving an SS PDU from a MS registered in this SwMI . 28
9.2 SS PDU sent by a SwMI to a MS . 29
9.2.0 SS PDU sent by a SwMI to a MS general. 29
9.2.1 SS PDU addressed individually by a SwMI to an MS . 29
ETSI
4 ETSI EN 300 392-9 V1.7.1 (2020-04)
9.2.2 SS PDU originated by a SwMI using a group address . 30
9.2.3 Sending of SS PDU by the destination SwMI to MS . 30
9.3 SS PDU transport by ANF-ISISS . 30
10 ANF-ISISS . 31
10.1 Service model . 31
10.2 Service primitives . 31
10.3 Protocol . 32
10.3.1 Protocol general . 32
10.3.2 Possible groupings of ISI SS PDUs and of invoked ANF-ISISSs . 34
10.3.3 Void . 34
11 Exceptional cases . 34
11.1 ISI exceptional cases . 34
11.1.0 General . 34
11.1.1 Case a) . 35
11.1.1.1 Call unrelated ANF-ISISS PDU . 35
11.1.1.2 Call related ANF-ISISS PDU . 35
11.1.2 Case b) . 35
11.1.3 Case c) . 36
11.1.3.1 Case c) General . 36
11.1.4 Case d) . 36
11.1.4.0 Case d) General . 36
11.1.4.1 Cases d.1) and d.2) . 36
11.1.4.2 Case d.3) . 37
11.2 Exceptional cases at the air interface . 37
11.2.1 No ISI involved . 37
11.2.2 ISI involved . 38
12 Generic specification of activation/deactivation, definition and interrogation operations . 38
12.1 Stage 2 description . 38
12.2 Stage 3 description . 39
13 Authentication issues . 39
13.1 Authentication requirements for TETRA supplementary services . 39
13.2 The use of security class to meet authentication requirements for TETRA supplementary services . 40
13.2.0 General . 40
13.2.1 Class 1 . 40
13.2.2 Class 2 . 40
13.2.3 Class 3 . 40
13.2.4 Impact of ISI . 40
13.2.5 Security of data within a SwMI . 40
Annex A (informative): Definition of the ISI operation . 41
Annex B: Void . 42
Annex C: Void . 43
Annex D (informative): Change requests . 44
Annex E: Void . 45
History . 46
ETSI
5 ETSI EN 300 392-9 V1.7.1 (2020-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee TETRA and Critical Communications
Evolution (TCCE).
The present document is part 9 of a multi-part deliverable covering the Terrestrial Trunked Radio (TETRA); Voice plus
Data (V+D) and Direct Mode Operation (DMO), as identified below:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 3: "Interworking at the Inter-System Interface (ISI)";
Part 4: "Gateways basic operation";
Part 5: "Peripheral Equipment Interface (PEI)";
Part 7: "Security";
Part 9: "General requirements for supplementary services";
Part 10: "Supplementary services stage 1";
Part 11: "Supplementary services stage 2";
Part 12: "Supplementary services stage 3";
Part 13: "SDL model of the Air Interface (AI)";
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 15: "TETRA frequency bands, duplex spacings and channel numbering";
Part 16: "Network Performance Metrics";
Part 17: "TETRA V+D and DMO specifications";
Part 18: "Air interface optimized applications";
Part 19: "Interworking between TETRA and Broadband systems".
ETSI
6 ETSI EN 300 392-9 V1.7.1 (2020-04)
NOTE 1: Part 3, sub-parts 6 and 7 (Speech format implementation), part 4, sub-part 3 (Data networks gateway),
part 10, sub-part 15 (Transfer of control), part 13 (SDL) and part 14 (PICS) of this multi-part deliverable
are in status "historical" and are not maintained.
NOTE 2: Some parts are also published as Technical Specifications such as ETSI TS 100 392-2 and those may be
the latest version of the document.
National transposition dates
Date of adoption of this EN: 13 November 2019
Date of latest announcement of this EN (doa): 31 July 2020
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 January 2021
Date of withdrawal of any conflicting National Standard (dow): 31 January 2021
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
7 ETSI EN 300 392-9 V1.7.1 (2020-04)
1 Scope
The present document is applicable to any TETRA terminal equipment (Mobile Station (MS)) and to any TETRA
network (Switching and Management Infrastructure (SwMI)) which support at least one TETRA Supplementary
Service (SS). In addition, its routeing requirements of supplementary service information are applicable to any TETRA
network with a Voice plus Data (V+D) Inter-System Interface (ISI) to another TETRA network which supports at least
one TETRA SS.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETS EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[2] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[3] ETSI EN 300 392-3-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 9: Transport layer independent,
General design".
[4] Void.
[5] Void.
[6] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[7] ETSI EN 300 392-10-6: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 10: Supplementary services stage 1; Sub-part 6: Call Authorized by Dispatcher (CAD)".
[8] ETSI EN/ETS 300 392-11 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 11: Supplementary services stage 2".
[9] ETSI EN/ETS 300 392-12 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 12: Supplementary services stage 3".
[10] ISO/IEC 11571 (1998): "Information technology -- Telecommunications and information
exchange between systems -- Private Integrated Services Networks -- Addressing".
[11] Void.
[12] Void.
ETSI
8 ETSI EN 300 392-9 V1.7.1 (2020-04)
[13] Recommendation ITU-T I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[14] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
[15] Recommendation ITU-T X.121: "International numbering plan for public data networks".
[16] Void.
[17] Void.
[18] Void.
[19] Void.
[20] ETSI ETS 300 392-12-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 12: Supplementary services stage 3; Sub-part 7: Short Number Addressing (SNA)".
[21] ISO/IEC 10646: "Information technology -- Universal Coded Character Set (UCS)".
[22] ETSI TS 100 392-18-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and Direct
Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 3: Direct mode
Over The Air Management protocol (DOTAM)".
[23] ETSI EN 300 392-3-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 10: General design, PSS1
over E.1".
[24] ETSI EN 300 392-3-11: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 11: General design, SIP/IP".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETSI EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Designers'
guide; Part 5: Guidance on Numbering and addressing".
3 Definition of terms, symbols, abbreviations and
Functional Entities (FE)
3.1 Terms
For the purposes of the present document, the terms given in ETSI EN 300 392-2 [2] and the following apply:
affected user: user who is subject to the operation
affected user SwMI: SwMI where the affected user is currently registered
ETSI
9 ETSI EN 300 392-9 V1.7.1 (2020-04)
authorized user: user who is responsible for the definition, activation and deactivation of the service
NOTE: The authorized user may also interrogate the service. Affected user and served user may also be
authorized user as defined in each supplementary service.
authorized user SwMI: SwMI where the authorized user is currently registered
call related service: service requested from call set-up initiation until call disconnection and related to that call
NOTE: The call-related service can also be valid a certain short time after disconnection but before next call
set-up is initiated.
call unrelated service: service either requested outside a call or inside a call but not referring to that call
ISI Mediation Function: entity which provides the services that are not supported by the transport layer protocol to
different ANF-ISI entities
served user: user for whom the supplementary service is invoked
served user SwMI: SwMI where the served user is currently registered
user: entity using the services of a telecommunications network via an externally accessible service access point
NOTE: A user may be a person or an application process.
user application: application process which acts as a user
NOTE: See definition of user.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
AI Air Interface
ANF Additional Network Feature
ANF-ISIGC Additional Network Feature - Inter-System Interface Group Call
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
ANF-ISISS Additional Network Feature - Inter-System Interface Supplementary Service
APDU Application Packet Data Unit
APP APProved
CC PDU Call Control Protocol Data Unit
DMO Direct Mode Operation
DOTAM Direct mode Over The Air Management protocol
EPT ETSI Project TETRA
ETS European Telecommunication Standard
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
IP Internet Protocol
ISI SS Inter System Interface Supplementation Service
ISI Inter-System Interface
ISISS Inter-System Interface Supplementary Service
ISSI Individual Short Subscriber Identity
ITSI Individual TETRA Subscriber Identity
ITU International Telecommunication Union
MAC Media Access Control
MCC Mobile Country Code
MLE Mobile Link Entity
ETSI
10 ETSI EN 300 392-9 V1.7.1 (2020-04)
MNC Mobile Network Code
MNI Mobile Network Identity
MS Mobile Station
MS-ISDN Mobile Station ISDN number
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PISN Private Integrated Services Network
PSS1 Private Signalling System no. 1
PSTN Public Services Telephone Network
SAP Service Access Point
SDL (Functional) Specification and Description Language
SIP Session Initiation Protocol
SS PDU Supplementary Service Protocol Data Unit
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SSI Short Subscriber Identity
SS-PDU Supplementary Service PDU
SwMI Switching and Management Infrastructure
TNCC-SAP TETRA Network layer Call Control - Service Access Point
TNSS TETRA Network layer Supplementary Service
TNSS-SAP TETRA Network layer Supplementary Service - Service Access Point
TSI TETRA Subscriber Identity
UCS Universal Multiple-Octet Coded Character Set, also known as Universal Character Set
UCS-2 Universal Character Set coded in 2 octets
UTF-16BE Unicode Transformation Format serialized as two bytes in Big-Endian format
V+D Voice plus Data
WG3 TC TETRA Working Group 3
XX generic name of an information element
Supplementary Service abbreviations
For the purposes of the present document, the following abbreviations also apply:
NOTE 1: Supplementary service abbreviations are also used without "SS-" preamble e.g. "SS-AL" and "AL" are
used as appropriate.
NOTE 2: The supplementary services list contains also abbreviations that are not used in the present document.
SS-AL Ambience Listening
SS-AP Access Priority
SS-AS Area Selection
SS-BIC Barring of Incoming Calls
SS-BOC Barring of Outgoing Calls
SS-CAD Call Authorized by Dispatcher
SS-CCBS Call Completion on Busy Subscriber
SS-CCNR Call Completion on No Reply
SS-CF Call Forwarding
SS-CFB Call Forwarding on Busy
SS-CFNR Call Forwarding on No Reply (generic for both CFNRy and CFNRc)
SS-CFNRc Call Forwarding on Mobile Subscriber Not Reachable
SS-CFNRy Call Forwarding on No Reply
SS-CFU Call Forwarding Unconditional
SS-CI Call Identification
SS-CLIP Calling Line Identification Presentation
SS-CLIR Calling Line Identification Restriction
SS-COLP COnnected Line identification Presentation
SS-COLR COnnected Line identification Restriction
SS-CR Call Report
SS-CRT Call Retention
SS-CW Call Waiting
SS-DGNA Dynamic Group Number Assignment
ETSI
11 ETSI EN 300 392-9 V1.7.1 (2020-04)
SS-DL Discreet Listening
SS-HOLD call HOLD
SS-IC Include Call
SS-LE Late Entry
SS-LSC List Search Call
SS-PC Priority Call
SS-PPC Pre-emptive Priority Call
SS-SNA Short Number Addressing
SS-TPI Talking Party Identification
3.4 Functional Entities (FE)
The functional model for each supplementary service is comprised of a number of FEs. The FEs below should always
have the following definitions:
• FE1 served user's service agent;
• FE2 SwMI service control functional entity;
• FE3 authorized user's service agent;
• FE5 service agent of the user affected by service operation;
• FE6 service agent of second listening party;
• FE7 service agent of dispatcher (in the case of SS-CAD) or of monitoring user (in the case of SS-DL);
• FE8 service agent of user removed from a call during a pre-emptive priority call;
• FE9 service agent of user informed that another user has been removed from a call during a pre-emptive
priority call;
• FE10 service agent of user affected by management functions.
FE2, the SwMI functional entity, may be split into secondary FEs when needed for a given supplementary service.
These FEs are called FE2x in the corresponding stage 2 description (in the related ETSI EN/ETS 300 392-11 [8]).
4 Supplementary service concepts
4.1 Stage 1, 2 and 3 descriptions
4.1.0 General Description
Supplementary service descriptions are covered in 3 stages according to the method described in Recommendation
ITU-T I.130 [13], each stage in a separate document. The contents of each stage description are described in the
following clauses.
4.1.1 Stage 1 description
This stage is the overall service description from the user viewpoint and also details the interaction of the service with
other supplementary services.
4.1.2 Stage 2 description
Stage 2 identifies the functional capabilities and the information flows needed to support the supplementary service as
specified in its stage 1 description. It defines the FEs, the information flow between these entities, the FE actions and
the allocation of FEs to physical locations.
ETSI
12 ETSI EN 300 392-9 V1.7.1 (2020-04)
4.1.3 Stage 3 description
The stage 3 description specifies the signalling protocols needed to implement the service. The present document
addresses the encoding of the service Protocol Data Units (PDU) and of the related information elements, the protocol
procedures and the corresponding SDL diagrams.
NOTE: According to Recommendation ITU-T I.130 [13], the stage 3 description of any telecommunication
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. The latter have not been provided
since they can be derived from the specification of the FE actions in the stage 2 description.
Service management procedures specified in the above stages (e.g. activation or interrogation) are optional unless
otherwise stated in the specific supplementary service stage documents.
4.2 Concepts associated with supplementary services
The terms used to define the procedures associated with supplementary services are given in ETSI EN 300 392-1 [1],
clause 14.3.1.
5 Service primitives
5.1 Service primitive general description
Primitives are specified for each supplementary service at the TNSS Service Access Point (TNSS-SAP), in a specific
clause of the corresponding stage 3 description in ETSI EN/ETS 300 392-12 [9].
Primitive names shall take the form of TNSS-service-name type where:
• service - supplementary service identifier;
• name - indicates the type of function this primitive is performing (e.g. DEFINE);
• type - indicates whether the primitive is a request, confirm, indication or response.
For example, an INTERROGATE request primitive for the supplementary service Ambience Listening (SS-AL) would
be specified as TNSS-AL-INTERROGATE request, when primitives of more than one supplementary service are used
in the same document. When a document refers only to one supplementary service the short form such as
INTERROGATE request may be used.
Parameters are listed with mandatory and conditional parameters first, followed by optional parameters. Repeatable
parameters are identified by a comment in the remarks column in the table specifying the primitive's parameters.
Following the specifications of a service's primitives, there is a parameter description section listing alphabetically all
primitive parameters used in this service and the values allowed.
Among those parameters, special mention is to be made of the parameter access priority. This parameter has to be
included in every service primitive request or response, since the priority defined for the corresponding air interface
(uplink) PDUs is set according to the its value (i.e. low, high or emergency priority as seen by the user application of
"0" to "7" as defined in the lower layer service primitives).
NOTE: For call related services the TNSS-SAP and TNCC-SAP logically form a combined SAP defining access
to the total service. Some of the supplementary service parameters are actually defined as TNCC-SAP
parameters.
ETSI
13 ETSI EN 300 392-9 V1.7.1 (2020-04)
5.2 Notification service primitive
Many of the air interface PDUs can carry supplementary service-related information in special information element
notification. The notification information element values are used by many supplementary services to carry information
to the equipment not supporting the specific supplementary service. The information in the notification information
element may be displayed to the user in some format, e.g. in natural language or as a number code.
The information is presented to the user application via TNSS-SAP using service primitive NOTIFICATION indication.
The notification information element values are defined in clause 7.2.2. The same values are used as parameter values
in the NOTIFICATION indication primitive.
6 Supplementary service invocation order
Before allowing an outgoing call from a calling user to proceed towards the called user, or before offering an incoming
call to the called user, the SwMI shall search through the user supplementary service database for supplementary
services activated and proceed with their invocation in the order detailed in table 1. Due to the interactions specified
between supplementary services, the invocation of some of those listed in table 1 may result in the invocation of others
further below in that list being overridden although they have been activated, e.g. SS-CAD overrides SS-BIC.
Table 1: Supplementary service invocation order
Incoming calls Outgoing calls
PPC SNA
PC PPC
CAD CAD (see note 1)
BIC BOC
CFU AS
CW PC (see note 1)
CFB
CFNRy (see note 2)
CFNRc
NOTE 1: If SS-PC has been invoked for a call and if SS-CAD for outgoing call is
invoked for that call and operated with diversion towards a dispatcher
registered in another SwMI, SS-PC shall also be invoked for this diversion.
NOTE 2: If the called user is busy, SS-CFNRy may only be invoked if SS-CW has been
previously invoked. But the SS-CFNRy operation shall take precedence over
further SS-CW operation when the CFNRy no-reply timer has elapsed.
7 Transfer of information related to supplementary
service at the MS interface
7.1 Methods of transportation
There are 4 methods by which information related to supplementary service may be transferred at the MS interface:
• using the facility information element in a basic service PDU;
• using specific elements in a basic service PDU (e.g. Area Selection (SS-AS) in a U-SETUP PDU);
• using the Notification indicator information element in a basic service PDU;
• using a U/D-FACILITY PDU.
The first 3 methods may be used to send call related SS PDUs. The forth method is used to send call unrelated
SS PDUs.
NOTE: See definition of call related and call services unrelated in clause 3.1.
ETSI
14 ETSI EN 300 392-9 V1.7.1 (2020-04)
7.2 Call related service information
7.2.1 Facility information element general construction
The facility information element is a type 3 CC PDU element as defined in clause 14.7 of ETSI EN 300 392-2 [2]. It is
used to convey call related supplementary service PDUs (SS PDUs) across the air interface and is present in all
CC PDU definitions (except U/D-FACILITY). Each SS PDU is encoded as stated in clause 8.
The encoding rules defined in annex E of ETSI EN 300 392-2 [2] shall apply for the definition of the facility
information element. Notably according to clause 14.8.48 of ETSI EN 300 392-2 [2], the value of the corresponding
type 3 element identifier will be equal to the binary value 0011 .
The contents of the facility information element in an uplink CC PDU shall be as defined in table 2.
Table 2: Uplink facility information element contents
Information sub-element Length C/O/M Remarks
Routeing 2 M See note 1
MNI 24 C See note 2
SS PDU Variable M See note 3
NOTE 1: The meaning of the information sub-element routeing shall be the following:
- same SwMI, if its binary value is equal to 00 ;
- end SwMI, if its binary value is equal to 01 ;
- home SwMI of called ITSI/GTSI, if its binary value is equal to 10 ;
- other SwMI indicated by its MNI value, if its binary value is equal to 11 .
NOTE 2: Shall be present if the binary value of the information sub-element routeing is equal to 11 .
NOTE 3: See clause 8.
NOTE: Since SS PDUs are not specified in table 2 as being repeatable, this means that as many different facility
information elements will be needed in a CC PDU as there are SS PDUs to be conveyed.
The contents of a facility information element in a downlink CC PDU shall be the same as that defined in table 2 except
for that there shall be no information sub-element routeing and no information sub-element MNI.
ETSI
15 ETSI EN 300 392-9 V1.7.1 (2020-04)
7.2.2 Notification indicator information element
The notification indicator information element values that may be used shall be as shown in table 3. When, in a
situation, more than one notification indicator value is applicable the SwMI may choose the most appropriate and reject
the other values or it may send additional PDUs containing the other notification indicator values.
Table 3: Notification indicator information element contents
Information element Length Value Remarks
Notification indicator 6 0 LE broadcast
1 LE acknowledgement
2 LE paging
3 AL operation (see note 1)
4 Call barred by SS-BIC
5 Call barred by SS-BOC
6 Call is forwarded (diverting)
7 Forwarding (diversion) activated
8 Identity presentation restricted
9 Presentation restriction overridden
10 Call waiting invoked
11 Call put on hold (remote hold)
12 Call on hold retrieved (remote retrieval)
13 Include call (see note 2)
14 Multiparty call (see note 3)
15 LSC invoked
16 Call rejected due to SS-AS
17 SS-AS not invoked/supported
18 Called user alerted
19 Called user connected
20 Call proceeding
21 SS-CFU invoked
22 SS-CFB invoked
23 SS-CFNRy invoked
24 SS-CFNRc invoked
25 AL-call or speech item (see note 4)
26 Notice of imminent call disconnection
27 Limited group coverage
28 Reserved
etc. etc.
63 Reserved
NOTE 1: Not to be presented to the user.
NOTE 2: Refer to SS-IC.
NOTE 3: Any other than TETRA group call comprising multiple participants.
NOTE 4: This notification information element value is intended to be presented to the user.
NOTE: According to the definition of this information element in clause 14.8.27 of ETSI EN 300 392-2 [2], when
an SwMI receives such information element in a (call related) ISI PDU, it may relay it to the MS.
7.3 Call unrelated supplementary service information
All call unrelated SS PDUs are transported using a U/D-FACILITY PDU.
The U/D-FACILITY PDU is used to convey only call unrelated SS PDUs across the air interface. Each SS PDU is
encoded as stated in clause 8. The U/D-FACILITY PDU may contain more than one SS PDU. It may contain also, or
instead, one or more proprietary information elements.
The encoding rules defined in annex E of ETSI EN 300 392-2 [2] shall apply for U/D-FACILITY PDU definitions.
The contents of the U-FACILITY PDU shall be as defined in table 4.
ETSI
---------------------
...
SLOVENSKI STANDARD
01-julij-2020
Prizemni snopovni radio (TETRA) - Govor in podatki (V+D) - 9. del: Splošne
zahteve za dopolnilne storitve
Terrestrial Trunked Radio (TETRA) - Voice plus Data (V+D) - Part 9: General
requirements for supplementary services
Ta slovenski standard je istoveten z: ETSI EN 300 392-9 V1.7.1 (2020-04)
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
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 9: General requirements for supplementary services
2 ETSI EN 300 392-9 V1.7.1 (2020-04)
Reference
REN/TCCE-03265
Keywords
supplementary service, 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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI EN 300 392-9 V1.7.1 (2020-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols, abbreviations and Functional Entities (FE) . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
3.4 Functional Entities (FE) . 11
4 Supplementary service concepts . 11
4.1 Stage 1, 2 and 3 descriptions . 11
4.1.0 General Description . 11
4.1.1 Stage 1 description . 11
4.1.2 Stage 2 description . 11
4.1.3 Stage 3 description . 12
4.2 Concepts associated with supplementary services . 12
5 Service primitives . 12
5.1 Service primitive general description . 12
5.2 Notification service primitive . 13
6 Supplementary service invocation order . 13
7 Transfer of information related to supplementary service at the MS interface . 13
7.1 Methods of transportation . 13
7.2 Call related service information . 14
7.2.1 Facility information element general construction . 14
7.2.2 Notification indicator information element . 15
7.3 Call unrelated supplementary service information . 15
8 SS PDU contents . 16
8.0 SS PDU contents general . 16
8.1 SS type . 17
8.2 SS PDU type. 17
8.3 Repeated information element or set of information elements . 19
8.3.1 Range type information element . 19
8.3.2 Response to a SS PDU including repeated information elements controlled by a range type
information element . 20
8.3.3 Information element number of XX . 21
8.4 Encoding of other SS PDU ele ments . 21
8.4.0 Encoding of other SS PDU elements general . 21
8.4.1 User identity. 22
8.4.2 Character string . 23
8.4.3 External number . 25
8.4.4 External call restriction . 27
8.4.5 Activation, definition, and interrogation failure values . 27
8.4.6 Manufacturer identifier information element . 28
9 SS PDU routeing . 28
9.1 Actions at the SwMI receiving an SS PDU from a MS registered in this SwMI . 28
9.2 SS PDU sent by a SwMI to a MS . 29
9.2.0 SS PDU sent by a SwMI to a MS general. 29
9.2.1 SS PDU addressed individually by a SwMI to an MS . 29
ETSI
4 ETSI EN 300 392-9 V1.7.1 (2020-04)
9.2.2 SS PDU originated by a SwMI using a group address . 30
9.2.3 Sending of SS PDU by the destination SwMI to MS . 30
9.3 SS PDU transport by ANF-ISISS . 30
10 ANF-ISISS . 31
10.1 Service model . 31
10.2 Service primitives . 31
10.3 Protocol . 32
10.3.1 Protocol general . 32
10.3.2 Possible groupings of ISI SS PDUs and of invoked ANF-ISISSs . 34
10.3.3 Void . 34
11 Exceptional cases . 34
11.1 ISI exceptional cases . 34
11.1.0 General . 34
11.1.1 Case a) . 35
11.1.1.1 Call unrelated ANF-ISISS PDU . 35
11.1.1.2 Call related ANF-ISISS PDU . 35
11.1.2 Case b) . 35
11.1.3 Case c) . 36
11.1.3.1 Case c) General . 36
11.1.4 Case d) . 36
11.1.4.0 Case d) General . 36
11.1.4.1 Cases d.1) and d.2) . 36
11.1.4.2 Case d.3) . 37
11.2 Exceptional cases at the air interface . 37
11.2.1 No ISI involved . 37
11.2.2 ISI involved . 38
12 Generic specification of activation/deactivation, definition and interrogation operations . 38
12.1 Stage 2 description . 38
12.2 Stage 3 description . 39
13 Authentication issues . 39
13.1 Authentication requirements for TETRA supplementary services . 39
13.2 The use of security class to meet authentication requirements for TETRA supplementary services . 40
13.2.0 General . 40
13.2.1 Class 1 . 40
13.2.2 Class 2 . 40
13.2.3 Class 3 . 40
13.2.4 Impact of ISI . 40
13.2.5 Security of data within a SwMI . 40
Annex A (informative): Definition of the ISI operation . 41
Annex B: Void . 42
Annex C: Void . 43
Annex D (informative): Change requests . 44
Annex E: Void . 45
History . 46
ETSI
5 ETSI EN 300 392-9 V1.7.1 (2020-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee TETRA and Critical Communications
Evolution (TCCE).
The present document is part 9 of a multi-part deliverable covering the Terrestrial Trunked Radio (TETRA); Voice plus
Data (V+D) and Direct Mode Operation (DMO), as identified below:
Part 1: "General network design";
Part 2: "Air Interface (AI)";
Part 3: "Interworking at the Inter-System Interface (ISI)";
Part 4: "Gateways basic operation";
Part 5: "Peripheral Equipment Interface (PEI)";
Part 7: "Security";
Part 9: "General requirements for supplementary services";
Part 10: "Supplementary services stage 1";
Part 11: "Supplementary services stage 2";
Part 12: "Supplementary services stage 3";
Part 13: "SDL model of the Air Interface (AI)";
Part 14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 15: "TETRA frequency bands, duplex spacings and channel numbering";
Part 16: "Network Performance Metrics";
Part 17: "TETRA V+D and DMO specifications";
Part 18: "Air interface optimized applications";
Part 19: "Interworking between TETRA and Broadband systems".
ETSI
6 ETSI EN 300 392-9 V1.7.1 (2020-04)
NOTE 1: Part 3, sub-parts 6 and 7 (Speech format implementation), part 4, sub-part 3 (Data networks gateway),
part 10, sub-part 15 (Transfer of control), part 13 (SDL) and part 14 (PICS) of this multi-part deliverable
are in status "historical" and are not maintained.
NOTE 2: Some parts are also published as Technical Specifications such as ETSI TS 100 392-2 and those may be
the latest version of the document.
National transposition dates
Date of adoption of this EN: 13 November 2019
Date of latest announcement of this EN (doa): 31 July 2020
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 January 2021
Date of withdrawal of any conflicting National Standard (dow): 31 January 2021
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
7 ETSI EN 300 392-9 V1.7.1 (2020-04)
1 Scope
The present document is applicable to any TETRA terminal equipment (Mobile Station (MS)) and to any TETRA
network (Switching and Management Infrastructure (SwMI)) which support at least one TETRA Supplementary
Service (SS). In addition, its routeing requirements of supplementary service information are applicable to any TETRA
network with a Voice plus Data (V+D) Inter-System Interface (ISI) to another TETRA network which supports at least
one TETRA SS.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETS EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[2] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air
Interface (AI)".
[3] ETSI EN 300 392-3-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 9: Transport layer independent,
General design".
[4] Void.
[5] Void.
[6] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[7] ETSI EN 300 392-10-6: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 10: Supplementary services stage 1; Sub-part 6: Call Authorized by Dispatcher (CAD)".
[8] ETSI EN/ETS 300 392-11 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 11: Supplementary services stage 2".
[9] ETSI EN/ETS 300 392-12 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 12: Supplementary services stage 3".
[10] ISO/IEC 11571 (1998): "Information technology -- Telecommunications and information
exchange between systems -- Private Integrated Services Networks -- Addressing".
[11] Void.
[12] Void.
ETSI
8 ETSI EN 300 392-9 V1.7.1 (2020-04)
[13] Recommendation ITU-T I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[14] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
[15] Recommendation ITU-T X.121: "International numbering plan for public data networks".
[16] Void.
[17] Void.
[18] Void.
[19] Void.
[20] ETSI ETS 300 392-12-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 12: Supplementary services stage 3; Sub-part 7: Short Number Addressing (SNA)".
[21] ISO/IEC 10646: "Information technology -- Universal Coded Character Set (UCS)".
[22] ETSI TS 100 392-18-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and Direct
Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 3: Direct mode
Over The Air Management protocol (DOTAM)".
[23] ETSI EN 300 392-3-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 10: General design, PSS1
over E.1".
[24] ETSI EN 300 392-3-11: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 11: General design, SIP/IP".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE 1: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
NOTE 2: Note that for the TETRA standards, the reference is always to a European Standard (ETSI EN 300 xxx) if
such has been published, but the latest version of that standard can be either an EN or a Technical
Specification (ETSI TS 100 xxx), even if this is not visible in the reference list.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Designers'
guide; Part 5: Guidance on Numbering and addressing".
3 Definition of terms, symbols, abbreviations and
Functional Entities (FE)
3.1 Terms
For the purposes of the present document, the terms given in ETSI EN 300 392-2 [2] and the following apply:
affected user: user who is subject to the operation
affected user SwMI: SwMI where the affected user is currently registered
ETSI
9 ETSI EN 300 392-9 V1.7.1 (2020-04)
authorized user: user who is responsible for the definition, activation and deactivation of the service
NOTE: The authorized user may also interrogate the service. Affected user and served user may also be
authorized user as defined in each supplementary service.
authorized user SwMI: SwMI where the authorized user is currently registered
call related service: service requested from call set-up initiation until call disconnection and related to that call
NOTE: The call-related service can also be valid a certain short time after disconnection but before next call
set-up is initiated.
call unrelated service: service either requested outside a call or inside a call but not referring to that call
ISI Mediation Function: entity which provides the services that are not supported by the transport layer protocol to
different ANF-ISI entities
served user: user for whom the supplementary service is invoked
served user SwMI: SwMI where the served user is currently registered
user: entity using the services of a telecommunications network via an externally accessible service access point
NOTE: A user may be a person or an application process.
user application: application process which acts as a user
NOTE: See definition of user.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
AI Air Interface
ANF Additional Network Feature
ANF-ISIGC Additional Network Feature - Inter-System Interface Group Call
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
ANF-ISISS Additional Network Feature - Inter-System Interface Supplementary Service
APDU Application Packet Data Unit
APP APProved
CC PDU Call Control Protocol Data Unit
DMO Direct Mode Operation
DOTAM Direct mode Over The Air Management protocol
EPT ETSI Project TETRA
ETS European Telecommunication Standard
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
IP Internet Protocol
ISI SS Inter System Interface Supplementation Service
ISI Inter-System Interface
ISISS Inter-System Interface Supplementary Service
ISSI Individual Short Subscriber Identity
ITSI Individual TETRA Subscriber Identity
ITU International Telecommunication Union
MAC Media Access Control
MCC Mobile Country Code
MLE Mobile Link Entity
ETSI
10 ETSI EN 300 392-9 V1.7.1 (2020-04)
MNC Mobile Network Code
MNI Mobile Network Identity
MS Mobile Station
MS-ISDN Mobile Station ISDN number
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PISN Private Integrated Services Network
PSS1 Private Signalling System no. 1
PSTN Public Services Telephone Network
SAP Service Access Point
SDL (Functional) Specification and Description Language
SIP Session Initiation Protocol
SS PDU Supplementary Service Protocol Data Unit
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SSI Short Subscriber Identity
SS-PDU Supplementary Service PDU
SwMI Switching and Management Infrastructure
TNCC-SAP TETRA Network layer Call Control - Service Access Point
TNSS TETRA Network layer Supplementary Service
TNSS-SAP TETRA Network layer Supplementary Service - Service Access Point
TSI TETRA Subscriber Identity
UCS Universal Multiple-Octet Coded Character Set, also known as Universal Character Set
UCS-2 Universal Character Set coded in 2 octets
UTF-16BE Unicode Transformation Format serialized as two bytes in Big-Endian format
V+D Voice plus Data
WG3 TC TETRA Working Group 3
XX generic name of an information element
Supplementary Service abbreviations
For the purposes of the present document, the following abbreviations also apply:
NOTE 1: Supplementary service abbreviations are also used without "SS-" preamble e.g. "SS-AL" and "AL" are
used as appropriate.
NOTE 2: The supplementary services list contains also abbreviations that are not used in the present document.
SS-AL Ambience Listening
SS-AP Access Priority
SS-AS Area Selection
SS-BIC Barring of Incoming Calls
SS-BOC Barring of Outgoing Calls
SS-CAD Call Authorized by Dispatcher
SS-CCBS Call Completion on Busy Subscriber
SS-CCNR Call Completion on No Reply
SS-CF Call Forwarding
SS-CFB Call Forwarding on Busy
SS-CFNR Call Forwarding on No Reply (generic for both CFNRy and CFNRc)
SS-CFNRc Call Forwarding on Mobile Subscriber Not Reachable
SS-CFNRy Call Forwarding on No Reply
SS-CFU Call Forwarding Unconditional
SS-CI Call Identification
SS-CLIP Calling Line Identification Presentation
SS-CLIR Calling Line Identification Restriction
SS-COLP COnnected Line identification Presentation
SS-COLR COnnected Line identification Restriction
SS-CR Call Report
SS-CRT Call Retention
SS-CW Call Waiting
SS-DGNA Dynamic Group Number Assignment
ETSI
11 ETSI EN 300 392-9 V1.7.1 (2020-04)
SS-DL Discreet Listening
SS-HOLD call HOLD
SS-IC Include Call
SS-LE Late Entry
SS-LSC List Search Call
SS-PC Priority Call
SS-PPC Pre-emptive Priority Call
SS-SNA Short Number Addressing
SS-TPI Talking Party Identification
3.4 Functional Entities (FE)
The functional model for each supplementary service is comprised of a number of FEs. The FEs below should always
have the following definitions:
• FE1 served user's service agent;
• FE2 SwMI service control functional entity;
• FE3 authorized user's service agent;
• FE5 service agent of the user affected by service operation;
• FE6 service agent of second listening party;
• FE7 service agent of dispatcher (in the case of SS-CAD) or of monitoring user (in the case of SS-DL);
• FE8 service agent of user removed from a call during a pre-emptive priority call;
• FE9 service agent of user informed that another user has been removed from a call during a pre-emptive
priority call;
• FE10 service agent of user affected by management functions.
FE2, the SwMI functional entity, may be split into secondary FEs when needed for a given supplementary service.
These FEs are called FE2x in the corresponding stage 2 description (in the related ETSI EN/ETS 300 392-11 [8]).
4 Supplementary service concepts
4.1 Stage 1, 2 and 3 descriptions
4.1.0 General Description
Supplementary service descriptions are covered in 3 stages according to the method described in Recommendation
ITU-T I.130 [13], each stage in a separate document. The contents of each stage description are described in the
following clauses.
4.1.1 Stage 1 description
This stage is the overall service description from the user viewpoint and also details the interaction of the service with
other supplementary services.
4.1.2 Stage 2 description
Stage 2 identifies the functional capabilities and the information flows needed to support the supplementary service as
specified in its stage 1 description. It defines the FEs, the information flow between these entities, the FE actions and
the allocation of FEs to physical locations.
ETSI
12 ETSI EN 300 392-9 V1.7.1 (2020-04)
4.1.3 Stage 3 description
The stage 3 description specifies the signalling protocols needed to implement the service. The present document
addresses the encoding of the service Protocol Data Units (PDU) and of the related information elements, the protocol
procedures and the corresponding SDL diagrams.
NOTE: According to Recommendation ITU-T I.130 [13], the stage 3 description of any telecommunication
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. The latter have not been provided
since they can be derived from the specification of the FE actions in the stage 2 description.
Service management procedures specified in the above stages (e.g. activation or interrogation) are optional unless
otherwise stated in the specific supplementary service stage documents.
4.2 Concepts associated with supplementary services
The terms used to define the procedures associated with supplementary services are given in ETSI EN 300 392-1 [1],
clause 14.3.1.
5 Service primitives
5.1 Service primitive general description
Primitives are specified for each supplementary service at the TNSS Service Access Point (TNSS-SAP), in a specific
clause of the corresponding stage 3 description in ETSI EN/ETS 300 392-12 [9].
Primitive names shall take the form of TNSS-service-name type where:
• service - supplementary service identifier;
• name - indicates the type of function this primitive is performing (e.g. DEFINE);
• type - indicates whether the primitive is a request, confirm, indication or response.
For example, an INTERROGATE request primitive for the supplementary service Ambience Listening (SS-AL) would
be specified as TNSS-AL-INTERROGATE request, when primitives of more than one supplementary service are used
in the same document. When a document refers only to one supplementary service the short form such as
INTERROGATE request may be used.
Parameters are listed with mandatory and conditional parameters first, followed by optional parameters. Repeatable
parameters are identified by a comment in the remarks column in the table specifying the primitive's parameters.
Following the specifications of a service's primitives, there is a parameter description section listing alphabetically all
primitive parameters used in this service and the values allowed.
Among those parameters, special mention is to be made of the parameter access priority. This parameter has to be
included in every service primitive request or response, since the priority defined for the corresponding air interface
(uplink) PDUs is set according to the its value (i.e. low, high or emergency priority as seen by the user application of
"0" to "7" as defined in the lower layer service primitives).
NOTE: For call related services the TNSS-SAP and TNCC-SAP logically form a combined SAP defining access
to the total service. Some of the supplementary service parameters are actually defined as TNCC-SAP
parameters.
ETSI
13 ETSI EN 300 392-9 V1.7.1 (2020-04)
5.2 Notification service primitive
Many of the air interface PDUs can carry supplementary service-related information in special information element
notification. The notification information element values are used by many supplementary services to carry information
to the equipment not supporting the specific supplementary service. The information in the notification information
element may be displayed to the user in some format, e.g. in natural language or as a number code.
The information is presented to the user application via TNSS-SAP using service primitive NOTIFICATION indication.
The notification information element values are defined in clause 7.2.2. The same values are used as parameter values
in the NOTIFICATION indication primitive.
6 Supplementary service invocation order
Before allowing an outgoing call from a calling user to proceed towards the called user, or before offering an incoming
call to the called user, the SwMI shall search through the user supplementary service database for supplementary
services activated and proceed with their invocation in the order detailed in table 1. Due to the interactions specified
between supplementary services, the invocation of some of those listed in table 1 may result in the invocation of others
further below in that list being overridden although they have been activated, e.g. SS-CAD overrides SS-BIC.
Table 1: Supplementary service invocation order
Incoming calls Outgoing calls
PPC SNA
PC PPC
CAD CAD (see note 1)
BIC BOC
CFU AS
CW PC (see note 1)
CFB
CFNRy (see note 2)
CFNRc
NOTE 1: If SS-PC has been invoked for a call and if SS-CAD for outgoing call is
invoked for that call and operated with diversion towards a dispatcher
registered in another SwMI, SS-PC shall also be invoked for this diversion.
NOTE 2: If the called user is busy, SS-CFNRy may only be invoked if SS-CW has been
previously invoked. But the SS-CFNRy operation shall take precedence over
further SS-CW operation when the CFNRy no-reply timer has elapsed.
7 Transfer of information related to supplementary
service at the MS interface
7.1 Methods of transportation
There are 4 methods by which information related to supplementary service may be transferred at the MS interface:
• using the facility information element in a basic service PDU;
• using specific elements in a basic service PDU (e.g. Area Selection (SS-AS) in a U-SETUP PDU);
• using the Notification indicator information element in a basic service PDU;
• using a U/D-FACILITY PDU.
The first 3 methods may be used to send call related SS PDUs. The forth method is used to send call unrelated
SS PDUs.
NOTE: See definition of call related and call services unrelated in clause 3.1.
ETSI
14 ETSI EN 300 392-9 V1.7.1 (2020-04)
7.2 Call related service information
7.2.1 Facility information element general construction
The facility information element is a type 3 CC PDU element as defined in clause 14.7 of ETSI EN 300 392-2 [2]. It is
used to convey call related supplementary service PDUs (SS PDUs) across the air interface and is present in all
CC PDU definitions (except U/D-FACILITY). Each SS PDU is encoded as stated in clause 8.
The encoding rules defined in annex E of ETSI EN 300 392-2 [2] shall apply for the definition of the facility
information element. Notably according to clause 14.8.48 of ETSI EN 300 392-2 [2], the value of the corresponding
type 3 element identifier will be equal to the binary value 0011 .
The contents of the facility information element in an uplink CC PDU shall be as defined in table 2.
Table 2: Uplink facility information element contents
Information sub-element Length C/O/M Remarks
Routeing 2 M See note 1
MNI 24 C See note 2
SS PDU Variable M See note 3
NOTE 1: The meaning of the information sub-element routeing shall be the following:
- same SwMI, if its binary value is equal to 00 ;
- end SwMI, if its binary value is equal to 01 ;
- home SwMI of called ITSI/GTSI, if its binary value is equal to 10 ;
- other SwMI indicated by its MNI value, if its binary value is equal to 11 .
NOTE 2: Shall be present if the binary value of the information sub-element routeing is equal to 11 .
NOTE 3: See clause 8.
NOTE: Since SS PDUs are not specified in table 2 as being repeatable, this means that as many different facility
information elements will be needed in a CC PDU as there are SS PDUs to be conveyed.
The contents of a facility information element in a downlink CC PDU shall be the same as that defined in table 2 except
for that there shall be no information sub-element routeing and no information sub-element MNI.
ETSI
15 ETSI EN 300 392-9 V1.7.1 (2020-04)
7.2.2 Notification indicator information element
The notification indicator information element values that may be used shall be as shown in table 3. When, in a
situation, more than one notification indicator value is applicable the SwMI may choose the most appropriate and reject
the other values or it may send additional PDUs containing the other notification indicator values.
Table 3: Notification indicator information element contents
Information element Length Value Remarks
Notification indicator 6 0 LE broadcast
1 LE acknowledgement
2 LE paging
3 AL operation (see note 1)
4 Call barred by SS-BIC
5 Call barred by SS-BOC
6 Call is forwarded (diverting)
7 Forwarding (diversion) activated
8 Identity presentation restricted
9 Presentation restriction overridden
10 Call waiting invoked
11 Call put on hold (remote hold)
12 Call on hold retrieved (remote retrieval)
13 Include call (see note 2)
14 Multiparty call (see note 3)
15 LSC invoked
16 Call rejected due to SS-AS
17 SS-AS not invoked/supported
18 Called user alerted
19 Called user connected
20 Call proceeding
21 SS-CFU invoked
22 SS-CFB invoked
23 SS-CFNRy invoked
24 SS-CFNRc
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...