J.3.6 Conformance Requirements

Implementations claiming Standard SOP Class Conformance to the Storage Commitment Push Model SOP Class shall be conformant as described in this Section and shall include within their Conformance Statement information as described in this Section and sub-Sections.

An implementation may claim conformance to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS 3.2.

J.3.6.1 SCU Conformance

An implementation which is conformant to this SOP Class as an SCU shall meet conformance requirements for

— the operations and actions which it invokes

— the notifications which it receives.

The mechanisms used by the SCU to transfer SOP Instances to the SCP shall be documented.

J.3.6.1.1 Operations

The SCU shall document in the SCU Operations Statement the actions and behavior which cause the SCU to generate an N-ACTION primitive (Storage Commitment Request).

The SCU shall specify the SOP Class UIDs for which it may request storage commitment.

The SCU shall specify the duration of applicability of the Transaction UID. This may be specified as a time limit or a policy which defines the end of a transaction (e.g. how long will the SCU wait for a N-EVENT-REPORT).

The SCU shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these Attributes are supported, the SCU shall also specify which Storage Media Application Profiles are supported.

The SCU Operations Statement shall be formatted as defined in PS 3.2

J.3.6.1.2 Notifications.

The SCU shall document in the SCU Notifications Statement the behavior and actions taken by the SCU upon receiving an N-EVENT-REPORT primitive (Storage Commitment Result).

The SCU shall specify the behavior and actions performed when a success status is received (i.e. if and when local SOP Instances copies are deleted).

The SCU shall specify the behavior and actions performed when a failure status is received (i.e. recovery mechanisms, etc.).

The SCU Notifications Statement shall be formatted as defined in PS 3.2

J.3.6.2 SCP Conformance.

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for

— the operations and actions which it performs

— the notifications which it generates.

J.3.6.2.1 Operations

The SCP shall document in the SCP Operations Statement the behavior and actions of the SCP upon receiving the N-ACTION primitive (Storage Commitment Request).

The SCP shall specify parameters indicating the level of storage commitment, such as:

— under what conditions the SCP would delete SOP Instances

– persistence of storage

— capacity

— volatility

— other pertinent information

The SCP shall specify the mechanisms and characteristics of retrieval of stored SOP Instances, such as:

— supported query/retrieve services

— latency

— other pertinent information

The SCP shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these Attributes are supported, the SCP shall also specify which Storage Media Application Profiles are supported.

The SCP Operations Statement shall be formatted as defined in PS 3.2

J.3.6.2.2 Notifications

The SCP shall document in the SCP Notifications Statement the behavior and actions which cause the SCP to generate an N-EVENT-REPORT primitive (Storage Commitment Result).

The SCP shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-EVENT-REPORT and describe the policies for how the Media is used. The SCP shall also specify which Storage Media Application Profiles are supported.

The SCP shall specify if it supports the optional Retrieve AE Title (0008,0054) Attribute in the N-EVENT-REPORT and describe the policies for how it is used.

The SCP Notifications Statement shall be formatted as defined in PS 3.2