13.4 Request Transaction

13.4 Request Transaction (Current)
Prev	13 Storage Commitment Service and Resources	Next

This transaction allows a user agent to request an origin server to commit to the safekeeping of a set of Instances.

13.4.1 Request

The request shall have the following syntax:

POST SP /commitment-requests/{transactionUID} SP version CRLF

Accept: 1#media-type CRLF

*(header-field CRLF)

CRLF

payload

13.4.1.1 Target Resource

The Target Resource of this transaction is an individual commitment request identified by its Transaction UID.

In DIMSE, results may return asynchronously and the SCU uses the Transaction UID attribute returned by the SCP in the result to match it to the corresponding request. In DICOMweb, each request, which contains the Transaction UID in the resource path, is synchronously paired with the response, so the Transaction UID is not encoded in the response.

13.4.1.2 Query Parameters

The request has no Query Parameters.

13.4.1.3 Request Header Fields

The origin server shall support Request Header Fields as required in Table 13.4.1-2.

The user agent shall supply Request Header Fields as required in Table 13.4.1-2.

Table 13.4.1-2. Request Header Fields

Name	Values	Usage		Description
Name	Values	User Agent	Origin Server	Description
Accept	media-type	M	M	The Acceptable Media Types of the response payload.

13.4.1.4 Request Payload

The request payload shall be present and shall contain one representation consistent with the Content-Type Header Field. The representation shall conform to Media Types described in Section 8.7.3 DICOM Media Type Sets. The payload shall conform to Section 8.6 Payloads.

The request payload shall contain the Referenced SOP Instance UIDs for which the user agent requests the origin server to commit storage.

A request payload shall contain a Storage Commitment Request Module. See Section J.1.

Prev	Up	Next
13.3 Transactions Overview	Home	13.4.2 Behavior