SIST I-ETS 300 491-1 E1:2003

• Abstract:

  Conformance testing specification for ETS 300 075 file transfer protocol. Establish: Protocol Implementation Conformance Statement proforma

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• ICS: 35.180 - IT Terminal and other peripheral equipment
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: T-301/2
• Ref Project: ETSI I-ETS 300 491-1 ed.1 (1996-09) - Terminal Equipment (TE); Conformance testing for file transfer over the Integrated Services Digital Network (ISDN); Part 1: ETS 300 075 Protocol Implementation Conformance Statement (PICS) proforma

SIST I-ETS 300 491-1 E1:2003 is the Slovenian adoption of ETSI I-ETS 300 491-1 Edition 1, published by SIST. It gives a Protocol Implementation Conformance Statement (PICS) proforma for conformance testing of file transfer over the Integrated Services Digital Network (ISDN) for ETS 300 075. In practice, it is used to record which protocol roles, services, PDUs, and parameter options a Terminal Equipment (TE) implementation supports.

What does SIST I-ETS 300 491-1 E1:2003 specify?

SIST I-ETS 300 491-1 E1:2003 specifies the PICS proforma for the Telesoftware Data Unit (TDU) layer protocol requirements of ETS 300 075, in line with ISO/IEC DIS 9646-7. It is a documentation tool for conformance evaluation: the supplier completes the proforma to state what the implementation supports and how it behaves.

The document is organized into four main clauses and one normative annex:

Part of the document	What it covers
Clauses 1-4	Scope, normative references, definitions and abbreviations, and the PICS conformance requirement
Annex A	The normative PICS proforma for ETS 300 075, including instructions, identification fields, conformance claims, static requirements, PDUs, and parameter tables

Annex A is the practical core of the document. It provides the questions and coding rules used to describe an implementation in a standard form.

What are the key requirements of SIST I-ETS 300 491-1 E1:2003?

SIST I-ETS 300 491-1 E1:2003 requires the supplier of a protocol implementation claimed to conform to ETS 300 075 to complete the PICS proforma in Annex A and identify both the supplier and the implementation. Clause 4 makes the PICS a required part of the conformance claim, so the document is not just descriptive - it is the formal statement used in evaluation.

Conformance claim and identification

Annex A begins with instructions and identification fields for the implementation, the system under test, the supplier, the client, and the ICS contact person. It also includes a global conformance statement asking whether the implementation meets all mandatory requirements of ETS 300 075. In practice, this gives test labs and purchasers a single place to see what is being claimed and who stands behind the claim.

Roles, classes, and regimes

The PICS asks the supplier to state support for implicit and explicit roles, service classes, and protocol regimes. The main regime entries are Association, Access, and Transfer, with Access and some service capabilities conditional on symmetrical service support. This matters because the protocol can be implemented in different operating profiles, and the PICS shows which profile applies.

Service elements and functional units

Annex A lists service elements such as T_ASSOCIATE, T_RELEASE, T_ACCESS, T_END_ACCESS, T_DIRECTORY, T_LOAD, T_SAVE, T_RENAME, T_DELETE, T_TYPED_DATA, T_WRITE, T_WRITE_END, T_U_EXCEPT, and T_P_EXCEPT. The implementation has to declare which of these are supported for the relevant roles. In practice, this tells an integrator whether the equipment can do only the basic file transfer functions or also more specialized operations and exception reporting.

PDU support

The annex breaks down support for Protocol Data Units (PDUs) by regime: association, access, transfer, mass transfer, and exception reporting. For each service, the proforma asks whether request, response, or indication PDUs are supported. This helps conformance testers check the protocol behavior at the message level instead of relying on broad functional claims.

Parameter values and coding rules

The proforma goes beyond yes/no support and asks for supported parameter values, lengths, defaults, and encodings. Examples include address strings, service class values, confirmation flags, transfer unit size, anticipation window, recovery settings, designation formats, recovery points, and reason codes for negative responses. For a reader, this is the part that shows how the implementation is configured and what parameter values must be handled correctly during testing.

Conditional rules and default values

Annex A uses standard notation such as mandatory, optional, conditional, prohibited, and not applicable, together with a support column. Some entries depend on whether symmetrical service is supported or whether Basic Transfer Mode is used. The annex also says that default values must be stated as supported even if they are not transmitted. In practice, this prevents gaps in the conformance statement and makes the implementation's behavior easier to test.

What terms does SIST I-ETS 300 491-1 E1:2003 define?

• Protocol Implementation Conformance Statement (PICS) - An ICS for an implementation or system that claims conformance to a given protocol specification.
• PICS proforma - An ICS proforma prepared for a protocol specification, used as the standard form to record support.
• Implementation Conformance Statement (ICS) - A structured statement of what an implementation supports against a specification.
• Implementation Under Test (IUT) - The implementation being assessed for conformance.
• System Under Test (SUT) - The overall system configuration in which the implementation is tested or described.
• Protocol Data Unit (PDU) - A protocol message unit used by the TDU layer to carry requests, responses, and indications.
• Telesoftware Data Unit (TDU) - The protocol layer named in the scope of this standard, where the ETS 300 075 requirements are addressed.

Who uses SIST I-ETS 300 491-1 E1:2003?

SIST I-ETS 300 491-1 E1:2003 is used by TE suppliers, protocol developers, conformance test laboratories, and quality teams that need a formal statement of protocol support for ETS 300 075. It is also useful to buyers and integrators who need to check whether an ISDN file transfer implementation supports the roles, services, and parameter ranges they require.

In practice, these users complete or review the PICS before testing, certification, or procurement. The document helps them compare implementations on the same basis.

What changed in SIST I-ETS 300 491-1 E1:2003 from the previous edition?

SIST I-ETS 300 491-1 E1:2003 is identical to I-ETS 300 491-1 Edition 1.

Which standards are used with SIST I-ETS 300 491-1 E1:2003?

• ETS 300 075 (1994) - The base file transfer specification whose TDU layer requirements are covered by the PICS.
• ISO/IEC 9646-1 (1994) - Provides the general concepts of conformance testing methodology and framework.
• ISO/IEC 9646-2 (1994) - Provides the abstract test suite specification framework and the status notation used in the proforma.
• ISO/IEC DIS 9646-7 (1993) - Provides the guidance for Implementation Conformance Statements and the tabular PICS structure.
• ITU-T Recommendation T.51 (1993) - Defines the coded character sets used for user data strings and optional text in several parameters.
• Part 2 of I-ETS 300 491 - Covers the Test Suite Structure and Test Purposes (TSS&TP).
• Part 3 of I-ETS 300 491 - Covers the Abstract Test Suite (ATS) for conformance testing of ETS 300 075 restricted by ETS 300 383.

What does the SIST I-ETS 300 491-1 E1:2003 document contain?

SIST I-ETS 300 491-1 E1:2003 contains a structured questionnaire in Annex A with numbered tables for roles, service classes, regimes, service elements, PDU support, and parameter values. It also includes the coding rules for the status and support columns, along with conditional expressions that control when an item is mandatory, optional, or not applicable.

The annex gives the exact fields needed to identify the implementation, the supplier, the system under test, and the overall conformance claim. It then lists the request, response, and indication forms for association, access, transfer, write, and exception services.

A major part of the document is the parameter coding detail: address lengths, designation syntax, confirmation flags, recovery points, transfer sizes, and reason codes for negative responses. These tables are used for conformance documentation, test planning, and checking that the implementation accepts the right protocol values.

SLOVENSKI STANDARD
01-december-2003
Terminalska oprema (TE) – Preskušanje skladnosti prenosa datotek prek
digitalnega omrežja z integriranimi storitvami (ISDN) – 1. del: ETS 300 075 Izjava o
skladnosti izvedbe protokola (PICS) - Proforma specifikacija
Terminal Equipment (TE); Conformance testing for file transfer over the Integrated
Services Digital Network (ISDN); Part 1: ETS 300 075 Protocol Implementation
Conformance Statement (PICS) proforma
Ta slovenski standard je istoveten z: I-ETS 300 491-1 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERIM
EUROPEAN I-ETS 300 491-1
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-TE Reference: DI/TE-01060-1
ICS: 33.080, 35.180
Key words: ISDN, file transfer
Terminal Equipment (TE);
Conformance testing for file transfer over
the Integrated Services Digital Network (ISDN);
Part 1: ETS 300 075 Protocol Implementation Conformance
Statement (PICS) proforma
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: [e-mail]
Tel.: [phone] - Fax: [phone]
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 1996. All rights reserved.

Page 2
I-ETS 300 491-1: September 1996
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
I-ETS 300 491-1: September 1996
Contents
Foreword .5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 Conformance requirement concerning PICS .8
Annex A (normative): PICS proforma for ETS 300 075 .9
A.1 Instructions for completing the PICS proforma .10
A.1.1 Purposes and structure.10
A.1.2 Symbols, abbreviations and conventions.10
A.1.2.1 Standardized symbols for the status column.11
A.1.2.2 Standardized symbols for the support column .11
A.1.2.3 The supported values column .11
A.1.3 Instructions for completing the PICS .11
A.2 Identification of the implementation.12
A.2.1 Date of statement .12
A.2.2 Implementation Under Test (IUT) identification .12
A.2.3 System Under Test (SUT) identification .12
A.2.4 Product supplier.12
A.2.5 Client.13
A.2.6 ICS contact person .13
A.3 ICS/System Conformance Statement (SCS) .14
A.4 Identification of the protocol .14
A.5 Global statement of conformance .14
A.6 Static requirements .14
A.6.1 Roles.14
A.6.2 Major capabilities .15
A.6.2.1 Service classes .15
A.6.2.2 Protocol classes - Regimes.15
A.6.2.3 Functional units .15
A.6.2.4 Service elements.16
A.6.3 Handling capabilities .16
A.6.4 Protocol Data Units (PDUs) .16
A.6.4.1 Association PDUs.17
A.6.4.1.1 Association PDUs/Association establishment .17
A.6.4.1.2 Association PDUs/Association release.17
A.6.4.1.3 Association PDUs/Association user abort .17
A.6.4.1.4 Association PDUs/Association provider abort .17
A.6.4.2 Access PDUs .17
A.6.4.2.1 Access PDUs/Access establishment.17
A.6.4.2.2 Access PDUs/Access end.18
A.6.4.3 Transfer PDUs .18

Page 4
I-ETS 300 491-1: September 1996
A.6.4.3.1 Transfer PDUs/File directory. 18
A.6.4.3.2 Transfer PDUs/Load . 18
A.6.4.3.3 Transfer PDUs/Save. 18
A.6.4.3.4 Transfer PDUs/Rename service . 18
A.6.4.3.5 Transfer PDUs/Delete service . 19
A.6.4.3.6 Transfer PDUs/Typed_Data service . 19
A.6.4.4 Mass transfer PDUs . 19
A.6.4.4.1 Mass transfer PDUs/Write service. 19
A.6.4.4.2 Exception report service . 19
A.6.5 PDU parameters . 20
A.6.5.1 Parameters of association PDUs. 21
A.6.5.1.1 Association establishment request parameters . 21
A.6.5.1.2 Association establishment response parameters . 22
A.6.5.1.3 Association release parameters. 23
A.6.5.1.4 Association abort parameters . 24
A.6.5.2 Parameters of access PDUs . 25
A.6.5.2.1 Access establishment request parameters. 25
A.6.5.2.2 Access establishment response parameters. 29
A.6.5.2.3 Access end request parameters . 30
A.6.5.2.4 Access end response parameters . 31
A.6.5.3 Parameters of transfer PDUs . 31
A.6.5.3.1 File directory parameters . 31
A.6.5.3.2 File load parameters . 33
A.6.5.3.3 File save parameters . 34
A.6.5.3.4 File rename parameters. 36
A.6.5.3.5 File delete parameters . 37
A.6.5.3.6 Typed data parameters. 38
A.6.5.3.7 Write parameters . 39
A.6.5.3.8 Write end parameters . 40
A.6.5.3.9 User exception parameters. 41
A.6.5.3.10 Provider exception parameters. 42
History. 43

Page 5
I-ETS 300 491-1: September 1996
Foreword
Part 1 of this Interim European Telecommunication Standard (I-ETS) has been produced by the Terminal
Equipment (TE) Technical Committee of the European Telecommunications Standards Institute (ETSI).
An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution ahead
of a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETS
is limited to three years after which it can be converted into an ETS, have its life extended for a further two
years, be replaced by a new version, or be withdrawn.
This is the first part of an I-ETS which comprises three parts as follows:
Terminal Equipment (TE); Conformance testing for file transfer over the Integrated Services Digital
Network (ISDN):
Part 1: ETS 300 075 Protocol Implementation Conformance Statement (PICS) proforma;
Part 2: ETS 300 075 Test Suite Structure and Test Purposes (TSS&TP);
Part 3: Conformance testing for ETS 300 075 restricted by ETS 300 383 - Abstract Test Suite (ATS).
Proposed announcement date
Date of adoption of this I-ETS: 30 August 1996
Date of latest announcement of this I-ETS (doa): 31 December 1996
Introduction
To evaluate the conformance of a particular implementation, a statement of which capabilities and options
have been implemented for a given specification is needed. Such a statement is called a Protocol
Implementation Conformance Statement (PICS).

Page 6
I-ETS 300 491-1: September 1996
Blank page
Page 7
I-ETS 300 491-1: September 1996
1 Scope
Part 1 of this Interim European Telecommunication Standard (I-ETS) provides a Protocol Implementation
Conformance Statement (PICS) proforma for the Telesoftware Data Unit (TDU) layer protocol
requirements of ETS 300 075 [1], in compliance with the relevant requirements, and in accordance with
the relevant guidance, given in ISO/IEC DIS 9646-7 [4].
2 Normative references
Part 1 of this I-ETS incorporates by dated or 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 part of the I-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 075 (1994): "Terminal Equipment (TE); Processable data, File
transfer".
[2] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts".
[3] ISO/IEC 9646-2 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 2:
Abstract Test Suite specification".
[4] ISO/IEC DIS 9646-7 (1993): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation Conformance Statements".
[5] ITU-T Recommendation T.51 (1993): "Coded character sets for telematic
services".
Page 8
I-ETS 300 491-1: September 1996
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this part of the I-ETS, the definitions in ETS 300 075 [1] and ISO/IEC DIS 9646-7 [4]
apply along with the following terms defined in ISO/IEC 9646-1 [2]:
Protocol Implementation Conformance Statement (PICS): An Implementation Conformance
Statement (ICS) for an implementation or system claimed to conform to a given protocol specification.
PICS proforma: An ICS proforma for a protocol specification.
3.2 Abbreviations
For the purposes of this I-ETS, the following abbreviations apply:
BK Basic Kernel
ICS Implementation Conformance Statement
ISDN Integrated Services Digital Network
IUT Implementation Under Test
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCS System Conformance Statement
Spt Support
SS or Sym. Service Symmetrical Service
Sts Status
SUT System Under Test
TDU Telesoftware Data Unit
TE Terminal Equipment
TTCN Tree and Tabular Combined Notation
4 Conformance requirement concerning PICS
The supplier of a protocol implementation which is claimed to conform to ETS 300 075 [1] shall complete
a copy of the PICS proforma provided in annex A and shall provide the information necessary to identify
both the supplier and the implementation.

Page 9
I-ETS 300 491-1: September 1996
Annex A (normative): PICS proforma for ETS 300 075
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.
The following table of contents refers to the location of the tables containing the indexed questions of
annex A.
Questions
A.1 Implicit roles.14
A.2 Explicit roles.15
A.3 Service classes.15
A.4 Regimes.15
A.5 Functional units : services.15
A.6 Service elements .16
A.7 Negotiation capabilities in symmetrical service.16
A.8 PDU/Association establishment.17
A.9 PDU/Association release .17
A.10 PDU/Association user abort.17
A.11 PDU/Association provider abort.17
A.12 PDU/Access establishment .17
A.13 PDU/Access end.18
A.14 PDU/Directory service.18
A.15 PDU/Load service.18
A.16 PDU/Save service.18
A.17 PDU/Rename service .18
A.18 PDU/Delete service.19
A.19 PDU/Typed data service.19
A.20 PDU/Write service .19
A.21 PDU/Write end service .19
A.22 PDU/User exception report service .19
A.23 PDU/Provider exception report service.19
A.24 Association establishment/request parameters.21
A.24.1 Application name parameter: values allowed.21
A.24.2 Service class parameter: values allowed .22
A.24.3 Identification parameter: values allowed .22
A.25 Association establishment/Response_pos parameters.22
A.26 Association establishment/Response_neg parameters.23
A.26.1 Reason parameter values for Response Negative .23
A.27 Association release/Request parameters.23
A.28 Association release/Response_pos parameters .24
A.29 Association abort/Request parameters.24
A.29.1 Reason parameter values for service provider .24
A.29.2 Reason parameter values for service user .25
A.30 Access establishment/Request parameters .25
A.30.1 Function parameter details/primitives handled.26
A.30.2 Function parameter details/primitives handled.27
A.30.3 Function parameter details/primitives handled.28
A.31 Access establishment/Response_pos parameters.29
A.32 Access establishment/Response_neg parameters .29
A.32.1 Reason parameter values for Response Negative .30
A.33 Access End/Request parameters .30
A.33.1 Reason parameter values for service user .30
A.34 Access End/Response_pos parameters .31
A.35 File directory/Request parameters.31
A.35.1 Directory designation elements parameter values .31
A.36 File directory/Response_pos parameters .32

Page 10
I-ETS 300 491-1: September 1996
A.37 File directory/Response_neg parameters . 32
A.37.1 Reason parameter values for Response Negative. 32
A.38 File load/Request parameters . 33
A.38.1 Load designation elements parameter values. 33
A.39 File load/Response_pos parameters . 33
A.40 File load/Response_neg parameters . 34
A.40.1 Reason parameter values for Response Negative. 34
A.41 File save/Request parameters . 34
A.42 File save/Response_pos parameters. 35
A.43 File save/Response_neg parameters . 35
A.43.1 Reason parameter values for Response Negative. 35
A.44 File rename/Request parameters. 36
A.45 File rename/Response_pos parameters. 36
A.46 File rename/Response_neg parameters. 36
A.46.1 Reason parameter values for Response Negative. 37
A.47 File delete/Request parameters . 37
A.48 File delete/Response_pos parameters . 37
A.49 File delete/Response_neg parameters . 38
A.49.1 Reason parameter values for Response Negative. 38
A.50 Typed_Data/Request parameters . 38
A.51 Write/Request parameters. 39
A.52 Write/Response_pos parameters . 39
A.52.1 Write/Response_pos block number parameter values. 39
A.53 Write/Response_neg parameters . 40
A.54 Write End/ Request parameters. 40
A.55 Write End/Response_pos parameters. 40
A.56 Write End/Response_neg parameters. 41
A.56.1 Write End response negative result parameter values. 41
A.56.2 Reason values for Response Negative . 41
A.57 User Exception/Request parameters . 41
A.58 Provider Exception/Request parameters . 42
A.58.1 Reason parameter values for service provider. 42
A.1 Instructions for completing the PICS proforma
A.1.1 Purposes and structure
The purpose of this PICS is to provide a mechanism whereby a supplier of an implementation of the
requirements of ETS 300 075 [1] may provide information in a standard form.
The PICS proforma is subdivided into clauses for the following categories of information:
- implementation details;
- protocol details;
- overall conformance claim;
- static requirements:
1) roles;
2) major capabilities;
3) negotiation capabilities;
4) Protocol Data Units (PDU);
5) Protocol Data Units parameters.
- timer;
- supplementary services;
- dynamic requirements.
A.1.2 Symbols, abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in a tabular form in accordance
with the guidelines presented in ISO/IEC DIS 9646-7 [4].
References within tables are to ETS 300 075 [1], except where explicitly stated.

Page 11
I-ETS 300 491-1: September 1996
A.1.2.1 Standardized symbols for the status column
The following notations, defined in ISO/IEC 9646-2 [3] are used in the proforma to indicate the status of a
question:
- m (mandatory): the capability shall be implemented, in conformance with the protocol standard;
- o (optional): the capability may be implemented, and if it is implemented it shall conform to
the protocol specification (cf. ISO/IEC 9646-1 [2], clause A.3);
- o.n (optional): the capability may be implemented, and if it is implemented it shall conform to
the protocol specification, and the option is mutually exclusive or selectable
among a set (cf. ISO/IEC 9646-1 [2], clause A.3);
- x (prohibited): there is a requirement not to use this capability in a given context;
- c (conditional): the requirement on the capability depends on the selection of other optional or
conditional items;
- n/a (not applicable): in the given context the base specification makes it impossible to use this
capability.
If appropriate, a "c" followed by an integer is placed in the status column, providing a reference to a
conditional status expression defined as a note inside the table. As defined in ISO/IEC DIS 9646-7 [4], this
predicate expression is consistent with Tree and Tabular Combined Notation (TTCN) boolean expressions
(i.e. IF . THEN (IF . THEN . ELSE) ELSE .). In all cases, "ELSE n/a" is implied if an ELSE clause is
omitted.
A.1.2.2 Standardized symbols for the support column
To specify the level of support for all entries, the standardized symbols for the support column shall be as
follows:
- y (supported): the capability is implemented in conformance with the ETS;
- n (not supported): the capability is not implemented;
- n/a (no answer required): the question has a status value of either not applicable or out of scope.
A.1.2.3 The supported values column
A "supported" values column, if appropriate, in which the values or ranges of values supported can be
indicated, as well as type and length, if relevant.
A.1.3 Instructions for completing the PICS
The supplier of the implementation shall enter an explicit statement in each of the boxes provided, using
the notation described in subclause A.1.2. A specific instruction is provided in the text which precedes
each table.
Page 12
I-ETS 300 491-1: September 1996
A.2 Identification of the implementation
A.2.1 Date of statement
........................................................................................................................................................................
A.2.2 Implementation Under Test (IUT) identification
IUT name:
........................................................................................................................................................................
........................................................................................................................................................................
IUT version:
........................................................................................................................................................................
A.2.3 System Under Test (SUT) identification
SUT name:
........................................................................................................................................................................
........................................................................................................................................................................
Hardware configuration:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Operating system:
........................................................................................................................................................................
A.2.4 Product supplier
Name:
........................................................................................................................................................................
Address:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
Telephone number:
........................................................................................................................................................................
Facsimile number:
........................................................................................................................................................................

Page 13
I-ETS 300 491-1: September 1996
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.5 Client
Name:
.........................................................................................................................................................................
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.6 ICS contact person
Name:
.........................................................................................................................................................................
Telephone number:
.........................................................................................................................................................................
Facsimile number:
.........................................................................................................................................................................
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
.........................................................................................................................................................................

Page 14
I-ETS 300 491-1: September 1996
A.3 ICS/System Conformance Statement (SCS)
Provide the relationship of the ICS with the SCS for the system:
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
........................................................................................................................................................................
A.4 Identification of the protocol
This PICS proforma applies to the following standard:
- Title of specification: Terminal Equipment (TE); Processable data, File transfer;
- Reference no.: ETS 300 075 [1], 2nd Edition;
- Date of publication: February 1994.
A.5 Global statement of conformance
The implementation described in this PICS meets all the mandatory requirements of ETS 300 075 [1].
[ ] Yes
[ ] No
NOTE: Answering "No" to this question indicates non-conformance to the protocol
specification. Identify non-supported mandatory capabilities in the ICS, with an
explanation of why the implementation is non-conforming.
A.6 Static requirements
A.6.1 Roles
The supplier of the implementation shall state the support of the roles of the implementation, in the boxes
below.
The support of the implicit role in the table below corresponds to the role assigned at the association
regime establishment.
Table A.1: Implicit roles
Item No. Role Ref. Status Support
1 Master 4.1.2.2.3 o.1
2 Slave 4.1.2.2.3 o.1
o.1 it is mandatory to support at least one of these options.
The support of the explicit role in the table below corresponds to the role assigned for the access regime
or the transfer regime.
Page 15
I-ETS 300 491-1: September 1996
Table A.2: Explicit roles
Item No. Role Ref. Status Support
1 Master 4.1.2.2.3 o.2
Slave 4.1.2.2.3 o.2
3 Sender 4.1.2.2.3 o.3
4 Receiver 4.1.2.2.3 o.3
o.2 it is mandatory to support at least one of these options.
o.3 it is mandatory to support at least one of these options.
A.6.2 Major capabilities
A.6.2.1 Service classes
The supplier of the implementation shall state the support of the service(s) class(es) of the
implementation, in the box below.
Table A.3: Service classes
Item No. Service class Ref. Status Support
1 Basic kernel 4.1.3.1.2.1 o.4
Symmetrical service 4.1.3.1.2.1 o.4
o.4 it is mandatory to support at least one of the two service classes.
A.6.2.2 Protocol classes - Regimes
The supplier of the implementation shall state the support of the regimes of the implementation, in the
table A.4.
Table A.4: Regimes
Item No. Regime Ref. Status Support
Association 4.1.2.3.2 m
2 Access 4.1.2.3.3 c1
3 Transfer 4.1.2.3.4 m
c1 IF A.3/2 THEN m ELSE n/a.
A.6.2.3 Functional units
The supplier of the implementation shall state the support of the functional units of the implementation, in
the box below.
Table A.5: Functional units: services
Item No. Service Ref. Status Support
1 File directory service 4.1.4.3 c2
Load service 4.1.4.4 c2
3 Save service 4.1.4.5 c2
Rename service 4.1.4.6 c2
5 Delete service 4.1.4.7 c2
6 Typed Data service 4.1.4.8 c2
Mass transfer service 4.1.5.1 m
8 Exception report service 4.1.5.2 m
c2 IF A.3/2 THEN o ELSE n/a.
Page 16
I-ETS 300 491-1: September 1996
A.6.2.4 Service elements
The supplier of the implementation shall state the support of the service elements of the implementation,
in table A.6.
Table A.6: Service elements
Item No. Service Ref. Role: Master Role: Slave
Sts Spt Sts Spt
1 T_ASSOCIATE 4.1.2.3.1 m m
2 T_RELEASE 4.1.2.3.1 m m
T_U_ABORT 4.1.2.3.1 c3 m
4 T_P_ABORT 4.1.2.3.1 c3 c3
T_ACCESS 4.1.2.3.1 c3 c3
6 T_END_ACCESS 4.1.2.3.1 c3 c3
7 T_DIRECTORY 4.1.2.3.1 c4 c4
T_LOAD 4.1.2.3.1 c4 c4
9 T_SAVE 4.1.2.3.1 c4 c4
T_RENAME 4.1.2.3.1 c5 c5
11 T_DELETE 4.1.2.3.1 c5 c5
12 T_TYPED_DATA 4.1.2.3.1 c5 c5
T_WRITE 4.1.2.3.1 m m
14 T_WRITE_END 4.1.2.3.1 m m
T_U_EXCEPT 4.1.2.3.1 c3 m
16 T_P_EXCEPT 4.1.2.3.1 c5 c5
c3 IF A.3/2 THEN m ELSE n/a.
c4 IF Basic Transfer Mode used THEN n/a ELSE c5.
c5 IF A.3/2 THEN o ELSE n/a.
A.6.3 Handling capabilities
The supplier of the implementation shall provide information to describe the negotiation options available
in the protocol, and indicate which have been implemented, in the box below.
Those negotiation capabilities are only available in symmetrical service. The use of these services is
negotiated during the Access regime establishment.
Table A.7: Capabilities in symmetrical service
Item No. Service handled Ref. Role: Master Role: Slave
Sts Spt Sts Spt
File directory service 4.1.4.1.2.2 n/a c6
2 Load service 4.1.4.1.2.2 n/a c6
Save service 4.1.4.1.2.2 n/a c6
4 Rename service 4.1.4.1.2.2 n/a o
5 Delete service 4.1.4.1.2.2 n/a o
Typed Data service 4.1.4.1.2.2 o o
7 Exception report 4.1.4.1.2.2 o o
Basic Transfer Mode 4.1.4.1.2.6 o o
c6 IF Basic Transfer Mode is used THEN n/a ELSE o.
A.6.4 Protocol Data Units (PDUs)
This subclause lists all the PDUs defined for the ETS 300 075 [1] protocol, grouped according to regime
control. It concerns only the TDU layer, i.e. the PDUs of the T_Protocol.

Page 17
I-ETS 300 491-1: September 1996
A.6.4.1 Association PDUs
The supplier of the implementation shall state the support of association PDUs of the implementation in
the boxes below.
A.6.4.1.1 Association PDUs/Association establishment
Table A.8: PDU/Association establishment
Item No. PDU type Ref Status Support
T_ASSOCIATE Request 4.1.3.1.1 m
2 T_ASSOCIATE Response 4.1.3.1.1 c7
c7 IF A.3/2 THEN m ELSE o.
A.6.4.1.2 Association PDUs/Association release
Table A.9: PDU/Association release
Item No. PDU type Ref Status Support
1 T_RELEASE Request 4.1.3.2.1 m
T_RELEASE Response 4.1.3.2.1 m
A.6.4.1.3 Association PDUs/Association user abort
Table A.10: PDU/Association user abort
Item No. PDU type Ref Status Support
T_U_ABORT Request 4.1.3.3.1 c8
c8 IF A.6/3 THEN m ELSE n/a.
A.6.4.1.4 Association PDUs/Association provider abort
Table A.11: PDU/Association provider abort
Item No. PDU type Ref. Status Support
1 T_P_ABORT Indication 4.1.3.3.1 c9
c9 IF A.6/4 THEN m ELSE n/a.
A.6.4.2 Access PDUs
The supplier of the implementation shall state the support of access PDUs of the implementation in the
boxes below.
A.6.4.2.1 Access PDUs/Access establishment
Table A.12: PDU/Access establishment
Item No. PDU type Ref. Status Support
T_ACCESS Request 4.1.4.1.1 c10
2 T_ACCESS Response 4.1.4.1.1 c10
c10 IF A.6/5 THEN m ELSE n/a.
Page 18
I-ETS 300 491-1: September 1996
A.6.4.2.2 Access PDUs/Access end
Table A.13: PDU/Access end
Item No. PDU type Ref. Status Support
1 T_END_ACCESS Request 4.1.4.2.1 c11
T_END_ACCESS Response 4.1.4.2.1 c11
c11 IF A.6/6 THEN m ELSE n/a.
A.6.4.3 Transfer PDUs
The supplier of the implementation shall state the support of transfer PDUs of the implementation in the
boxes below.
A.6.4.3.1 Transfer PDUs/File directory
Table A.14: PDU/Directory service
Item No. PDU type Ref. Status Support
1 T_DIRECTORY Request 4.1.4.3.1 c12
T_DIRECTORY Response 4.1.4.3.1 c12
c12 IF A.6/7 THEN m ELSE n/a.
A.6.4.3.2 Transfer PDUs/Load
Table A.15: PDU/Load service
Item No. PDU type Ref. Status Support
T_LOAD Request 4.1.4.4.1 c13
2 T_LOAD Response 4.1.4.4.1 c13
c13 IF A.6/8 THEN m ELSE n/a.
A.6.4.3.3 Transfer PDUs/Save
Table A.16: PDU/Save service
Item No. PDU type Ref. Status Support
T_SAVE Request 4.1.4.5.1 c14
2 T_SAVE Response 4.1.4.5.1 c14
c14 IF A.6/9 THEN m ELSE n/a.
A.6.4.3.4 Transfer PDUs/Rename service
Table A.17: PDU/Rename service
Item No. PDU type Ref. Status Support
1 T_RENAME Request 4.1.4.6.1 c15
2 T_RENAME Response 4.1.4.6.1 c15
c15 IF A.6/10 THEN m ELSE n/a.

Page 19
I-ETS 300 491-1: September 1996
A.6.4.3.5 Transfer PDUs/Delete service
Table A.18: PDU/Delete service
Item No. PDU type Ref. Status Support
1 T_DELETE Request 4.1.4.7.1 c16
T_DELETE Response 4.1.4.7.1 c16
c16 IF A.6/11 THEN m ELSE n/a.
A.6.4.3.6 Transfer PDUs/Typed_Data service
Table A.19: PDU/Typed Data service
Item No. PDU type Ref. Status Support
T_TYPED_DATA Request 4.1.4.8.1 c17
c17 IF A.6/12 THEN m ELSE n/a.
A.6.4.4 Mass transfer PDUs
The supplier of the implementation shall state the support of mass transfer PDUs of the implementation in
the boxe
...