SIST ETS 300 015 E1:2003
(Main)Terminal Equipment (TE); Basic and recommended additional requirements for terminal equipment supporting Teletex application
Terminal Equipment (TE); Basic and recommended additional requirements for terminal equipment supporting Teletex application
This ETS distinguishes between basic equipment and equipment with recommended additional requirements for advanced features of service
Terminalska oprema (TE) – Osnovne in priporočene dodatne zahteve za terminalsko opremo, ki podpira uporabo sistema Teletex
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
7HUPLQDOVNDRSUHPD 7( ±2VQRYQHLQSULSRURþHQHGRGDWQH]DKWHYH]D
WHUPLQDOVNRRSUHPRNLSRGSLUDXSRUDERVLVWHPD7HOHWH[
Terminal Equipment (TE); Basic and recommended additional requirements for terminal
equipment supporting Teletex application
Ta slovenski standard je istoveten z: ETS 300 015 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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 015
TELECOMMUNICATION February 1994
STANDARD
Source: ETSI TC-TE Reference: T/TE 07-01
ICS: 33.020, 33.040.40
Teletex
Key words:
Terminal Equipment (TE);
Basic and recommended additional
requirements for terminal equipment
supporting Teletex application
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 1994. All rights reserved.
New presentation - see History box
Page 2
ETS 300 015: February 1994
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 015: February 1994
Contents
Foreword.7
1 Scope .9
2 Normative references .9
3 Definitions. 11
4 Abbreviations. 11
5 Scenario description. 11
6 Conformity. 11
7 Layer description. 11
7.1 Network dependent layers (1-4). 11
7.1.1 Access from telephone network(s). 11
7.1.2 Access from packet switched network(s). 11
7.1.3 Access from circuit switched network(s) . 12
7.1.4 Access from integrated services digital network(s). 12
7.2 Network independent layers (5-7). 12
7.2.1 Session layer description . 12
7.2.2 Presentation layer description . 12
7.2.3 Application layer description. 12
8 Test specifications. 12
8.1 Test suites for protocols with end-to-end significance. 12
8.2 Test suites without end-to-end significance. 12
8.3 Test suites for system related requirements. 12
9 Additional session layer requirements (to ITU-T Recommendation T.62). 13
9.1 ETSI agreed additional requirements to ITU-T Recommendation T.62. 13
9.1.1 Paragraph 3.4.1.2a/T.62. 13
9.1.2 Paragraph 3.4.4.3/T.62 . 13
9.1.3 Paragraph 3.4.5.1/T.62 . 13
9.1.4 Paragraph 3.4.12/T.62 . 13
9.1.5 Paragraph 3.2.3.2/T.62 . 13
9.1.6 Paragraph 3.2.10/T.62 . 13
9.1.7 Paragraph 3.3.1.1.c/T.62. 13
9.1.8 Paragraph 3.3.2.6/T.62 . 13
9.1.9 Paragraph 3.3.2.7.b/T.62. 13
9.1.10 Paragraph 3.3.2.10/T.62. 14
9.1.11 Paragraph 3.4.3/T.62 . 14
9.1.12 Paragraph 3.4.3.2.e/T.62. 14
9.1.13 Paragraph 3.4.4.4/T.62 . 14
9.1.14 Paragraph 3.5.3/T.62 . 14
9.1.15 Paragraph 4.1.4/T.62 . 14
9.1.16 Annex J, paragraph 2.1.1.c/T.62 . 14
9.2 Use of the session protocol for interworking with automatic Teletex directory service . 14
9.3 Types of document. 14
10 ETSI agreed additional service and terminal requirements (modifications to ITU-T
Recommendation T.60). 14
10.1 Paragraph 4.1.1.1/T.60 . 15
Page 4
ETS 300 015: February 1994
10.2 Paragraph 4.1.3/T.60 .15
10.3 Paragraph 8.2.1/T.60 .15
10.4 Paragraph 4.1.4/T.60 .15
10.5 Paragraph 5.1.3/T.60 .15
10.6 Paragraph 7.2.3/T.60 .16
10.7 Paragraph 4.1.3.3/T.60 .16
10.8 Paragraph 4.1.3/T.60 .16
10.9 Paragraph 5.2/T.60 .16
10.10 Paragraph 6/T.60.16
10.11 Paragraph 7/T.60.17
10.12 Paragraph 7.2.2/T.60 .17
10.13 Paragraph 4.1.3/T.60 .18
10.14 Paragraph 5.2/T.60 .18
10.15 Paragraph 4.1.2.4/T.60 .19
11 Additional requirements for Teletex systems participating in the Teletex service .20
11.1 Description of a Teletex system.20
11.2 Types of Teletex systems .20
11.2.1 Teletex system with automatic access .20
11.2.1.1 Teletex system with switched access .20
11.2.1.2 Teletex system with memory based access .20
11.2.1.3 Teletex system with switched and memory based access. 20
11.2.2 Teletex system without automatic access.20
11.2.3 Supplementary Teletex system equipment.20
11.3 Types of terminals for Teletex system.20
11.3.1 Independent Teletex terminal.20
11.3.2 Other terminals for the Teletex service.21
11.3.3 Other equipment.21
11.4 Specification of a Teletex system .21
11.4.1 Quality of service. 21
11.4.2 System's Terminal Identifier (TID). 21
11.4.3 Communication-log . 21
11.4.4 Requirements for equipment to connect.21
11.4.4.1 Independent Teletex terminals .21
11.4.4.2 Text terminals for the Teletex service . 22
11.4.4.3 Other terminals for the Teletex service . 22
11.4.4.4 Other equipment.22
11.4.5 Teletex communications .22
11.4.5.1 Incoming traffic. 22
11.4.5.2 Outgoing traffic. 22
11.4.5.3 Traffic restrictions.23
11.4.6 Test specifications. 23
12 Date and time provisions.23
13 Local despatching at the receiving side .23
Annex A (normative): Use of the session protocol for interworking with the automatic Teletex
directory service .24
Introduction .24
A.1 General .24
A.2 Request for information.24
A.3 Example diagram for the sequence of events of a request for information carried out within the
scope of the Teletex protocol .25
A.4 Format specification .26
Page 5
ETS 300 015: February 1994
A.4.1 Subscriber request. 26
A.4.2 General request. 26
Annex B (normative): Types of documents. 27
B.1 Types of documents. 27
B.1.1 Annex F.2/T.62, Normal document. 27
B.1.2 Annex F.3/T.62, Operator document. 27
B.1.3 Annex F.5/T.62, Monitor document . 27
B.2 Advisory notes and additional information . 27
B.2.1 Paragraph 4.2.10/T.62 . 27
B.2.2 Paragraph 3.2.1.2/T.62 . 27
B.2.3 Paragraph 3.2.8 and 3.2.9/T.62 . 27
B.2.4 Paragraph 3.4.11.2/T.62 . 28
B.2.5 Paragraph 4.1.4/T.62. 28
Annex C (informative): Advisory notes and additional information concerning the presentation of
graphic characters . 29
C.1 Introduction. 29
C.2 Fall-back procedures (ISO 6937/2, Annex E, Clause E.1). 29
C.3 Fall-back presentation of accented letters (ISO 6937/1, Annex E, Clause E.2). 30
C.4 Examples of fall-back presentations of non-alphabetic characters (ISO 6937/1, Annex E, Clause
E.3). 30
Annex D (normative): Date and time provisions . 31
Annex E (normative): Local dispatching at the receiving side (sub-addressing at the application
layer). 32
Introduction . 32
E.1 Local dispatching needs. 32
E.2 Mechanism used . 32
E.2.1 Description . 32
E.2.2 Connection interrupt . 32
E.3 Coding and format of the normal or control document. 33
Annex F (informative): Bibliography. 34
History. 35
Page 6
ETS 300 015: February 1994
Blank page
Page 7
ETS 300 015: February 1994
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terminal Equipment (TE)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS defines the basic and recommended additional minimum requirements for terminal equipment
participating in the Teletex service. The terminal described herein offers users the ability to prepare
character coded text messages together with a means of conveying the true contents of such messages to
a distant terminal equipment complying with the same specifications.
Teletex systems such as cluster, Private Automatic Branch Exchanges (PABX), etc., may need additional
requirements. These can be found in Clause 10 of this ETS.
This ETS provides a description of the basic Teletex equipment for use in the international Teletex service.
For optional features the following ETSs apply:
- ETS 300 154: "Terminal Equipment (TE); Terminal characteristics for the telematic file transfer
within the teletex service [ITU-T Recommendation T.571 (1993) modified]" [13].
- prETS 300 243-1 (1993): "Terminal Equipment (TE); Programming Communication Interface (PCI)
Appli/Com for Facsimile group 3, Facsimile group 4, Teletex and Telex services [ITU-T
Recommendation T.611 (1992) modified]" [14].
- prETS 300 243-2 (1993): "Terminal Equipment (TE); Application of ITU-T Recommendation T.611
(1992) and conformance testing on ETS 300 243-1" [22].
Page 8
ETS 300 015: February 1994
Blank page
Page 9
ETS 300 015: February 1994
1 Scope
This ETS describes the specification to be used for basic Teletex terminal equipment for use in the
international Teletex service.
This ETS is based on the relevant CCITT and ITU-T Recommendations. In order to provide guidance,
modifications and/or additions are also contained and identified where necessary.
NOTE: Throughout this ETS the term "Administration" should be taken to read as either
"Administration" or "Recognised Private Operating Agency".
2 Normative references
This 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 ETS
only when incorporated in it by amendment or revision. For undated references the latest edition of the
publication referred to applies.
[1] ITU-T Recommendation T.60: "Terminal equipment for use in the teletex
service".
[2] ITU-T Recommendation T.61: "Character repertoire and coded character sets
for the international teletex service".
[3] ITU-T Recommendation T.62: "Control procedures for teletex and Group 4
facsimile services".
[4] ITU-T Recommendation T.63: "Provisions for verification of teletex terminal
compliance".
[5] ITU-T Recommendation T.64: "Conformance Testing Procedures for the Teletex
Recommendations".
[6] ITU-T Recommendation T.70: "Network independent basic transport service for
the telematic services".
[7] CCITT Recommendation T.90 (1992): "Characteristics and protocols for
terminals for telematic services in ISDN".
[8] CCITT Recommendation T.390 (1988): "Teletex requirements for interworking
with the telex service".
[9] CCITT Recommendation F.200 (1992): "Teletex service".
[10] ITU-T Recommendation F.201: "Interworking between teletex service and telex
service - General principles".
[11] ETS 300 081 (1993): "Integrated Services Digital Network (ISDN); Teletex end-
to-end protocol over the ISDN".
[12] ETS 300 017: "Terminal Equipment (TE); Test procedures for Teletex".
[13] ETS 300 154: "Terminal Equipment (TE); Terminal characteristics for the
telematic file transfer within the teletex service [ITU-T Recommendation T.571
(1993) (modified)]".
[14] prETS 300 243-1: "Terminal Equipment (TE); Programming Communication
Interface (PCI) Appli/Com for Facsimile group 3, Facsimile group 4, Teletex and
Telex services [CCITT Recommendation T.611 (1992) modified]".
Page 10
ETS 300 015: February 1994
[15] ENV 41104: "Packet-switched data network; permanent access (FS T/31)".
[16] ENV 41106: "Digital data circuit (circuit switched data networks); provision of the
OSI connection-mode transport service in the T.70 case for telematic end
systems (FS T/41)".
[17] ENV 41105: "Packet-switched data network; switched access (FS T/32)".
[18] NET 1: "Approval requirements for data terminal equipment to connect to CSPN
and leased circuits using CCITT Recommendation X.21 interface".
[19] NET 2 (1988): "Approval requirements for Data Terminal Equipment (DTE) to
connect to Packet Switched Public Data Network (PSPDN) using CCITT
Recommendation X.25 (1984) interface".
[20] ETS 300 001 (1992): "Attachments to Public Switched Telephone Network
(PSTN); General technical requirements for equipment connected to an analogue
subscriber interface in the PSTN (candidate NET 4)".
[21] ETS 300 080 (1992): "Integrated Services Digital Network (ISDN); ISDN lower
layer protocols for telematic terminals".
[22] prETS 300 243-2: "Terminal Equipment (TE); Application of CCITT
Recommendation T.611 (1992) and conformance testing on ETS 300 243-1".
An overview on the relation of standards to each other is given in figures 1 and 2 as follows.
Layers Teletex Terminal Specification
�˜˜˜˜˜˜˜¿ �˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ 7 ‡ ‡ ‡
ˆ˜˜˜˜˜˜˜· ‡ ‡
‡ 6 ‡ ‡ ETS 300 015 ‡
ˆ˜˜˜˜˜˜˜· ‡ ETR 052 (NOTE 2) ‡
‡ 5 ‡ ‡ ‡
ˆ˜˜˜˜˜˜˜· ‡ �˜˜¿ �˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ 4 ‡ ‡ ‡ ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜· ‡ ‡ ‡ ‡
ˆ˜˜˜˜˜˜˜· ‡ ‡ ‡ ‡ ‡ETS 300 080 ‡ ‡ ETS 300 001 ‡
‡ 3 ‡ ‡ ‡ ‡ ‡ ‡[21] (NOTE 4) ‡ ‡ [20] (NOTE 3)‡
ˆ˜˜˜˜˜˜˜· ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
‡ 2 ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
ˆ˜˜˜˜˜˜˜· ˆ˜˜˜˜˜˜˜˜˜˜˜´˜˜· ‡ �˜˜· ‡ �˜˜˜· ˆ˜˜˜˜˜˜˜˜˜˜˜´˜˜·
‡ 1 ‡ ‡NET 1 [18]‡1)‡ ‡NET 2 [19] ‡1)‡ ‡ ‡ 1)‡ ‡ NET 4 ‡1)‡
�˜˜˜˜˜˜˜� �˜˜˜˜˜˜˜˜˜˜˜`˜˜� �˜˜˜˜˜˜˜˜˜˜˜`˜˜� �˜˜˜˜˜˜˜˜˜˜`˜˜˜� �˜˜˜˜˜˜˜˜˜˜˜`˜˜�
CSPDN PSPDN ISDN PSTN
NOTE 1: National additions (e.g. mandatory use of data and time information in CSPDN).
NOTE 2: ETR 052 deals with Teletex-telex-intercommunication.
NOTE 3: ETS 300 001 [20] includes layer 4 as well.
NOTE 4: See figure 2.
Figure 1: Teletex terminal specification
Page 11
ETS 300 015: February 1994
Layers
�˜˜˜˜˜˜˜¿
‡ ‡ �˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ 4 ‡ ‡ ITU-T Recommendation T.70 [6](Clauses 1 to 4) ‡
‡ ‡ ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
ˆ˜˜˜˜˜˜˜· ‡ ETR 018 ‡ ‡
‡ ‡ ‡ ETS 300 102-1 ‡ ‡
‡ 3 ‡ ‡ ETS 300 102-2 ‡ ISO 8208 ‡
‡ ‡ ‡ ‡ ‡
ˆ˜˜˜˜˜˜˜· ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ ‡ ‡ ‡ ‡
‡ 2 ‡ ‡ ETS 300 125 ‡ CCITT X.75 ‡
‡ ‡ ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
ˆ˜˜˜˜˜˜˜· ‡ ‡
‡ ‡ ‡ ETS 300 012 ‡
‡ 1 ‡ ‡ ‡
‡ ‡ ‡ ETS 300 011 ‡
�˜˜˜˜˜˜˜� �˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
Figure 2: ETS 300 080 [21]
3 Definitions
The terms used in this ETS are as defined in the ITU-T Recommendations T.60 [1], T.61 [2], T.62 [3], T.63
[4], T.64 [5], T.70 [6] and F.201 [10] and CCITT Recommendation T.90 [7], T.390 [8] and F.200 [9].
4 Abbreviations
The abbreviations used in this ETS are as defined in the same ITU-T and CCITT Recommendations
referenced in Clause 3 above. The following abbreviations also apply.
ETS European Telecommunication Standard
ETSI European Telecommunications Standards Institute
TE Terminal Equipment
5 Scenario description
Exchange of Teletex documents between two end systems, which are Teletex terminal equipments
participating in the international Teletex service.
The overall operation of the Teletex service is as defined in CCITT Recommendation F.200 [9].
6 Conformity
A Teletex equipment shall be in conformity with this ETS if it follows the requirements which are contained
in Clause 7 below.
NOTE: The tests to be passed in order to check the conformance technically are laid down in
ITU-T Recommendation T.64 [5] and ETS 300 017 [12].
7 Layer description
7.1 Network dependent layers (1-4)
7.1.1 Access from telephone network(s)
The implementation of the telephone network access shall be fully in line with the provisions laid down and
described in ITU-T Recommendation T.70 [6] together with ENV 41105 [17].
7.1.2 Access from packet switched network(s)
The implementation of the Packet Switched Public Data Network (PSPDN) access shall be fully in line with
the provisions laid down and described in ITU-T Recommendation T.70 [6] together with ENV 41104 [15].
Page 12
ETS 300 015: February 1994
7.1.3 Access from circuit switched network(s)
The implementation of the Circuit Switched Public Data Network (CSPDN) access shall be fully in line with
the provisions laid down and described in ITU-T Recommendation T.70 [6] together with ENV 41106 [16].
7.1.4 Access from integrated services digital network(s)
The implementation of the Integrated Services Digital Network (ISDN) access shall be fully in line with the
provisions laid down and described in ITU-T Recommendation T.70 [6] together with ETS 300 080 [21].
7.2 Network independent layers (5-7)
7.2.1 Session layer description
The implementation of the session layer shall be fully in line with the provisions laid down and described in
ITU-T Recommendation T.62 [3] together with Clause 9 of this ETS.
7.2.2 Presentation layer description
The implementation of the presentation layer shall be fully in line with the provisions laid down and
described in ITU-T Recommendation T.61 [2].
7.2.3 Application layer description
The implementation of the application/service layer shall be fully in line with the provisions laid down and
described in ITU-T Recommendation T.60 [1]. This provides compatible intercommunication (according to
CCITT Recommendation F.200 [9]) between terminal equipment. However, to allow a more sophisticated
quality of service, recommended additional service and terminal requirements are given in Clause 10 of this
ETS.
8 Test specifications
8.1 Test suites for protocols with end-to-end significance
The test suites for protocols with end-to-end significance in the CSPDN, PSPDN, Public Switched
Telephone Network (PSTN) and ISDN shall be laid down as described in ETS 300 017 [12].
8.2 Test suites without end-to-end significance
a) The test suites for the CSPDN access layers, laid down and described in NET 1 [18], shall apply.
b) The test suites for the PSPDN access layers, laid down and described in NET 2 [19], shall apply.
c) The test suites for the ISDN access layers, D-channel only, laid down and described in ETS 300 080
[21], shall apply.
d) The test suites for the PSTN access layers, laid down and described in ETS 300 001 [20], shall
apply.
e) The test procedures with end-to-end significance in the ISDN shall be laid down as described in ETS
300 081 [11].
8.3 Test suites for system related requirements
To be considered.
Page 13
ETS 300 015: February 1994
9 Additional session layer requirements (to ITU-T Recommendation T.62)
9.1 ETSI agreed additional requirements to ITU-T Recommendation T.62
9.1.1 Paragraph 3.4.1.2a/T.62
If a normal document is transmitted from a Teletex terminal to the Teletex-Telex conversion facility this
parameter shall be indicated.
9.1.2 Paragraph 3.4.4.3/T.62
All terminals shall examine the non-basic terminal capabilities indicated in Command Session Start (CSS)
or Response Session Start Positive (RSSP) and not rely on a subsequent Command Document Capability
List/Response Document Capability List Positive (CDCL/RDCLP) exchange to negotiate the use of any
capabilities from table 3/T.62 [3].
9.1.3 Paragraph 3.4.5.1/T.62
If the CDCL also contains the indication of receiving capabilities given in table 3/T.62 [3], the receiving
terminal shall indicate these in the RDCLP as far as it supports these capabilities.
9.1.4 Paragraph 3.4.12/T.62
Sending terminals shall limit the content size of Command Document User Information (CDUI) to 5 000
octets or less.
Although ITU-T Recommendation T.62 [3] requires the possibilities to receive blocks of arbitrary size, the
implementation of receiving buffers is allowed, if the following requirement is met:
- test-blocks of at least 10 000 octets in a single CDUI shall be accepted.
9.1.5 Paragraph 3.2.3.2/T.62
A negative response to CSS with reason parameter 000 0001 shall be mandatory for Teletex terminals if
the receive storage capacity is below 2 k-octets.
9.1.6 Paragraph 3.2.10/T.62
It shall not be mandatory for terminals to respond to a request (via a "Request Session Function" in RSSP
or RSUI) for change of control.
However, a calling terminal shall be able to allow the called equipment to send document(s) by giving
change of control (CSCC). The choice of whether or not CSCC is sent shall be left to the operator.
9.1.7 Paragraph 3.3.1.1.c/T.62
The CSCC command shall only be invoked outside document boundaries.
9.1.8 Paragraph 3.3.2.6/T.62
The timer value T shall be T = 4 s ± 1 s.
9.1.9 Paragraph 3.3.2.7.b/T.62
A Teletex terminal shall support the window size of three.
Page 14
ETS 300 015: February 1994
9.1.10 Paragraph 3.3.2.10/T.62
In general, the session protocol does allow the use of more than one session connection per transport
connection. In order to avoid ambiguities in case of linking parts of a document which might be necessary,
the calling terminal may only use this possibility if the unambiguity of the document linking information is
guaranteed at both communication parties.
9.1.11 Paragraph 3.4.3/T.62
The sink shall not reject the reception of a document continuation because of the evaluation of document
linking information.
The possibility to reject a Command Document Continue (CDC) because of syntax errors is not touched
upon by this rule.
9.1.12 Paragraph 3.4.3.2.e/T.62
Third sentence shall read:
A terminal receiving a CDC that does not contain all of the terminal capabilities shall not reject the
continuation of the document.
9.1.13 Paragraph 3.4.4.4/T.62
The CDCL command shall only be invoked outside document boundaries.
9.1.14 Paragraph 3.5.3/T.62
When a called terminal has answered any checkpoint positively within a document it subsequently may not
send a negative retrospective response, Response Document General Reject (RDGR), to the commands
Command Document Start (CDS) or CDC which initiated the start of this document.
9.1.15 Paragraph 4.1.4/T.62
During one transport connection a Teletex page may be repeated only once. All Teletex terminals need to
be equipped with a control facility in order to avoid endless loops in case of page repetition or the transfer
of the right to transmit. Such loops shall lead to a disconnection. There is no obligation to implement a
specific control mechanism.
9.1.16 Annex J, paragraph 2.1.1.c/T.62
The timer value T shall be T = ± 1 s.
9.2 Use of the session protocol for interworking with automatic Teletex directory service
See Annex A (normative).
9.3 Types of document
See Annex B (normative).
10 ETSI agreed additional service and terminal requirements (modifications to
ITU-T Recommendation T.60)
The following are ETSI agreed additional service and terminal requirements which are also modifications to
ITU-T Recommendation T.60 [1].
Page 15
ETS 300 015: February 1994
10.1 Paragraph 4.1.1.1/T.60
Transmission periods
To ensure an adequate level of service to users, terminals shall, under ideal conditions (i.e. without frame
repetitions, no options, no satellite or multiplexers links), be capable of receiving a document of one page
(1 500 octets) and four pages (1 500 characters each) within the following range of time.
a) CSPDN, PSPDN, PSTN case:
one page: 12 seconds;
four pages: 30 seconds.
b) PSTN (half duplex) case:
one page: 24 seconds;
four pages: 60 seconds.
c) ISDN case:
one page: 7,2 seconds;
four pages: 7,8 seconds.
NOTE: Every single page requires 0,2 seconds for pure transmission and about 7 seconds in
total are required for call initiation, etc.
10.2 Paragraph 4.1.3/T.60
The terminal shall be designed and constructed for 24 hours a day operation.
Even after a mains failure the terminal shall be able to receive messages automatically. Local operation
shall not influence the ability to receive calls.
10.3 Paragraph 8.2.1/T.60
Terminals shall be able to utilise the printable area of ISO-A4 (horizontally and vertically).
10.4 Paragraph 4.1.4/T.60
The terminal identification shall not be lost even if the terminal is without power. The identification shall in
such cases remain intact for at least 4 weeks.
The terminal identification shall only be entered and amended by an authorised body, which is specified by
the administration.
The method of entering the terminal identification shall, as far as possible, exclude the possibility of the
terminal identification being altered by the terminal user.
10.5 Paragraph 5.1.3/T.60
The terminal shall provide the capability of automatic checking of part 4 (= mnemonic abbreviation) of the
terminal identification. The identification check shall not be extended to parts other than part 4 (mnemonic
abbreviation).
The choice of whether the check is performed is left to the operator.
If the result of the checking is negative, automatic text transmission shall not take place.
Page 16
ETS 300 015: February 1994
10.6 Paragraph 7.2.3/T.60
As soon as the available storage capacity is less than the memory threshold, the sender of the document
is informed that the ability of the receiving terminal to continue to accept traffic is jeopardized (see ITU-T
Recommendation T.62 [3], paragraph 3.4.14.2). A value of 2 k-octets is recommended for the memory
threshold.
A called terminal in the receive mode shall not enter a session if its spare storage capacity is below 2 k-
octets, i.e. it shall send a negative response to CSS with a reason parameter identifier and value indicating
that it is temporarily unable to enter a session.
10.7 Paragraph 4.1.3.3/T.60
A minimum receiving-store-size of 32 k-octets shall be provided.
10.8 Paragraph 4.1.3/T.60
Received information shall be in a non-volatile memory before acknowledgements Response Document
Page Boundary Positive (RDPBP) or Response Document End Positive (RDEP) are given.
Messages in the receiving memory shall not be lost for at least 72 hours even in the event of mains failure.
A non-volatile memory is understood to be not only a magnetic tape, disc memory etc., but also a
semiconductor memory whose power supply is ensured by appropriate accumulators in case of a mains
failure.
10.9 Paragraph 5.2/T.60
Since the date and time may not be provided by the network but by the terminal, the calling terminal
provides one or both possibilities, according to the list appended in Annex D.
For a locally provided clock, the inaccuracy should not be more than one minute per month.
Temporary mains failure shall not result in an incorrect date and time.
In the event of a mains failure, the clock continues to function correctly for at least 24 hours (72 hours is
recommended).
10.10 Paragraph 6/T.60
If the use of a plug-in modem is allowed, additional national requirements may have to be met, which are,
however, presently outside the scope of this ETS.
Page 17
ETS 300 015: February 1994
10.11 Paragraph 7/T.60
Communication log(s)
If a Teletex terminal provides a communication log, it shall contain the following information:
Transmitted documents:
- for each document sent either the Call Identification Line (CIL) or at least:
- the called terminal's Terminal IDentifier (TID) (if received);
- session date and time;
- number of last acknowledged page;
- document reference number;
- reason for non-delivery (if any);
- indication, whether CDC was used;
- indication on type of document (e.g. control, operator) if different from normal document.
A sent control document, that is related to a "normal" document AND does not carry additional user
information (e.g. a control document used to precede a normal document in the Teletex-telex-
intercommunication case) does not necessarily need an entry in the log nor need the document be
maintained.
Received document:
- for each document received either the CIL or at least:
- the calling terminal's TID;
- session date and time;
- document reference number;
- number of last acknowledged page;
- reason for interruption (if any (e.g. own memory overflow));
- linking information (if any);
- indication on type of document (e.g. control, operator), if different from normal control.
A received control document, the content of which may be checked automatically AND leads to an
appropriate indication in the associated entry of the "normal" document (e.g. a positive acknowledgement
control document in the case of Teletex-telex-intercommunication) does not necessarily need a separate
entry in the log nor need the document be maintained.
Entries in the communication log shall be cleared on request of the operator. When the receive log is full,
the terminal shall refuse all incoming calls, until the log is emptied, e.g. by sending Response Session Start
Negative (RSSN) at the session establishment indicating a memory overflow.
Concerning safety against loss of entries subclause 10.8 of this ETS applies.
The representation of the communication log shall be independent from the representation of associated
sent/received documents.
Additional information (such as calling/called line ID or locally provided additional indications) may be given.
The above mentioned requirements are mandatory in the following countries:
Austria, Belgium, Germany, Netherlands, Switzerland.
10.12 Paragraph 7.2.2/T.60
A "Receive Store Nearly full" indicator shall be provided for the terminal operator. A minimum threshold
value of 4 k-octets is recommended for this indicator.
Page 18
ETS 300 015: February 1994
10.13 Paragraph 4.1.3/T.60
The loss of a received message should be excluded as far as possible.
10.14 Paragraph 5.2/T.60
The CIL, if printed out, is represented in the 5th line (= first line of the printable area), preferably
superscripted.
The sequence of functions which lead to a visualisation (e.g. printing) of the CIL is a local property of the
terminal.
Arrangement of field 4 of the call identification line
It is not laid down internationally that the numbers of digits of the document reference number and page
reference number is equal to 6. It may be smaller (one digit each as a minimum).
The following agreement was reached in order to ensure a clear and uniform representation.
For the representation of field 4 of the CIL on the receiving side the following shall apply:
1) the document reference number shall be represented flush left;
2) the page reference number shall be represented flush right;
3) document (and page) reference numbers are to be separated by at least one hyphen;
4) leading zeros may be represented. Preferably, the format used by the sender should apply.
EXAMPLE 1:
received : document ref. No. 001; page ref. No. 002,
represented : /80-11-24-12:17/001-002.
EXAMPLE 2:
received : document ref. No. 1; page ref. No. 2,
represented : /80-11-24-12:17/1-----2,
or : /80-11-24-12:17/1-00002.
If the number of digits of the document reference number and page reference number is larger than 6, a
case of fault has occurred according to ITU-T Recommendation T.61 [2], supplement to paragraph 3.3.3.4
(if possible, the faulty message shall be represented).
Therefore, the attempt should be made to print out, if required, all transmitted information beyond field 4.
In this case, the following applies:
a) the hyphen shall be kept;
b) leading zeros shall be deleted;
c) the value of the document reference number shall be kept;
d) digits of the page reference number with highest value shall be deleted.
Page 19
ETS 300 015: February 1994
Linking
Linking is rendered possible by the use of command CDC in the procedural level.
In order to make automatic linking at all possible, all terminals shall be capable of receiving command
CDC. If wrong parameters have been used within the CDC command, the latter should not be rejected so
that manual linking can at least be applied where parameters to now allow automatic linking.
The linking information contains:
- identification of the calling terminal;
- identification of the called terminal;
- date and time of the actual transmission;
- document reference number of the actual transmission;
- linking information;
- date and time of the first transmission;
- document reference number of the first transmission;
- page reference number of the page with which the transmission is continued;
and is evaluated as follows:
a) automatic linking
Automatic linking shall only apply on the following conditions:
1) the document to be linked shall be available in the receiving store and no local access has yet been
taken place;
2) no pages shall be missing;
3) pages with identical page reference number shall be identical in contents and layout.
If automatic linking applies, the presentation of the linking information is not required. The CIL of the linked
document shall contain the data of the last linking.
b) manual linking
The call identification line of the continuation of a document shall contain the actual data.
The linking informa
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...