9.3.4 A-ASSOCIATE-RJ PDU STRUCTURE

An A-ASSOCIATE-RJ PDU shall be made of a sequence of mandatory fields. Table 9-21 shows the sequence of the mandatory fields.

Table 9-21 ASSOCIATE-RJ PDU FIELDS

PDU bytes Field name Description of field
1 PDU-type 03H
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 Reason/Diag. 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 Result This Result field shall contain an integer value encoded as an unsigned binary number. One of the following values shall be used: 1 - rejected-permanent 2 - rejected-transient
9 Source This Source field shall contain an integer value encoded as an unsigned binary number. One of the following values shall be used: 1 - DICOM UL service-user 2 - DICOM UL service-provider (ACSE related function) 3 - DICOM UL service-provider (Presentation related function)
10 Reason/Diag. This field shall contain an integer value encoded as an unsigned binary number. If the Source field has the value (1) “DICOM UL service-user”, it shall take one of the following: 1 - no-reason-given 2 - application-context-name-not-supported 3 - calling-AE-title-not-recognized 4-6 - reserved 7 - called-AE-title-not-recognized 8-10 - reserved If the Source field has the value (2) “DICOM UL service provided (ACSE related function),” it shall take one of the following: 1 - no-reason-given 2 - protocol-version-not-supported If the Source field has the value (3) “DICOM UL service provided (Presentation related function),” it shall take one of the following: 0 - reserved 1 - temporary-congestion 2 - local-limit-exceeded 3-7 - reserved Note: The reserved fields are used to preserve symmetry with OSI ACSE/Presentation Services and Protocols.