DICOM PS3.4 2017b - Service Class Specifications

J.3.3 Notifications
Prev | J.3 Storage Commitment Push Model SOP Class | Next

### J.3.3 Notifications

The DICOM AEs that claim conformance to this SOP Class as an SCP shall invoke the N-EVENT-REPORT request. The DICOM AEs that claim conformance to this SOP Class as an SCU shall be capable of receiving the N-EVENT-REPORT request.

#### J.3.3.1 Storage Commitment Result

The Storage Commitment Result notification allows an SCP to inform the SCU whether or not it has accepted storage commitment responsibility for the SOP Instances referenced by a Storage Commitment Request. This notification is also used to convey error information (i.e., storage commitment could not be achieved for one or more of the referenced SOP Instances). This notification shall be invoked through the N-EVENT-REPORT primitive.

##### J.3.3.1.1 Event Information

The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Event Types and Event Information as specified in Table J.3-2.

Table J.3-2. Storage Commitment Result - Event Information

Event Type Name | Event Type ID | Attribute Name | Tag | Requirement Type SCU/SCP
--- | --- | --- | --- | ---
Storage Commitment Request Successful | 1 | Transaction UID | (0008,1195) | -/1
|  | Retrieve AE Title | (0008,0054) | -/3 See Section J.3.3.1.1.1.
|  | Storage Media File-Set ID | (0088,0130) | -/3 See Section J.3.3.1.1.2.
|  | Storage Media File-Set UID | (0088,0140) | -/3 See Section J.3.3.1.1.2.
|  | Referenced SOP Sequence | (0008,1199) | -/1
|  | >Referenced SOP Class UID | (0008,1150) | -/1
|  | >Referenced SOP Instance UID | (0008,1155) | -/1
|  | >Retrieve AE Title | (0008,0054) | -/3 See Section J.3.3.1.1.1.
|  | >Storage Media File-Set ID | (0088,0130) | -/3 See Section J.3.3.1.1.2.
|  | >Storage Media File-Set UID | (0088,0140) | -/3 See Section J.3.3.1.1.2.
Storage Commitment Request Complete - Failures Exist | 2 | Transaction UID | (0008,1195) | -/1
|  | Retrieve AE Title | (0008,0054) | -/3 See Section J.3.3.1.1.1.
|  | Storage Media File-Set ID | (0088,0130) | -/3 See Section J.3.3.1.1.2.
|  | Storage Media File-Set UID | (0088,0140) | -/3 See Section J.3.3.1.1.2.
|  | Referenced SOP Sequence | (0008,1199) | -/1C This Attribute shall be provided if storage commitment for one or more SOP Instances has been successful
|  | >Referenced SOP Class UID | (0008,1150) | -/1
|  | >Referenced SOP Instance UID | (0008,1155) | -/1
|  | >Retrieve AE Title | (0008,0054) | -/3 See Section J.3.3.1.1.1.
|  | >Storage Media File-Set ID | (0088,0130) | -/3 See Section J.3.3.1.1.2.
|  | >Storage Media File-Set UID | (0088,0140) | -/3 See Section J.3.3.1.1.2.
|  | Failed SOP Sequence | (0008,1198) | -/1
|  | >Referenced SOP Class UID | (0008,1150) | -/1
|  | >Referenced SOP Instance UID | (0008,1155) | -/1
|  | >Failure Reason | (0008,1197) | -/1

###### J.3.3.1.1.1 Retrieve AE Title Attribute

If present, the Retrieve AE Title (0008,0054) shall appear either outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that sequence, but not both. If they appear outside of the sequence, then all of the SOP Instances within the sequence shall be retrievable from the specified Retrieve AE Title. If they appear within an Item of that sequence, then the SOP Instance referenced to by that Item shall be retrievable from the specified Retrieve AE Title.

###### J.3.3.1.1.2 Storage Media File Set ID Attributes

If present, the Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall appear either outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that sequence, but not both. If they appear outside of the sequence, then all of the SOP Instances within the sequence shall be retrievable from the specified Storage Media File-Set. If they appear within an Item of that sequence, then the SOP Instance referenced to by that Item shall be retrievable from the specified Storage Media File-Set.

##### J.3.3.1.2 Service Class Provider Behavior

If the SCP determines that it has successfully completed storage commitment for all the SOP Instances referenced by a Storage Commitment Request, the SCP shall issue an N-EVENT-REPORT with the Event Type ID set to 1 (storage commitment request successful). This event shall include references to the successfully stored SOP Instances. The SCP shall store the referenced SOP Instances in accordance with Level 2 as defined in the Storage Service Class (i.e., all Attributes, including Private Attributes). The Storage Service Class is defined in PS3.4. After the N-EVENT-REPORT has been sent, the Transaction UID is no longer active and shall not be reused for other transactions.

If it is determined that storage commitment could not be achieved for one or more referenced SOP Instances, the SCP shall issue an N-EVENT-REPORT with the Event Type ID set to 2 (storage commitment request complete - failure exists) conveying that the SCP does not commit to store all SOP Instances. This event shall include references to the failed SOP Instances together with references to those SOP Instances that have been successfully stored. For each failed SOP Instance the reason for failure shall be described by the Failure Reason Attribute. After the N-EVENT-REPORT has been sent, the Transaction UID is no longer active and shall not be reused for other transactions.

The complete set of SOP Instances referenced by the Referenced SOP Sequence (0008,1199) Attribute, in the initiating N-ACTION, shall be present in both Event Types either in the Referenced SOP Sequence (0008,1199) or in the Failed SOP Sequence (0008,1198).

The N-EVENT-REPORT shall include the same Transaction UID Attribute (0008,1195) value as contained in the initiating N-ACTION.

An SCP shall be capable of issuing the N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was performed.

### Note

1. The SCP may attempt to issue the N-EVENT-REPORT on the same Association, but this operation may fail because the SCU is free to release at any time the Association on which it sent the N-ACTION-Request. As DICOM defaults the association requestor to the SCU role, the SCP (i.e., the association requester) negotiates an SCP role using the SCU/SCP role negotiation (see PS3.7).

2. When responding on a different Association, the SCP must use the same AE Title as it used on the original Association, because the DICOM Standard defines a Service between two peer applications, each identified by an AE Title. Thus the SCP should be consistently identified for all Associations in the particular instance of the Storage Commitment Service.

3. The optional Attributes Retrieve AE Title (0008,0054), Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) within the Event Information allows an SCP to indicate the location where it has stored SOP Instances for safekeeping. For example, the SCP could relay SOP Instances to a third Application Entity using this Service Class, in which case it can use the Retrieve AE Title Attribute to indicate the real location of the data. Another example is if the SCP stores data on media, it can indicate this using the Storage Media File-Set ID and UID Attributes.

##### J.3.3.1.3 Service Class User Behavior

An SCU shall be capable of receiving an N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was performed.

### Note

To receive this N-EVENT-REPORT, the SCU accepts an association where the SCP role is proposed by the Storage Commitment SCP acting as an association requestor.

The SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the associated request. The actions taken by the SCU upon receiving the N-EVENT-REPORT are beyond the scope of this Standard but are stated in its Conformance Statement.

### Note

In the case where the SCP indicates that it cannot achieve storage commitment for some SOP Instances, the SCU might, for example, re-send the failed SOP Instances to the SCP (via the Storage Service Class) and then re-transmit the N-ACTION request. However, this behavior is beyond the scope of this Standard.

##### J.3.3.1.4 Status Codes

No Service Class specific status values are defined for the N-EVENT-REPORT Service. See PS3.7 for general response status codes.

### Note

This Section refers to status codes returned by the N-EVENT-REPORT response primitive. The Failure Reason Attribute returned in the Storage Commitment Result - Event Information (see PS3.3) are described in the Storage Commitment IOD.

Prev | Up | Next
J.3.2 Operations | Home | J.3.4 Storage Commitment Push Model SOP Class UID

DICOM PS3.4 2017b - Service Class Specifications