SIST ETS 300 243-2 E1:2003

SLOVENSKI STANDARD
SIST ETS 300 243-2 E1:2003
01-december-2003
Terminalska oprema (TE) – Programirljivi komunikacijski vmesnik (PCI) –
APPLI/COM za faksimilno skupino 3, faksimilno skupino 4 ter storitve teletex in
telex – 2. del: Preskušanje skladnosti
Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLI/COM
for facsimile group 3, facsimile group 4, teletex and telex services; Part 2: Conformance
testing
Ta slovenski standard je istoveten z: ETS 300 243-2 Edition 1
ICS:
33.050.30 Oprema za teleks, teletekst, Equipment for telex, teletext,
telefaks telefax
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
SIST ETS 300 243-2 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 243-2 E1:2003

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

SIST ETS 300 243-2 E1:2003
EUROPEAN ETS 300 243-2
TELECOMMUNICATION November 1995
STANDARD
Source: ETSI TC-TE Reference: DE/TE-02015-2
ICS: 33.180, 33
PCI, APPLI/COM, conformance testing
Key words:
Terminal Equipment (TE);
Programmable Communication Interface (PCI) APPLI/COM for
facsimile group 3, facsimile group 4, teletex and telex services;
Part 2: Conformance testing
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: 3 ----------------------

SIST ETS 300 243-2 E1:2003
Page 2
ETS 300 243-2: November 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: 4 ----------------------

SIST ETS 300 243-2 E1:2003
Page 3
ETS 300 243-2: November 1995
Contents
Foreword .7
Introduction.7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 PCI testing model.11
4.1 Overview .11
4.2 PCI interfaces and ISO/IEC 9646 .11
4.3 Model .12
4.3.1 Lower LA PCO .13
4.3.2 Upper LA PCO .14
4.3.3 Upper CA PCO.14
4.3.4 Lower CA PCO.15
5 Testing procedure .15
5.1 PCI Implementation Conformance Statement (PICS) .16
5.2 PCI Implementation eXtra Information for Testing (PIXIT).16
5.3 ATS.16
5.3.1 Mapping of TTCN terms.17
5.3.2 Limits and constants.17
5.3.3 Testing of TDDs .17
5.3.4 Transfer Format testing.18
5.3.5 ICE testing.18
5.3.5.1 Reactions to the ICE (LA Test Suite).18
5.3.5.2 Connection test using ICE (LA Test Suite) .19
5.3.5.3 Features adaptation test using ICE (LA Test Suite) .19
5.4 Basic Interconnection Test (BIT) .19
5.5 Many LA to one CA relationship.19
5.6 Documentation requirements.20
5.6.1 CA documentation requirements.20
5.6.2 LA documentation requirements .20
6 CA Test Suite .21
6.1 Test Suite overview.21
6.1.1 Overview: Test Suite Structure (TSS) .21
6.1.2 Overview: Test Case Index .22
6.1.3 Overview: Test Step Index .24
6.1.4 Overview: default index .24
6.2 CA Test Suite: Declarations.25
6.2.1 Declaration: Test Components.25
6.2.2 Declaration: Test Component Configurations .25
6.2.3 Declaration: Points of Control and Observation (PCOs) .25
6.2.4 Declaration: Control Points (CPs) .26
6.2.5 Declaration: Timers .26
6.2.6 Declaration: Test Suite Parameter .27
6.2.7 Declaration: Test Suite Constants.28
6.2.8 Declaration: Test Suite Variables.29
6.2.9 Declaration: Test Case Variables.29
6.3 CA Test Suite: Type Definitions.29

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

SIST ETS 300 243-2 E1:2003
Page 4
ETS 300 243-2: November 1995
6.3.1 Type Definition: Simple Types . 29
6.3.1.1 Simple Types applying to TDDs. 30
6.3.1.2 Simple Types applying to Exchange Method . 32
6.3.1.3 Simple Types applying to Transfer Format. 32
6.3.1.4 Simple Types applying to ICE . 33
6.3.2 Type Definition: Abstract Service Primitives (ASPs). 33
6.3.3 Type Definition: Task Data Descriptions (TDDs). 35
6.3.4 Type Definition: Transfer Formats (TFs) . 44
6.3.5 Type Definition: ICE. 47
6.4 CA Test Suite: Constraint Declarations. 50
6.4.1 Constraint Declaration: ASPs . 51
6.4.2 Constraint Declaration: TDDs. 51
6.4.3 Constraint Declaration: TFs. 80
6.5 CA Test Suite: Dynamic Behaviour. 82
6.5.1 Dynamic Behaviour: Test Groups. 82
6.5.1.1 Test Group: CA/Send. 83
6.5.1.2 Test Group: CA/Receive . 93
6.5.1.3 Test Group: CA/Trace. 98
6.5.1.4 Test Group: CA/Submit. 108
6.5.2 Dynamic Behaviour: Test Steps . 109
6.5.3 Dynamic Behaviour: Test Defaults . 114
7 LA Test Suite . 114
7.1 LA Test Suite: Overview. 114
7.1.1 Overview: Test Suite Structure. 114
7.1.2 Overview: Test Case Index. 116
7.1.3 Overview: Test Step Index. 118
7.1.4 Overview: Default Index. 119
7.2 LA Test Suite: Declarations. 119
7.2.1 Declaration: Test Components . 119
7.2.2 Declaration: Test Component Configurations. 119
7.2.3 Declaration: Points of Control and Observation (PCOs) . 119
7.2.4 Declaration: Control Points (CPs). 119
7.2.5 Declaration: Timers . 120
7.2.6 Declaration: Test Suite Parameter . 120
7.3 LA Test Suite: Type Definitions. 120
7.4 LA Test Suite: Constraint Declarations . 120
7.4.1 Constraint Declaration: ASPs . 121
7.4.2 Constraint Declaration: TDDs. 121
7.4.3 Constraint Declarations: ICE . 140
7.5 LA Test Suite: Dynamic Behaviour. 143
7.5.1 Dynamic Behaviour: Test Groups. 143
7.5.1.1 Test Group: LA/ICE. 143
7.5.1.2 TestGroup: LA/Active/Send . 144
7.5.1.3 TestGroup: LA/Active/Receive. 151
7.5.1.4 Test Group: LA/Active/Trace. 152
7.5.1.5 Test Group: LA/Active/Submit. 159
7.5.1.6 Test Group: LA/Passive . 161
7.5.2 Dynamic Behaviour: Test Steps . 163
7.5.3 Dynamic Behaviour: Test Defaults . 165
Annex A (normative): PICS Proforma. 166
A.1 CA PICS Proforma . 166
A.1.1 Global requirements. 166
A.1.1.1 Functional classes . 166
A.1.1.2 TDD Types. 166
A.1.1.3 Support of many LAs . 166
A.1.2 ICE . 167
A.1.3 TDDs . 168
A.1.3.1 General . 168
A.1.3.1.1 Status of parameters in the TDD Requests . 169

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

SIST ETS 300 243-2 E1:2003
Page 5
ETS 300 243-2: November 1995
A.1.3.1.2 Status of parameters in the TDD Responses.169
A.1.3.2 List of predicates .169
A.1.3.3 Send TDD Keywords support (“sendack” variation, CA side) .170
A.1.3.4 Send TDD Keywords support (“send” variation, CA side).172
A.1.3.5 Receive TDD Keywords support (CA side) .173
A.1.3.6 Trace: Delete TDD Keywords support (CA side).174
A.1.3.7 Trace:Copy TDD Keywords support (CA side).174
A.1.3.8 Trace:Cancel TDD Keywords support (CA side).175
A.1.3.9 Trace:Purge TDD Keywords support (CA side) .175
A.1.3.10 Trace:Reschedule TDD Keywords support (CA side).176
A.1.3.11 Trace:Dispatch TDD Keywords support (CA side).176
A.1.3.12 Submit:Print TDD Keywords support (CA side).177
A.1.3.13 Submit:Convert TDD Keywords support (CA side) .177
A.1.3.14 Submit:Check TDD Keywords support (CA side).177
A.1.4 Exchange Method.178
A.1.4.1 Primitive-based Exchange Mechanism .178
A.1.4.1.1 Login.178
A.1.4.1.2 Logout.178
A.1.4.1.3 PutTDD.178
A.1.4.1.4 PollTDD .179
A.1.4.1.5 GetTDD .179
A.1.4.1.6 SetAlarm.179
A.1.4.1.7 CallBackRoutine .179
A.1.5 Transfer Formats .179
A.2 LA PICS Proforma.180
A.2.1 Global requirements .180
A.2.1.1 Functional classes.180
A.2.1.2 TDD Types .180
A.2.2 ICE.180
A.2.3 TDDs.181
A.2.3.1 General.181
A.2.3.1.1 Status of parameters in the TDD Requests.182
A.2.3.1.2 Status of parameters in the TDD Responses.182
A.2.3.2 List of predicates .182
A.2.3.3 Send TDD Keywords support (“sendack” variation, LA side).183
A.2.3.4 Send TDD Keywords support (“send” variation, LA side).184
A.2.3.5 Receive TDD Keywords support (LA side).186
A.2.3.6 Trace:Delete TDD Keywords support (LA side) .187
A.2.3.7 Trace:Copy TDD Keywords support (LA side) .187
A.2.3.8 Trace:Cancel TDD Keywords support (LA side) .188
A.2.3.9 Trace:Purge TDD Keywords support (LA side).188
A.2.3.10 Trace:Reschedule TDD Keywords support (LA side) .189
A.2.3.11 Trace:Dispatch TDD Keywords support (LA side) .189
A.2.3.12 Submit:Print TDD Keywords support (LA side) .190
A.2.3.13 Submit:Convert TDD Keywords support (LA side).190
A.2.3.14 Submit:Check TDD Keywords support (LA side) .190
A.2.4 Exchange Method.191
A.2.4.1 Primitive-based Exchange Mechanism .191
A.2.4.1.1 Login.191
A.2.4.1.2 Logout.191
A.2.4.1.3 PutTDD.191
A.2.4.1.4 PollTDD .191
A.2.4.1.5 GetTDD .192
A.2.4.1.6 SetAlarm.192
A.2.4.1.7 CallBackRoutine .192
Annex B (normative): PIXIT Proforma.193
B.1 PIXITs concerning the CA Test Suite.193
B.1.1 General Information .193
B.1.2 Procedural Information .193

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

SIST ETS 300 243-2 E1:2003
Page 6
ETS 300 243-2: November 1995
B.2 PIXITs concerning the LA Test Suite. 194
B.2.1 General Information . 194
B.2.2 Procedural information . 196
B.2.3 LA support of ICE features: Invocation of features . 197
B.2.4 LA Support of ICE Features: Confirmation of features support . 198
Annex C (normative): APPLI/COM Transfer Formats . 200
C.1 ASCII oriented Transfer Formats. 200
C.1.1 Control sequences . 200
C.1.2 Character Sets . 200
C.1.2.1 Character Set for facsimile service. 201
C.1.2.2 Character Set for Teletex Service . 202
C.1.2.3 Character Set for Telex service . 204
C.2 TIFF Transfer Format . 204
Annex D (informative): Bibliography . 205
History. 206

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

SIST ETS 300 243-2 E1:2003
Page 7
ETS 300 243-2: November 1995
Foreword
Part 2 of this European Telecommunication Standard (ETS) was produced by the Terminal Equipment
(TE) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS comprises two Parts:
"Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLI/COM for facsimile group
3, facsimile group 4, teletex and teletex services;
Part 1: CCITT Recommendation T.611 (1992) [modified];
Part 2: Conformance testing".
Transposition dates
Date of adoption of this ETS: 10 November 1995
Date of latest announcement of this ETS (doa): 29 February 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1996
Date of withdrawal of any conflicting National Standard (dow): 31 August 1996
Introduction
This second Part of ETS 300 243 describes the conformance testing of APPLI/COM Programmable
Communication Interfaces (PCIs). ETS 300 243-1 [1] endorses CCITT Recommendation T.611 [2], which
is known as APPLI/COM PCI. As described in CCITT Recommendation T.611 [2], an APPLI/COM PCI is
located within a TE between two entities, a Communication Application (CA) as service provider and a
Local Application (LA) as service user. The services provided by the CA and used by the LA are services
such as sending a document, receiving a document or tracing document transmissions. This second Part
of the ETS describes the testing of the conformance of both entities - CA and LA - with respect to the
interface behaviour.
The reason for providing this Part of the ETS was to give developers assistance in the testing of their
commercial products as well as to make test laboratories able to perform fair testing on different
APPLI/COM products that claim conformance to the APPLI/COM PCI standard. It is expected that CA
testing will be mainly performed by test laboratories, whereas LA testing is rather seen as assistance to
LA developers.
Since no former material exists on which the description of conformance testing of PCIs could rely, the
terminology and notation for describing the testing was deduced from ISO/IEC 9646, Parts 1 to 4 [3].
ISO/IEC 9646 [3] is a general framework for conformance testing of OSI layer protocols. However,
because a PCI is not a protocol, adaptation of certain terms and notations to the requirements of PCIs
were necessary. They are described at appropriate places in this ETS.
Besides the general clauses describing test methodology and adaptation of ISO/IEC 9646 [3], this ETS
contains two separate Abstract Test Suite (ATS) descriptions using (adapted) Tree and Tabular
Combined Notation (TTCN). Hence the testing of either component - CA or LA - can be set up and carried
out independently of each other. In both cases, this ETS tries to provide the shortest list of test cases
necessary to be confident in the conformance of the interface implementation under test. However,
passing the test suites does not guarantee good performance nor does it guarantee reliability in any
environment.

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

SIST ETS 300 243-2 E1:2003
Page 8
ETS 300 243-2: November 1995
Blank page

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

SIST ETS 300 243-2 E1:2003
Page 9
ETS 300 243-2: November 1995
1 Scope
Part 2 of this ETS describes the conformance testing of APPLI/COM Programmable Communication
Interfaces (PCIs) that claim conformance to ETS 300 243-1 [1], which in turn endorses CCITT
Recommendation T.611 [2], with certain ETSI modifications.
The aim of this Part of the ETS is to define conformance tests and methods which ensure, when applied,
that:
- a conforming implementation of a Local Application (LA) can work together with a conforming
implementation of a Communication Application (CA). The LA can coexist, access and communicate
with the CA from within the Terminal Equipment (TE) of the LA;
- a conforming implementation of a CA offers and carries out the functionality and features declared
and covered by one of the functional classes defined by CCITT Recommendation T.611 [2].
The intention of this Part of the ETS is to test one LA to one CA relation.
When many LAs are present within the same TE, many LAs to one CA relation, testing of the LAs need to
handle one LA at a time. To ensure conformance in the case of a many LA to one CA relationship, test
cases are provided exclusively for testing the CA conformance with respect to multiple LAs.
When many CAs are accessible from within the same TE, the testing of the CAs needs to be carried out
one CA at a time. No special test cases are provided for the case of multiple CAs in the same equipment.
2 Normative references
Part 2 of this ETS incorporates by dated and undated references, 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 Part of the 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 243-1 (1995): "Terminal Equipment (TE); Programmable
Communication Interface (PCI) APPLI/COM for facsimile group 3, facsimile
group 4, teletex and telex services; Part 1: CCITT Recommendation T.611
(1992) [modified]".
[2] CCITT Recommendation T.611 (1992): "Programmable Communication
Interface (PCI) APPLI/COM for facsimile group 3, facsimile group 4, teletex and
telex services".
[3] ISO/IEC 9646: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework
Part 1: General concepts;
Part 2: Abstract Test Suite specification;
Part 3: The Tree and Tabular Combined Notation (TTCN);
Part 4: Test realization".

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

SIST ETS 300 243-2 E1:2003
Page 10
ETS 300 243-2: November 1995
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this Part of the ETS, the following definitions apply along with those given in CCITT
Recommendation T.611 [2] and ISO/IEC 9646 [3].
Communication Application Emulator (CA Emulator): Lower Local Application (LA) Tester, emulating
a CA.
Local Emulation Application (LA Emulator): Upper CA Tester, emulating a LA.
LA User: Upper LA Tester; test entity using the LA under test.
Lower LA PCO: Point of Control and Observation (PCO) for LA testing, located "below" the LA towards
the CA Emulator.
Lower CA PCO: Point of Control and Observation (PCO) for CA testin
...