Материал: part07

Note​

The contents of Composite Information Object Definitions, encoded as a series of Data Elements, are defined in PS3.3 and​ PS3.4​

9.3.1.2 C-STORE-RSP​

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

Table 9.3-2. C-STORE-RSP Message Fields​

9.3.1.3 C-STORE Protocol Procedures​

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

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

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

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

On receipt of the C-STORE response primitive, issued by the performing DIMSE Service User, the DIMSE-C protocol machine shall:​

•​construct a Message conveying the C-STORE-RSP​

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

On receipt of a Message conveying a C-STORE-RSP the DIMSE-C protocol machine shall issue a C-STORE confirmation primitive​ to the invoking DIMSE Service User, thus completing the C-STORE procedure.​

- Standard -​

TheperformingDIMSEServiceUsermayreturnaC-STORE-RSPwiththestatusofFailedorRefusedbeforethecompleteC-STORE-​ 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-STORE-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-STORE-RQ Message has been completely transmitted if it has not received a Failed or Refused C-STORE-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.2 C-FIND Protocol​

The information necessary for the C-FIND request and indication DIMSE-C primitives are conveyed in the C-FIND-RQ Message. The​ information necessary for the C-FIND response and confirmation DIMSE-C primitives are conveyed in the C-FIND-RSP Message.​ The information necessary for the C-FIND Cancel Request and Cancel Indication primitives are conveyed in the C-CANCEL-FIND-​ RQ Message.​

9.3.2.1 C-FIND-RQ​

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

Table 9.3-3. C-FIND-RQ Message Fields​

Note​

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

- Standard -​

9.3.2.2 C-FIND-RSP​

The C-FIND-RSP Message contains fields as defined in Table 9.3-4 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-FIND service definition unless otherwise​ noted in Table 9.3-4. Fields not specified in the C-FIND service definition but present in Table 9.3-4 are required by the DIMSE-C​ protocol.​

Table 9.3-4. C-FIND-RSP Message Fields​

9.3.2.3 C-CANCEL-FIND-RQ​

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

Table 9.3-5. C-CANCEL-FIND-RQ Message Fields​

9.3.2.4 C-FIND Protocol Procedures​

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

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

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

- Standard -​

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

The DIMSE-C protocol machine shall:​

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

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

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

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

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

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

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

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

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

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

Note​

The C-FIND 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-FIND-RSP with the status of Failed or Refused before the complete C-FIND-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-FIND-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-FIND-RQ​ Message has been completely transmitted if it has not received a Failed or Refused C-FIND-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.3 C-GET Protocol​

The information necessary for the C-GET request and indication DIMSE-C primitives are conveyed in the C-GET-RQ Message. The​ information necessary for the C-GET response and confirmation DIMSE-C primitives are conveyed in the C-GET-RSP Message. The​ information necessary for the C-GET Cancel Request and Cancel Indication primitives are conveyed in the C-CANCEL-GET-RQ​ Message.​

9.3.3.1 C-GET-RQ​

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

- Standard -​

Page 60​ DICOM PS3.7 2020a - Message Exchange​

Table 9.3-6. C-GET-RQ Message Fields​

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.3.2 C-GET-RSP​

The C-GET-RSP Message contains fields as defined in Table 9.3-7 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-GET service definition unless otherwise​ noted in Table 9.3-7. Fields not specified in the C-GET service definition but present in Table 9.3-7 are required by the DIMSE-C​ protocol.​

Table 9.3-7. C-GET-RSP Message Fields​

- Standard -​