SIST ETS 300 075 E2:2003

• Abstract:

  Extension to support compression techniques and new file header parame ters.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.160.99 - Other audio, video and audiovisual equipment
• 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
• Ref Project: ETSI ETS 300 075 ed.2 (1994-02) - Terminal Equipment (TE); Processable data; File transfer

SIST ETS 300 075 E2:2003 is the Slovenian adoption of ETS 300 075 Edition 2 for Terminal Equipment (TE); Processable data; File transfer. It specifies how processable data files are transferred in Videotex environments, including telesoftware and printer-related applications, and how the file structure, service primitives, and protocol coding are organized for that transfer. The document is aimed at terminal equipment, host or server systems, and other end systems that need controlled file exchange.

What does SIST ETS 300 075 E2:2003 specify?

SIST ETS 300 075 E2:2003 specifies a file transfer facility for processable data, including files that may contain computer software or other file types. The scope covers download from a host to a terminal and transfer between two end systems in both directions, with the transfer controlled by one side or the other after preliminary negotiation.

The document is designed for a Videotex environment, but it can also be used outside that environment. In practice, that means implementers can reuse the same service model and coding rules on different networks if they can support the specified dialogue and transfer behavior.

The main body is organized as follows:

Clause	Topic
1	Scope
2	Normative references
3	Definitions and abbreviations
4	Service, applications, protocols, coding
5	Telesoftware and auxiliary device applications
6	T-Protocol specification
7	Coding of TDUs
8	D-protocol specification

Clause 4 defines the service model and the protocol layers. Clause 5 applies that model to telesoftware and printer-oriented file exchange. Clauses 6 to 8 give the TDU behavior, coding rules, and DDU adaptation rules that make the transfer work across different Videotex systems.

What are the key requirements of SIST ETS 300 075 E2:2003?

Two service classes are defined in Clause 4

SIST ETS 300 075 E2:2003 defines a basic kernel and a symmetrical service. The basic kernel supports file transfer from a host to a terminal, with the host controlling the operations and with lower-level recovery mechanisms. The symmetrical service supports transfer in both directions between two systems, with either side able to act as Master after preliminary negotiation.

In practice, this is the first decision an implementer or buyer needs to make. If the system only downloads files in one direction, the basic kernel is the relevant model. If both ends must initiate, control, and recover transfers, the symmetrical service is the better fit.

The transfer is split into a T-layer and a D-layer

Clause 4 describes processable data as being carried by Telesoftware Data Units (TDUs) exchanged by the T-protocol, while the Dialogue Data Units (DDUs) form the D-protocol layer used to adapt to different Videotex systems. The document also states that optional 8-bit transparency and optional error detection and recovery are provided through this layered structure.

This matters because a conforming implementation has to support both the file-transfer meaning of the TDU and the transport adaptation performed by the DDU layer. In Syntax Based Videotex (SBV), the DDU protocol is not used, and the transparent processable data primitives are linked directly to the processable-data service.

The T-service is organized into regimes and service elements

Clause 4 breaks the T-service into an Association regime, an Access regime, and a Transfer regime. It also defines the service elements for association establishment and release, access establishment and end of access, file directory, load, save, rename, delete, typed data, mass transfer, exception reporting, and collision handling.

In practice, this regime model tells the implementation when a service is allowed and what kind of exchange is taking place. It also makes recovery easier to design, because the standard separates connection management, file access, and data transfer into different phases.

File transfer is based on a header plus content structure

Clause 5 defines a transfer file as having a header and file content. The header carries attributes such as file type, execution order, transfer name, filename, date or time of last modification, file length, destination code, file coding, destination name, cost, user field, load and execute addresses, compression mode, device, file checksum, author name, future file length, permitted actions, legal qualification, creation data, access history, recipient, telematic file transfer version, and status of file attributes.

This is important because interoperability depends on how the sender encodes file identity and file behavior. The header is not just descriptive metadata - it is also what lets the receiver decide where the file belongs, whether it should be executed, and how local storage should treat it.

Telesoftware and printer applications have specific file groupings and rules

Clause 5 defines two applications: telesoftware and printer device application. Telesoftware uses three file groups - group A, group B, and group C - and the basic kernel uses group A only. The printer device application is treated as a specific case of the auxiliary device application and does not use all file parameters.

For implementers, this means the same file-transfer mechanism is reused for different business functions, but not every file group or header field has to be implemented in every profile. Buyers should check whether they need only software transfer, or also presentation files and service support files.

Directory requests use a defined designation syntax

Clause 5.7 defines the designation field used in a directory request. It supports the wildcard "*" and the logical operators AND, shown as "/", and OR, shown as "+", with parentheses controlling grouping and operator priority.

This matters for file browsing and automated selection. A system that supports directory requests must parse this syntax correctly, because the designation field is the search criterion used to retrieve matching file names from the current database.

TDUs and DDUs have specific coding, confirmation, and recovery rules

Clause 6 maps each service primitive to one or more TDUs. It also states how TDUs are conveyed: T-Associate uses D-set mode, other TDUs use D-Data, and confirmation-related TDUs are handled with the confirmation flag when required. Clause 6 also defines what happens on exceptions, including recovery actions and the rule that repeated identical errors can lead to D-U-Abort.

Clause 7 gives the TLV coding for TDUs, including the Command Identifier, Length Indicator, and parameter field. It also covers provider and user refusal reasons, file header coding, and file content coding.

Clause 8 defines the D-protocol modes for translation and DDU handling. It lists four translation modes and seven DDU modes, and it covers error detection and recovery using sequence numbering, flags, timers, and Block Check Sequence (BCS) coding.

In practice, these clauses are the implementation rules. They determine how the sender frames data, how the receiver interprets it, and how both sides recover from loss, refusal, or protocol error.

What terms does SIST ETS 300 075 E2:2003 define?

• Acceptor - the entity that accepts or refuses a service indication.
• Initiator - the entity that starts a service request.
• Master - the entity that controls the dialogue.
• Regime - a set of protocol phases forming a continuous period of time, used to limit when certain services are available.
• Telesoftware Data Unit (TDU) - the protocol element used to handle the T-Protocol.
• Dialogue Data Unit (DDU) - the protocol element used in the D-protocol to adapt processable-data exchanges to different Videotex systems.
• Mass transfer phase - the phase that begins with the first T-Write TDU and ends with T-Abort, T-Transfer-reject, T-Read-restart, or confirmation of the last T-Write.
• Transfer unit - the data transferred by one mass transfer primitive.

Who uses SIST ETS 300 075 E2:2003?

SIST ETS 300 075 E2:2003 is used by designers and integrators of Videotex terminal equipment, host systems, servers, and executors that exchange processable data files. It is also relevant to developers of telesoftware download functions and printer-device applications that rely on a controlled file structure and protocol exchange.

In practice, quality managers and buyers use it to check whether an implementation supports the right service class, file groups, transfer modes, and recovery behavior. Telecommunications and terminal-equipment engineers use it when they need interoperable file transfer across systems that may not share the same internal storage model.

What changed in SIST ETS 300 075 E2:2003 from the previous edition?

SIST ETS 300 075 E2:2003 is identified as the second edition. The scope states that this edition extends support for compression techniques and new file header parameters.

Which standards are used with SIST ETS 300 075 E2:2003?

• CCITT Recommendation T.101 (1988) - gives the interworking basis for videotex services.
• ETS 300 072 - provides the Videotex presentation layer protocol and data syntax used by the processable-data facility.
• ETS 300 079 - covers syntax-based Videotex end-to-end protocols in ISDN circuit-mode DTE-DTE use.
• ETS 300 223 - provides the syntax-based Videotex end-to-end protocol mechanisms used with SBV.
• CCITT Recommendation X.200 (1988) - supplies the OSI reference model used for the layered description.
• CCITT Recommendation X.210 (1988) - defines the OSI layer service definition convention used in the service model.
• CCITT Recommendation T.51 (1988) - supplies coded character sets for telematic services.

What does the SIST ETS 300 075 E2:2003 document contain?

The document contains the service model for processable data, the telesoftware and printer-device application rules, and the full T-Protocol and D-protocol behavior. It includes mapping tables for service primitives and TDUs, plus the rules for sending, receiving, confirming, rejecting, aborting, and recovering transfers.

It also contains the file header and file content coding rules, directory request syntax examples, and the parameter coding rules for telesoftware and printer applications. Clause 8 adds the DDU modes, translation modes, error detection, timer use, and a CRC example for BCS coding.

For engineering work, the most useful parts are the tables and coding sections, because they define what has to be encoded, how responses are formed, and how errors are handled during transfer.

SLOVENSKI STANDARD
01-december-2003
7HUPLQDOVNDRSUHPD7(±3RGDWNLNLMLKMHPRJRþHREGHODWL±3UHQRVGDWRWHN
Terminal Equipment (TE); Processable data; File transfer
Ta slovenski standard je istoveten z: ETS 300 075 Edition 2
ICS:
33.160.99 Druga avdio, video in Other audio, video and
avdiovizuelna oprema audiovisual equipment
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 075
TELECOMMUNICATION February 1994
STANDARD Second Edition
Source: ETSI TC-TE Reference: RE/TE-01041
ICS: 33.040.40
Processable data, file transfer
Key words:
Terminal Equipment (TE);
Processable data
File transfer
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 - [e-mail]
X.400: Internet:
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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 075: 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 075: February 1994
Contents
Foreword .13
1 Scope .15
2 Normative references.15
3 Definitions and abbreviations .15
3.1 Definitions .15
3.2 Abbreviations .16
4 Service, applications, protocols, coding .17
4.1 Service definition.19
4.1.1 Scope and field of application .19
4.1.2 Model of the T-service.19
4.1.2.1 Services references.19
4.1.2.2 Services definitions.19
4.1.2.2.1 General terms.19
4.1.2.2.2 Regimes .19
4.1.2.2.3 Roles.20
4.1.2.2.4 Local concepts.20
4.1.2.3 Service elements .21
4.1.2.3.1 General organisation .21
4.1.2.3.2 Association regime .22
4.1.2.3.3 Access regime.22
4.1.2.3.4 Transfer regime .23
4.1.2.3.5 Restrictions on the use of services.23
4.1.2.4 Concepts related to mass transfer .23
4.1.2.4.1 Recovery during a mass transfer.23
4.1.2.4.2 Recovery outside a mass transfer.24
4.1.2.4.3 Anticipation window .24
4.1.3 Association regime control .24
4.1.3.1 Association establishment .25
4.1.3.1.1 Function.25
4.1.3.1.2 Parameters .25
4.1.3.1.2.1 Service class.25
4.1.3.1.2.2 Called address.26
4.1.3.1.2.3 Calling address.26
4.1.3.1.2.4 Application name .26
4.1.3.1.2.5 Explicit confirmation.26
4.1.3.1.2.6 Timeouts.26
4.1.3.1.2.7 Request identification .26
4.1.3.1.2.8 Identification.26
4.1.3.1.2.9 User data .27
4.1.3.1.2.10 Result.27
4.1.3.1.3 Association establishment operation .27
4.1.3.2 Association release.28
4.1.3.2.1 Function.28
4.1.3.2.2 Parameters .28
4.1.3.2.2.1 User data .28
4.1.3.2.2.2 Result.28
4.1.3.2.3 Association release operation.28
4.1.3.3 Association abort .28
4.1.3.3.1 Function.28
4.1.3.3.2 Parameters .29
4.1.3.3.3 Association abort operation .29
4.1.4 Access regime control.29
4.1.4.1 Access establishment.30

Page 4
ETS 300 075: February 1994
4.1.4.1.1 Function . 30
4.1.4.1.2 Parameters . 30
4.1.4.1.2.1 Role. 30
4.1.4.1.2.2 Function . 30
4.1.4.1.2.3 Size of transfer units . 30
4.1.4.1.2.4 Anticipation window. 31
4.1.4.1.2.5 Recovery . 31
4.1.4.1.2.6 Transfer mode. 31
4.1.4.1.2.7 User data. 31
4.1.4.1.2.8 Result. 31
4.1.4.2 End of Access service. 32
4.1.4.2.1 Function . 32
4.1.4.2.2 Parameters . 32
4.1.4.2.2.1 User data. 32
4.1.4.2.2.2 Result. 32
4.1.4.3 File directory service . 32
4.1.4.3.1 Function . 32
4.1.4.3.2 Parameters . 32
4.1.4.3.2.1 Designation . 33
4.1.4.3.2.2 User data. 33
4.1.4.3.2.3 Result. 33
4.1.4.4 Load service. 33
4.1.4.4.1 Function . 33
4.1.4.4.2 Parameters . 33
4.1.4.4.2.1 Recovery point . 33
4.1.4.4.2.2 Designation . 34
4.1.4.4.2.3 User data. 34
4.1.4.4.2.4 Result. 34
4.1.4.5 Save service. 34
4.1.4.5.1 Function . 34
4.1.4.5.2 Parameters . 34
4.1.4.5.2.1 Recovery point . 35
4.1.4.5.2.2 Designation . 35
4.1.4.5.2.3 User data. 35
4.1.4.5.2.4 Result. 35
4.1.4.6 Rename service . 35
4.1.4.6.1 Function . 35
4.1.4.6.2 Parameters . 35
4.1.4.6.2.1 New name. 36
4.1.4.6.2.2 Designation . 36
4.1.4.6.2.3 User data. 36
4.1.4.6.2.4 Result. 36
4.1.4.7 Delete service . 36
4.1.4.7.1 Function . 36
4.1.4.7.2 Parameters . 36
4.1.4.7.2.1 Designation . 36
4.1.4.7.2.2 User data. 36
4.1.4.7.2.3 Result. 37
4.1.4.8 Typed data service. 37
4.1.4.8.1 Function . 37
4.1.4.8.2 Parameters . 37
4.1.4.8.2.1 User data. 37
4.1.5 Transfer regime control . 37
4.1.5.1 Mass transfer . 38
4.1.5.1.1 Function . 38
4.1.5.1.2 Parameters for T-WRITE. 38
4.1.5.1.2.1 Explicit confirmation . 38
4.1.5.1.2.2 First block. 38
4.1.5.1.2.3 Block number. 39
4.1.5.1.2.4 Data field. 39
4.1.5.1.2.5 Result. 39
4.1.5.1.3 Parameters for T-WRITE-END. 39
4.1.5.1.3.1 First block. 39

Page 5
ETS 300 075: February 1994
4.1.5.1.3.2 Block number.39
4.1.5.1.3.3 Data field.39
4.1.5.1.3.4 Result.40
4.1.5.1.4 Operation of the mass transfer procedure.40
4.1.5.2 Exception report service .41
4.1.5.2.1 Function.41
4.1.5.2.2 Parameters .41
4.1.5.2.2.1 Reason .41
4.1.5.2.3 Error recovery operation.41
4.1.6 Exception.42
4.1.6.1 Exception reporting.42
4.1.6.1.1 Function.42
4.1.6.1.2 Parameters .42
4.1.6.1.2.1 Reason .42
4.1.6.1.3 Error recovery operation.42
4.1.7 Collisions .42
4.1.7.1 Collision in the Association phase .42
4.1.7.2 Collision in the Association regime.42
4.1.7.3 Collision in the Access regime.43
4.1.7.4 Collision in the Transfer regime.43
5 Telesoftware and auxiliary device applications .44
5.1 Preliminaries .44
5.2 The telesoftware application organisation.44
5.2.1 Transferable files - group A.44
5.2.2 Application presentation file - group B.44
5.2.3 Service support - group C .45
5.2.4 Working area.45
5.3 Printer application organisation.45
5.4 Files .45
5.4.1 File identification.45
5.4.1.1 Preliminaries.45
5.4.1.2 Description files .45
5.4.1.3 Software file.45
5.4.1.4 Data files.45
5.4.1.5 Command files.45
5.4.1.6 Text files .46
5.4.1.6.1 Text files - group A .46
5.4.1.6.2 Text files - group B .46
5.4.1.6.3 Text files - group C .46
5.4.1.6.4 Text files from a file directory request.46
5.4.2 Transferable applications .46
5.4.2.1 Structure of a transferable application.46
5.4.2.1.1 Purpose of the description file .46
5.4.2.1.2 Organisation of the description file .46
5.4.3 File classification .46
5.4.3.1 Structure of a transfer name.47
5.4.3.1.1 Keywords .47
5.4.3.1.2 Transfer name .47
5.5 Description of the transfer file structure.47
5.5.1 Header.47
5.5.1.1 File type .47
5.5.1.2 Execution order.47
5.5.1.3 Transfer name .47
5.5.1.4 Filename.48
5.5.1.5 Date/time of last modification .48
5.5.1.6 File length .48
5.5.1.7 Destination code.48
5.5.1.8 File coding .48
5.5.1.9 Destination name.48
5.5.1.10 Cost .49
5.5.1.11 User field.49
5.5.1.12 Load address.49

Page 6
ETS 300 075: February 1994
5.5.1.13 Execute address (absolute) . 49
5.5.1.14 Execute address (relative) . 49
5.5.1.15 Compression mode. 49
5.5.1.16 Device . 49
5.5.1.17 File checksum. 49
5.5.1.18 Author name . 49
5.5.1.19 Future file length . 49
5.5.1.20 Permitted actions . 50
5.5.1.21 Legal qualification . 50
5.5.1.22 Creation. 50
5.5.1.23 Last read access. 50
5.5.1.24 Identity of the last modifier . 50
5.5.1.25 Identity of the last reader. 50
5.5.1.26 Recipient . 50
5.5.1.27 Telematic file transfer version. 50
5.5.1.28 Status of file attributes . 51
5.5.2 File content . 51
5.6 Use of the T-service for telesoftware and printer device application. 51
5.6.1 Preliminaries. 51
5.6.2 Association . 52
5.6.3 Release. 52
5.6.4 Abort . 52
5.6.5 Access . 52
5.6.6 End of access . 52
5.6.7 File directory . 53
5.6.7.1 Byte sequence in a directory request. 53
5.6.8 Load. 53
5.6.9 Help . 53
5.6.10 Save. 54
5.6.11 Rename . 54
5.6.12 Suppression. 54
5.6.13 Transfer abort . 55
5.7 The designation field in a directory request. 55
6 T-Protocol specification . 57
6.1 Overview . 57
6.2 Description and use of TDU. 58
6.2.1 T-Associate. 58
6.2.1.1 Content of the T-Associate TDU and the associated
responses . 59
6.2.1.2 Sending T-Associate. 59
6.2.1.3 Receiving T-Associate . 60
6.2.2 T-Release . 60
6.2.2.1 Content of the T-Release TDU and the associated
response . 60
6.2.2.2 Sending T-Release . 60
6.2.2.3 Receiving T-Release. 60
6.2.3 T-Abort. 60
6.2.3.1 Content of the T-Abort TDU. 61
6.2.3.2 Sending T-Abort. 61
6.2.3.3 Receiving T-Abort . 61
6.2.4 T-Access. 61
6.2.4.1 Content of the T-Access TDU and the associated
responses . 62
6.2.4.2 Sending T-Access. 62
6.2.4.3 Receiving T-Access . 62
6.2.5 T-End-Access . 63
6.2.5.1 Content of the T-End-Access TDU and the associated
response . 63
6.2.5.2 Sending T-End-Access . 63
6.2.5.3 Receiving T-End-Access. 63
6.2.6 T-Directory . 63

Page 7
ETS 300 075: February 1994
6.2.6.1 Content of the T-Directory TDU and the associated
responses .63
6.2.6.2 Sending T-Directory.64
6.2.6.3 Receiving T-Directory .64
6.2.7 T-Load.64
6.2.7.1 Content of the T-Load TDU and the associated
responses .64
6.2.7.2 Sending T-Load .65
6.2.7.3 Receiving T-Load.65
6.2.8 T-Save.65
6.2.8.1 Content of the T-Save TDU and the associated
responses .65
6.2.8.2 Sending T-Save.66
6.2.8.3 Receiving T-Save .66
6.2.9 T-Rename .66
6.2.9.1 Content of the T-Rename TDU and the associated
responses .66
6.2.9.2 Sending T-Rename .67
6.2.9.3 Receiving T-Rename.67
6.2.10 T-Delete.67
6.2.10.1 Content of the T-Delete TDU and the associated
responses .67
6.2.10.2 Sending T-Delete.68
6.2.10.3 Receiving T-Delete .68
6.2.11 T-Typed-data.68
6.2.11.1 Content of the T-Typed-data TDU.68
6.2.11.2 Sending T-Typed-data.68
6.2.11.3 Receiving T-Typed-data .68
6.2.12 T-Write .68
6.2.12.1 Content of the T-Write TDU and the associated
responses .68
6.2.12.1.1 First/last .69
6.2.12.1.2 Explicit confirmation.69
6.2.12.1.3 Block number.69
6.2.12.1.4 Data .69
6.2.12.2 Sending T-Write.69
6.2.12.3 Receiving T-Write.70
6.2.13 T-Transfer-reject .70
6.2.13.1 Content .70
6.2.13.2 Sending T-Transfer-reject .70
6.2.13.3 Receiving T-Transfer-reject.70
6.2.14 T-Read-restart.70
6.2.14.1 Content .70
6.2.14.2 Sending T-Read-restart .70
6.2.14.3 Receiving T-Read-restart .71
6.2.15 T-P-Exception.71
6.2.15.1 Content .71
6.2.15.2 Sending T-P-exception .71
6.2.15.3 Receiving T-P-exception .71
6.2.16 T-Response-positive .71
6.2.16.1 Content .71
6.2.16.2 Sending T-Response-positive .71
6.2.16.3 Receiving T-Response-positive.72
6.2.17 T-Response-negative.72
6.2.17.1 Content .72
6.2.17.2 Sending T-Response-negative .72
6.2.17.3 Receiving T-Response-negative .72
6.3 Exceptions and timers .72
6.3.1 Application response timer.72
6.3.2 Abnormal termination of the mass transfer .73
6.3.3 Errors outside a mass transfer phase .73
6.4 Use of DDU layer.73
6.5 Use of syntax based videotex.74

Page 8
ETS 300 075: February 1994
7 Coding of TDUs . 74
7.1 Coding of TDUs. 74
7.1.1 Structure of TDUs. 74
7.1.1.1 Command Identifier field (CI). 74
7.1.1.2 Length Indicator field (LI) . 74
7.1.1.3 Parameter field. 75
7.1.2 Coding of TDUs . 75
7.1.2.1 Associate. 76
7.1.2.1.1 Request. 76
7.1.2.1.2 Responses . 77
7.1.2.1.3 Called address . 77
7.1.2.1.4 Calling address . 77
7.1.2.1.5 Application name. 77
7.1.2.1.6 Application response timeout. 78
7.1.2.1.7 Service class. 78
7.1.2.1.8 Explicit confirmation . 78
7.1.2.1.9 Identification. 78
7.1.2.1.10 Request identification. 78
7.1.2.1.11 User data. 78
7.1.2.1.12 Reason (in the Result parameter). 78
7.1.2.2 T-Release . 78
7.1.2.2.1 Request. 78
7.1.2.2.2 Response. 79
7.1.2.3 T-Abort . 79
7.1.2.3.1 Request. 79
7.1.2.4 T-Access. 79
7.1.2.4.1 Request. 79
7.1.2.4.2 Response. 79
7.1.2.4.3 Role/function . 80
7.1.2.4.4 Size, recovery, window. 80
7.1.2.4.5 Transfer mode. 81
7.1.2.4.6 User data. 81
7.1.2.5 T-End-access. 81
7.1.2.5.1 Request. 81
7.1.2.5.2 Response. 81
7.1.2.6 T-Directory . 82
7.1.2.6.1 Request. 82
7.1.2.6.2 Response. 82
7.1.2.6.3 User data. 82
7.1.2.6.4 Designation . 82
7.1.2.7 T-Load. 82
7.1.2.7.1 Request. 82
7.1.2.7.2 Responses . 82
7.1.2.7.3 Recovery point . 83
7.1.2.7.4 Designation . 83
7.1.2.7.5 User data. 83
7.1.2.8 T-Save. 83
7.1.2.8.1 Request. 83
7.1.2.8.2 Responses . 83
7.1.2.9 T-Rename. 84
7.1.2.9.1 Request. 84
7.1.2.9.2 Responses . 84
7.1.2.9.3 Designation, New name. 84
7.1.2.10 T-Delete . 84
7.1.2.10.1 Request. 84
7.1.2.10.2 Responses . 85
7.1.2.11 T-Typed data. 85
7.1.2.11.1 Request. 85
7.1.2.12 T-Write . 85
7.1.2.12.1 Request. 85
7.1.2.12.2 Responses to a T-Write (not last). 85
7.1.2.12.3 Responses to a T-Write (last). 86
7.1.2.12.4 Explicit confirmation, first/last, block number. 86

Page 9
ETS 300 075: February 1994
7.1.2.12.5 Result.87
7.1.2.13 T-Transfer-reject.87
7.1.2.13.1 Request .87
7.1.2.14 T-Read-restart .87
7.1.2.14.1 Request .87
7.1.2.15 T-P-Exception.87
7.1.2.15.1 Indication .87
7.2 Coding of provider and user refusals.87
7.2.1 Reason codes in a T-Response negative .87
7.2.2 Reason in other TDUs.88
7.2.2.1 Provider reason .88
7.2.2.2 User reason .88
7.3 File coding.88
7.3.1 File structure coding.88
7.3.2 File Header (FH) coding.88
7.3.2.1 File type .89
7.3.2.2 Execution order.89
7.3.2.3 Transfer name .89
7.3.2.4 File name.90
7.3.2.5 Date .90
7.3.2.6 File length .90
7.3.2.7 Destination code.90
7.3.2.8 File coding .90
7.3.2.9 Destination name.91
7.3.2.10 Cost .91
7.3.2.11 User field/Application reference.91
7.3.2.12 Load address.91
7.3.2.13 Execute address (absolute).92
7.3.2.14 Execute address (relative).92
7.3.2.15 Compression mode .92
7.3.2.16 Device.92
7.3.2.17 File checksum.94
7.3.2.18 Author name .94
7.3.2.19 Future file length.94
7.3.2.20 Permitted actions.95
7.3.2.21 Legal qualification.95
7.3.2.22 Creation .95
7.3.2.23 Last read access .95
7.3.2.24 Identity of the last modifier.95
7.3.2.25 Identity of the last reader .95
7.3.2.26 Recipient.96
7.3.2.27 Telematic file transfer version.96
7.3.3 Coding of the file content.96
7.3.3.1 Description file .96
7.3.3.2 Other file .96
7.3.4 Content of some specific files .96
7.3.4.1 Text file resulting of a T-DIRECTORY Request .96
7.3.4.2 File of group B and C.96
7.3.4.3 Coding of data intended for a standardised printer .97
7.3.4.3.1 Basic control codes .97
7.4 Coding of parameters for the telesoftware and printer device applications.99
7.4.1 User data in T-Access and in T-(Access) Response positive .99
7.4.2 User data in T-Directory .99
7.4.3 Designation in T-Directory.100
7.4.4 Designation in T-Load and T-Save.100
7.4.5 User data in T-Load, T-Save, T-Rename, T-Delete.100
8 D-protocol specification.
...