Материал: part07

9.1.4.1.1 Message ID​

This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE​ ServiceProvidermayhaveinprogress.NotwoidenticalvaluesfortheMessageID(0000,0110)shallbeusedforoutstandingoperations​ or notifications.​

Note​

1.​Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use​ is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE Service User​ should not attach any semantic significance to this parameter.​

2.​The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug pro-​ cedures.​

9.1.4.1.2 Message ID Being Responded To​

This parameter specifies the Message ID (0000,0110) of the request/indication to which this response/confirmation applies.​

9.1.4.1.3 Affected SOP Class UID​

For the request/indication, this parameter specifies the SOP Class of the Information Model for the retrieve. It may be included in the​ response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.​

9.1.4.1.4 Priority​

This parameter specifies the priority of the C-MOVE operation. It shall be one of LOW, MEDIUM or HIGH . This priority shall also be​ the priority used for all sub-operations.​

9.1.4.1.5 Move Destination​

ThisparameterspecifiestheDICOMAETitleofthedestinationDICOMAEtowhichtheC-STOREsub-operationsarebeingperformed.​

9.1.4.1.6 Identifier​

Intherequest/indication,thisisalistofAttributestobematchedagainstthevaluesoftheAttributesofknowncompositeSOPInstances​ of the performing DIMSE Service User. The list of Attributes allowed and the rules for the construction are in PS3.4.​

Note​

TheIdentifierisspecifiedasUintheResponse/Confirmation,butServicesdefinedinPS3.4thatusethisprimitivemayimpose​ mandatory or conditional requirements on its presence.​

Intheresponse/confirmation,thisisalistofAttributesthatprovidestatusinformationabouttheC-MOVEoperation.ThelistofAttributes​ allowed and the rules that define the usage of the Identifier are specified in PS3.4.​

9.1.4.1.7 Status​

Indicates the status of the response. It may have any of the following values (see also Annex C):​

a.​Success (0000H) - This indicates that processing of the matches and all sub-operations are complete.​

b.​Pending (Status value is Service Class specific) - This indicates that procession of the matches and sub-operations is initiated​ or continuing.​

c.​Refused:Outofresources(StatusvalueisServiceClassspecific)-IndicatesthatprocessingoftheC-MOVEhasbeenterminated​ because it was out of resources. This may be the initial response to the C-MOVE or may be sent after a number of Pending​ statuses.​

d.​Refused: SOP Class not supported (0122H) - Indicates that processing of the C-MOVE has been terminated because the SOP​ Class was not supported.​

- Standard -​

e.​Refused:MoveDestinationunknown(StatusvalueisServiceClassspecific)-IndicatesthatprocessingoftheC-MOVEhasbeen​ terminated because the Move destination was unknown.​

f.​ Cancel (FE00H) - Indicates that processing of the C-MOVE has been terminated due to a C-MOVE Cancel indication primitive.​

g.​Failed (Status value is Service Class specific) - Indicates that the C-MOVE operation failed at the performing DIMSE Service​ User.​

h.​Duplicateinvocation(0210H)-IndicatesthattheMessageID(0000,0110)specifiedisallocatedtoanothernotificationoroperation.​

i.​ Mistyped argument (0212H) - Indicates that one of the parameters supplied has not been agreed for use on the Association​ between the DIMSE Service Users.​

j.​ Unrecognized operation (0211H) - Indicates that the operation is not one of those agreed between the DIMSE Service Users.​

k.​Refused: Not authorized (0124H) - Indicates that the peer DIMSE Service User was not authorized to invoke the C-MOVE oper-​ ation.​

l.​ Warning (Status value is Service Class specific) - This indicates that the peer DIMSE Service User was able to perform sub-op-​ erations but detected a probable error with one or more of them.​

9.1.4.1.8 Number of Remaining Sub-Operations​

This specifies the number of remaining C-STORE sub-operations to be invoked by this C-MOVE operation. It may be included in any​ response/confirmation and shall be included if the status is equal to Pending.​

9.1.4.1.9 Number of Completed Sub-Operations​

This specifies the number of C-STORE sub-operations invoked by this C-MOVE operation that have completed successfully. It may​ be included in any response/confirmation and shall be included if the status is equal to Pending.​

9.1.4.1.10 Number of Failed Sub-Operations​

This specifies the number of C-STORE sub-operations invoked by this C-MOVE operation that have failed. It may be included in any​ response/confirmation and shall be included if the status is equal to Pending.​

9.1.4.1.11 Number of Warning Sub-Operations​

This specifies the number of C-STORE sub-operation invoked by this C-MOVE operation that generated Warning responses. It may​ be included in any response/confirmation and shall be included if the status is equal to Pending.​

9.1.4.2 C-MOVE Service Procedures​

The following C-MOVE service procedures apply to the invoking DIMSE-service user:​

a.​The invoking DIMSE Service User requests a performing DIMSE Service User to match an Identifier against the Attributes of all​ SOPInstancesknowntotheperformingDIMSEServiceUserandgenerateaC-STOREsub-operationforeachmatch.Thisrequest​ is made by issuing a C-MOVE request primitive to the DIMSE Service Provider. If the request is rejected by the DIMSE Service​ Provider, the following procedures do not apply.​

b.​At any time before receiving a C-MOVE confirmation primitive with status unequal to Pending, the invoking DIMSE Service User​ may request the performing DIMSE Service User to cancel the service by issuing a C-MOVE cancel request primitive to the​ DIMSE Service Provider.​

c.​The invoking DIMSE Service User may receive C-MOVE confirmation primitives with status of Pending during the processing of​ the C-MOVE operation.​

d.​The invoking DIMSE Service User receives a final C-MOVE confirmation primitive.​

Note​

in the above procedures, (c) may precede (b).​

- Standard -​

The following C-MOVE service procedures apply to the performing DIMSE Service User:​

a.​When the performing DIMSE Service User receives a C-MOVE indication from the DIMSE Service Provider it matches the​ Identifier against the Attributes of known composite SOP Instances and generates a C-STORE sub-operation for each match.​

b.​At any time following the C-MOVE indication, the performing DIMSE Service User may receive a C-MOVE cancel indication.​

c.​If the C-MOVE cancel indication is received before the processing of the C-MOVE request has completed, then the C-MOVE​ operation is terminated; otherwise the following procedure does not apply.​

d.​The performing DIMSE Service User issues a C-MOVE response with a status of Canceled to the DIMSE Service Provider to​ indicate that the C-MOVE has been canceled. The following procedures do not apply.​

e.​For each matching composite SOP Instance, the C-MOVE performing DIMSE Service User initiates a C-STORE sub-operation​ on a different Association than the C-MOVE. In this sub-operation, the C-MOVE performing DIMSE Service User becomes the​ C-STOREinvokingDIMSEServiceUser.TheC-STOREperformingDIMSEServiceUsermayormaynotbetheC-MOVEinvoking​ DIMSE Service User.​

f.​ During the processing of the C-MOVE operation, the performing DIMSE Service User may issue C-MOVE response primitives​ with a status of Pending.​

g.​When the C-MOVE operation completes (either in success or in failure), the performing DIMSE Service User issues a C-MOVE​ response with the status set to either Refused, Failed, or Success to the DIMSE Service Provider.​

The following C-MOVE service procedures apply to the DIMSE Service Provider:​

a.​When the DIMSE Service Provider receives a C-MOVE request primitive from the invoking DIMSE Service User, it issues a C-​ MOVE indication primitive to the performing DIMSE Service User.​

b.​When the DIMSE Service Provider receives a C-MOVE cancel request primitive from the invoking DIMSE Service User, it issues​ a C-MOVE cancel indication to the performing DIMSE Service User.​

c.​When the DIMSE Service Provider receives a C-MOVE response primitive from the performing DIMSE Service User, it issues a​ C-MOVE confirmation primitive to the invoking DIMSE Service User.​

The performing DIMSE Service User may return a C-MOVE response primitive with the status of Failed or Refused before the entire​ C-MOVE indication (Data Set) has been completely transmitted by the invoking DIMSE Service User. A C-MOVE response primitive​ with the status of Success or Warning shall not be returned until the entire C-MOVE indication has been received by the performing​ DIMSE Service User.​

Note​

1.​Notes: Such an occurrence of a "Failed" response is often called an early failed response.​

9.1.5 C-ECHO Service​

The C-ECHO service is invoked by a DIMSE Service User to verify end-to-end communications with a peer DIMSE Service User. It​ is a confirmed service.​

9.1.5.1 C-ECHO Parameters​

Table 9.1-5. C-ECHO Parameters​

- Standard -​

9.1.5.1.1 Message ID​

This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE​ ServiceProvidermayhaveinprogress.NotwoidenticalvaluesfortheMessageID(0000,0110)shallbeusedforoutstandingoperations​ or notifications.​

Note​

1.​Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use​ is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE Service User​ should not attach any semantic significance to this parameter.​

2.​The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug pro-​ cedures.​

9.1.5.1.2 Message ID Being Responded To​

This parameter specifies the Message ID (0000,0110) of the request/indication to which this response/ confirmation applies.​

9.1.5.1.3 Affected SOP Class UID​

For the request/indication, this parameter specifies the SOP Class of the SOP Instance for the verification. It may be included in the​ response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.​

9.1.5.1.4 Status​

Indicates the status of the response. It may have any of the following values (see also Annex C):​

a.​Success (0000H)​

b.​Refused: SOP Class not supported (0122H) - Indicates that a different SOP Class than the Verification SOP Class was specified,​ which was not supported.​

c.​Duplicateinvocation(0210H)-IndicatesthattheMessageID(0000,0110)specifiedisallocatedtoanothernotificationoroperation.​

d.​Mistyped argument (0212H) - Indicates that one of the parameters supplied has not been agreed for use on the Association​ between the DIMSE Service Users.​

e.​Unrecognized operation (0211H) - Indicates that a different SOP Class than the Verification SOP Class was specified, which​ does not recognize a C-ECHO operation.​

9.1.5.2 C-ECHO Service Procedures​

The following C-ECHO procedures apply:​

a.​The invoking DIMSE Service User requests verification of communication to the performing DIMSE Service User by issuing a​ C-ECHO request primitive to the DIMSE Service Provider.​

b.​The DIMSE Service Provider issues a C-ECHO indication primitive to the performing DIMSE Service User.​

c.​The performing DIMSE Service User verifies communication by issuing a C-ECHO response primitive to the DIMSE Service​ Provider.​

d.​The DIMSE Service Provider issues a C-ECHO confirmation primitive to the invoking DIMSE Service User, completing the C-​ ECHO operation.​

9.2 Sequencing​

9.2.1 Types of Services​

All operation and notifications shall be confirmed services.​

- Standard -​

9.2.2 Usage Restrictions​

These services may only be invoked within the context of an established Association.​

9.2.3 Disrupted Procedures​

These services do not disrupt any other service procedure.​

9.2.4 Disrupting Procedures​

These services are disrupted by the A-ABORT service procedure.​

9.3 Protocol​

This section specifies the protocol necessary to perform the set of DIMSE-C operations. The Value Representations (VR) specified​ in the following tables shall be encoded as defined in PS3.5.​

9.3.1 C-STORE Protocol​

TheinformationnecessaryfortheC-STORErequestandindicationDIMSE-CprimitivesareconveyedintheC-STORE-RQMessage.​ The information necessary for the C-STORE response and confirmation DIMSE-C primitives are conveyed in the C-STORE-RSP​ Message.​

9.3.1.1 C-STORE-RQ​

The C-STORE-RQ Message contains fields as defined in Table 9.3-1. Each field shall conform to DICOM encoding and Value Rep-​ resentationasdefinedinPS3.5.FieldsarerequiredasspecifiedintheC-STOREservicedefinitionunlessotherwisenotedinTable9.3-​ 1. Fields not specified in the C-STORE service definition but present in Table 9.3-1 are required by the DIMSE-C protocol.​

Table 9.3-1. C-STORE-RQ Message Fields​

- Standard -​