1、ETS 300 243-1 November 1995 Source: ETSI TC-TE Reference: DUTE-0201 5-1 ICs: 35.180, 33 Key words: PCI, APPLVCOM, facsimile, teletex, telex Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLIKOM for facsimile group 3, facsimile group 4, teletex and telex services Part I : CCITT
2、 Recommendation T.611 (1 992) modified ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: F-O6921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: s
3、ecretariatetsi.fr Tel.: +33 92 94 42 O0 - 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. Q European Telecommunications Standards Institute 1995. All ri
4、ghts reserved. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesETSI ETS*300*243 -II 95 3400855 !lob3384 bLO Page 2 ETS 300 243-1 : November 1995 Whilst every care has been taken in the preparation and publication of this document, errors in content,
5、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. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesPage 3 ETS 300 243
6、-1: November 1995 Transposition dates I Date of adoption of this ETS: 10 November 1995 Foreword Date of latest publication of new National Standard , or endorsement of this ETS (dople): This European Telecommunication Standard (ETS) was produced by the Terminal Equipment (TE) Technical Committee of
7、the European Telecommunications Standards Institute (ETSI). 1 Date of withdrawal of any conflicting National Standard (dow): 31 August 1996 This ETS comprises two parts: “Terminal Equipment (TE); Programming Communication Interface (PCI) APPLI/COM for facsimile group 3, facsimile group 4, teletex an
8、d telex services; Part 1: CCITT Recommendation T.611 (1992) modified, Part 2: Conformance testing“. Date of latest announcement of this ETS (doa): 29 February 1996 31 August 1996 Endorsement Notice CCITT Recommendation T.611 (1 992) 1 provides the technical description of the APPLICOM interface. The
9、 text of CCITT Recommendation T.611 (1992) l was approved by ETSI as an ETS with the agreed modifications as given below. NOTE: New or modified text is indicated using side bars. Normative references Part 1 of this ETS incorporates by dated or undated reference, provisions from an other publication.
10、 This normative reference is cited at the appropriate places in the text and the publication is listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this Part of the ETS only when incorporated in it by amendment or revision. For undated
11、references the latest edition of the publication referred to applies: CCITT Recommendation T.611 (1 992): “Programmable Communication Interface (PCI) APPLVCOM for facsimile group 3, facsimile group 4, teletex and telex services“. COPYRIGHT European Telecommunications Standards InstituteLicensed by I
12、nformation Handling ServicesETSI ETS*300*243 -L 95 m 3400855 O063386 493 Page 4 ETS 300 243-1: November 1995 Application guidelines and common modifications to CCITT Recommendation T.611 The following modifications define how CCITT Recommendation T.611 l shall be interpreted. Areas which may be ambi
13、guous are addressed and clarified. All remarks, references and comments are related to CCITT Recommendation T.611 l. 1) Delete the scope statement (clause 2) and insert the following: 2 Scope Part 1 of this European Telecommunication Standard (ETS) describes the high layer software interface APPLI/C
14、OM, located inside a teminal equipment between two logical entities, the Local Application (LA) and the Communication Application (CA). The technical description of the APPLVCOM interface is contained in CCITT Recommendation T.611 (1992) l. For the application of Pari 2, this ETS contains applicatio
15、n guidelines and amendments to be applied to CCITT Recommendation T.611 l to fulfil the requirements of ETS 300 243-2. 2) Page 1, clause 1, replace 3rd paragraph starting with “The APPLKOM interface can be used.“ by the following: The APPLVCOM interface can be used in communication equipment to give
16、 access to the facsimile group 3, facsimile group 4, teletex and telex services. The access to the telex services does not include the dialogue facility. 3) Page 1, subclause 1 .i, replace the headline “1 .i Normative References“ by: 1 .I informative references. 4) Page i, subclause 1.1, add the fol
17、lowing two informative references: - Recommendation F.59, General characteristics of the international telex service. - Recommendation F.60, Operational provisions for the international telex service. 5) Page 12, subclause 6.3.2, replace complete subclause, starting with “This section describes .“ b
18、y the following: This section describes the syntax of the ICE. The first syntax element in the ICE is always the APPLVCOM Header. No other elements, including SPACE and TABULATION format effectors are allowed before. Following are the CA-Descriptors. A CA-Descriptor is introduced by a single line co
19、ntaining a Yi (NUMBER SIGN) as first element. The detailed syntax is described in BNF-based grammar in annex A. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services- ETSI ETS*300*243 -1 75 m 3400855 O063387 32T “STD, “OPD“, “MD“, “CTL“, “DTM “ , “ B FT“
20、, “EDI“ Page 5 ETS 300 243-1: November 1995 Used only if the CA offers the Facsimile Group 4 sewice. In this case, in the minimum the value “STD“ shall be specified. Pages 13, 14, 15 and subclause 6.3.3, table 1, describing the ICE components shall be replaced by the text and tables shown below. The
21、se tables contain the same information as the table provided by CCITT Recommendation T.611 l with minor editorial corrections. However, the structure shown as follows makes their use more evident: Table 1 : CA-Descriptor information items independent of operating system or exchange mechanism Ke ord
22、APPLICOM CODING* COUNTRY L I 1 A I* (star) at the end of a keyword indicates that this keyword may be repeated. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services - ETSI ETS*300*243 -I 95 H 3400855 0063388 266 PRIVATE* Page 6 ETS 300 243-1: November 19
23、95 national administrations. (il supported keywords shall be listed). Provides the possibility for private extensions to the keyword Table 1 (concluded): CA-Descriptor information items independent of operating system or exchange mechanism SUBMIT* Parameter Recommendation. (All supported keywords sh
24、all be listed). Declares which functions are supported in the Submit TDD “PRINT“, keyword CONVCHK* PRINT* Interpretation Lists all the additional keywords supported by the CA. Only keywords classified as “+O in the TDD tables of clause 7 may be specified here. Provides the possibility for extensions
25、 to the Recommendation. Can only be implemented as formal changes to the Recommendation. All the CA-supported keywords shall be listed. Provides the possibility for national extensions to the Recommendation. Can onlv be imdemented with the ariDroval of “CONVERT“, “CHECK req ui red. Convert-ID Print-
26、ID function. This keyword shall be repeated as many times as Declares which transfer formats are supported in the Submit TDD function CONVERT and/or CHECK. Declares which printers could be addressed by the CA in the string keyword, integer “MSDOS“, “WINDOWS“, “UNIX, “OS2“, “MacOS“ Submit TDD functio
27、n PRINT. Specifies the additional code pages for the extended ASCII character sets the CA supports. String indicates the number of the code page (e.g. “850). Gives the complete list of CA-Record field names supported by the CA, in the order they are found in the file resulting from the TRACE:COPY fu
28、nction. The CA shall state the keyword followed by - and separated by comma - the length the field will have in the resulting file. This keyword specifies the operating environment of the CA. If a CA supports several environments, the ICE shall contain as many ENVIRON keyword instances as the number
29、 of different operating systems supported. Keyword Parameter Ilyes“ I Ilno“ SYNC Interpretation Indicates whether the CA is sync-driven“. See annex E for further Table la: CA-Descriptor information items applying for the file exchange mechanism ,Path ,Path details. ISpecifies the path of the TDD req
30、uest files. See annex E for further F-JOB-Q IPath details. Specifies the path of the TDD response files. See annex E for further details. Specifies the path of the TDD response files relating to errors. See annex E for further details. - I Keyword Parameter ALARM “yes“ I “no“ I Interpretation States
31、 whether the CA supports the SetAlam function. IERROR-Q Table 1 b: CA-Descriptor information items applying to the primitive exchange mechanism, any operating system COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesTable 1 c: CA-Descriptor information
32、 items applying to the primitive exchange mechanism, MSIDOS operating system Parameter hex,hex 3, “yes“ I “no“ Path Ilyes“ I Ilno“ Path “yes“ 1 “no“ String String String Keyword I Parameter I Interpretation DRIVER IPath IName of the driver that shall be opened to initiate dialogues with Interpretati
33、on Indicates the interrupt number. Two hexadecimal numbers; the first specifies the multiplex number, the second the program code number. If the interrupt is not multiplexed, then the second hex number shall not be specified. CA is a static library (LA shall be linked to it). Path) of the library(ie
34、s) (used in conjunction with the LIB keyword). Dynamic Link Library. See annex E. The DLL-NAME keyword shal be supported only if the DLL exchange mechanism is supported. Path) of the DLL file) (used in conjunction with the DLL keyword). Dynamic Data Exchange mechanism. In the WINDOWS environment if
35、the application supports the DDE exchange mechanism, it shall specify “yes“. See annex E. The next three keywords shall be included in the ICE if the DDE mechanism is used. Application Name (MsDos format) XXXXXXXX.XXX. All CA “Subjects“ shall be mentioned (if any) otherwise leave emptl (to be used w
36、ith the DDE keyword). All CA “Items“ shall be mentioned (if any) otherwise leave empty (to be used with the DDE keyword). Ithe CA. See annex E for further details. (Indicates the interrupt number. Two hexadecimal numbers: the first - I NT I hex, hex *) Keyword 1 Parameter specifies the multiplex num
37、ber, the second the program code number. If the interruot is not multiolexed, then the second hex Interpretation number shall not be specified. CA is a static library (LA shall be linked to it). Path) of the library(ies) (used in conjunction with the LIB LIB LIB-NAME* Path “yes“ I “no“ I keyword). T
38、able 1 d: CA-Descriptor information items applying to the primitive exchange mechanism, WINDOWS system Ke ord LIB LIB-NAME* DLL DLL-NAME* r Table 1 e: CA-Descriptor information items applying to the primitive exchange mechanism, OS12 operating system Table if: CA-Descriptor information items applyin
39、g to the primitive exchange mechanism, UNIX operating system Keyword I Parameter I Interpretation For Further Studv 2, Note that the syntax has changed from the original .e. the original syntax stated “hex-hex“, and it reads “hex,hef now. Note that the syntax has changed from the original .e. the or
40、iginal syntax stated “hex-hex“, and it reads “hex,hef now. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services- - ETSI ETS*300*243 -1 95 3400855 O063390 9LY = Page 8 ETS 300 243-1: November 1995 1 I Table lg: CA-Descriptor information items applying to
41、the primitive exchange mechanism, MacOS operating system Keyword I Parameter Interpretation For Further Studv 7) Page 19, subclause 7.4.1, Ist paragraph, add the following text just in front of last sentence (“For clarification purposes .I) of the 1st paragraph: If an LA wants to send to a list of r
42、ecipients it shall use the SEND functionality (using the ADDRLIST keyword. The transmission status is not available through this function (there is no Response-TDD generated). However, the status of the transmission can be obtained using the TRACE functionality (see subclause 7.4.3). The TRACE funct
43、ionality is available through CAS conforming to functional class B (FCB). NOTE: 8) Page 19, subclause 7.4.1, 2nd paragraph, add following text to the end of the 2nd paragraph: So, whenever the Response-TDD is available, the LA can relay definitely on contents of the status parameter showing the resu
44、lt of the transmission. The status parameter will indicate the following (see also table 21lT.611 i I): document successfully and completely transmitted; transmission failed, all attempts to transmit are given up by CA; transmission partially failed, parts are already transmitted, but no complete tr
45、ansmission could be achieved!. ie+n II II #+_#I 9) Page 21, subclause 7.4.1, table 6lT.611 1, Keyword “TYPE“, in the “Type“ column of the keyword “TYPE“ change “o“ to ce, because the “TYPE“ keyword shall only be used, if the “FILENAME“ keyword is used too. Add the following text in the “Comment“ col
46、umn of the keyword “TYPE“: Applicable only if the Filename keyword is used. It specifies the document type to be sent (see subclause 7.5.2). Condition: Only one single file to send. 10) Page 23, subclause 7.4.1, table 6/T.611 I, Keyword “T61OPTSe, in the “type“ column of the keyword “T61OPTS“ change
47、 “o“ to ce, because the “T61OPTS“ keyword shall only be used, if the “FILENAME“ keyword is used too. Replace the last sentence in the Comment column of the keyword “T61OPTSe, reading “See annex 1 for syntax“ by following text: The syntax of the TGloptions parameter is for further study (annex I). 11
48、) Page 25, subclause 7.4.1, table 7lT.611 l, Keyword “TYPE“, in the “Type“ column of the keyword “TYPE“ change “o“ to “c“, because the “TYPE“ keyword shall only be used, if the “FILENAME“ keyword is used too. Add following text in the “Comment“ column of the keyword “TYPE“: Applicable only if the Fi
49、lename keyword is used. It specifies the document type to be sent (see subclause 7.5.2). Condition: Only one single file to send. 12) Page 26, subclause 7.4.1, table 7/T.611 l, Keyword “ADDRLIST“, the “service applicability“ column of the keyword “ADDRLIST“ shall indicate applicability for all services. 13) Page 26, subclause 7.4.1, table 7lT.611 l, Keyword “T61OPTS“, add the following text at the end of the last sentence in the “Comment“ column of the keyword “T61 OPTS“: The syntax of the T61 options parameter is for further s
