520   Control model and associations

Created: 20 Apr 2007

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page:

Clause: 17

Paragraph:

Category: Issue for edition 2 of this part

Issue

During the WG10 Meeting in Seoul, the following TISSUE was raised:

In general, it needs to be specified, what happens with the state machines of the control model, when the association is lost. In particular, this can be of relevance for time activated control.

Proposal

Discussion Created Status
WG10 Meeting - Fredericia.
Final Proposal not accepted.
The CD of 7-2 alreay integrates the behavior of control sequences and disconnection from client in the state machines.
The Client that performed the select is the only one that can perform the operate. At disconnection, the selection is aborted - see the sbo-with-normal-security and sbo-with-enhanced-security.
27 Feb 08 In Force (green)
Accepted in principle.

Wolfgang's explanation should be be used to add a note:

"NOTE: In case of an association lost, the following may happen: If the assocoation is re-established before timeout and the command completed, it is fine - if not, the state machine times out and finalizes / cancels the command. This might include that another (standby) client connects and continues the command handling (e.g. operate after existing select)." 		17 Feb 08 Ballot Period
I suggest to do nothing special, just let the state machine run, especially the timeouts. If the assocoation is re-established before timeout and the command completed, it is fine - if not, the state machine times out and finalizes / cancels the command. This might include that another (standby) client connects and continues the command handling (e.g. operate after existing select). 28 Sep 07 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1