The following sections describe the Status Codes supported by the system for each implemented service as well as the reason for issuing specific Status Codes or the associated behavior when receiving it.
[Throughout all SCP related subsections, if necessary provide in the "Condition" Column further information (beyond the information in the "Further Meaning" Column) on the specific situation/condition, in which the respective Status Code is sent. E.g. for the Status Code
-
"A700 - Refused: Out of Resource" document details whether there is no space in the database, or on the hard drive, …
-
"0110 Processing Failure" document the nature of the processing failure.]
N.7.3.1 General AE Communication and Failure Behavior and Handling
N.7.3.1.1 Communication Failure Behavior as Association Initiator
Table N.7-8 describes behavior of the AE if a communication failure occurs when it initiated an Association.
[Describe below the behavior of the AE if a communication failure occurs when it initiated an Association, e.g.: Timeout, Network disconnect ABORT etc.]
Table N.7-8. DICOM Communication Failure Behavior as Association Initiator
|
Failure
|
Failure Behavior
|
|
Timeout
|
[Describe what the Application Entity does, if it does not receive any messages after the Association request and times out, e.g.,]
The Association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user.
|
|
Association aborted
|
[Describe what the Application Entity does if an ABORT happens during the Association, e.g.,]
The command is marked as failed. The reason is logged and reported to the user.
|
|
Network Disconnect
|
[Describe what an Application Entity does if the network is disconnected during Association, e.g.,]
The command is marked as failed. The reason is logged and reported to the user. Automatic retry of this service connection is started
|
N.7.3.1.2 Communication Failure Handling as Association Acceptor
Table N.7-9 describes how the AE responds when it receives an Association request that leads to a failure in communication.
[Describe how the AE responds when it receives Association requests that leads to a failure in communication: application error during processing, unrecognized PDU values in the Association request etc. List all cases supported by the product.]
Table N.7-9. DICOM Communication Failure Handling as Association Acceptor
|
Exception
|
Failure response
|
|
Failure during processing of an Association request
|
[Describe what the AE does if there is an internal error during processing of an Association request, e.g.,]
ABORT message is sent out and the connection is closed
|
|
Unrecognized Called AE
|
[Describe what the AE does if the Called AE is not recognized, e.g.,]
AE responds with Association-RJ
|
|
Exceed limit for number of connections supported
|
[Describe what the AE does if it receives a new Association request if the limit of connections supported by the AE is exceeded, e.g.,]
AE responds with Association-RJ
|