Материал: part02
Page 246 |
DICOM PS3.2 2020a - Conformance |
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.
Peer Storage
Commitment
STORAGE -
SCU AE
SCP AE
1.Peer AE Opens Association
2.Peer AE Requests Storage Commitment of Composite SOP Instances
3.Peer AE Closes Association
4.Open Association
5.Send Storage Commitment Notification for Composite SOP Instances
6.Close Association
Figure F.4.2-3. Sequencing of Activity - Send Storage Commitment Notification Over New Association
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:
1.Peer AE opens an Association with the STORAGE-SCP AE.
2.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).
3.Peer AE closes the Association before the STORAGE-SCP AE can successfully send the Storage Commitment Push Model Notification (N-EVENT-REPORT-RQ).
4.STORAGE-SCP AE opens an Association with the peer AE.
5.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.
6.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.
F.4.2.3.3.1.2 Proposed Presentation Contexts
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 |
||
Name |
UID |
Name |
UID |
|
Negotiation |
|
|
||||
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCU |
None |
|
|
Endian |
|
|
|
Storage Commitment |
1.2.840.10008.1.20.1DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
Push Model |
|
Endian |
|
|
|
Storage Commitment |
1.2.840.10008.1.20.1DICOM Explicit VR Little |
1.2.840.10008.1.2.1 SCP |
None |
||
Push Model |
|
Endian |
|
|
|
- Standard -
DICOM PS3.2 2020a - Conformance |
Page 247 |
F.4.2.3.3.1.3 SOP Specific Conformance for Storage SOP Classes
The associated Activity with the Storage Commitment Push Model service is the communication by the STORAGE-SCP AE to peer AEsthatithascommittedtopermanentlystoreCompositeSOPInstancesthathavebeensenttoit.ItthusallowspeerAEstodetermine 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 ori- ginalAssociationoverwhichthiswassentisnolongeropen.ForadetailedexplanationoftheSOPspecificBehavioroftheSTORAGE- SCP AE in this case please refer to 4.2.4.4.1.3.3, Storage Commitment Push Model as an SCP.
F.4.2.3.3.1.4 SOP Specific Conformance for Verification SOP Class
StandardconformanceisprovidedtotheDICOMVerificationServiceClassasanSCU.TheVerificationServiceasanSCUisactually onlysupportedasadiagnosticservicetoolfornetworkcommunicationissues.ItcanbeusedtotestwhetherAssociationscanactually 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).
F.4.2.3.4 Association Acceptance Policy
F.4.2.3.4.1 Activity - Receive Images and Storage Commitment Requests
F.4.2.3.4.1.1 Description and Sequencing of Activity
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.
Peer Storage
Commitment
STORAGE -
SCU AE
SCP AE
1.Peer AE Opens Association
2.Peer AE Sends Composite SOP Instances
3.Peer AE Requests Storage Commitment of Composite SOP Instances
4.Send Storage Commitment Notification for Composite SOP Instances
5.Peer AE Close Association
Figure F.4.2-4. Sequencing of Activity - Receive Images and Storage Commitment Requests
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:
1.Peer AE opens an Association with the STORAGE-SCP AE.
2.Peer AE sends zero or more Composite SOP Instances.
3.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).
- Standard -
Page 248 |
DICOM PS3.2 2020a - Conformance |
4.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.
5.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 Asso- ciation 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).
TheSTORAGE-SCPAEmayrejectAssociationattemptsasshownintheTablebelow.TheResult,SourceandReason/Diagcolumns 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-29. 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.3.4.1.2 Accepted Presentation Contexts
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
- Standard -
DICOM PS3.2 2020a - Conformance |
Page 249 |
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 En- dian 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 SyntaxesareproposedinasinglePresentationContextthentheacceptedTransferSyntaxwillbeExplicitVRLittleEndian.Thisorder 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 |
||
Name |
UID |
Name |
UID |
|
Negotiation |
|
|
||||
Verification |
1.2.840.10008.1.1 |
DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
|
Endian |
|
|
|
Storage Commitment 1.2.840.10008.1.20.1 |
DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
Push Model |
|
Endian |
|
|
|
Storage Commitment 1.2.840.10008.1.20.1 |
DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
Push Model |
|
Endian |
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
(Retired) |
|
Endian |
|
|
|
|
|
|
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
(Retired) |
|
Endian |
|
|
|
|
|
|
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6 DICOM Explicit JPEG |
1.2.840.10008.1.2.4.50SCP |
None |
||
(Retired) |
|
baseline lossy compression |
|
|
|
|
|
|
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
|
|
Endian (uncompressed) |
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
|
|
Endian (uncompressed) |
|
|
|
US Image Storage |
1.2.840.10008.5.1.4.1.1.6.1DICOM Explicit JPEG |
1.2.840.10008.1.2.4.50SCP |
None |
||
|
|
baseline lossy compression |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
||
(Retired) |
|
Endian |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
||
(Retired) |
|
Endian |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3 DICOM Explicit JPEG |
1.2.840.10008.1.2.4.50SCP |
None |
|||
(Retired) |
|
baseline lossy compression |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3.1DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
||
|
|
Endian (uncompressed) |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3.1DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
||
|
|
Endian (uncompressed) |
|
|
|
US Multi-frame Storage1.2.840.10008.5.1.4.1.1.3.1DICOM Explicit JPEG |
1.2.840.10008.1.2.4.50SCP |
None |
|||
|
|
baseline lossy compression |
|
|
|
- Standard -
Page 250 |
|
DICOM PS3.2 2020a - Conformance |
|
|
|
|
|
Presentation Context Table |
|
|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended |
||
Name |
UID |
Name |
UID |
|
Negotiation |
|
|
||||
Computer Radiography1.2.840.10008.5.1.4.1.1.1 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
||
Image Storage |
|
Endian |
|
|
|
Computer Radiography1.2.840.10008.5.1.4.1.1.1 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
||
Image Storage |
|
Endian |
|
|
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
|
|
Endian |
|
|
|
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
|
|
Endian |
|
|
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
|
|
Endian |
|
|
|
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
|
|
Endian |
|
|
|
NM Image Storage |
1.2.840.10008.5.1.4.1.1.5 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
(Retired) |
|
Endian |
|
|
|
Secondary Capture |
1.2.840.10008.5.1.4.1.1.7 DICOM Implicit VR Little |
1.2.840.10008.1.2 |
SCP |
None |
|
Image Storage |
|
Endian |
|
|
|
Secondary Capture |
1.2.840.10008.5.1.4.1.1.7 DICOM Explicit VR Little |
1.2.840.10008.1.2.1 |
SCP |
None |
|
Image Storage |
|
Endian |
|
|
|
Secondary Capture |
1.2.840.10008.5.1.4.1.1.7 DICOM Explicit JPEG lossy1.2.840.10008.1.2.4.50SCP |
None |
|||
Image Storage |
|
compression |
|
|
|
F.4.2.3.4.1.3 SOP Specific Conformance for Verification SOP Class
The STORAGE-SCP AE provides standard conformance to the Verification SOP Class as an SCP.
F.4.2.3.4.1.4 SOP Specific Conformance for Storage SOP Classes
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.
TheSTORAGE-SCPAEdoesnothaveanydependenciesonthenumberofAssociationsusedtosendimagestoit.Imagesbelonging 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 DICOMformatfiles.InadditiontosavingallElementsinfiles,asubsetoftheElementsarestoredintheEXAMPLE-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 receivedSOPInstanceifitconflictswithanexistingSOPInstanceUID.Analternativeconfigurationispossiblethatcausestheoriginal 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.
Forthepurposesofimagedisplaythesystemsupportsthefollowingphotometricinterpretations: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.
- Standard -