9.1.1 C-STORE SERVICE

The C-STORE service is used by a DIMSE-service-user to store a composite SOP Instance on a peer DIMSE-service-user. It is a confirmed service.

9.1.1.1 C-STORE parameters

Table 9.1-1 lists the parameters of this service.

Table 9.1-1 C-STORE PARAMETERS

DIMSE-C Parameter Name Req/Ind Rsp/Conf
Message ID M U
Message ID Being Responded To M
Affected SOP Class UID M U(=)
Affected SOP Instance UID M U(=)
Priority M
Move Originator Application Entity Title U
Move Originator Message ID U
Data Set M
Status M

9.1.1.1.1 Message ID

This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE-service-provider may have in progress. No two identical values for the Message ID (0000,0110) shall be used for outstanding operations or notifications.

Notes: 1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

9.1.1.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

9.1.1.1.3 Affected SOP class UID

For the request/indication, this parameter specifies the SOP Class for the storage. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

9.1.1.1.4 Affected SOP instance UID

For the request/indication, this parameter specifies the SOP Instance to be stored. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

9.1.1.1.5 Priority

This parameter specifies the priority of the C-STORE operation. It shall be one of LOW, MEDIUM, or HIGH.

9.1.1.1.6 Move originator application entity title

This parameter specifies the DICOM AE Title of the DICOM AE which invoked the C-MOVE operation from which this C-STORE sub-operation is being performed.

9.1.1.1.7 Move originator message ID

This parameter specifies the Message ID (0000,0110) of the C-MOVE request/indication primitive from which this C-STORE sub-operation is being performed.

9.1.1.1.8 Data set

The Data Set accompanying the C-STORE primitive contains the Attributes of the Composite SOP Instance to be stored.

9.1.1.1.9 Status

This parameter contains the error or success notification for the operation. It shall be included by the performing DIMSE-service-user in the response/confirmation. The following types of status may occur in a response/confirmation:

a) Refused: Out of Resources⎯This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because it was out of resources.

b) Refused: SOP Class Not Supported⎯This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because the SOP Class is not supported,

c Error: Cannot Understand⎯This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because it cannot understand certain Data Elements.

d) Error: Data Set does not match SOP Class⎯This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because the Data Set does not match the SOP Class.

e) Warning⎯This indicates that the peer DIMSE-service-user was able to store the composite SOP Instance, but detected a probable error.

f) Success⎯ This indicates that the composite SOP Instance was successfully stored.

9.1.1.2 C-STORE service procedures

The following C-STORE procedures apply:

a) The invoking DIMSE-service-user requests that the performing DIMSE-service-user store a composite SOP Instance by issuing a C-STORE request primitive to the DIMSE-service-provider.

b) The DIMSE-service-provider issues a C-STORE indication primitive to the performing DIMSE-service-user.

c) The performing DIMSE-service-user reports acceptance or rejection of the C-STORE request primitive by issuing a C-STORE response primitive to the DIMSE-service-provider,

d) The DIMSE-service-provider issues a C-STORE confirmation primitive to the invoking DIMSE-service-user, completing the C-STORE operation.

The performing DIMSE-service-user may return a C-STORE response primitive with the status of Failed or Refused before the entire C-STORE indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A C-STORE response primitive with the status of Success or Warning shall not be returned until the entire C-STORE indication has been received by the performing DIMSE-service-user.

Note: Such an occurrence of a "Failed" response is often called an early failed response.