The division of EXAMPLE-QUERY-RETRIEVE-SERVER into the separate DICOM Application Entities represents a somewhat arbitrary partitioning of functionality. For the purpose of this document they are organized in this manner so as to detail their independent logical functionality.
By default all of the defined Application Entities have different AE Titles. However, EXAMPLE-QUERY-RETRIEVE-SERVER can be configured so that the QUERY-RETRIEVE-SCP AE and STORAGE-SCU AE share the same Application Entity Title. However, the QUERY-RETRIEVE-SCP AE and STORAGE-SCP AE must have separate Application Entity Titles.
The Application Entities detailed in the Application Data Flow Diagram are all Windows NT applications.
-
The STORAGE-SCU AE can send Composite SOP Instances. It handles requests from the QUERY-RETRIEVE-SCP AE to transmit Images to a specific DICOM destination. The STORAGE-SCU AE functions as a C-STORE SCU. (Note that in this example Conformance Statement this STORAGE-SCU AE does not allow a Local User to request that images be sent to a Remote AE. If a 'real' AE does allow this then this should be mentioned here and in the other appropriate areas of the Conformance Statement).
-
The QUERY-RETRIEVE-SCP AE can handle incoming query and retrieve requests. It can handle external queries for Patient, Study, Series, and Image data, and also handle Image retrieval requests. The QUERY-RETRIEVE-SCP AE handles retrieval requests by issuing a command to the STORAGE-SCU AE to send the requested Images to the destination specified by the Remote AE. The QUERY-RETRIEVE-SCP AE functions as an SCP for C-FIND and C-MOVE requests.
-
The STORAGE-SCP AE can receive incoming DICOM images and add them to the EXAMPLE-QUERY-RETRIEVE-SERVER database. It can respond to external Storage and Verification Requests as a Service Class Provider (SCP) for C-STORE and C-ECHO requests. The STORAGE-SCP AE can also handle Storage Commitment Push Model Requests. It can thus be used to query whether the EXAMPLE-QUERY-RETRIEVE-SERVER will confirm ownership and responsibility for specific Composite SOP Instances. The STORAGE-SCP AE currently only supports image type Composite SOP Instances.
The STORAGE-SCU AE can be invoked by the QUERY-RETRIEVE-SCP AE to trigger the transfer of specific images to a remote destination AE. The STORAGE-SCU AE must be correctly configured with the host and port number of any external DICOM AEs that are to be C-MOVE retrieval destinations. The Presentation Contexts to use are determined from the headers of the DICOM files to be transferred. Some conversion of the DICOM image objects is possible if the original Presentation Context is not supported by the remote destination AE or if compression is preferred.
The QUERY-RETRIEVE-SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, QUERY-RETRIEVE-SCP AE expects it to be a DICOM application. QUERY-RETRIEVE-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the DICOM Query-Retrieve Service Class, and Verification Service Class. It will handle query and retrieve requests on these Presentation Contexts and respond with data objects with values corresponding to the contents of the EXAMPLE-QUERY-RETRIEVE-SERVER database. For C-MOVE requests the destination for the image objects is determined from the Destination AE Title contained in the C-MOVE request. When a retrieval request is received, the QUERY-RETRIEVE-SCP AE issues a command to the STORAGE-SCU AE to send the specified images to the C-MOVE Destination AE.
The STORAGE-SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, the STORAGE-SCP AE expects it to be a DICOM application. The STORAGE-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the Verification, Storage, and Storage Commitment Service Classes. Any images received on such Presentation Contexts will be added to the EXAMPLE-QUERY-RETRIEVE-SERVER database. If a Storage Commitment Push Model N-ACTION Request is received then the STORAGE-COMMITMENT-SCP AE will immediately check if the referenced Composite SOP Instances are in the EXAMPLE-QUERY-RETRIEVE-SERVER database and return an N-EVENT-REPORT Notification. It will never 'cache' Storage Commitment Push Model Requests and wait for Composite SOP Instances to be received at a later time.
The only sequencing constraint that exists across all the EXAMPLE-QUERY-RETRIEVE-SERVER Application Entities is the fact that a Composite SOP Instance must be received by the STORAGE-SCP AE before Storage Commitment Push Model or Query-Retrieve Requests related to this SOP Instance can be successfully handled:
Note that the only constraint is for the Composite SOP Instance to be received prior to the other events. For example, it is not necessary for the Storage Commitment Push Model Request to be received prior to receiving Query or Retrieval Requests related to the SOP Instance.
The STORAGE-SCU AE provides Standard Conformance to the following DICOM V3.0 SOP Classes:
Table F.4.2-1. SOP Classes for STORAGE-SCU AE
|
SOP Class Name |
SOP Class UID |
SCU |
SCP |
|---|---|---|---|
|
Verification |
1.2.840.10008.1.1 |
Yes |
No |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
Yes |
No |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
Yes |
No |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
Yes |
No |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
Yes |
No |
|
Computed Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
Yes |
No |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
Yes |
No |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
Yes |
No |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
Yes |
No |
STORAGE-SCU AE can be configured to use the retired US Image objects (US Image Storage, 1.2.840.10008.5.1.4.1.1.6, and US Multi-frame Storage, 1.2.840.10008.5.1.4.1.1.3) rather than the current US SOP Classes for ultrasound images or vice-versa, making any necessary changes to make the transformed image objects conformant to the corresponding SOP Class. This is only done if the external Storage SCP AE does not support the SOP Instance's original SOP Class.
By altering the configuration it is possible to support additional or fewer SOP Classes.
The STORAGE-SCU AE can only form Associations when requested to do so by the QUERY-RETRIEVE-SCP AE. The STORAGE-SCU AE can only request the opening of an Association. It cannot accept requests to open Associations from external Application Entities.
The DICOM standard Application Context Name for DICOM is always proposed:
Table F.4.2-2. DICOM Application Context for STORAGE-SCU AE
|
Application Context Name |
1.2.840.10008.3.1.1.1 |
The maximum number of simultaneous Associations is configurable, but is usually limited to a maximum of 10. This configuration largely depends on whether relatively quick response to multiple simultaneous C-MOVE Destination AEs is required or maximum throughput performance is required. If the latter is the case, then no simultaneous Associations are permitted, in order to reduce disk thrashing and thus maximize throughput. The STORAGE-SCU AE can initiate simultaneous Associations to a given external C-MOVE Destination AE up to the maximum number configured. There is no separate limit on the maximum number permitted to the same C-MOVE Destination AE.
If the first attempt to open an Association fails then the STORAGE-SCU AE will reschedule the task to attempt it again after a configurable time delay. The number of times to reattempt Association establishment is configurable, with the default being zero.
Table F.4.2-3. Number of Associations as a SCU for STORAGE-SCU AE
|
Maximum number of simultaneous Associations |
10 (Configurable) |
The STORAGE-SCU AE does not support asynchronous communication (multiple outstanding transactions over a single Association). All Association requests must be completed and acknowledged before a new operation can be initiated.
Table F.4.2-4. Asynchronous Nature as a SCU for STORAGE-SCU AE
|
Maximum number of outstanding asynchronous transactions |
1 (Not Configurable) |
Table F.4.2-5. DICOM Implementation Class and Version for STORAGE-SCU AE
|
Implementation Class UID |
1.840.xxxxxxx.yyy.etc… |
|
Implementation Version Name |
EX_VERS_01 |
Note that the STORAGE-SCU AE and QUERY-RETRIEVE-SCP AE use the same Implementation Class UID. All EXAMPLE-QUERY-RETRIEVE-SERVER AEs use the same Implementation Version Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released independently.
The STORAGE-SCU AE will initiate a new Association when the QUERY-RETRIEVE-SCP AE invokes the STORAGE-SCU AE to transmit images. The QUERY-RETRIEVE-SCP AE will issue such a command whenever it receives a valid C-MOVE Request. An Association Request is sent to the specified C-MOVE Destination AE and upon successful negotiation of the required Presentation Context the image transfer is started. In all cases an attempt will be made to transmit all the indicated images in a single Association, but this may not always be possible. The Association will be released when all the images have been sent. If an error occurs during transmission over an open Association then the image transfer is halted. The STORAGE-SCU AE will not attempt to independently retry the image export.
Note that the STORAGE-SCU AE does not support the unsolicited sending of SOP Instances using the DICOM Storage Service Class. It will only send SOP Instances in response to a C-MOVE Request from a peer AE.
The following sequencing constraints illustrated in Figure F.4.2-1 apply to the STORAGE-SCU AE:
-
Peer AE requests retrieval of Study, Series, or Images from QUERY-RETRIEVE-SCP AE (C-MOVE-RQ).
-
QUERY-RETRIEVE-SCP AE signals STORAGE-SCU AE to send the image Composite SOP Instances indicated in the C-MOVE-RQ to the C-MOVE Destination AE.
-
STORAGE-SCU AE opens a new Association with the indicated C-MOVE Destination AE.
-
STORAGE-SCU AE sends the indicated Composite SOP Instances.
-
STORAGE-SCU AE closes the Association.
-
The Verification Service is only supported as a utility function for Service staff. It is used only as a diagnostic tool.
STORAGE-SCU AE will propose Presentation Contexts as shown in the following table:
Table F.4.2-6. Proposed Presentation Contexts By the STORAGE-SCU AE
|
Presentation Context Table |
|||||
|---|---|---|---|---|---|
|
Abstract Syntax |
Transfer Syntax |
Role |
Ext. Neg. |
||
|
Name |
UID |
Name |
UID |
||
|
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCU |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCU |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCU |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCU |
None |
|
Computer Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
Computer Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCU |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCU |
None |
Note
The SOP Classes and Transfer Syntaxes that the STORAGE-SCU AE proposes, as listed above, represent the default behavior. The STORAGE-SCU AE can be configured to propose a subset of these contexts or additional Presentation Contexts. Also, the default Behavior is to propose just a single Transfer Syntax per Presentation Context. However, this can be altered so that every proposed Presentation Context has a unique SOP Class and one or more Transfer Syntaxes. That is, the default behavior is to determine the Transfer Syntaxes the SCP can accept as opposed to which it prefers.
Standard conformance is provided to the DICOM Verification Service Class as an SCU. The Verification Service as an SCU is actually only supported as a diagnostic service tool for network communication issues.
Composite DICOM SOP Instances are maintained as DICOM Part 10 compliant files in the EXAMPLE-QUERY-RETRIEVE-SERVER database. The entire set of tags received with the image will be saved in EXAMPLE-QUERY-RETRIEVE-SERVER; this includes all Private and SOP Extended Elements. When a SOP Instance is selected for export from EXAMPLE-QUERY-RETRIEVE-SERVER, its content will be exported as it was originally received except for a few possible exceptions. Some of the Patient demographic and Study information Elements whose values can have been altered due to changes administered on EXAMPLE-QUERY-RETRIEVE-SERVER or changes to the state of the image data due to compression can be altered when the SOP Instance is exported.
The Patient demographic and Study information can be entered or altered by several means: manually, or from HL7 messaging,. The replacement behavior depends on which specific DICOM and HL7 services are supported. Also, this behavior is configurable. Values can be altered without changing the SOP Instance UID unless otherwise noted. Refer to the Annex for the specific details of which Elements can have their values altered at time of export.
The EXAMPLE-QUERY-RETRIEVE-SERVER creates files called Service Logs that can be used to monitor their status and diagnose any problems that may arise. If any error occurs during DICOM communication then appropriate messages are always output to these Service Logs. In addition, error messages may be output as alerts to the User Interface in certain cases.
The STORAGE-SCU AE will exhibit the following Behavior according to the Status Code value returned in a C-STORE Response from a destination C-STORE SCP:
Table F.4.2-7. STORAGE-SCU AE C-STORE Response Status Handling Behavior
|
Service Status |
Further Meaning |
Error Code |
Behavior |
|---|---|---|---|
|
Success |
Success |
0000 |
The SCP has successfully stored the exported SOP Instance. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Success indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Refused |
Out of Resources |
A700 -A7FF |
This is treated as a permanent Failure. A message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure and the Association is released. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Error |
Data Set does not match SOP Class |
A900 -A9FF |
This is treated as a permanent Failure. A message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure and the Association is released. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Error |
Cannot Understand |
C000 -CFFF |
This is treated as a permanent Failure. A message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure and the Association is released. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Coercion of Data Elements |
B000 |
Image transmission is considered successful. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Data Set does not match SOP Class |
B007 |
Image transmission is considered successful. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Elements Discarded |
B006 |
Image transmission is considered successful. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Attribute List Error |
0107 |
Image transmission is considered successful. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Attribute Value Out of Range |
0116 |
Image transmission is considered successful. A message is sent to the QUERY-RETRIEVE-SCP AE indicating successful export. The QUERY-RETRIEVE-SCP AE will send the appropriate PENDING or SUCCESS Status in the C-MOVE Response. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
* |
* |
Any other status code. |
This is treated as a permanent Failure. A message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure and the Association is released. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
All Status Codes indicating an error or refusal are treated as a permanent failure. The STORAGE-SCU AE never automatically resends images when an error Status Code is returned in a C-STORE Response. For specific behavior regarding Status Code values returned in C-MOVE Responses, refer to the Services Supported as an SCP by the QUERY-RETRIEVE-SCP AE.
Table F.4.2-8. STORAGE-SCU AE Communication Failure Behavior
|
Exception |
Behavior |
|---|---|
|
Timeout expiry for an expected DICOM Message Response (DIMSE level timeout). |
The Association is aborted using a DICOM A-ABORT and a message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). |
The Association is aborted using a DICOM A-ABORT and a message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Association A-ABORTed by the SCP or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) |
A message is sent to the QUERY-RETRIEVE-SCP AE indicating an export failure. The QUERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
The QUERY-RETRIEVE-SCP AE provides Standard Conformance to the following DICOM V3.0 SOP Classes:
Table F.4.2-9. SOP Classes for QUERY-RETRIEVE-SCP AE
|
SOP Class Name |
SOP Class UID |
SCU |
SCP |
|---|---|---|---|
|
Patient Root Q/R Information Model - FIND |
1.2.840.10008.5.1.4.1.2.1.1 |
No |
Yes |
|
Patient Root Q/R Information Model - MOVE |
1.2.840.10008.5.1.4.1.2.1.2 |
No |
Yes |
|
Study Root Q/R Information Model - FIND |
1.2.840.10008.5.1.4.1.2.2.1 |
No |
Yes |
|
Study Root Q/R Information Model - MOVE |
1.2.840.10008.5.1.4.1.2.2.2 |
No |
Yes |
The QUERY-RETRIEVE-SCP AE will never initiate Associations; it only accepts Association Requests from external DICOM AEs. The QUERY-RETRIEVE-SCP AE will accept Associations for Verification, C-FIND, and C-MOVE requests. In the case of a C-MOVE request, the QUERY-RETRIEVE-SCP AE will issue a command to the STORAGE-SCU AE to initiate an Association with the Destination DICOM AE to send images as specified by the originator of the C-MOVE Request.
The DICOM standard Application Context Name for DICOM 3.0 is always accepted:
Table F.4.2-10. DICOM Application Context for QUERY-RETRIEVE-SCP AE
|
Application Context Name |
1.2.840.10008.3.1.1.1 |
The QUERY-RETRIEVE-SCP AE can support multiple simultaneous Associations. Each time the QUERY-RETRIEVE-SCP AE receives an Association, a child process will be spawned to process the Verification, Query, or Retrieval request. The maximum number of child processes, and thus the maximum number of simultaneous Associations that can be processed, is set by configuration. The default maximum is 10 in total. The maximum number of simultaneous Associations can be either an absolute number or a maximum number for each requesting external Application Entity. The latter flexibility can be useful if communication with one external AE is unreliable and one does not wish 'hung' connections with this AE to prevent Associations with other client AEs.
Table F.4.2-11. Number of Simultaneous Associations as a SCP for QUERY-RETRIEVE-SCP AE
|
Maximum number of simultaneous Associations |
10 (Configurable) |
The QUERY-RETRIEVE-SCP AE does not support asynchronous communication (multiple outstanding transactions over a single Association). All Association requests must be completed and acknowledged before a new operation can be initiated.
Table F.4.2-12. Asynchronous Nature as a SCP for QUERY-RETRIEVE-SCP AE
|
Maximum number of outstanding asynchronous transactions |
1 (Not Configurable) |
The implementation information for the Application Entity is:
Table F.4.2-13. DICOM Implementation Class and Version for QUERY-RETRIEVE-SCP AE
|
Implementation Class UID |
1.840.xxxxxxx.yyy.etc… |
|
Implementation Version Name |
EX_VERS_01 |
Note that the STORAGE-SCU AE, and QUERY-RETRIEVE-SCP AE use the same Implementation Class UID. All EXAMPLE-QUERY-RETRIEVE-SERVER AEs use the same Implementation Version Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released independently.
The QUERY-RETRIEVE-SCP AE accepts Associations only if they have valid Presentation Contexts. If none of the requested Presentation Contexts are accepted then the Association Request itself is rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address) and/or Application Entity Titles.
If QUERY-RETRIEVE-SCP AE receives a query (C-FIND) request then the response(s) will be sent over the same Association used to send the C-FIND-Request.
If QUERY-RETRIEVE-SCP AE receives a retrieval (C-MOVE) request then the responses will be sent over the same Association used to send the C-MOVE-Request. The QUERY-RETRIEVE-SCP AE will notify the STORAGE-SCU to send the requested SOP Instances to the C-MOVE Destination. The STORAGE-SCU AE notifies the QUERY-RETRIEVE-SCP AE of the success or failure of each attempt to send a Composite SOP Instance to the peer C-MOVE Destination AE. The QUERY-RETRIEVE-SCP AE then sends a C-MOVE Response indicating this status after each attempt. Once the STORAGE-SCU AE has finished attempting to transfer all the requested SOP Instances, the QUERY-RETRIEVE-SCP AE sends a final C-MOVE Response indicating the overall status of the attempted retrieval.
The following sequencing constraints illustrated in Figure F.4.2-2 apply to the QUERY-RETRIEVE-SCP AE for handling queries (C-FIND-Requests) :
-
Peer AE opens an Association with the QUERY-RETRIEVE-SCP AE.
-
Peer AE sends a C-FIND-RQ Message
-
QUERY-RETRIEVE-SCP AE returns a C-FIND-RSP Message to the peer AE with matching information. A C-FIND-RSP is sent for each entity matching the identifier specified in the C-FIND-RQ. A final C-FIND-RSP is sent indicating that the matching is complete.
-
Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further C-FIND or C-MOVE Requests can be sent over the Association before it is closed.
The following sequencing constraints illustrated in Figure F.4.2-2 apply to the QUERY-RETRIEVE-SCP AE for handling retrievals (C-MOVE-Requests) :
-
Peer AE opens an Association with the QUERY-RETRIEVE-SCP AE.
-
Peer AE sends a C-MOVE-RQ Message
-
QUERY-RETRIEVE-SCP AE notifies the STORAGE-SCU AE to send the Composite SOP Instances to the peer C-MOVE Destination AE as indicated in the C-MOVE-RQ.
-
After attempting to send a SOP Instance, the STORAGE-SCU AE indicates to the QUERY-RETRIEVE-SCP AE whether the transfer succeeded or failed. The QUERY-RETRIEVE-SCP AE then returns a C-MOVE-RSP indicating this success or failure.
-
Once the STORAGE-SCU AE has completed all attempts to transfer the SOP Instances to the C-MOVE Destination AE, or the first failure occurred, the QUERY-RETRIEVE-SCP AE sends a final C-MOVE-RSP indicating the overall success or failure of the retrieval.
-
Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further C-FIND or C-MOVE Requests can be sent over the Association before it is closed.
The QUERY-RETRIEVE-SCP AE may reject Association attempts as shown in the table below. The Result, Source and Reason/Diag columns represent the values returned in the corresponding fields of an ASSOCIATE-RJ PDU (see Section 9.3.4 “A-ASSOCIATE-RJ PDU Structure” in PS3.8 ). The following abbreviations are used in the Source column:
-
1 - DICOM UL service-user
-
2 - DICOM UL service-provider (ASCE related function)
-
3 - DICOM UL service-provider (Presentation related function)
Table F.4.2-14. Association Rejection Reasons
|
Result |
Source |
Reason/Diag |
Explanation |
|---|---|---|---|
|
2 - rejected-transient |
c |
2 - local-limit-exceeded |
The (configurable) maximum number of simultaneous Associations has been reached. An Association request with the same parameters may succeed at a later time. |
|
2 - rejected-transient |
c |
1 - temporary-congestion |
No Associations can be accepted at this time due to the real-time requirements of higher priority activities (e.g., during image acquisition no Associations will be accepted) or because insufficient resources are available (e.g., memory, processes, threads). An Association request with the same parameters may succeed at a later time. |
|
1 - rejected-permanent |
a |
2 - application-context-name-not-supported |
The Association request contained an unsupported Application Context Name. An association request with the same parameters will not succeed at a later time. |
|
1 - rejected-permanent |
a |
7 - called-AE-title-not-recognized |
The Association request contained an unrecognized Called AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association initiator is incorrectly configured and attempts to address the Association acceptor using the wrong AE Title. |
|
1 - rejected-permanent |
a |
3 - calling-AE-title-not-recognized |
The Association request contained an unrecognized Calling AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association acceptor has not been configured to recognize the AE Title of the Association initiator. |
|
1 - rejected-permanent |
b |
1 - no-reason-given |
The Association request could not be parsed. An Association request with the same format will not succeed at a later time. |
QUERY-RETRIEVE-SCP AE will accept Presentation Contexts as shown in the following table:
Table F.4.2-15. Accepted Presentation Contexts By the QUERY-RETRIEVE-SCP AE
|
Presentation Context Table |
|||||
|---|---|---|---|---|---|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended Negotiation |
||
|
Name |
UID |
Name |
UID |
||
|
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Patient Root Q/R Information Model - FIND |
1.2.840.10008.5.1.4.1.2.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Patient Root Q/R Information Model - MOVE |
1.2.840.10008.5.1.4.1.2.1.2 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Study Root Q/R Information Model - FIND |
1.2.840.10008.5.1.4.1.2.2.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Study Root Q/R Information Model - MOVE |
1.2.840.10008.5.1.4.1.2.2.2 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
The QUERY-RETRIEVE-SCP AE supports hierarchical queries and not relational queries. There are no attributes always returned by default. Only those attributes requested in the query identifier are returned. Query responses always return values from the EXAMPLE-QUERY-RETRIEVE-SERVER database. Exported SOP Instances are always updated with the latest values in the database prior to export. Thus, a change in Patient demographic information will be contained in both the C-FIND Responses and any Composite SOP Instances exported to a C-MOVE Destination AE.
Patient Root Information Model
All required search keys on each of the four levels (Patient, Study, Series, and Image) are supported. However, the Patient ID (0010,0020) key must have at least a partial value if the Patient's Name (0010,0010) is not present in a Patient Level query.
Study Root Information Model
All the required search keys on each of the three levels (Study, Series, and Image) are supported. If no partial values are specified for Study attributes then either the Patient ID (0010,0020) key or the Patient's Name (0010,0010) must have at least a partial value specified.
Table F.4.2-16. Patient Root C-FIND SCP Supported Elements
|
Level Name Attribute Name |
Tag |
VR |
Types of Matching |
|---|---|---|---|
|
SOP Common |
|||
|
Specific Character Set |
0008,0005 |
CS |
NONE |
|
Patient Level |
|||
|
Patient's Name Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Other Patient Names |
0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 0010,1001 |
PN LO DA CS LO PN |
S,*,U S,*,U S,U S,U NONE NONE |
|
Study Level |
|||
|
Study Date Study Time Accession Number Study ID Study Instance UID Referring Physician's Name Study Description |
0008,0020 0008,0030 0008,0050 0020,0010 0020,000D 0008,0090 0008,1030 |
DA TM SH SH UI PN LO |
S,R,U R,U S,*,U S,*,U S,U,L S,*,U S,*,U |
|
Series Level |
|||
|
Modality Series Number Series Instance UID Operator's Name |
0008,0060 0020,0011 0020,000E 0008,1070 |
CS IS UI PN |
S,U S,*,U S,U,L NONE |
|
Image Level |
|||
|
Instance Number SOP Instance UID |
0020,0013 0008,0018 |
IS UI |
S,*,U S,U,L |
Table F.4.2-17. Study Root C-FIND SCP Supported Elements
|
Level Name Attribute Name |
Tag |
VR |
Types of Matching |
|---|---|---|---|
|
SOP Common |
|||
|
Specific Character Set |
0008,0005 |
CS |
NONE |
|
Study Level |
|||
|
Patient's Name Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Other Patient Names Study Date Study Time Accession Number Study ID Study Instance UID Referring Physician's Name Study Description |
0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 0010,1001 0008,0020 0008,0030 0008,0050 0020,0010 0020,000D 0008,0090 0008,1030 |
PN LO DA CS LO PN DA TM SH SH UI PN LO |
S,*,U S,*,U S,U S,U NONE NONE S,R,U R,U S,*,U S,*,U S,U,L S,*,U S,*,U |
|
Series Level |
|||
|
Modality Series Number Series Instance UID Operator's Name |
0008,0060 0020,0011 0020,000E 0008,1070 |
CS IS UI PN |
S,U S,*,U S,U,L NONE |
|
Image Level |
|||
|
Instance Number SOP Instance UID |
0020,0013 0008,0018 |
IS UI |
S,*,U S,U,L |
The tables should be read as follows:
Attribute Name: Attributes supported for returned C-FIND Responses.
Tag: Appropriate DICOM tag for this attribute.
VR: Appropriate DICOM VR for this attribute.
Types of Matching: The types of Matching supported by the C-FIND SCP. A "S" indicates the identifier attribute can specify Single Value Matching, a "R" will indicate Range Matching, a "*" will denote wild card matching, an 'U' will indicate universal matching, and 'L' will indicate that UID lists are supported for matching. "NONE" indicates that no matching is supported, but that values for this Element in the database can be returned.
Table F.4.2-19. QUERY-RETRIEVE-SCP AE C-FIND Response Status Return Behavior
|
Service Status |
Further Meaning |
Error Code |
Behavior |
|---|---|---|---|
|
Success |
Success |
0000 |
Matching is complete. No final identifier is supplied. |
|
Refused |
Out of Resources |
A700 |
System reached the limit in disk space or memory usage. Error message is output to as an alert to the User Interface, and to the Service Log. |
|
Failed |
Identifier does not match SOP Class |
A900 |
The C-FIND query identifier contains invalid Elements or values, or is missing mandatory Elements or values for the specified SOP Class. Error message is output to the Service Log. |
|
Unable to process |
C001 |
The C-FIND query identifier is valid for the specified SOP Class but cannot be used to query the database. For example, this can occur if a Patient Level query is issued but the identifier has only empty values for both the Patient ID and the Patient Name. Error message is output to the Service Log. |
|
|
Cancel |
Matching terminated due to Cancel Request |
FE00 |
The C-FIND SCU sent a Cancel Request. This has been acknowledged and the search for matches has been halted. |
|
Pending |
Matches are continuing and current match is supplied. |
FF00 |
Indicates that the search for further matches is continuing. This is returned when each successful match is returned and when further matches are forthcoming. This status code is returned if all Optional keys in the query identifier are actually supported. |
|
Matches are continuing but one or more Optional Keys were not supported. |
FF01 |
Indicates that the search for further matches is continuing. This is returned when each successful match is returned and when further matches are forthcoming. This status code is returned if there are Optional keys in the query identifier that are not supported. |
The QUERY-RETRIEVE-SCP AE will convey to the STORAGE-SCU AE that an Association with a DICOM Application Entity named by the external C-MOVE SCU (through a MOVE Destination AE Title) should be established. It will also convey to the STORAGE-SCU AE to perform C-STORE operations on specific images requested by the external C-MOVE SCU. One or more of the Image Storage Presentation Contexts listed in Table F.4.2-6 will be negotiated.
The QUERY-RETRIEVE-SCP AE can support lists of UIDs in the C-MOVE Request at the Study, Series, and Image Levels. The list of UIDs must be at the Level of the C-MOVE Request however. For example, if the C-MOVE Request is for Series Level retrieval but the identifier contains a list of Study UIDs then the C-MOVE Request will be rejected, and the A900 Failed Status Code will be returned in the C-MOVE Response.
An initial C-MOVE Response is always sent after confirming that the C-MOVE Request itself can be processed. After this, the QUERY-RETRIEVE-SCP AE will return a response to the C-MOVE SCU after the STORAGE-SCU AE has attempted to send each image. This response reports the number of remaining SOP Instances to transfer, and the number transferred having a successful, failed, or warning status. If the Composite SOP Instances must be retrieved from long-term archive prior to export there may be quite a long delay between the first C-MOVE Response and the next one after the attempt to export the first image. The maximum length of time for this delay will depend on the particular type of archive used but typically varies between 3 and 10 minutes.
Table F.4.2-20. QUERY-RETRIEVE-SCP AE C-MOVE Response Status Return Behavior
|
Service Status |
Further Meaning |
Error Code |
Behavior |
|---|---|---|---|
|
Success |
Sub-operations complete - No Failures |
0000 |
All the Composite SOP Instances have been successfully sent to the C-MOVE Destination AE. |
|
Refused |
Out of Resources - Unable to calculate number of matches |
A701 |
Number of matches cannot be determined due to system failure. Returned if the server's database is not functioning so the search for matches to the C-MOVE Request cannot be found. Error message is output as an alert on the User Interface, and to the Service Log. |
|
Out of Resources - Unable to perform sub-operations |
A702 |
C-STORE sub-operations cannot be performed due to failure to access Composite SOP Instances in archive, or failure of a C-STORE Request. For example, this Status will be returned if the required SOP Instances are determined to be off-line (i.e., the MO media has been removed from the archive jukebox). Error message is output as an alert on the User Interface, and to the Service Log. |
|
|
Move destination unknown |
A801 |
The Destination Application Entity named in the C-MOVE Request is unknown to Query-Retrieve SCP AE. Error message is output to the Service Log. |
|
|
Failed |
Identifier does not match SOP Class |
A900 |
The C-MOVE identifier contains invalid Elements or values, or is missing mandatory Elements or values for the specified SOP Class or retrieval level. Error message is output to the Service Log. |
|
Cancel |
Matching terminated due to Cancel Request |
FE00 |
The C-MOVE SCU sent a Cancel Request. This has been acknowledged and the export of Composite SOP Instances to the C-MOVE Destination AE has been halted. |
|
Pending |
Sub-operations are continuing |
FF00 |
A Response with this Status Code is sent every time a Composite SOP Instance has been successfully sent to the C-MOVE Destination AE. |
Note that the Warning Status, B000 (Sub-operations complete - One or more Failures) is never returned. If a failure occurs during export to the C-MOVE Destination AE by the STORAGE-SCU AE then the entire task is aborted. Thus any remaining matches are not exported.
Table F.4.2-21. QUERY-RETRIEVE-SCP AE Communication Failure Behavior
|
Exception |
Behavior |
|---|---|
|
Timeout expiry for an expected DICOM Message Request (DIMSE level timeout). I.e. The QUERY-RETRIEVE-SCP AE is waiting for the next C-FIND or C-MOVE Request on an open Association but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If the STORAGE-SCU AE is still exporting Composite SOP Instances as a result of an earlier C-MOVE Request received on this Association, it will continue attempting to complete the entire C-MOVE Request. |
|
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). I.e. The QUERY-RETRIEVE-SCP AE is waiting for the next message PDU but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If the STORAGE-SCU AE is still exporting Composite SOP Instances as a result of an earlier C-MOVE Request received on this Association, it will continue attempting to complete the entire C-MOVE Request. |
|
Association aborted by the SCU or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) |
Error message is output to the Service Log. If the STORAGE-SCU AE is still exporting Composite SOP Instances as a result of an earlier C-MOVE Request received on this Association, it will continue attempting to complete the entire C-MOVE Request. |
The STORAGE-SCP AE provides Standard Conformance to the following DICOM V3.0 SOP Classes:
Table F.4.2-22. SOP Classes for STORAGE-SCP AE
|
SOP Class Name |
SOP Class UID |
SCU |
SCP |
|---|---|---|---|
|
Verification |
1.2.840.10008.1.1 |
Yes |
Yes |
|
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
No |
Yes |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
No |
Yes |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
No |
Yes |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
No |
Yes |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
No |
Yes |
|
Computed Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
No |
Yes |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
No |
Yes |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
No |
Yes |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
No |
Yes |
These are the default SOP Classes supported. By altering the configuration it is possible to support additional or fewer SOP Classes.
The STORAGE-SCP AE can both accept and propose Association Requests. The STORAGE-SCP AE will accept Association Requests for the Verification, Storage, and Storage Commitment Push Model Services. It will propose Associations only for the Storage Commitment Push Model Service.
The DICOM standard Application Context Name for DICOM 3.0 is always accepted and proposed:
Table F.4.2-23. DICOM Application Context for STORAGE-SCP AE
|
Application Context Name |
1.2.840.10008.3.1.1.1 |
The STORAGE-SCP AE can support multiple simultaneous Associations requested by peer AEs. Each time the STORAGE-SCP AE receives an Association, a child process will be spawned to process the Verification, Storage, or Storage Commitment Push Model Service requests. The maximum number of child processes, and thus the maximum number of simultaneous Associations that can be processed, is set by configuration. The default maximum number is 10 in total. This maximum number of simultaneous Associations can be either an absolute number or a maximum number for each requesting external Application Entity. The latter flexibility can be useful if communication with one external AE is unreliable and one does not wish 'hung' connections with this AE to prevent Associations with other client AEs.
The STORAGE-SCP AE initiates one Association at a time for sending Storage Commitment Push Model N-EVENT-REPORTs to peer AEs.
Table F.4.2-24. Number of Simultaneous Associations as an SCP for STORAGE-SCP AE
|
Maximum number of simultaneous Associations requested by peer AEs |
10 (Configurable) |
|
Maximum number of simultaneous Associations proposed by STORAGE-SCP AE |
1 |
The STORAGE-SCP AE does not support asynchronous communication (multiple outstanding transactions over a single Association). The STORAGE-SCP AE does permit an SCU to send multiple Storage Commitment Push Model Requests before it has sent back any N-EVENT-REPORT Notifications. However, the STORAGE-SCP AE must send an N-ACTION Response before permitting another N-ACTION Request to be received so the DICOM communication itself is not truly asynchronous.
Table F.4.2-25. Asynchronous Nature as a SCP for STORAGE-SCP AE
|
Maximum number of outstanding asynchronous transactions |
1 (Not Configurable) |
There is no limit on the number of outstanding Storage Commitment Push Model Requests that can be received and acknowledged before the STORAGE-SCP AE has responded with the corresponding N-EVENT-REPORT Notifications.
Table F.4.2-26. Outstanding Storage Commitment Push Model Requests for STORAGE-SCP AE
|
Maximum number of outstanding Storage Commitment Requests for which no N-EVENT Notification has been sent |
No Maximum Limit |
The implementation information for this Application Entity is:
Table F.4.2-27. DICOM Implementation Class and Version for STORAGE-SCP AE
|
Implementation Class UID |
1.840.xxxxxxx.yyy.etc… |
|
Implementation Version Name |
EX_VERS_01 |
Note that the STORAGE-SCP AE specifies a different Implementation Class UID than that used by the other Application Entities. All EXAMPLE-QUERY-RETRIEVE-SERVER AEs use the same Implementation Version Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released independently.
The STORAGE-SCP AE will initiate a new Association if a Storage Commitment Push Model Notification (N-EVENT-REPORT) cannot be sent back over the original Association used to send the corresponding request. A new Association will always be requested by the STORAGE-SCP AE in such cases even if the peer AE requests another Association after the original has been closed (i.e., A peer AE opens an Association and sends some Storage requests and a Storage Commitment Push Model request. Before the STORAGE-SCP AE can send the Storage Commitment Push Model N-EVEN-REPORT the Association is closed. The peer AE then opens another Association and begins to send Storage requests. In such a case the STORAGE-SCP AE will always initiate a new Association to send the N-EVENT-REPORT even though it could send the N-EVENT-REPORT over the new Association opened by the peer AE).
An Association Request is sent to the peer AE that sent the Storage Commitment Push Model request and upon successful negotiation of the required Presentation Context the outstanding N-EVENT-REPORT is sent. If there are multiple outstanding N-EVENT-REPORTs to be sent to a single peer AE then the STORAGE-SCP AE will attempt to send them all over a single Association rather than requesting a new Association for each one. The Association will be released when all the N-EVENT-REPORTs for the peer AE have been sent. If any type of error occurs during transmission (either a communication failure or indicated by a Status Code returned by the peer AE) over an open Association then the transfer of N-EVENT-REPORTs is halted. A new Association will be opened to retry sending outstanding N-EVENT-REPORTs. The maximum number of times the STORAGE-SCP AE will attempt to resend an N-EVENT-REPORT is configurable, along with the amount of time to wait between attempts to resend.
If the STORAGE-SCP AE sends a Notification request (N-EVENT-REPORT-RQ) over the original Association opened by the peer AE but receives a request to close the Association rather than a response to the Notification (N-EVENT-REPORT-RSP) then this is handled in the same way as if the request to close the Association had been received before trying to send the Notification request. Thus, the STORAGE-SCP AE will then open a new Association to resend the Notification request.
The STORAGE-SCP AE can be configured to always open a new Association before sending a Storage Commitment Push Model Notifications (N-EVENT-REPORT), in which case the sequencing illustrated in Figure F.4.2-3 will always be followed.
The following sequencing constraints illustrated in Figure F.4.2-3 apply to the STORAGE-SCP AE for handling Storage Commitment Push Model Requests using a new Association:
-
Peer AE opens an Association with the STORAGE-SCP AE.
-
Peer AE requests Storage Commitment of Composite SOP Instance(s) (peer sends N-ACTION-RQ and STORAGE-SCP AE responds with N-ACTION-RSP to indicate that it received the request).
-
Peer AE closes the Association before the STORAGE-SCP AE can successfully send the Storage Commitment Push Model Notification (N-EVENT-REPORT-RQ).
-
STORAGE-SCP AE opens an Association with the peer AE.
-
STORAGE-SCP AE sends Storage Commitment Push Model Notification (N-EVENT-REPORT). More than one can be sent over a single Association if multiple Notifications are outstanding.
-
STORAGE-SCP AE closes the Association with the peer AE.
The Verification Service as an SCU is only supported as a utility function for Service staff. It is used only as a diagnostic tool when the STORAGE-SCP AE is failing to open new Associations to send N-EVENT-REPORTs to peer AEs.
STORAGE-SCP AE will propose Presentation Contexts as shown in the following table:
Table F.4.2-28. Proposed Presentation Contexts By the STORAGE-SCP AE
|
Presentation Context Table |
|||||
|---|---|---|---|---|---|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended Negotiation |
||
|
Name |
UID |
Name |
UID |
||
|
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCU |
None |
|
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
The associated Activity with the Storage Commitment Push Model service is the communication by the STORAGE-SCP AE to peer AEs that it has committed to permanently store Composite SOP Instances that have been sent to it. It thus allows peer AEs to determine whether the EXAMPLE-QUERY-RETRIEVE-SERVER has taken responsibility for the archiving of specific SOP Instances so that they can be flushed from the peer AE system.
The STORAGE-SCP AE will initiate a new Association to a peer AE that sent a Storage Commitment Push Model request if the original Association over which this was sent is no longer open. For a detailed explanation of the SOP specific Behavior of the STORAGE-SCP AE in this case please refer to 4.2.4.4.1.3.3, Storage Commitment Push Model as an SCP.
Standard conformance is provided to the DICOM Verification Service Class as an SCU. The Verification Service as an SCU is actually only supported as a diagnostic service tool for network communication issues. It can be used to test whether Associations can actually be opened with a peer AE that is issuing Storage Commitment Push Model requests (i.e., to test whether the indicated TCP/IP port and AE Title for sending N-EVENT-REPORT Requests to the peer AE are truly functional).
The STORAGE-SCP AE accepts Associations only if they have valid Presentation Contexts. If none of the requested Presentation Contexts are accepted then the Association Request itself is rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address) and/or Application Entity Titles.
The default behavior of the STORAGE-SCP AE is to always attempt to send a Storage Commitment Push Model Notification (N-EVENT-REPORT) over the same Association opened by the peer AE to send the request (N-ACTION). If the STORAGE-SCP AE receives a request to close the Association either before sending the Notification or before receiving the corresponding N-EVENT-REPORT-RSP then it will open a new Association to send the Notification. Refer to Section F.4.2.3.4.1.5 for the details.
The following sequencing constraints illustrated in Figure F.4.2-4 apply to the STORAGE-SCP AE for handling Storage Commitment Push Model Requests over the original Association:
-
Peer AE opens an Association with the STORAGE-SCP AE.
-
Peer AE sends zero or more Composite SOP Instances.
-
Peer AE requests Storage Commitment of Composite SOP Instance(s) (peer sends N-ACTION-RQ and STORAGE-SCP AE responds with N-ACTION-RSP to indicate that it received the request).
-
STORAGE-SCP AE sends Storage Commitment Push Model Notification request (N-EVENT-REPORT-RQ) and successfully receives Notification response (N-EVENT-REPORT-RSP) from peer AE.
-
Peer AE closes the Association.
If the STORAGE-SCP AE receives a request to close the Association from the peer AE before sending the Notification request (N-EVENT-REPORT-RQ) or when expecting to receive a Notification response (N-EVENT-REPORT-RSP) then it will open a new Association to send (or resend) the Notification. Refer to 0 for the details. The STORAGE-SCP AE has a configurable timeout value for the maximum amount of time that it will wait on an open Association for a new request from a peer AE. A peer AE can reset this timer by sending a Verification request (C-ECHO-RQ). This can act as a useful mechanism for a peer AE to maintain an active Association if the length of time between sending Storage or Storage Commitment requests can be long (such as when using a single Association to send images as they are acquired during an ultrasound exam).
The STORAGE-SCP AE may reject Association attempts as shown in the Table below. The Result, Source and Reason/Diag columns represent the values returned in the corresponding fields of an ASSOCIATE-RJ PDU (see Section 9.3.4 “A-ASSOCIATE-RJ PDU Structure” in PS3.8 ). The following abbreviations are used in the Source column:
-
1 - DICOM UL service-user
-
2 - DICOM UL service-provider (ASCE related function)
-
3 - DICOM UL service-provider (Presentation related function)
Table F.4.2-29. Association Rejection Reasons
|
Result |
Source |
Reason/Diag |
Explanation |
|---|---|---|---|
|
2 - rejected-transient |
c |
2 - local-limit-exceeded |
The (configurable) maximum number of simultaneous Associations has been reached. An Association request with the same parameters may succeed at a later time. |
|
2 - rejected-transient |
c |
1 - temporary-congestion |
No Associations can be accepted at this time due to the real-time requirements of higher priority activities (e.g., during image acquisition no Associations will be accepted) or because insufficient resources are available (e.g., memory, processes, threads). An Association request with the same parameters may succeed at a later time. |
|
1 - rejected-permanent |
a |
2 - application-context-name-not-supported |
The Association request contained an unsupported Application Context Name. An association request with the same parameters will not succeed at a later time. |
|
1 - rejected-permanent |
a |
7 - called-AE-title-not-recognized |
The Association request contained an unrecognized Called AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association initiator is incorrectly configured and attempts to address the Association acceptor using the wrong AE Title. |
|
1 - rejected-permanent |
a |
3 - calling-AE-title-not-recognized |
The Association request contained an unrecognized Calling AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association acceptor has not been configured to recognize the AE Title of the Association initiator. |
|
1 - rejected-permanent |
b |
1 - no-reason-given |
The Association request could not be parsed. An Association request with the same format will not succeed at a later time. |
The default Behavior of the STORAGE-SCP AE supports the Implicit VR Little Endian and Explicit VR Little Endian Transfer Syntaxes for all Associations. In addition, explicit JPEG (baseline lossy) compression syntax is supported for the following SOP Classes: US Image, US Multi-frame Image, US Image (retired), US Multi-frame Image (retired), VL Image, VL Multi-frame and Secondary Capture Image Storage.
The STORAGE-SCP AE can be configured to accept a subset of these Transfer Syntaxes, with the inclusion of Implicit VR Little Endian being mandatory.
If multiple Transfer Syntaxes are proposed per Presentation Context then only the most preferable Transfer Syntax is accepted. The order of Transfer Syntax preference for the STORAGE-SCP AE is configurable. The default preference order if multiple Transfer Syntaxes are proposed in a single Presentation Context is: JPEG Baseline1, Little Endian Explicit, Little Endian Implicit (if all these are proposed for a single Presentation Context). This means that if the Implicit VR Little Endian and Explicit VR Little Endian Transfer Syntaxes are proposed in a single Presentation Context then the accepted Transfer Syntax will be Explicit VR Little Endian. This order of preference is configurable.
Any of the Presentation Contexts shown in the following table are acceptable to the STORAGE-SCP AE for receiving images.
Table F.4.2-30. Accepted Presentation Contexts By STORAGE-SCP AE
|
Presentation Context Table |
|||||
|---|---|---|---|---|---|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended Negotiation |
||
|
Name |
UID |
Name |
UID |
||
|
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
US Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCP |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Implicit VR Little Endian (uncompressed) |
1.2.840.10008.1.2 |
SCP |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Explicit VR Little Endian (uncompressed) |
1.2.840.10008.1.2.1 |
SCP |
None |
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCP |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
US Multi-frame Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCP |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Implicit VR Little Endian (uncompressed) |
1.2.840.10008.1.2 |
SCP |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Explicit VR Little Endian (uncompressed) |
1.2.840.10008.1.2.1 |
SCP |
None |
|
US Multi-frame Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
DICOM Explicit JPEG baseline lossy compression |
1.2.840.10008.1.2.4.50 |
SCP |
None |
|
Computer Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Computer Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
NM Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.5 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
|
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
DICOM Explicit JPEG lossy compression |
1.2.840.10008.1.2.4.50 |
SCP |
None |
The STORAGE-SCP AE provides standard conformance to the Verification SOP Class as an SCP.
The associated Activity with the Storage service is the storage of medical image data received over the network on a designated hard disk. The STORAGE-SCP AE will return a failure status if it is unable to store the images on to the hard disk.
The STORAGE-SCP AE does not have any dependencies on the number of Associations used to send images to it. Images belonging to more than one Study or Series can be sent over a single or multiple Associations. Images belonging to a single Study or Series can also be sent over different Associations. There is no limit on either the number of SOP Instances or the maximum amount of total SOP Instance data that can be transferred over a single Association.
The STORAGE-SCP AE is configured to retain the original DICOM data in DICOM Part 10 compliant file format. The STORAGE-SCP AE is Level 2 (Full) conformant as a Storage SCP. In addition, all Private and SOP Class Extended Elements are maintained in the DICOM format files. In addition to saving all Elements in files, a subset of the Elements are stored in the EXAMPLE-QUERY-RETRIEVE-SERVER database to support query and retrieval requests and also allow updating of Patient, Study, and Series information by user input, or demographic and Study related messages. Refer to the Annex for the list of Elements that are checked and/or processed upon receiving a Composite SOP Instance.
The Behavior for handling duplicate SOP Instances is configurable. The default Behavior is to assign a new SOP Instance UID to a received SOP Instance if it conflicts with an existing SOP Instance UID. An alternative configuration is possible that causes the original object with the conflicting SOP Instance UID to be replaced by the new SOP Instance. This Behavior is most commonly enabled if a Storage SCU re-sends entire Studies or Series if a single failure occurs when sending a group of SOP Instances.
For the purposes of image display the system supports the following photometric interpretations: MONOCHROME1, MONOCHROME2, RGB, PALETTE COLOR, YBR FULL 422, and YBR FULL.
It is expected that optimal Window Center and Width values are specified in the DICOM Image Objects if they have greater than 8 bits of image data stored per sample. If optimal Window Center and Width values are not provided, then the EXAMPLE-QUERY-RETRIEVE-SERVER is capable of estimating values using histogram analysis.
For multi-frame image SOP Instances sent using JPEG compression Transfer Syntax, sending a fully specified offset table increases performance, because the entire file does not have to be parsed to find the individual frame offsets. However, the inclusion of an offset table is not required for archiving or viewing of such SOP Instances.
Display of information conveyed using the DICOM Curve Module is not supported. Graphic overlay data sent either embedded in the unused image pixel data bits or in the separate Overlay Data Element is supported for display. Region of Interest overlays are not yet supported.
If an image SOP Instance specifies an aspect ratio that is not one-to-one then the image data will be automatically resized when displayed on the system monitor so that they are always displayed in a one-to-one aspect ratio.
The average throughput performance has been determined to be between 2 and 6 Mega Bytes per second on a 100 Megabit Ethernet network. Actual performance will depend greatly on the performance of the C-STORE SCU, the number of simultaneous active Associations, and the underlying network performance.
Table F.4.2-31. STORAGE-SCP AE C-STORE Response Status Return Reasons
|
Service Status |
Further Meaning |
Error Code |
Reason |
|---|---|---|---|
|
Success |
Success |
0000 |
The Composite SOP Instance was successfully received, verified, and stored in the system database. |
|
Refused |
Out of Resources |
A700 |
Indicates that there was not enough disk space to store the image. Error message is output to the Service Log. The SOP Instance will not be saved. |
|
Error |
Data Set does not match SOP Class |
A900 |
Indicates that the Data Set does not encode a valid instance of the SOP Class specified. This status is returned if the DICOM Object stream can be successfully parsed but does not contain values for one or more mandatory Elements of the SOP Class. The STORAGE-SCP AE does not perform a comprehensive check, as it only checks a subset of required Elements. In addition, if the SOP Class is for a type of image but the SOP Instance does not contain values necessary for its display then this status is returned. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis. |
|
Cannot understand |
C000 |
Indicates that the STORAGE-SCP AE cannot parse the Data Set into Elements. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis. |
|
|
Warning |
Coercion of Data Elements |
B000 |
Indicates that one or more Element values were coerced. Refer to the Attributes defined in Annex for a list of those that can be coerced. Note that return of this status is disabled by default, as some SCUs treat it as an Error code rather than a Warning. |
Note
If a failure condition does occur when handling an Association then all images previously received successfully over the Association are maintained in the EXAMPLE-QUERY-RETRIEVE-SERVER database. No previously successfully received images are discarded. Even if an image is successfully received but an error occurs transmitting the C-STORE Response then this final image is maintained rather than discarded. If the loss of an Association is detected then the Association is closed.
The Behavior of STORAGE-SCP AE during communication failure is summarized in the following table:
Table F.4.2-32. STORAGE-SCP AE Storage Service Communication Failure Reasons
|
Exception |
Reason |
|---|---|
|
Timeout expiry for an expected DICOM Message Request (DIMSE level timeout). I.e. The STORAGE-SCP AE is waiting for the next C-STORE Request on an open Association but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If some Composite SOP Instances have already been successfully received then they are maintained in the database. They are not automatically discarded because of a later failure. |
|
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). I.e. The STORAGE-SCP AE is waiting for the next C-STORE Data Set PDU but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If a C-STORE Data Set has not been fully received then the data already received is discarded. If some Composite SOP Instances have already been successfully received over the Association then they are maintained in the database. |
|
Association aborted by the SCU or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) |
Error message is output to the Service Log. If some Composite SOP Instances have already been successfully received then they are maintained in the database. They are not automatically discarded because of a later failure. |
The associated Activity with the Storage Commitment Push Model service is the communication by the STORAGE-SCP AE to peer AEs that it has committed to permanently store Composite SOP Instances that have been sent to it. It thus allows peer AEs to determine whether the EXAMPLE-QUERY-RETRIEVE-SERVER has taken responsibility for the archiving of specific SOP Instances so that they can be flushed from the peer AE system.
The STORAGE-SCP AE takes the list of Composite SOP Instance UIDs specified in a Storage Commitment Push Model N-ACTION Request and checks if they are present in the EXAMPLE-QUERY-RETRIEVE-SERVER database. As long as the Composite SOP Instance UIDs are present in the database, the STORAGE-SCP AE will consider those Composite SOP Instance UIDs to be successfully archived. The STORAGE-SCP AE does not require the Composite SOP Instances to actually be successfully written to archive media in order to commit to responsibility for maintaining these SOP Instances.
Once the STORAGE-SCP AE has checked for the existence of the specified Composite SOP Instances, it will then attempt to send the Notification request (N-EVENT-REPORT-RQ). The default behavior is to attempt to send this Notification over the same Association that was used by the peer AE to send the original N-ACTION Request. If the Association has already been released or Message transfer fails for some reason then the STORAGE-SCP AE will attempt to send the N-EVENT-REPORT-RQ over a new Association. The STORAGE-SCP AE will request a new Association with the peer AE that made the original N-ACTION Request. The STORAGE-SCP AE can be configured to always open a new Association in order to send the Notification request.
The STORAGE-SCP AE will not cache Storage Commitment Push Model N-ACTION Requests that specify Composite SOP Instances that have not yet been transferred to the EXAMPLE-QUERY-RETRIEVE-SERVER. If a peer AE sends a Storage Commitment Push Model N-ACTION Request before the specified Composite SOP Instances are later sent over the same Association, the STORAGE-SCP AE will not commit to responsibility for such SOP Instances.
The STORAGE-SCP AE does not support the optional Storage Media File-Set ID & UID attributes in the N-ACTION.
The EXAMPLE-QUERY-RETRIEVE-SERVER never automatically deletes Composite SOP Instances from the archive. The absolute persistence of SOP Instances and the maximum archiving capacity for such SOP Instances is dependent on the archiving media and capacity used by the EXAMPLE-QUERY-RETRIEVE-SERVER and is dependent on the actual specifications of the purchased system. It is necessary to check the actual system specifications to determine these characteristics.
The STORAGE-SCP AE will support Storage Commitment Push Model requests for SOP Instances of any of the Storage SOP Classes that are also supported by the STORAGE-SCP AE:
Table F.4.2-33. Supported Referenced SOP Classes in Storage Commitment Push Model N-ACTION Requests
|
Supported Referenced SOP Classes |
|---|
|
US Image Storage (Retired) |
|
US Image Storage |
|
US Multi-frame Storage (Retired) |
|
US Multi-frame Storage |
|
Computed Radiography Image Storage |
|
CT Image Storage |
|
MR Image Storage |
|
Secondary Capture Image Storage |
The STORAGE-SCP AE will return the following Status Code values in N-ACTION Responses:
Table F.4.2-34. STORAGE-SCP AE Storage Commitment Push Model N-ACTION Response Status Return Behavior
|
Service Status |
Further Meaning |
Error Code |
Behavior |
|---|---|---|---|
|
Success |
Success |
0000 |
The SCP has successfully received the Storage Commitment Push Model N-ACTION Request and can process the commitment request for the indicated SOP Instances. |
|
Error |
Processing Failure |
0110 |
Indicates that the Storage Commitment Push Model N-ACTION Request cannot be parsed or fully processed due to a database or system failure. |
|
Error |
Missing Attribute |
0120 |
Indicates that the Storage Commitment Push Model N-ACTION Request cannot be processed because a required attribute is missing from the N-ACTION Request Data Set. |
|
Error |
Missing Attribute Value |
0121 |
Indicates that the Storage Commitment Push Model N-ACTION Request cannot be processed because a Type 1 attribute in the N-ACTION Request Data Set does not specify a value. |
The STORAGE-SCP AE will exhibit the following Behavior according to the Status Code value returned in an N-EVENT-REPORT Response from a destination Storage Commitment Push Model SCU:
Table F.4.2-35. STORAGE-SCP AE N-EVENT-REPORT Response Status Handling Behavior
|
Service Status |
Further Meaning |
Error Code |
Behavior |
|---|---|---|---|
|
Success |
Success |
0000 |
The SCU has successfully received the Storage Commitment Push Model N-EVENT-REPORT Request. Success indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Warning |
Attribute List Error |
0107 |
Transmission of Storage Commitment Push Model N-EVENT-REPORT Request is considered successful. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
|
* |
* |
Any other status code. |
This is treated as a permanent Failure. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
All Status Codes indicating an error or refusal are treated as a permanent failure. The STORAGE-SCP AE can be configured to automatically reattempt the sending of Storage Commitment Push Model N-EVENT-REPORT Requests if an error Status Code is returned or a communication failure occurs. The maximum number of times to attempt sending as well as the time to wait between attempts is configurable.
Table F.4.2-36. STORAGE-SCP AE Storage Commitment Push Model Communication Failure Behavior
|
Exception |
Behavior |
|---|---|
|
Timeout expiry for an expected DICOM Message Request (DIMSE level timeout). I.e. The STORAGE-SCP AE is waiting for the next N-ACTION Request on an open Association but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. If some Composite SOP Instances have been successfully received over the same Association via the Storage Service then they are maintained in the database. They are not automatically discarded because of a later Storage Commitment messaging failure. Any previously received Storage Commitment Push Model N-ACTION Requests will still be fully processed. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Timeout expiry for an expected DICOM Message Response (DIMSE level timeout). I.e. The STORAGE-SCP AE is waiting for the next N-EVENT-REPORT Response on an open Association but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. If some Composite SOP Instances have been successfully received over the same Association via the Storage Service then they are maintained in the database. They are not automatically discarded because of a later Storage Commitment messaging failure. Any previously received Storage Commitment Push Model N-ACTION Requests will still be fully processed. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). |
The Association is aborted by issuing a DICOM A-ABORT. If some Composite SOP Instances have been successfully received over the same Association via the Storage Service then they are maintained in the database. They are not automatically discarded because of a later Storage Commitment messaging failure. Any previously received Storage Commitment Push Model N-ACTION Requests will still be fully processed. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
|
Association A-ABORTed by the SCU or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) |
The TCP/IP socket is closed. If some Composite SOP Instances have been successfully received over the same Association via the Storage Service then they are maintained in the database. They are not automatically discarded because of a later Storage Commitment messaging failure. Any previously received Storage Commitment Push Model N-ACTION Requests will still be fully processed. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
The EXAMPLE-QUERY-RETRIEVE-SERVER supports a single network interface. One of the following physical network interfaces will be available depending on installed hardware options:
EXAMPLE-QUERY-RETRIEVE-SERVER conforms to the System Management Profiles listed in Table F.4.3-2. All requested transactions for the listed profiles and actors are supported. It does not support any optional transactions.
Table F.4.3-2. Supported System Management Profiles
|
Profile Name |
Actor |
Protocols Used |
Optional Transactions |
Security Support |
|---|---|---|---|---|
|
Network Address Management |
DHCP Client |
DHCP |
N/A |
|
|
DNS Client |
DNS |
N/A |
DHCP can be used to obtain TCP/IP network configuration information. The network parameters obtainable via DHCP are shown in Table F.4.3-3. The Default Value column of the table shows the default used if the DHCP server does not provide a value. Values for network parameters set in the Service/Installation tool take precedence over values obtained from the DHCP server. Support for DHCP can be configured via the Service/Installation Tool. The Service/Installation tool can be used to configure the machine name. If DHCP is not in use, TCP/IP network configuration information can be manually configured via the Service/Installation Tool.
Table F.4.3-3. Supported DHCP Parameters
|
DHCP Parameter |
Default Value |
|---|---|
|
IP Address |
None |
|
Hostname |
Requested machine name |
|
List of NTP servers |
Empty list |
|
List of DNS servers |
Empty list |
|
Routers |
Empty list |
|
Static routes |
None |
|
Domain name |
None |
|
Subnet mask |
Derived from IP Address (see service manual) |
|
Broadcast address |
Derived from IP Address (see service manual) |
|
Default router |
None |
|
Time offset |
Site configurable (from Time zone) |
|
MTU |
Network Hardware Dependent |
|
Auto-IP permission |
No permission |
If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted.
DNS can be used for address resolution. If DHCP is not in use or the DHCP server does not return any DNS server addresses, the identity of a DNS server can be configured via the Service/Installation Tool. If a DNS server is not in use, local mapping between hostname and IP address can be manually configured via the Service/Installation Tool.
The mapping from AE Title to TCP/IP addresses and ports is configurable and set at the time of installation by Installation Personnel.
Table F.4.4-1. Default Application Entity Characteristics
|
Application Entity |
Role |
Default AE Title |
Default TCP/IP Port |
|---|---|---|---|
|
STORAGE-SCU |
SCU |
EX_STORE_SCU |
None |
|
STORAGE-SCP |
SCP |
EX_STORE_SCP |
4000 |
|
QUERY-RETRIEVE-SCP |
SCP |
EX_QUERY_SCP |
5000 |
The STORAGE-SCU and QUERY-RETRIEVE-SCP Application Entities can be configured to have the same AE Title. The STORAGE-SCP Application Entity must not have the same AE Title as the other two.
The mapping of external AE Titles to TCP/IP addresses and ports is configurable and set at the time of installation by Installation Personnel. This mapping is necessary for resolving the IP address and port of C-MOVE Destination Application Entities and must be correctly configured for the QUERY-RETRIEVE-SCP AE to correctly function as a C-MOVE SCP.
Table F.4.4-2. Configuration Parameters
|
Parameter |
Configurable |
Default Value |
|---|---|---|
|
General Parameters |
||
|
Maximum PDU size I can receive |
Yes |
128kbytes |
|
Maximum PDU size I can send |
Yes |
128kbytes |
|
Time-out waiting for response to TCP/IP connect() request. (Low-level timeout) |
Yes |
10 s |
|
Time-out waiting for A-ASSOCIATE RQ PDU on open TCP/IP connection. (ARTIM timeout) |
Yes |
30 s |
|
Time-out waiting for acceptance or rejection response to an Association Open Request. (Application Level timeout) |
Yes |
30s |
|
Time-out waiting for acceptance of a TCP/IP message over the network. (Low-level timeout) |
Yes |
30 s |
|
Time-out for waiting for data between TCP/IP packets. (Low-level timeout) |
Yes |
30 s |
|
The Windows NT TCP/IP socket buffer size is set to 1,342,177 bytes in order to improve image data throughput performance. |
No |
1,342,177 bytes |
|
STORAGE-SCU AE Parameters |
||
|
Maximum number of simultaneous Associations. |
Yes |
10 |
|
STORAGE-SCU AE time-out waiting for a Response to a C-STORE-RQ. (DIMSE timeout) |
Yes |
5 minutes |
|
STORAGE-SCU AE number of times a failed send job to a C-MOVE Destination is automatically retried. |
No |
0 |
|
STORAGE-SCP AE Parameters |
||
|
Maximum PDU Size |
Yes |
16384 |
|
Maximum number of simultaneous Associations (Can be configured to be a maximum total number or a maximum per external SCU AE) |
Yes |
10 |
|
STORAGE-SCP AE time-out waiting on an open Association for the next Request message (C-STORE-RQ, Association Close Request. etc.) (DIMSE timeout) |
Yes |
15 minutes |
|
STORAGE-SCP AE maximum number of simultaneous Associations |
Yes NoteCan be configured with a maximum per external AE |
10 |
|
Permanent archival of SOP Instances sent by a peer AE to the STORAGE-SCP AE in response to a retrieval request from QUERY-RETRIEVE AE. |
Yes |
FALSE (Such received SOP Instances are not archived.) |
|
Permanent archival of SOP Instances sent unsolicited by a peer AE to the STORAGE-SCP AE. I.e. Not in response to a retrieval request from QUERY-RETRIEVE AE. |
Yes |
TRUE (Such received SOP Instances are archived.) |
|
Always open a new Association to send a Storage Commitment Push Model Notification request (N-EVENT-REPORT-RQ). |
Yes |
FALSE (Default is to try and send Notifications over original Association opened by peer AE). |
|
Maximum number of times to attempt sending a Storage Commitment Push Model N-EVENT-REPORT Request when an error status is returned or communication failure occurs. |
Yes |
5 |
|
Time to wait between attempts to send a Storage Commitment Push Model N-EVENT-REPORT Request when an error status is returned or communication failure occurs. |
Yes |
5 minutes |
|
QUERY-RETRIEVE-SCP AE Parameters |
||
|
Maximum PDU Size |
Yes |
16384 |
|
Maximum number of simultaneous Associations (Can be configured to be a maximum total number or a maximum per external SCU AE) |
Yes |
10 |
|
QUERY-RETRIEVE-SCP AE time-out waiting on an open Association for the next message (C-FIND-RQ, C-MOVE-RQ, Association Close Request. etc.) (DIMSE timeout) |
Yes |
3 minutes |
|
QUERY-RETRIEVE-SCP AE maximum number of simultaneous Associations |
Yes NoteCan be configured with a maximum per external AE |
10 |