SIST EN 300 392-9 V1.3.1:2006

• Abstract:

  The present document defines principles and requirements generally applicable to the stage 2 and 3 descriptions of supplementary services for the Terrestrial Trunked Radio (TETRA). The present document is applicable to any TETRA terminal equipment (Mobile Station (MS) or Line Station (LS) 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.

• Status: Published
• Publication Date: 31-Mar-2006
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2006
• Due Date: 01-Apr-2006
• Completion Date: 01-Apr-2006
• Ref Project: ETSI EN 300 392-9 V1.3.1 (2004-11) - Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9: General requirements for supplementary services

SIST EN 300 392-9 V1.3.1:2006 is the Slovene adoption of ETSI EN 300 392-9 Version 1.3.1 for Terrestrial Trunked Radio (TETRA) Voice plus Data (V+D). It specifies general principles and requirements for TETRA supplementary services at stage 2 and stage 3, including how supplementary service information is carried, routed and encoded for Mobile Station (MS), Line Station (LS) and Switching and Management Infrastructure (SwMI) implementations.

What does SIST EN 300 392-9 V1.3.1:2006 specify?

SIST EN 300 392-9 V1.3.1:2006 defines common rules for TETRA supplementary services rather than a single service. It is used when a terminal or network supports at least one Supplementary Service (SS), and it also covers routeing of supplementary service information across the Voice plus Data (V+D) Inter-System Interface (ISI).

The document is organized as a framework for later service-specific stage 2 and stage 3 descriptions. Its main clauses cover scope, references, definitions and abbreviations, service concepts, service primitives, invocation order, transport at the MS interface, SS PDU contents, routeing, ANF-ISISS, exceptional cases, generic activation/deactivation/definition/interrogation procedures, and authentication issues.

Annex	What it covers
Annex A	Definition of the ISI ROSE operation
Annex B	Examples of ANF-ISISS ROSE APDUs and PSS1 messages
Annex C	Suggested introduction for SDL representation of call-related and call-unrelated procedures
Annex D	Change requests

What are the key requirements of SIST EN 300 392-9 V1.3.1:2006?

Clause 1 limits the scope to general principles and requirements for supplementary services in TETRA, and it applies to MS, LS and SwMI implementations that support at least one SS. In practice, this means terminal and network designers use this part as the common rules base for supplementary services, especially when systems must interwork.

Clause 3 defines the roles that matter in supplementary service handling, such as authorized user, served user and affected user, and it introduces the functional entity model FE1 to FE10. This matters because the rest of the standard describes who initiates, controls, receives and is affected by a service operation.

Service description and primitives

Clause 4 explains that supplementary services are described in three stages, following ITU-T Recommendation I.130, and that service management procedures are optional unless a specific service document says otherwise. Clause 5 then defines service primitives at the TNSS-SAP, with names formed from the service name and primitive type. For implementers, this sets the interface contract between the user application and the service logic.

Clause 5 also makes access priority a mandatory parameter in every service primitive request or response. The standard links that value to the priority used for uplink PDUs, so implementations must carry it through to the air interface behavior.

Invocation order and transfer at the MS interface

Clause 6 gives the order in which the SwMI checks activated supplementary services before allowing an outgoing call or offering an incoming call. The order matters because some services override others, for example SS-CAD can override SS-BIC, and SS-CFNRy has special interaction with SS-CW. In practice, this tells network logic which service gets first chance to act.

Clause 7 defines four ways to transfer supplementary service information at the MS interface: a facility information element in a basic service PDU, specific elements in a basic service PDU, the Notification indicator information element, and an U/D-FACILITY PDU. Call unrelated SS PDUs are carried only in an U/D-FACILITY PDU, which may contain more than one SS PDU and may also contain proprietary information elements.

SS PDU structure and encoding

Clause 8 defines the structure of SS PDUs. The first two elements are SS type and SS PDU type, and the clause provides the common encoding rules for repeated information elements, user identity, character string, external number, external call restriction, failure values and manufacturer identification. This is the part that implementers use to build interoperable protocol messages.

Clause 8.2 also defines the main error responses: supplementary service not supported, action not supported and ISI problem. For equipment behavior, that means a terminal or SwMI can tell whether the service itself is unsupported, only one action is unsupported, or the problem happened while using the ISI.

Routeing and interworking

Clause 9 states that a compliant SwMI shall route SS PDUs received at the air or LS interface either internally or toward a destination SwMI, according to the routeing information element. When routeing over the ISI is needed, the SwMI uses ANF-ISISS. This is the key clause for multi-network TETRA installations.

Clause 10 defines ANF-ISISS as the service used by supplementary service control entities in different SwMIs. It specifies the service primitives ISI SS INFORMATION request/indication and the optional response/confirm, and it describes how call related and call unrelated ANF-ISISS PDUs are formed and transported over PSS1 signalling. Clause 10 also explains how source and destination entities are identified when the SS PDU crosses the ISI.

Exceptional cases, management procedures and authentication

Clause 11 covers exceptional cases such as a target MS no longer being registered, a target group no longer being attached, unsupported SS PDUs in the destination SwMI, or protocol errors on the ISI. That matters for fault handling, because the source SwMI may receive ReturnError or Reject APDUs depending on the case.

Clauses 12 and 13 deal with activation/deactivation, definition and interrogation, and with authentication requirements for specific supplementary services. Table 28 in clause 13 is the practical checklist for deciding whether a service operation needs authentication and how security class can be used to meet those requirements.

What terms does SIST EN 300 392-9 V1.3.1:2006 define?

• Switching and Management Infrastructure (SwMI) - the TETRA network entity that controls service behavior and routes supplementary service information.
• Mobile Station (MS) - the TETRA terminal equipment used by a mobile user.
• Line Station (LS) - a TETRA terminal in line-station form, treated alongside MS in this standard.
• Supplementary Service (SS) - an additional service layered on top of the basic TETRA service.
• Additional Network Feature - Inter-System Interface Supplementary Service (ANF-ISISS) - the inter-system feature used to carry SS PDUs between SwMIs.
• Call related - information conveyed with a call reference that has an associated user-information connection.
• Call unrelated - information conveyed without a call reference that has an associated user-information connection.
• Protocol Data Unit (PDU) - the encoded protocol message unit used for air interface and ISI signalling.

Who uses SIST EN 300 392-9 V1.3.1:2006?

This standard is used by TETRA network operators, SwMI manufacturers, terminal designers and system integrators. It is especially relevant to engineers who implement supplementary services, routeing and inter-system signalling, and to quality teams checking interoperability between terminals and networks.

It is also useful for buyers and technical evaluators who need to know whether a product supports TETRA supplementary services, how those services are signalled, and what interworking behavior is expected across the ISI.

What changed in SIST EN 300 392-9 V1.3.1:2006 from the previous edition?

Annex D records change requests that led to this version, including updates to the Notification indicator set, new SS-CF values, mnemonic name presentation, support for characters beyond UCS-2 encoding, handling of SS PDU type responses, and additional notifications such as called user alerted and notice of imminent call disconnection. The document history lists earlier publications in V1.1.1, V1.2.1, V1.3.0 and this V1.3.1 publication.

Which standards are used with SIST EN 300 392-9 V1.3.1:2006?

The standard depends on the rest of the TETRA V+D series and on several signalling and encoding references. The most important are:

• EN 300 392-1 - general network design and core TETRA definitions.
• EN 300 392-2 - air interface rules, PDU encoding and basic transport rules.
• EN 300 392-3-1 - general ISI design, including ROSE/APDU handling and signalling connection behavior.
• EN 300 392-3-2 and EN 300 392-3-3 - ANF-ISIIC and ANF-ISIGC support for inter-system call handling.
• EN 300 392-7 - security, including the security class note used in clause 13.
• EN 300 392-10-6, EN 300 392-11 and EN 300 392-12 - the stage 1, stage 2 and stage 3 supplementary service documents that this part supports.
• ISO/IEC 11571, 11572 and 11582 - numbering, circuit-mode signalling and supplementary service protocol rules used in routeing and service behavior.
• ITU-T I.130, E.164, X.121, X.219, X.229 and Z.100 - service characterization, numbering plans, remote operations and SDL.
• ISO/IEC 8859-1 to 8859-15 and ISO/IEC 10646 - character set references used for character string encoding.

What does the SIST EN 300 392-9 V1.3.1:2006 document contain?

The document contains formal definitions, primitive naming rules, routeing rules, PDU layouts and encoding rules for supplementary services. It also includes a notification indicator table, SS type and SS PDU type tables, repeated-element handling, identity and number encoding rules, and routeing models for call related and call unrelated SS traffic.

Annex A provides a formal ROSE operation definition for ISI encoding. Annex B gives worked examples of how ANF-ISISS ROSE APDUs appear in PSS1 FACILITY and SETUP messages. Annex C gives text intended for SDL representation of call-related and call-unrelated procedures, and Annex D records the change requests that shaped this version.

SLOVENSKI STANDARD
01-april-2006
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: EN 300 392-9 Version 1.3.1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 9: General requirements for supplementary services

2 ETSI EN 300 392-9 V1.3.1 (2004-11)

Reference
REN/TETRA-03130
Keywords
supplementary service, TETRA, V+D
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

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

© European Telecommunications Standards Institute 2004.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 300 392-9 V1.3.1 (2004-11)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
3 Definitions, abbreviations and Functional Entities (FE) .9
3.1 Definitions.9
3.2 Abbreviations.9
3.3 Functional Entities (FE) .11
4 Supplementary service concepts .11
4.1 Stage 1, 2 and 3 descriptions .11
4.1.1 Stage 1 description.11
4.1.2 Stage 2 description.11
4.1.3 Stage 3 description.11
4.2 Concepts associated with supplementary services .12
5 Service primitives.12
5.1 Service primitive general description.12
5.2 Notification service primitive.12
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 information.13
7.2.1 Facility information element general construction .14
7.2.2 Notification indicator information element.14
7.3 Call unrelated supplementary service information .15
8 SS PDU contents .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 elements.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.1 SS PDU addressed individually by a SwMI to an MS.29
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
9.3.1 Call related SS PDUs.30
9.3.2 Call unrelated SS PDUs.30
10 ANF-ISISS.31
10.1 Service model.31
ETSI
4 ETSI EN 300 392-9 V1.3.1 (2004-11)
10.2 Service primitives.32
10.3 Protocol.32
10.3.1 General.32
10.3.2 Possible groupings of ISI SS PDUs and of invoked ANF-ISISSs .35
10.3.3 Interpretation APDU.36
11 Exceptional cases.37
11.1 ISI exceptional cases .37
11.1.1 Case a).37
11.1.1.1 Call unrelated ANF-ISISS PDU.38
11.1.1.2 Call related ANF-ISISS PDU.38
11.1.2 Case b).38
11.1.3 Case c).39
11.1.4 Case d).39
11.1.4.1 Cases d.1) and d.2).39
11.1.4.2 Case d.3).40
11.2 Exceptional cases at the air (or LS) interface .40
11.2.1 No ISI involved.40
11.2.2 ISI involved.41
12 Generic specification of activation/deactivation, definition and interrogation operations.42
12.1 Stage 2 description .42
12.2 Stage 3 description .42
13 Authentication issues.43
13.1 Authentication requirements for TETRA supplementary services.43
13.2 The use of security class to meet authentication requirements for TETRA supplementary services .43
13.2.1 Class 1.44
13.2.2 Class 2.44
13.2.3 Class 3.44
13.2.4 Impact of ISI.44
13.2.5 Security of data within a SwMI .44
Annex A (informative): Definition of the ISI ROSE operation .45
Annex B (informative): Examples of inclusion of ANF-ISISS ROSE APDUs or PSS1
messages.48
B.1 Call unrelated PSS1 FACILITY message .48
B.2 Call related PSS1 FACILITY message .50
B.3 ANF-ISIIC PSS1 basic call message.50
Annex C (informative): Introduction suggested to an annex on SDL representation of call-
related and call-unrelated procedures .52
Annex D (informative): Change requests .53
History .54

ETSI
5 ETSI EN 300 392-9 V1.3.1 (2004-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Project Terrestrial Trunked Radio
(TETRA).
The present document is part 9 of a multi-part deliverable covering Voice plus Data (V+D), as identified below:
EN 300 392-1: "General network design";
EN 300 392-2: "Air Interface (AI)";
EN 300 392-3: "Interworking at the Inter-System Interface (ISI)";
ETS 300 392-4: "Gateways basic operation";
EN 300 392-5: "Peripheral Equipment Interface (PEI)";
EN 300 392-7: "Security";
EN 300 392-9: "General requirements for supplementary services";
EN 300 392-10: "Supplementary services stage 1";
EN 300 392-11: "Supplementary services stage 2";
EN 300 392-12: "Supplementary services stage 3";
ETS 300 392-13: "SDL model of the Air Interface (AI)";
ETS 300 392-14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
TS 100 392-15: "TETRA frequency bands, duplex spacings and channel numbering";
TS 100 392-16: "Network Performance Metrics";
TS 100 392-17: "TETRA V+D and DMO Release 1.1 specifications".
NOTE: 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.

ETSI
6 ETSI EN 300 392-9 V1.3.1 (2004-11)
National transposition dates
Date of adoption of this EN: 26 November 2004
Date of latest announcement of this EN (doa): 28 February 2005
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 August 2005
Date of withdrawal of any conflicting National Standard (dow): 31 August 2005

ETSI
7 ETSI EN 300 392-9 V1.3.1 (2004-11)
1 Scope
The present document defines principles and requirements generally applicable to the stage 2 and 3 descriptions of
supplementary services for the Terrestrial Trunked Radio (TETRA).
The present document is applicable to any TETRA terminal equipment (Mobile Station (MS) or Line Station (LS) 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
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] 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-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 1: General design".
[4] ETSI EN 300 392-3-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 2: Additional Network Feature
Individual Call (ANF-ISIIC)".
[5] ETSI EN 300 392-3-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI); Sub-part 3: Additional Network Feature
Group Call (ANF-ISIGC)".
[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/ETSI ETS 300 392-11 (all parts): "Terrestrial Trunked Radio (TETRA); Voice plus Data
(V+D); Part 11: Supplementary services stage 2".
[9] ETSI EN/ETSI 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] ISO/IEC 11572: "Information technology - Telecommunications and information exchange
between systems - Private Integrated Services Network - Circuit mode bearer services -
Inter-exchange signalling procedures and protocol".
ETSI
8 ETSI EN 300 392-9 V1.3.1 (2004-11)
[12] ISO/IEC 11582: "Information technology - Telecommunications and information exchange
between systems - Private Integrated Services Network - Generic functional protocol for the
support of supplementary services - Inter-exchange signalling procedures and protocol".
[13] ITU-T Recommendation I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[14] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[15] ITU-T Recommendation X.121: "International numbering plan for public data networks".
[16] ITU-T Recommendation X.219 (1988): "Remote Operations: Model, notation and service
definition".
[17] ITU-T Recommendation X.229 (1988): "Remote Operations: Protocol specification".
[18] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".
[19] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Designers' guide; Part 5: Guidance on Numbering and addressing".
[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 8859-1: "Information technology - 8-bit single-byte coded graphic character sets -
Part 1: Latin alphabet No. 1".
[22] ISO/IEC 8859-2: "Information technology - 8-bit single-byte coded graphic character sets -
Part 2: Latin alphabet No. 2".
[23] ISO/IEC 8859-3: "Information processing - 8-bit single-byte coded graphic character sets -
Part 3: Latin alphabet No. 3".
[24] ISO/IEC 8859-4: "Information processing - 8-bit single-byte coded graphic character sets -
Part 4: Latin alphabet No. 4".
[25] ISO/IEC 8859-5: "Information technology - 8-bit single-byte coded graphic character sets -
Part 5: Latin/Cyrillic alphabet".
[26] ISO/IEC 8859-6: "Information technology - 8-bit single-byte coded graphic character sets -
Part 6: Latin/Arabic alphabet".
[27] ISO/IEC 8859-7: "Information technology - 8-bit single-byte coded graphic character sets -
Part 7: Latin/Greek alphabet".
[28] ISO/IEC 8859-8: "Information technology - 8-bit single-byte coded graphic character sets -
Part 8: Latin/Hebrew alphabet".
[29] ISO/IEC 8859-9: "Information technology - 8-bit single-byte coded graphic character sets -
Part 9: Latin alphabet No. 5".
[30] ISO/IEC 8859-10: "Information technology - 8-bit single-byte coded graphic character sets -
Part 10: Latin alphabet No. 6".
[31] ISO/IEC 8859-13: "Information technology - 8-bit single-byte coded graphic character sets -
Part 13: Latin alphabet No. 7".
[32] ISO/IEC 8859-14: "Information technology - 8-bit single-byte coded graphic character sets -
Part 14: Latin alphabet No. 8 (Celtic)".
[33] ISO/IEC 8859-15: "Information technology - 8-bit single-byte coded graphic character sets -
Part 15: Latin alphabet No. 9".
[34] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set (UCS)".
ETSI
9 ETSI EN 300 392-9 V1.3.1 (2004-11)
3 Definitions, abbreviations and Functional Entities
(FE)
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 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
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: property of information which is conveyed across the Q reference point (as defined in clause 4.3.3 of
T
EN 300 392-1 [1] which uses a call reference which has an associated user-information connection (definition derived
from that of the same term in clause 4.9 of ISO/IEC 11582 [12]
call unrelated: property of information which is conveyed across the Q reference point (as defined in clause 4.3.3 of
T
EN 300 392-1 [1] which does not use a call reference which has an associated user-information connection (definition
derived from that of "call independent" in clause 4.8 of ISO/IEC 11582 [12]
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 just above.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AL Ambience Listening
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
AP Access Priority
AS Area Selection
BIC Barring of Incoming Calls
BOC Barring of Outgoing Calls
CAD Call Authorized by Dispatcher
CCBS Call Completion to Busy Subscriber
CCNR Call Completion on No Reply
CF Call Forwarding
CI Call Identification
CR Call Report
CRT Call ReTention
CW Call Waiting
DGNA Dynamic Group Number Assignment
DL Discreet Listening
ETSI
10 ETSI EN 300 392-9 V1.3.1 (2004-11)
FE Functional Entity
GSSI Group Short Subscriber Identity
GTSI Group TETRA Subscriber Identity
HOLD call Hold
IC Include Call
ITSI Individual TETRA Subscriber Identity
LE Late Entry
LS Line Station
LSC List Search Call
MNI Mobile Network Identity
MS Mobile Station
MS-ISDN Mobile Station ISDN number
PC Priority Call
PDU Protocol Data Unit
PISN Private Integrated Services Network
PPC Pre-emptive Priority Call
SAP Service Access Point
SDL (Functional) Specification and Description Language
SNA Short Number Addressing
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
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-CFB Call Forwarding on Busy
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/Connected Line Identification Restriction
SS-COLP Connected Line Identification Presentation
SS-CR Call Report
SS-CW Call Waiting
SS-DGNA Dynamic Group Number Assignment
SS-DL Discreet Listening
SS-IC Include Call
SS-PC Priority Call
SS-SNA Short Number Addressing
SS-TPI Talking Party Identification
SwMI Switching and Management Infrastructure
TNCC-SAP TETRA Network layer Call Control - Service Access Point
TNSS-SAP TETRA Network layer Supplementary Service - Service Access Point
TPI Talking Party Identification
UCS-2 Universal Character Set coded in 2 octets
ISSI Individual Short Subscriber Identity
UTF-16BE Unicode Transformation Format serialized as two bytes in Big-Endian format
V+D Voice plus Data
ETSI
11 ETSI EN 300 392-9 V1.3.1 (2004-11)
3.3 Functional Entities (FE)
The functional model for each supplementary service shall be 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 EN/ETS 300 392-11 [8]). An
example of this splitting is given in clause C.1.1.
4 Supplementary service concepts
4.1 Stage 1, 2 and 3 descriptions
Supplementary service descriptions are covered in 3 stages according to the method described in
ITU-T Recommendation 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.
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 ITU-T Recommendation 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.
ETSI
12 ETSI EN 300 392-9 V1.3.1 (2004-11)
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 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 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.
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.
ETSI
13 ETSI EN 300 392-9 V1.3.1 (2004-11)
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 an U/D-FACILITY PDU.
7.2 Call related information
The first 3 methods in clause 7.1 may be used to send call related SS PDUs.
NOTE: See definition of call related in clause 3.1.
ETSI
14 ETSI EN 300 392-9 V1.3.1 (2004-11)
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 EN 300 392-2 [2]. It is used
to convey call related supplementary service PDUs (SS PDUs) across the air (or LS) 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 clause 14.7 of EN 300 392-2 [2] shall apply for the definition of the facility information
element. Notably according to table 132 of 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 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 element routeing shall be the following:
- same SwMI, if its binary value is equal to 002;
- end SwMI, if its binary value is equal to 012;
- home SwMI of called ITSI/GTSI, if its binary value is equal to 102;
- other SwMI indicated by its MNI value, if its binary value is equal to 112.
The binary value 102 is reserved.
NOTE 2: Shall be present if the binary value of the information element routeing is equal to 112.
NOTE 3: See clause 8.
NOTE: Since SS PDUs are not specified in the above 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 element routeing.
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.
ETSI
15 ETSI EN 300 392-9 V1.3.1 (2004-11)
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 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 EN 300 392-2 [2], when an
SwMI receives such information element in a (call related) ISI PDU, it will relay it to the MS.
7.3 Call unrelated supplementary service information
All call unrelated SS PDUs are transported using an U/D-FACILITY PDU.
NOTE: See definition of call unrelated in clause 3.1.
The U/D-FACILITY PDU is used to convey only call unrelated SS PDUs across the air (or LS) 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 clause 14.7 of 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
16 ETSI EN 300 392-9 V1.3.1 (2004-11)
Table 4: U-FACILITY PDU contents
Information element Length Type C/O/M Remarks
PDU type 5 1 M (See note 1)
Routeing 2 1 M (See note 2)
MNI 24 1 C (See note 3)
Number of SS PDUs 4 1 M (See note 4)
Length indicator 11 1 C (See notes 5 and 6)
SS PDU contents variable 1 C (See notes 5, 7 and 8)
Proprietary variable 3 O (see note 4) (See note 9)
NOTE 1: Equal to the binary value 10000 , as defined in table 114 of EN 300 392-2 [2].
NOTE 2: The meaning of the information element routeing shall be the following:
- same SwMI, if its binary value is equal to 002;
- home SwMI of the sending MS, if its binary value is equal to 012;
- other SwMI indicated by its MNI value, if its binary value is equal to 112.
The binary value 102 is reserved.
NOTE 3: Shall be present if the binary value of the information element routeing is equal to 112.
NOTE 4: The value of the information element number of SS PDUs shall be equal at least to one when no
proprietary information element is present. Conversely, if it is equal to 0, at least one proprietary
information element has to be present.
NOTE 5: Shall be conditional on the value of the information element number of SS PDUs being different from 0.
Shall be repeated as a set according to the value of the information element number of SS PDUs when
this value is larger than 1.
NOTE 6: The value of the information element length indicator defines the length in bits of the contents of the next
SS PDU. There is neither O-bit nor M-bit between the SS PDUs.
NOTE 7: See clause 8.
NOTE 8: If there is at least one SS PDU, then only the last SS PDU is followed by O-bit indicating whether any
type 3/4 element will follow. If there is no SS PDU as indicated by the number of SS PDUs value 0, then
the number o
...