DICOM PS3.8 2019b - Network Communication Support for Message Exchange

9.3.8 A-ABORT PDU Structure

An A-ABORT PDU shall be made of a sequence of mandatory fields. Table 9-26 shows the sequence of the fields.

The A-ABORT PDU shall support both the A-ABORT Service (user initiated) and the A-P-ABORT Service (provider initiated).

Table 9-26. A-ABORT PDU Fields

PDU bytes

Field name

Description of field

1

PDU-type

07H

2

Reserved

This reserved field shall be sent with a value 00H but not tested to this value when received.

3-6

PDU-length

This PDU-length shall be the number of bytes from the first byte of the following field to the last byte of the Reserved field. In the case of this PDU, it shall have the fixed value of 00000004H encoded as an unsigned binary number.

7

Reserved

This reserved field shall be sent with a value 00H but not tested to this value when received.

8

Reserved

This reserved field shall be sent with a value 00H but not tested to this value when received.

9

Source

This Source field shall contain an integer value encoded as an unsigned binary number. One of the following values shall be used:

0 - DICOM UL service-user (initiated abort)

1 - reserved

2 - DICOM UL service-provider (initiated abort)

10

Reason/Diag.,

This field shall contain an integer value encoded as an unsigned binary number. If the Source field has the value (2) "DICOM UL service-provider", it shall take one of the following:

0 - reason-not-specified1 - unrecognized-PDU

2 - unexpected-PDU

3 - reserved

4 - unrecognized-PDU parameter

5 - unexpected-PDU parameter

6 - invalid-PDU-parameter value

If the Source field has the value (0) "DICOM UL service-user", this reason field shall not be significant. It shall be sent with a value 00H but not tested to this value when received.

Note

The reserved fields are used to preserve symmetry with OSI ACSE/Presentation Services and Protocol.


DICOM PS3.8 2019b - Network Communication Support for Message Exchange