Материал: part07

10.3.4.1 N-ACTION-RQ​

The N-ACTION-RQ Message contains fields as defined in Table 10.3-7. Each field shall conform to DICOM encoding and Value​ Representation as defined in PS3.5. Fields are required as specified in the N-ACTION service definition unless otherwise noted in​ Table10.3-7.FieldsnotspecifiedintheN-ACTIONservicedefinitionbutpresentinTable10.3-7arerequiredbytheDIMSE-Nprotocol.​

Table 10.3-7. N-ACTION-RQ Message Fields​

Note​

1.​ServiceClassSpecificationscontainedinPS3.4definethevaluesneededfortheActionTypeID(0000,1008)parameter.​

2.​Service Class Specifications contained in PS3.4 define the Data Set needed for the Action Information parameter.​

10.3.4.2 N-ACTION-RSP​

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

Table 10.3-8. N-ACTION-RSP Message Fields​

- Standard -​

Note​

1.​ServiceClassSpecificationscontainedinPS3.4definethevaluesneededfortheActionTypeID(0000,1008)parameter.​

2.​Service Class Specifications contained in PS3.4 define the Data Set needed for the Action Reply parameter related to​ each defined Action Type ID.​

3.​Service Class Specifications contained in PS3.4 define the encoding of the Action Reply parameter.​

10.3.4.3 N-ACTION Protocol Procedures​

The N-ACTION procedures are initiated by the invoking DIMSE Service User issuing an N-ACTION request primitive. On receipt of​ the N-ACTION request primitive the DIMSE-N protocol machine shall:​

•​construct a Message conveying the N-ACTION-RQ​

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

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

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

•​construct a Message conveying the N-ACTION-RSP​

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

On receipt of a Message conveying an N-ACTION-RSP the DIMSE-N protocol machine shall issue an N-ACTION confirmation prim-​ itive to the invoking DIMSE Service User, thus completing the N-ACTION procedure.​

TheperformingDIMSEServiceUsermayreturnanN-ACTION-RSPwiththestatusofFailedorRefusedbeforethecompleteN-ACTION-​ 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 N-ACTION-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​ anN-ACTION-RQMessagehasbeencompletelytransmittedifithasnotreceivedaFailedorRefusedN-ACTION-RSPtothatrequest.​

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.​

- Standard -​

10.3.5 N-CREATE Protocol​

TheinformationnecessaryfortheN-CREATErequestandindicationDIMSE-NprimitivesareconveyedintheN-CREATE-RQMessage.​ The information necessary for the N-CREATE response and confirmation DIMSE-N primitives are conveyed in the N-CREATE-RSP​ Message.​

10.3.5.1 N-CREATE-RQ​

The N-CREATE-RQ Message contains fields as defined in Table 10.3-9. Each field shall conform to DICOM encoding and Value​ Representation as defined in PS3.5. Fields are required as specified in the N-CREATE service definition unless otherwise noted in​ Table10.3-9.FieldsnotspecifiedintheN-CREATEservicedefinitionbutpresentinTable10.3-9arerequiredbytheDIMSE-Nprotocol.​

Table 10.3-9. N-CREATE-RQ Message Fields​

Note​

The permitted contents of Attribute List, encoded as a series of Data Elements, are defined in the Information Object Defin-​ ition (PS3.3) and Service Class Specifications (PS3.4).​

10.3.5.2 N-CREATE-RSP​

TheN-CREATE-RSPMessagecontainsfieldsasdefinedinTable10.3-10andAnnexC.EachfieldshallconformtoDICOMencoding​ and Value Representation as defined in PS3.5. Fields are required as specified in the N-CREATE service definition unless otherwise​ noted in Table10.3-10. Fields not specified in the N-CREATE service definition but present in Table 10.3-10 are required by the​ DIMSE-N protocol.​

Table 10.3-10. N-CREATE-RSP Message Fields​

- Standard -​

Note​

The permitted contents of Attribute List, encoded as a series of Data Elements, are defined in the Information Object Defin-​ ition (PS3.3) and Service Class Specifications (PS3.4).​

10.3.5.3 N-CREATE Protocol Procedures​

The N-CREATE procedures are initiated by the invoking DIMSE Service User issuing an N-CREATE request primitive. On receipt of​ the N-CREATE request primitive the DIMSE-N protocol machine shall:​

•​construct a Message conveying the N-CREATE-RQ​

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

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

OnreceiptoftheN-CREATEresponseprimitive,issuedbytheperformingDIMSEServiceUser,theDIMSE-Nprotocolmachineshall:​

•​construct a Message conveying the N-CREATE-RSP​

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

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

The performing DIMSE Service User may return an N-CREATE-RSP with the status of Failed or Refused before the complete N-​ CREATE-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 N-CREATE-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 an N-CREATE-RQ Message has been completely transmitted if it has not received a Failed or Refused N-CREATE-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.​

10.3.6 N-DELETE Protocol​

TheinformationnecessaryfortheN-DELETErequestandindicationDIMSE-NprimitivesareconveyedintheN-DELETE-RQMessage.​ The information necessary for the N-DELETE response and confirmation DIMSE-N primitives are conveyed in the N-DELETE-RSP​ Message.​

- Standard -​

10.3.6.1 N-DELETE-RQ​

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

Table 10.3-11. N-DELETE-RQ Message Fields​

10.3.6.2 N-DELETE-RSP​

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

Table 10.3-12. N-DELETE-RSP Message Fields​

10.3.6.3 N-DELETE Protocol Procedures​

The N-DELETE procedures are initiated by the invoking DIMSE Service User issuing an N-DELETE request primitive. On receipt of​ the N-DELETE request primitive the DIMSE-N protocol machine shall:​

•​construct a Message conveying the N-DELETE-RQ​

- Standard -​