Материал: part07

Note​

The list of Attributes allowed and the rules that define the usage of the Identifier are specified in PS3.4.​

9.3.3.3 C-CANCEL-GET-RQ​

The C-CANCEL-GET-RQ Message contains fields as defined in Table 9.3-8. Each field shall conform to DICOM encoding and Value​ Representation as defined in PS3.5. Fields are required as specified in the C-GET service definition unless otherwise noted in​ Table 9.3-8. Fields not specified in the C-GET service definition but present in Table 9.3-8 are required by the DIMSE-C protocol.​

Table 9.3-8. C-CANCEL-GET-RQ Message Fields​

9.3.3.4 C-GET Protocol Procedures​

The C-GET procedures are initiated by the invoking DIMSE Service User issuing a C-GET request primitive. On receipt of the C-GET​ request primitive the DIMSE-C protocol machine shall:​

•​construct a Message conveying the C-GET-RQ​

•​send the Message using the P-DATA request service (see 8.1).​

On receipt of a Message conveying a C-GET-RQ the DIMSE-C protocol machine shall issue a C-GET indication primitive to the per-​ forming DIMSE Service User.​

The DIMSE-C protocol machine shall:​

•​accept zero or more C-GET response primitives containing the status of Pending, issued by the performing DIMSE Service User,​ followed by a single C-GET response primitive containing the final status​

•​for each C-GET response primitive containing the Pending status the DIMSE-C protocol machine shall:​

a.​construct a Message conveying the (Pending) C-GET-RSP​

b.​send the Message using the P-DATA request service (see 8.1)​

- Standard -​

•​for the C-GET response primitive containing the final status the DIMSE-C protocol machine shall:​

a.​construct a Message conveying the (final) C-GET-RSP​

b.​send the Message using the P-DATA request service (see 8.1)​

Note​

The C-GET indication primitive initiates a sub-operation identical to the C-STORE operation. However, for the C-STORE​ sub-operation the DIMSE Service Users switch their invoking and performing roles (i.e., the invoking DIMSE Service User​ becomes the performing DIMSE Service User, etc.).​

On receipt of a Message conveying a C-GET-RSP the DIMSE-C protocol machine shall:​

•​if the Message indicates the status of Pending, issue a C-GET confirmation primitive to the invoking DIMSE Service User with a​ Pending status​

•​if the Message indicates a final status, issue a C-GET confirmation primitive to the invoking DIMSE Service User with a final status,​ thus completing the C-GET procedure​

Note​

The C-GET procedures can be canceled at any time by the invoking DIMSE Service User. This is accomplished by the in-​ voking DIMSE Service User issuing a C-CANCEL request primitive.​

The performing DIMSE Service User may return a C-GET-RSP with the status of Failed or Refused before the complete C-GET-RQ​ request Message has been completely transmitted by the invoking DIMSE Service User (this is called an early failed response). Upon​ receipt of this Failed or Refused C-GET-RSP the invoking DIMSE Service User may terminate the Message before it is completely​ sent (i.e., set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke another operation​ or notification. It is a protocol violation for an invoking DIMSE Service User to set the Last Fragment bit to 1 before a C-GET-RQ​ Message has been completely transmitted if it has not received a Failed or Refused C-GET-RSP to that request.​

Note​

When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE Service User to transmit​ several Messages before a response. Therefore, while sending a Message it may receive a response to a previously trans-​ mitted Message. In this case this response is not an early failed response because the related Message has already been​ sent.​

9.3.4 C-MOVE Protocol​

The information necessary for the C-MOVE request and indication DIMSE-C primitives are conveyed in the C-MOVE-RQ Message.​ The information necessary for the C-MOVE response and confirmation DIMSE-C primitives are conveyed in the C-MOVE-RSP​ Message.TheinformationnecessaryfortheC-MOVECancelrequestandCancelindicationprimitivesareconveyedintheC-CANCEL-​ MOVE-RQ Message.​

9.3.4.1 C-MOVE-RQ​

The C-MOVE-RQ Message contains fields as defined in Table 9.3-9. Each field shall conform to DICOM encoding and Value Repres-​ entation as defined in PS3.5. Fields are required as specified in the C-MOVE service definition unless otherwise noted in Table 9.3-​ 9. Fields not specified in the C-GET-MOVE service definition but present in Table 9.3-9 are required by the DIMSE-C protocol.​

Table 9.3-9. C-MOVE-RQ Message Fields​

- Standard -​

Note​

Implementations that require compatibility to previous versions of this Standard must set the Command Data Set Type​ (0000,0800) Field to 0102H (Identifier).​

9.3.4.2 C-MOVE-RSP​

The C-MOVE-RSP Message contains fields as defined in Table 9.3-10 and in Annex C. Each field shall conform to DICOM encoding​ and Value Representation as defined in PS3.5. Fields are required as specified in the C-MOVE service definition unless otherwise​ noted in Table 9.3-10. Fields not specified in the C-MOVE service definition but present in Table 9.3-10 are required by the DIMSE-​ C protocol.​

Table 9.3-10. C-MOVE-RSP Message Fields​

- Standard -​

9.3.4.3 C-CANCEL-MOVE-RQ​

The C-CANCEL-MOVE-RQ Message contains fields as defined in Table 9.3-11. Each field shall conform to DICOM encoding and​ Value Representation as defined in PS3.5. Fields are required as specified in the C-MOVE service definition unless otherwise noted​ inTable9.3-11.FieldsnotspecifiedintheC-MOVEservicedefinitionbutpresentinTable9.3-11arerequiredbytheDIMSE-Cprotocol.​

Table 9.3-11. C-CANCEL-MOVE-RQ Message Fields​

9.3.4.4 C-MOVE Protocol Procedures​

The C-MOVE procedures are initiated by the invoking DIMSE Service User issuing a C-MOVE request primitive. On receipt of the C-​ MOVE request primitive the DIMSE-C protocol machine shall:​

•​construct a Message conveying the C-MOVE-RQ​

•​send the Message using the P-DATA request service (see 8.1)​

On receipt of a Message conveying a C-MOVE-RQ the DIMSE-C protocol machine shall issue a C-MOVE indication primitive to the​ performing DIMSE Service User.​

The DIMSE-C protocol machine shall:​

•​accept zero or more C-MOVE response primitives containing the status of Pending, issued by the performing DIMSE Service User,​ followed by a single C-MOVE response primitive containing the final status​

•​for each C-MOVE response primitive containing the Pending status the DIMSE-C protocol machine shall:​

a.​construct a Message conveying the (Pending) C-MOVE-RSP​

b.​send the Message using the P-DATA request service (see 8.1)​

•​for the C-MOVE response primitive containing the final status the DIMSE-C protocol machine shall:​

a.​construct a Message conveying the (final) C-MOVE-RSP​

- Standard -​

b.​send the Message using the P-DATA request service (see 8.1)​

Note​

The C-MOVE indication primitive initiates a sub-operation identical to the C-STORE operation.​

On receipt of a Message conveying a C-MOVE-RSP the DIMSE-C protocol machine shall:​

•​if the Message indicates the status of Pending, issue a C-MOVE confirmation primitive to the invoking DIMSE Service User with a​ Pending status;​

•​if the Message indicates a final status, issue a C-MOVE confirmation primitive to the invoking DIMSE Service User with a final​ status, thus completing the C-MOVE procedure​

Note​

The C-MOVE procedures can be canceled at any time by the invoking DIMSE Service User. This shall be accomplished by​ the invoking DIMSE Service User issuing a C-CANCEL request primitive.​

The performing DIMSE Service User may return a C-MOVE-RSP with the status of Failed or Refused before the complete C-MOVE-​ RQ request Message has been completely transmitted by the invoking DIMSE Service User (this is called an early failed response).​ Upon receipt of this Failed or Refused C-MOVE-RSP the invoking DIMSE Service User may terminate the Message before it is​ completely sent (i.e., set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke an-​ other operation or notification. It is a protocol violation for an invoking DIMSE Service User to set the Last Fragment bit to 1 before a​ C-MOVE-RQ Message has been completely transmitted if it has not received a Failed or Refused C-MOVE-RSP to that request.​

Note​

When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE Service User to transmit​ several Messages before a response. Therefore, while sending a Message it may receive a response to a previously trans-​ mitted Message. In this case this response is not an early failed response because the related Message has already been​ sent.​

9.3.5 C-ECHO Protocol​

The information necessary for the C-ECHO request and indication DIMSE-C primitives are conveyed in the C-ECHO-RQ Message.​ TheinformationnecessaryfortheC-ECHOresponseandconfirmationDIMSE-CprimitivesareconveyedintheC-ECHO-RSPMessage.​

9.3.5.1 C-ECHO-RQ​

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

Table 9.3-12. C-ECHO-RQ Message Fields​

- Standard -​