Page 236 |
DICOM PS3.2 2020a - Conformance |
Table F.4.2-10. DICOM Application Context for QUERY-RETRIEVE-SCP AE
Application Context Name |
1.2.840.10008.3.1.1.1 |
F.4.2.2.2.2 Number of Associations |
|
TheQUERY-RETRIEVE-SCPAEcansupportmultiplesimultaneousAssociations.EachtimetheQUERY-RETRIEVE-SCPAEreceives 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) |
F.4.2.2.2.3 Asynchronous Nature |
|
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) |
F.4.2.2.2.4 Implementation Identifying Information |
|
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 |
NotethattheSTORAGE-SCUAE,andQUERY-RETRIEVE-SCPAEusethesameImplementationClassUID.AllEXAMPLE-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.
F.4.2.2.3 Association Initiation Policy
The QUERY-RETRIEVE-SCP AE does not initiate Associations.
F.4.2.2.4 Association Acceptance Policy
F.4.2.2.4.1 Activity - Handling Query and Retrieval Requests
F.4.2.2.4.1.1 Description and Sequencing of Activity
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
- Standard -
DICOM PS3.2 2020a - Conformance |
Page 237 |
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.
Peer C-MOVE |
|
Peer Query - |
|
QUERY - |
|
STORAGE - |
|
Retrieve |
|
RETRIEVE - |
|
||
Destination AE |
|
|
|
SCU AE |
||
|
SCU AE |
|
SCP AE |
|
||
|
|
|
|
|
||
|
|
|
|
|
|
|
1.Open Association
2.Peer AE Queries for Patient, Study, Series, or Image Information
3.Return Patient, Study, Series, or Image Information
4.Close Association
5.Open Association
6.Peer AE Queries for Patient, Study, Series, or Image Information
7.Notification of Images to be sent to C-MOVE Destination AE in Response
8.Open Association
REPEAT...
9a. Images Sent to C-MOVE Destination
9b. Notification of success or failure for each attempt
9c. C-MOVE-RSP sent for each Image Sent
10.Close Association
11.Final C-MOVE-RSP set
12.Close Association
Figure F.4.2-2. Sequencing of Activity - Handling Query and Retrieval Requests
The following sequencing constraints illustrated in Figure F.4.2-2 apply to the QUERY-RETRIEVE-SCP AE for handling queries (C- FIND-Requests) :
1.Peer AE opens an Association with the QUERY-RETRIEVE-SCP AE.
2.Peer AE sends a C-FIND-RQ Message
3.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.
4.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) :
1.Peer AE opens an Association with the QUERY-RETRIEVE-SCP AE.
2.Peer AE sends a C-MOVE-RQ Message
- Standard -
Page 238 |
DICOM PS3.2 2020a - Conformance |
3.QUERY-RETRIEVE-SCP AE notifies the STORAGE-SCU AE to send the Composite SOP Instances to the peer C-MOVE Des- tination AE as indicated in the C-MOVE-RQ.
4.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.
5.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.
6.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:
a.1 - DICOM UL service-user
b.2 - DICOM UL service-provider (ASCE related function)
c.3 - DICOM UL service-provider (Presentation related function)
Table F.4.2-14. Association Rejection Reasons
Result |
Source |
Reason/Diag |
Explanation |
|
2 - |
c |
2 |
- local-limit-exceeded |
The (configurable) maximum number of simultaneous |
rejected-transient |
|
|
|
Associations has been reached. An Association request with |
|
|
|
|
the same parameters may succeed at a later time. |
2 - |
c |
1 |
- temporary-congestion |
No Associations can be accepted at this time due to the |
rejected-transient |
|
|
|
real-timerequirementsofhigherpriorityactivities(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 - |
a |
2 |
- |
The Association request contained an unsupported |
rejected-permanent |
application-context-name-not-supportedApplication Context Name. An association request with the |
|||
|
|
|
|
same parameters will not succeed at a later time. |
1 - |
a |
7 |
- called-AE-title-not-recognized |
The Association request contained an unrecognized Called |
rejected-permanent |
|
|
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 - |
a |
3 |
- calling-AE-title-not-recognized |
The Association request contained an unrecognized Calling |
rejected-permanent |
|
|
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 - |
b |
1 |
- no-reason-given |
TheAssociationrequestcouldnotbeparsed.AnAssociation |
rejected-permanent |
|
|
request with the same format will not succeed at a later time. |
|
F.4.2.2.4.1.2 Accepted Presentation Contexts
QUERY-RETRIEVE-SCP AE will accept Presentation Contexts as shown in the following table:
- Standard -
DICOM PS3.2 2020a - Conformance Page 239
Table F.4.2-15. Accepted Presentation Contexts By the QUERY-RETRIEVE-SCP AE
|
|
Presentation Context Table |
|
|
|
|
Abstract Syntax |
|
Transfer Syntax |
Role |
Extended |
Name |
UID |
Name |
UID |
|
Negotiation |
|
|
||||
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little1.2.840.10008.1.2 SCP |
None |
||
|
|
Endian |
|
|
|
Patient Root Q/R |
1.2.840.10008.5.1.4.1.2.1.1DICOM Implicit VR Little1.2.840.10008.1.2 SCP |
None |
|||
Information Model - FIND |
Endian |
|
|
|
|
Patient Root Q/R |
1.2.840.10008.5.1.4.1.2.1.2DICOM Implicit VR Little1.2.840.10008.1.2 SCP |
None |
|||
Information Model - MOVE |
Endian |
|
|
|
|
Study Root Q/R Information1.2.840.10008.5.1.4.1.2.2.1DICOM Implicit VR Little1.2.840.10008.1.2 SCP |
None |
||||
Model - FIND |
|
Endian |
|
|
|
Study Root Q/R Information1.2.840.10008.5.1.4.1.2.2.2DICOM Implicit VR Little1.2.840.10008.1.2 SCP |
None |
||||
Model - MOVE |
|
Endian |
|
|
|
F.4.2.2.4.1.3 SOP Specific Conformance for Query SOP Classes
The QUERY-RETRIEVE-SCP AE supports hierarchical queries and not relational queries. There are no attributes always returned bydefault.Onlythoseattributesrequestedinthequeryidentifierarereturned.QueryresponsesalwaysreturnvaluesfromtheEXAMPLE- 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 |
Tag |
VR |
Types of Matching |
Attribute Name |
|
|
|
SOP Common |
|
|
|
Specific Character Set |
0008,0005 |
CS |
NONE |
Patient Level |
|
|
|
Patient's Name |
0010,0010 |
PN |
S,*,U |
Patient ID |
0010,0020 |
LO |
S,*,U |
Patient's Birth Date |
0010,0030 |
DA |
S,U |
Patient's Sex |
0010,0040 |
CS |
S,U |
Other Patient IDs |
0010,1000 |
LO |
NONE |
Other Patient Names |
0010,1001 |
PN |
NONE |
Study Level |
|
|
|
- Standard -
Page 240 |
DICOM PS3.2 2020a - Conformance |
|
|
Level Name |
Tag |
VR |
Types of Matching |
Attribute Name |
|
|
|
Study Date |
0008,0020 |
DA |
S,R,U |
Study Time |
0008,0030 |
TM |
R,U |
Accession Number |
0008,0050 |
SH |
S,*,U |
Study ID |
0020,0010 |
SH |
S,*,U |
Study Instance UID |
0020,000D |
UI |
S,U,L |
Referring Physician's Name |
0008,0090 |
PN |
S,*,U |
Study Description |
0008,1030 |
LO |
S,*,U |
Series Level |
|
|
|
Modality |
0008,0060 |
CS |
S,U |
Series Number |
0020,0011 |
IS |
S,*,U |
Series Instance UID |
0020,000E |
UI |
S,U,L |
Operator's Name |
0008,1070 |
PN |
NONE |
Image Level |
|
|
|
Instance Number |
0020,0013 |
IS |
S,*,U |
SOP Instance UID |
0008,0018 |
UI |
S,U,L |
Table F.4.2-17. Study Root C-FIND SCP Supported Elements |
|||
Level Name |
Tag |
VR |
Types of Matching |
Attribute Name |
|
|
|
SOP Common |
|
|
|
Specific Character Set |
0008,0005 |
CS |
NONE |
Study Level |
|
|
|
- Standard -