SIST ETS 300 383 E1:2003

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

1. Produce an ETS which has to cover the following items; 1.1 Selection of lower layer protocols parameters 1.2 Selection of parameters carried by lower layer protocols (eg code points for HLC, LLC, ...) in liaison with SPS5. // 1.3 Selection of facilities offered by the file transfer protocol describ in ETS 300 075 and EN 41216 (ISP 10607)  Simple FTAM . Selection of the appropriate parameter values with the aim to have an option free kernel protocol. // 2. Provide further requirements and coordination for other related Teams ( API for File Transfer over ISDN  and  Conformance test for File Transfer over ISDN ).

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

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• 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/1
• Ref Project: ETSI ETS 300 383 ed.1 (1995-01) - Integrated Services Digital Network (ISDN); File transfer over the ISDN EUROFILE transfer profile

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
STANDARD
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: [e-mail].: [phone] - Fax: [phone]Copyright 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.157.2.1.1Connection.157.2.1.2End-to-end protocol.157.2.1.3Association.167.2.1.4Access.167.2.1.5Abort and release.177.2.1.6End of data exchange and hang-up.177.2.1.7Access regime.177.2.2Information exchanged between the service and the user.197.2.2.1Data supplied to the users.197.2.2.2Error codes.197.3Functions for files operations.207.3.1Working area.207.3.2Local files operations.207.3.3Files administration.217.3.3.1Local files.217.3.3.2Incoming files.217.3.3.3Remote files.227.3.4Remote file lists.227.3.5Navigation.227.3.5.1Definition of filestores.227.3.5.2Definition of working areas.237.3.5.3Available functions in the navigation facility.237.3.5.4Use of commands.267.3.5.5Reserved names.267.3.5.5.1Reserved file names.267.3.5.5.2Content of a reserved file.277.3.6Recovery mechanism.277.4Functions for management.277.4.1LogBooks.277.4.1.1Administration.277.4.1.2Content.277.4.2Correspondent PhoneBook and Access Control List.287.4.2.1Administration.287.4.2.2Content.28SIST ETS 300 383 E1:2003

Page 4ETS 300 383: January 19957.4.3Configuration.297.4.3.1Administration.297.4.3.2Static configuration.297.4.3.3Dynamic 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 4.1.4.8).mnemonic: 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 4.1.2.4.2).This 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 assumed to have acorrect syntax).7.1.5Management functionsA user shall have access, at least when there is no communication in progress, to the following functions:-the Configuration function shall be accessible at least to read the network parameters andprotocol parameters;-the Logbook function shall be accessible at least to read the trace of any communication event orany communication incident;-the Correspondent PhoneBook function shall be accessible for management (Create, Modify orDelete a correspondent) and shall provide characteristics of correspondents to be called (NetworkAddress and optionally local working filestore);-the Access Control List function shall be accessible for management (Create, Modify or Deletean identifier), and shall provide characteristics and functions of correspondent accepted as callers(Identifier, authorizations granted, mandatory working area and, if necessary, navigation workingarea).7.2Use of the regimes7.2.1Phases and rules of a communication sessionThis subclause describes the use of the regimes (as defined in ETS 300 075 [1]) to establish acommunication session.The EUROFILE service shall provide a mechanism to automatically process the appropriate exchanges toestablish an access regime by means of the connection and start of data exchange (see ETS 300 079 [2],subclauses 7.2.1, 7.2.2 and 7.3.3) and association and access TDUs (see ETS 300 075 [1]).If the automatic communication is a supported service, the application shall provide a mechanism toprocess automatically the appropriate exchanges to establish an access regime, use the needed fileservices and release the communication.These mechanisms shall use the information available in the Correspondent PhoneBook.7.2.1.1ConnectionIn order to establish a communication, the user calls a correspondent.The address of the correspondent (ISDN number and, where appropriate, sub-address) can be supplieddirectly, or indirectly, by the Correspondent PhoneBook.The caller terminal shall issue a SBV_Establish_Request (see ETS 300 079 [2], subclause 7.2.1), thecalled terminal receives a SBV_Establish_Indication.The caller terminal remains waiting for an SBV_Establish_Response, as long as the inactivity timeout hasnot run out.An answer to a SBV_Establish_Indication shall always be provided.An application selection criteria, during an interim period based only on user data, shall be provided asdescribed in annex A. Additional selection mechanisms may also be provided.7.2.1.2End-to-end protocolThe caller terminal shall issue a SBV_TPD_BEGIN_Request, the called terminal receives aSBV_TPD_BEGIN_Indication (see clause 9 of this ETS).SIST ETS 300 383 E1:2003

Page 16ETS 300 383: January 19957.2.1.3AssociationThe user can choose whether or not to identify himself to his correspondent. The transmission of anidentifier shall not be mandatory.The identifier consists of two keywords, the name and the password. The identifier may be supplieddirectly or take an optional default value. Both may be allocated to a user in advance and then be usedlater on during the communications between the caller and the called party correspondents.This identifier is used by the called party to accept or refuse incoming calls. This enables a user to makeuse of his own capabilities over a called party from any terminal.a)Use of identifier by the callerThe caller may supply his name, password or both at the start of the call.If the identifier is not transmitted during the call or not listed in the remote Access Control List, thecaller shall not be identified.The user may enter a name and a password: these given values shall be used for requesting theassociation regime instead of any default values.b)Use of identifier by the called terminalWhen an association request is received, the called party may accept or refuse the associationdepending on the identifier received.It shall be the responsibility of the application to define the access entitlements to file functionsassociated with a caller not identified (unknown identifier or no identifier).If the Access Control List does not grant entitlement (no entitlements to file functions) to callers whohave not been identified, the received identifier shall not be accepted, that is to say the call shallnot be accepted.A refusal on the grounds of an unaccepted identifier shall produce a negative response to the callerrequest and the cause shall be indicated ("identifier rejected"). The caller application shall thenproceed with the release of the communication or with another association request. If connectionrelease does not follow the negative response, the called party and the caller application shallprovide a mechanism to allow a maximum number of retries of the association request.c)Use of application nameThe application name used in EUROFILE shall be coded "!K".If the remote entity refuses the application name because of an "unknown application name", afallback mode may be used. This mode is outside the scope of this ETS.d)Use of Calling Address and Called AddressThe use of this data is private. However, it should not result in reactions that are contrary to theEUROFILE specifications.7.2.1.4AccessThe identifier supplied by the caller shall be used by the called party to define access entitlements to filefunctions.The caller shall be informed about the functions which are available.The identifier shall be used to define, locally, the remote filestore available to the caller.SIST ETS 300 383 E1:2003

Page 17ETS 300 383: January 1995For all accepted calls, a minimum function shall be provided, that is at least one of the basic functionssuch as file save, file load or the access of the file list.In addition, the message function may be provided.If the file delete, file rename or message functions do not exist in the called party, the called party shallexplicitly indicate in the response that these functions as not available.This access phase may be used to indicate the capabilities of the caller and the called party.7.2.1.5Abort and releaseThis phase covers the cleardown of the access regime and the end of the association regime.This phase is accessible through the communication abort function.The normal and abnormal termination of the association regime shall cause the end of the data exchangein transparent mode using SBV_TPD_End or the re-use of the association regime if the user is theinitiator.Whatever the called party, or caller mode, the end of the inactivity time-out shall be indicated by thetransmission of a T-Abort caused by "delay expired".7.2.1.6End of data exchange and hang-upThis phase covers the end of the data exchange regime and the release of the communication describedin ETS 300 079 [2].This phase is accessible through the communication abort function.The normal and abnormal termination of the data exchange regime shall cause the end of thecommunication using SBV_Release or the re-use of the data exchange regime if the user is the initiator.7.2.1.7Access regimeThe functions not provided by the called party shall be explicitly inhibited to the caller who shall not, underany circumstances, be able to activate them at the user interface level.The interrupt of a current transfer by the user shall result in a file transfer abort and the return of the "userabort" indication. This interrupt shall not affect the call or the following transfers in the case of a multiplerequest.The functions provided by the master and the slave are:a)File Transfer AbortAt any time during a file transfer operation (transmitting or receiving), the master and, optionally, theslave shall be able to interrupt the operation. This interrupt has no effect either on thecommunication or on the following transfers in case of a multiple request.b)Communication abortA user shall be able to interrupt a call at any time. If an operation is underway, a confirm requestindication is displayed. The confirmation interrupts the current function and terminates theestablished call.If the communication is interrupted during the transfer phase, the file transfer is aborted and a "userabort" indication shall be displayed. The application shall then continue with the connection releasefunction.SIST ETS 300 383 E1:2003

Page 18ETS 300 383: January 1995c)MessageThis function is optional. If supported, the message function shall be possible during the accessregime.The functions provided by the master, and only accessible to the master, are based on file functions.The files are accessible through their transfer names.Multiple requests on files as formulated by the user (i.e. Save or Load or Rename or Delete several files)shall be managed automatically. The transfer primitives are still carried out on a file-by-file basis.An incident on one of the files concerned by the request shall not require user intervention to continue theoperation.The following functions are also subject to authorization by the remote correspondent:1)Save one or more files (single or multiple requests)The transfer name(s) shall be selected from the list of files in the local filestore or shall be enteredby the user.A save request for which the transfer name already exists in the receiving entity shall be refused bythe receiving entity if the dynamic configuration parameter "Overlay existing files" is set to NO.Otherwise the request shall be accepted (the existing file may already have been stored underanother transfer name).2)List the names of remote filesThe funtion allows the files from the remote filestore or a subset of the remote filestore to berequested.The criteria for the selection of this subset shall be available to the user. The syntax is unrestrictedat the user interface level; the syntax transmitted online shall comply with ETS 300 075 [1](subclause 5.7).Incoming data shall be displayed and contain at least the transfer name and the file size. As anoptional function, if accepted by the remote peer entity, this data shall be more detailed within anextended directory function.3)Load one or more remote files (single or multiple requests)The transfer name(s) shall be selected from the list received in response to the file list request orshall be entered by the user: both options shall be available.4)Delete one or more remote files (single or multiple requests)The transfer name(s) shall be selected from the list received in response to the file list request orshall be entered by the user: both options shall be available.5)Rename one or more remote files (single or multiple requests)The original transfer name(s) shall be selected from the list received in response to the file listrequest or shall be entered by the user: both options shall be available.The new names shall be entered by the user.A Rename request containing a new transfer name that already exists in the receiver shall berefused if the dynamic configuration parameter "Overlay existing files" is set to NO, otherwise therequest shall be accepted.SIST ETS 300 383 E1:2003

Page 19ETS 300 383: January 19957.2.2Information exchanged between the service and the user7.2.2.1Data supplied to the usersThis data shall be displayed automatically without user intervention.The display may be masked temporarily, especially, in the automatic mode. In this case, a user action isrequired to reveal the information.a)Display of a confirm requestIf the user breaks an established communication, the initiator of the break shall provide a confirmrequest indication.b)Display of the current status of exchangesThe current status of exchanges shall be displayed whatever the call status is.The current status covers the following:-call status: established call, current call, end of call, no current call;-the name of the caller supplied by its identifier;-the current operation, at least for file transmissions.c)Display of file transfer operationsThe current file transfer operation shall be displayed in the established call status during the actualfile transfer.It enables the user to estimate the duration of the transfer.d)Indication of inactivity on an established communicationA user indication shall be provided if the inactivity time-out runs out.e)Result code for operations completed successfullyThe user may be informed of the success of the operation requested.f)Indication of incidentsRefusals from the remote entity, transfer aborts by the remote entity, transfer aborts for anyreasons, end-of-call at the initiative of the remote correspondent, local incidents (e.g. file accessproblems), end-of-call as a result of inactivity time-outs, end-of-call due to others reasons (protocolerrors, network failure, etc.) shall be indicated to the local user.g)Display of incoming messagesThe display of incoming messages shall not affect the other operations.7.2.2.2Error codesThe error codes used online are those defined in subclause 7.2 of ETS 300 075 [1] to which are addedother codes at the application level in order to give users the greatest possible amount of detailedinformation.These additional codes are:-"identifier rejected";-"disk full";-"file access impossible";-"user interrupt of communication";SIST ETS 300 383 E1:2003

Page 20ETS 300 383: January 1995-"user abort";-"extended format not available";-"log access impossible";-"compression format not supported";-"incorrect recovery FCS";-"coding error in compressed data".7.3Functions for files operations7.3.1Working areaThe transfer operations are carried out between two filestores, the remote filestore and the local filestore.When the slave accepts to setup an access regime, it shall offer a working area to the master. Thisworking area contains the mandatory remote filestore.The remote filestore, accessible to a given caller, contains the files offered by the called party to the caller.The remote filestore is defined in the Access Control List of the called terminal.By default the local filestore corresponds to the caller's entire working area, otherwise the local filestore isdefined in the Correspondent PhoneBook of called parties.Files are described in each of the two filestores by a single name, the transfer name, which isindependent of the local file management systems.File operations are carried out, either in accordance with the mandatory working area, or in accordancewith an optional service, the navigation facility.If the navigation facility is not used, the caller has no knowledge of the structure of the remote workingarea.If navigation facility is used, it is possible to take into account the structure of the remote working area.By default, the facilities to access remote files shall not require navigation.The facilities "list", "load", "delete", "rename" shall then apply to the mandatory remote filestore but thestructure of the remote working area remains transparent.Consequently, users of the "save" service do not know the exact storage location of the transmitted filestored in the remote filestore.As an optional feature, and if the remote correspondent agrees to this type of system operati
...