|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 57984 (0xe280)
Types: RcTekst
Names: »VIL2.WP«, »VIL2.WPB«
└─⟦51ec6abc5⟧ Bits:30005985 Manualer - TELETEX Document Handler
└─⟦this⟧ »VIL2.WP«
└─⟦this⟧ »VIL2.WPB«
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆ -┆06┆┆0b┆ -↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
┆0e┆↓
╞ Table 21↲
↲
╞ ┆a1┆state ! event ! action ! new state ↲
wait reply ! ! !↲
ok ! SESS ABORT ! DH stream ! 26a↲
┆e1┆& wait cap ! IND ! break ! ↲
┆a1┆ resp ! ! ! ↲
wait reply ! ! SESS ABORT! ↲
ok ! TU removed ! REQ !↲
& wait cap ! ! DH stream ! 35a↲
┆a1┆ resp ! ! break ! ↲
wait reply ! ! !↲
ok ! prio break ! DH stream ! 25d *3)↲
┆a1┆ ! ! break ! ↲
wait cap ! ! !↲
resp ! prio break ! DH stream ! 25c *4)↲
┆a1┆ ! ! break ! ↲
wait reply ! REQ.REGRET ! IND.UPD !↲
ok ! regret ! state = ! -↲
┆a1┆ ! possible ! regretting!╞ ╞ ↲
╞ wait reply ! REQ.REGRET ! !↲
╞ ok ! regret not ! - ! -↲
╞ ┆a1┆ ! possible ! ! ↲
╞ wait reply !╞ ! DH stream !↲
╞ ┆a1┆ok ╞ ! REQ.ABORT ! break ! 25d *3)╞ ↲
╞ wait cap╞ !╞ ! DH stream !↲
╞ ┆a1┆resp ╞ ! REQ.ABORT ! break ! 25c *4)╞ ↲
wait reply ! REPLY NOT ! !↲
ok ! OK ! DH stream ! 25d↲
╞ ╞ ! & TTXSI ! close !↲
╞ ╞ ! stream ! !↲
╞ ┆a1┆ ! close ! ! ↲
┆1f┆ wait reply ! stream pro-! DH stream !↲
┆a1┆ok ! tocol err ! break ! 25d╞ ↲
╞ wait cap ! stream pro-! DH stream !↲
╞ ┆a1┆resp ! tocol err ! close !╞ ╞ ↲
wait cap ! REPLY NOT ! !↲
╞ RESP ╞ ! OK ! DH stream ! 25c↲
╞ ╞ !& TTXSI ! close !↲
╞ ╞ ! stream !╞ !↲
╞ ┆a1┆╞ ! close !╞ !╞ ╞ ↲
↲
↲
┆0f┆↓
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
╞ fig. 21, footnotes↲
↲
╞ *1) ┆84┆The parameters are set thus:↲
↲
╞ a) mode=R↲
↲
╞ b) ┆84┆document: the document number field in doc_dcr in the ↓
┆19┆┆90┆┄┄packet description.↲
════════════════════════════════════════════════════════════════════════
↓
╞ c) ┆84┆checkpoint: the checkpoint field in doc_dcr.↲
↲
d) ┆84┆reservation: the res_no field in the session description, ↓
┆19┆┆90┆┄┄to which the packet is connected.↲
↲
The document stream is now open.↲
↲
╞ *2) ┆84┆The STREAM CHECKPOINT and STREAM END blocks are queued in the ↓
┆19┆┆8d┆┄┄packet description.↲
↲
╞ *3) ┆84┆The handling will be as if a RESYNCH REQ has been sent and ↓
┆19┆┆8d┆┄┄confirmed inside the normal document level.↲
↲
╞ *4) ┆84┆The response to CAP REQ will be awaited, otherwise as *3).↲
↲
╞ *5) ┆84┆The capabilities delivered in REPLY OK (and now confirmed) ↓
┆19┆┆8d┆┄┄will be used in a later DOC START REQ or DOC CONT REQ.↲
↲
╞ *6) ┆84┆State will transmitting (regret switch off or regret not ↓
┆19┆┆8d┆┄┄possible) or regretting.↲
↲
↲
┆a1┆┆b0┆6.4.4.3╞ Packet Source, Normal Operation↲
↲
╞ ┆84┆This section describes normal document transmission, and the ↓
┆19┆┆89┆┄┄protocol machine is shown in fig. 22. It is normally left when a ↓
┆19┆┆89┆┄┄STREAM END is received on the document stream.↲
↲
╞ fig. 22 has the entry point:↲
↲
╞ 22a: ┆84┆The capabilities has been confirmed from the remote party. A ↓
┆19┆┆8d┆┄┄DOC START REQ or a DOC CONT REQ should be sent according to ↓
┆19┆┆8d┆┄┄the current document description.↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 22. Packet Source, normal operation↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
↲
╞ ╞ ╞ 22a↲
↲
╞ ╞ CHECKPOINT=0╞ CHECKPOINT<>0↲
╞ ╞ *2)╞ *2)↲
↲
↲
╞ DOC START REQ╞ DOC CONT REQ↲
↲
↲
↲
╞ ╞ ╞ ╞ DOC START CONF *3)↲
↲
↲
PAGE END CONF/IND.WRITE doc source STREAM/DATA REQ↲
*4)╞ ╞ *1)↲
↲
↲
╞ ╞ ╞ ╞ CHECKPOINT/PAGE END REQ↲
↲
RESP.WRITE PAGE END↲
*5) CONF RESP↲
↲
↲
↲
↲
↲
↲
╞ ╞ ╞ STREAM END PAGE END REQ↲
↲
↲
╞ ╞ ╞ 23a↲
↲
↲
↲
↲
↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ table 22.↲
↲
┆0e┆↓
╞ ┆a1┆state ! event ! action ! new state ↲
doc ! TTXSI !╞ !↲
source╞ ! stream !╞ !↲
╞ ╞ ! close╞ !╞ !↲
╞ ╞ !& REPLY ! DH stream !↲
┆a1┆ ! NOTOK ! close ! 25b *7 ↲
doc ! stream pro-! DH stream !↲
┆a1┆source ! tocol err ! break ! 25b *7)╞ ↲
! ! DH stream !↲
doc ! SESS ABORT ! break ! 26a↲
┆a1┆source ! IND ! ! ↲
doc ! EXCEPTION ! DH stream ! 25b *7)↲
╞ ┆a1┆source ! IND ! break ! ↲
╞ doc ! ┆82┆prio break┆81┆ ! DH stream ! 25b *7)↲
╞ ┆a1┆source ! ! break ! ↲
╞ doc ╞ ! ┆82┆REQ.ABORT┆81┆ ! DH stream ! 25b *7)↲
╞ ┆a1┆source !╞ ! close !╞ ╞ ↲
╞ ╞ ! REQ.REGRET !╞ !↲
╞ doc ╞ ! regret ! DH stream ! 25a *6)↲
╞ source ! possile ! break ! IND.UPD↲
╞ ┆a1┆╞ ! !╞ ! state = ↲
╞ ╞ ! REQ.REGRET !╞ !↲
╞ doc ╞ ! regret not !╞ !↲
┆a1┆source ! possible !╞ - ! - ↲
┆a1┆┆e1┆╞ ! ! DH stream !↲
╞ doc ! TU removed ! break ! 35a↲
source ! ! SESS ABORT!↲
╞ ┆a1┆ ! ! REQ ! ↲
┆0f┆↓
↲
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
╞ Fig. 22, footnotes.↲
↲
╞ *1) ┆84┆The saved STREAM CHECKPOINT and STREAM END blocks are ↓
┆19┆┆8d┆┄┄simulated received in this state.↲
↲
╞ *2) ┆84┆The checkpoint field in doc_dcr. Note that checkpoint=0 always ↓
┆19┆┆8d┆┄┄holds for service=TLX.↲
↲
╞ *3) ┆84┆The document reference number delivered is saved in the ↓
┆19┆┆8d┆┄┄document description, which is now fully defined.↲
↲
╞ *4) ┆84┆The document description is updated with the corresponding ↓
┆19┆┆8d┆┄┄checkpoint number.↲
↲
╞ *5) ┆84┆It is confirmed against S62CP that the checkpoint number ↓
┆19┆┆8d┆┄┄contained in the IND.WRITE is saved at DS.↲
↲
╞ *6) ┆84┆A discard will be sent.↲
↲
╞ *7) A resynchronize will be sent.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆6.4.4.4╞ Packet Source, Document Termination↲
↲
╞ ┆84┆Fig. 23 describes the normal termination of the transmission of a ↓
┆19┆┆89┆┄┄document. This envolves waiting for a DOC END CONF, updating of ↓
┆19┆┆89┆┄┄the document description at DS and closing of the document stream. ↓
┆19┆┆89┆┄┄Finally, the next document description in the packet is read, if ↓
┆19┆┆89┆┄┄there are more documents to send.↲
↲
╞ Fig. 23 has the entry point 23a.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 23. Packet source, document termination.↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ ╞ ╞ ╞ 23b↲
↲
↲
↲
╞ ╞ ╞ ╞ ╞ DOC START CONF *4)↲
↲
↲
↲
╞ ╞ ╞ doc↲
RESP.WRITE PAGE END CONF source PAGE END CONF/IND.WRITE↲
RESP╞ term↲
↲
↲
↲
╞ ╞ ╞ ╞ DOC END CONF/IND.WRITE↲
╞ ╞ ╞ ╞ *1)↲
╞ ╞ wait doc↲
╞ ╞ source↲
╞ ╞ write↲
↲
↲
↲
↲
╞ ╞ RESP.WRITE/DH stream close *7)↲
↲
↲
↲
╞ ╞ wait doc↲
╞ ╞ source↲
╞ ╞ close↲
↲
↲
↲
answ DH stream close answ DH stream close IND.READ *2)↲
doc eq no = no of des doc seq no<no of des (next doc des) *2)↲
↓
↲
↲
↲
╞ ╞ ╞ RESP.READ↲
╞ ╞ ╞ *8)↲
↲
↲
↲
get nest↲
doc dcr╞ ╞ abort switch off↲
╞ ╞ ╞ ╞ ╞ ╞ *3)↲
↲
↲
↲
╞ ╞ ╞ ╞ ╞ ╞ prio break↲
↲
↲
24a╞ ╞ ╞ ╞ ╞ 21a 25d↲
════════════════════════════════════════════════════════════════════════
↓
┆0e┆↓
╞ Table 23↲
↲
╞ ┆a1┆state ╞ ! event ! action ╞ ! new state↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ doc source term╞ ! stream╞ !╞ ╞ !↲
╞ & wait doc source╞ ! protocol ! -╞ ╞ ! -↲
╞ write╞ ╞ ! err╞ ! *6)╞ ╞ !↲
╞ & wait doc source╞ !╞ !╞ ╞ !↲
╞ ┆a1┆ close╞ ╞ !╞ !╞ ╞ ╞ ↲
╞ ! ! !↲
╞ ╞ ╞ ! TTXSI !╞ ╞ !↲
╞ doc source term ! stream !╞ ╞ !↲
╞ ┆a1┆╞ ╞ ! close !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ wait doc source ! TTXSI╞ ! answ TTXSI ! -↲
╞ write╞ ╞ ! stream ! stream close╞ !↲
╞ & wait doc source╞ ! close╞ !╞ ╞ !↲
╞ ┆a1┆ close╞ ╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ doc source term╞ ! REQ.ABORT ! -╞ ╞ ! -↲
╞ & wait doc source ! ╞ !╞ ╞ !↲
╞ write╞ ╞ !╞ !╞ ╞ !↲
╞ & wait doc source╞ !╞ !╞ ╞ !↲
╞ close╞ ╞ !╞ !╞ ╞ !↲
╞ ┆a1┆& get next doc dcr╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ doc source term╞ !╞ !╞ ╞ !↲
╞ & wait doc source╞ ! REQ.REGRET ! -╞ ╞ ! -↲
╞ write╞ ╞ !╞ !╞ ╞ !↲
╞ & wait doc source╞ !╞ ! ╞ ╞ !↲
╞ close╞ ╞ !╞ !╞ ╞ !↲
╞ ┆a1┆& get next doc dcr╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ doc source term╞ ! SESS ABORT ! DH stream╞ ! 26a↲
╞ & wait doc source╞ ! IND╞ ! break╞ !↲
╞ ┆a1┆ write╞ ╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ wait doc source╞ !╞ !╞ ╞ !↲
╞ close╞ ╞ ! SESS ABORT ! -╞ ╞ ! 26a↲
╞ ┆a1┆& get next doc dcr╞ ! IND╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
! EXCEPTION ! DH stream !↲
╞ ┆a1┆& doc source term╞ ! IND╞ ! break╞ !╞ ↲
╞ doc source term╞ !╞ !╞ ╞ !↲
╞ & wait doc source╞ ! prio break ! -╞ ╞ ! -↲
╞ close╞ ╞ !╞ !╞ ╞ !↲
╞ ┆a1┆& get next doc dcr╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ & doc source term╞ ! TU removed ! SESS ABORT REQ ! 35a↲
╞ & wait doc source╞ !╞ ! DH stream break!↲
╞ ┆a1┆ write ╞ ╞ !╞ !╞ ╞ !╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ wait doc source╞ ! TU removed ! SESS ABORT REQ╞ ! 35a↲
╞ ┆a1┆ close╞ ╞ !╞ !╞ ╞ ╞ ↲
╞ ╞ ╞ !╞ !╞ ╞ !↲
╞ get next doc dcr╞ ! TU removed ! SESS ABORT REQ╞ ! 20a↲
╞ ┆a1┆╞ ╞ !╞ !start sess clear!╞ ↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 23, footnotes.↲
↲
╞ *1) ┆84┆The checkpoint number in the document description is updated ↓
┆19┆┆8d┆┄┄to the number corresponding to DOC END REQ, and finished is ↓
┆19┆┆8d┆┄┄set to true.↲
╞ ┆84┆All buffers from this packet pending at S62CP is now home.↲
↲
╞ *2) read_seq_no is increased by one.↲
↲
╞ *3) ┆84┆If there is a packet in the busy queue where the following ↓
┆19┆┆8d┆┄┄holds: "queued packet interrupts current", a prio break is ↓
┆19┆┆8d┆┄┄simulated.↲
↲
╞ *4) ┆84┆See footnote *3) for figure 22.↲
↲
╞ *5) ┆84┆The packet is fully transmitted.↲
↲
╞ *6) ┆84┆The DH has sent anything on the document stream after STREAM ↓
┆19┆┆8d┆┄┄END. Nothing can be done about it, since the document has been ↓
┆19┆┆8d┆┄┄transmitted.↲
↲
╞ *7) ┆84┆A possible pending TTXSI stream close is returned.↲
↲
╞ *8) ┆84┆If service=TLX, checkpoint no is set to 0 and finished for ↓
┆19┆┆8d┆┄┄false. The document description read becomes the current ↓
┆19┆┆8d┆┄┄document description.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆6.4.4.5╞ Normal Submit Termination↲
↲
╞ ┆84┆This section describes fig. 24, which handles termination of a ↓
┆19┆┆89┆┄┄sub┄mit packet. All documents have been sent correctly. The session ↓
┆19┆┆89┆┄┄is left by "doc level exit", except when charge req=true. In the ↓
┆19┆┆89┆┄┄latter cases the session will be terminated under control of the ↓
┆19┆┆89┆┄┄packet.↲
↲
╞ 24a: The normal entry point.↲
↲
╞ 24b: ┆84┆As 24a, but the packet is already disconnected from session.↲
↲
╞ 24c: ┆84┆Entry point used in all cases where a possible pending ↓
┆19┆┆8e┆┄┄REQ.SUBMIT shall be answered by CONF.SUBMIT, result=ok, and a ↓
┆19┆┆8e┆┄┄possible CONF.REGRET shall contain the result "pers_err" (The ↓
┆19┆┆8e┆┄┄REGRET was too late). ↲
↲
╞ 24d: ┆84┆Entry where it is tested if a REQ.ABORT is pending. Used when ↓
┆19┆┆8e┆┄┄another transaction has been terminated with result<>not_proc↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 24. Normal Submit termination.↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ ╞ ╞ 24a↲
↲
↲
╞ ╞ charge req↲
↲
↲
╞ not charge req╞ SESS END REQ↲
↲
↲
doc level exit↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ submit↲
╞ ╞ ╞ charge↲
↲
↲
↲
╞ ╞ CHARGE INF IND↲
↲
↲
╞ ╞ ╞ ╞ start sess clear↲
↲
↲
╞ ╞ IND.UPD↲
24b state=transmission complete↲
↲
↲
╞ ╞ ╞ ╞ ╞ RESP.UPD (not last)↲
↲
↲
╞ wait↲
24c submit updates↲
↲
↲
RESP.UPD (last) CONF.SUBMIT RESP.UPD (last)↲
submit switch on result=ok╞ submit swtitc off↲
↲
↲
↲
╞ ╞ ╞ regret switch on╞ CONF.REGRET↲
╞ ╞ ╞ ╞ ╞ RESULT=pers_err↲
↲
↲
regret switch off↲
↲
↲
24d↲
↲
╞ abort switch↲
↲
20a╞ off╞ ╞ abort switch on↲
↲
╞ ╞ CONF.ABORT↲
╞ ╞ result = rec_unkw *3)↲
╱04002d440c00060000000002014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
════════════════════════════════════════════════════════════════════════
↓
↲
┆0e┆↓
╞ Table 24.↲
↲
↲
╞ ┆a1┆state ! event ! action ! new state ↲
╞ wait submit! ! !↲
╞ charge ! REQ.ABORT ! - ! -↲
╞ & wait sub-! ! !↲
╞ ┆a1┆mit updates! ! !╞ ╞ ↲
wait submit! SESS ABORT ! ! ↲
╞ ┆a1┆ charge ! IND ! - ! -╞ ↲
wait submit! ! !↲
┆a1┆┆e1┆charge ! TU removed ! start sess! 20a ↲
┆a1┆ ! ! clear ! ↲
wait ! ! !↲
submit ! TU removed ! - ! 20a↲
╞ ┆a1┆updates ! ! ! ↲
↲
┆0f┆↓
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 24, footnotes↲
↲
*1) ┆84┆The charge delivered is sent to DS in the next IND.UPD.↲
↲
╞ *2) ┆84┆It is simulated that the REQ.ABORT was received after ↓
┆19┆┆8d┆┄┄CONF.SUBMIT (REGRET) was delivered. ↲
↲
↲
┆b0┆┆a1┆6.4.4.6╞ Resynchronize/Discard Handling↲
↲
╞ ┆84┆The protocol machine shown in fig. 25 is described in this ↓
┆19┆┆89┆┄┄section. The primary goal is to↲
↲
╞ - terminate a REQ.REGRET by sending a discard.↲
↲
╞ - ┆84┆to handle errors where the document level can be left in an ↓
┆19┆┆8b┆┄┄orderly manner.↲
↲
╞ ┆84┆However, by service = TLX the session will be aborted in all these ↓
┆19┆┆89┆┄┄cases.↲
↲
╞ Fig. 25 has the entry points:↲
↲
╞ 25a: ┆84┆the packet is inside the document level started with DOC ↓
┆19┆┆8e┆┄┄START REQ or DOC CONT REQ, and the command executed is a ↓
┆19┆┆8e┆┄┄REQ.REGRET ↲
↲
┆8c┆┆83┆┆e0┆↓
╞ 25b: ┆84┆A resynchronize should be performed. Used in the following ↓
┆19┆┆8e┆┄┄cases:↲
↲
╞ - ┆84┆document stream protocol error in document level states.↲
╞ - prio break in document level states.↲
╞ - EXCEPT IND received.↲
╞ - A REQ.ABORT is being executed.↲
↲
╞ 25c: ┆84┆Document stream protocol error or prio break in the "wait cap ↓
┆19┆┆8d┆┄┄resp" state (CAP RESP POS is awaited).↲
↲
╞ 25d: ┆84┆Document stream protocol error, REQ.ABORT or prio break ↓
┆19┆┆8d┆┄┄outside document level.↲
↲
╞ 25e: ┆84┆A REQ.ABORT or prio break outside document level, but before ↓
┆19┆┆8e┆┄┄a document stream was opened (se fig. 23).↲
↲
╞ A DH stream close has been sent in all these cases.↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 25. Resynchronize/Discard Handling↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
25a╞ 25d╞ ╞ 25c╞ 25b↲
↲
↲
↲
╞ service=TLX╞ service=TLX╞ service=TLX service=TLX↲
↲
↲
↲
service=TTX╞ service=TTX╞ service=TTX╞ service=TTX↲
↲
↓
↲
╞ denne har jeg lidt svært ved - undskyld viggo.↲
↲
↲
↲
↲
↲
↲
↲
↲
╞ ╞ ╞ ╞ ╞ SESS ABORT REQ↲
↲
↲
↲
↲
↲
↲
↲
╞ ╞ charge req╞ SESS END REQ↲
↲
╞ not charge req↲
↲
↲
╞ doc level exit╞ ╞ ╞ ╞ wait↲
╞ ╞ ╞ ╞ ╞ ╞ resync↲
╞ ╞ ╞ ╞ ╞ ╞ charge↲
↲
↲
↲
╞ ╞ ╞ ╞ ╞ CHARGE IND/IND.UPDATE↲
↲
╞ ╞ ╞ start sess clear↲
╞ 27a↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆0e┆↓
Table 25.↲
↲
╞ ┆a1┆state ╞ ! event ! action ! new state ↲
╞ discarding ╞ ! ! !↲
╞ & clear doc level╞ ! TTXSI ! - ! -↲
┆a1┆& resynchronizing╞ !stream close! !╞ ↲
wait doc ╞ ! ! answ TTXSI!↲
level close╞ ! TTXSI ! stream ! -↲
┆a1┆ ╞ !stream close! close ! ↲
discarding ╞ ! ! ! ↲
& clear doc level╞ ! answ DH ! - ! -↲
┆a1┆& resynchronizing╞ !stream close! ! ↲
discarding ╞ ! ! !↲
& clear doc level╞ ! SESS ABORT ! - ! 26a↲
& wait doc level╞ ! IND ! !↲
close ! ! !↲
╞ ┆a1┆& resynchronizing╞ !╞ !╞ !╞ ↲
wait resync charge ! SESS ABORT ! - ! -↲
┆a1┆ ╞ ! IND ! ! ↲
╞ discarding ╞ ! Document ! !↲
╞ & clear doc level╞ ! level S62CP! - ! -↲
╞ ╞ ! commands ! !↲
╞ ┆a1┆& resynchronizing╞ ! *4) ! !╞ ↲
╞ discarding ╞ ! document ! !↲
╞ & wait doc level╞ ! stream ! - ! -↲
╞ close ╞ ! commands ! !↲
& clear doc level ! ! !↲
╞ ┆a1┆┆e1┆┆a1┆& resynchronizing╞ ! *5) ! !╞ ↲
╞ discarding ╞ ! ! !↲
╞ & clear doc level╞ !RESP.WRITE ! - ! -↲
& resynchronizing ! ! !↲
╞ & wait doc ╞ ! ! !↲
╞ level close╞ ! ! !↲
╞ & wait resync ╞ ! ! !↲
╞ ┆a1┆ charge ╞ ! ! ! ↲
╞ discarding ╞ ! ! !↲
╞ & clear doc level ! prio break ! - ! -↲
& resynchronizing ! ! !↲
╞ & wait doc ╞ ! ! !↲
╞ level close╞ ! ! !↲
╞ ┆a1┆& wait resync charge! ! !╞ ↲
╞ discarding ╞ ! ! !↲
╞ & clear doc level ! TU removed ! SESS ABORT! 35a↲
& resynchronizing ! ! REQ !↲
╞ & wait doc ╞ ! ! !↲
╞ ┆a1┆ level close╞ ! ! ! ↲
╞ wait resync╞ ! ! !↲
╞ charge ╞ ! TU removed ! - ! 35a↲
╞ ┆a1┆ ╞ ! ! ! ↲
════════════════════════════════════════════════════════════════════════
↓
Table 25. (cont.)↲
↲
╞ ┆a1┆state ! event ! action ! new state ↲
╞ discarding ╞ ! ! !↲
╞ & clear doc level╞ ! REQ.ABORT ! - ! -↲
& resynchronizing ! ! !↲
╞ & wait doc level╞ ! ! !↲
╞ close ╞ ! ! !↲
╞ ┆a1┆& wait resync charge! ! !╞ ↲
clear doc level ! ! !↓
& resynchronizing ! REQ.REGRET ! - ! -↲
& wait doc level ! ! !↲
close ! ! !↲
┆a1┆& wait resync charge! ! ! ↲
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 25, footnotes↲
↲
╞ *1) ┆84┆Checkpoint in the document description is set to 0, indicating ↓
┆19┆┆8d┆┄┄that the document should be transmitted from the beginning in ↓
┆19┆┆8d┆┄┄case of a SUBMIT.↲
↲
╞ *2) ┆84┆All buffers pending at S62CP for this packet is now home. A ↓
┆19┆┆8d┆┄┄possible pending TTXSI stream close is answered.↲
↲
╞ *3) ┆84┆If DH close pending is false, an "answ DH stream close" event ↓
┆19┆┆8d┆┄┄is simulated.↲
↲
╞ *4) ┆84┆They have passed DOC DISC REQ or DOC RESYNC REQ across the ↓
┆19┆┆8d┆┄┄interface.↲
↲
╞ *5) ┆84┆They have passed DH stream close across the interface.↲
↲
╞ *6) ┆84┆The charge delivered is sent to DS in the next IND.UPD.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆6.4.4.7╞ Session Break Down Handling, Source↲
↲
╞ ┆84┆This section handles premature terminations of a session, des┄↓
┆19┆┆89┆┄┄cribed in fig. 26. The session is completely terminated under ↓
┆19┆┆89┆┄┄packet control, because pending buffers shall be home from S62CP ↓
┆19┆┆89┆┄┄before the document stream can be terminated.↲
↲
╞ Fig. 26 is entered (via 26a) in the following cases.↲
↲
╞ - ┆84┆SESS ABORT IND received in states where a document stream has ↓
┆19┆┆8b┆┄┄been open and not fully terminated.↲
↲
╞ - ┆84┆REQ.ABORT or REQ.REGRET executed when service=TLX.↲
↲
╞ - Document stream protocol error when service=TLX.↲
↲
╞ - except ind received when service = TLX.↲
↲
╞ - ┆84┆prio break when service=TLX.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 26. Session break down handling, source.↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ ╞ ╞ 26a↲
↲
↲
╞ ╞ ╞ ╞ CHARGE INF IND/IND.UPDATE↲
↲
↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ clear↲
╞ ╞ ╞ ind↲
↲
↲
↲
╞ STREAM CLEAR IND/STREAM CLEAR RESP↲
╞ ╞ ╞ *1)↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ bufs↲
╞ ╞ ╞ home↲
↲
↲
↲
↲
↲
╞ ╞ answ STREAM CLEAR RESP↲
╞ ╞ ╞ *2)↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ error source↲
╞ ╞ ╞ close *3)↲
↲
↲
↲
╞ ╞ answ DH stream close↲
↲
↲
↲
╞ ╞ term sess↲
↲
↲
↲
outstanding writes<>0 outstanding writes=0↓
↲
↲
↲
27a 27b↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Table 26.↲
┆0e┆↓
↲
╞ ┆a1┆state ╞ ! event ╞ ! action ! new state↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait clear ind╞ ! S62CP messages╞ !╞ !↲
╞ ╞ ╞ ! different from╞ ! -╞ ! -↲
╞ ┆a1┆╞ ╞ ! SESS CLEAR IND╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait clear ind╞ ! document stream╞ !╞ !↲
╞ & wait bufs home╞ ! messages different! -╞ ! -↲
╞ & wait error source╞ ! from TTXSI stream╞ !╞ !↲
╞ ┆a1┆ close╞ ╞ ! close╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait clear ind╞ !╞ ╞ !╞ !↲
╞ & wait bufs home╞ ! REQ.REGRET╞ ! -╞ ! -↲
╞ & wait error source╞ !╞ ╞ !╞ !↲
╞ ┆a1┆ close╞ ╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait clear ind╞ ! REQ.ABORT ╞ ! -╞ ! -↲
╞ & wait bufs home╞ !╞ ╞ !╞ !↲
╞ & wait error source╞ !╞ ╞ !╞ !↲
╞ ┆a1┆ close╞ ╞ !╞ ╞ !╞ !╞ ↲
↲
wait clear ind ╞ !╞ ╞ !╞ !↲
& wait bufs home ! ! !↲
& wait error source ! RESP.WRITE ! - !↲
╞ ┆a1┆ close ! ! ! ↲
↲
wait clear ind ! answ ! !↲
┆a1┆& wait bufs home ! DH stream close ! ! ↲
↲
╞ wait clear ind╞ !╞ ╞ !╞ !↲
╞ & wait bufs home╞ ! prio break╞ ! -╞ ! -↲
╞ & wait error source !╞ ╞ !╞ !↲
╞ ┆a1┆ close╞ ╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait clear ind╞ ! TTXSI stream close! -╞ ! -↲
╞ ┆a1┆& wait bufs home╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait error source╞ ! TTXSI stream close! answ TTXSI! -↲
╞ close╞ ╞ !╞ ╞ ! stream !↲
╞ ┆a1┆╞ ╞ !╞ ╞ ! close╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ ┆a1┆wait clear ind╞ ! TU removed╞ ! -╞ ! 35a╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ ┆a1┆wait bufs home╞ ! TU removed╞ ! -╞ ! 35b╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait error source╞ ! TU removed╞ ! -╞ ! 35c↲
╞ ┆a1┆ close╞ ╞ !╞ ╞ !╞ !╞ ↲
┆0f┆↓
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 26, footnotes.↲
↲
╞ *1) ┆84┆SESS CLEAR RESP can be sent at once, because no S62CP messages ↓
┆19┆┆8d┆┄┄will be pending at TTXSI in packet source mode.↲
↲
┆8c┆┆83┆┆d0┆↓
╞ *2) ┆84┆All pending messages are now home from S62CP, also the ones ↓
┆19┆┆8d┆┄┄belonging to TTXSI. A possible pending TTXSI stream close can ↓
┆19┆┆8d┆┄┄be returned.↲
↲
╞ *3) ┆84┆If DH close pending is false, receival of an answ DH stream ↓
┆19┆┆8d┆┄┄close is simulated.↲
↲
↲
┆b0┆┆a1┆6.4.4.8╞ Termination Test↲
↲
╞ ┆84┆This section describes fig. 27. It handles the cases where the ↓
┆19┆┆89┆┄┄packet has been disconnected from the session, and where the issue ↓
┆19┆┆89┆┄┄is not a normal termination of a REQ.SUBMIT.↲
↲
╞ ┆84┆The entry into this figure happens when one of the following ↓
┆19┆┆89┆┄┄events have occurred:↲
↲
╞ - a REQ.ABORT has been executed.↲
╞ - a REQ.REGRET has been executed.↲
╞ - document stream break down.↲
╞ - EXCEPT IND received.↲
╞ - prio break occurred↲
╞ - CAP CONF NEG received↲
╞ - answ SESS START REQ, result=busy received↲
╞ - SESS START CONF NEG received↲
╞ - ABORT IND received.↲
↲
╞ ┆84┆The main function of the algorithm is to see if the packet should ↓
┆19┆┆89┆┄┄be terminated, using the information in submit switch, regret ↓
┆19┆┆89┆┄┄switch, abort switch and the content of the document description.↲
↲
╞ ┆84┆The handling in fig. 27 ends in either a packet termination or in ↓
┆19┆┆89┆┄┄entry in fig. 28 (encapsulation handling).↲
↲
╞ ┆84┆The figure has two entry points:↲
↲
╞ ┆84┆27a: ┆84┆One or more IND.WRITE's is outstanding, or IND.READ is out┄↓
┆19┆┆8e┆┄┄standing (in the last case outstanding writes must be zero).↲
↲
╞ 27b: ┆84┆No outstanding WRITE's or READ's.↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 27. Termination test.↲
╱04002d440c00060000000002014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ ╞ ╞ ╞ 27a↲
↲
┆b0┆Kære Viggo, jeg forstår ikke rigtigt dine rettelser på denne tegning.↲
╞ ╞ ╞ ╞ wait↲
╞ ╞ RESP.READ error source RESP.WRITE(not last)↲
╞ ╞ service=TTX╞ writes↲
24b╞ ╞ & result=failed╞ *1↲
↲
↲
╞ ╞ ╞ RESP.READ╞ ╞ RESP.WRITE(last)↲
╞ ╞ ╞ result=ok↲
╞ ╞ ╞ or↲
╞ IND.READ *4)╞ service=TLX↲
╞ (next doc dcr)↲
↲
╞ ╞ ╞ service=TTX╞ service=TLX↲
╞ finished=true↲
↲
╞ finished=false↲
↲
╞ ╞ ╞ regret switch off╞ regret switch↲
╞ regret switch on╞ or doc seq no<>1╞ on↲
╞ & doc seq no=1↲
╞ ╞ ╞ ╞ ╞ ╞ regret switch↲
*5)╞ ╞ ╞ ╞ ╞ ╞ off↲
↲
╞ submit switch on↲
↲
╞ CONF.SUBMIT submit switch╞ ╞ *7)↲
╞ result=not proc off↲
↲
↲
╞ ╞ ╞ checkpoint<>0 *6)↲
╞ ╞ ╞ & service=TTX↲
╞ ╞ ╞ ╞ ╞ abort╞ abort↲
╞ checkpoint=0 *2)╞ ╞ ╞ switch on╞ switch off↲
╞ or service=TLX↲
↲
↲
╞ CONF.REGRET╞ submit╞ submit↲
╞ result=ok╞ ╞ switch on╞ switch off↲
↲
24c↲
╞ ╞ ╞ CONF.SUBMIT↲
╞ ╞ ╞ result=not_proc↲
↲
↲
╞ ╞ ╞ regret switch on↲
╞ regret switch↲
╞ off↲
↲
20a ╞ ╞ CONF.REGRET╞ ╞ ╞ 28a↲
╞ CONF.ABORT╞ result= not proc↲
╞ result=ok↲
════════════════════════════════════════════════════════════════════════
↓
┆0e┆↓
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Table 27.↲
↲
╞ ┆a1┆state ! event ! action ! new state ↲
╞ wait error ! ! !↲
╞ source ! REQ.ABORT ! - ! -↲
┆a1┆ writes ! ! !╞ ╞ ↲
╞ wait error !╞ !╞ !↲
╞ source╞ ! REQ.REGRET ! -╞ ! -╞ ╞ ↲
╞ ┆a1┆ writes╞ !╞ !╞ !╞ ╞ ↲
wait error ! ! !↲
source ! TU removed ! - ! 20a↲
╞ ┆a1┆┆e1┆ writes ! ! !╞ ╞ ↲
& wait ! ! !↲
╞ abort ! ! !↲
┆a1┆ updates ! ! !╞ ↲
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 27, footnotes.↲
↲
╞ *1) ┆84┆The document description read becomes the current document ↓
┆19┆┆8d┆┄┄des┄cription. If service=TLX the checkpoint will be set to ↓
┆19┆┆8d┆┄┄zero, and finished to false.↲
↲
╞ *2) ┆84┆If service=TTX and checkpoint in the document description is ↓
┆19┆┆8d┆┄┄equal to 0, an regret can be regarded as successful.↲
↲
╞ *3) ┆84┆Finished from the current document description. The document ↓
┆19┆┆8d┆┄┄has been fully transmitted.↲
↲
╞ *4) read seq no is set to doc seq no +1.↲
↲
╞ *5) It is a REQ.REGRET which is being executed.↲
↲
╞ *6) ┆84┆The regret has not yet been performed (error recovery should ↓
┆19┆┆8d┆┄┄be made).↲
↲
╞ *7) ┆84┆The packet has been fully transmitted before the error oc┄↓
┆19┆┆8d┆┄┄curred.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆6.4.4.9╞ Encapsulation Handling↲
↲
╞ ┆84┆This section describes packet error recovery, which is shown in ↓
┆19┆┆89┆┄┄fig. 28.↲
↲
╞ ┆84┆Entry, via 28a, is done when one of the the following events have ↓
┆19┆┆89┆┄┄happened:↲
↲
╞ - document stream break down↲
╞ - EXCEPT IND received↲
╞ - prio break occurred↲
╞ - CAP CONF NEG received↲
╞ - answ SESS START REQ,result=busy has occurred↲
╞ - SESS START CONF NEG received↲
╞ - ABORT IND received↲
↲
╞ ┆84┆To decide what should be done, the DH uses the information in the ↓
┆19┆┆89┆┄┄"error inf" field, see chapter 7.↓
↲
╞ ┆84┆The entry point 28b is used when a REQ.REGRET should be terminated ↓
┆19┆┆89┆┄┄with result = ok.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31400000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
╞ fig. 28. Encapsulation handling.↲
↲
↲
╞ ╞ ╞ 28a↲
↲
↲
╞ ╞ service=TTX╞ ╞ service=TLX↲
╞ ╞ or╞ ╞ ╞ &↲
╞ ╞ doc seq no=1╞ ╞ doc seq no<>1↲
╞ ╞ ╞ ╞ ╞ *4)↲
↲
↲
╞ ╞ test encapsulation↲
╞ ╞ *1)↲
↲
↲
↲
╞ ╞ encapsulation *2)╞ giveup↲
↲
↲
↲
╞ ╞ encapsulated╞ submit╞ ╞ submit↲
╞ ╞ ╞ ╞ switch on╞ ╞ switch off↲
↲
↲
╞ ╞ ╞ CONF.SUBMIT *3) CONF.REGRET *3)↲
╞ ╞ timeout╞ result=term result result=term result↲
↲
↲
↲
╞ service=TTX╞ service=TLX↲
↲
↲
↲
╞ 20b╞ ╞ 20c╞ 24b╞ ╞ 20a↲
════════════════════════════════════════════════════════════════════════
↓
╞ Table 28.↲
↲
↲
╞ ┆a1┆state╞ ╞ ! event╞ ╞ ! action╞ ! new state↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ ┆a1┆encapsulated╞ ! REQ.ABORT╞ ! -╞ ! 27a╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ encapsulated╞ ! REQ.REGRET╞ !╞ !↲
╞ ┆a1┆╞ ╞ ! service=TLX╞ ! -╞ ! 27a╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ encapsulated╞ ! REQ.REGRET╞ ! -╞ ! 20b *5)↲
╞ ╞ ╞ ! service=TTX╞ !╞ !↲
╞ ┆a1┆╞ ╞ ! & doc seq no=1╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ encapsulated╞ ! REQ.REGRET╞ ! -╞ ! -↲
╞ ╞ ╞ ! service=TTX╞ !╞ !↲
╞ ┆a1┆╞ ╞ ! & doc seq no<>1╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ ┆a1┆encapsulated╞ ! TU removed╞ ! -╞ ! 20a╞ ↲
↲
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ fig. 28, footnotes.↲
↲
╞ *1) ┆84┆This stands for the following algorithme: Using the user inf ↓
┆19┆┆8d┆┄┄field in the packet description, a lookup is performed in the ↓
┆19┆┆8d┆┄┄submit_error_table described in section 8.3. This will deliver ↓
┆19┆┆8d┆┄┄two values a retries count and a retry timer. ↲
↲
╞ ┆84┆The following is done:↲
↲
╞ ┆84┆If user inf=error inf (the same error two times in a row), ↓
┆19┆┆8d┆┄┄retries left will be decreased with one. Otherwise is retries ↓
┆19┆┆8d┆┄┄left set to retries count.↲
↲
╞ ┆84┆After that is error inf set to user inf, and retry timer is ↓
┆19┆┆8d┆┄┄added to retry timer sum.↲
↲
╞ ┆84┆The following possibilities then arises:↲
↲
a) ┆84┆retries left =0↲
╞ The pseudo event giveup is performed.↲
↲
╞ b) ┆84┆retry timer sum>= max retry timer (see section 8.3)↲
╞ ┆84┆giveup is performed.↲
↲
╞ c) ┆84┆Otherwise the pseudo event encapsulation is performed.↲
↲
┆8c┆┆83┆┆e4┆↓
╞ ┆84┆The following should be noted, however:↲
↲
╞ (a) ┆84┆If user inf indicates prio break, a retry timer=0 is used ↓
┆19┆┆91┆┄┄giving an immediate retry (which probably will cause the ↓
┆19┆┆91┆┄┄packet to enter the busy queue).↲
↲
╞ (b) ┆84┆If the error was a SESS START CONF NEG with rej_reason= ↓
┆19┆┆91┆┄┄address_enc, the retry timer is given in the SESS START ↓
┆19┆┆91┆┄┄CONF NEG. (The wait_time parameter).↲
↲
╞ (c) ┆84┆If the error was a answ SESS START REQ with result=busy, ↓
┆19┆┆91┆┄┄the retry timer value from submit_error_table is not used, ↓
┆19┆┆91┆┄┄but a short timer value, busy_retry_timer (see section ↓
┆19┆┆91┆┄┄8.3).↲
↲
╞ ┆84┆the reason for this is that the session resources should ↓
┆19┆┆91┆┄┄be configurated alike in DH and S62CP. A busy answer must ↓
┆19┆┆91┆┄┄therefore be due to the following situation.↲
┆0e┆↓
↲
╞ DH╞ ╞ ╞ S62CP↲
↲
↲
╞ ╞ ╞ ╞ ╞ ╞ incoming call↲
↲
╞ ╞ SESS START REQ↲
↲
↲
↲
╞ ╞ answ SESS START REQ↲
╞ ╞ result=busy↲
↲
↲
┆0f┆↓
↲
╞ ┆84┆The busy_retry timer should be just long enough for the ↓
┆19┆┆91┆┄┄incoming call to reach DH. (If it is not rejected by ↓
┆19┆┆91┆┄┄S62CP).↲
↲
╞ *2) ┆84┆A timer is started with the duration retry_timer.↲
↲
┆8c┆┆83┆┆d4┆↓
╞ *3) ┆84┆Term result is decided from user inf in the following way:↲
↲
╞ - = pers_err if if document stream break down has occurred↲
- = ┆84┆rec unknown if SESS START CONF NEG was received with rej ↓
┆19┆┆91┆┄┄reason = rec unkn↲
╞ - = ill fac if a CAP CONF NEG was received↲
╞ - = failed otherwise.↲
↲
╞ *4) ┆84┆The control document has been sent and acknowledged. ↓
┆19┆┆8d┆┄┄Retransmission is not allowed.↲
↲
╞ *5) ┆84┆An immediate retry is performed. This is done because the ↓
┆19┆┆8d┆┄┄encapsulation could have been done for reasons not related to ↓
┆19┆┆8d┆┄┄a discard (f.ex EXCEPTION IND caused by lack of resources at ↓
┆19┆┆8d┆┄┄the receiver).↲
↲
┆b0┆┆a1┆6.5╞ Packet Sink Handling↲
↲
╞ ┆84┆This section describes the part of the packet protocol machine, ↓
┆19┆┆89┆┄┄which handles packet receival, terminated with IND.DELIVER or ↓
┆19┆┆89┆┄┄IND.CANCEL. As for packet source handling, a packet description ↓
┆19┆┆89┆┄┄will be allocated. The allocation will here be performed by a ↓
┆19┆┆89┆┄┄session, which has received a DOC START IND or a DOC CONT IND.↲
↲
↲
┆b0┆┆a1┆6.5.1 ╞ Packet Descriptor Content for Sink States↲
↲
╞ ┆84┆See section 6.4.1. Many of the fields are the same, and here are ↓
┆19┆┆89┆┄┄mentioned those which are important to the protocol machine. ↓
↲
╞ service ╞ ╞ : TTX or TLX↲
╞ cur doc dcr╞ : the same↲
╞ doc seq no╞ : the same↲
╞ outstanding writes╞ : the same↲
╞ outstanding read╞ : the same↲
╞ DH close pending╞ : the same↲
╞ user inf╞ ╞ : the same↲
↲
┆8c┆┆83┆┆c8┆↓
┆0e┆↓
╞ Concerning the document description:↲
↲
╞ document number╞ : the same↲
╞ S62 document id╞ : the same↲
╞ checkpoint no╞ : ┆84┆The last checkpoint number acknowledged from ↓
┆19┆┆9f┆┄┄this side (CHECKPOINT received on the ↓
┆19┆┆9f┆┄┄document stream)↲
╞ finished╞ ╞ : ┆84┆= true if DOCUMENT END IND has been received↲
╞ continuation╞ : ┆84┆= true if the packet was initialized by a ↓
┆19┆┆9f┆┄┄DOCUMENT CONT IND i.e. the DH was unable to ↓
┆19┆┆9f┆┄┄perform document linkage.↲
┆0f┆↓
↲
↲
┆b0┆┆a1┆6.5.2╞ Packet Sink Events↲
↲
╞ Document level events from S62CP:↲
↲
╞ ┆84┆- DOCUMENT START IND, abr. DOC START IND↲
╞ Start of a document receival.↲
↲
╞ - DOCUMENT CONTINUE IND, abr. DOC CONT IND↲
╞ Continuation of an earlier interrupted document receival↲
↲
╞ - DATA IND↲
╞ An amount of document data↲
↲
╞ - PAGE END IND↲
╞ A checkpoint in the document↲
↲
╞ - DOCUMENT END IND, abr. DOC END IND↲
╞ End of document receival.↲
↲
╞ - DOCUMENT DISCARD IND abr DOC DISC IND↲
╞ ┆84┆Request for cancellation of the already received part of the ↓
┆19┆┆8b┆┄┄document.↲
↲
╞ - DOCUMENT RESYNCHRONIZE IND, abr. DOC RESYNC IND↲
╞ Temporarily interruption of a document receival.↲
↲
┆8c┆┆83┆┆d4┆↓
╞ - answ DOC END RESP↲
╞ ┆84┆Answer from S62CP on a DOC END RESP message. It is assumed ↓
┆19┆┆8b┆┄┄(through not explicit stated in ref. 4) that this answer ↓
┆19┆┆8b┆┄┄signifies that all messages concerning this document are home ↓
┆19┆┆8b┆┄┄from S62CP↲
↲
╞ - answ DOC RESYNC-DISC RESP↲
╞ ┆84┆Answer on a DOC RESYNC-DISC RESP message. The same assumption as ↓
┆19┆┆8b┆┄┄for DOC END RESP is made.↲
↲
╞ Session level event from S62CP.↲
↲
╞ - SESSION ABORT IND, abr. SESS ABORT IND↲
╞ An abnormal session break down.↲
↲
╞ - SESSION END IND, abr. SESS END IND↲
╞ ┆84┆Normal session termination. Received by the packet when ↓
┆19┆┆8b┆┄┄service=TLX.↲
↲
╞ DS events:↲
↲
╞ - RESPONCE.DELIVER, abr. RESP.DELIVER↲
↲
╞ - RESPONCE.INITIATE, abr. RESP.INIT↲
╞ ┆84┆A document description has been created.↲
↲
╞ - RESPONCE.READ, abr. RESP.READ↲
↲
╞ - RESPONCE.WRITE, abr. RESP.WRITE↲
↲
╞ document stream events:↲
↲
╞ - REPLY OK↲
╞ Responce on a TRANSFER(write)↲
↲
╞ - REPLY NOT OK↲
╞ DS indicates that document stream troubles has occurred.↲
↲
┆8c┆┆83┆┆c8┆↓
┆0e┆↓
╞ - CHECKPOINT↲
╞ Acknowledge on a CHECKPOINT from DH. The page is stored at DS.↲
┆0f┆↓
↲
╞ - STREAM END↲
╞ ┆84┆Acknowledge on a STREAM END from DH. The whole document is ↓
┆19┆┆8b┆┄┄stored at DS.↲
↲
╞ - TTXSI stream close↲
╞ Request from TTXSI for termination of the document stream.↲
↲
╞ - answ DH stream close↲
╞ ┆84┆Answer on a DH stream close. The document stream is terminated, ↓
┆19┆┆8b┆┄┄and all pending buffers on the stream are home.↲
↲
↲
╞ special events:↲
↲
╞ - TU removed↲
╞ A TU removal procedure has been initiated.↲
↲
╞ - stream protocol err↲
╞ A protocol error has occurred on a document stream.↲
↲
╞ - sess queued↲
╞ ┆84┆A session had received a DOC CONT IND referring to this packet. ↓
┆19┆┆8b┆┄┄The session is placed in the packet session queue.↲
↲
↲
┆b0┆┆a1┆6.5.3╞ Packet Sink Actions↲
↲
╞ Document level actions against S62CP:↲
↲
╞ - DOCUMENT START/CONT RESP POS, abr DOC START-CONT RESP POS↲
╞ ┆84┆Positive acknowledge of a DOC START IND or a DOC CONT IND.↲
↲
╞ - DOCUMENT CONTINUE RESP NEG, abr DOC CONT RESP NEG↲
╞ ┆84┆Rejection of a DOC CONT IND. (Forward jump in reference ↓
┆19┆┆8b┆┄┄numbers).↲
↲
┆8c┆┆83┆┆d4┆↓
╞ - PAGE END RESP↲
╞ ┆84┆A checkpoint has been stored and the document description has ↓
┆19┆┆8b┆┄┄been updated, both at DS.↲
↲
╞ - DOCUMENT END RESP↲
╞ The whole document has been stored at DS.↲
↲
╞ - EXCEPTION REQ, abr EXCEPT REQ↲
╞ ┆84┆Request for a premature interruption of the document receival.↲
↲
╞ - DOCUMENT RESYNCH/DISC RESP, abr. DOC RESYNC-DISC RESP↲
╞ Responce on a DOC DISC IND or a DOC RESYNC IND.↲
↲
↲
╞ actions agains DH:↲
↲
╞ - INDICATION.CREATE, abr. IND.CREATE↲
╞ ┆84┆Creation of a receival packet.↲
↲
╞ - INDICATION.DELIVER, abr. IND.DELIVER↲
╞ ┆84┆Termination of a receival packet.↲
↲
╞ - INDICATION.CANCEL, abr. IND.CANCEL↲
╞ Termination of a receival packet consisting only of a discard.↲
↲
╞ - INDICATION.INITIATE, abr. IND.INIT↲
╞ Request for creation of a document description at DS.↲
↲
╞ - INDICATION.READ, abr. IND.READ↲
↲
╞ - INDICATION.WRITE, abr. IND.WRITE↲
↲
╞ document stream actions:↲
↲
╞ - TRANSFER(write)↲
╞ A TRANSFER block with mode=w. Opens a document stream.↲
↲
╞ - STREAM↲
╞ An amount of document data.↲
↲
┆8c┆┆83┆┆e0┆↓
╞ - CHECKPOINT↲
╞ Indicates end of a page.↲
↲
╞ - STREAM END↲
╞ Indicates end of a document↲
↲
↲
╞ special actions:↲
↲
╞ - reject call↲
╞ ┆84┆A responce on a sess queued event, when it has occurred in an ↓
┆19┆┆8b┆┄┄illegal state. The corresponding event is generated in the ↓
┆19┆┆8b┆┄┄session.↲
↲
╞ - doc level exit↲
╞ ┆84┆The packet disconnects itself from the session after the ↓
┆19┆┆8b┆┄┄document level has been left. The corresponding event is ↓
┆19┆┆8b┆┄┄performed in the session.↲
↲
╞ - start sess clear↲
╞ ┆84┆The packet is disconnected from the session before SESS CLEAR ↓
┆19┆┆8b┆┄┄IND has been received. No document stream is open or being ↓
┆19┆┆8b┆┄┄closed. The corresponding event is generated in the session.↲
↲
╞ - TU rem sess clear↲
╞ ┆84┆As start sess clear, but a TU removal procedure has been ↓
┆19┆┆8b┆┄┄started.↲
↲
┆b0┆┆a1┆6.5.4╞ Packet Sink, Protocol machine↲
↲
╞ ┆84┆In this section is the packet sink protocol machine shown in ↓
┆19┆┆89┆┄┄detail.↲
↲
╞ Each subsection will contain one figure.↲
↲
↲
┆8c┆┆83┆┆b0┆↓
┆0e┆↓
┆a1┆┆b0┆6.5.4.1╞ Packet Sink, Initialization↲
↲
╞ ┆84┆The states here, shown in fig. 29, handles packet initialization ↓
┆19┆┆89┆┄┄in sink mode.↲
↲
╞ ┆84┆DOC START IND or a DOC CONT IND has been received and the packet ↓
┆19┆┆89┆┄┄has been allocated by the session.↲
↲
╞ Fig. 29 has the entry points:↲
↲
╞ 29a: return to packet idle state↲
↲
╞ 29b: ┆84┆Entry when a DOC CONT IND was received to an existing packet.↲
↲
╞ 29c: ┆84┆Used in TLX mode when a DOC START IND has been received, and ↓
┆19┆┆8e┆┄┄the corresponding document is not the first in the packet. A ↓
┆19┆┆8e┆┄┄new document description is being created.↲
┆0f┆↓
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 29, Packet sink, initialization.↲
↲
↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ 29a↲
╞ ╞ ╞ ╞ packet↲
╞ ╞ ╞ ╞ idle↲
↲
↲
╞ ╞ DOC START IND/IND.CREATE↲
╞ ╞ *1)╞ ╞ ╞ DOC CONT IND/IND.CREATE↲
╞ ╞ ╞ ╞ ╞ *2)↲
↲
↲
╞ ╞ ╞ ╞ creating↲
↲
↲
↲
╞ ╞ RESP.CREATE╞ ╞ RESP.CREATE IND.INIT↲
╞ ╞ result=busy╞ ╞ result=ok↲
↲
↲
↲
╞ SESS ABORT REQ↲
╞ start sess clear↲
↲
29c╞ ╞ ╞ ╞ initiating↲
↲
↲
↲
╞ ╞ RESP.INIT╞ ╞ ╞ RESP.INIT IND.WRITE↲
╞ ╞ result=busy╞ ╞ result=ok *3)↲
↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ 29b↲
╞ SESS ABORT REQ↲
╞ start sess clear╞ ╞ ╞ ╞ *4)↲
╞ IND.DELIVER ,result=↲
╞ ╞ failed╞ ╞ ╞ checkpoint↲
╞ ╞ ╞ ╞ ╞ ok↲
↲
╞ ╞ ╞ ╞ ╞ ╞ checkpoint↲
31b╞ ╞ ╞ ╞ IND.WRITE╞ ╞ failure↲
╞ ╞ ╞ ╞ *5)↲
↲
↲
╞ ╞ ╞ ╞ def╞ DOC CONT RESP NEG↲
╞ ╞ ╞ doc dcr↲
↲
╞ ╞ ╞ ╞ ╞ ╞ 33a↲
╞ ╞ ╞ RESP.WRITE↲
↲
↲
╞ ╞ ╞ TRANSFER(write) *6)↲
↲
↲
╞ ╞ ╞ ╞ 30a↲
════════════════════════════════════════════════════════════════════════
↓
╞ Table 29.↲
↲
↲
┆0e┆↓
╞ ┆a1┆state ! event ! action ! new state ↲
╞ ! ! !↲
╞ creating ! SESS ABORT ! start sess ! 34c↲
┆a1┆ ! IND ! clear !╞ ╞ ↲
! ! ! ↲
initiating ! SESS ABORT ! start sess ! 34b↲
┆a1┆ ! IND ! clear ! ↲
! ! !↲
def doc dcr! SESS ABORT ! start sess ! 34a↲
┆a1┆ ! IND ! clear ! ↲
creating ! ! !↲
! TU removed ! SESS ABORT ! packet idle↲
╞ &initiating! ! REQ !↲
& def doc ! ! TU rem !↲
╞ ┆a1┆ d┆a1┆cr ! ! sess clear! ↲
┆0f┆↓
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 29, footnotes↲
↲
╞ *1) ┆84┆The doc_id field in the document decription is set according ↓
┆19┆┆8d┆┄┄to the parameters in DOC START IND. doc seq no is set to 1. ↓
┆19┆┆8d┆┄┄continuation and finished is set to false.↲
↲
╞ *2) ┆84┆As *1), but continuation is set to true. Linkage of the ↓
┆19┆┆8d┆┄┄document cannot be performed by DH.↲
↲
╞ *3) ┆84┆The document number field is set according to the document no ↓
┆19┆┆8d┆┄┄parameter in RESP.INIT. The now fully updated document ↓
┆19┆┆8d┆┄┄description is written back at DS.↲
↲
╞ *4) ┆84┆Here is checked that no forward jump in the checkpoint number ↓
┆19┆┆8d┆┄┄is made.↲
↲
╞ *5) ┆84┆the document description with the updated checkpoint number is ↓
┆19┆┆8d┆┄┄written back at DS.↲
↲
╞ *6) ┆84┆the parameter is set thus:↲
↲
╞ Mode=W↲
╞ document : ┆84┆the document number from the document ↓
┆19┆┆9a┆┄┄description.↲
╞ checkpoint : ┆84┆the checkpoint field from the document ↓
┆19┆┆9a┆┄┄description.↲
┆8c┆┆83┆┆d4┆↓
╞ reservation: ┆84┆the res_no field from the connected session.↲
╞ header : ┆84┆contains the capabilities received in DOC START ↓
┆19┆┆9a┆┄┄IND and DOC CONT IND.↲
↲
↲
┆b0┆┆a1┆6.5.4.2╞ Packet Sink, Normal Operation↲
↲
╞ ┆84┆In fig 30 is described receival of a document, terminated by ↓
┆19┆┆89┆┄┄sending a DOC END RESP.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 30, Packet Sink, normal operation.↲
↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
╞ ╞ ╞ 30a↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ sink reply↲
╞ ╞ ╞ ok↲
↲
↲
╞ ╞ REPLY OK/DOC START-CONT RESP POS↲
↲
↲
╞ ╞ ╞ ╞ ╞ RESP.WRITE/PAGE END RESP↲
PAGE END IND/CHECKPOINT╞ ╞ ╞ ╞ *2)↲
╞ ╞ ╞ doc sink↲
↲
↲
CHECKPOINT/IND.WRITE╞ ╞ ╞ DOC END IND/STREAM END↲
*1)↲
↲
↲
╞ ╞ STREAM END/IND.WRITE↲
╞ ╞ *3)↲
↲
↲
╞ ╞ ╞ ╞ RESP.WRITE PAGE END↲
╞ ╞ ╞ term╞ (not last) RESP↲
╞ ╞ ╞ doc sink↲
↲
↲
↲
╞ ╞ RESP.WRITE(last)/DH stream close↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ doc sink↲
╞ ╞ ╞ close↲
↲
↲
↲
╞ ╞ answ DH stream close/DOC END RESP↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ doc level↲
╞ ╞ ╞ exit↲
↲
↲
╞ ╞ answ DOC END RESP *4)↲
↲
↲
╞ ╞ ╞ 31a↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆0e┆↓
╞ Table 30↲
↲
╞ ┆a1┆state ╞ ! event ╞ ! action ! new state↲
╞ wait sink ╞ !REPLY NOT OK╞ ! DOC START-!↲
╞ reply ok ╞ !& stream protocol╞ ! CONT RESP! 32a↲
╞ ╞ ! err╞ ╞ ! POS !↲
╞ ╞ ╞ !& TTXSI stream╞ ! EXCEPT REQ!↲
╞ ╞ ! close╞ ╞ ! DH stream !↲
┆a1┆ ╞ ! ╞ ! close ! ↲
╞ !REPLY NOT OK╞ ! EXCEPT REQ!↲
doc sink ╞ !& stream ╞ ! DH stream ! 32a↲
╞ ╞ ! protocol err╞ ! close !↲
╞ ╞ !& TTXSI ╞ ! !↲
┆a1┆ ╞ ! stream close╞ ! ! ↲
╞ term doc sink╞ !stream protocol err! EXCEPT REQ! 32a↲
╞ ╞ ╞ !╞ ╞ ! DH stream !↲
╞ ┆a1┆╞ ╞ !╞ ╞ ! close╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ ┆a1┆wait doc sink close !stream protocol err! EXCEPT REQ! 32a ↲
term doc sink ╞ ! ╞ ! ! ↲
& wait╞ ╞ ! TTXSI stream close! - ! -↲
╞ ┆a1┆ doc sink close╞ ! ╞ ! !╞ ↲
╞ ╞ ! ╞ ! !↲
╞ doc sink ╞ ! DOC RESYNC╞ ! DH stream ! 32b↲
╞ ┆a1┆& term doc sink ╞ ! IND╞ ╞ ! close ! ↲
╞ wait doc sink ╞ !╞ ╞ !╞ !↲
╞ close╞ ╞ ! DOC RESYNC╞ ! -╞ ! 32b↲
╞ & wait doc level╞ ! IND╞ ╞ !╞ !↲
╞ ┆a1┆ exit╞ ╞ !╞ ╞ !╞ !╞ ↲
╞ wait doc sink close╞ ! ╞ ! !↲
╞ & wait doc level ! DOC DISC IND╞ ! -╞ ! 32c↲
╞ ┆a1┆ exit╞ ╞ !╞ ╞ !╞ ! ↲
╞ & doc sink ╞ ! DOC DISC ╞ ! DH stream ! 32c↲
╞ ┆a1┆& term doc sink ! IND ╞ ! close ! ↲
╞ wait sink reply ok╞ !╞ ╞ !╞ !↲
╞ & doc sink╞ !╞ ╞ ! DH stream !↲
╞ ┆a1┆& term doc sink╞ ! SESS ABORT IND╞ ! close ! 33a ↲
╞ & wait doc sink╞ !╞ ╞ ! ╞ !↲
╞ close╞ ╞ ! SESS ABORT IND╞ ! -╞ ! 33a↲
╞ & wait doc level╞ !╞ ╞ !╞ !↲
╞ ┆a1┆ exit╞ ╞ !╞ ╞ !╞ !╞ ↲
╞ wait sink reply ok !╞ ╞ !╞ !↲
╞ & doc sink╞ !╞ ╞ !╞ !↲
╞ & term doc sink╞ ! sess queued╞ !reject call! -↲
╞ & wait doc sink╞ !╞ ╞ !╞ !↲
╞ close╞ ╞ !╞ ╞ !╞ !↲
╞ & wait doc level╞ !╞ ╞ !╞ !↲
╞ ┆a1┆ exit╞ ╞ !╞ ╞ !╞ !╞ ↲
╞ wait sink reply ok╞ !╞ ╞ ! SESS ABORT!↲
╞ & doc sink╞ !╞ ╞ ! REQ╞ !↲
╞ & term doc sink╞ ! TU removed╞ ! DH stream ! 35a↲
╞ ┆a1┆╞ ╞ !╞ ╞ ! close╞ ! ╞ ↲
╞ wait doc sink╞ !╞ ╞ !╞ !↲
╞ close╞ ╞ !╞ ╞ ! SESS ABORT!↲
╞ & wait doc level╞ ! TU removed╞ ! REQ╞ ! 35a↲
╞ ┆a1┆ exit╞ ╞ !╞ ╞ !╞ !╞ ↲
┆0f┆↓
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
┆81┆╞ Fig. 30, footnotes↲
↲
╞ *1) ┆84┆Confirms that a CHECKPOINT block has been received by DS. The ↓
┆19┆┆8d┆┄┄checkpoint field in the document description is updated ↓
┆19┆┆8d┆┄┄accordingly.↲
↲
╞ *2) ┆84┆the document description is now updated at DS. The receival of ↓
┆19┆┆8d┆┄┄the page can now be confirmed against the remote party.↲
↲
╞ *3) ┆84┆Confirms that the STREAM END block has been received by DS. ↓
┆19┆┆8d┆┄┄The checkpoint field in the document description is updated ↓
┆19┆┆8d┆┄┄accordingly, and the finished field is set to true.↲
↲
╞ *4) ┆84┆All messages from this packet pending at S62CP is home. A ↓
┆19┆┆8d┆┄┄possible pending TTXSI stream close is returned.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆6.5.4.3╞ Packet Sink, Termination.↲
↲
╞ ┆84┆This section describes normal packet termination, ending with ↓
┆19┆┆89┆┄┄IND.DELIVER. There are two entry points:↲
↲
╞ 31a: ┆84┆normal entry. a document has been received and stored.↲
↲
╞ 31b: ┆84┆Used in all cases where an IND.DELIVER has been sent. ↓
┆19┆┆8e┆┄┄RESP.DELIVER is awaited.↓
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 31, Packet sink, termination.↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ 31a↲
↲
↲
↲
╞ service=TTX╞ service=TLX *1)↲
↲
↲
↲
doc level exit↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ next doc↲
↲
↲
↲
╞ ╞ SESS END IND╞ ╞ DOC START IND↲
╞ ╞ ╞ ╞ ╞ *2)↲
↲
╞ ╞ start sess clear↲
↲
↲
↲
╞ IND.DELIVER╞ ╞ doc seq no>2╞ doc seq no<=2↲
╞ result=ok╞ ╞ *3)↲
↲
↲
↲
31b╞ ╞ wait↲
╞ ╞ deliver╞ ╞ SESS ABORT REQ╞ IND.INIT↲
╞ ╞ answ╞ start sess clear╞ (next doc dcr)↲
↲
↲
↲
↲
╞ ╞ RESP.DELIVER↲
↲
↲
↲
╞ ╞ 29a╞ ╞ 34a╞ ╞ 29c↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆0e┆↓
╞ Table 31.↲
↲
╞ ┆a1┆state ! event ! action ╞ ! new state ↲
╞ ! ! ╞ !↲
╞ wait next ! sess queued! reject call╞ ! -↲
┆a1┆doc ! ! ╞ ! ╞ ↲
! ! ╞ !↲
wait next ! SESS ABORT ! start sess╞ ! wait deliver answ↲
doc ! IND ! clear ╞ ! *4) ↲
╞ ╞ !╞ ! IND.DELIVER╞ !↲
╞ ┆a1┆╞ !╞ ! result=ok╞ !╞ ↲
! ! ╞ ! ↲
wait next ! DOC CONT !SESS ABORT ╞ ! 33a↲
┆a1┆doc ! IND ! REQ ╞ ! ↲
! ! ╞ !↲
wait next ! TU removed !SESS ABORT ╞ ! 35a↲
┆a1┆doc ! ! REQ ╞ ! ↲
! ! ╞ !╞ ↲
wait deli- ! TU removed ! - ╞ ! 29a↲
┆a1┆ver answ ! ! ╞ ! ↲
┆0f┆↓
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 31, Footnotes.↲
↲
╞ *1) A new document can be received inside the same packet.↲
↲
╞ *2) ┆84┆the doc id field in the document description is set according ↓
┆19┆┆8d┆┄┄to the parameters in DOC START IND. doc seq no in the packet ↓
┆19┆┆8d┆┄┄description is increased with one.↲
↲
╞ *3) ┆84┆This is an error, because at most two documents (the control ↓
┆19┆┆8d┆┄┄document and the normal document) can be transferred in one ↓
┆19┆┆8d┆┄┄session.↲
╞ ┆84┆Note that the packet has remained in possession of the ses┄↓
┆19┆┆8d┆┄┄sion, even if the two documents have been received. Receival ↓
┆19┆┆8d┆┄┄of a DOC START IND is not a new packet in this case, but a ↓
┆19┆┆8d┆┄┄proce┄dural error.↲
↲
╞ *4) ┆84┆It is for futher study if this is right. It depends on how ↓
┆19┆┆8d┆┄┄long the conversion unit is able to retransmit a packet.↲
↲
┆8c┆┆83┆┆98┆↓
┆0e┆↓
┆b0┆┆a1┆6.5.4.4╞ Resynchronize/Discard Handling, Sink↲
↲
╞ ┆84┆This section handles errors where the document level can be left ↓
┆19┆┆89┆┄┄in an orderly manner. The protocol machine is shown in fig. 32.↲
↲
╞ This figure has three entry points:↲
↲
╞ 32a: ┆84┆an EXCEPT REQ has been sent due to document stream troubles. ↓
┆19┆┆8e┆┄┄The reaction from the other side is awaited.↲
↲
╞ 32b: A DOC RESYNC IND has been received.↲
↲
╞ 32c: A DOC DISC IND has been received.↲
↲
╞ ┆84┆In all this cases will a DH stream close have been sent.↲
↲
┆0f┆↓
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 32. Resynchronize/discard handling, sink↲
↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ 32b╞ ╞ 32a╞ ╞ 32c↲
↲
↲
╞ service=TLX╞ ╞ service=TLX╞ sevice=TLX↲
↲
↲
↲
╞ ╞ ╞ ╞ ╞ ╞ SESS ABORT REQ↲
↲
↲
↲
╞ service=TTX╞ service=TTX╞ service=TTX 33a╞ ↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ resync↲
↲
↲
╞ ╞ ╞ ╞ DOC DISC IND↲
↲
╞ ╞ DOC RESYNC IND↲
↲
╞ ╞ ╞ ╞ checkpoint=0 *3)↲
↲
↲
↲
╞ ╞ ╞ sync↲
╞ ╞ ╞ close↲
╞ ╞ ╞ *1)↲
↲
↲
↲
╞ ╞ answ DH stream close/DOC RESYNC-DISC RESP↲
↲
↲
↲
╞ ╞ ╞ sync↲
╞ ╞ ╞ doc exit↲
↲
↲
↲
╞ ╞ answ DOC RESYNC-DISC RESP *2)↲
↲
↲
╞ ╞ doc level exit↲
↲
↲
↲
↲
╞ ╞ ╞ 34a↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆0e┆↓
╞ Table 14↲
↲
╞ ┆a1┆state╞ ╞ ! event╞ ╞ ! action╞ ! new state↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ !╞ ╞ !╞ !↲
╞ & sync close╞ ! RESP.WRITE╞ ! -╞ ! -↲
╞ ┆a1┆& sync doc exit ╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ ! document stream╞ ! -╞ ! -↲
╞ & sync close╞ ! messages different!╞ !↲
╞ ╞ ╞ ! from TTXSI stream !╞ !↲
╞ ┆a1┆╞ ╞ ! close╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ ! TTXSI stream close! -╞ ! -↲
╞ ┆a1┆& sync close╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ ! S62CP document╞ !╞ !↲
╞ ╞ ╞ ! level messages╞ ! -╞ ! -↲
╞ ╞ ╞ ! different from╞ !╞ !↲
╞ ╞ ╞ ! DOC RESYNC IND╞ !╞ !↲
╞ ┆a1┆╞ ╞ ! and DOC DISC IND╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ ! answ DH stream╞ ! -╞ ! -↲
╞ ┆a1┆╞ ╞ ! close╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ !╞ ╞ !╞ !↲
╞ & sync close╞ ! sess queued╞ ! reject call! -↲
╞ ┆a1┆& sync doc exit╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ ! TU removed╞ ! SESS ABORT ! 35a↲
╞ & sync close╞ !╞ ╞ ! REQ╞ !↲
╞ ┆a1┆& sync doc exit╞ !╞ ╞ !╞ !╞ ↲
╞ ╞ ╞ !╞ ╞ !╞ !↲
╞ wait resync╞ !╞ ╞ !╞ !↲
╞ & sync close╞ ! SESS ABORT IND╞ ! -╞ ! 33a↲
╞ ┆a1┆& sync doc exit╞ !╞ ╞ !╞ !╞ ↲
┆0f┆↓
↲
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 32, footnotes.↲
↲
╞ *1) ┆84┆If DH close pending is false, answ DH stream close is ↓
┆19┆┆8d┆┄┄simulated.↲
↲
╞ *2) ┆84┆All messages pending at S62CP are home. A possible pending ↓
┆19┆┆8d┆┄┄TTXSI stream close is returned.↲
↲
╞ *3) ┆84┆Checkpoint number in the document description is set to zero. ↓
┆19┆┆8d┆┄┄This will force an erase of the description at DS later on. ↓
┆19┆┆8d┆┄┄Therefore is no IND.WRITE sent.↲
↲
↲
┆8c┆┆83┆┆d8┆↓
┆b0┆┆a1┆6.5.4.5╞ Session Break Down Handling, sink↲
↲
╞ ┆84┆This section describes fig. 33, which handles cases where a ↓
┆19┆┆89┆┄┄session break down has occurred and the document stream was not ↓
┆19┆┆89┆┄┄terminated.↲
↲
╞ ┆84┆The entry point is 33a. One of the following events has occurred:↲
↲
╞ - A SESS ABORT IND has been received.↲
↲
╞ - ┆84┆document stream troubles, a DOC RESYNC IND or a DOC DISC IND has ↓
┆19┆┆8b┆┄┄occurred, all in with service=TLX. A SESS ABORT REQ has been ↓
┆19┆┆8b┆┄┄sent.↲
↲
╞ - ┆84┆Too many documents or DOC CONT IND received by service=TLX. SESS ↓
┆19┆┆8b┆┄┄ABORT REQ has been sent.↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 33, Error handling, sink↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ ╞ ╞ 33a↲
↲
↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ sink clear↲
╞ ╞ ╞ ind↲
↲
↲
↲
↲
╞ ╞ SESS CLEAR IND↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ sink bufs↲
╞ ╞ ╞ *2)↲
↲
↲
↲
╞ ╞ answ DH stream close/SESS CLEAR RESP↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ sink clear↲
╞ ╞ ╞ answ↲
↲
↲
↲
╞ ╞ answ SESS CLEAR RESP↲
╞ ╞ ╞ ╞ *3)↲
↲
↲
╞ ╞ term sess↲
↲
↲
┆81┆↲
↲
↲
↲
╞ ╞ ╞ 34a↲
════════════════════════════════════════════════════════════════════════
↓
┆0e┆↓
╞ Table 33↲
↲
╞ ┆a1┆state ! event ╞ ! action ! new state ↲
╞ wait sink ! ╞ ! !↲
╞ clear ind ! SESS ABORT ╞ ! - ! -↲
┆a1┆ ! IND ╞ ! !╞ ╞ ↲
wait sink ! ╞ ! ! ↲
clear ind ! RESP.WRITE ╞ ! - ! -↲
╞ & wait sink! ╞ ! !↲
bufs ! ╞ ! ! ↲
╞ & wait sink!╞ ╞ !╞ !↲
╞ ┆a1┆ clear answ!╞ ╞ !╞ !╞ ╞ ↲
wait sink ! ╞ ! !↲
clear ind ! SESS QUEUED╞ ! - ! -↲
╞ & wait sink! *1) ╞ ! !↲
bufs ! ╞ ! ! ↲
╞ & wait sink!╞ ╞ !╞ !↲
╞ ┆a1┆ clear answ!╞ ╞ !╞ !╞ ╞ ↲
╞ wait sink ! messages from !╞ !↲
╞ clear ind ! S62CP╞ different╞ ! -╞ ! -╞ ╞ ↲
╞ ╞ ! from SESS CLEAR !╞ !↲
╞ ┆a1┆╞ ! IND╞ ╞ !╞ !╞ ╞ ↲
╞ wait sink ! document stream╞ !╞ !↲
╞ clear ind ! messages diffe-╞ ! -╞ ! -↲
╞ & wait sink! rent from TTXSI !╞ !↲
╞ ┆a1┆ bufs╞ ! stream close╞ !╞ !╞ ╞ ↲
╞ wait sink╞ !╞ ╞ !╞ !↲
╞ clear ind ! TTXSI stream╞ ! -╞ ! -↲
╞ & wait sink! close╞ ╞ !╞ !↲
╞ ┆a1┆ bufs╞ !╞ ╞ !╞ !╞ ╞ ↲
wait sink ! ╞ ! !↲
clear ind ! TU removed ╞ ! - ! 35a↲
┆a1┆ ! ╞ ! ! ↲
╞ wait sink ! ╞ ! !↲
╞ bufs ! TU removed ╞ ! - ! 35b↲
╞ ┆a1┆╞ ! ╞ ╞ ! !╞ ╞ ↲
╞ wait sink╞ !╞ ╞ !╞ !↲
╞ ┆a1┆ clear answ! TU removed╞ !╞ ! 35c╞ ╞ ↲
┆0f┆↓
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
╞ Fig. 33, footnotes.↲
↲
╞ *1) ┆84┆A new DOC CONT IND referring to the same document has been ↓
┆19┆┆8d┆┄┄received before the session clean up procedure was ended.↲
↲
╞ *2) S62CP buffers can be pending at TTXSI↲
↲
╞ *3) ┆84┆If TTXSI buffers can be pending at S62CP (which will probably ↓
┆19┆┆8d┆┄┄not be the case), the answer on a TTXSI stream close should be ↓
┆19┆┆8d┆┄┄delayed until this happens.↲
↲
┆8c┆┆83┆┆c0┆↓
┆0e┆↓
┆b0┆┆a1┆6.5.4.6╞ Packet Sink, Error Handling↲
↲
╞ ┆84┆This section describes error handling termination for sink states. ↓
┆19┆┆89┆┄┄Aside from normal error handling, it handles errors occurred under ↓
┆19┆┆89┆┄┄packet initalization. The protocol machine is showed in fig. 34. ↓
┆19┆┆89┆┄┄It has the entry points:↲
↲
╞ 34a: ┆84┆One of the following errors has occurred:↲
- SESS ABORT IND received.↲
╞ - Document stream troubles↲
╞ - DOC RESYNC IND received↲
╞ - DOC DISC IND received↲
╞ - Too many documents or DOC CONT IND received in TLX mode↲
╞ ┆84┆user inf will tell which. The packet has been disconnected ↓
┆19┆┆8e┆┄┄from the session.↲
↲
╞ 34b: ┆84┆Session break down while a RESP.INIT was awaited.↲
↲
╞ 34c: Packet creation was in progress.↲
↲
┆0f┆↓
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 34, Packet sink, error handling↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
34c╞ ╞ 34b╞ ╞ 34a↲
↲
↲
wait╞ ╞ wait ╞ ╞ ╞ wait↲
error╞ ╞ error╞ ╞ ╞ error sink↲
create╞ ╞ init╞ ╞ ╞ write↲
╞ ╞ ╞ ╞ ╞ ╞ *1)↲
↲
↲
╞ RESP.CREATE IND.INIT RESP.INIT IND.WRITE↲
╞ result=ok ╞ result=ok↲
↲
╞ ╞ ╞ ╞ ╞ ╞ RESP.WRITE↲
╞ ╞ ╞ ╞ ╞ ╞ (not last)↲
↲
RESP.CREATE╞ ╞ RESP.INIT↲
result=busy╞ ╞ result=busy↲
╞ *9)╞ ╞ *9)╞ RESP.WRITE(last)↲
↲
↲
29a╞ ╞ IND.DELIVER↲
╞ ╞ result=failed↲
↲
╞ ╞ ╞ ╞ service=TLX╞ service=TTX↲
↲
↲
31b╞ ╞ checkpoint=0 *2)╞ ╞ ╞ checkpoint<>0↲
↲
↲
╞ ╞ IND.ERASE↲
↲
↲
↲
╞ continuation╞ not continuation test packet wait↲
╞ *7)╞ ╞ ╞ ╞ *3)↲
↲
↲
╞ IND.CANCEL╞ ╞ ╞ giveup╞ wait *4)↲
↲
↲
29a╞ ↲
↲
╞ ╞ ╞ *9)╞ ╞ ╞ packet↲
31b╞ ╞ IND.DELIVER ╞ timeout╞ sink *5)↲
╞ ╞ result=term result ╞ waiting↲
╞ ╞ *8)↲
↲
╞ ╞ ╞ ╞ sess queued/connect sess↲
╞ ╞ ╞ ╞ ╞ ╞ *6)↲
↲
╞ ╞ ╞ ╞ ╞ 29b↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
╞ Table 34.↲
┆0e┆↓
↲
╞ ┆a1┆state ╞ ! event ! action ! new state↲
╞ wait error create╞ ! ! !↲
╞ & wait error init ! sess queued! - ! -↲
╞ & wait error sink╞ ! ! !↲
╞ ┆a1┆ write ╞ ! ! !╞ ↲
wait error create ! TU removed ! - ! 29a↲
╞ & wait error init╞ ! ! !↲
╞ & wait error sink ! ! !↲
╞ write╞ ╞ ! ! !↲
╞ & packet sink ! !╞ !↲
┆a1┆ waiting ╞ ! ! ! ↲
┆0f┆↓
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
╞ Fig. 34, footnotes.↲
↲
╞ *1) ┆84┆If outstanding writes=0 and outstanding read=false, receival of ↓
┆19┆┆8d┆┄┄a RESP.WRITE is simulated.↲
↲
╞ *2) ┆84┆If the checkpoint number field in the document description is ↓
┆19┆┆8d┆┄┄zero the document should be regarded as discarded. If a ↓
┆19┆┆8d┆┄┄discard really has been received, this field has been set to ↓
┆19┆┆8d┆┄┄zero.↲
↲
╞ *3) ┆84┆The user inf. field is used to a lookup in the receival table ↓
┆19┆┆8d┆┄┄described in section 8. This will decide whether the receival ↓
┆19┆┆8d┆┄┄should be abandoned (the pseudo event giveup) or a ↓
┆19┆┆8d┆┄┄continuation should be awaited (the pseudo event wait).↲
↲
╞ *4) ┆84┆A timer is started with the duration packet_wait_time (see ↓
┆19┆┆8d┆┄┄section 8).↲
↲
╞ *5) ┆84┆If the packet session queue is not empty, a "sess queued" ↓
┆19┆┆8d┆┄┄event is simulated.↲
↲
╞ *6) ┆84┆the parameters from the DOC CONT IND is transferred to the ↓
┆19┆┆8d┆┄┄packet.↲
↲
╞ *7) ┆84┆If continuation in the document description is true, the ↓
┆19┆┆8d┆┄┄packet has been initialized by a DOC CONT IND.↲
↲
┆8c┆┆83┆┆cc┆↓
┆0e┆↓
╞ *8) ┆84┆Term result is:↲
╞ - pers_err if the error was a document stream break down↲
╞ - failed otherwise↲
┆0f┆↓
↲
↲
┆b0┆┆a1┆6.6╞ TU removal Handling for Packets.↲
↲
╞ ┆84┆This section, corresponding to fig. 35, describes handling of a ↓
┆19┆┆89┆┄┄packet where a TU removed event has occurred while a document ↓
┆19┆┆89┆┄┄stream has been open or not fully terminated.↲
↲
╞ ┆84┆All packet communication with DS is terminated, but the packet is ↓
┆19┆┆89┆┄┄not disconnected from the session before the stream has been ↓
┆19┆┆89┆┄┄terminated. This ensures that the session and thereby the TU, is ↓
┆19┆┆89┆┄┄alive until this happens.↲
↲
╞ ┆84┆The following entry points can be entered both from packet source ↓
┆19┆┆89┆┄┄states (section 6.4) or packet sink states (section 6.5). The ↓
┆19┆┆89┆┄┄events to the protocol machine are the S62CP events that can occur ↓
┆19┆┆89┆┄┄for these states, but most of them are ignored (they are crossing ↓
┆19┆┆89┆┄┄the SESS ABORT REQ at the interface).↲
↲
╞ 35a: SESS CLEAR IND is awaited.↲
↲
╞ 35b: ┆84┆SESS CLEAR IND has already occurred, but the DH stream close ↓
┆19┆┆8e┆┄┄should be awaited.↲
↲
╞ 35c: ┆84┆A SESS CLEAR RESP is pending at S62CP. Thus when this message ↓
┆19┆┆8e┆┄┄is home it will be sure that all buffers from the document ↓
┆19┆┆8e┆┄┄stream are home.↲
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 35, TU removal handling↲
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
↲
↲
↲
╞ ╞ ╞ 35a╞ 35b╞ ╞ 35c↲
↲
↲
↲
↲
╞ ╞ wait↲
╞ ╞ tu rem clear↲
↲
↲
↲
╞ ╞ SESS CLEAR IND↲
↲
↲
↲
╞ ╞ wait rem↲
╞ ╞ close↲
╞ ╞ ╞ *2↲
↲
↲
↲
╞ answ DH stream close/SESS CLEAR RESP *3)↲
↲
↲
↲
╞ ╞ wait tu↲
╞ ╞ rem end↲
↲
↲
↲
↲
╞ answ SESS CLEAR RESP *1)↲
↲
↲
↲
╞ TU rem term sess *4)↲
↲
↲
↲
╞ ╞ packet idle↲
↲
╱04002d440c00060000000003014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
╱04002d440c00060000000002014b31000000000000000000000000000000000000000000000000000a141e28323c464b555f69737d8791ff04╱
↓
════════════════════════════════════════════════════════════════════════
↓
╞ Fig. 35, footnotes.↲
↲
╞ *1) ┆84┆All pending messages at S62CP are home. A possible pending ↓
┆19┆┆8d┆┄┄TTXSI stream close is returned.↲
↲
╞ *2) ┆84┆If DH close pending is false, an answ DH stream close is ↓
┆19┆┆8d┆┄┄simulated.↲
↲
╞ *3) ┆84┆All messages pending at the document stream are home.↲
↲
╞ *4) ┆84┆Generates the corresponding event in the session.↲
↲
↲
┆1a┆┆1a┆urred:↲
↲
╞ - A Sreak Down HD↲
↲
↲
╞ ╞ ╞ wait↲
╞ ╞ ╞ sink bufs↲
╞ ╞ ╞ *2)↲
↲
↲
↲
╞ ╞ answ DH st