SIST ETS 300 392-12-3 E1:2003

SLOVENSKI STANDARD
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$±*RYRULQSRGDWNL9'±GHO'RSROQLOQH
VWRULWYHVWRSQMH±SRGGHO,GHQWLILNDFLMDJRYRUHþHJDXGHOHåHQFD73,
Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 12: Supplementary
services stage 3; Sub-part 3: Talking Party Identification (TPI)
Ta slovenski standard je istoveten z: ETS 300 392-12-3 Edition 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 ETS 300 392-12-3
TELECOMMUNICATION August 1999
STANDARD
Source: TETRA Reference: DE/TETRA-03001-12-03
ICS: 33.020
Key words: TETRA, V+D
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 12: Supplementary services stage 3;
Sub-part 3: Talking Party Identification (TPI)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1999. All rights reserved.

Page 2
ETS 300 392-12-3: August 1999
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 392-12-3: August 1999
Contents
Foreword .7
1 Scope .9
2 References.9
3 Definitions and abbreviations.10
3.1 Definitions .10
3.2 General abbreviations.11
3.3 Supplementary service abbreviations.11
4 SS-TPI service description.11
4.1 General .11
4.2 SS-TPI services offered over the TNSSSAP.12
4.2.1 ACTIVATE indication.12
4.2.2 ACTIVATE request.13
4.2.3 DEFINE indication.13
4.2.4 DEFINE request .14
4.2.5 INFORM indication.14
4.2.6 INTERROGATE indication .14
4.2.7 INTERROGATE request .15
4.2.8 INTERROGATE BY NAME indication.15
4.2.9 INTERROGATE BY NAME request .16
4.3 Parameter description.16
5 Signalling protocol for the support of SS-TPI.19
5.1 SS-TPI operational requirements .19
5.1.1 Served user MS/LS .19
5.1.2 Group controlling SwMI.19
5.1.3 Served user SwMI.19
5.1.4 Talking/sending user SwMI .19
5.1.5 Authorized user MS/LS .19
5.1.6 Authorized user SwMI .20
5.1.7 Managed user home SwMI .20
5.2 Coding requirements .20
5.2.1 SS-TPI PDUs .20
5.2.1.1 ACTIVATE PDU .20
5.2.1.2 ACTIVATE ACK PDU.21
5.2.1.3 DEFINE PDU.21
5.2.1.4 DEFINE ACK PDU .23
5.2.1.5 INFORM PDU.23
5.2.1.6 INTERROGATE PDU.26
5.2.1.7 INTERROGATE ACK PDU.27
5.2.1.8 INTERROGATE BY NAME PDU.28
5.2.1.9 INTERROGATE BY NAME ACK PDU .29
5.2.1.10 NAME REQ PDU.29
5.2.1.11 NAME ACK PDU .30
5.2.1.12 NAME REQ BIS PDU.31
5.2.1.13 TX PRIORITY REQUEST PDU.31
5.2.1.14 TX DEMAND PRIORITY PDU.31
5.2.2 TETRA PDU information element coding .31
5.2.2.1 Activated/defined/interrogated party short number
address.31
5.2.2.2 Activated/defined/interrogated/talking/sending party short
subscriber identity.31
5.2.2.3 Activated/defined/interrogated/talking/sending party
extension .31

Page 4
ETS 300 392-12-3: August 1999
5.2.2.4 Activation failure cause.32
5.2.2.5 Activation request .32
5.2.2.6 Activation result.32
5.2.2.7 Activation state.33
5.2.2.8 Address type of
activated/defined/interrogated/talking/sending party.33
5.2.2.9 Character set .33
5.2.2.10 Definition failure cause.34
5.2.2.11 Definition result .34
5.2.2.12 External talking/sending party number length indicator .34
5.2.2.13 External talking/sending party number digits .34
5.2.2.14 Interrogation failure cause .35
5.2.2.15 Interrogation by name failure cause.35
5.2.2.16 Interrogation result.36
5.2.2.17 Multiple user mask and Multiple user mask present.36
5.2.2.18 Mnemonic name character string .36
5.2.2.19 Mnemonic name information .36
5.2.2.20 Mnemonic name length indicator.36
5.2.2.21 Range type for activated/defined/interrogated
party/parties or for mnemonic name/names .36
5.2.2.22 SS-CLIR invoked for talking/sending party .36
5.2.2.23 TPI PDU type .37
5.2.2.24 TX demand priority.37
5.2.2.25 SS-TPI profile.38
5.2.2.26 SS-TPI profile ACK information element .38
5.2.3 Additional coding requirements over the ISI.38
5.3 SS-TPI state definitions.39
5.3.1 States at the served user MS/LS.39
5.3.2 States at the group controlling SwMI.39
5.3.2.1 State for SS-TPI activation, deactivation, definition or
interrogation .39
5.3.2.2 States for SS-TPI invocation and operation.39
5.3.2.2.1 TPI-Idle.39
5.3.2.2.2 TPI-Activated.39
5.3.2.2.3 TPI-Option-TX-Priority.39
5.3.2.2.4 TPI-Option-Name.39
5.3.2.2.5 TPI-Options-Name-and-TX-Priority.40
5.3.2.2.6 TPI-Option-Name-Caller-Name-
Waiting .40
5.3.2.2.7 TPI-Options-Name-and-TX-Priority-
Caller-Name-Waiting.40
5.3.3 Served user SwMI .40
5.3.3.1 TPI-Idle .40
5.3.3.2 TPI-Activated .40
5.3.3.3 TPI-Option-TX-Priority .40
5.3.3.4 TPI-Option-Name-Requested .40
5.3.3.5 TPI-Options-Name-and-TX-Priority .40
5.3.4 Talking/sending user SwMI .40
5.3.4.1 TPI-Idle .41
5.3.4.2 TPI-Name-Requested.41
5.3.4.3 TPI-TX-Priority-Requested.41
5.3.5 Authorized user MS/LS.41
5.3.6 Authorized user SwMI.41
5.3.7 Managed user home SwMI.41
5.4 SS-TPI signalling procedures.41
5.4.1 Actions at the served user MS/LS .41
5.4.1.1 Normal procedures .41
5.4.1.2 Exceptional procedures .43
5.4.2 Actions at the group controlling SwMI .43
5.4.2.1 Normal procedures .43
5.4.2.2 Exceptional procedures .45
5.4.3 Actions at the served user SwMI .46
5.4.3.1 Normal procedures .46

Page 5
ETS 300 392-12-3: August 1999
5.4.3.1.1 Individual call .46
5.4.3.1.2 Group call .47
5.4.3.2 Exceptional procedures.48
5.4.4 Actions at the talking/sending user SwMI.49
5.4.4.1 Normal procedures.49
5.4.4.1.1 Group call .49
5.4.4.1.2 Individual call .49
5.4.4.2 Exceptional procedures.50
5.4.5 Actions at authorized user MS/LS.50
5.4.5.1 Normal procedures.50
5.4.5.2 Exceptional procedures.50
5.4.6 Actions at the authorized user SwMI.51
5.4.7 Actions at the managed user home SwMI .51
5.4.7.1 Normal procedures.51
5.4.7.1.1 Case where the managed user home
SwMI coincides with the authorized
user SwMI.51
5.4.7.1.2 Case where the managed user home
SwMI is different from the authorized
user SwMI.51
5.4.7.2 Exceptional procedures.52
5.5 SS-TPI impact of interworking with other networks .52
5.6 Protocol interactions between SS-TPI and other supplementary services and ANFs.53
5.6.1 Interaction with Calling Line Identification Presentation (SS-CLIP).53
5.6.2 Interactions with Calling/Connected Line Identification Restriction (SS-
CLIR).53
5.6.3 Interactions with Call Authorized by Dispatcher (SS-CAD).54
5.6.3.1 Individual call .54
5.6.3.2 Group call .55
5.6.4 Interactions with Connected Line identification Presentation (SS-COLP).55
5.6.5 Interactions with ISI Mobility Management (ANF-ISIMM).56
5.7 SS-TPI parameter values (timers) .56
Annex A (informative): Examples of message sequences .57
A.1 Example message sequence for normal operation of SS-TPI in a group call in the case where
transmission is not granted automatically at set-up time .57
A.2 Example message sequence for normal operation of SS-TPI in a group call where transmission
is granted automatically to the calling user at set-up time .57
A.3 Example message sequence for normal operation of SS-TPI in a group call where transmission
is granted automatically to another user than the calling user at set-up time.57
A.4 Example message sequence for exceptional operation of SS-TPI in a group call where the
originating SwMI does not support the sending of name .58
A.5 Example message sequence for normal operation of SS-TPI in an individual call for the calling
user .63
A.6 Example message sequence for normal operation of SS-TPI in an individual call for the
connected user.64
Annex B (informative): Specification and Description Language (SDL) representation of procedures .66
B.1 SDL representation of SS-TPI at the served user MS/LS.67
B.2 SDL representation of SS-TPI at the group controlling SwMI.69
B.3 SDL representation of SS-TPI at the served user SwMI.75
B.4 SDL representation of SS-TPI at the talking/sending user SwMI.80

Page 6
ETS 300 392-12-3: August 1999
B.5 SDL representation of SS-TPI at the authorized user MS/LS .83
B.6 SDL representation of SS-TPI at the authorized user SwMI .85
B.7 SDL representation of SS-TPI at the managed user home SwMI.87
Annex C (informative): Bibliography .90
History.91

Page 7
ETS 300 392-12-3: August 1999
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
This ETS is a multi-part standard and will consist of the following parts:
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 6: "Line connected Station (LS)";
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".
Transposition dates
Date of adoption of this ETS: 23 July 1999
Date of latest announcement of this ETS (doa): 31 October 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 April 2000
Date of withdrawal of any conflicting National Standard (dow): 30 April 2000

Page 8
ETS 300 392-12-3: August 1999
Blank page
Page 9
ETS 300 392-12-3: August 1999
1 Scope
This ETS specifies the stage 3 description of the Supplementary Service Talking Party Identification
(SS-TPI) for the Terrestrial Trunked Radio (TETRA).
The SS-TPI supplementary service enables the party/parties participating in a call to receive the
identification of the talking/sending party. The SS-TPI is activated against individual identity in individual
call and against group identity in group calls.
Man-Machine Interface (MMI) and charging principles are outside the scope of this ETS.
The supplementary service stage 3 description is preceded by the stage 1 and the stage 2 description of
the service, according to the method described in CCITT Recommendation I.130 [10]. The stage 1
description specifies the service from the user’s point of view. The stage 2 description identifies the
functional capabilities and the information flows needed to support the supplementary service as specified
in its stage 1 description. The present stage 3 description specifies the protocols at the air interface and at
the various Inter-System Interfaces (ISI) to support SS-TPI.
NOTE: According to CCITT Recommendation I.130 [10], 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 functional entity actions in the stage 2 description.
This ETS is applicable to Voice plus Data individual call or group call; more specifically to the following
entities:
- the MS/LS of listening/receiving users during an individual call or a group call;
- to the originating Switching and Management Infrastructures (SwMIs) in an individual call or a group
call;
- to the group home SwMI and the participating SwMI for a group call;
- to the terminating SwMI for an individual call;
- and, optionally, to the home SwMI of the group or of the MS/LSs involved, for managing the
supplementary service.
2 References
This ETS incorporates, by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to, or revisions of, any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 2: Air Interface (AI)".
[2] ETS 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".
[3] ETS 300 392-3-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-Systems Interface (ISI); Sub-part 2: Additional
Network Functions Individual Call (ANF-ISIIC)".

Page 10
ETS 300 392-12-3: August 1999
[4] ETS 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 Functions Group Call (ANF-ISIGC)".
[5] ETS 300 392-3-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 3: Interworking at the Inter-system Interface (ISI); Sub-part 5: Additional
Network Functions Mobility Management (ANF-ISIMM)".
[6] ETS 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 9: General requirements for supplementary services".
[7] ETS 300 392-10-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 10: Supplementary services stage 1; Sub-part 3: Talking Party Identification
(TPI)".
[8] ETS 300 392-11-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 11: Supplementary services stage 2; Sub-part 3: Talking Party Identification
(TPI)".
[9] ETS 300 392-12-6: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 12: Supplementary services stage 3; Sub-part 6: Call Authorized by
Dispatcher (CAD)".
[10] CCITT Recommendation I.130 (1988): "Method for the characterization of
telecommunication services supported by an ISDN and network capabilities of
an ISDN".
[11] ITU-T Recommendation Z.100: "CCITT specification and description language
(SDL)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
authorized User: identified user who is allowed to define, activate, deactivate and/or interrogate the
SS-TPI parameters
served user: listening/receiving party in a call, that receives the SS-TPI information. In a group call, all
parties except the talking/sending party will be served users. In an individual call, if SS-TPI is provided to
the calling and the connected users:
- if the call is half-duplex, whenever one of the two parties becomes the talking/sending user, the
other party is the served user;
- if the call is duplex, both of them are served users.
served user SwMI: in the case of an individual call, SwMI where the served user is registered, or in the
case of a group call, any SwMI where served users are registered different from the group controlling
SwMI. The protocol specified for the start of the call in this ETS for such SwMI applies independently of
whether or not the/a served user is registered in that SwMI at that time (i.e. the user registered in that
SwMI involved the call may be talking/sending at set-up time, and become served user only later during
the call)
Page 11
ETS 300 392-12-3: August 1999
talking/sending user: party to whom transmission permission has been granted during a group call or a
half-duplex individual call. That party may change during a call
talking/sending user SwMI: SwMI where the talking/sending user is registered. That definition applies
without restriction in the case of an individual call. In the case of a group call, the talking/sending user
SwMI exists only when it is different from the group controlling SwMI, The protocol specified for the start of
the call in this ETS for such SwMI applies independently of whether or not the talking/sending user is
registered in that SwMI at that time (i.e. the user registered in that SwMI involved the call may be
listening/receiving at set-up time, i.e. thus the/a served user, and become talking/sending user only later
during the call)
In addition, the other definitions given in ETS 300 392-9 [6] shall apply.
3.2 General abbreviations
For the purposes of this ETS, the following abbreviations apply:
ANF-ISIGC Additional Network Feature - Inter-System Interface Group Call
ANF-ISIIC Additional Network Feature - Inter-System Interface Individual Call
ANF-ISIMM Additional Network Feature - Inter-System Interface Mobility Management
ANF-ISISS Additional Network Feature - Inter-System Interface Supplementary Service
GTSI Group TETRA Subscriber Identity
ISI Inter-System Interface
ITSI Individual TETRA Subscriber Identity
LS Line Station
MS Mobile Station
PDU Protocol Data Unit
ROSE Remote Operation Service Element
SS Supplementary Service
NOTE: The abbreviation SS is only used when referring to a specific supplementary service.
SwMI Switching and Management Infrastructure
3.3 Supplementary service abbreviations
For the purposes of this ETS, the following abbreviations apply:
CAD Call Authorized by Dispatcher
CLIR Calling/connected Line Identification Restriction
COLP Connected Line identification Presentation
TPI Talking Party Identification
4 SS-TPI service description
4.1 General
SS-TPI enables a listening/receiving user in an individual or a group call to be provided with the identity of
the talking/sending party, and on an optional basis, with its mnemonic name and/or with the level of priority
of its request for transmission grant.
This subclause describes SS-TPI specific services offered by the Circuit Mode Control Entity (CMCE) at
the Supplementary Services service access point (TNSS-SAP) of the TETRA voice plus data layer 3
service boundary in a TETRA Mobile Station (MS) or TETRA Line Station (LS). The SS-TPI service
access point is used in conformance testing as a normative boundary in MSs and LSs.
NOTE: As the present document only deals with the SS-TPI all the service primitives has been
shown without a TNSS-TPI-prefix e.g. the TNSS-TPI-ACTIVATE request is shorten
into an ACTIVATE request.
Page 12
ETS 300 392-12-3: August 1999
4.2 SS-TPI services offered over the TNSSSAP
NOTE 1: As man-machine interface or user applications are outside the scope of the present
document service primitives are used to define information exchange to and from the
standardized part of the MS/LS. Those primitives may be only indirectly accessible.
The SS-TPI service primitives at the served user MS/LS TNSS-SAP shall be:
- INFORM indication.
The SS-TPI service primitives at the authorized user MS/LS TNSS-SAP shall be:
- ACTIVATE request;
- ACTIVATE indication;
- DEFINE request;
- DEFINE indication;
- INFORM indication;
- INTERROGATE request;
- INTERROGATE indication;
- INTERROGATE BY NAME request;
- INTERROGATE BY NAME indication.
Any user to whom SS-TPI is provided should have the possibility to use the INTERROGATE primitives
mentioned above, limited to its own ITSI and to GTSIs of groups he is member of.
NOTE 2: Formally, when such user is using the INTERROGATE primitives to know whether
SS-TPI has been activated for him, and if yes with which optional subscription
parameters, he is acting as a served user. While when he is using those primitives to
know his mnemonic name, he is acting as a talking/sending user (since that name is
going to be delivered to the served user(s)). However no difference have been made
between the two cases, since during a call any user can be in turn a served user and
talking/sending user.
4.2.1 ACTIVATE indication
The ACTIVATE indication primitive shall be sent to the user application by the MS/LS CMCE over
TNSS-SAP to inform it of the result of a previous ACTIVATE request.
If the previous request has been addressed to a SwMI for more than one identity, that SwMI may send its
corresponding response either in one single request which applies to all those identities or in multiple
requests.
The ACTIVATE indication primitive shall contain the SS-TPI parameters listed in table 1.
Table 1: Parameters for the primitive ACTIVATE indication
Parameter Indication
Activation result M (note 1)
TETRA identity/identities M (note 2)
Activation state C (notes 1 and 3)
NOTE 1: There shall be only one activation result and one activation state per indication primitive.
NOTE 2: It is optional to support more than one identity.
NOTE 3: Conditional on the activation result.

Page 13
ETS 300 392-12-3: August 1999
4.2.2 ACTIVATE request
The ACTIVATE request primitive shall be sent to the MS/LS CMCE by the user application by over
TNSS-SAP to activate SS-TPI.
The activation process shall support one TETRA identity in a request. Optionally it may support a list
and/or range of identities. Such identity/identities may be those of either individual users or of groups.
The ACTIVATE request primitive shall contain the SS-TPI parameters listed in table 2.
Table 2: Parameters for the primitive ACTIVATE request
Parameter Request
Access priority O
TETRA identity/identities M (note 1)
Activation request M (note 2)
NOTE 1: It is optional to support more than one identity.
NOTE 2: There shall be only one activation request per request primitive.
4.2.3 DEFINE indication
The DEFINE indication primitive shall be sent to the user application by the MS/LS CMCE over
TNSS-SAP to inform it of the result of a previous DEFINE request.
If the previous request has been addressed to a SwMI for more than one identity, that SwMI may send its
corresponding response either in one single request which applies to all those identities or in multiple
requests.
The DEFINE indication primitive shall contain the SS-TPI parameters listed in table 3.
Table 3: Parameters for the primitive DEFINE indication
Parameter Indication
Definition result M (note 1)
TETRA identity/identities M (note 2)
Activation state C (notes 1 and 3)
NOTE 1: There shall be only one definition result and one activation state per indication primitive.
NOTE 2: It is optional to support more than one identity.
NOTE 3: Conditional on the definition result.

Page 14
ETS 300 392-12-3: August 1999
4.2.4 DEFINE request
The DEFINE request primitive shall be sent to the MS/LS CMCE by the user application by over
TNSS-SAP to give a mnemonic name to a user.
The definition process shall support one TETRA identity in a request. Optionally it may support a list
and/or range of identities. Such identity/identities may only be those of individual users (since the groups
have no mnemonic names).
The DEFINE request primitive shall contain the SS-TPI parameters listed in table 4.
Table 4: Parameters for the primitive DEFINE request
Parameter Request
Access priority O
TETRA identity/identities M (note 1)
TETRA mnemonic name/names M (note 2)
Activation request C (note 2)
NOTE 1: It is optional to support more than one identity.
NOTE 2: There shall be as many mnemonic names as there are identities.
NOTE 3: There shall be only one activation request per request primitive.
4.2.5 INFORM indication
The INFORM indication primitive shall be sent to the user application by the MS/LS CMCE over
TNSS-SAP as a result of SS-TPI operation. The INFORM indication primitive shall contain the SS-TPI
parameters listed in table 5.
Table 5: Parameters for the primitive INFORM indication
Parameter Indication
SS-CLIR invoked for talking/sending party M
Talking/sending party identity C (note 1)
Talking/sending party mnemonic name O (note 2)
Tx demand priority O
NOTE 1: Conditional on SS-CLIR not having been invoked for talking/sending party.
NOTE 2: Shall not be present if SS-CLIR has been invoked for talking/sending party.
4.2.6 INTERROGATE indication
The INTERROGATE indication primitive shall be sent to the user application by the MS/LS CMCE over
TNSS-SAP to inform it of the result of a previous INTERROGATE request.
If the previous request has been addressed to a SwMI for more than one identity, that SwMI may send its
corresponding response either in one single request which applies to all those identities or in multiple
requests.
The INTERROGATE indication primitive shall contain the SS-TPI parameters listed in table 6.

Page 15
ETS 300 392-12-3: August 1999
Table 6: Parameters for the primitive INTERROGATE indication
Parameter Indication
Interrogation result M (note 1)
TETRA identity/identities M (note 2)
TETRA mnemonic name/names C (notes 3 and 4)
Activation state C (notes 1 and 3)
NOTE 1: There shall be only one interrogation result and one activation state per indication primitive.
NOTE 2: It is optional to support more than one identity.
NOTE 3: Conditional on the interrogation result.
NOTE 4: If that parameter is present (see note 3), there shall be as many mnemonic names as there
are identities.
4.2.7 INTERROGATE request
The INTERROGATE request primitive shall be sent to the MS/LS CMCE by the user application by over
TNSS-SAP to know the SS-TPI activation status of a user and his mnemonic name.
The interrogation process shall support one TETRA identity in a request. Optionally it may support a list
and/or range of identities. Such identity/identities may be those of either individual users or of groups.
The INTERROGATE request primitive shall contain the SS-TPI parameters listed in table 7.
Table 7: Parameters for the primitive INTERROGATE request
Parameter Request
Access priority O
TETRA identity/identities M (note)
NOTE: It is optional to support more than one identity.
4.2.8 INTERROGATE BY NAME indication
The INTERROGATE BY NAME indication primitive shall be sent to the user application by the MS/LS
CMCE over TNSS-SAP to inform it of the result of a previous INTERROGATE BY NAME request.
If the previous request has been addressed to a SwMI for more than one identity, that SwMI may send its
corresponding response either in one single request which applies to all those identities or in multiple
requests.
The INTERROGATE BY NAME indication primitive shall contain the SS-TPI parameters listed in table 8.
Table 8: Parameters for the primitive INTERROGATE BY NAME indication
Parameter Indication
Interrogation result M (note 1)
TETRA mnemonic name/names M (note 2)
TETRA identity/identities C (notes 3 and 4)
Activation state C (notes 1 and 3)
NOTE 1: There shall be only one interrogation result and one activation state per indication primitive.
NOTE 2: It is optional to support more than one mnemonic name.
NOTE 3: Conditional on the interrogation result.
NOTE 4: If that parameter is present (see note 3), there shall be as many identities as there are
mnemonic names.
Page 16
ETS 300 392-12-3: August 1999
4.2.9 INTERROGATE BY NAME request
The INTERROGATE BY NAME request primitive shall be sent to the MS/LS CMCE by the user
application by over TNSS-SAP to know the identity corresponding to a mnemonic name.
The interrogation process shall support one TETRA identity in a request. Optionally it may support a list
and/or range of identities. Such identity/identities may only be those of individual users (since the groups
have no mnemonic names).
The INTERROGATE BY NAME request primitive shall contain the SS-TPI parameters listed in table 9.
Table 9: Parameters for the primitive INTERROGATE BY NAME request
Parameter Request
Access priority O
TETRA mnemonic name/names M (note)
NOTE: It is optional to support more than one mnemonic name.
4.3 Parameter description
Access priority:
low priority;
high priority;
emergency priority.
The default value for that parameter shall be low priority. The value emergency priority should not be used
for that parameter in any primitive.
Activation request:
That parameter shall contain the following information:
Speech call activation:
deactivate;
activate;
no change.
Speech call mnemonic name:
no name;
use mnemonic name.
Indication of priority levels of the talking party speech requests:
no indication;
indication.
Data call activation:
deactivate;
activate;
no change.
Data call mnemonic name:
no name;
use mnemonic name.
Page 17
ETS 300 392-12-3: August 1999
Indication of priority levels of the sending party data transmission requests:
no indication;
indication.
Activation result:
unsuccessful request;
successful request.
If the request has been unsuccessful, one of the following reasons shall be indicated:
rejected for any reason;
user not authorized;
supplementary service not subscribed for the user addressed;
unknown TETRA identity;
repetition of parameters not supported;
protocol problem.
Activation state:
That parameter shall contain the following information:
Speech call activation:
deactivated;
activated.
Speech call mnemonic name:
no name;
use mnemonic name.
Indication of priority levels of the talking party speech requests:
no indication;
indication.
Data call activation:
deactivated;
activated.
Data call mnemonic name:
no name;
use mnemonic name.
Indication of priority levels of the sending party data transmission requests:
no indication;
indication.
Page 18
ETS 300 392-12-3: August 1999
Definition result:
unsuccessful request;
successful request.
If the request has been unsuccessful, one of the following reasons shall be indicated:
rejected for any reason;
not an authorized user;
supplementary service not subscribed for the user addressed;
unknown TETRA identity;
character set not supported;
number of characters larger than 15;
repetition of parameters not supported;
protocol problem.
Interrogation result:
unsuccessful request;
successful request.
If the INTERROGATE request has been unsuccessful, one of the following reasons shall be
indicated:
rejected for any reason;
not an authorized user;
unknown TETRA identity;
repetition of parameters not supported;
protocol problem.
If the INTERROGATE BY NAME request has been unsuccessful, one of the following reasons shall
be indicated:
rejected for any reason;
not an authorized user;
unknown mnemonic name;
character set not supported;
number of characters larger than 15;
repetition of parameters not supported;
protocol problem.
SS-CLIR invoked for talking/sending party:
restriction on presentation of talking/sending party identity or mnemonic name:
no restriction on presentation of talking/sending party identity or mnemonic name.
Talking/sending party mnemonic name and TETRA mnemonic name:
1 to 15 characters.
Talking/sending party identity:
Short Subscriber Identity (SSI);
Short Subscriber Identity (SSI) + Address extension;
Gateway identity, possibly complemented by external party number.
TETRA identity:
Short Number Address (SNA);
Short Subscriber Identity (SSI);
Short Subscriber Identity (SSI) + Address extension.
The Short Number Address (SNA) shall be valid only in requests.

Page 19
ETS 300 392-12-3: August 1999
TX demand priority (i.e. priority level of the talking/sending party request for transmission permission):
low priority;
high priority;
pre-emptive priority;
emergency.
5 Signalling protocol for the support of SS-TPI
5.1 SS-TPI operational requirements
5.1.1 Served user MS/LS
The served user MS/LS shall comply with the requirements in clause 14 of ETS 300 392-2 [1] which apply
to the tele and bearer services which it supports. In addition, it shall comply with the relevant call related
requirements in clauses 7 and 11 of ETS 300 392-9 [6].
5.1.2 Group controlling SwMI
If the served user MS/LS is registered in the group controlling SwMI, that SwMI shall support this MS/LS
complying with the requirements for participating in a group call in the receive mode only set in clause 14
of ETS 300 392-2 [1]. This SwMI shall also comply with the relevant call related requirements in clauses 7
to 11 of ETS 300 392-9 [6].
If the talking/sending user MS/LS is registered in the group controlling SwMI, that SwMI shall support this
MS/LS complying with the requirements for participating in a group call with the possibility to talk/send
data, as defined in clause 14 of ETS 300 392-2 [1]. That SwMI shall also comply with the relevant call
related requirements in clauses 7 to 11 of ETS 300 392-9 [6].
If the served user MS/LSs and the talking/sending user MS/LS are not all registered in the group
controlling SwMI, that SwMI shall comply with the ISI requirements necessary to support group calls, set in
ETS 300 392-3-3 [4]. It shall also comply with the relevant call related requirements in clauses 9 to 11 of
ETS 300 392-9 [6].
5.1.3 Served user SwMI
That SwMI shall support the served user MS/LS complying with the requirements for individual calls set in
subclause 5.1.1.
It shall also support the served user MS/LS complying with the requirements for group calls set in
subclause 5.1.1 if it is different from the group controlling SwMI.
If the call is over the ISI, the served user SwMI shall comply with the corresponding ISI requirements, set
in ETS 300 392-3-2 [3], for individual calls and in ETS 300 392-3-3 [4], for group calls. It shall also comply
with the relevant call related in clauses 9 to 11 of ETS 300 392-9 [6].
5.1.4 Talking/sending user SwMI
For an individual call, that SwMI shall support the possibility for the talking/sending party MS/LS t
...