Abstract

Conformance Testing for ETS 300 391-1

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Documents

Standard

SIST ETS 300 391-3 E1:2003

English language (20 pages)
Preview
Preview
e-Library read for
×1 day

SIST ETS 300 391-3 E1:2003 is the Slovenian adoption of ETS 300 391-3 Edition 1, published by SIST and originating from ETSI. It is a Conformance Test Specification (CTS) for the security architecture of Universal Personal Telecommunication (UPT) phase 1, and it defines how to test advanced Dual Tone Multi Frequency (DTMF) devices and Authenticating Entities (AEs) against ETS 300 391-1 and ETS 300 391-2.

What does SIST ETS 300 391-3 E1:2003 specify?

SIST ETS 300 391-3 E1:2003 specifies the tests needed to verify conformance of advanced DTMF devices and AEs with the UPT phase 1 security architecture. In practice, it is the testing document you use when you need a structured way to check whether an implementation follows the security and authentication behavior defined in the related specification and ICS proformas.

The document focuses on:

  • the test suite and test purposes,
  • the test methods and configurations,
  • the test steps and test cases.

Its structure is straightforward:

  • Clause 1 gives the scope.
  • Clause 2 lists normative references.
  • Clause 3 defines abbreviations.
  • Clause 4 describes the test suite structure.
  • Clause 5 gives the test purposes.
  • Clause 6 explains the test methods and configurations.
  • Clause 7 gives the test cases.
  • Annex A is a bibliography.

For readers, that means the standard is not a service description or a protocol definition. It is the test companion used to check implementations against the UPT security architecture.

What are the key requirements of SIST ETS 300 391-3 E1:2003?

SIST ETS 300 391-3 E1:2003 organizes conformance testing around two implementations under test: the advanced DTMF device and the AE. Clause 5 states that the tests aim both to verify compliance with ETS 300 391-1 and to support interoperability between products from different manufacturers. That matters because the same security functions must behave consistently across different equipment.

Test suite structure and test purpose coding

Clause 4 defines the Test Suite Structure (TSS) and the mnemonic format for test purposes. The test names identify the implementation under test, the major function, the nature of the test, and a number within the test group. In practice, this lets a test lab trace every test case to a specific function such as DHV, strong authentication, or weak authentication.

Advanced DTMF device testing

Clause 5.1 groups the advanced DTMF device tests into:

  • Device Holder Verification (DHV),
  • strong authentication,
  • physical protection of sensitive data.

These tests check whether the device accepts the authorized user, produces the authentication data correctly, increments the sequence number, and protects sensitive data such as PUI, n, and K. That matters because the device must not only generate the right authentication output but also resist unauthorized access to stored security data.

Clause 7.1 turns those purposes into concrete test cases:

  • DHV tests check successful and unsuccessful verification and the timeout behavior.
  • Strong authentication tests check the DTMF output format, the Authentication Code (AC), and the sequence number update.
  • Physical protection test purposes are listed, but the document treats them as untestable in the test cases.

AE testing

Clause 5.2 defines the AE test group around:

  • PUI check,
  • weak authentication,
  • strong authentication.

The AE tests check that the Authenticating Entity validates the PUI, handles blacklists, processes PIN and SPIN behavior for weak authentication, and checks AC and sequence-number range for strong authentication. In practice, this is the part that confirms the network-side security checks are working as intended.

Clause 7.2 provides the test cases for:

  • invalid and blacklisted PUI handling,
  • successful and failed weak authentication,
  • blocking and unblocking behavior with PIN and SPIN,
  • strong authentication with valid and invalid n and AC values.

Test methods and configurations

Clause 6 says the advanced DTMF device is tested locally, with keyboard, display, loudspeaker, and microphone used as points of control and observation. It also states that the AE is tested by the distributed test method. This matters because the two implementations are exercised in different environments: one as a local user device, the other as a network entity.

Clause 6 also states that the test laboratory chooses the identification and authentication parameters to be implemented in the AE and, where applicable, in the advanced DTMF device. That means the lab controls the test data, while the manufacturer provides the implementation and the means to install those values.

Test framework limits

Clause 1 states that the TTCN description of test cases is outside the scope of this ETS. It also says that a partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma is not identified as applicable. For a reader, this means the document defines what to test and how to structure the tests, but not the TTCN description itself.

What terms does SIST ETS 300 391-3 E1:2003 define?

  • AC (Authentication Code) - the code calculated in the UPT access device and checked during strong authentication.
  • AE (Authenticating Entity) - the entity that performs authentication checks for UPT users.
  • DHV (Device Holder Verification) - the step that verifies the holder of the device before authentication can proceed.
  • DTMF (Dual Tone Multi Frequency) - the tone signaling method used by the advanced device to send authentication data.
  • IUT (Implementation Under Test) - the device or entity being tested for conformance.
  • PCO (Point of Control and Observation) - the interface used by the tester to control or observe the implementation.
  • PUI (Personal User Identity) - the identity used to identify the user during authentication.
  • SPIN (Special Personal Identification Number) - the special number used for unblocking in weak authentication.
  • TTCN (Tree and Tabular Combined Notation) - the formal notation used to describe test cases.
  • UPT (Universal Personal Telecommunication) - the service concept for personal mobility across networks and terminals.

Who uses SIST ETS 300 391-3 E1:2003?

SIST ETS 300 391-3 E1:2003 is used by test laboratories, manufacturers, and conformity assessment teams working on UPT phase 1 security functions. It is relevant to engineers and quality managers who need to verify advanced DTMF devices or AEs against the security architecture specification.

It is also useful for:

  • product developers implementing DHV, weak authentication, or strong authentication,
  • laboratory staff preparing conformance tests and selecting test parameters,
  • buyers or evaluators who need to understand what kind of evidence a supplier can provide,
  • interoperability testing teams checking that products from different manufacturers work together.

What changed in SIST ETS 300 391-3 E1:2003 from the previous edition?

SIST ETS 300 391-3 E1:2003 is identical to ETS 300 391-3 Edition 1. The document history identifies the original publication as the first edition.

Which standards are used with SIST ETS 300 391-3 E1:2003?

Clause 2 names the main standards and documents used with this CTS:

  • ETS 300 391-1 - the specification of the UPT phase 1 security architecture that the tests verify.
  • ETS 300 391-2 - the Implementation Conformance Statement (ICS) proformas that accompany the specification.
  • I-ETS 300 380 - the DTMF sender specification for acoustic coupling to a handset microphone, relevant to advanced DTMF device testing.
  • ISO/IEC 9646 parts 1 to 5 - the conformance testing methodology and framework used for the testing approach.

What does the SIST ETS 300 391-3 E1:2003 document contain?

The document contains a test suite structure, detailed test purposes, test methods and configurations, and 15 test cases covering the advanced DTMF device and the AE. It includes figures showing the test suite structure and the test configurations for both implementations, which helps a test laboratory understand where each control and observation point sits.

The test cases cover DHV, strong authentication, PUI checking, weak authentication, unblocking, PIN change, and sequence-number behavior. For practical use, this gives testers a direct map from a security function to the test case that exercises it.

Annex A provides a bibliography for related UPT and testing documents.

Buy Documents

Standard

SIST ETS 300 391-3 E1:2003

English language (20 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST ETS 300 391-3 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Universal Personal Telecommunication (UPT); Specification of the security architecture for UPT phase 1; Part 3: Conformance Test Specification (CTS)". This standard covers: Conformance Testing for ETS 300 391-1

Conformance Testing for ETS 300 391-1

SIST ETS 300 391-3 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST ETS 300 391-3 E1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-december-2003
Svetovne osebne telekomunikacije (UPT) – Specifikacija varnostne arhitekture za
1. fazo sistema UPT – 3. del: Specifikacija za preskušanje skladnosti (CST)
Universal Personal Telecommunication (UPT); Specification of the security architecture
for UPT phase 1; Part 3: Conformance Test Specification (CTS)
Ta slovenski standard je istoveten z: ETS 300 391-3 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 391-3
TELECOMMUNICATION August 1995
STANDARD
Source: ETSI TC-NA Reference: DE/NA-071403
ICS: 33.040
Authentication, DTMF, security, UPT
Key words:
Universal Personal Telecommunication (UPT);
Specification of the security architecture for UPT phase 1;
Part 3: Conformance Test Specification (CTS)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 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 1995. All rights reserved.
New presentation - see History box

Page 2
ETS 300 391-3: August 1995
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 3
ETS 300 391-3: August 1995
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Abbreviations.8
4 Test suite structure.8
5 Test purposes .9
5.1 Advanced DTMF device test group .9
5.1.1 DHV test purposes .9
5.1.2 Strong authentication test purposes.10
5.1.3 Physical protection test purposes.10
5.2 AE test group .10
5.2.1 PUI check test purposes .11
5.2.2 Weak authentication test purposes.11
5.2.3 Strong authentication test purposes.12
6 Test methods and configurations.12
6.1 Advanced DTMF device.13
6.2 AE .13
6.2.1 Strong authentication .14
6.2.2 Weak authentication.15
7 Test cases.15
7.1 Advanced DTMF device.15
7.1.1 DHV.15
7.1.2 Strong authentication .16
7.1.3 Physical protection .16
7.2 AE .16
7.2.1 PUI check.16
7.2.2 Weak authentication.17
7.2.3 Strong authentication. .18
Annex A (informative): Bibliography.19
History.20

Page 4
ETS 300 391-3: August 1995
Blank page
Page 5
ETS 300 391-3: August 1995
Foreword
This European Telecommunication Standard (ETS) has been produced by the Network Aspects (NA)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS consists of 3 parts as follows:
Part 1: "Specification".
Part 2: "Implementation Conformance Statement (ICS) proformas".
Part 3: "Conformance Test Specification (CTS)".
Transposition dates
Date of adoption of this ETS: 28 July 1995
Date of latest announcement of this ETS (doa): 30 November 1995
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 May 1996
Date of withdrawal of any conflicting National Standard (dow): 31 May 1996
Introduction
Universal Personal Telecommunication (UPT) is a service that enables improved access to
telecommunication service by allowing personal mobility. It enables each UPT user to participate in a user
defined set of subscribed services, and to initiate and receive calls on the basis of a unique, personal,
network independent UPT number across multiple networks at any terminal, fixed, movable or mobile.
ETSI Sub Technical Committee (STC) NA 7 has defined three service scenarios for UPT (see
ETR 055-2). The specification of the security architecture for UPT phase 1 (ETS 300 391-1 [1]) deals only
with the restricted, short term UPT service scenario for UPT phase 1. This scenario has restrictions on
networks, services, user friendliness and also on the possibilities to implement security features.
ETS 300 391-1 [1] has specified the mechanisms for weak and strong authentication. The detailed
specification of the protocols within the Intelligent Network will be described elsewhere as part of the
specification of the overall UPT protocols.

Page 6
ETS 300 391-3: August 1995
Blank page
Page 7
ETS 300 391-3: August 1995
1 Scope
This European Telecommunication Standard (ETS) provides a Conformance Test Specification (CTS)
specifying the tests which are necessary to verify the conformance of advanced Dual Tone
Multi Frequency (DTMF) devices and Authenticating Entities (AEs) with ETS 300 391-1 [1] and
ETS 300 391-2 [2].
In particular, the following issues are considered:
- test suite and test purposes;
- test methods and configurations;
- test steps and test cases.
The Tree and Tabular Combined Notation (TTCN) description of test cases is outside the scope of this
ETS. However, the TTCN description may be part of the CTSs of the overall Universal Personal
Telecommunication (UPT) protocol specifications.
A partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma is not identified as
applicable for this CTS.
The conformance testing methodology and framework used in this ETS is given in ISO/IEC 9646 [4].
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 391-1: "Universal Personal Telecommunication (UPT); Specification of
the security architecture for UPT phase 1; Part 1: Specification".
[2] ETS 300 391-2: "Universal Personal Telecommunication (UPT); Specification of
the security architecture for UPT phase 1; Part 2: Implementation Conformance
Statement (ICS) proformas".
[3] I-ETS 300 380: "Universal Personal Telecommunications (UPT); Access
devices; Dual Tone Multi Frequency (DTMF) sender for acoustic coupling to the
microphone of a handset telephone".
[4] ISO/IEC 9646, parts 1 - 5: "Conformance Testing Methodology and Framework".

Page 8
ETS 300 391-3: August 1995
3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AC Authentication Code, calculated in the UPT access device
AE Authenticating Entity
d tolerance for the difference between the sequence number sent by the UPT
access device and the sequence number stored in the SDF
DHV Device Holder Verification
DTMF Dual Tone Multi Frequency
f algorithm for the calculation of the AC
IUT Implementation Under Test
K Key
LPIN Local Personal Identification Number
n sequence number, used by the UPT access device
n sent part of the sequence number, i.e. the 16 least significant bits of n
s
PCO Point of Control and Observation
PIN Personal Identification Number
PIXIT Protocol Implementation eXtra Information for Testing
PUI Personal User Identity
SDF Service Data Function
SLPIN Special Local Personal Identification Number
SPIN Special Personal Identification Number
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UPT Universal Personal Telecommunication
4 Test suite structure
Figure 1 shows the Test Suite Structure (TSS).
Authentication
Security feature
Implementation
Advanced Authenticating
under test
DTMF device (D) Entity (A)
Major
Device  Physical Strong  Weak Strong
PUI
functions
Holder Protection Authentication Authentication Authentication
check
Verification (PP) (SA) (WA) (SA)
(PC)
(HV)
Invalid Invalid
Nature Capability Valid  Capability Valid
Behaviour Behaviour
of test tests (CA) Behaviour  tests (CA) Behaviour
tests (BI) tests (BI)
tests (BV) tests (BV)
Figure 1: The TSS
The characters within parentheses in figure 1 are used in the mnemonics identifying each test purpose in
the following clauses. Every mnemonic consists of four fields:
a) {implementation under test};
b) {major function};
c) {nature of test};
d) {number within the test group}.
EXAMPLE: Capability test number 1 of the strong authentication of the advanced DTMF
device is coded DSACA1.
Page 9
ETS 300 391-3: August 1995
5 Test purposes
Two entities in the UPT security architecture have been identified to need testing:
- the advanced DTMF device; and
- the AE.
There are two objectives to be met:
- to ensure that both entities have been implemented in accordance with the requirements stated in
ETS 300 391-1 [1];
- to achieve interoperability between products from different manufacturers.
The references made in this clause can be found in ETS 300 391-1 [1].
5.1 Advanced DTMF device test group
The advanced DTMF device is tested with respect to the following aspects:
- Device Holder Verification (DHV) is correctly implemented;
- the data for strong authentication is correctly sent;
- sensitive data is physically protected.
5.1.1 DHV test purposes
DHVCA1: Check that the device can perform DHV (covered by DHVBV1 and DHVBI1).
Initial conditions: The device is not blocked.
Reference: 8 requirements for the security module and 8.2 processing.
Check that the authorised user is accepted by the DHV.
DHVBV1:
The device is not blocked.
Initial conditions:
Reference: 8.2 processing.
DHVBV2: Check that authentication attempts can be performed after a successful DHV.
Initial conditions: The device is not blocked.
Reference: 8.2 processing.
Check that incorrect DHV attempts fail.
DHVBI1:
The device not being blocked.
Initial conditions:
Reference: 8 requirements for the security module, 8.2 processing.
DHVBI2: Check that no authentication attempt can be performed without a previous
successful DHV.
Initial conditions: None.
8.2 processing.
Reference:
Check that an authentication attempt cannot be performed when the time-out
DHVBI3:
has been reached.
Initial conditions: A successful DHV has been performed.
Reference: 8.2 processing.
Page 10
ETS 300 391-3: August 1995
5.1.2 Strong authentication test purposes
Check that the Authentication Code (AC) is correctly calculated and correctly
DSACA3:
converted to DTMF signals by the device.
Initial conditions: A DHV has been successfully performed and the time-out has not been
reached. The expected value of AC and the value of n and K used are known
by the tester.
11 authentication algorithms and 8.2 processing.
Reference:
DSABV3: Check that n is incremented by one at every authentication attempt.
Initial conditions: n is known by the tester and it has not reached its maximum value.
Reference: 8.2.5 Sequence number incrementation.
Check that the conversion of n to n as DTMF signals has been correctly
DSACA4:
s
performed.
A successful DHV has been performed.
Initial conditions:
Reference: 8.2.3 Sequence number conversion.
DSABV1: Check that the data field CT is correctly coded.
Initial conditions: An authentication attempt has been made.
Reference: 9.3.2 The authentication process.
5.1.3 Physical protection test purposes
Check that the Personal User Identity (PUI), n and K cannot be written into the
DPPCA1:
device by a user.
Initial conditions: None.
Reference: 8.1 Storage of data.
DPPCA2: Check that K and the authentication algorithm cannot be read out from the
device.
None.
Initial conditions:
8.1 Storage of data.
Reference:
5.2 AE test group
The AE is tested with respect to the following aspects:
- PUI check is implemented;
- strong authentication is correctly implemented;
- and/or weak authentication is correctly implemented.

Page 11
ETS 300 391-3: August 1995
5.2.1 PUI check test purposes
Check that received PUIs are checked with respect to validity at every
APCCA1:
authentication attempt.
Initial conditions: Authentication data has been received.
Reference: 6.2 User authentication mechanisms and 10 requirements for the AE of the
Service Data Function (SDF).
APCCA2: Check that received PUIs are checked against a blacklist at every
authentication attempt.
Authentication data has been received.
Initial conditions:
6.2 User authentication mechanisms and 10 requirements for the AE of the
Reference:
SDF.
...