DICOM PS3.2 2020a - Conformance

F.4.2.3.2 Association Policies (Current)
Prev | F.4.2.3 STORAGE-SCP Application Entity Specification | Next

##### F.4.2.3.2 Association Policies

###### F.4.2.3.2.1 General

The STORAGE-SCP AE can both accept and propose Association Requests. The STORAGE-SCP AE will accept Association Requests for the Verification, Storage, and Storage Commitment Push Model Services. It will propose Associations only for the Storage Commitment Push Model Service.

The DICOM standard Application Context Name for DICOM is always accepted and proposed:

Table F.4.2-23. DICOM Application Context for STORAGE-SCP AE

Application Context Name | 1.2.840.10008.3.1.1.1

###### F.4.2.3.2.2 Number of Associations

The STORAGE-SCP AE can support multiple simultaneous Associations requested by peer AEs. Each time the STORAGE-SCP AE receives an Association, a child process will be spawned to process the Verification, Storage, or Storage Commitment Push Model Service requests. The maximum number of child processes, and thus the maximum number of simultaneous Associations that can be processed, is set by configuration. The default maximum number is 10 in total. This maximum number of simultaneous Associations can be either an absolute number or a maximum number for each requesting external Application Entity. The latter flexibility can be useful if communication with one external AE is unreliable and one does not wish 'hung' connections with this AE to prevent Associations with other client AEs.

The STORAGE-SCP AE initiates one Association at a time for sending Storage Commitment Push Model N-EVENT-REPORTs to peer AEs.

Table F.4.2-24. Number of Simultaneous Associations as an SCP for STORAGE-SCP AE

Maximum number of simultaneous Associations requested by peer AEs | 10 (Configurable)
Maximum number of simultaneous Associations proposed by STORAGE-SCP AE | 1

###### F.4.2.3.2.3 Asynchronous Nature

The STORAGE-SCP AE does not support asynchronous communication (multiple outstanding transactions over a single Association). The STORAGE-SCP AE does permit an SCU to send multiple Storage Commitment Push Model Requests before it has sent back any N-EVENT-REPORT Notifications. However, the STORAGE-SCP AE must send an N-ACTION Response before permitting another N-ACTION Request to be received so the DICOM communication itself is not truly asynchronous.

Table F.4.2-25. Asynchronous Nature as a SCP for STORAGE-SCP AE

Maximum number of outstanding asynchronous transactions | 1 (Not Configurable)

There is no limit on the number of outstanding Storage Commitment Push Model Requests that can be received and acknowledged before the STORAGE-SCP AE has responded with the corresponding N-EVENT-REPORT Notifications.

Table F.4.2-26. Outstanding Storage Commitment Push Model Requests for STORAGE-SCP AE

Maximum number of outstanding Storage Commitment Requests for which no N-EVENT Notification has been sent | No Maximum Limit

###### F.4.2.3.2.4 Implementation Identifying Information

The implementation information for this Application Entity is:

Table F.4.2-27. DICOM Implementation Class and Version for STORAGE-SCP AE

Implementation Class UID | 1.840.xxxxxxx.yyy.etc…
Implementation Version Name | EX_VERS_01

Note that the STORAGE-SCP AE specifies a different Implementation Class UID than that used by the other Application Entities. All EXAMPLE-QUERY-RETRIEVE-SERVER AEs use the same Implementation Version Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released independently.

Prev | Up | Next
F.4.2.3 STORAGE-SCP Application Entity Specification | Home | F.4.2.3.3 Association Initiation Policy

DICOM PS3.2 2020a - Conformance