G.4.2.2 STORAGE-SCU

G.4.2.2.1 SOP Classes

STORAGE-SCU provides Standard Conformance to the following SOP Class(es):

Table G.4.2-7SOP Classes Supported by STORAGE-SCU

SOP Class Name SOP Class UID SCU SCP
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Yes No
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Yes No
MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Yes No
Digital Mammography X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.2 Yes No
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1 Yes No
Hanging Protocol Storage 1.2.840.10008.5.1.4.38.1 Yes No

G.4.2.2.2 Association Policies

G.4.2.2.2.1 General

STORAGE-SCU initiates but never accepts associations.

Table G.4.2-8Maximum PDU Size Received as a SCP for STORAGE-SCU

Maximum PDU size received Unlimited

G.4.2.2.2.2 Number of Associations

Table G.4.2-9Number of Associations as a SCP for STORAGE-SCU

Maximum number of simultaneous associations 1

G.4.2.2.2.3 Asynchronous Nature

STORAGE-SCU will only allow a single outstanding operation on an Association. Therefore, STORAGE-SCU will not perform asynchronous operations window negotiation.

G.4.2.2.2.4 Implementation Identifying Information

Table G.4.2-10DICOM Implementation Class and Version for STORAGE-SCU

Implementation Class UID 1.2.840.999999.3.6
Implementation Version Name Viewer1.0

G.4.2.2.3 Association Initiation Policy

STORAGE-SCU attempts to initiate a new association for each instance it attempts to transfer.

G.4.2.2.3.1 Activity – Send Storage Request

G.4.2.2.3.1.1 Description and Sequencing of Activities

For each Image, Presentation State, or Hanging Protocol Instance selected from the user interface to be transferred, a single attempt will be made to transmit it to the selected remote AE. If the send fails, for whatever reason, no retry will be performed, and an attempt will be made to send the next instance.

G.4.2.2.3.1.2 Proposed Presentation Contexts

Table G.4.2-11Proposed Presentation Contexts for STORAGE-SCU and Receive Storage Request

Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended Negotiation
Name UID Name UID
See Table G.4.2-7 See Table G.4.2-7 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None

STORAGE-SCU will propose Presentation Contexts only for the SOP Class of the instance that is to be transferred.

For that SOP Class, STORAGE-SCU will propose multiple Presentation Contexts, one for each of the supported Transfer Syntaxes, and an additional Presentation Context with all of the supported Transfer Syntaxes, in order to determine which Transfer Syntaxes the remote SCP supports, and which it prefers.

G.4.2.2.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

G.4.2.2.3.1.3 SOP Specific Conformance

G.4.2.2.3.1.3.1 SOP Specific Conformance to Storage Service Class

STORAGE-SCU provides standard conformance to the Storage Service Class.

G.4.2.2.3.1.3.2 SOP Specific Conformance to Hanging Protocol Storage Service Class

STORAGE-SCU provides standard conformance to the Hanging Protocol Storage Service Class.

In Hanging Protocol Instances created on the Viewer, no Private Attributes are used as the value of Selector Attribute (0072,0026) in any of the Sequence Attributes to which it applies.

G.4.2.2.3.1.3.3 Presentation Context Acceptance Criterion

STORAGE-SCU does not accept associations.

G.4.2.2.3.1.3.4 Transfer Syntax Selection Policies

STORAGE-SCU prefers explicit Transfer Syntaxes. If offered a choice of Transfer Syntaxes in the accepted Presentation Contexts, it will apply the following priority to the choice of Presentation Context to use for the C-STORE operation:

  1. first encountered explicit Transfer Syntax,

  2. default Transfer Syntax.

G.4.2.2.3.1.3.4 Response Status

STORAGE-SCU will behave as described in the Table below in response to the status returned in the C-STORE response command message.

Table G.4.2-12Response Behavior for STORAGE-SCU and Send Storage Request

Service Status Further Meaning Status Codes Behavior
Failure Refused: Out of Resources A7xx The user is notified and the failure is logged
Error: Data Set does not match SOP Class A9xx The user is notified and the failure is logged
Error: Cannot understand Cxxx The user is notified and the failure is logged
Warning Coercion of Data Elements B000 Ignored
Data Set does not match SOP Class B007 Ignored
Elements Discarded B006 Ignored
Success 0000 Ignored

G.4.2.2.4 Association Acceptance Policy

STORAGE-SCU does not accept associations.