SIST ETS 300 394-5-1 E1:2003

SLOVENSKI STANDARD
01-december-2003
Prizemni snopovni radio (TETRA) – Specifikacija za preskušanje skladnosti – 5.
del: Varnost – 1. poddel: Izjava o skladnosti izvedbe protokola (PICS) – Proforma
specifikacija
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 5: Security;
Sub-part 1: Protocol Implementation Conformance Statement (PICS) proforma
specification
Ta slovenski standard je istoveten z: ETS 300 394-5-1 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 394-5-1
TELECOMMUNICATION July 1999
STANDARD
Source: TETRA Reference: DE/TETRA-06025
ICS: 33.020
Key words: PICS, TETRA, security, V+D, voice, data
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 5: Security;
Sub-part 1: Protocol Implementation Conformance
Statement (PICS) proforma specification
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 394-5-1: July 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 394-5-1: July 1999
Contents
Foreword . 5
1 Scope. 7
2 Normative references . 7
3 Definitions and abbreviations. 8
3.1 Definitions. 8
3.2 Abbreviations. 8
4 Conformance to this PICS proforma specification. 8
Annex A (normative): Protocol ICS proforma for TETRA Security . 9
A.1 Guidance for completing the PICS proforma. 9
A.1.1 Purposes and structure . 9
A.1.2 Abbreviations and conventions. 9
A.1.3 Instructions for completing the PICS proforma . 11
A.2 Identification of the implementation . 11
A.2.1 Date of the statement . 11
A.2.2 Implementation Under Test (IUT) identification. 11
A.2.3 System Under Test (SUT) identification. 12
A.2.4 Product supplier. 12
A.2.5 Client . 12
A.2.6 PICS contact person. 13
A.2.7 Authentication algorithm identification. 13
A.3 Identification of the protocol. 14
Annex B (normative): Protocol ICS tables proforma for TETRA V+D Security. 15
B.1 Global statement of conformance. 15
B.2 Structure of V+D ICS tables. 15
B.3 Major capabilities . 16
B.4 Authentication . 17
B.4.1 Authentication algorithms .18
B.4.2 Authentication cipher keys.18
B.4.3 Authentication PDUs . 18
B.4.4 Authentication PDU elements. 19
B.4.5 Registration PDU extended elements . 21
B.5 OTAR. 21
B.5.1 OTAR algorithms. 23
B.5.2 OTAR cipher keys . 23
B.5.3 OTAR PDUs . 24
B.5.4 OTAR PDU elements . 25
B.5.5 Registration PDU extended elements . 27
B.6 Enable/disable . 27
B.6.1 Enable Disable PDUs.28
B.6.2 Secure Enable Disable PDU elements. 29

Page 4
ETS 300 394-5-1: July 1999
B.7 AI encryption.30
B.7.1 AI encryption algorithms and keys.30
B.7.2 AI encryption algorithms (KSG) .31
B.8 Key change protocol.32
B.9 End-to-end encryption .33
B.10 Encrypted short identities .34
B.10.1 ESI algorithms.35
B.10.2 ESI keys.35
B.11 TEI delivery.36
B.11.1 TEI delivery PDU .36
B.11.2 TEI delivery PDU elements.36
B.11.3 Registration PDU extended elements.36
B.12 PDU support.37
Annex C (normative): Protocol ICS tables proforma for TETRA DMO Security.38
C.1 Global statement of conformance .38
C.2 OTAR in DMO .38
C.2.1 DMO OTAR algorithms.39
C.2.2 OTAR DMO PDUs .40
C.2.3 OTAR DMO PDU elements .40
C.2.4 SDS Element encoding for carriage of OTAR PDUs.41
C.3 Secure enable/disable in DMO.42
C.3.1 DMO Secure enable/disable algorithms .43
C.3.2 DMO secure enable/disable PDUs .44
C.3.3 ENDIS PDU elements.44
C.3.4 SDS Element encoding for carriage of ENDIS PDUs.45
C.4 DMO AI encryption .47
C.4.1 DMO AI encryption algorithms.48
C.5 DMO End-to-end encryption.48
History.51

Page 5
ETS 300 394-5-1: July 1999
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
Every ETS prepared by ETSI is a voluntary standard. This ETS contains text concerning conformance
testing of the equipment to which it relates. This text should be considered only as guidance and does not
make this ETS mandatory.
This ETS is a multi-part standard and will consist of the following parts:
Part 1: "Radio";
Part 2: "Protocol testing specification for Voice plus Data (V+D)";
Part 4: "Protocol testing specification for Direct Mode Operation (DMO)";
Part 5: "Security".
Transposition dates
Date of adoption of this ETS: 25 June 1999
Date of latest announcement of this ETS (doa): 30 September 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 March 2000
Date of withdrawal of any conflicting National Standard (dow): 31 March 2000

Page 6
ETS 300 394-5-1: July 1999
Blank page
Page 7
ETS 300 394-5-1: July 1999
1 Scope
This European Telecommunication Standard (ETS) provides the Protocol Implementation Conformance
Statement (PICS) proforma in compliance with the relevant requirements, and in accordance with the
relevant guidance given in ISO/IEC 9646-7 [8], ETS 300 406 [3], and in ETR 212 [9] for the following
standards:
TETRA; Voice plus Data (V+D); Part 7: Security defined in ETS 300 392-7 [1];
TETRA; Direct Mode; Part 6: Security defined in ETS 300 396-6 [2].
The PICS draft has acted as a fair and independent review of the above standards. The above standards
may therefore be subject to modification or extension as a result of this PICS proforma.
The role of the PICS is to enable selection of test cases from ETS 300 394-5-2 for the MS. In the case of
the SwMI the PICS is a tool to guide procurement of TETRA systems. This ETS acts as a complement to
the PICS for TETRA V+D, ETS 300 392-14.
2 Normative references
This ETS incorporates by dated and 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-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[2] ETS 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation
(DMO); Part 6: Security".
[3] ETS 300 406 : "Methods for testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[4] ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 2: Air Interface (AI)".
[5] ETS 300 396-3: "Terrestrial Trunked Radio (TETRA); Technical requirements
for Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile Station
(MS-MS) Air Interface (AI) protocol".
[6] ETS 300 393-7: "Terrestrial Trunked Radio (TETRA); Packet Data Optimized
(PDO); Part 7: Security".
[7] ISO/IEC 9646-1 (1994): "Information technology - Open systems interconnection
- Conformance testing methodology and framework - Part 1: General concepts".
[8] ISO/IEC 9646-7 (1995): "Information technology - Open systems interconnection
- Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
[9] ETR 212: "Methods for testing and Specification (MTS); Implementation
Conformance Statement (ICS) proforma style guide".
[10] ISO 8208 (1995): "Information technology - Data communications - X.25 Packet
Layer Protocol for Data Terminal Equipment".
[11] ISO/IEC 8348 (1996): "Information technology - Open Systems Interconnection -
Network Service Definition".
Page 8
ETS 300 394-5-1: July 1999
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- Terms defined in ETS 300 392-7 [1];
- Terms defined in ETS 300 396-6 [2];
- Terms defined in ISO/IEC 9646-1 [7] and in ISO/IEC 9646-7 [8].
In particular, the following terms defined in ISO/IEC 9646-1 [7] apply:
Implementation Conformance Statement (ICS): statement made by the supplier of an implementation
or system claimed to conform to a given specification, stating which capabilities have been implemented.
The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or
system becomes an ICS
Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol
specification
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
BS Base Station
CC Call Control sub entity within CMCE
CMCE Circuit Mode Control Entity
CONP Connection Oriented Network Protocol
DTMF Dual Tone Multi Frequency
ETS European Telecommunication Standard
ICS Implementation Conformance Statement
ITSI Individual TETRA Subscriber Identity
IUT Implementation Under Test
LLC Logical Link Control
LLME Lower Layer Management Entity
MAC Medium Access Control
MCC Mobile Country Code
MM Mobility Management
MNC Mobile Network Code
MS Mobile Station
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
RPDI Radio Packet Data Infrastructure
SCLNP Specific Connectionless Network Protocol
SAP Service Access Point
SCS System Conformance Statement
SDU Service Data Unit
SP Service Primitive
SS Supplementary Service sub entity within CMCE
SUT System Under Test
SwMI Switching and Management Infrastructure
4 Conformance to this PICS proforma specification
If it claims to conform to this ETS the actual PICS proforma to be filled in by a supplier shall be technically
equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming
and ordering of the proforma items.
A PICS which conforms to this ETS shall be a conforming PICS proforma completed in accordance with
the guidance for completion given in clause A.1.

Page 9
ETS 300 394-5-1: July 1999
Annex A (normative): Protocol ICS proforma for TETRA Security
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PICS.
A.1 Guidance for completing the PICS proforma
A.1.1 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of
the requirements defined in ETS 300 392-7, or ETS 300 396-6, may provide information about the
implementation in a standardized manner.
The PICS proforma is subdivided into subclauses for the following categories of information with some of
these subclauses also included in a set of separate annexes covering V+D and DMO specific aspects:
- Guidance for completing the PICS proforma (annex A)
- Identification of the implementation;
- Identification of the protocol;
- V+D Specific Aspects (annex B)
- Global statement of conformance;
- Authentication;
- Over The Air Rekeying (OTAR);
- Enable/disable;
- Air Interface encryption;
- Key change protocol;
- End-to-end encryption.
- Encrypted short identities;
- TEI delivery;
- PDU support.
- DMO specific aspects (annex C)
- OTAR in DMO;
- Enable/Disable in DMO (ENDIS);
- Air Interface encryption;
- End-to-end encryption.
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with
the guide-lines presented in ISO/IEC 9646-7.
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. elements, timers, etc.). It
implicitly means "is supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7, are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.

Page 10
ETS 300 394-5-1: July 1999
x prohibited (excluded) - there is a requirement not to use this capability in the
given context.
oi qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer which identifies a unique group of related optional items and the logic
of their selection which is defined immediately following the table.
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on
the support of other optional or conditional items. "i" is an integer identifying a
unique conditional status expression which is defined immediately following the
table.
Reference column
The reference column gives reference to ETS 300 392-7, except where explicitly stated otherwise. In
providing the reference the format [x] a.b.c.d is used where [x] is the number of the referenced document
from clause 2, and a.b.c.d refers to the specific clause or subclause of the reference document.
Support column
The support column shall be filled in by the supplier of the implementation. The following common
notations, defined in ISO/IEC 9646-7, are used for the support column:
Y or y supported by the implementation
N or n not supported by the implementation
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation
of a conditional status)
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
NOTE: As stated in ISO/IEC 9646-7, support for a received PDU requires the ability to
encode/decode all mandatory elements of that PDU. Supporting a PDU while having
no ability to encode/decode a mandatory element is non-conformant. Support for an
element of a PDU means that the semantics of that element are supported. It does not
mean that the element shall always be present in the PDU.
Values allowed column
The values allowed column contains the type, the list, the range, or the length of values allowed. The
following notations are used:
- range of values: .
EXAMPLE: 5 . 20
- list of values: , , .,
EXAMPLE: 2, 4, 6, 8, 9
EXAMPLE: '1101'B, '1011'B, '1111'B
EXAMPLE: '0A'H, '34'H, '2F'H
- list of named values: (), (), ., ()
EXAMPLE: reject(1), accept(2)
- length: size ( . )
EXAMPLE: size (1 . 8)
Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the
values or the ranges of values supported by the implementation shall be indicated.

Page 11
ETS 300 394-5-1: July 1999
References to items
For each possible item answer (answer in the support column) within the PICS proforma exists a unique
reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed
by a solidus character "/", followed by the item number in the table. If there is more than one support
column in a table, the columns are discriminated by letters (a, b, etc.), respectively.
EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table A.5.
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column)
of item 3 in table A.6.
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite line in the beginning of a clause or table indicates that the whole clause or the whole table
is not required to be completed if the predicate is FALSE.
NOTE: In this PICS proforma, all the tables have a prerequisite independently on the status of
the predicate referred to being mandatory or optional. This is done for readability
reasons.
A.1.3 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In
particular, an explicit answer shall be entered, in each of the support or supported column boxes provided,
using the notation described in subclause A.1.2.
If necessary, the supplier may provide additional comments in space at the bottom of the tables, or
separately on sheets of paper.
More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.
A.2 Identification of the implementation
NOTE: This section is to be completed for each submission of a PICS for V+D and DMO.
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System
Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version
numbers and configuration options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the
contact person.
A.2.1 Date of the statement
........................................................................................................................................................................
A.2.2 Implementation Under Test (IUT) identification
IUT name:
........................................................................................................................................................................
........................................................................................................................................................................
IUT version:
........................................................................................................................................................................

Page 12
ETS 300 394-5-1: July 1999
A.2.3 System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................
.........................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Operating system:
.........................................................................................................................................................................
A.2.4 Product supplier
Name:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
E-mail address:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.5 Client
(If different from product supplier)
Name:
.........................................................................................................................................................................

Page 13
ETS 300 394-5-1: July 1999
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
E-mail address:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
A.2.6 PICS contact person
(A person to contact if there are any queries concerning the content of the PICS)
Name:
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................
E-mail address:
........................................................................................................................................................................
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
A.2.7 Authentication algorithm identification
If TAA1 (ETSI) is used then this section can be skipped.
Supplier:
........................................................................................................................................................................

Page 14
ETS 300 394-5-1: July 1999
.........................................................................................................................................................................
Version:
.........................................................................................................................................................................
A.3 Identification of the protocol
This PICS proforma applies to the following standards:
ETS 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V + D); Part 7: Security".
ETS 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation (DMO); Part 6: Security".

Page 15
ETS 300 394-5-1: July 1999
Annex B (normative): Protocol ICS tables proforma for TETRA V+D Security
B.1 Global statement of conformance
Are all mandatory capabilities implemented? (Yes/No)   .
NOTE: Answering "No" to this question indicates non-conformance to the protocol
specification. Non-supported mandatory capabilities are to be identified in the PICS,
with an explanation of why the implementation is non-conforming, on pages attached
to the PICS proforma.
B.2 Structure of V+D ICS tables
The map below summarizes the general structure of the document and the corresponding tables that shall
be completed as a consequence of any entry in any other table. It should be noted that a single PICS may
involve traversing this map more than one once.
NOTE: The map below, and similar maps introducing each section, is intended for guidance
and is not intended to be treated as normative.

Page 16
ETS 300 394-5-1: July 1999
TB1
TB2
TB3
Authentication TA11 K-ITSI TA41
TA12 TA51
SCK-ITSI
TA21 TA52 (MS)
TA22
OTAR SCK
Enable-
CCK Delivery OTAR GCK GCK-GTSI
disable
TA31 TA81
TA32 (MS) TA82 (MS)
AI Encryption using
CCK
SCK
TEI Delivery MGCK TA71
DCK
TB4
End-to-end End-to-end
encryption OTAR
ESI TA61
NOTE 1: Arrows on the map indicate the relation "tail" requires "head" (e.g OTAR CCK requires
Authentication to be supported).
NOTE 2: The relation from TA61 to CCK and SCK should be interpreted as an either/or relation.
NOTE 3: The link from K-ITSI to TBx is an optional or weak relation.
NOTE 4: The relations from AI Encryption and TA61 to the cipher keys is an either/or relation.
Figure B.1: Overall structure of V+D PICS annex
If the implementation supports authentication this means that as a consequence the implementation shall
support TA11, TA12 (and perhaps TA21, TA22) and storage of the ITSI-K relation.
B.3 Major capabilities
Table B.1: V+D Security class supported
Item Role Reference Status Support
1 Class 1 [1] 6.1.1 o.1
Class 2 [1] 6.1.1 o.1
Class 3 [1] 6.1.1 o.1
o.1: It is mandatory to support at least one of these items.

Page 17
ETS 300 394-5-1: July 1999
Table B.2: V+D Security capabilities supported
Item Security capability Reference Status Support
1 Authentication [1] 4 c201
2 OTAR [1] 4 c201
3 Enable/disable [1] 5 m
4 AI encryption [1] 6 c202
5 End-to-end encryption [1] 7 o
TEI delivery [1] 4.1.6 m
7 ESI [1] 4.2.5 c202
8 Key change protocol [1] 4.4.6 c203
c201: IF B.1/3 - If security class 3 then mandatory else optional
THEN m
ELSE o
c202: IF B.1/3 or B.1/2 - If security class 3, or security class 2 then mandatory
THEN m - else not applicable
ELSE n/a
c203: IF B.1/3or B.2/2 - If security class 3 or if OTAR supported then mandatory
THEN m - else not applicable
ELSE n/a
B.4 Authentication
NOTE: This clause needs to be completed only if the IUT supports authentication.
Are all mandatory capabilities of authentication implemented? (Yes/No)   .
Authentication Algorithms Keys PDUs
(Tables B.3, B.4) TA11 K-ITSI (Tables B.7 to B.16)
TA12 (Table B.6)
TA21
TA22
(Table B.5)
Figure B.2: Authentication PICS table navigation map
Figure B.2 is intended to assist in identifying the tables that should be completed for those
implementations purporting to support authentication as defined in ETS 300 392-7, clause 4.
Table B.3: Authentication role
Prerequisite: B.2/1 – IUT supports authentication
Item Authentication role Reference Status Support
1 MS [1] 4.4.2.2 o.301
2 SwMI [1] 4.4.2.1 o.301
o.301 It is mandatory to support at least one of these items.

Page 18
ETS 300 394-5-1: July 1999
Table B.4: Authentication sub-types
Prerequisite: B.2/1 – IUT supports authentication
Item Authentication sub-type Reference Status Support
1 SwMI initiated authentication [1] 4.4.2.1 m
2 MS initiated authentication [1] 4.4.2.2 m
3 Authentication initiated by SwMI and made [1] 4.4.2.3 m
mutual by MS
4 Authentication initiated by MS and made mutual [1] 4.4.2.4 m
by SwMI
SwMI initiated authentication during registration [1] 4.4.2.5 m
6 MS initiated authentication during registration [1] 4.4.2.6 m
7 Authentication initiated by MS during registration [1] 4.4.2.7 m
made mutual by SwMI
8 Authentication initiated by SwMI during [1] 4.4.2.8 m
registration made mutual by MS
Comment: It is stated in ETS 300 392-7ed2, subclause 4.4.2 that if a terminal supports authentication then
it shall support all modes. This therefore requires that all entries in table B.4 are mandatory.
B.4.1 Authentication algorithms
The supplier of the implementation shall state the support of each of the AI authentication algorithms.
If the algorithms are not sourced from TAA1 the source of the algorithms shall be specified in subclause
A.2.7.
Table B.5: Authentication Algorithms
Prerequisite: B.2/1 – IUT supports authentication
Item Algorithm Reference Status Support
1 TA11 [1] 4.1.2 m
TA12 [1] 4.1.2 m
3 TA21 [1] 4.1.3 m
4 TA22 [1] 4.1.3 m
NOTE: Support of any of the algorithms (TAxx) requires that the conformance tests
defined for the algorithms have been successfully completed.
Comment: It is stated in ETS 300 392-7ed.2, subclause 4.4.2 that if a terminal supports authentication
then it shall support all modes. This therefore requires that all entries in table B.5 are mandatory.
B.4.2 Authentication cipher keys
The supplier of the implementation shall state the support of the store of the cipher key to TETRA address
relations.
Table B.6: Authentication cipher key support
Prerequisite: B.2/1 – IUT supports authentication
Item Cipher key Reference Status Support
1 K-ITSI [1] 4.2.6 m
B.4.3 Authentication PDUs
The supplier of the implementation shall state the support in the implementation for each of the
authentication PDUs presented in tables B.7. to B.10.

Page 19
ETS 300 394-5-1: July 1999
Table B.7: Downlink PDUs for authentication
Prerequisite: B.2/1 – IUT supports authentication
Item Authentication PDUs Reference Status Support
1 D-AUTHENTICATION DEMAND [1] 4.4.7.1 m
D-AUTHENTICATION RESPONSE [1] 4.4.7.3 m
3 D-AUTHNETICATION RESULT [1] 4.4.7.4 m
4 D-AUTHENTICATION REJECT [1] 4.4.7.2 m
D-LOCATION UPDATE ACCEPT [1] 4.4.2.5 m
Comment: D-LOCATION UPDATE ACCEPT contains cipher negotiation parameters and may include the
Authentication Downlink type-3 element.
Table B.8: Uplink PDUs for authentication
Prerequisite: B.2/1 – IUT supports authentication
Item Authentication PDUs Reference Status Support
U-AUTHENTICATION DEMAND [1] 4.4.7.9 m
2 U-AUTHENTICATION RESPONSE [1] 4.4.7.11 m
3 U-AUTHENTICATION RESULT [1] 4.4.7.12 m
U-AUTHENTICATION REJECT [1] 4.4.7.10 m
5 U-LOCATION UPDATE DEMAND [1] 4.4.2.5 m
Comment: U-LOCATION UPDATE DEMAND contains cipher negotiation parameters and may include the
Authentication Downlink type-3 element.
B.4.4 Authentication PDU elements
The supplier of the implementation shall state the support of the implementation for each of the
authentication PDU elements presented in tables B.9 to B.16.
Table B.9: Elements for D-AUTHENTICATION DEMAND PDU
Prerequisite: B.7/1 – IUT supports D-AUTHENTICATION DEMAND
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
Authentication sub-type [1] 4.4.7 m
3 Random challenge [RAND1] [1] 4.4.9.24 m
Random seed [RS] [1] 4.4.9.25 m
5 Proprietary element [1] 4.4.9.22 o
Table B.10: Elements for D-AUTHENTICATION RESPONSE PDU
Prerequisite: B.7/2 – IUT supports D-AUTHENTICATION RESPONSE
Item Element Reference Status Support
PDU Type [1] 4.4.9.21 m
2 Authentication sub-type [1] 4.4.7 m
Random seed [RS] [1] 4.4.9.25 m
4 Response value [RES2] [1] 4.4.9.27 m
5 Mutual authentication flag [1] 4.4.9.16 m
Random challenge [RAND1] [1] 4.4.9.24 m
7 Proprietary element [1] 4.4.9.22 o

Page 20
ETS 300 394-5-1: July 1999
Table B.11: Elements for D-AUTHENTICATION RESULT PDU
Prerequisite: B.7/3 – IUT supports D-AUTHENTICATION RESULT
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
Authentication sub-type [1] 4.4.7 m
3 Authentication result [R1] [1] 4.4.9.3 m
4 Mutual authentication flag [1] 4.4.9.16 m
Response value [RES2] [1] 4.4.9.27 m
6 Proprietary element [1] 4.4.9.22 o
Table B.12: Elements for D-AUTHENTICATION REJECT PDU
Prerequisite: B.7/4 – IUT supports D-AUTHENTICATION REJECT
Item Element Reference Status Support
PDU Type [1] 4.4.9.21 m
2 Authentication sub-type [1] 4.4.7 m
Authentication reject reason [1] 4.4.9.2 m
Table B.13: Elements for U-AUTHENTICATION DEMAND PDU
Prerequisite: B.8/1 – IUT supports U-AUTHENTICATION DEMAND
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
Authentication sub-type [1] 4.4.7 m
3 Random challenge [RAND2] [1] 4.4.9.24 m
Proprietary element [1] 4.4.9.22 o
Table B.14: Elements for U-AUTHENTICATION RESPONSE PDU
Prerequisite: B.8/2 – IUT supports U-AUTHENTICATION RESPONSE
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
Authentication sub-type [1] 4.4.7 m
3 Response value [RES1] [1] 4.4.9.27 m
4 Mutual authentication flag [1] 4.4.9.16 m
Random challenge [RAND2] [1] 4.4.9.24 m
6 Proprietary element [1] 4.4.9.22 o
Table B.15: Elements for U-AUTHENTICATION RESULT PDU
Prerequisite: B.8/3 – IUT supports U-AUTHENTICATION RESULT
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
2 Authentication sub-type [1] 4.4.7 m
Authentication result [R2] [1] 4.4.9.3 m
4 Mutual authentication flag [1] 4.4.9.16 m
5 Response value [RES1] [1] 4.4.9.27 m
6 Proprietary element [1] 4.4.9.22 o

Page 21
ETS 300 394-5-1: July 1999
Table B.16: Elements for U-AUTHENTICATION REJECT PDU
Prerequisite: B.8/4 – IUT supports U-AUTHENTICATION REJECT
Item Element Reference Status Support
1 PDU Type [1] 4.4.9.21 m
Authentication sub-type [1] 4.4.7 m
3 Authentication reject reason [1] 4.4.9.2 m
B.4.5 Registration PDU extended elements
The support of authentication during registration requires that the implementation support the MM PDUs
identified by B.7/5 and B.8/5. Support of the MM-registration PDUs shall be declared in the TETRA V+D
PICS Proforma ETS 300 392-14. The following "type 3" elements are used to support authentication in
these PDUs.
Table B.17: MM Type 3 elements for security enabling at registration
Prerequisite: B.7/5 or B.8/5 – IUT supports U-LOCATION UPDATE COMMAND or
D–LOCATION UPDATE ACCEPT PDUs
Item Type 3 element Reference Status Support
Authentication uplink [1] 4.4.8.2
1 m
2 Authentication downlink [1] 4.4.8.1 m
Table B.18: Elements for authentication uplink type 3 element
Prerequisite: B.17/1 – IUT supports authentication uplink type 3 element
Item Element Reference Status Support
1 CCK request flag [1] 4.4.9.6 m
2 Random challenge [1] 4.4.9.24
m
Table B.19: Elements for authentication downlink type 3 ele
...