DICOM PS3.2 2024b - Conformance

N.5.2.6 Storage Commitment Service

N.5.2.6.1 SCU of the Storage Commitment SOP Class

As a Service Class User of the Storage Commitment SOP Class, the <Product> uses the N-ACTION-RQ message to request storage commitment from a remote SCP. In turn, it receives N-EVENT-REPORT-RQ messages from the SCP indicating success or failure of the request.

[Provide a list of Storage SOP Classes for which the product requests storage commitment. Also indicate whether this is configurable.]

[If Storage Commitment is provided for all supported SOP Classes, you can provide a reference to the list of supported Storage SOP Classes in Section N.1.1]

As a Service Class User of the Storage Commitment Push Model SOP Classes the product supports committing all Storage SOP Classes listed in Section N.1.1 Content and Transfer are supported.

[If Storage Commitment is provided for a subset of all supported Storage SOP Classes, provide a list of those, and delete the paragraph above.]

[Specify whether your product supports the Storage Media File Set ID and UID Attributes in the N-ACTION-Request. If this is supported, also list the Media Application profiles supported in this context.]

[Describe whether your product supports receiving the N-EVENT-REPORT request on the same Association as the N-ACTION.]

[Document the Behavior of <product> upon receiving an N-EVENT-REPORT with an Event Type ID of 1, e.g.

Upon receiving an N-EVENT-REPORT with an Event Type of 1 Instances will be removed from system after a configurable amount of time or if space is needed]

Table N.5-15 lists the behavior of <Product> for each possible Failure Reason (0008,1197) in the Failed SOP Sequence (0008,1198) upon receiving an N-EVENT-REPORT request from the SCP with an Event Type ID of 2 (Storage Commitment Request Complete - Failures Exist).

[Fill in the behavior of your product upon encountering the Status Code. Note that for each code, that is listed in the table, a behavior needs to be provided. If your system does not support specific codes, list "Code is ignored by the system".]

Table N.5-15. Failure Behavior for Storage Commitment SCU

Status Code

Description

Behavior

0110

Processing failure: A general failure in processing the operation was encountered.

The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances

0112

No such object instance: One or more of the elements in the Referenced SOP Instance Sequence was not available.

The instance is re-sent, and the N-ACTION request is repeated.

0119

Class / Instance conflict: The SOP Class of an element in the Referenced SOP Instance Sequence did not correspond to the SOP Class registered for this SOP Instance at the SCP.

Code is ignored by the system

0122

Referenced SOP Class not supported: Storage Commitment has been requested for a SOP Instance with a SOP Class that is not supported by the SCP.

The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances

0131

Duplicate Transaction UID: The Transaction UID of the Storage Commitment Request is already in use.

The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances

0213

Resource limitation: The SCP does not currently have enough resources to store the requested SOP Instance(s).

The request for storage commitment is marked as failed. A warning is displayed if the user tries to delete affected instances


[Describe your product behavior in case the N-EVENT-REPORT request is not received after a specific time, e.g., <Product> expects to receive the N-EVENT-REPORT request in a configurable time frame after the N-ACTION is sent. If the N-EVENT-REPORT is not received within this configurable timeframe it repeats the N-ACTION-REQUEST.]

[Describe the policies for deleting instances from your product, both upon successful storage commitment as well as in failure scenarios.]

DICOM PS3.2 2024b - Conformance