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