Integrated Services Digital Network (ISDN); File transfer over the ISDN EUROFILE transfer profile


Digitalno omrežje z integriranimi storitvami (ISDN) – Prenos datotek prek profila za prenos datotek ISDN EUROFILE

General Information

Publication Date
Current Stage
12 - Completion
Due Date
Completion Date

Buy Standard

ETS 300 383 E1:2003
English language
56 pages
sale 10% off
sale 10% off
e-Library read for
1 day

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) – Prenos datotek prek profila za prenos datotek ISDN EUROFILEIntegrated Services Digital Network (ISDN); File transfer over the ISDN EUROFILE transfer profile33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 383 Edition 1SIST ETS 300 383 E1:2003en01-december-2003SIST ETS 300 383 E1:2003SLOVENSKI

SIST ETS 300 383 E1:2003

EUROPEANETS 300 383TELECOMMUNICATIONJanuary 1995STANDARDSource: ETSI TC-TEReference: DE/TE-01042-1ICS:33.080Key words:ISDN, file transferIntegrated Services Digital Network (ISDN);File transfer over the ISDNEUROFILE transfer profileETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1995. All rights reserved.SIST ETS 300 383 E1:2003

Page 2ETS 300 383: January 1995Whilst 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.SIST ETS 300 383 E1:2003

Page 3ETS 300 383: January 1995ContentsForeword.71Scope.92Normative references.93Definitions.104Abbreviations.115Overview.116Configurations.117EUROFILE transfer teleservice.127.1General.127.1.1General functions provided.127.1.2Functions available in the interactive communication mode.137.1.3Functions available in the automatic communication mode.147.1.4File functions.147.1.5Management functions.157.2Use of the regimes.157.2.1Phases and rules of a communication session. protocol. and release. of data exchange and hang-up. regime.177.2.2Information exchanged between the service and the user. supplied to the users. codes.197.3Functions for files operations.207.3.1Working area.207.3.2Local files operations.207.3.3Files administration. files. files. files.227.3.4Remote file lists.227.3.5Navigation. of filestores. of working areas. functions in the navigation facility. of commands. names. file names. of a reserved file.277.3.6Recovery mechanism.277.4Functions for management.277.4.1LogBooks. PhoneBook and Access Control List. ETS 300 383 E1:2003

Page 4ETS 300 383: January 19957.4.3Configuration. configuration. configuration.298Encoding.308.1Use and encoding of TDUs.308.1.1Association.308.1.1.1T-Associate Request.308.1.1.2T-Response-positive.318.1.1.3T-Response-negative.328.1.2Access regime.328.1.2.1T-Access Request.328.1.2.2T-Response-positive.338.1.2.3T-Response-negative.358.1.3Save-Load-Directory-Delete-Rename.358.1.3.1T-Save.358.1.3.2T-Load.368.1.3.3T-Directory.368.1.3.4T-Delete.378.1.3.5T-Rename.378.1.3.6T-Response-positive.378.1.3.7T-Response-negative.378.1.4Typed Data.378.1.4.1T-Typed-data.378.1.5File transfer.378.1.5.1T-Write.378.1.5.2T-Response-positive.388.1.5.3T-Response-negative.388.1.6Transfer Abort.388.1.6.1T-Transfer-reject.388.1.7Exception.388.1.7.1T-P-Exception.388.1.8End of Access.398.1.8.1T-End-Access.398.1.8.2T-Response-positive.398.1.9Termination.398.1.9.1T-Release.398.1.9.2T-Response-positive.398.1.10Abort.398.1.10.1T-Abort.398.2Description of the files structures.398.2.1Files.398.2.2File lists.418.2.2.1Simple directory.418.2.2.2Extended directory.418.2.3Navigation facility.428.2.3.1Format of filestore list and sub-list.428.2.3.2Format of the file containing the name of the currentfilestore.438.2.3.3Format of the filestore selection file.438.2.4Presentation files.438.3Error codes.439End-to-end protocol.4310Application rules for lower layer protocols for EUROFILE Transfer over ISDN.4410.1General overview of ETS 300 080 application for EUROFILE Transfer.4410.1.1General.4410.1.2Layer 1 and D-channel protocols.4410.1.3B-Channel Protocols.4510.2Additional application rules specific for EUROFILE transfer.4610.2.1Protocol pillars (subclause 4.1).46SIST ETS 300 383 E1:2003

Page 5ETS 300 383: January 199510.2.2Terminal Selection and Compatibility checking (subclause 7.2).4610.2.3Service specific use of supplementary services (subclause 7.3 ).4610.2.4Specific rules for base protocol CCITT Recommendation X.75 (subclause8.1.3).4610.2.5Specific rules for base protocol ISO 7776 (subclause 8.1.4).4710.2.6B-channel layer 3 (subclause 8.2).48Annex A (normative):Application selection criteria for EUROFILE transfer applications.49Annex B (informative):Recommended combinations of parameter values to insure optimumthroughput.50Annex C (informative):Examples of operation in navigation facility.51Annex D (normative):Enhancements.54D.1Description on transfer names and physical names.54D.2Signatures.54D.3Private extensions of the navigation facility.55History.56SIST ETS 300 383 E1:2003

Page 6ETS 300 383: January 1995Blank pageSIST ETS 300 383 E1:2003

Page 7ETS 300 383: January 1995ForewordThis European Telecommunication Standard (ETS) was produced by the Terminal Equipment (TE)Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS aims to meet the urgent need for a standardized simple file transfer protocol as expressed bythe European ISDN Users Forum (EUIF), ISDN MOU Implementation and Management Group (IMIMG)and the ISDN Management and Co-ordination Committee (IMCC).Proposed transposition datesDate of latest announcement of this ETS (doa):31 March 1995Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 September 1995Date of withdrawal of any conflicting National Standard (dow):30 September 1995SIST ETS 300 383 E1:2003

Page 8ETS 300 383: January 1995Blank pageSIST ETS 300 383 E1:2003

Page 9ETS 300 383: January 19951ScopeThis ETS specifies the usage of all protocols and supplementary services for file transfer based onETS 300 075 [1] over the ISDN (which within this ETS is identified as EUROFILE).The purpose of this ETS is to select the facilities offered by the ETS 300 075 [1] file transfer andETS 300 079 [2] end-to-end protocol, to provide requirements for Correspondent PhoneBook, LogBooksand services facilities offered to the user and to select the lower layers protocols parameters offered byETS 300 080 [3].2Normative referencesThis ETS incorporates by dated or undated reference, provision from other publication. These normativereferences are cited at the appropriate places in the text and the publications are listed hereafter. Fordated references, subsequent amendments to or revision of any of these publications apply to thisETS only when incorporated in it by amendment or revision. For undated references the latest edition ofthe publication referred to applies.[1]ETS 300 075: "Terminal Equipment (TE); Processable data, File transfer".[2]ETS 300 079 (1991): "Integrated Services Digital Network (ISDN); Syntax-basedvideotex, End-to-end protocols, circuit mode DTE-DTE".[3]ETS 300 080 (1992): "Integrated Services Digital Network (ISDN); ISDN lowerlayer protocols for telematic terminals".[4]ISO/IEC 8073 (X.224): "Information technology - Telecommunications andinformation exchange between systems - Open Systems Interconnection -Protocol for providing the connection-mode transport service".[5]ISO/IEC 8208 (1990): "Information technology - Data communications - X.25Packet Layer Protocol for Data Terminal Equipment".[6]ISO 7776 (1986): "Information processing systems - Data communications -High-level data link control - Description of the X25 LAPB - compatible DTE datalink procedures".[7]CCITT Recommendation X.75 (1984): "Packet switched signalling systembetween public networks providing data transmission services".[8]CCITT Recommendation T.70 (1988): "Network independent basic transportservice for the telematic services".[9]CCITT Recommendation T.90 (1988): "Characteristics and protocols forterminals for telematic services in ISDN".[10]ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN);User-network interface layer 3, Specifications for basic call control".[11]CCITT Recommendation T.51 (1988): "Coded character sets for telematicservices".[12]prETS 300 409: "Integrated Services Digital Network (ISDN); Eurofile transferteleservice, Service description".[13]CCITT Recommendation V.42 bis (1990): "Data compression procedures fordata circuiT-terminating equipment (DCE) using error correcting procedures".[14]ETS 300 196-1, A1: "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".SIST ETS 300 383 E1:2003

Page 10ETS 300 383: January 19953DefinitionsFor the purposes of this ETS, the following definitions apply:Access Control List: List which consists of the rights of each caller (list of file operations offered anddefinition base accessible to the caller).address: Data used to identify a user. The address consists of an ISDN number and, where appropriate,a sub-address.base: Work space that contains the files available for use to the remote or local user.called party: The party which should wait for calls and operations. It has a passive role and acts as aslave.caller: The party which is the initiator of the call. It has an active role and is the master compared to theremote terminal. It inputs the requests for actions on files.Correspondent PhoneBook: List which consists of the address and local base (optional) of every calledterminal.dynamic configuration: ProducT-level configuration which is accessible to the user.EUROFILE: The teleservice whose technical description is given in this ETS.extended directory: List of file names with detailed information for each file.file operations: The options available to users as regards file transfer, i.e. Save file, Consult list of filenames, Load file, Delete file, Rename file.identifier: User identification (name and, where appropriate, password) which can be supplied during thecall in order to indicate entitlements with regard to operations on files.local files: Files from the local user.LogBook: Record of communications.message: Information transmitted from the user of the application transfer service with the T-Typed-dataTelesoftware Data Unit (TDU) (see ETS 300 075 [1], subclause Indication which provides access points for a list of names (Correspondent, Identifier,.).Mandatory coded parameter (Mand.cod.): ETS 300 075 [1] parameters which are mandatory in theTDU primitive.Mandatory parameter (Mand.): EUROFILE parameter which is mandatory.navigation: Facility with capability to manage the change of filestore of the remote terminal.Optionally coded parameter (Opt.cod.): ETS 300 075 [1] parameters which are optional in the TDUprimitive.Optional parameter (Opt.): EUROFILE parameter which is optional.product signature: Confidential data which can be exchanged by products during the call phase.SIST ETS 300 383 E1:2003

Page 11ETS 300 383: January 1995regime: A set of protocol phases; a regime is a continuous period of time. A regime is established byusing a confirmed or optionally confirmed service and it is orderly terminated using a confirmed service, itmay also be interrupted in an abnormal manner. A regime is fully defined by specifying the service(s) usedto establish it and the service (s) used to terminate it. A regime is used in this description to limit the rangeof some services which may only be available during a particular regime.remote files: Files from the correspondent.single base facility: Mandatory facility, working on a single filestore of the remote terminal.single directory: List of file names in ETS 300 075 [1] format.static configuration: Configuration of the network connection parameters and ETS 300 075 [1]parameters.transfer name: File name that is unique and not dependent on local file management systems.4AbbreviationsFor the purposes of this ETS, the following abbreviations apply:DUData UnitEIUFEuropean ISDN Users ForumFCSFile Check SumFTAMFile Transfer Access & ManagementIMCCISDN Management and Co-ordination CommitteeIMIMGISDN MOU Implementation and Management GroupImpl.Implicity coded parameterISDNIntegrated Services Digital NetworkLANLocal Area NetworkMand.Mandatory parameterMand. Cod.Mandatory Coded parameterOpt.Optional parameterOpt. Cod.Optionally Coded parameterTDUTelesoftware Data UnitTETerminal Equipment5OverviewThe main purposes of this ETS are as follows:-to define a standard file exchange service operating on ISDN;-to specify end-to-end compatibility between terminals supporting such a service;-to recommend minimum user interface common features so that users can adapt more easily toproducts from different manufacturers;-to minimize the difficulties inherent to configurations so that users can access products that areeasy to install and use.6ConfigurationsThe EUROFILE profile takes into account different types of terminals:-non-dedicated EUROFILE terminals (e.g. personal computer based multiservice terminals);-file servers;-multi-user system or multi access systems (e.g. Local Area Network (LAN)).SIST ETS 300 383 E1:2003

Page 12ETS 300 383: January 19957EUROFILE transfer teleservice7.1GeneralThe service specified by this ETS is called EUROFILE.EUROFILE is an ISDN teleservice, in which end-to-end compatibility between terminals is guaranteed andwhich supports file exchanges between different types of equipment.End-to-end compatibility is one of the major objectives for EUROFILE.Files are exchanged over one single B-channel at a rate of 64 kbit/s.The dialogue between the two systems is based on the following ETSs:-ETS 300 080 [3] (relating to the use of lower layers protocols);-ETS 300 079 [2] (end-to-end protocol);-ETS 300 075 [1] (Data file transfer).This ETS specifies the profile of these ETSs and indicates the parameter choices that shall be made forthe EUROFILE protocol and encoding system.The rules applicable to the files shall follow those defined for the transferable files of telesoftwareapplication in ETS 300 075 [1].NOTE:The files have common rules for the naming as they are accessed by their transfername, which is unique. This provides file independence compared with the various filemanagement systems available and enables different file management systems tounderstand each other.The lower layer configuration is defined in such a way that interoperability is provided between the twosystems without configuration adjustment.7.1.1General functions providedThe mandatory specificationned in this ETS define the minimum service which shall be provided by anyproduct which claims to be a EUROFILE prs contaioduct (see NOTE).EUROFILE provides a service for interactive communications and an optional minimum set offunctions for automatic communications.The file functions implemented during a connection between two users are based on three basicfunctions, i.e. file save, the file lists (both remote and local), and file load and include, optionally, a filedelete function and file rename function (both remote and local).EUROFILE also covers the definition of Management functions such as Configuration, an AccessControl List, a Correspondent PhoneBook and a LogBook.SIST ETS 300 383 E1:2003

Page 13ETS 300 383: January 1995 File Func.
LoadSaveNavigationDeleteRenameInteractiveTerminalRulesAutomatic TerminalRulesLogBookCorresp. PhoneBookAccess Control ListConfigurationMANAGEMENT FUNCTIONSFILE SERVICESCOMMUNICATION MODERemote operationsLocal operationsListDeleteRenameOptional facilities and functions are in italic.Figure 1: EUROFILE minimum servicesAs a default service, any incoming call shall always be reported to, and handled by, the application.Incoming calls may be refused or accepted according to the configuration and the exchanges in progress.The EUROFILE application, in particular, shall always accept or reject calls once the communication is inprogress. An answer to an incoming call (SBV_Establish_Indication of ETS 300 079 [2]) shall always beprovided.NOTE:However, EUROFILE products may also provide additional functions compliant withETS 300 075 [1]. Such additional functions are outside the scope of this ETS.7.1.2Functions available in the interactive communication modeA call is established between two end systems, one operating as a caller and the other as a called party.The interactive communication mode requires, on the caller side, the presence of the user.The called party does not necessarily require the user to be present.The caller shall establish the call. It has an active role, i.e. it acts as the master. The caller is the onewho requests file functions.The called party is waiting for calls and file functions. It has a passive role, i.e. it acts as the slave.The Master has access, as an initiator, to the following file functions:-save, load, list and (optionally) delete, rename;and also to the following functions:-file transfer abort, communication abort and (optionally) navigation, message.The slave has access, as an initiator, to the following functions:-file transfer abort, communication abort and (optionally) message.SIST ETS 300 383 E1:2003

Page 14ETS 300 383: January 19957.1.3Functions available in the automatic communication modeWithin this mode the caller shall communicate automatically and shall not require the presence of theuser.Terminals supporting this mode shall also support the recovery mechanism (see ETS 300 075 [1],subclause mode shall be used to define a complete communication session in advance.Automatic communication mode allows the manipulation (i.e. Create and Delete.) of automatic sessions.An automatic session contains:-a list of correspondents;-a list of functions (save, load, file list) and the associated files (files being selected withcriteria to select a subset of the filestore);-a date and time of execution (relative or real).The other Delete File and Rename File functions are optional.The automatic sessions may be initiated immediately or at a later time.The service shall provide an optional presentation file associated with the files transmitted to provideinformation on the files (Group B file as defined in the telesoftware application by ETS 300 075 [1]).Presentation files associated with the files loaded or saved, if used, and the service for consultation ofthese files, shall be used to add presentation information to these files.Specific mechanisms shall be included in the application to recover from failure or incident during anoperation or a call. These mechanisms shall be described in the configuration files as:-maximum number of possible retries for an unsuccessful communication session;-maximum number of possible retries for an unsuccessful call;-delay between two retries;-use of Recovery;-date and time of execution.This list is not exhaustive.These events shall not block the operation, for any reason.7.1.4File functionsThe file functions shall be accessible when the access regime is established (see ETS 300 075 [1]).The minimum basic file functions between a caller and a called party which shall be supported are:-save a file;-access to the remote simple file directory;-load a file;-file transfer abort;-access to the local list of files.Optionally, the file functions supported are:-delete a remote file;-rename a remote file;-navigation commands;-access to an extended file directory, which contains detailed data relating to the files;-delete a local file;-rename a local file.SIST ETS 300 383 E1:2003

Page 15ETS 300 383: January 1995NOTE:When a file is accepted by the remote peer entity, the service contents are alsoassumed to be accepted (e.g. a simple directory file accepted is

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.