ETSI ETS 300 760 ed.1 (1997-06)

SLOVENSKI STANDARD
SIST ETS 300 760:2001
01-september-2001
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&7$YWHQWLNDFLMVNLPRGXO
'$0'(&7,]MDYDRVNODGQRVWLL]YHGEH,&63URIRUPDVSHFLILNDFLMH
Digital Enhanced Cordless Telecommunications (DECT); DECT Authentication Module
(DAM); Implementation Conformance Statement (ICS) proforma specification
Ta slovenski standard je istoveten z: ETS 300 760 Edition 1
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
SIST ETS 300 760:2001 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 760:2001

---------------------- Page: 2 ----------------------

SIST ETS 300 760:2001
EUROPEAN ETS 300 760
TELECOMMUNICATION June 1997
STANDARD
Source: ETSI EP-DECT Reference: DE/DECT-060046
ICS: 33.020
Key words: DECT, DAM, ICS, profile, radio, testing
Digital Enhanced Cordless Telecommunications (DECT);
DECT Authentication Module (DAM);
Implementation Conformance Statement (ICS)
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
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
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 1997. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 760:2001
Page 2
ETS 300 760: June 1997
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 Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 760:2001
Page 3
ETS 300 760: June 1997
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions, symbols and abbreviations.7
3.1 Definitions .7
3.2 Symbols .7
3.3 Abbreviations .8
4 Conformance to this ICS proforma specification.8
Annex A (normative): ICS proforma for ETS 300 331.9
A.1 Guidance for completing the ICS proforma.9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions.10
A.1.3 Instructions for completing the ICS proforma .12
A.2 Identification of the implementation.12
A.2.1 Date of the statement .12
A.2.2 Implementation Under Test (IUT) identification .12
A.2.3 System Under Test (SUT) identification .13
A.2.4 Product supplier.13
A.2.5 Client (if different from product supplier) .14
A.2.6 ICS contact person .14
A.3 Identification of the standard .15
A.4 Global statement of conformance .15
A.5 Roles .15
A.6 DECT Authentication Module (DAM).15
A.6.1 Physical characteristics.16
A.6.1.1 Format and layout .16
A.6.1.1.1 ID-1 card.16
A.6.1.1.2 Plug-in card.17
A.6.1.2 Contacts .17
A.6.2 Electronic signals and transmission protocols.18
A.6.2.1 Supply voltage Vcc (contact C1) .18
A.6.2.2 Reset RST (contact C2) .19
A.6.2.3 Clock CLK (contact C3).19
A.6.2.4 I/O (contact C7).20
A.6.2.5 States .20
A.6.2.6 Answer To Reset (ATR) .21
A.6.2.6.1 ATR: TC1 parameter values.21
A.6.3 Logical model.22
A.6.3.1 File identifier .22
A.6.3.2 Dedicated files.22
A.6.3.3 Elementary files.23
A.6.3.4 Methods for selecting the DECT application .23
A.6.3.5 Reservation of file IDs .23

---------------------- Page: 5 ----------------------

SIST ETS 300 760:2001
Page 4
ETS 300 760: June 1997
A.6.3.5.1 DFs. 23
A.6.3.5.2 EFs. 24
A.6.4 Security services and facilities . 24
A.6.4.1 Algorithms and processes . 24
A.6.4.2 Authentication . 25
A.6.4.3 UAK allocation . 25
A.6.4.4 File access control. 26
A.6.5 Description of the functions.26
A.6.6 Description of the commands . 27
A.6.6.1 Mapping principles. 27
A.6.6.2 Coding of the commands. 27
A.6.6.3 Definitions and coding . 28
A.6.6.4 Status conditions returned by the DAM . 28
A.6.6.4.1 Coding of the status words . 28
A.6.6.4.2 Commands versus possible status responses . 28
A.6.7 Contents of the elementary files. 29
A.6.7.1 Contents of the EFs at the MF level . 30
A.6.7.1.1 Optional data parameters in EF . 30
ICC
A.6.7.1.2 Optional data parameters in EF . 30
ID
A.6.7.1.3 Optional data parameters in EF . 31
NAME
A.6.7.1.4 Optional data parameters in EF . 31
DIR
A.6.7.1.5 Optional data parameters in EF . 31
LANG
A.6.7.2 Contents of the EFs at the parent level of the DECT application . 32
A.6.7.3 Contents of the EFs at the DECT application level. 32
A.6.7.3.1 Optional data parameters in EF . 32
LSR
A.6.7.4 Contents of the EFs at the subscription registration level. 33
A.6.7.4.1 DF . 33
SR1
A.6.7.4.1.1 Optional data parameters in EF . 33
PARK
A.6.7.4.1.2 Optional data parameters in EF . 34
UAK
A.6.7.4.1.3 Optional data parameters in EF . 34
AC
A.6.7.4.2 DF . 35
SR2
A.6.7.4.2.1 Optional data parameters in EF . 35
PARK
A.6.7.4.2.2 Optional data parameters in EF . 36
UAK
A.6.7.4.2.3 Optional data parameters in EF . 36
AC
A.7 DECT Portable Equipment (PE) . 37
A.7.1 Physical characteristics. 37
A.7.2 Electronic signals and transmission protocols . 38
A.7.2.1 Supply voltage Vcc (contact C1). 39
A.7.2.2 Reset RST (contact C2) . 39
A.7.2.3 Programming voltage Vpp (contact C6) . 40
A.7.2.4 Clock CLK (contact C3) . 40
A.7.2.5 I/O (contact C7) . 41
A.7.2.6 States. 41
A.7.2.7 Answer To Reset (ATR) . 42
A.7.3 Logical model . 42
A.7.3.1 Methods for selecting the DECT application. 42
A.7.4 Description of the commands . 43
A.7.4.1 Mapping principles. 43
A.7.4.2 Coding of the commands. 43
A.7.5 Application protocol. 44
A.7.5.1 General procedures. 44
A.7.5.2 DAM management procedures. 44
A.7.5.3 CHV related procedures . 44
A.7.5.4 Authentication procedures. 45
A.7.5.5 UAK allocation . 45
A.7.5.6 General information procedures . 45
A.7.5.7 Subscription registration maintenance. 46
Annex B (informative): Bibliography . 47
History. 48

---------------------- Page: 6 ----------------------

SIST ETS 300 760:2001
Page 5
ETS 300 760: June 1997
Foreword
This European Telecommunication Standard (ETS) has been produced by the Digital Enhanced Cordless
Telecommunications (DECT) Project of the European Telecommunications Standards Institute (ETSI).
Transposition dates
Date of adoption: 23 May 1997
Date of latest announcement of this ETS (doa): 30 September 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 March 1998
Date of withdrawal of any conflicting National Standard (dow): 31 March 1998
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which
capabilities and options have been implemented for a telecommunication specification. Such a statement
is called an Implementation Conformance Statement (ICS).

---------------------- Page: 7 ----------------------

SIST ETS 300 760:2001
Page 6
ETS 300 760: June 1997
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 760:2001
Page 7
ETS 300 760: June 1997
1 Scope
This European Telecommunication Standard (ETS) provides the Implementation Conformance Statement
(ICS) proforma for the Digital Enhanced Cordless Telecommunications (DECT) Authentication Module
(DAM) and portable equipment defined in ETS 300 331 [1] in compliance with the relevant requirements,
and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [2].
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 331 (1995): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); DECT Authentication Module (DAM)".
[2] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[3] ISO/IEC 9646-1 (1995): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts".
[4] ISO/IEC 9646-7 (1995): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation Conformance Statements".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 331 [1];
- terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-7 [4].
In particular, the following terms defined in ISO/IEC 9646-1 [3] apply:
Implementation Conformance Statement (ICS): A 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: A document, in the form of a questionnaire, which when completed for an implementation
or system becomes an ICS.
3.2 Symbols
For the purposes of this ETS, the following symbols apply:
{} Optional data, e.g. "CLA, INS, P1, P2, P3 {, data}" indicates that data may or
may not follow the CLA, INS, P1, P2, P3 bytes.

---------------------- Page: 9 ----------------------

SIST ETS 300 760:2001
Page 8
ETS 300 760: June 1997
3.3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
DECT Digital Enhanced Cordless Telecommunications
ICS Implementation Conformance Statement
IUT Implementation Under Test
PE Portable Equipment
SCS System Conformance Statement
SUT System Under Test
UAK User Authentication Key
4 Conformance to this ICS proforma specification
If it claims to conform to this ETS, the actual ICS proforma to be filled in by a supplier shall be technically
equivalent to the text of the ICS proforma given in annex A, and shall preserve the numbering/naming and
ordering of the proforma items.
An ICS which conforms to this ETS shall be a conforming ICS proforma completed in accordance with the
guidance for completion given in clause A.1.

---------------------- Page: 10 ----------------------

SIST ETS 300 760:2001
Page 9
ETS 300 760: June 1997
Annex A (normative): ICS proforma for ETS 300 331
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 ICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed ICS.
A.1 Guidance for completing the ICS proforma
A.1.1 Purposes and structure
The purpose of this ICS proforma is to provide a mechanism whereby a supplier of an implementation of
the requirements defined in ETS 300 331 [1] may provide information about the implementation in a
standardized manner.
The ICS proforma is subdivided into subclauses for the following categories of information:
- guidance for completing the ICS proforma;
- identification of the implementation;
- identification of the standard;
- global statement of conformance;
- roles;
- DECT Authentication Module (DAM):
- physical characteristics:
- format and layout:
- ID-1 card;
- plug-in card;
- Contacts;
- electronic signals and transmission protocols:
- supply Voltage Vcc (contact C1);
- Reset RST (contact C2);
- Clock CLK (contact C3);
- I/O (contact C7);
- states;
- Answer To Reset (ATR):
- ATR: TC1 parameter values;
- logical model:
- file identifier;
- dedicated files;
- elementary files;
- methods for selecting the DECT application;
- reservation of file IDs:
- DFs;
- EFs;
- security services and facilities:
- algorithms and processes;
- authentication;
- UAK allocation;
- file access control;
- description of the functions;
- description of the commands:
- mapping principles;
- coding of the commands;
- definitions and coding;
- status conditions returned by the DAM:
- coding of the status words;
- commands versus possible status responses;
- contents of the elementary files:
- contents of the EFs at the MF level:
- optional data parameters in EF ;
ICC
- optional data parameters in EF ;
ID
- optional data parameters in EF ;
NAME
- optional data parameters in EF ;
DIR

---------------------- Page: 11 ----------------------

SIST ETS 300 760:2001
Page 10
ETS 300 760: June 1997
- optional data parameters in EF ;
LANG
- contents of the EFs at the parent level of the DECT application;
- contents of the EFs at the DECT application level:
- optional data parameters in EF ;
LSR
- contents of the EFs at the subscription registration level:
-DF :
SR1
- optional data parameters in EF ;
PARK
- optional data parameters in EF ;
UAK
- optional data parameters in EF ;
AC
-DF :
SR2
- optional data parameters in EF ;
PARK
- optional data parameters in EF ;
UAK
- optional data parameters in EF ;
AC
- DECT Portable Equipment (PE):
- physical characteristics;
- electronic signals and transmission protocols:
- supply Voltage Vcc (contact C1);
- Reset RST (contact C2);
- programming Voltage Vpp (contact C6);
- Clock CLK (contact C3);
- I/O (contact C7);
- states;
- Answer To Reset (ATR);
- logical model:
- methods for selecting the DECT application;
- description of the commands:
- mapping principles;
- coding of the commands;
- application protocol:
- general procedures;
- DAM management procedures;
- CHV related procedures;
- authentication procedures;
- UAK allocation;
- general information procedures;
- subscription registration maintenance.
A.1.2 Abbreviations and conventions
The ICS proforma contained in this annex is comprised of information in tabular form in accordance with
the guidelines presented in ISO/IEC 9646-7 [4].
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. parameters, timers, etc.). It
implicitly means "is supported by the implementation?".

---------------------- Page: 12 ----------------------

SIST ETS 300 760:2001
Page 11
ETS 300 760: June 1997
Status column
The following notations, defined in ISO/IEC 9646-7 [4], 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.
x prohibited (excluded) - there is a requirement not to use this capability in the
given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer which identifies an 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 an
unique conditional status expression which is defined immediately following the
table.
Reference column
The reference column gives reference to ETS 300 331 [1], except where explicitly stated otherwise.
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 [4], 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).
If this ICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary
to be able to answer that a capability is supported for one profile and not supported for another. In that
case, the supplier shall enter the unique reference to a conditional expression, preceded by "?" (e.g. ?3).
This expression shall be given in the space for comments provided at the bottom of the table. It uses
predicates defined in the SCS, each of which refers to a single profile and which takes the value TRUE if
and only if that profile is to be used.
EXAMPLE 1: ?3: IF prof1 THEN Y ELSE N
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
References to items
For each possible item answer (answer in the support column) within the ICS 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 shall be discriminated by letters (a, b, etc.), respectively.
EXAMPLE 2: A.5/4 is the reference to the answer of item 4 in table A.5 of annex A.
EXAMPLE 3: A.6/3b is the reference to the second answer (i.e. in the second support column)
of item 3 in table A.6 of annex A.

---------------------- Page: 13 ----------------------

SIST ETS 300 760:2001
Page 12
ETS 300 760: June 1997
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not
required to be completed if the predicate is FALSE.
A.1.3 Instructions for completing the ICS proforma
The supplier of the implementation shall complete the ICS proforma in each of the spaces provided. In
particular, an explicit answer shall be entered, in each of the support boxes provided, using the notation
described in subclause A.1.2.
However, the tables containing in the "DECT Authentication Module" subclause shall only be completed
for DAM implementations, and the tables containing in the "DECT Portable Equipment" subclause shall
only be completed for PE implementations.
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 ICS proforma.
A.2 Identification of the implementation
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 ICS 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: 14 ----------------------

SIST ETS 300 760:2001
Page 13
ETS 300 760: June 1997
A.2.3 System Under Test (SUT) identification
SUT name:
.........................................................................................................................................................................
.........................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Operating system:
.........................................................................................................................................................................
A.2.4 Product supplier
Name:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.................................................................................................
...