ETSI EN 301 060-4 V1.1.4 (1999-08)

SLOVENSKI STANDARD
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13URWRNROGLJLWDOQHQDURþQLãNH
VLJQDOL]DFLMHãW'66.UPLOMHQMHRVQRYQHJDNOLFD,]EROMãDQMHYYVWRSQLWRþNL
EVWRULWYH]DDSOLNDFLMHQDYLGH]QHJD]DVHEQHJDRPUHåMD931GHO$EVWUDNWQL
SUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHGHOQHL]YHGEH
SURWRNROD3,;,76SHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one
(DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual
Private Network (VPN) applications; Part 4: Abstract Test Suite (ATS) and partial
Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for
the user
Ta slovenski standard je istoveten z: EN 301 060-4 Version 1.1.4
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Digital Subscriber Signalling System No. one (DSS1) protocol;
Basic call control;
Enhancement at the "b" service entry point for
Virtual Private Network (VPN) applications;
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user

2 ETSI EN 301 060-4 V1.1.4 (1999-08)
Reference
DEN/SPS-05109-4 (9td00ieo.PDF)
Keywords
ISDN, DSS1, ATS, basic, PIXIT, VPN, user
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
secretariat@etsi.fr
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
editor@etsi.fr
comment to:
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.
ETSI
3 ETSI EN 301 060-4 V1.1.4 (1999-08)
Contents
Intellectual Property Rights. 5
Foreword. 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions .7
3.1.1 Definitions related to conformance testing .7
3.1.2 Definitions related to EN 301 060-1 .8
3.2 Abbreviations .8
4 Abstract Test Method (ATM). 9
5 Untestable test purposes . 9
6 ATS conventions. 9
6.1 Declarations part.9
6.1.1 Type definitions.9
6.1.1.1 Simple type definitions.9
6.1.1.2 Structured type definitions.10
6.1.1.2.1 TTCN structured type definitions.10
6.1.1.2.2 ASN.1 structured type definitions .10
6.1.1.3 ASP type definitions.10
6.1.1.3.1 TTCN ASP type definitions .10
6.1.1.3.2 ASN.1 ASP type definitions.10
6.1.1.4 PDU type definitions.11
6.1.1.4.1 TTCN PDU type definitions.11
6.1.1.4.2 ASN.1 PDU type definitions .11
6.1.2 Test suite constants.11
6.1.3 Test suite parameters.11
6.1.4 Variables.11
6.1.4.1 Test suite variables.11
6.1.4.2 Test case variables.11
6.1.5 Test suite operation definitions .11
6.2 Constraints part.12
6.2.1 Structured type constraint declaration .12
6.2.2 ASN.1 type constraint declaration.12
6.2.3 ASP type constraint declaration .12
6.2.3.1 ASN.1 ASP type constraint declaration.12
6.2.3.2 TTCN ASP type constraint declaration .12
6.2.4 PDU type constraint declaration.12
6.2.4.1 ASN.1 PDU type constraint declaration .12
6.2.4.2 TTCN PDU type constraint declaration.12
6.2.4.3 Special coding.13
6.2.5 Derived constraints .13
6.2.6 Parameterized constraints.13
6.2.7 Value assignment.13
6.2.7.1 Specific values .13
6.2.7.2 Matching values.13
6.3 Dynamic part.13
6.3.1 Test cases.13
6.3.2 Test steps.13
6.3.3 Defaults .13
ETSI
4 ETSI EN 301 060-4 V1.1.4 (1999-08)
7 ATS to TP map. 13
8 PCTR conformance . 14
9 PIXIT conformance. 14
10 ATS conformance. 14
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 15
A.1 Identification summary. 15
A.1.1 Protocol conformance test report .15
A.1.2 IUT identification.15
A.1.3 Testing environment.15
A.1.4 Limits and reservations.15
A.1.5 Comments.16
A.2 IUT conformance status . 16
A.3 Static conformance summary. 16
A.4 Dynamic conformance summary. 16
A.5 Static conformance review report. 16
A.6 Test campaign report . 17
A.7 Observations. 34
Annex B (normative): Partial PIXIT proforma . 35
B.1 Identification summary. 35
B.2 Abstract test suite summary . 35
B.3 Test laboratory. 35
B.4 Client (of the test laboratory). 36
B.5 System Under Test (SUT). 36
B.6 Protocol information . 37
B.6.1 Protocol identification .37
B.6.2 Configuration to be tested .37
B.6.3 Configuration options.37
B.6.4 Test management timers .38
B.6.5 Sending of messages by IUT .38
B.6.6 Parameter values.39
Annex C (normative): Abstract Test Suite (ATS). 41
C.1 The TTCN Graphical form (TTCN.GR) . 41
C.2 The TTCN Machine Processable form (TTCN.MP). 41
Annex D (informative): General structure of ATS . 42
Annex E (informative): TTCN MP and GR version history. 43
History. 44
ETSI
5 ETSI EN 301 060-4 V1.1.4 (1999-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in
SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can
be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server) which
are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Signalling
Protocols and Switching (SPS).
The present document is part 4 of a multi-part standard covering the Digital Subscriber Signalling System No. one (DSS1)
protocol specification for the Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control
extensions at the "b" service entry point for Virtual Private Network (VPN) applications, as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network".
National transposition dates
Date of adoption of this EN: 6 August 1999
Date of latest announcement of this EN (doa): 30 November 1999
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 May 2000
Date of withdrawal of any conflicting National Standard (dow): 31 May 2000
ETSI
6 ETSI EN 301 060-4 V1.1.4 (1999-08)
1 Scope
This fourth part of EN 301 060 is applicable to the Basic call control extensions at the "b" service entry point for VPN
applications for the pan-European Integrated Services Digital Network (ISDN) as provided by European public
telecommunications operators at the T reference point (as defined in ITU-T Recommendation I.411 [11]) by means of the
Digital Subscriber Signalling System No. one (DSS1) protocol. Stage three identifies the protocol procedures and
switching functions needed to support a telecommunications service (see ITU-T Recommendation I.130 [10]).
The present document specifies the Abstract Test Suite (ATS), and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma for the user side of the T reference point or coincident S and T reference point of
implementation conforming to EN 301 060-1 [6] in compliance with the relevant requirements and in accordance with the
relevant guidance given in ISO/IEC 9646.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] Void.
[2] Void.
[3] EN 300 195-2: "Integrated Services Digital Network (ISDN); Supplementary service interactions;
Digital Subscriber Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification".
[4] Void.
[5] ETS 300 196-2: "Integrated Services Digital Network (ISDN); Generic functional protocol for the
support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".
[6] EN 301 060-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry point for
Virtual Private Network (VPN) applications; Part 1: Protocol specification".
[7] Void.
[8] ISO/IEC 9646-1: "Information technology; Open systems interconnection; Conformance testing
methodology and framework; Part 1: General concepts".
[9] ISO/IEC 9646-7: "Information technology; Open systems interconnection; Conformance testing
methodology and framework; Part 7: Implementation Conformance Statements".
[10] ITU-T 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 I.411 (1993): "ISDN user-network interfaces; Reference configurations".
[12] Void.
[13] Void.
ETSI
7 ETSI EN 301 060-4 V1.1.4 (1999-08)
[14] Void.
[15] ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".
[16] EN 301 060-3 (V1.1): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling
System No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry point for
Virtual Private Network (VPN) applications; Part 3: Test Suite Structure and Test Purposes
(TSS&TP) specification for the user".
[17] ISO/IEC 9646-5: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[18] ISO/IEC 9646-4: "Information technology; Open Systems Interconnection; Conformance testing
methodology and framework; Part 4: Test realization".
[19] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[20] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[21] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN
and the means to describe them".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
3.1.1 Definitions related to conformance testing
abstract test case: refer to ISO/IEC 9646-1 [8]
Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [8]
active test: test case where the IUT is required to send a particular message, but not in reaction to a received message.
This would usually involve the use of PIXIT information to see how this message can be generated and quite often is
specified in an ATS using an implicit send event
Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [8]
implicit send event: refer to ISO/IEC 9646-3 [15]
lower tester: refer to ISO/IEC 9646-1 [8]
passive test: test case where the IUT is required to respond to a protocol event (e.g. received message) with another
protocol event (e.g. send message) which normally does not require any special operator intervention as associated with
the implicit send event
point of control and observation: refer to ISO/IEC 9646-1 [8]
Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [8]
PICS proforma: refer to ISO/IEC 9646-1 [8]
Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [8]
PIXIT proforma: refer to ISO/IEC 9646-1 [8]
system under test: refer to ISO/IEC 9646-1 [8]
ETSI
8 ETSI EN 301 060-4 V1.1.4 (1999-08)
Test Purpose (TP): refer to ISO/IEC 9646-1 [8]
3.1.2 Definitions related to EN 301 060-1
Dummy call reference: see ETS 300 403-1 [8], subclause 4.3
Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [20], definition 308
ISDN number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [19]
service; telecommunication service: see ITU-T Recommendation I.112 [20], definition 201
supplementary service: see ITU-T Recommendation I.210 [21], subclause 2.4
T: DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is a
Private ISDN)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BA Basic Access
CES Connection Endpoint Suffix
CM Co-ordination Message
ExTS Executable Test Suite
ISDN Integrated Services Digital Network
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PRA Primary Rate Access
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
VPN Virtual Private Network
ETSI
9 ETSI EN 301 060-4 V1.1.4 (1999-08)
4 Abstract Test Method (ATM)
The Remote test method is applied for the basic call user ATS. The Point of Control and Observation (PCO) resides at the
service access point between layers 2 and 3. This PCO is named "L" (for Lower). The L PCO is used to control and
observe the behaviour of the Implementation Under Test (IUT) and test case verdicts are assigned depending on the
behaviour observed at this PCO.
Tester SUT
LT IUT
PCO
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 1: Remote test method
5 Untestable test purposes
There are no untestable test purposes in this ATS.
6 ATS conventions
This clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses are arranged in
a way more suitable to the present document.
6.1 Declarations part
6.1.1 Type definitions
6.1.1.1 Simple type definitions
Where appropriate, simple types have a length, a value list or a range restriction attached.
Simple types defined as being of some string type (e.g. BIT STRING, OCTET STRING), have a length restriction or a
value list attached.
Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.
ETSI
10 ETSI EN 301 060-4 V1.1.4 (1999-08)
6.1.1.2 Structured type definitions
6.1.1.2.1 TTCN structured type definitions
All structured type definitions are provided with a full name.
All elements in every structured type definition, defined as being of some string type (e.g. BIT STRING,
OCTET STRING), have a length restriction attached.
If an element in a structured type definition is defined as being of a referenced type, the (possible) restriction is defined in
that referenced type.
For information elements the identifier, which is unique for each element, has its type defined as a simple type where the
value list is restricted to the single value which is the identifier itself. This has the advantage that it allows a test system
derived from this ATS to easily identify information elements embedded in messages. An ATS where information element
identifiers are represented as unrestricted types can present difficulties for a derived test system in the case where it
needs to find one information element embedded in a number of others and the constraints for the other elements have the
any-or-omit value. In such a case the test system cannot easily find the beginning of each information element.
6.1.1.2.2 ASN.1 structured type definitions
There are no ASN.1 structured type definitions in the ATS.
6.1.1.3 ASP type definitions
6.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all.
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used for requesting or
receiving service from the lower layer.
Table 1: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME : DL_REL_IN(DL_RELEASE_INDICATION)
: SAP
PCO Type
Comments :
Parameter Name           |   Parameter Type    |    Comments
Detailed Comments :
Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no other
parameters.
Table 2: TTCN ASP type definition DL_DATA_RQ
TTCN ASP Type Definition
ASP NAME : DL_DATA_RQ(DL_DATA_REQUEST)
: SAP
PCO Type
Comments :
Parameter Name           |   Parameter Type    |    Comments
mun (MessageUnit)         |PDU            |
:
Detailed Comments
6.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
ETSI
11 ETSI EN 301 060-4 V1.1.4 (1999-08)
6.1.1.4 PDU type definitions
6.1.1.4.1 TTCN PDU type definitions
The TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded in ASPs.
If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element has a restriction
attached to it.
6.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
6.1.2 Test suite constants
Each test suite constant is defined in terms of a predefined type or a referenced type. The values given in the value column
will remain unchanged throughout the test suite.
6.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type or a referenced type. A referenced type is used when it
is necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test suite
parameter table). The referenced type can have a length or value restriction attached to it in its declaration table.
6.1.4 Variables
6.1.4.1 Test suite variables
No Test Suite Variables are used or defined in this ATS.
6.1.4.2 Test case variables
Each test case variable is defined in terms of a predefined type or a referenced type. A referenced type is used when it is
necessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test case
variable table). The referenced type can have a length or value restriction attached to it in its declaration table.
Where test case variables are used in constraints, they are passed as formal parameters.
6.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 3: Test suite operation definition ASSIGN_CHI
Test Suite Operation Definition
: ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)
Operation Name
Result Type  : CHI
: This operation is used to assign a correct Channel identification
Comments
information
element to PDUs dependent on the type of access that is tested.
Description
CHI ASSIGN_CHI(basic,primary,basic_flag)
If the value of the basic_flag is set to TRUE, the result of the operation ASSIGN_CHI will be
the value represented by the parameter basic which is of type CHI. Else the operation results
in the value represented by the parameter primary.
Examples:
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, TRUE) = CHI1b_R1
ASSIGN_CHI(CHI1b_R1, CHI1p_R1, FALSE) = CHI1p_R1
:
Detailed comments
ETSI
12 ETSI EN 301 060-4 V1.1.4 (1999-08)
The test suite operation definition shown in table 3 is used in the constraints part when assigning an element of type CHI a
value. The CHI type can be defined in two ways depending on whether the ATS is testing basic or primary rate access. To
avoid duplicate types and thereby duplicate test cases this operation is used to assign a value to an element of CHI type. It
takes three parameters:
SULPDU\ DFRQVWUDLQWRIW\SH&+,YDOLGIRU3ULPDU\UDWHDFFHVV
EDVLF DFRQVWUDLQWRIW\SH&+,YDOLGIRU%DVLFDFFHVV
EDVLFBIODJ D%RROHDQYDOXH758(LIEDVLFDFFHVVLVDSSOLFDEOH)$/6(RWKHUZLVH
This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will then be
assigned to the specific element of type CHI.
6.2 Constraints part
6.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
6.2.2 ASN.1 type constraint declaration
There are no ASN.1 type constraint declarations in the ATS.
6.2.3 ASP type constraint declaration
6.2.3.1 ASN.1 ASP type constraint declaration
There are no ASN.1 ASP type constraint declarations in the ATS.
6.2.3.2 TTCN ASP type constraint declaration
The PDUs to be sent or received are passed to the TTCN ASP constraint declarations Ms and Mr as parameters of meta
type PDU. Only if values inside a specific PDU have to be referenced, the use of the meta type PDU is not allowed
according to ISO/IEC 9646-3 [15]. In such cases different TTCN ASP constraint declarations are used, that are defined to
carry only a specific type of PDU (e.g. SETUP). Table 4 shows an example of such a TTCN ASP constraint declaration.
Table 4: TTCN ASP constraint declaration Sr
TTCN ASP Constraint Declaration
Constraint Name : Sr(PARAM: SETUP_PDU)
: DL_DAT_IN_SETUP
ASP Type
Derivation Path :
: ASP to indicate the receipt of SETUP messages.
Comments
|       |
Parameter Name Parameter Value Comments
mun                |PARAM            |
Detailed Comments :
All ASP constraints have a specific value for its parameter. No matching symbols are used in ASPs.
6.2.4 PDU type constraint declaration
6.2.4.1 ASN.1 PDU type constraint declaration
There are no ASN.1 PDU type constraint declarations in the ATS.
6.2.4.2 TTCN PDU type constraint declaration
PDU constraints are used for assigning values or patterns to the data being sent or received.
ETSI
13 ETSI EN 301 060-4 V1.1.4 (1999-08)
6.2.4.3 Special coding
The information element transit counter, present in the SETUP PDU, shall be defined in codeset 4, for this purpose the
ATS is coding this IE with a locking shift (codeset 4) at the end of the PDU SETUP.
6.2.5 Derived constraints
Derived constraints are used in this ATS only for SETUP and ERROR PDUs.
6.2.6 Parameterized constraints
Parameterized constraints are used in this ATS.
6.2.7 Value assignment
6.2.7.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.
6.2.7.2 Matching values
As matching values the following mechanisms are used:
Instead of Value:
AnyOrOmit "*"
AnyValue "?"
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
6.3 Dynamic part
6.3.1 Test cases
Each test case contains the test purpose text from EN 301 060-3 [16]. To be able to read and understand the test case
dynamic behaviour it is recommended that the test steps are understood first.
6.3.2 Test steps
Much use has been made of test steps to avoid needless repetition of dynamic behaviour.
6.3.3 Defaults
Note the use of the RETURN statement which is defined in DAM1 of ISO/IEC 9646-3 [15]. This allows valid background
behaviour to be handled in the default tree with a possibility to return to the original set of alternatives in the test case.
7 ATS to TP map
The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.
ETSI
14 ETSI EN 301 060-4 V1.1.4 (1999-08)
8 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [17], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [17].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a client
to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A of the
present document.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
9 PIXIT conformance
A test realizer, producing an Executable Test Suite (ExTS) for the ATS specification contained in annex C, is required, as
specified in ISO/IEC 9646-4 [18], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT
proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum,
have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may contain additional
questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular IUT.
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [17], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma conformant
with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents which
are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be answered in
order to prepare the test laboratory for a particular IUT.
10 ATS conformance
The test realizer, producing MOT and ExTS for this ATS specification, shall comply with the requirements of
ISO/IEC 9646-4 [18]. In particular, these concern the realization of an ExTS based on each ATS. The test realizer shall
provide a statement of conformance of the MOT to this ATS specification.
An ExTS which conforms to this ATS specification shall contain test groups and test cases which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall be
capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each test
case.
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [17].
A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.
ETSI
15 ETSI EN 301 060-4 V1.1.4 (1999-08)
Annex A (normative):
Protocol Conformance Test Report (PCTR) proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of
the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its intended
purposes and may further publish the completed PCTR.
A.1 Identification summary
A.1.1 Protocol conformance test report
PCTR number:
PCTR date:
Corresponding SCTR number:
Corresponding SCTR date:
Test laboratory identification:
Test laboratory manager:
Signature:
A.1.2 IUT identification
Name:
Version:
Protocol specification: EN 301 060-1
PICS:
Previous PCTRs (if any):
A.1.3 Testing environment
PIXIT Reference number:
ATS Specification: EN 301 060-4
Abstract Test Method: Remote test method (see ISO/IEC 9646-2)
Means of Testing identification:
Dates of testing:
Conformance log reference(s):
Retention date for log reference(s):
A.1.4 Limits and reservations
Additional information relevant to the technical contents or further use of the test report, or to the rights and
obligations of the test laboratory and the client, may be given here. Such information may include restriction on the
publication of the report.
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
ETSI
16 ETSI EN 301 060-4 V1.1.4 (1999-08)
A.1.5 Comments
Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for
example, to note disagreement between the two parties.
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
A.2 IUT conformance status
This IUT has/has not been shown by conformance assessment to be non-conforming to the specified protocol
specification.
Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance
requirements (as specified in clause A.3 of this report) and there are no "FAIL" verdicts to be recorded (in clause A.6)
strike the word "has", otherwise strike the words "has not".
A.3 Static conformance summary
The PICS for this IUT is/is not consistent with the static conformance requirements in the specified protocol.
Strike the appropriate words in this sentence.
A.4 Dynamic conformance summary
The test campaign did/did not reveal errors in the IUT.
Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause A.6 of this
report) strike the word "did", otherwise strike the words "did not".
Summary of the results of groups of tests:
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
A.5 Static conformance review report
If clause A.3 indicates non-conformance, this clause itemizes the mismatches between the PICS and the static
conformance requirements of the specified protocol specification.
..........................................................................................................................................................................................
..........................................................................................................................................................................................
..........................................................................................................................................................................................
.........................................................................................................................................
...