WPC 2%.Bpz W"S^11>bbu"::Dg1:11bbbbbbbbbb11gggbuuuk1Xubuukuuuk111Rb:bbXbb1bb''X'bbbb:X1bXXXX;.;g:=::m:::mmmmm::::::mm:k1mubububububXubububub11111111bbbbbbbbbuXubbkbuXmmmmumububXXXXbububububbmbbbbbb:k:k::=kmmX:uXb'b:b:b:b'bmbbbb:::uXuXuXuXk:k:k:mbbbmbuXkXkXKQmmmm^b:kbbbbmbA@mmbmmbmmmmmmm:b:mmmbbmmmmmmmmmmmmXXmmmmmmmmmmmmmmmmmmcm`m`mm`m:mmmmmm}}}mjjmmmmmmmmmmmmmmm0mm}mmmmmmmmmmmmmmmmmmmmmmm}Mmmmmmmmmmmmmjmmmtmmmmmmmmm`'mmm`mmjmlWmmmmmmmmmmmmmmmmmmmW`mmmmjmM#|xaHelveticaCourierCourier Bold4PkCQMS PS Jet Plus /800 II QPJPII.PRSPl`D4PkCg2W _a.s|x-HelveticaCourierHelveticaCourierCourier BoldHelvetica BoldmQrrr r  @C2M.IzPw@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C"S^1:Sbb1::Dg1:11bbbbbbbbbb::gggkuk1bkuukuuuk:1:gb1bkbkb:kk11b1kkkkDb:kbbbXD1Dg:=::r:::rrrrr::::::rr:k1rbbbbbbubububub11111111kkkkkkkkkubbkkkubrrrrrbbbbbbkububububkrkkkkkk:k:k::=krrb:bk1k:k:k:k1krkkkkDDDububububk:k:k:rkkkrkubkXkXKQrrrrbb:kbbbbrbA@rrbrrbrrrrrrrXb::rrbbrrrrrrrrrrrrkkrrrrrrrrrrrrrrrrrrcr`r`rr`r:rrrrrr}}}rjjrrrrrrrrrrrrrrr0rr}rrrrrrrrrrrrrrrrrrrrrrr}Mrrrrrrrrrrrrjrrrtrrrrrrrrr`'rrr`rrjrlWrrrrrrrrrrrrrrrrrrrW`rrrrjrM@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@,dK1dD4p}wC2.'  x"S^"55U@ %8 55555555558885a@@EE@;KE0@5PEK@KE@;E@[@@;-5 55055550P5555 050E000  8 " m mmmmm mm ;m@5@5@5@5@5`UE0@5@5@5@5E5K5K5K5K5E5E5E5E5@0@5E5K;K5@0mmmmmm@5@5E0E0E0E0E5@5@5@5@5K5mmK5K5K5K5E5E5 ; ; ";mm0 @055 5 5 5E5mmE5E5K5K5`[E E E @0@0@0@0; ; ; mmE5E5E5mmE5[E@0;0;0K,mmmm45 ;5555m5$#mm5mmLL5mmmmmmm 5` mmm55Ummmmmmmmmmmm00`mmmmmmmmmmmmmmmmmm`cm5m5mm5m mmmmmJmDDDm::mdmmmmmmmmmmmmmmmmDmmmmmmmmmmmm__mmdmmmmmmmmmD*Ommmmmmmmmmmm:mmm?mmmmmmmmm5'mmm5mm:m;/mmmmmmmmmmmmmmmmmmm/H5Jmmmm:m*@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@,dK1dD4p}wC@H4': 4D4PkC@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@,dK1dD4p}wC@H4': 4D4PkC;,>>> >  @C2  X` hp x (#%'HP ")x-    3'3'Standard6'6'StandardC6QMS $=R- y:"?  x|@   Fascicle VII.7 Rec. T.432 y:'m  x|@  Fascicle VII.7 Rec. T.432    Recommendation T.432  DOCUMENT TRANSFER AND MANIPULATION (DTAM) ă  SERVICES AND PROTOCOLS SERVICE DEFINITION ă * * 'CONTENT 0HIntroduction  1HScope and field of application  2HReferences  3HDefinitions and abbreviations  4HConventions  5HModel of the DTAM service  6HDTAM services  H6.1  DTAM association use control H6.2  DTAM capability H6.3  Document bulk transfer H6.4  Document unconfirmed manipulations H6.5  Document confirmed manipulations H6.6  Typed data transmission H6.7  Reliable transfer H6.8  Exception report H6.9  Document selection control H6.10  Document management H6.11  Document open control H6.12  Grouping control  7HFunctional units  H7.1  Association use control functional unit H7.2  Capability functional unit H7.3  Data transmission functional unit H7.4  Exception report functional unit H7.5  Session management functional units H7.6  Other functional units  8HService overview  9HService definition  H9.1  DINITIATE service H9.2  DTERMINATE service H9.3  DPABORT service H9.4  DUABORT service H9.5  DCAPABILITY service H9.6  DTRANSFER service H9.7  DTYPEDDATA service H9.8  DUNCONFIRMEDCREATE service H9.9  DUNCONFIRMEDDELETE service H9.10  DUNCONFIRMEDMODIFY service H9.11  DUNCONFIRMEDCALL service H9.12  DUNCONFIRMEDREBUILD service H9.13  DTOKENGIVE service H9.14  DCONTROLGIVE service H9.15  DTOKENPLEASE service H9.16  DPEXCEPTIONREPORT service H9.17  DUEXCEPTION REPORT service H9.18  Reliable transfer support service P+  0 H Introduction  HThis Recommendation defines the services provided by an applicationserviceelement, the document transfer and manipulation service element (DTAM), to support applications in a distributed telematic systems environment. This Recommendation is one of a set of Recommendations defining the services for sets of applicationserviceelements specifically used by a number of applications. 1 H Scope and field of application  HThis Recommendation defines in an abstract way the document transfer and manipulation (DTAM) service within the OSI application layer in terms of:  Ha)  the primitive actions and events of the service;  HHb)X  the parameter data associated with each primitive action and event;'   HHc)X  the relationship between, and the valid sequences of, these actions and events.'   HThe DTAM service is provided in conjunction with the association control service element (ACSE) service (RecommendationX.217), and the presentation service (RecommendationX.216) or sessionservice (RecommendationX.215) according to the rules of RecommendationT.62bis.   HThis Recommendation does not specify individual implementations or products, nor does it contain the implementation of entities and interfaces within a telematic system. 2 H References  HH©X Rec. T.62bis: Control procedures for Teletex and Group 4 facsimile services based on Recommendations X.215 and X.225.'   HH©X Rec. T.400: Introduction to document architecture, transfer and manipulation.'   HH©X Rec. T.411: Open document architecture (ODA) and interchange format Introduction and general principles.'   HH©X Rec. T.412: Open document architecture (ODA) and interchange format Document structures.'   HH©X Rec. T.414: Open document architecture (ODA) and interchange format Document profile.'   HH©X Rec. T.415: Open document architecture (ODA) and interchange format Open document interchange format (ODIF).'   HH©X Rec. T.416: Open document architecture (ODA) and interchange format Character content architecture.'   HH©X Rec. T.417: Open document architecture (ODA) and interchange format Raster graphics content architectures.'   HH©X Rec. T.418: Open document architecture (ODA) and interchange format Geometric graphics content architectures.'   HH©X Rec. T.431: Document transfer and manipulation (DTAM) Services and protocols Introduction and general principles.'   HH©X Rec. T.433: Document transfer and manipulation (DTAM) Services and protocols Protocol specifications.'   HH©X Rec. T.441: Document transfer and manipulation (DTAM) Operational structure.'   HH©X Rec. X.200: Reference model of open systems interconnection for CCITT applications.'  H Rec. X.208: Specification of abstract syntax notation one (ASN.1).' &  HH©X Rec. X.209: Specification of basic encoding rules for abstract syntax notation one (ASN.1).'   HH©X Rec. X.215: Session service definition for open systems interconnection for CCITT applications.'   HH©X Rec. X.216: Presentation service definition for open system interconnection for CCITT applications.'   HH©X Rec. X.217: Association control service definition for open systems interconnection for CCITT applications.'  HH©X Rec. X.218: Reliable transfer: Model and service definition.'  HH©X Rec. X.219: Remote operation: Model, notation and service definition.'   3 H Definitions and abbreviations HTerms and abbreviations are defined in RecommendationT.431.   4 H Conventions  HThis Recommendation defines services for the DTAM following the descriptive conventions defined in Recommendation X.210. In 9, the definition of each DTAM service includes a table that lists the parameters of its primitives. For a given primitive, the presence of each parameter is described by one of the following values:  Hblank  Not applicable  HM Presence mandatory  HU Presence is a user option   HHC  Presence is conditional on a successful negotiation of another parameter in previous Primitive'  HD Presence is a DTAMSE serviceprovider option  HA Presence subject to conditions defined in RecommendationX.217'  HP Presence subject to conditions defined in RecommendationX.216. '   HIn addition, the notation (=) indicates that a parameter value is semantically equal to the value to its left in the table.   5 H Model of the DTAM service  HThis Recommendation uses the abstract model for a service defined in the OSI service convention in RecommendationX.210 (see Note1). The model defines the interactions between the two DTAMserviceusers and the DTAMserviceprovider which take place between application entities. Information is passed between a DTAMserviceuser and the DTAMservice provider by DTAM service primitives which may carry parameters.   HOne of the DTAMserviceusers is defined as the initiator and the other is defined as the responder.  HThe model of the DTAM service is illustrated in Figure1/T.432.   HThe DTAM service defines a single activity between the initiator and the responder (see Note2).   HNote 1 Recommendation X.210 defines a model for the service provided by a layer of the OSI reference model.   HNote 2 At any one time, an application entity may be involved in more than one instance of the DTAM service activity, and each instance is based on a separate application association. % HThe DTAM is provided in two modes of operations:  Ha)  Transparent mode   HHX is provided solely to allow interworking with older implementations based on Recommendation T.73. This mode implies some restrictions in use of DTAM services;'  Hb)  Normal mode'   HHX is provided to allow full use of DTAM services based on the OSI service definition and protocol specification.' #FIGURE 1/T.432  Model of DTAM service ă 6 H DTAM services  HThis section provides a short description of the DTAM service. The services and the primitives by which they are invoked are defined in 9. For each service, the user of the service (the application entity that begins the sequence of primitives) is stated.  6.1HDTAM association use control  HThree services are associated with DTAM association use control:   HHa)X  the DTAM establishment service is used by the initiator to create a DTAM association for the application association linking the two DTAMserviceusers;'   Hb)  the DTAM termination service is used by either the initiator or the responder being subject to the owning the data token to dissolve the DTAM association between the DTAM serviceuser and the DTAMserviceprovider;'   H Note The DTAM termination is not restricted to a map into ARELEASE service provided by ACSE;'   Hc)  the DTAM abort service is used by either the service users or the service provider to dissolve the DTAM association unconditionally.' 6.2HDTAM capability  HThe DTAM capability service provides the means for invocation or negotiation of application and communication characteristics during an association being in effect up to the next subsequent DTAM capability invocation. A DTAM capability service is used by either the initiator or the responder being subject to the owning the data token to negotiate or invoke the above characteristics. 6.3HDocument bulk transfer  HDTAM provides a function to transmit the document in bulk from the one DTAM user to another peer under the communications environment defined by the DTAM association use and the DTAM capability functions. 6.4HDocument unconfirmed manipulations  HDTAM provides a function partially modifying a document seen by both users, by generating, revising or deleting structures (pages, blocks, etc.) of an existing document or to create a new document by generating structure without any confirmation of the manipulation. Five services are associated with document manipulation:   Ha)  the unconfirmed create operation service is used by both sides to add the constituents of ODA and operational structure to an existing document or to create constituents of ODA and operational structure;'   Hb)  the unconfirmed delete operation service is used by both sides to delete the constituents of ODA and operational structure of an existing document;'   Hc)  the unconfirmed modify operation service is used by both sides to modify the attributes of the constituents of ODA and operational structure of an existing document;'   Hd)  the unconfirmed call operation service is used by both sides to request to address or to read an object of the operational structure which contains a sequence of the DTAM protocol data units. These protocol data units are applicable to the existing document;'  He)  the unconfirmed rebuild operation service is for further study.' 6.5HDocument confirmed manipulation (for further study)  HDTAM provides a function to partially modify a document seen by both users, by generating, revising or deleting structure of an existing document or to create a new document by generating structure with a confirmation of the manipulation. 6.6HTyped data transmission  HDTAM optionally provides the function of typed data transmission which is independent of data token control. 6.7HReliable transfer (checkpointing and retransferring)  HTwo services are associated with reliable transfer (checkpointing, restarting and recovery):   Ha)  the checkpointing service is used by the sender (DTAMPM) of document to establish marks in the flow of data for the purpose of subsequent recovery or restart;'   Hb)  the document retransfer service is used by the sender or the receiver (DTAM user) of document to interrupt a transfer in progress and negotiate a point at which it is to be restarted.' (& 6.8HException report  HDTAM optionally provides an exception reporting function for exceptional error control during the DTAM communication.  6.9HDocument selection control (for further study) HFour services are associated with document selection control:   HHa)X  the document selection service is used by the initiator to select an existing document and to bind the specified document to the DTAM applicationassociation;'   Hb)  the document deselection service is used by the initiator to release the binding between the DTAM applicationassociation and the specified document;'   Hc)  the document creation service is used by the initiator to create a specified document and to select to newly created document;'   Hd)  the document deletion service is used by the initiator to release an existing selection in such a way that the previously selected document ceases to exist.' 6.10HDocument management (for further study)  HTwo services are associated with document management:   Ha)  the read attributes service is used by the initiator to interrogate the document attributes of the selected document;'   Hb)  the change attributes service is used by the initiator to modify the document attributes of the selected document.' 6.11HDocument open control (for further study)  HTwo services are associated with document open control:   Ha)  the document open service is used by the initiator to establish the presentation context and the concurrency and commitment controls for data transfer;'   Hb)  the document close service is used by the initiator to release the context established by the document open service.' 6.12HGrouping control (for further study)  HTwo services are associated with grouping control:   Ha)  the beginning of grouping service is used by the initiator to indicate the start of a set of grouped primitives which are to be processed and responded to as a group;'   Hb)  the end of grouping service is used by the initiator to indicate the end of a set of grouped primitives which are to be processed and responded to as a group.' 7 H Functional units  HDTAM service classes in the Recommendation T.431 and functional units are logical groupings of related services defined in this Recommendation for the purpose of:   Ha)  negotiation of the DTAMserviceuser's requirements during DTAM applicationassociation establishment;'  Hb)  reference by other CCITT Recommendations.' 7.1HAssociation use control functional unit   HThe DTAM provides the trigger for the establishment and use of the association. The association use control unit supports the basic DTAM services for unique discrimination of both application entities(AEs), selection of functional units, set of an initial DTAM capability, establishment, termination and abort of association use. ' 7.2HCapability functional unit  HThe DTAM capability functional unit provides the means for invocation or negotiation of application and communication characteristics during an association being in effect up to the next subsequent DTAM capability invocation. 7.3HData transmission functional unit   HThe DTAM provides document transfer methods, such as bulk document transfer, document manipulation and typed data transmission. The data transmission unit consists of the following four units.  7.3.1HDocument bulk transfer functional unit   HThe DTAM has a function to transmit the document in bulk to the other DTAM user under the communication environment defined at the start of the association use and/or the capability control The documents represented by the document interchange format defined in Recommendations T.415 andT.441 are transmitted using the bulk document transfer unit.   HNote The detailed definition of Recommendation T.441 (interchange format of operational structure) depends on the ongoing work on operation structure.  7.3.2HDocument unconfirmed manipulation functional unit   HDTAM provides a function to partially modify a document by generating, revising or deleting structures of an existing document or to create a new document. The DTAM user uses a document manipulation unit to manipulate structures of an existing document or to create a new document.  7.3.3HDocument confirmed manipulation functional unit  HUse of this functional unit is for further study.  7.3.4HTyped data transmission functional unit   HThe DTAM provides a function to pass these units on directly to the DTAM user as typed data. User information (e.g. transmission interrupt) can be transported by typed data transmission unit without being subject to token control. 7.4HException report functional unit   HThe DTAM provides exception reporting services for exceptional conditions occurring in the DTAM user or DTAMserviceprovider. 7.5HSession management functional units   HThe DTAM manages dialogue control functions provided by the session layer, the following functional units being available for DTAM communication environment.  7.5.1HToken control functional unit   HTransmission rights required for document transfer and document manipulations are controlled with the token control unit. This functional unit will be selected in the case of the halfduplex communication mode.   HFor the document manipulation functional unit, only the "data token" is required in nature. However, the right to use the document manipulation is handled as follows:   H when the document bulk transfer functional unit is selected in addition to the document manipulation, DCONTROLGIVE service is used;'   H when only the document manipulation functional unit is selected, DTOKENGIVE service is used.'  7.5.2HReliable transfer support functional unit   HThis functional unit provides two different ways of transferring a document in a reliable way:   H reliable transfer mode 1 where the secure transfer is under the responsibility of the DTAMPM but the resumption of an interrupted transfer is under the responsibility of the DTAMuser;'   H reliable transfer mode 2 where the secure transfer is completely under the responsibility of the DTAMPM (including the resumptions).' % 7.6HOther functional units  HThe DTAM will provide a document selection control, a document management, an open control and a grouping control. These DTAM functions are left for further study. 8 H Service overview  HThis Recommendation defines the following services for the management of document transfer and manipulation facilities:  Ha)  DINITIATE;  Hb)  DTERMINATE;  Hc)  DPABORT;  Hd)  DUABORT;  He)  DCAPABILITY;  Hf)  DTRANSFER;  Hg)  DTYPEDDATA;  Hh)  DCREATE;  Hi)  DDELETE;  Hj)  DMODIFY;  Hk)  DCALL;  Hl)  DREBUILD;  Hm)  DTOKENGIVE;  Hn)  DCONTROLGIVE;  Ho)  DTOKENPLEASE;  Hp)  DUEXCEPTIONREPORT;  Hq)  DPEXCEPTIONREPORT.   HDINITIATE service enables a DTAMserviceuser to request the establishment of a DTAM applicationassociation with another AE.   HDTERMINATE service enables the association initiating or responding DTAMserviceuser to request the termination of the established applicationassociation. It may do so only if it possesses the data token.   HDPABORT service enables a DTAMservice provider to abort the applicationassociation.   HDUABORT service enables a DTAMserviceuser to abort the applicationassociation.   HDCAPABILITY service enables the DTAM service user to invoke or negotiate some applications and communication characteristics during the life time of association.   HDTRANSFER service enables a DTAMserviceuser that possesses the data token to request the bulk document transfer over an applicationassociation.   HDTYPEDDATA service enables a DTAMserviceuser to request the data transmission without being subject to token control, which is different from the above document transfer service.   HDCREATE, DDELETE and DMODIFY services enable a DTAM service user that possesses the data token to request the creation, deletion and modification of the architectural objects and contentportions of a document.   HDCALL service enables a DTAMserviceuser that possesses the data token to request to address or to read an object of the operational structure which contains a sequence of DTAM protocol data units (with some restrictions, i.e. that only DCREATE, DDELETE and DMODIFY can appear in this sequence). These protocol data units are applicable to the existing document. 8( HDREBUILD service is for further study.   HDTOKENGIVE service enables a DTAMserviceuser to relinquish the data token to its peer. It may do so only if it possesses the data token.   HDCONTROLGIVE service enables a DTAMserviceuser to relinquish all the tokens (control) to its peer. It may do so only if it possesses all the tokens.   HDTOKENPLEASE service enables a DTAMserviceuser to request the data token. It may do so only if it does not already possess the data token. The data token is requested by either DTAM serviceuser to allow the DTAMserviceuser to transfer documents.   HDUEXCEPTION REPORT service provides an exception reporting service for exceptional conditions occurring in either DTAMserviceusers.   HDPEXCEPTIONREPORT service provides an exception reporting service for exceptional conditions occurring in the DTAMservice provider. 9 H Service definition  HDTAM service is a logical interface for data handling between the DTAM user and DTAM service provider, and the DTAM services are listed in Table1/T.432. $TABLE 1/T.432 *  DTAM services summary ă   x|@ w      Service  Type      DINITIATE  confirmed        DTERMINATE  confirmed        DPABORT  providerinitiated        DUABORT  unconfirmed        DCAPABILITY  confirmed        DTRANSFER  providerconfirmed        DTYPEDDATA  unconfirmed        DCREATE  unconfirmed        DDELETE  unconfirmed        DMODIFY  unconfirmed        DCALL  unconfirmed        DREBUILD (see Note)  unconfirmed        DTOKENGIVE  unconfirmed        DCONTROLGIVE  unconfirmed        DTOKENPLEASE  unconfirmed        DPEXCEPTIONREPORT  providerinitiated        DUEXCEPTIONREPORT  unconfirmed      HP ")x-Xp"% X Note DREBUILD service is for further study. ,  9.1XDINITIATE service   XThe DTAM user notifies DTAMserviceprovider of association use start with DINITIATE. This service primitive includes parameter sets for:  Xa) unique discrimination of both AEs;'  Xb) selection of functional units for DTAM service used; and'  Xc) establishment of a common communication environment in both systems.'   XThe related service structure consists of four events, as illustrated in Figure 2/T.432. #FIGURE 2/T.432 *  DINITIATE service events ă 9.1.1XDINITIATE service parameters XTable 2/T.432 lists the DINITIATE service parameters. $TABLE 2/T.432  DINITIATE service parameters ă   w        Parameter  DINITIATE  DINITIATE  DINITIATE  DINITIATE      request  indication  response  confirm      Transparent mode  U                Telematic requirements  M  M(=)  Ca)  C(=)             Application capabilities  M  M(=)  M  M(=)             DTAMQOSb)  U  C(=)  U  C(=)             Accountb)  U  C(=)  U  C(=)             Service classes (Note)                 Result    M  M(=)             User informationb)  U  C(=)  U  C(=)  / Ԍ           Application context nameb)  A  A(=)  A  A(=)             Calling AP titleb)  A  A(=)           tTABLE 2/T.432 (cont.) t) t DINITIATE service parameters ă   w        Parameter  DINITIATE  DINITIATE  DINITIATE  DINITIATE      request  indication  response  confirm      Calling AP         invocationidentifierb)  A  A(=)               Calling AE qualifierb)  A  A(=)               Calling AE         invocationidentifierb)  A  A(=)               Called AP titleb)  A  A(=)               Called AP         invocationidentifierb)  A  A(=)               Called AE qualifierb)  A  A(=)               Called AE         invocationidentifierb)  A  A(=)               Responding AP titleb)    A  A(=)             Responding AP         invocationidentifierb)    A  A(=)             Responding AE qualifierb)    A  A(=)             Responding AE         invocationidentifierb)    A  A(=)  >0 Ԍ           Calling presentation         addressb)  P  P(=)               Called presentation         addressb)  P  P(=)               Responding presentation         addressb)    P  P(=)             Presentation context         definition listb)  P  P(=)               Presentation context         definition resultb)    P  P(=)             Presentation requirementsb)  P  P(=)  P  P(=)             Initial assignment of tokenb)  P  P(=)  P  P(=)             Quality of serviceb)  P  P(=)  P  P(=)      Xp"%xXp"%  xxxa)XThis parameter is mandatory in case the responder returns the "accepted" result parameter to the proposed requirements.'x  xxxb)XThis parameter is absent in transparent mode.'x xx'x  xNote The use of this parameter is for further study. #  xXp"%Xp"%9.1.1.1 Transparent mode  XThis nonmandatory parameter is used to indicated to the local DTAMPM how the DTAM protocol is to be mapped onto the lower layers. Presence of this parameter indicated that the mapping is to be done onto the session service. Absence of this parameter indicates that the mapping is to be done onto ACSE and presentation layer services. 9.1.1.2 Telematic requirements  XAs defined in this Recommendation, DTAM has the following functional units as the application protocol in order to simplify the DTAM procedure:  X kernel (association use control);  X capability;  X document bulk transfer;  X typed data transmission;  X document unconfirmed manipulation;  X document confirmed manipulation;  X token control;  X exception report;  X reliable transfer (see Note):  X a) reliable transfer mode 1;  X b) reliable transfer mode 2.   XTelematic requirements specify the DTAM functional units which should be used during an association. In this case, each DTAM user proposes use or nonuse of each functional unit, except for the kernel functional unit, based on the DTAM user requirements. The functional unit is selected only if both the initiator and the responder propose to use the functional unit.   XNote When the reliable transfer support function is selected, document bulk transfer function should be used. This support function provides no service primitives but provides the two types of reliable transfer service (mode 1 and mode 2) within DTAMserviceprovider to support the secured document transfer (see 9.18). 9.1.1.3 Application capabilities  XThe requested application capabilities parameter indicates, for each direction of transmission, the receiving application capabilities of the requester. Each DTAM user exchanges its own receiving application capabilities with a peer DTAM user through Dinitiate service. Values of this parameter may be the reason for subsequent termination. The continued progress of the service is only guaranteed if the DTAM user acts as a sender of a document within the requested receiving capabilities by the peer DTAM user (receiver of document). This parameter is stated independently by each DTAM user as the maximum receiving capabilities when that user is the receiving side. There is no negotiation. The stated value from each DTAM user is maintained by the corresponding user for use when it is the sending DTAM user. The values for each direction of document transfer are not necessarily the same.   XThe application capabilities parameter consists of one or more sets of subparameters. Each set, if present, shall contain one document application profile parameter and, optionally, a combination of the four other parameter described hereafter. 9.1.1.3.1  Document application profile  XThe parameter specifies the document application profile available to sender of this parameter as the receiving capabilities. The value of its parameter is one of the following capabilities:  XX© handling the document application profile'X  X (RecommendationT.501);  X handling the document application profile X (RecommendationT.502); / X handling the document application profile X (RecommendationT.503);  X handling the document application profile X (RecommendationT.504).  9.1.1.3.2  Document architecture class   XThe parameter specifies the document application profile available to the sender of this parameter as the receiving capabilities. The value of this parameter is: X formatted.  9.1.1.3.3  Nonbasic document characteristics   XThis parameter specifies the nonbasic document characteristics available to the sender of this parameter as the receiving capabilities. The values of this parameter are any combination of capabilities defined in RecommendationT.414, and they are related to the value of the document application profile.  9.1.1.3.4  Nonbasic structural characteristics   XThis parameter specifies the nonbasic structural characteristics available to the sender of this parameter as the receiving capabilities. The values of this parameter are any combination of capabilities defined in Recommendation T.414, and they are related to the value of the document application profile.  9.1.1.3.5  Operational application profile  XDetailed specification of operational application profile is for further study.  9.1.1.4 DTAM QOS  XDTAM QOS is left for further study.  9.1.1.5 Account   XThe account parameter identifies the account to which costs incurred in the application association which is being established are to be charged.  XNote Further study will be requested.  9.1.1.6 Service classes  XThe use of this parameter is for further study.  9.1.1.7 Result   XIf the DINQ APDU was rejected by the responding DTAMPM (i.e. a DINITIATE indication primitive was not issued to the responder), this field is suppled by the responding DTAMPM; otherwise, this field is the result parameter from the DINITIATE response primitive. In either situation, it appears as the result parameter on the DINITIATE confirm primitive. This field can take one of the following symbolic values:  X accepted;  X rejected by responder (reasonsnotspecified);  X rejected by responder (protocol versionnotsupported);  X rejected by responder (DTAMQOSnotsupported);  X rejected by responder (applicationcontextnotsupported);  X rejected by responding DTAMQM.  9.1.1.8 User information   XThis is the user information associated with the initiation of application association.  9.1.1.9 Application context name   XThis parameter is used as defined in RecommendationX.217. The initiator of the application association shall propose one of the applicationcontext names for the specific application in the DINITIATE request primitive.  XThe responder shall either:  /Ԍ X accept the applicationcontext proposed by the initiator and return the same value of this parameter in DINITIATE response primitive;'   X or return, in the DINITIATE response primitive, a result parameter with the value "rejected by responder (applicationcontext name not supported)" and possibly make a counterproposal by returning a different applicationcontext name in the DINITIATE response primitive.'  9.1.1.10 Presentation context definition list   XThe presentation context definition list comprises a presentationcontextdefinition for each abstractsyntax included in the applicationcontext, i.e. one each for the specific application, the DTAM and the ACSE for instance. A presentationcontextdefinition comprises a presentationcontext identifier and an abstractsyntaxname for the ASE.  9.1.1.11 Other parameters  XParameters marked with "A" in Table2/T.432 are defined in RecommendationX.217.  XParameters marked with "P" in Table2/T.432 are defined in RecommendationX.216. 9.2XDTERMINATE service  XThe DTERMINATE service is used by either the associationinitiator or the association responder to request the termination of an applicationassociation. It may do so if it possesses the data token and this service is a confirmed service.   XThe termination of the applicationassociation is without loss of information in transit. This service cannot be rejected by the associationresponding DTAMservice user.   XThe related service structure consists of four events, as illustrated in Figure3/T.432. #FIGURE 3/T.432 *  DTERMINATE service events ă 9.2.1XDTERMINATE service parameters   XTable3/T.432 lists the DTERMINATE service parameters. These parameters are only present in the normal mode for use in the OSI lower layer service. In the case of a transparent mode, this service primitive has no parameters. $TABLE 3/T.432 *  DTERMINATE service parameters ă   w      Parameter  DTERMINATE  DTERMINATE  DTERMINATE  DTERMINATE     request  indication  response  confirm     Charginga)    C  C           User        informationa)  U  C(=)  U  C(=)       Xp"%Xp"% Xa) This parameter is absent in the transparent mode. / Xp"%Xp"%9.2.1.1 Charging  XThe charging parameter conveys information on the costs attributed to the account during the DTAM applicationassociation which is being released. The use of this parameter is for further study. 9.2.1.2 User information  XThis is the user information associated with the termination of applicationassociation. 9.3XDPABORT service  XThe DPABORT service provides an indication to both the DTAM users that the application association cannot be maintained (e.g. because retransmission is not possible). If it is the sender, the DTAM provider first issues a negative DTRANSFER confirm primitive for the document information not yet transferred. This service is applicable for document manipulation as well as bulk transfer. In the case of bulk transfer, if it is the receiver, the DTAM provider deletes any partially received document information prior to issuing the DPABORT indication. This service is a providerinitiated service.  XThe related service structure consists of two events, as illustrated in Figure4/T.432. #FIGURE 4/T.432  DPABORT service events ă 9.3.1XDPABORT service parameters XThe DPABORT service has no parameters. 9.4XDUABORT service  XThe DUABORT service enables a DTAM user to abort the applicationassociation. The abort may be requested by either DTAM user. This service is an unconfirmed service.  XThe related service structure consists of two events, as illustrated in Figure5/T.432. #FIGURE 5/T.432 *  DUABORT service events ă % 9.4.1XDUABORT service parameters XTable 4/T.432 lists the parameters of DUABORT. $TABLE 4/T.432 *  DUABORT service parameters ă   w      Parameter  DUABORT request  DUABORT indication          User      informationa)  U  C(=)       Xp"%X(p"%X (  a)pThis parameter is absent in the transparent mode. 9.4.1.1 User information  XThis is the user information associated with the abort of applicationassociation. 9.5XDCAPABILITY service  XThis service should be used outside the document transmission procedure. The multiple use of the DCAPABILITY service within a single association may be permitted.  XThe related service structure consists of four events, as illustrated in Figure6/T.432. #FIGURE 6/T.432  DCAPABILITY service events ă " X(p"%X(p"%9.5.1XDCAPABILITY service parameters  XTable 5/T.432 lists the DCAPABILITY service parameters.  $TABLE 5/T.432  DCAPABILITY service parameters ă   X(p"%Xp"w       Parameter  DCAPABILITY  DCAPABILITY  DCAPABILITY  DCAPABILITY      request  indication  response  confirm      Application capabilities                 Document application         profile  U  C(=)  U  C(=)             Document architecture         Class  U  C(=)  U  C(=)             Non basic         structural         characteristics  U  C(=)  U  C(=)             Non basic document         characteristics  U  C(=)  U  C(=)             Operational application         profile  U  C(=)  U  C(=)             Capability         resulta)    M  M(=)             User informationa)  U  C(=)  U  C(=)     Xp"Xp"% >0Ԍa)XThis parameter is absent in the transparent mode. 9.5.1.1 Application capabilities   XThe application capabilities parameter requested by the requesting DTAM user (requestor: sender of documents) indicates a list of receiving application capabilities that may be required at the responding DTAM user by the requesting DTAM user.  XApplication capabilities consist of the following five parameters.  9.5.1.1.1  Document application profile   XThe parameter specifies the document application profile that may be required at the responding DTAM user by the requesting DTAM user. The values of this parameter are any combination of the following capabilities:  X handling the document application profile X (Recommendation T.501);  X handling the document application profile X (Recommendation T.502);  X handling the document application profile X (Recommendation T.503);  X handling the document application profile X (Recommendation T.504).  9.5.1.1.2  Document architecture class   XThis parameter specifies the document architecture classes that may be required at the responding DTAM user by the requesting DTAM user. The value of this parameter is: X formatted.  9.5.1.1.3  Nonbasic document characteristics   XThis parameter specifies the nonbasic document characteristics that may be required at the responding DTAM user by the requesting DTAM user. The values of this parameter are any combination of capabilities defined in RecommendationT.414.  9.5.1.1.4  Nonbasic structural characteristics   XThis parameter specifies the nonbasic structural characteristics that may be required at the responding DTAM user by the requesting DTAM user. The values of this parameter are any combination of capabilities defined in RecommendationT.414.  9.5.1.1.5  Operational application profile  XDetailed specification of operational application profile is for further study.  9.5.1.2 Capability result  XThis result parameter contains one of the following:   XXa)X confirmation that all the requested capabilities are available at the DTAM responder;'    Xb) a list of the requested capabilities that are available at the DTAM responder;'  Xc) a complete list of nonbasic receiving capabilities;'   Xd) indication that no extended capabilities are available in the DTAM responder, or that none of the capabilities requested by the initiator are available.'  9.5.1.3 User information  XThis parameter is the user information associated with the capability.  9.6XDTRANSFER service   XThe remote document bulk transfer is used to convey the document which contains ODA and operational structure to the remote DTAMuser. The requestor who requests the remote document bulk transfer must have a data token in an appropriate manner. It supports the DTRANSFER services.  XIn this situation, a reliable transfer support functional unit will be selected by the negotiation of functional units in the association establishment phase. If a reliable transfer support functional unit is not selected, the RTSE service will be used. The use of RTSE is for further study.   XThe DTRANSFER service performs the following two types of documents transmission:   Xa) transmission of a complete document by transfer procedure defined in 6.6.3 of RecommendationT.433;'   Xb) retransmission of a partial document for resuming purposes by transferuserresume procedure defined in 6.6.4 of RecommendationT.433.'   XThe related service structure consists of three events, as illustrated in Figure7/T.432. #FIGURE 7/T.432 *  DTRANSFER service events ă + 9.6.1XDTRANSFER service parameters  XTableau 6/T.432 lists the DTRANSFER service parameters. $TABLE 6/T.432  DTRANSFER service parameters ă   w        Parameter  DTRANSFER  DTRANSFER  DTRANSFER     request  indication  confirm     Document information  M  C       (Note 1)           Transfer timea)  M            Document information       type  M  C  C(=)          Document reference       information  M  M  M          Synchronization point  C   C     (Note 2)  (Note 4)  (Note 3)          Result    M          Checkpoint mechanism  M          Xa) Presence only for reliable transfer mode 2 (see 9.18).  XNote 1 Mandatory in the case of successful DTRANSFER procedure.   XXNote 2 Mandatory when the document information type has the value "transfer of a document from a synchronization point".'X   XNote 3 Mandatory in the case of incomplete DTRANSFER procedure.   XNote 4 Use of this parameter in DTRANSFER indication is for further study.  9.6.1.1 Document information   XThis consists of one or more "interchange data elements" of the types defined in RecommendationsT.415, T.441 and T.541, in accordance with the document application profile and operational application profile that are in effect.  9.6.1.2 Transfer time   XThis parameter defines the time period within which the DTAMprovider must successfully transfer the document information to the other DTAMuser. This parameter is used only in the reliable transfer mode 2 as mandatory parameter and has to be suppled by the requestor of the DTRANSFER service. The absence of this parameter indicates that the established DTAM applicationassociation is performed under the reliable transfer mode 1 (see  9.18).  9.6.1.3 Document information type   XThis parameter may take different values depending on the primitive where it is used:  Xa) in a DTRANSFER request it shall take one of the following values:'  X i) "transfer of a document from its beginning";  XXX   XX ii) "transfer of a document from a synchronization point";' >0  XXX  when the parameter takes this latter value, the value of the corresponding synchronization point shall be given in the parameter "synchronization point" (see 9.6.1.5);'    Xb) in a DTRANSFER indication for confirm it shall take one of the following values:'  X i) "transfer completed";'  XXX   XX ii) "transfer not completed";'   XXX  When this parameter takes this latter value, the value of the last positively acknowledged synchronization point is given in the parameter "synchronization point" (see 9.6.1.5).'   XThis parameter is used only in reliable transfer mode1.  XNote In a logical interface sense, it is assumed that, for retransmission of document, the complete document is submitted to DTAM protocol machine (PM) using the DTRANSFER service. It is assumed that DTAMPM locates the checkpoints in the same manner as in the first transmission. 9.6.1.4 Document reference information  XThis parameter uniquely identifies a document in the DTRANSFER service. The value of this parameter shall be assigned as decimal digits, preferably but not necessarily starting from 001. This value shall then sequentially be incremented by one for each successive document transmission. This parameter shall be assigned to all documents by the DTAM user sending the document.  XIn order to uniquely identify the documents exchanged, it is recommended that the same value of this parameter should not appear within an application association. This parameter is used in reliable transfer mode1. 9.6.1.5 Synchronization point XThis parameter has different significations depending on the service primitive:  Xi) in a DTRANSFERrequest it indicates the requested minor synchronization point number from which the initiator tries to retransmit. It is used together with the value "transfer of a document from a synchronization point" of the parameter document information type;'   Xii) in a DTRANSFERindication it indicates the last positively confirmed minor synchronization point number (for further study);'   XXX XXiii)  in a DTRANSFERconfirm it indicates the last positively confirmed minor synchronization point number. It is used together with the value "transfer not completed" of the parameter document information type. If no synchronization point was confirmed during the document transfer, this parameter may be absent.'  XThis parameter is used only in reliable transfer mode1. 9.6.1.6 Result XThis parameter specifies the result of the transfer as follows:  X documentinformationtransmitted: positive confirm; the documentinformation has been transferred to, and secured by the receiving DTAMprovider (used for both reliable transfer modes);'   X documentinformationnottransferred: negative confirm; the documentinformation could not be transferred within the specified transfer time (used for reliable transfer mode2);'   X documentinformationnotcompletely transferred: negative confirm; the documentinformation could not be completely transferred, remaining part of >0 the document as indicated by the value of the parameter "document information type" (used for reliable transfer mode 1). The indication of this parameter may result to resume the transmission of the remaining part of the document from the requesting DTAM user;' :  X documentinformationcontinuenotpossible: negative confirm; this value is used when the document linking information is not available at the sending or receiving side (used for reliable transfer mode 1). This indication of this parameter may result to retry the transmission of the entire document again from the requesting DTAM user.' XThis parameter has to be supplied by the DTAMprovider.