Материал: part02

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

DICOM PS3.2 2020a - Conformance​

Page 251​

For multi-frame image SOP Instances sent using JPEG compression Transfer Syntax, sending a fully specified offset table increases​ performance,becausetheentirefiledoesnothavetobeparsedtofindtheindividualframeoffsets.However,theinclusionofanoffset​ table is not required for archiving or viewing of such SOP Instances.​

Display of information conveyed using the DICOM Curve Module is not supported. Graphic overlay data sent either embedded in the​ unused image pixel data bits or in the separate Overlay Data Element is supported for display. Region of Interest overlays are not​ yet supported.​

If an image SOP Instance specifies an aspect ratio that is not one-to-one then the image data will be automatically resized when​ displayed on the system monitor so that they are always displayed in a one-to-one aspect ratio.​

Theaveragethroughputperformancehasbeendeterminedtobebetween2and6MegaBytespersecondona100MegabitEthernet​ network. Actual performance will depend greatly on the performance of the C-STORE SCU, the number of simultaneous active Asso-​ ciations, and the underlying network performance.​

Table F.4.2-31. STORAGE-SCP AE C-STORE Response Status Return Reasons​

Service​

Further Meaning​

Error Code​

Reason​

Status​

 

 

 

 

Success​

Success​

0000​

The Composite SOP Instance was successfully received, verified, and stored​

 

 

 

in the system database.​

 

Refused​

Out of Resources​

A700​

Indicates that there was not enough disk space to store the image.​

 

 

 

Error message is output to the Service Log. The SOP Instance will not be​

 

 

 

saved.​

 

Error​

Data Set does not​

A900​

Indicates that the Data Set does not encode a valid instance of the SOP Class​

 

match SOP Class​

 

specified.ThisstatusisreturnediftheDICOMObjectstreamcanbesuccessfully​

 

 

 

parsed but does not contain values for one or more mandatory Elements of​

 

 

 

the SOP Class. The STORAGE-SCP AE does not perform a comprehensive​

 

 

 

check, as it only checks a subset of required Elements. In addition, if the SOP​

 

 

 

Class is for a type of image but the SOP Instance does not contain values​

 

 

 

necessary for its display then this status is returned.​

 

 

 

Error message is output to the Service Log. The system can be configured to​

 

 

 

temporarily save such Data Sets in order to aid problem diagnosis.​

 

Cannot understand​

C000​

IndicatesthattheSTORAGE-SCPAEcannotparsetheDataSetintoElements.​

 

 

 

Error message is output to the Service Log. The system can be configured to​

 

 

 

temporarily save such Data Sets in order to aid problem diagnosis.​

Warning​

Coercion of Data​

B000​

IndicatesthatoneormoreElementvalueswerecoerced.RefertotheAttributes​

 

Elements​

 

defined in Annex for a list of those that can be coerced. Note that return of this​

 

 

 

status is disabled by default, as some SCUs treat it as an Error code rather​

 

 

 

than a Warning.​

 

Note​

If a failure condition does occur when handling an Association then all images previously received successfully over the​ Association are maintained in the EXAMPLE-QUERY-RETRIEVE-SERVER database. No previously successfully received​ images are discarded. Even if an image is successfully received but an error occurs transmitting the C-STORE Response​ then this final image is maintained rather than discarded. If the loss of an Association is detected then the Association is​ closed.​

The Behavior of STORAGE-SCP AE during communication failure is summarized in the following table:​

- Standard -​

Error message is output to the Service Log. If some Composite SOP​ Instanceshavealreadybeensuccessfullyreceivedthentheyaremaintained​ in the database. They are not automatically discarded because of a later​ failure.​

Page 252​

DICOM PS3.2 2020a - Conformance​

Table F.4.2-32. STORAGE-SCP AE Storage Service Communication Failure Reasons​

Exception​

Reason​

TimeoutexpiryforanexpectedDICOMMessageRequest​The Association is aborted by issuing a DICOM A-ABORT.​ (DIMSE level timeout). I.e. The STORAGE-SCP AE is​

waiting for the next C-STORE Request on an open​ Association but the timer expires.​

Timeout expiry for an expected DICOM PDU or TCP/IP​The Association is aborted by issuing a DICOM A-ABORT.​

packet (Low-level timeout). I.e. The STORAGE-SCP AE​

is waiting for the next C-STORE Data Set PDU but the​ Error message is output to the Service Log. If a C-STORE Data Set has​ timer expires.​ notbeenfullyreceivedthenthedataalreadyreceivedisdiscarded.Ifsome​ Composite SOP Instances have already been successfully received over​

the Association then they are maintained in the database.​

Association aborted by the SCU or the network layers​ Error message is output to the Service Log. If some Composite SOP​ indicatecommunicationloss(i.e.,low-levelTCP/IPsocket​Instanceshavealreadybeensuccessfullyreceivedthentheyaremaintained​ closure)​ in the database. They are not automatically discarded because of a later​

failure.​

F.4.2.3.4.1.5 SOP Specific Conformance for Storage Commitment SOP Class​

The associated Activity with the Storage Commitment Push Model service is the communication by the STORAGE-SCP AE to peer​ AEsthatithascommittedtopermanentlystoreCompositeSOPInstancesthathavebeensenttoit.ItthusallowspeerAEstodetermine​ whether the EXAMPLE-QUERY-RETRIEVE-SERVER has taken responsibility for the archiving of specific SOP Instances so that​ they can be flushed from the peer AE system.​

The STORAGE-SCP AE takes the list of Composite SOP Instance UIDs specified in a Storage Commitment Push Model N-ACTION​ Request and checks if they are present in the EXAMPLE-QUERY-RETRIEVE-SERVER database. As long as the Composite SOP​ InstanceUIDsarepresentinthedatabase,theSTORAGE-SCPAEwillconsiderthoseCompositeSOPInstanceUIDstobesuccessfully​ archived.TheSTORAGE-SCPAEdoesnotrequiretheCompositeSOPInstancestoactuallybesuccessfullywrittentoarchivemedia​ in order to commit to responsibility for maintaining these SOP Instances.​

Once the STORAGE-SCP AE has checked for the existence of the specified Composite SOP Instances, it will then attempt to send​ theNotificationrequest(N-EVENT-REPORT-RQ).ThedefaultbehavioristoattempttosendthisNotificationoverthesameAssociation​ that was used by the peer AE to send the original N-ACTION Request. If the Association has already been released or Message​ transfer fails for some reason then the STORAGE-SCP AE will attempt to send the N-EVENT-REPORT-RQ over a new Association.​ The STORAGE-SCP AE will request a new Association with the peer AE that made the original N-ACTION Request. The STORAGE-​ SCP AE can be configured to always open a new Association in order to send the Notification request.​

TheSTORAGE-SCPAEwillnotcacheStorageCommitmentPushModelN-ACTIONRequeststhatspecifyCompositeSOPInstances​ that have not yet been transferred to the EXAMPLE-QUERY-RETRIEVE-SERVER. If a peer AE sends a Storage Commitment Push​ Model N-ACTION Request before the specified Composite SOP Instances are later sent over the same Association, the STORAGE-​ SCP AE will not commit to responsibility for such SOP Instances.​

The STORAGE-SCP AE does not support the optional Storage Media File-Set ID & UID attributes in the N-ACTION.​

The EXAMPLE-QUERY-RETRIEVE-SERVER never automatically deletes Composite SOP Instances from the archive. The absolute​ persistence of SOP Instances and the maximum archiving capacity for such SOP Instances is dependent on the archiving media and​ capacityusedbytheEXAMPLE-QUERY-RETRIEVE-SERVERandisdependentontheactualspecificationsofthepurchasedsystem.​ It is necessary to check the actual system specifications to determine these characteristics.​

TheSTORAGE-SCPAEwillsupportStorageCommitmentPushModelrequestsforSOPInstancesofanyoftheStorageSOPClasses​ that are also supported by the STORAGE-SCP AE:​

- Standard -​

DICOM PS3.2 2020a - Conformance​

Page 253​

Table F.4.2-33. Supported Referenced SOP Classes in Storage Commitment Push Model N-ACTION​

Requests​

Supported Referenced SOP Classes​

US Image Storage (Retired)​

US Image Storage​

US Multi-frame Storage (Retired)​

US Multi-frame Storage​

Computed Radiography Image Storage​

CT Image Storage​

MR Image Storage​

Secondary Capture Image Storage​

The STORAGE-SCP AE will return the following Status Code values in N-ACTION Responses:​

TableF.4.2-34.STORAGE-SCPAEStorageCommitmentPushModelN-ACTIONResponseStatusReturn​

Behavior​

Service Status​ Further Meaning​

Error Code​

Behavior​

Success​

Success​

0000​

The SCP has successfully received the Storage Commitment Push​

 

 

 

Model N-ACTION Request and can process the commitment request​

 

 

 

for the indicated SOP Instances.​

Error​

Processing Failure​

0110​

IndicatesthattheStorageCommitmentPushModelN-ACTIONRequest​

 

 

 

cannotbeparsedorfullyprocessedduetoadatabaseorsystemfailure.​

Error​

Missing Attribute​

0120​

IndicatesthattheStorageCommitmentPushModelN-ACTIONRequest​

 

 

 

cannot be processed because a required attribute is missing from the​

 

 

 

N-ACTION Request Data Set.​

Error​

Missing Attribute Value​0121​

IndicatesthattheStorageCommitmentPushModelN-ACTIONRequest​

 

 

 

cannot be processed because a Type 1 attribute in the N-ACTION​

 

 

 

Request Data Set does not specify a value.​

The STORAGE-SCP AE will exhibit the following Behavior according to the Status Code value returned in an N-EVENT-REPORT​ Response from a destination Storage Commitment Push Model SCU:​

Table F.4.2-35. STORAGE-SCP AE N-EVENT-REPORT Response Status Handling Behavior​

Service Status​ Further Meaning​

Error Code​

Behavior​

Success​

Success​

0000​

The SCU has successfully received the Storage Commitment Push​

 

 

 

Model N-EVENT-REPORT Request.​

 

 

 

Success indication message is output to the Service Logs.​

 

 

 

No message is posted to the User Interface.​

Warning​

Attribute List Error​ 0107​

TransmissionofStorageCommitmentPushModelN-EVENT-REPORT​

 

 

 

Request is considered successful.​

 

 

 

Warning indication message is output to the Service Logs.​

 

 

 

No message is posted to the User Interface.​

*​

*​

Any other status​

This is treated as a permanent Failure.​

 

 

code.​

Error indication message is output to the Service Logs.​

 

 

 

No message is posted to the User Interface.​

- Standard -​

Timeout expiry for an expected DICOM​ The Association is aborted by issuing a DICOM A-ABORT.​
Message Request (DIMSE level timeout). I.e.​
If some Composite SOP Instances have been successfully received over the same​ TheSTORAGE-SCP AEis waitingforthe next​
N-ACTION Request on an open Association​Association via the Storage Service then they are maintained in the database. They​ but the timer expires.​ are not automatically discarded because of a later Storage Commitment messaging​
failure.​
Any previously received Storage Commitment Push Model N-ACTION Requests will​ still be fully processed.​
Error indication message is output to the Service Logs.​
No message is posted to the User Interface.​
Timeout expiry for an expected DICOM​ The Association is aborted by issuing a DICOM A-ABORT.​
MessageResponse(DIMSEleveltimeout).I.e.​
If some Composite SOP Instances have been successfully received over the same​ TheSTORAGE-SCP AEis waitingforthe next​
N-EVENT-REPORT Response on an open​ Association via the Storage Service then they are maintained in the database. They​ Association but the timer expires.​ are not automatically discarded because of a later Storage Commitment messaging​
failure.​
Any previously received Storage Commitment Push Model N-ACTION Requests will​ still be fully processed.​
Error indication message is output to the Service Logs.​
No message is posted to the User Interface.​
Timeout expiry for an expected DICOM PDU​The Association is aborted by issuing a DICOM A-ABORT.​
or TCP/IP packet (Low-level timeout).​
If some Composite SOP Instances have been successfully received over the same​ Association via the Storage Service then they are maintained in the database. They​ are not automatically discarded because of a later Storage Commitment messaging​ failure.​
Any previously received Storage Commitment Push Model N-ACTION Requests will​ still be fully processed.​
Error indication message is output to the Service Logs.​
No message is posted to the User Interface.​
Association A-ABORTed by the SCU or the​ The TCP/IP socket is closed.​
network layers indicate communication loss​
(i.e., low-level TCP/IP socket closure)​ If some Composite SOP Instances have been successfully received over the same​ Association via the Storage Service then they are maintained in the database. They​
are not automatically discarded because of a later Storage Commitment messaging​ failure.​
Any previously received Storage Commitment Push Model N-ACTION Requests will​ still be fully processed.​
Error indication message is output to the Service Logs.​ No message is posted to the User Interface.​
- Standard -​
Behavior​
Exception​
All Status Codes indicating an error or refusal are treated as a permanent failure. The STORAGE-SCP AE can be configured to​ automatically reattempt the sending of Storage Commitment Push Model N-EVENT-REPORT Requests if an error Status Code is​ returned or a communication failure occurs. The maximum number of times to attempt sending as well as the time to wait between​ attempts is configurable.​
Table F.4.2-36. STORAGE-SCP AE Storage Commitment Push Model Communication Failure Behavior​
DICOM PS3.2 2020a - Conformance​
Page 254​

DICOM PS3.2 2020a - Conformance​

Page 255​

F.4.3 Network Interfaces​

F.4.3.1 Physical Network Interface​

The EXAMPLE-QUERY-RETRIEVE-SERVER supports a single network interface. One of the following physical network interfaces​ will be available depending on installed hardware options:​

Table F.4.3-1. Supported Physical Network Interfaces​

Ethernet 100baseT​

Ethernet 10baseT​

F.4.3.2 Additional Protocols​

EXAMPLE-QUERY-RETRIEVE-SERVER conforms to the System Management Profiles listed in Table F.4.3-2. All requested trans-​ actions for the listed profiles and actors are supported. It does not support any optional transactions.​

Table F.4.3-2. Supported System Management Profiles​

Profile Name​

Actor​

Protocols Used​

Optional Transactions​ Security Support​

Network Address​

DHCP Client​

DHCP​

N/A​

Management​

DNS Client​

DNS​

N/A​

 

F.4.3.2.1 DHCP​

DHCP can be used to obtain TCP/IP network configuration information. The network parameters obtainable via DHCP are shown in​ Table F.4.3-3. The Default Value column of the table shows the default used if the DHCP server does not provide a value. Values for​ network parameters set in the Service/Installation tool take precedence over values obtained from the DHCP server. Support for​ DHCP can be configured via the Service/Installation Tool. The Service/Installation tool can be used to configure the machine name.​ If DHCP is not in use, TCP/IP network configuration information can be manually configured via the Service/Installation Tool.​

 

Table F.4.3-3. Supported DHCP Parameters​

DHCP Parameter​

Default Value​

IP Address​

None​

Hostname​

Requested machine name​

List of NTP servers​

Empty list​

List of DNS servers​

Empty list​

Routers​

Empty list​

Static routes​

None​

Domain name​

None​

Subnet mask​

Derived from IP Address (see service manual)​

Broadcast address​

Derived from IP Address (see service manual)​

Default router​

None​

Time offset​

Site configurable (from Time zone)​

MTU​

Network Hardware Dependent​

Auto-IP permission​

No permission​

If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted.​

- Standard -​