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--h.    3'3'Standard6'6'StandardC6QMS $=R- y:(  x|@   Fascicle VII.7 Rec. T.521 y:- x|@  Fascicle VII.7 Rec. T.521    Recommendation T.521 *  COMMUNICATION APPLICATION PROFILE BT0 FOR DOCUMENT BULK ă  TRANSFER BASED ON THE SESSION SERVICE ă *  (According to the rules defined in Recommendation T.62 bis) &CONTENTS 0HIntroduction 1HScope and field of application 2HReferences 3HDefinitions 4HAbbreviations and conventions 5HDefinition of communication application profile BT0 H5.1  Overview of BT0 H5.2  DTAM functional units H5.3  DTAM service primitives and lower layer mapping 0 6HDocument interchange data structures 7HDocument transfer H7.1  Synchronization H7.2  Document transfer recovery Annex AOverall protocol sequence 0 H Introduction  HT.400 Series of Recommendations define the open document architecture and interchange format (T.410 Series) and the DTAM Services and protocols (T.430 Series) for the purpose of the document transfer and manipulation. In order to apply T.400 Series to various telematic services it is necessary to specify the application profiles for each service that consists of a document application profile and a communication application profile.  HAccording to this requirement, T.500 Series of Recommendations define the document application profiles and T.520 Series of Recommendations define the communication application profiles.  HRecommendation T.521 is one of a set of T.520 Series of Recommendations to define the communication application profile for the document bulk transfer based on the session service according to the rules defined in Recommendation T.62 bis. 1 H Scope and field application  HThis Recommendation defines the communication application profile for the document bulk transfer using the session service defined in Recommendation T.62 bis in terms of: Ha)  DTAM functional units used; Hb)  DTAM service primitives and parameters used;  Hc)  lower layer X.215 session service mapping according to the rules of T.62 bis. 2 H References  HThe following references are required in order to implement this communication profile defined in this Recommendation.  H Rec.T.431:Document transfer and manipulation (DTAM) Services and protocols Introduction and general principles'  H Rec.T.432:Document transfer and manipulation (DTAM) Service protocols Service definition'  H Rec.T.433:Document transfer and manipulation (DTAM) Service protocols Service specification' H Rec.T.62:Control procedures for teletex and Group 4 facsimile services'  H Rec.T.62bis:Control procedures for teletex and Group 4 facsimile services based on Recommendation X.215/X.225'  H Rec.X.215:Session service definition for open systems interconnection of CCITT application' (  3 H Definitions  HThe definitions of T.400 Series of Recommendations and Recommendation T.62 bis also apply to this Recommendation. 4 H Abbreviations and conventions  HThe abbreviations and conventions defined in T.400 Series of Recommendations and Recommenda tion T.62 bis also apply to this Recommendation. 5 H Definitions of communication application profile BT0 5.1HOverview of BT0  HThis Recommendation defines units and communication support function in accordance with Recommendation T.431. 5.2HDTAM functional units  HThe following functional units defined in Recommendation T.432 are used for BT0: H association use control (kernel); H capability; H document bulk transfer; H token control; H exception report; H reliable transfer mode 1. 5.3HDTAM service primitives and lower layer mapping 5.3.1HDTAM service primitives and parameters  HGeneral DTAM service definition and parameters are defined in Recommendation T.432. This section specifies the parameters of DTAM service of BT0. 5.3.1.1HDINITIATE service parameters HThe following parameters of this service are used as follows: H transparent mode; H telematic requirements; H application capabilities; H result. HTable 1A/T.521 lists the DINITIATE service parameters. H1)  Transparent mode HThis parameter should be specified in DINITIATE request service primitive. H2)  Telematic requirements  H The following functional units defined in Recommendation T.432 are used for BT0 as mandatory functional units.' H association use control (kernel); H capability; H document bulk transfer; H token control; H exception report; H reliable transfer mode 1. 0 H3)  Application capabilities  HHX This "application capabilities" is defined in Recommendation T.432 and the following sub parameters:' H a)document application profile'  H  The value of this parameter indicates the document application profile being used. Its value is specified in Recommendations that define terminal characteristics for particular telematic services.' H b)Document architecture class  H  The value 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.' H4)  Result H This field can take the values defined in Recommendation T.432. #TABLE 1A/T.521 *  DINITIATE service parameters ă   x|@ w       DINITIATE  DINITIATE  DINITIATE  DINITIATE      request  indication  response  confirm      Transparent mode  M             Telematic requirements  M  M(=)  M  M(=)          Application capabilities  M  M(=)  M  M(=)            | Document application profile  M  M(=)  M  M(=)    |        | Document architecture class  M  M(=)  M  M(=)          Result    U  C(=)      HP ,x--h.Xp$%%p& 5.3.1.2 DTERMINATE service parameters  XThis service has no parameter for BT0. Only the initiator can issue DTERMINATE. In addition, the initiator can issue DTERMINATE only if he has a data token. 5.3.1.3 DUABORT service parameters XThis service has the parameter of "user information". XTable 1B/T.521 lists the DUABORT service parameters. #TABLE 1B/T.521  DUABORT service parameters ă   w    J0Ԍ   DUABORT  DUABORT     request  indication     User information  U  C(=)        5.3.1.4 DCAPABILITIY service parameters  XThis service has the parameter "application capabilities" which consists of subparameters as follows: X document application profile; X document architecture class; X nonebasic document characteristics. XTable 1C/T.521 lists the DCAPABILITY service parameters. #TABLE 1C/T.521 *  DCAPABILITY service parameters ă   w       DCAPABILITY DCAPABILITY DCAPABILITY DCAPABILITY      request  indication  response  confirm      Application capabilities                | Document application profile  M  M(=)  M  M(=)    |        | Document architecture class  M  M(=)  M  M(=)    |        | Nonbasic document        | characteristics  U  C(=)  U  C(=)       X1) Application capabilities X See 5.3.1.1. X a) Document application profile X See 5.3.1.1. X b) Document architecture class X See 5.3.1.1. X c) Nonbasic document characteristics  X This is the "nonbasic document characteristics" defined in Recommendation T.432. 5.3.1.5 DTRANSFER service parameters XThis service has the following parameters: X1) Document information  X This consists of the interchange data elements representing the document. The "Document characteristics" from the document profile are transferred using SACTSTART (Note).'  X NoteAll interchange data elements, except the document profile descriptor, are transferred using SDATA service. The document profile is reconstructed by the receiving DTAM PM, on the basis of the "document characteristics" transferred in the SACTSTART.' /ԌX2) Document information type  X This parameter always has the value "transfer of a document from its beginning" (see Recommendation T.432).' X3) Document reference information'  X The value of this parameter is to be provided by the DTAM user in accordance with the rules specified in Recommendation T.432.' X4) Result  X This parameter has one of the values "document information transferred" and "document information not transferred", as defined in Recommendation T.432.'  X5) Checkpoint mechanism X Checkpoint mechanism 2 is applied. Value of this parameter is integer 2.'  XThe following restriction is applied to the transfer syntax coding rules defined in X.209 for the interchange of the document application profile defined in Recommendation T.503:  X 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 65535; a data element with a length exceeding 65 535 shall have a length field of the indefinite form.' XTable 1D/T.521 lists the DTRANSFER service parameter. #TABLE 1D/T.521 *  DTRANSFER service parameters ă   w      Parameter  DTRANSFER  DTRANSFER  DTRANSFER     request  indication confirmation     Document information  M  M(=)           Document information type  M  M(=)  M(=)          Document reference information  M  M(=)  M(=)          Result    M          Checkpoint mechanism  M         Xp$%%p&XHp  XHNoteThe document information is transferred using the type of normal document. 5.3.1.6H DCONTROL GIVE service parameters XThe DCONTROL GIVE service surrenders all available tokens and has no parameter. 5.3.1.7H DTOKEN PLEASE service parameters  XThe DTOKEN PLEASE service is used to request the data token and has no parameter. 5.3.1.8H DUEXCEPTIONREPORT service parameters XThis service has the parameter of "user information". XTable 1E/T.521 lists the DUEXCEPTIONREPORT service parameter. XH User information  XH This is the user information associated with the exception report of application association.' #TABLE 1E/T.521 *  DUEXCEPTIONREPORT service parameters ă   XHpXpw       DUEXCEPTIONREPORT  DUEXCEPTIONREPORT     request  indication     User information  U  C(=)     !/   5.3.1.9 DPEXCEPTIONREPORT service parameter XThis is used as defined in Recommendation T.432. 5.3.2XUse of session service and parameter mapping 5.3.2.1 DTAM protocol mapping to Recommendation X.215 session service XThis mapping rule is defined in 7.2 of Recommendation T.433.  XNoteDTRANSFER conf is implicitly informed by receipt of SACT END conf, SACT INT conf and SACT DCAD conf. 5.3.2.2 Parameters mapping to session parameters  XTables 2A/T.521 to 2H/T.521 show the mapping rule between DTAM service parameters and basic and additional session parameters. XThe category of parameters is defined as follows: X 1: parameters are generated by DTAM user; X 2: parameters are generated by DTAM provider; X 3: parameters are generated by DTAM session provider. XAnnex A illustrates the example of protocol sequences for BT0. #TABLE 2A/T.521 * % DINITIATE ă   w      DTAM service parameters  Basic and additional  Category     session parameters      Telematic requirements  Session requirements          Application capabilities   1         | Document application profile  Session user data     |      | Document architecture class        Session reference           Nonbasic session     None  capabilities  2          Service identifier           Inactivity timer       Private use           Nonstandardized      capabilities     None   3     Session control      functions           Reason      c.    t"TABLE 2B/T.521 t) t$ DTERMINATE ă   w      DTAM service parameters  Basic and additional  Category     session parameters      None  Session termination parameter  3        t"TABLE 2C/T.521 t) t% DUABORT ă   w      DTAM service parameters  Basic and additional  Category     session parameters      User information (Note)  Session termination parameter  1     (reason)      None  Session termination parameter  3     (transport disconnect)        XpXp  XNoteThis parameter is equal to reason of session termination parameter. #TABLE 2D/T.521 * # DUCAPABILITY ă   XpXpw      DTAM service parameters  Basic and additional  Category     session parameters      Application capabilities           | Document application profile      |      | Document architecture class  Session user data  1    |      | Nonbasic document      | characteristics       None  Inactivity timer  2      Acceptance of CDCL      parameters        >0 Ԍ  None  Private use  3          Nonstandardized      capabilities          t"TABLE 2E/T.521 t) t$ DTRANSFER ă   w      DTAM service parameters  Basic and additional  Category     session parameters      Document information  Session user data  1     Document information type  None   %    Document reference  Document reference number     information   1  %    Result  None         t"TABLE 2F/T.521 t) t" DCONTROL GIVE ă   w      DTAM service parameters  Basic and additional  Category     session parameters      None  None         t"TABLE 2G/T.521 t) t" DTOKEN PLEASE ă   w      DTAM service parameters  Basic and additional  Category     session parameters      None  Tokens  2        t"TABLE 2H/T.521 t) t DUEXCEPTIONREPORT ă   w >0 Ԍ     DTAM service parameters  Basic and additional  Category     session parameters      User information  Reason  1        6 X Document interchange data structures  XThe interchange representation of a document has to be defined in accordance with the Recom mendation which specifies the relevant document application profile. "  7 X Document transfer 7.1XSynchronization  XThe document information is divided into segments, in accordance with 7.2.4 of Recommenda tion T.433, such that each segment contains one page descriptor and the associated content portion. A minor synchronization point is associated with each segment. 7.2XDocument transfer recovery XFor further study. 'ANNEX A * (to Recommendation T.521) * *  Overall protocol sequence ă  XThis Annex illustrates the following procedures provided by BT0 (see Figures A1/T.521 to A4/T.521): X normal procedure; X token control procedure; X abort procedure; X exception report procedure.  CDCLX Command document capability list CDEX Command document end CDPBX Command document page boundary CDSX Command document start CDUIX Command document user information CSEX Command session end CSSX Command session start CSUIX Command session user information RDCLPX Response document capacity list positive RDEPX Response document end positive RDPBPX Response document page boundary positive RSEPX Response session end positive RSSPX Response session start positive RSUIX Response session user information "FIGURE A1/T.521 * " Normal procedure ă  CSCCX Command session change control RSCCPX Response session change control positive RSUIX Response session user information "FIGURE A2/T.521 *  Token control procedure ă CSAX Command session abort RSAPX Response session abort positive "FIGURE A3/T.521 * # Abort procedure ă \  CDDX Command document discard CDRX Command document resynchronize CSUIX Command session user information RDDPX Response document discard positive RDGRX Response document general reject RDPBNX Response document page boundary negative RDRPX Response document resynchronize positive RSUIX Response session user information "FIGURE A4/T.521 *  Exception report procedure ă