6.6.5 Transfer-interrupt 6.6.5.1Purpose The transfer-interrupt procedure is used by the requesting DTAMÍPM to handle a less severe (than those handled by the other error handling procedures) error situation during the transfer procedure, if at least one checkpoint was confirmed during the transfer procedure. 6.6.5.2APDUs used No APDUs are used in this procedure. 6.6.5.3Transfer-interrupt procedure 6.6.5.3.1Transfer-interrupt procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a requesting DTAMÍPM problem; b) a PÍACTIVITYÍINTERRUPT indication primitive; c) a PÍACTIVITYÍINTERRUPT confirm primitive. 6.6.5.3.1.1Requesting DTAMÍPM problem 6.6.5.3.1.1.1If the requesting DTAMÍPM detects a less severe problem and at least one checkpoint was confirmed during the transfer procedure, it issues a PÍACTIVITYÍINTERRUPT request primitive with one of the following Reason parameter values: a) "non-specific error", if the problem was indicated by an exception reporting procedure, b) "local SS-User error", if the problem is a local requesting DTAM-PM problem. 6.6.5.3.1.2PÍACTIVITYÍINTERRUPT indication primitive 6.6.5.3.1.2.1If the responding DTAMÍPM receives a PÍACTIVITYÍINTERRUPT indication primitive, it issues: - a PÍACTIVITYÍINTERRUPT response primitive followed by a DÍTRANSFER indication in Reliable transfer mode 1; - a PÍACTIVITYÍINTERRUPT response primitive in Reliable transfer mode 2. 6.6.5.3.1.3PÍACTIVITYÍINTERRUPT confirm primitive 6.6.5.3.1.3.1If the requesting DTAMÍPM receives a PÍACTIVITYÍINTERRUPT confirm primitive, it issues: - DÍTRANSFER confirmation to the requesting DTAM user in Reliable transfer mode 1; - the transfer-resumption procedure in Reliable transfer mode 2. 6.6.5.3.2Transfer-interrupt procedure mapped onto session service (transparent mode) This procedure is driven by the following events: a) a requesting DTAMÍPM problem: 1 Fascicle VII.7 - Rec. T.433 b) a SÍACTIVITYÍINTERRUPT indication primitive; c) a SÍACTIVITYÍINTERRUPT confirm primitive. 6.6.5.3.2.1Requesting DTAMÍPM problem 6.6.5.3.2.1.1If the requesting DTAMÍPM detects a less severe problem and at least one checkpoint was confirmed during the transfer procedure, it issues a SÍACTIVITYÍINTERRUPT request primitive with one of the following Reason parameter values: a) "non-specific error", if the problem was indicated by an exception reporting procedure; b) "local SS-User error", if the problem is a local requesting DTAMÍPM problem. Fascicle VII.7 - Rec. T.433 2 6.6.5.3.2.2SÍACTIVITYÍINTERRUPT indication primitive 6.6.5.3.2.2.1If the responding DTAMÍPM receives an SÍACTIVITYÍINTERRUPT confirm primitive, it issues an SÍACTIVITYÍINTERRUPT response primitive followed by DÍTRANSFER indication. 6.6.5.3.2.3SÍACTIVITYÍINTERRUPT confirm primitive 6.6.5.3.2.3.1If the requesting DTAMÍPM receives an SÍACTIVITYÍINTERRUPT confirm primitive, it issues DÍTRANSFER confirmation to the requesting DTAM user. 6.6.6 Transfer-discard 6.6.6.1Purpose The transfer-discard procedure is used by the requesting DTAMÍPM to escape from a more severe (than those handled by the transfer-interrupt procedure) error situation, or a less severe error situation if no checkpoint was confirmed, during the transfer procedure. 6.6.6.2APDUs used No APDUs are used in this procedure. 6.6.6.3Transfer-discard procedure 6.6.6.3.1Transfer-discard procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a requesting DTAMÍPM problem; b) a PÍACTIVITYÍDISCARD indication primitive; c) a PÍACTIVITYÍDISCARD confirm primitive. 6.6.6.3.1.1Requesting DTAMÍPM problem 6.6.6.3.1.1.1If the requesting DTAM-PM detects a more severe problem, or a less severe problem if no checkpoint was confirmed during the transfer procedure, it issues a PÍACTIVITYÍDISCARD request primitive with one of the following reason parameter values: a) "non-specific error", if the problem was indicated by an error reporting procedure; b) "local SS-User error", or "unrecoverable procedural error", if the problem is a local requesting DTAMÍPM problem. 6.6.6.3.1.2PÍACTIVITYÍDISCARD indication primitive 6.6.6.3.1.2.1If the responding DTAMÍPM receives a PÍACTIVITYÍDISCARD indication primitive, it issues: - a PÍACTIVITYÍDISCARD response primitive followed by DÍTRANSFER indication in reliable transfer mode 1; - a PÍACTIVITYÍDISCARD response primitive in reliable transfer mode 2. 6.6.6.3.1.2.2The responding DTAMÍPM deletes all knowledge and contents of the associated DTAM user information (segments of document information) so far received. 6.6.6.3.1.2.3If the responding DTAMÍPM has already issued a DÍTRANSFER indication primitive, it performs the association-abort procedure. The abort-reason field of the DAB APDU is "transfer- completed". 6.6.6.3.1.3PÍACTIVITYÍDISCARD confirm primitive 6.6.6.3.1.3.1If the requesting DTAM-PM receives a PÍACTIVITYÍDISCARD confirm primitive, it issues: - DÍTRANSFER confirmation to the requesting DTAM user in reliable transfer mode 1; - the transfer-retry procedure in reliable transfer mode 2. 3 Fascicle VII.7 - Rec. T.433 6.6.6.3.2Transfer-discard procedure mapped onto session service (transparent mode) This procedure is driven by the following events: a) a requesting DTAMÍPM problem; b) an SÍACTIVITYÍDISCARD indication primitive; c) an SÍACTIVITYÍDISCARD confirm primitive. 6.6.6.3.2.1Requesting DTAMÍPM problem 6.6.6.3.2.1.1If the requesting DTAM-PM detects a more severe problem, or a less severe problem if no checkpoint was confirmed during the transfer procedure, it issues an SÍACTIVITYÍDISCARD request primitive with one of following reason parameter values: a) "non-specific error", if the problem was indicated by an error reporting procedure; b) "local SS-User error", or "unrecoverable procedural error", if the problem is a local requesting DTAM-PM problem. 6.6.6.3.2.2SÍACTIVITYÍDISCARD indication primitive 6.6.6.3.2.2.1If the responding DTAM-PM receives an SÍACTIVITYÍDISCARD indication primitive, it issues an SÍACTIVITYÍDISCARD response primitive followed by DÍTRANSFER indication in reliable transfer mode 1. 6.6.6.3.2.2.2The responding DTAM-PM deletes all knowledge and contents of the associated DTAM user information (segments of document information) so far received. 6.6.6.3.2.2.3If the responding DTAM-PM has already issued a DÍTRANSFER indication primitive, it performs the session-abort procedure by issuing an SÍUÍABORT request. 6.6.6.3.2.3SÍACTIVITYÍDISCARD confirm primitive If the requesting DTAM-PM receives an SÍACTIVITYÍDISCARD confirm primitive, it issues DÍTRANSFER confirmation to the requesting DTAM user in reliable transfer mode 1. 6.6.7 Transfer-resumption 6.6.7.1Purpose The transfer-resumption procedure is used in the reliable transfer mode 2 by the requesting DTAMÍPM to recover from: a) an error situation handled by the transfer-interrupt procedure, or b) an error situation handled by the association-abort procedure during a transfer procedure. In this case the transfer-resumption procedure is performed after an association- recovery procedure is successfully performed. If no checkpoint was confirmed in the interrupted transfer procedure, the transfer-discard procedure followed by the transfer-retry procedure are performed. 6.6.7.2APDUs used No APDUs are used in this procedure. 6.6.7.3Transfer-resumption procedure 6.6.7.3.1Transfer-resumption procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) the resumption of an interrupted activity; b) a PÍACTIVITYÍRESUME indication primitive. Fascicle VII.7 - Rec. T.433 4 After these events, the transfer procedure is used to continue (see  6.6.3). 6.6.7.3.1.1Resumption of an interrupted activity 6.6.7.3.1.1.1The requesting DTAM-PM issues a PÍACTIVITYÍRESUME request primitive with parameters that link the resumed activity to the previously interrupted one. 5 Fascicle VII.7 - Rec. T.433 6.6.7.3.1.1.2After the requesting DTAMÍPM has issued the PÍACTIVITYÍRESUME request primitive and at least one checkpoint was confirmed in the interrupted transfer procedure, it continues the transfer procedure by issuing a PÍDATA request primitive for the segment of interchange-data-elements following the last confirmed checkpoint. If no checkpoint was confirmed in the interrupted transfer procedure, the transfer-discard procedure followed by the transfer-retry procedure are performed. 6.6.7.3.1.2PÍACTIVITYÍRESUME indication primitive 6.6.7.3.1.2.1If the responding DTAM-PM receives a PÍACTIVITYÍRESUME indication primitive, it checks the old activity identifier and the old session connection identifier parameters of the PÍACTIVITYÍRESUME indication primitive with the corresponding information (session-connection-identifier and activity identifier) recorded for the last completely secured transfer (see  6.6.3.1.4.3). 6.6.7.3.1.2.2If the information coincides with the recorded ones, the responding DTAM-PM either (a) responds correctly to the requesting DTAM-PM according to the normal transfer procedure, but discards the data it receives, and does not issue a D-TRANSFER indication primitive, or (b) performs the user-exception-report procedure with a Reason parameter value of "sequence error". 6.6.7.3.1.2.3If the information does not coincide, the transfer-resumption procedure continues as for the transfer procedure with a P-DATA indication primitive for the segment of interchange-data- element following the last confirmed checkpoint. 6.6.7.3.1.2.4If the responding DTAM-PM cannot resume the activity, the responding DTAM-PM performs the user- exception-report procedure. 6.6.8 Association-recovery 6.6.8.1Purpose The association-recovery procedure is used by the association-initiating DTAM-PM to recover from an error situation handled by the association-abort procedure or the association-provider-abort procedure. This procedure is for further study. 6.7 Document unconfirmed manipulation Document unconfirmed manipulation is used by the requestor to manipulate the constituents of ODA and operational structure which are commonly handled by both communication entities. Document unconfirmed manipulation consists of document create operation, document delete operation, document modify operation, document call operation and document rebuild operation. 6.7.1 Document create operation 6.7.1.1Purpose The document create operation procedure is used by the requestor of document manipulation to add the constituents of ODA and operational structure to a document without any confirmation of the create manipulation. 6.7.1.2APDUs used The document create operation procedure uses DÍCREATE (DCR) APDU. 6.7.1.2.1DCR APDU The field of the DCR APDU is listed in Table 10/T.433. TABLE 10/T.433 DCR APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³Create information³ M ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ Fascicle VII.7 - Rec. T.433 6 6.7.1.3 Document create operation procedure 6.7.1.3.1 Document create operation procedure mapped onto presentation service (normal mode) Procedure is driven by the following events: a) a DÍCREATE request primitive from the requestor; b) a DCR APDU as user data of a P-DATA indication primitive. 6.7.1.3.1.1 DÍCREATE request primitive 6.7.1.3.1.1.1 If the requesting DTAM-PM receives a D-CREATE request primitive, a DCR APDU is formed from the parameter values of the DÍCREATE request primitive and transferred as user-data of a PÍDATA request primitive. This may be done outside of an activity. 6.7.1.3.1.2 DCR APDU 6.7.1.3.1.2.1 If the responding DTAM-PM receives the DCR APDU as user data of a P-DATA indication primitive, the responding DTAM-PM issues a D-CREATE indication primitive to the responder. The DÍCREATE indication primitive parameter is derived from the DCR APDU. 6.7.1.4 Use of the DCR APDU fields The DCR APDU fields are used as specified below. 6.7.1.4.1 Create information This is the create information parameter value from the D-CREATE request primitive. It appears as the create information parameter value of the D-CREATE indication primitive. 6.7.2Document delete operation 6.7.2.1 Purpose The document delete operation procedure is used by the requestor of document manipulation to delete the constituents of ODA and operational structure of an existing document without any confirmation of the delete operation. 6.7.2.2 APDUs used The document delete operation procedure uses DÍDELETE (DDL) APDU. 6.7.2.2.1 DDL APDU The field of the DDL APDU is listed in Table 11/T.433. TABLE 11/T.433 DDL APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³Delete information ³ M ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ 6.7.2.3 Document delete operation procedure 6.7.2.3.1 Document delete operation procedure mapped onto presentation service (normal mode) 7 Fascicle VII.7 - Rec. T.433 This procedure request is driven by the following events: a) a D-DELETE request primitive from the requestor; b) a DDL APDU as user data of P-DATA indication primitive. Fascicle VII.7 - Rec. T.433 8 6.7.2.3.1.1 DÍDELETE request primitive 6.7.2.3.1.1.1 If the requesting DTAM-PM receives a D-DELETE request primitive, a DDL APDU is formed from the parameter values of D-DELETE request primitive and transferred as user-data of a PÍDATA request primitive. This may be done outside of an activity. 6.7.2.3.1.2 DDL APDU 6.7.2.3.1.2.1 If the responding DTAM-PM receives the DDL APDU as user data of a P-DATA indication primitive, the responding DTAMÍPM issues a D-DELETE indication primitive to the responder. The DÍDELETE indication primitive parameter is derived from the DDL APDU. 6.7.2.4 Use of the DDL APDU fields The DDL APDU fields are used as specified below. 6.7.2.4.1 Delete information This is the delete information parameter value from the D-DELETE request primitive. It appears as the delete information parameter value of the D-DELETE indication primitive. 6.7.3Document modify operation 6.7.3.1 Purpose The document modify operation procedure is used by the requestor of document manipulation to modify the attributes of constituents of ODA and operational structure of an existing document without any confirmation of the modifying operation. 6.7.3.2 APDUs used The document modify operation procedure uses D-MODIFY (DMD) APDU. 6.7.3.2.1 DMD APDU The field of the DMD APDU is listed in Table 12/T.433. TABLE 12/T.433 DMD APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ Modify information ³ M ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ 6.7.3.3 Document modify operation procedure 6.7.3.3.1 Document modify operation procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a DÍMODIFY request primitive from the requestor; b) a DMD APDU as user data of a P-DATA indication primitive. 6.7.3.3.1.1 D-MODIFY request primitive 6.7.3.3.1.1.1 If the requesting DTAM-PM receives a D-MODIFY request primitive, a DMD APDU is formed from the parameter values of D-MODIFY request primitive and transferred as user-data of a PÍDATA request primitive. This may be done outside of an activity. 6.7.3.3.1.2 DMD APDU 9 Fascicle VII.7 - Rec. T.433 6.7.3.3.1.2.1 If the responding DTAM-PM receives the DMD APDU as user data of a P-DATA indication primitive, the responding DTAM-PM issues a D-MODIFY indication primitive to the responder. The DÍMODIFY indication primitive parameter is derived from the DMD APDU. Fascicle VII.7 - Rec. T.433 10 6.7.3.4 Use of the DMD APDU fields The DMD APDU fields are used as specified below. 6.7.3.4.1 Modify information This is the modify information parameter value from the D-MODIFY request primitive. It appears as the modify information parameter value of the D-MODIFY indication primitive. 6.7.4Document call operation 6.7.4.1 Purpose The document call operation procedure is used by the requestor of document manipulation to address or to read an object of operational structure which contains a sequence of DTAM protocol data units (with some restrictions, i.e. that only DÍCREATE, DÍDELETE and DÍMODIFY can appear in this sequence). These protocol data units are applicable to the existing document. 6.7.4.2 APDUs used The document call operation procedure uses D-CALL (DCL) APDU. 6.7.4.2.1 DCL APDU The field of the DCL APDU is listed in Table 13/T.433. TABLE 13/T.433 DCL APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ Call information ³ M ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ 6.7.4.3 Document call operation procedure 6.7.4.3.1 Document call operation procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a DÍCALL request primitive from the requestor; b) a DCL APDU as user data of a P-DATA indication primitive. 6.7.4.3.1.1 DÍCALL request primitive 6.7.4.3.1.1.1 If the requesting DTAM-PM receives a D-CALL request primitive, a DCL APDU is formed from the parameter values of D-CALL request primitive and transferred as user- data of a PÍDATA request primitive. This may be done outside of an activity. 6.7.4.3.1.2 DCL APDU 6.7.4.3.1.2.1 If the responding DTAM-PM receives the DCL APDU as user data of a P-DATA indication primitive, the responding DTAM-PM issues a D-CALL indication primitive to the responder. The D-CALL indication primitive parameter is derived from the DCL APDU. 6.7.4.4 Use of the DCL APDU fields 11 Fascicle VII.7 - Rec. T.433 The DCL APDU fields are used as specified below. 6.7.4.4.1 Call information This is the call information parameter value from the D-CALL request primitive. It appears as the call information parameter value of the D-CALL indication primitive. 6.7.5Document rebuild operation (For further study.) Fascicle VII.7 - Rec. T.433 12 6.8 Document confirmed manipulation (For further study.) 6.9 Typed data transfer 6.9.1Purpose Typed data transmission is used independent of the data token and is issued from both DTAM users when required. 6.9.2APDUs usedw The typed data transfer procedure uses D-TYPED-DATA (DTD) APDU. 6.9.2.1 DTD APDU The field of the DTD APDU is listed in Table 14/T.433. TABLE 14/T.433 DTD APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ Typed data information ³ M ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ 6.9.3Typed data transfer procedure 6.9.3.1 Typed data transfer procedure mapped onto presentation service This procedure is driven by the following events: a) a DÍTYPEDÍDATA request primitive from the requestor; b) a DTD APDU as user data of a P-TYPED-DATA indication primitive. 6.9.3.1.1 D-TYPED-DATA request primitive 6.9.3.1.1.1 If the requesting DTAM-PM receives a D-TYPED-DATA request primitive, a DTD APDU is formed from the parameter values of D-TYPED-DATA request primitive and transferred as user-data of a PÍTYPEDÍDATA request primitive. 6.9.3.1.2 DTD APDU 6.9.3.1.2.1 If the responding DTAM-PM receives the DTD APDU as user data of a P-TYPED- DATA indication primitive, the responding DTAMÍPM issues a D-TYPED-DATA indication primitive to the responder. The DÍTYPEDÍDATA indication primitive parameter is derived from the DTD APDU. 6.9.4Use of the DTD APDU fields The DTD APDU fields are used as specified below. 6.9.4.1 Typed data information This is the typed data information parameter value from the DÍTYPEDÍDATA request primitive. It appears as the typed data information parameter value of the DÍTYPEDÍDATA indication primitive. 6.10 Remote document access (For further study.) 13 Fascicle VII.7 - Rec. T.433 6.11 Remote document management (For further study.) Fascicle VII.7 - Rec. T.433 14 6.12 Token control 6.12.1 Token please control 6.12.1.1 Purpose The token please procedure is used by a requestor (receiver of documents) to request the token from the responder (sender of documents). 6.12.1.2 APDUs used The token please procedure uses the D-TOKEN-PLEASE (DTP) APDU. 6.12.1.2.1DTP APDU The field of the DTP APDU is listed in Table 15/T.433. TABLE 15/T.433 DTP APDU field w ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄ¿ ³ Field name ³Presence³ Source ³ Sink ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ³ Priority ³ U ³ req ³ ind ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÙ 6.12.1.3 Token please procedure 6.12.1.3.1Token please procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a DÍTOKENÍPLEASE request primitive from the requestor; and b) a DTP APDU as user data of a PÍTOKENÍPLEASE indication primitive. 6.12.1.3.1.1 DÍTOKENÍPLEASE request primitive 6.12.1.3.1.1.1If the requesting DTAM-PM does not possess the token and receives a DÍTOKENÍPLEASE request from the requestor, a DTP APDU is formed from the parameter value of the DÍTOKENÍPLEASE request primitive and transferred as user data of a PÍTOKENÍPLEASE request primitive. This may be done either inside or outside an activity. 6.12.1.3.1.2 DTP APDU 6.12.1.3.1.2.1If the responding DTAM-PM receives the DTP APDU as user data of a PÍTOKENÍPLEASE indication primitive, the responding DTAM-PM issues a DÍTOKENÍPLEASE indication primitive to the responder. The DÍTOKENÍPLEASE indication primitive parameter is derived from the DTP APDU. 6.12.1.3.2Token please procedure mapped onto session service (transparent mode) This procedure is driven by the following events: a) a DÍTOKENÍPLEASE requestor primitive from the requestor; b) an SÍTOKENÍPLEASE indication primitive. 6.12.1.3.2.1 DÍTOKENÍPLEASE request primitive 15 Fascicle VII.7 - Rec. T.433 6.12.1.3.2.1.1If the requesting DTAM-PM does not possess the token and receives a DÍTOKENÍPLEASE request from the requestor, DTAM-PM issues a SÍTOKENÍPLEASE request primitive. This may be done either inside or outside an activity. 6.12.1.3.2.2 Implicit DTP APDU 6.12.1.3.2.2.1If the responding DTAM-PM receives an SÍTOKENÍPLEASE indication primitive without any APDU on its user data, the responding DTAM-PM issues a DÍTOKENÍPLEASE indication primitive to the responder. Fascicle VII.7 - Rec. T.433 16 6.12.1.4 Use of the DTP APDU fields The DTP APDU fields are use as specified below. 6.12.1.4.1Priority This parameter is the priority of the action, governed by the data token, that the requestor of the DÍTOKENÍPLEASE service wishes to carry out. This parameter has to be supplied by the requestor of the DÍTOKENÍPLEASE service. 6.12.2 Token give control 6.12.2.1 Purpose 6.12.2.1.1The token-give procedure is used by a requestor (sender of documents) to give the token to the responder (receiver of documents). 6.12.2.1.2The requestor becomes the receiver and the responder becomes the sender. 6.12.2.2 APDUs used No APDUs are used in this procedure. 6.12.2.3 Token give procedure 6.12.2.3.1Token give procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a DÍTOKENÍGIVE request primitive; b) a PÍTOKENÍGIVE indication primitive. 6.12.2.3.1.1 DÍTOKENÍGIVE request primitive 6.12.2.3.1.1.1If the requesting DTAM-PM possesses the token and receives a DÍTOKENÍGIVE request primitive from the requestor, it issues a PÍTOKENÍGIVE request primitive and becomes the responding DTAM-PM. This may be done only outside an activity. 6.12.2.3.1.2 PÍTOKENÍGIVE indication primitive 6.12.2.3.1.2.1If the responding DTAM-PM receives a PÍTOKENÍGIVE indication primitive, the responding DTAMÍPM issues a DÍTOKENÍGIVE indication primitive to the responder. The responding DTAMÍPM becomes the requesting DTAMÍPM. 6.12.2.3.2Token give procedure mapped onto session service (transparent mode) This procedure is driven by the following events: 17 Fascicle VII.7 - Rec. T.433 a) a D-TOKEN-GIVE request primitive from the requestor; b) an SÍTOKENÍGIVE indication primitive. 6.12.2.3.2.1 D-TOKEN-GIVE request primitive 6.12.2.3.2.1.1If the requesting DTAMÍPM possesses the token and receives a DÍTOKENÍGIVE request primitive from the requestor, it issues an SÍTOKENÍGIVE request primitive and becomes the responding DTAMÍPM. This may be done only outside an activity. 6.12.2.3.2.2 SÍTOKENÍGIVE indication primitive 6.12.2.3.2.2.1If the responding DTAMÍPM receives an SÍTOKENÍGIVE indication primitive, the responding DTAMÍPM issues a DÍTOKENÍGIVE indication primitive to the responder. The responding DTAMÍPM becomes the requesting DTAMÍPM. 6.12.3 Control-give 6.12.3.1 Purpose 6.12.3.1.1The CONTROL-GIVE procedure is used by a requestor to give all the tokens to the responder. 6.12.3.1.2The requestor becomes the receiver and the responder becomes the sender. 6.12.3.2 APDUs used No APDUs are used in this procedure. Fascicle VII.7 - Rec. T.433 18 6.12.3.3 CONTROL-GIVE procedure 6.12.3.3.1CONTROL-GIVE procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a DÍCONTROLÍGIVE request primitive; b) a PÍCONTROLÍGIVE indication primitive. 6.12.3.3.1.1 DÍCONTROLÍGIVE request primitive 6.12.3.3.1.1.1If the requesting DTAMÍPM possesses the tokens and receives a DÍCONTROLÍGIVE request primitive from the requestor, it issues a PÍCONTROLÍGIVE request primitive and becomes the responding DTAM-PM. This may be done only outside an activity. 6.12.3.3.1.2 PÍCONTROLÍGIVE indication primitive 6.12.3.3.1.2.1If the responding DTAMÍPM receives a PÍCONTROLÍGIVE indication primitive, the responding DTAM-PM issues a DÍCONTROLÍGIVE indication primitive to the responder. The responding DTAMÍPM becomes the requesting DTAM-PM. 6.12.3.3.2CONTROL GIVE procedure mapped onto session service (transparent mode) This procedure is driven by the following events: a) a DÍCONTROLÍGIVE request primitive from the requestor; b) an SÍCONTROLÍGIVE indication primitive. 6.12.3.3.2.1 DÍCONTROLÍGIVE request primitive 6.12.3.3.2.1.1If the requesting DTAMÍPM possesses the tokens and receives a DÍCONTROLÍGIVE request primitive from the requestor, it issues an SÍCONTROLÍGIVE request primitive and becomes the responding DTAMÍPM. This may be done only outside an activity. 6.12.3.3.2.2 SÍCONTROLÍGIVE indication primitive 6.12.3.3.2.2.1If the responding DTAMÍPM receives an SÍCONTROLÍGIVE indication primitive, the responding DTAM-PM issues a DÍCONTROLÍGIVE indication primitive to the responder. The responding DTAMÍPM becomes the requesting DTAMÍPM. 6.13 Exception report 6.13.1 User-exception report 6.13.1.1 Purpose The user-exception-report procedure is used by the responding DTAM-PM to report an error situation to the requesting DTAM-PM during document bulk transfer. 6.13.1.2 APDUs used No APDUs are used in this procedure. 6.13.1.3 User-exception report procedurew 6.13.1.3.1User-exception-report procedure mapped onto presentation service (normal mode) This procedure is driven by the following events: a) a responding DTAM-PM problem; b) a PÍUÍEXCEPTIONÍREPORT indication primitive. 6.13.1.3.1.1 Receiving DTAMÍPM problem 19 Fascicle VII.7 - Rec. T.433 6.13.1.3.1.1.1If the responding DTAMÍPM detects a problem, it issues a PÍUÍEXCEPTIONÍREPORT request primitive. Depending on the severity of the detected error, the value of the Reason parameter of the PÍUÍEXCEPTIONÍREPORT request primitive is as follows: a) in severe problem situations, the value "receiving ability jeopardized" is used; Fascicle VII.7 - Rec. T.433 20 b) in exceptional circumstances, the responding DTAMÍPM may have to delete a partially received document information, even though some minor synchronization points have been confirmed. In this case, the value "unrecoverable procedure error" is used; c) if the responding DTAMÍPM is not willing to complete a transfer procedure (see  6.6.3), the value "non-specific error" is used; d) if the requesting DTAMÍPM resumes a transfer procedure already finished by the responding DTAMÍPM within an application-association, the value "sequence error" is used; e) for all other less severe error situations, the value "local SS-User error" is used. 6.13.1.3.1.2 PÍUÍEXCEPTIONÍREPORT indication primitive 6.13.1.3.1.2.1If the requesting DTAMÍPM receives a PÍUÍEXCEPTIONÍREPORT indication primitive, it performs one of the following procedures depending on the Reason parameter value of the PÍUÍEXCEPTIONÍREPORT indication primitive and Reliable transfer modes: a) With a value "receiving ability jeopardized", - the transfer-abort procedure (see  6.4.3.1.4) followed by the DTAM provider-abort procedure are performed (mode 1/2). b) With a value "unrecoverable procedure error", - the transfer-discard procedure (see  6.6.6) followed by D-TRANSFER service (indication and confirmation) are performed (mode 1), - the transfer-discard procedure followed by transfer procedure are performed (mode 2). c) With a value "non-specific error", - the transfer-discard procedure followed by DÍTRANSFER service (indication and confirmation) are performed (mode 1), - the transfer-discard procedure followed by transfer procedure are performed (mode 2). d) With a value "sequence error", - the transfer-discard procedure is performed and the requesting DTAMÍPM issues an DÍTRANSFER confirm primitive with a result parameter value "document-information- transferred" to the requestor and the transfer procedure is finished (mode 1/2). e) With a value "local SS-User error" and at least one confirmed checkpoint in the transfer procedure, - the transfer-interrupt procedure (see  6.6.5) followed by DÍTRANSFER service (indication and confirmation) are performed (mode 1), - the transfer-interrupt procedure followed by the transfer-resumption procedure (see  6.6.7) are performed (mode 2). f) With a value "local SS-User error" and no checkpoint was confirmed in the transfer procedure, - the transfer-discard procedure followed by DÍTRANSFER service (indication and confirmation) are performed (mode 1), 21 Fascicle VII.7 - Rec. T.433 - the transfer-discard procedure followed by the transfer procedure are performed (mode 2). 6.13.1.3.1.2.2Table 16/T.433 summarizes the actions of the requesting DTAM-PM when receiving the PÍUÍEXCEPTIONÍREPORT indication primitive. Fascicle VII.7 - Rec. T.433 22