1、INTERNATIONAL TELECOMMUNICATION UNION CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE T.433 (09/92) TERMINAL EQUIPMENT AND PROTOCOLS FOR TELEMATIC SERVICES DOCUMENT TRANSFER, ACCESS AND MANIPULATION (DTAM) - SERVICES AND PROTOCOLS - PROTOCOL SPECIFICATION Recommendation T.433
2、FOREWORD The CCIT (the International Telegraph aod Telephone Consultative Committee) is a permanent organ of the international Telecommunication Union (ITU). CC is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing tele
3、communications on a worldwide basis. The Plenary Assembly of CCIT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. Tk approval of Recommendations by the members of CCI?T between Plenary Assemblies is covered by the procedure la
4、id down in CCIT Resolution No. 2 (Melbourne, 1988). Recommendation T.433 was revised by Study Group VI11 and was approved under the Resolution No. 2 procedure on thel8th September 1992. t CCIT NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a tel
5、ecommunication administration and a recognized priva operating agency. AU rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, elecmnic or mechanical, including photocopying and microfilm, witbout permission in writing from the . I . ITU-T *RECMN*T-
6、433 72 46b2591 Ob05405 O09 CONTENT Introduction 1 Scope and field of application 2 References . 3 Definitions and abbreviations 4 Conventions . 5 5.1 Service provision 5.2 5.3 Model of Telematic Protocol Architecture (TPA) . 6 Elements of procedure . Overview of the protocol . Relationship with othe
7、r ASES and lower layer services 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 Summary list of DTAM protocol dam unit DTAM association establishment Nonnal termination of a DTAM association . Abnormal termincation of a DTAM association Capability . Document bulk transfer . Document unc
8、onfirmed manipulation . Document confirmed manipulation . Typed Data Transfer . Remote document access Remote document management Token control . Exception report . Rules of extensibility 7 Mapping to the lower services . 7.1 Mapping to the presentation and ACSE services . 7.2 Mapping to the present
9、ation and RTSE services . 7.3 Abstract syntax definition of APDUs . 8 .i 8.2 Abstract syntax definition of APDUs for use of the session service in Transparent Mode 9 Conformance . Mapping to the Session service (Recommendation X.215) in Transparent Mode . Abstract syntax definition of APDUs in Norma
10、l Mode 8 Annex A - Examples of protocol sequence for document bulk transfer Annex B - DTAM-PM state tables . B . 1 General . B.2 Conventions B.3 Actions to be taken by the DTAM-PM B.4 Definition of variables Annex C - DTAM-PM state tables . C . 1 General . Recommendation T.433 (09/92) Page 11 1 1 1
11、1 2 2 2 3 5 6 6 13 17 20 26 32 35 36 36 36 37 39 41 31 41 45 49 51 57 60 61 62 65 65 74 74 75 76 76 1 - ITiU-T *RECMN*T*433 92 H 4862593 Ob0540b.,X45 INTRODUCTION This Recommendation specifies the protocol for the services provided by an application-service-element, tbe Document Transfer and Manipul
12、ation Service Element (DTAM) to support applications in a distributed Telematic systems environment. This Recommendation is one of a set of Recommendations specifying the protocols for sets of application-service-elements specifically used by a number of applications. 11 Recommendation T.433 (09/92)
13、 Recommendation T.433 DOCUMENT TRANSFER, ACCESS AND MANIPULATION (DTAM) - SERVICES AND PROTOCOLS - PROTOCOL SPECIFICATION (revised f992) 1 Scope and field of application This Recommendation specifies the protocol and procedures for the Document Transfer and Manipulation Service Element. The DTAM ser
14、vices are provided in conjunction with the Association Control Service Element (ACSE) service (see Recommendation X.217), Reliable Transfer Service Element (RTSE) service (see Recommendation X.218) and the Presentation-service (see Recommendation X.216) or the Session service (see Recommendation X.2
15、15). Depending on the mapping, Recommendation T.62 bis may also apply. The DTAM procedures are defined in terms of: a) the interactions between peer DTAM protocol machines through the use of the ACSE-service, RTSE- service and Presentation-service or Session service; and the interactions between the
16、 DTAM protocol machine and its service-user. b) This Recommendation specifies conformance requirements for systems implementing these procedures. The use of Remote Operation Service Element (ROSE: see Recommendation X.219) is for further study. 2 References c References are listed in Recommendation
17、T.43 1. 3 etnitions and abbreviations Terms and abbreviations are defined in Recommendation T.431. The definitions of service primitive names given in Recommendation T.432 are used in this Recommendation. 4 Conventions This Recommendation specifies the APDU fields. In section 6, tables are presented
18、 for each DTAM APDU. Each field is summarized by the following notation: M Presence is mandatory U Presence is optional req Source is related request primitive ind Sink is related indication primitive rsp Source is related response primitive cnf Sink is related confm primitive sp Source or sink is t
19、he DTAM-PM The structure of each DTAM APDU is specified in section 8 using the abstract syntax notation of Recommendation X.208. Recommendation T.433 (9D2) 1 - f ITU-T *RECMN*T.433 92 48b259L Ob05408 818 5 Overview of the protocol i 5. I Service provision The protocol specified in this Recommendatio
20、n provides the DTAM services defined in Recommendation T.432. These services are listed in Table 1.433. TABLE 1m.433 DTAM services summary Service D-INITIATE D-TERMINATE U-P-ABORT D-U-ABORT C-CAPABILITY D-TRANSFER D-TYPED-DATA D-CRE ATE D-DELETE D-MODIFY D-CALL D-REBUILD D-TOKENGIVE D-CONTROL-GIVE D
21、-TOKEN-PLEAS E D-P-EXCEPTION-REPORT D-U-EXCEPTION-REPORT Type confirmed Confmed Provider-initiated Uocodmed Confirmed Providercoofumed Unconfirmed Unconfirmed Uncodied Unconfirmed Unconfirmed Uncodmed Uocodmed uncoofied Uncoufmed Provider-initiated Unconfirmed Note - D-REBUILD, D-P-EXCEPTION-REPORT
22、and D-U-EXCEPTION -REPORT services are for further study. 5.2 Relationship with orher ASES and lower layer services 5.2.1 ACSE service (when RTSE is not used) The DTAM services require access to the A-ASSOCIATE, A-RELEASE, A-ABORT and A-P-ABORT services. The inclusion of the DTAM in an application-c
23、ontext precludes the use of any of the above ACSE services by any other ASE or the user-element. In the Transparent mode of DTAM, DTAM primitives are mapped directly onto the session service primitives, consequently, ACSE is not used. 2 Recommendation TA33 (09192) ITU-T *RECMN*T*433 92 = 48b259L Ob0
24、5409 754 5.2.2 RTSE service The RTSE is used to support document bulk transfer in the normal mode for document bulk transfer. The RTSE provides for the reliable transfer of appiication-protocoldata units (APDUs). The RTSE ensures that each APDU is completely transferred exactly once, or that the sen
25、der is warned of an exception. The RTSE recovers from communication and end-system failure and minimizes the amount of retransmission needed for recovery. 5.2.3 ROSE service The use of this ASE is for further study. 5.2.4 Preseruation-service DTAM services may require access to the P-CAPABILITY-DATA
26、, P-DATA, P-U-EXCEPTION-REPORT, P-P-EXCEPTION-REPORT, P-TOKEN-PLEASE and P-TOKEN-GIVE services. This Recommendation recognizes that the ACSE services require access to the P-CONNECT, P-RELEASE, P-U-ABORT and P-P-ABORT services. 5.2.5 X.215 Session service In the Tntisparent.Mode, APDUs defined in DT
27、AM are directly mapped to the Session service defined in Recommendation X.215. The procedures described in Recommendation T.62 bis also apply. DTAM services may require access to the S-CONNECT, S-CAPABILITY-DATA, S-ACTIVITY -START, S-DATA, S-MINOR-SYNCHRONIZE, S-ACTIVITY-END, S-ACTIVITY-J.NTERRUFT,
28、S-ACTIVITY-DISCARD, S-U-EXCEPTION-REPORT, S-ACTIVITY-RESUME, S-P-EXCEPTION-REPORT, S-TOKEN-PLEASE, S-CONTROL-GIVE, S-RELEASE, S-U-ABORT and S-P-ABORT services. 5.3 Model of Telematic Protocol Architecture (TPA) The DTAM operates between two DTAM Protocol Machines TAM-PMs) in the Application layer of
29、 the OS1 model. Protocol elements are exchanged between DTAM-PMs, using the Session service as defined in Recommendation X.215 or the services of RTSE, ACSE and of the Presentation Layer as defined in Recommendations X.218, X.217 and X.216 respectively. The model for Telematic Protocol Architecture
30、(TPA) is illustrated in Figure 1.433. This application layer protocol architecture is composed of the ACSE (Association Conuol Service Element), RTSE (Reliable Transfer Service Element), DTAM-SE (Service Element) and DTAM users. The use of RTSE is only for document bulk transfer in the Nomal Mode. U
31、se of tbe Remote Operation Service Element (ROSE) is for further study. 5.3. I Functions of DTAM user DTAM users have the role of accurately reflecting the actual Telematic user (.e. terminai user or system user) intentions in communication, and have functions to perform the applications (document b
32、ulk transfer, document manipulation, document tmnsfer and manipulation, etc.) on behalf of the actual user. This mechanism is provided by the use of the DTAM-SE through the DTAM service defmed in Recommendation T.432. The DTAM service is the logical interface between the DTAM user and DTAM service-p
33、rovider for data handling, and is independent of specific hardware and software technique. The DTAM user as an Application Service Element may be capable of interpreting the meaning of the content of an exchange document. For example, the retrieval command carried during information retrieval is not
34、 interpreted by the DTAM, but by the DTAM user. Recommendation T.433 (09192) 3 i I TO81n)8093fdO1 Note I - In the cascof use of the Session service (Transparent Mode), the appropriate DTAM APDUs are directly mapped to the Session service primitives. Nofe 2 - The use of RTSE is only for the Document
35、Bulk Transfer in the Normal mode. FIGURE 1fl.433 Telematic Protocol Architecture (TPA) model in Application Layer 5.3.2 Functions of DTAM service-provider To support Telematic Applications in single-source management of documents, DTAM service-provider provides the following communication fmctions.
36、1) Association use control (kmel) DTAM provides the mggcr for the use of the association given in ACSE, and controls association use during communication (temiination, abort, etc.) either directly or by means of the RTSE. Applying the Session service to the lower iayer functions of DTAM, this associ
37、ation use control will be mapped directly onto the session hmei functional unit. 2) DTAM capability The DTAM capability is defined by sets of parameters in order to specify the communication features: ODA application cailities a) document application profile; b) operational applicaon pro% c) non-bas
38、ic document characmistics: d) non-basic structural characteristics; and e) additional document.characiaistics, etc. File tran$er capabilities a) BFTcapabilities: b) Transparent Data Capabilities; c) DTMcapabilities; 4. d) EDIFACT capabilities. Private capabilities Recommendation TA33 (WB2) 3) Data t
39、ransmissionfunction DTAM provides functions for document buk transfer, document manipulations and typed data transmission as follows: a) Document bulk transfer DTAM provides a function to uansmit the document in bulk under the communications environment negotiated by D-INITIATE service and additiona
40、lly by D-CAPABILITY service. b) Document manipulations DTAM provides a function partially modifying a document seen by both users, by generating, revising oc deleting structures (pages, blocks, etc.) of an existing document or to create a new document by generating structure of ODA and operational s
41、tructure. c) Typed data transmission DTAM optionally provides a typed data transmission function which is independent of the data token control. 4) Document remote access For further study. 5) Document remote management For further study. 6) Token control DTAM optionally provides the function of tok
42、en control to handle the data token for dialogue. 7) Exception report DTAM optionally provides the exception reporting function for error control during the DTAM communication. 6 Elements of procedure This section identifies ail the types of protocol data units which constitute the elements of the D
43、TAM protocol between two DTAM-protocol-machines TAM-PMs). A protocol data unit (PDU) is the smallest quantity of information exchanged between DTAM-PMs wbich has a self-contained semantic significance. When a DTAM service primitive is received from the DTAM user, DTAM transmits the DTAM primitive da
44、ta to the opposite DTAM through the DTAM protocol, then the opposite DTAM generates the DTAM service primitives and notifies its DTAM user. The DTAM protocol data units -PDU) are shown in Table 2f.433. Individual parameters of DTAM service primitives are, in principle, all mapped to individual PDU p
45、arameters, but there are PDU including parameters, other than those specified in service primitives, such as those generated by DTAM itself. For example, D-INITIATE-REQ PDU also includes the DTAM protocol version parameter, which is used to negotiate the version of protocol between the DTAM-PMs. Not
46、e that the DTAM user is not concerned with this DTAM negotiation. The PDUs are here identified symbolically with minimal reference to their mapping on to the lower layer service functions which implement them, thus no differentiation is made, in this section, between PDUs wbich are effected as speci
47、fic Presentation service primitives and PDUs which are transferred as DTAM PDUs using the Presentation service data transfer functions. Details of PDU mapping and encoding are given in Section 8. r PDUs are given both full names, which should be used outside the context of this Recommendation, and a
48、bbreviated names which are used within this Recommendation for brevity. The full names consist of one or two words descriptive for the purpose of the PDU, prefixed by D- and, in the case of requesdresponse pairs of PDUs, suffixed by - REQ or -RESP as appropriate. The abbreviated names are three lett
49、ers each, with Q or R appended in the case of I requesbresponse pairs. Recommendation T.433 (09D2) 5 Protocol elements (PDU) Cross reference D-CREATE I-DELETE D-MODIFY D-CALL D-REBUILD (Further study) (Further study) 6.7 6.7 6.7 6.7 6.7 6.8 6.1 Summary list of DTAM protocol datu units TABLE f.433 DTAM protocol data units Functional units PDU abbreviation Association use control (kernel) DINQ DINR DTEQ DTER DAB D-INITIATE-REQ D-INITIATE-RESP D-TERMIN ATE-REQ D-TERMIN ATE-RESP D-ABORT 6.2 6.2 6.3 6.3 6.4 Ca
