ITU-T T 521-1994 Communication Application Profile BT0 for Document Bulk Transfer Based on the Session Service - Terminals for Telematic Services Amendment 1 (Study Group 8) 27 pp《.pdf

《ITU-T T 521-1994 Communication Application Profile BT0 for Document Bulk Transfer Based on the Session Service - Terminals for Telematic Services Amendment 1 (Study Group 8) 27 pp《.pdf》由会员分享，可在线阅读，更多相关《ITU-T T 521-1994 Communication Application Profile BT0 for Document Bulk Transfer Based on the Session Service - Terminals for Telematic Services Amendment 1 (Study Group 8) 27 pp《.pdf（27页珍藏版）》请在麦多课文档分享上搜索。

1、- - ITU-T RECMN*T.521 94 W 48b2591 Ob07378 035 = INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU TERMINALS FOR TELEMATIC SERVICES T.521 (1 1/94) COMMUNICATION APPLICATION PROFILE BTO FOR DOCUMENT BULK TRANSFER BASED ON THE SESSION SERVICE ITU-T Recommendat

2、ion T.521 (Previously “CCITT Recommendation”) ITU-T RECMN*T.523 94 W 4862593 Ob07379 T7L W FOREWORD The IT-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITLJ). The IT-T is responsible for studying technical, operating and tariff quest

3、ions and issuing Recommen- dations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the IT-T Study Groups which, in their turn, produce Recomm

4、endations on these topics. The approval of Recommendations by the Members of the IT-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation T.521 was revised by ITU-T Study Group 8 (1993-1996) and was approved under the WTSC Resolution No.

5、I procedure on the 1 lth of November 1994. NOTE this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITLJ 1995 All rights reserved. No part of this publication may be reproduced or utiliz

6、ed in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the IT. CONTENTS Scope and field of application References Definitions Abbreviations and conventions Definition of communication application profile BTO . 5.1 Overview o

7、f BTO 5.2 DTAM functional units . 5.3 DTAM service primitives and lower layer mapping Document interchange data structures . Document transfer 7.1 Synchronization 7.2 Document recovery . Appendix I . Overall Protocol Sequence Appendix I . Guidance for mapping of DTAM to Recommendation T.62 . Introdu

8、ction II . 1 Items to be considered when using DTAM on top of Recommendation T.62 . Page 1 1 1 1 1 1 2 2 9 9 9 9 9 13 13 13 Recommendation T.521 (194) 1 SUMMARY Recommendation this defines communication application profile for G4 facsimile apparatus. The definition of additional document characteris

9、tics in application capabilities for colour and other extension is added as an option in this revision. Il Recommendation T.521 (11/94) Recommendation T.521 COMMUNICATION APPLICATION PROFILE BTO FOR DOCUMENT BULK TRANSFER BASED ON THE SESSION SERVICE (Geneva, 1992; revised in Geneva 1994) 1 Scope an

10、d field of application This Recommendation defines the communication application profile for the document bulk transfer using the session service defined in Recommendation T.62 bis in terms of: a) DTAM functional units used; b) DTAM service primitives and parameters used; c) lower layer X.215 sessio

11、n service mapping according to the rules of Recommendation T.62 bis. 2 References The following references are required in order to implement the communication profile defined in this Recommendation. - CCITT Recommendation T.431 (1992), Document Transfer and Manipulation (DTAM) - Services and Protoc

12、ol - Introduction and General Principles. - CCIT Recommendation T.432 (1992). Document Transfer and Manipulation (DTAM) - Services and Protocols - Service Definition. - CC Recommendation T.433 (1992), Document Transfer and Manipulation (DTAM) - Services and Protocols - Protocol Specification. - Reco

13、mmendation T.62 (1993), Control procedures for teletex and group 4 facsimile services. - Recommendation T.62 bis (1993). Control procedures for teletex and G4 facsimile services based on Recommendations X. 21 5 and X. 225. - Recommendation X.2 IS (1994), Information technology - Open Systems Interco

14、nnection - Session service definition. 3 Definitions The definitions in the T.400-Series Recommendations and Recommendation T.62 bis also apply to this Recommendation. 4 Abbreviations and conventions The abbreviations and conventions defined in the T.400-Series Recommendations and Recommendation T.6

15、2 bis also apply to this Recommendation. Recommendation T.521 (1 Y94) 1 5 Definition of communication application profile BTO 5.1 Overview of BTO This Recommendation defines functional units and communication support functions in accordance with Recommen- dation T.431. BTO uses the document bulk tra

16、nsfer in transparent mode (mapping to session service as defined in the T.430-Series Recommendations). 5.2 DTAM functional units The following functional units defined in Recommendation T.432 are used for BTO: - association use control (Kernel); - capability: - document bulk transfer: - token contro

17、l. NOTE - The capability functional unit must be supported in this profile, but it is not required to use this service prior to every document transfer (D-TRANSFER). 5.3 DTAM service primitives and lower layer mapping 5.3.1 The general DTAM service definition and parameters are defined in Recommenda

18、tion T.432. This subclause specifies the parameters of the DTAM service for BTO. DTAM service primitives and parameters 5.3.1.1 D-INITIATE service parameters The following parameters of this service are used as follows: - transparent mode; - telematic requirements; - application capabilities; - resu

19、lt. Table 1 -A lists the D-INITIATE service parameters. Transparent mode This parameter shall be present in the D-INITIATE request service primitive. Telematic requirements The following functional units defined in Recommendation T.432 are used for BTO as mandatory functional units: - association us

20、e control (Kernel); - capability; - document bulk transfer; - token control. Application capabilities This “Application capabilities” parameter is defined in Recommendation T.432 and the following sub- parameter is used: ODA Application capabilities: a) Document application profile The value of this

21、 parameter indicates the document application profile being used. Its value is specified in Recommendations that define terminal characteristics for particular Telematic services. 2 Recommendation T.521 (11194) ITU-T RECMN*T-521 94 4862.593 Ob07384 339 = M M b) Document architecture class The value

22、of this parameter indicates the document architecture class used in the entire association. The use of this parameter and its possible value is specified in the Recommendations that define terminal characteristics for particular Telematic services. 4) Result This result field can take the values def

23、ined in Recommendation T.432. M(=) TABLE 1-NT.521 D-INITIATE service parameters Transparent mode Telematic requirements ODA Application capabilities I Document application profile I I Document architecture class . Result D-INITIATE D-INITIATE I request indication response confirm a) This parameter i

24、s mandatory in case the responder returns the “accepted” result parameter to the proposed requirements. 5.3.1.2 D-TERMINATE service parameters This service has no parameter for BTO. Only the initiator can issue D-TERMINATE service. In addition, the initiator can issue D-TERMINATE service only if he

25、has the data token. 5.3.1.3 D-U-ABORT service parameters This service has no parameter. 5.3.1.4 D-P-ABORT service parameter This service has no parameter. 5.3.1.5 D-CAPABILITY service parameters This service has the sub-parameter “ODA Application capabilities” which consists of the following paramet

26、ers: - document application profile; - document architecture class; - non-basic document characteristics; - additional document characteristics. Table 1-B lists the D-CAPABILITY service parameters. 1 ) Application capabilities See 5.3.1.1. ODA Application capabilities: a) Document application profil

27、e See 5.3.1.1. Recommendation T.521 (1Y94) 3 b) Document architecture class See 5.3.1.1. c) Non-basic document characteristics This is the parameter “Non-basic document characteristics” defined in Recommendation T.432. D-CAPABILITY request d) Additional document characteristics D-CAPABILITY indicati

28、on This is the parameter “Additional document characteristics defined in Recommendation T.432. I Document architecture class I I Non-basic document characteristics I I Additional document characteristics I I File transfer capabilities I I Private capabilities e) File transfer capabilities This is th

29、e parameter “File transfer capabilities” defined in Recommendation T.432. M U U U U f, Private capabilities This is the parameter “Private capabilities” defined in Recommendation T.432. TABLE 1-BR.521 ODA Application capabilities I Document application profile I M D-CAPABILITY response M M U U U U D

30、-CAPABILITY confirm i) Document informution This parameter consists of the interchange data elements representing the document. The “Document characteristics” from the document profile are transferred using S-ACT-START service. All interchange data elements, except the document profile descriptor, a

31、re transferred using S-DATA services. The document profile is reconstructed by the received DTAM-PM, on the basis of the “Document characteristics” transferred in the S-ACT-START service. 2) Document informution type This parameter has the value “transfer of a document from its beginning” in the req

32、uest primitive (see Recommendation T.432). For the indication and confirm primitive, the value is either “transfer completed” or “transfer not completed“. 3) Document reference information The value of this parameter is to be provided by the DTAM user in accordance with the rules specified in Recomm

33、endation T.432. 4) Result This parameter has one of the values “document information transferred“ or “document information not completely transferred”, as defined in Recommendation T.432. NOTE -The parameter value “document-information-continuation not possible” is for further study. 5) Checkpoint v

34、alue This parameter is used as defined in Recommendation T.432. The number of IDE per segment is integer 2. However, the document profile and the document root are not counted (see Figure i). In case of file transfer function, this parameter is used as defined in Recommendation T.432 (see Figure 2).

35、 4 Recommendation T.521 (11/94) ITU-T RECMN*T-522 94 m 4862591 Ob0738b 102 m 1 W e-!l o 1 1 1 I 7 E F? rn r: .I Recommendation T.521 (lV94) 5 The following restriction is applied to the transfer syntax coding rules defined in Recommendation X.209 for the interchange of the document application profi

36、le defined in Recommendation T.503: Length fields longer than three octets shall not be used. A length field of three octets allows for the representation of a length of up to 65 535. A data element with a length exceeding 65 535 shall have a length field of the indefinite form. - Checkpint value =

37、n (see 5.3.1.5) characteristics 1024.n 1024.n I S-ACT-START-req. S-MINOR- I I - S-MINOR- SYNC-req. I S-DATA-req. S-DATA-req. C-DATA-req. S-DATA-req. Segmented 1 data 1 O e data size c =1024=n C-ACT-END-req. S-DATA-req. S-DATA-req. To82oo6o-95/do1 FIGURE uT.521 Application of the segmenting mechanism

38、 as defined in Figure m.433 D-TRANSFER request Parameter Document information Document information type Document reference information Result Checkpoint value D-TRANSFER indication M M M M I NOTE -The document information is transferred using the type of normal document. D-TRAN S FER confirm M M 5.3

39、.1.7 D-CONTROL GIVE service parameters The D-CONTROL GIVE service surrenders all available tokens and has no parameter. 5.3.1.8 D-TOKEN PLEASE service parameters The D-TOKEN PLEASE service is used to request the data token and has no parameter. 5.3.2 Use of session service and parameter mapping 5.3.

40、2.1 DTAM protocol mapping to X.215 session service This mapping rule is defined in 7.3m.433. DCAD confirm. NOTE - D-TRANSFER confirm is implicitly formed by receipt of S-AC END confirm, S-ACT INT confirm and S-ACT 5.3.2.2 Table 2-A shows the mapping rule between DTAM service parameters and basic and

41、 additional session service parameters. DTAM parameter mapping to session service parameters The category of parameters is defined as follows: - 1 parameters are generated by DTAM user; - 2 parameters are generated by DTAM provider; - 3 parameters provided by other means than DTAM-user or DTAM-provi

42、der. Appendix I illustrates the example of protocol sequences for BTO. 6 Recommendation T.521 (11/94) ITU-T RECNN*T.521 94 H 4862591 Ob07389 910 DTAM service parameters None TABLE 2-M.521 D-INITIATE Basic and additional session Presence in session Category service parameters protocol Session termina

43、tion parameter nm 3 DTAM service parameters Basic and additional session service parameters DTAM service parameters Telematic requirements I Presence in session protocol Category ODA - Application capabilities I Document application profile I -_- I Document architecture class Session termination par

44、ameter (Transport disconnect) None m 3 m Mandatory nm Nomandatory Basic and additional session service parameters Session requirements Session user data Service identifier Inactivity timer Private use Non-standardized capabilities _- -_-_-_-_-_- Presence in session protocol m (defaultable) m m m m n

45、m nm nm Category 1 1 2 3 TABLE 2-BiT.521 D-TERMINATE TABLE 2-CiT.521 D-U-ABORT Recommendation T.521 (11194) 7 ITU-T RECMN*T.521 94 W 4Bb257L Ob07370 b32 1 Document information Session user data (Note) 1 Document reference information Document reference number (Note) 1 NOTE - There is no direct mappi

46、ng of the D-TRANSFER primitive to one single session primitive. DTAM service parameters ODA-Application capabilities None None Token m 2 None TABLE 2-DiT.521 D-CAPABILITY Basic and additional session service parameters Session user data Inactivity timer Storage capacity Private use (Note) Non-standa

47、rdized capabilities Presence in session protocol m m nm nm nm nm nm nm Category 1 2 3 NOTE - In case of file transfer, this parameter is used in accordance with the rules defined in Recommendation T.571. The use for facsimile Group 4 is for further study. TABLE 2-W.521 D-TRANSFER I I Category Basic

48、and additional session Presence in session DTAM service parameters I service parameters protocol I TABLE 2-FfT.52 1 D-TOKEN PLEASE I Basic and additional session Presence in session DTAM service parameters Category I service parameters protocol I 8 Recommendation T.521 (11/94) 6 Document interchange

49、 data structures The interchange representation of a document has to be defined in accordance with the Recommendation hich specifies the relevant document application profile. 7 Document transfer 7.1 Synchronization The document information is divided into segments, in accordance with 7.3.5R.433, such that each segment contains a one p