DICOM PS3.8 2024d - Network Communication Support for Message Exchange |
---|
The Presentation Context Item shall be made of a sequence of mandatory fixed length fields followed by a variable field. Table 9-18 shows the sequence of the mandatory fields.
The variable field shall consist of one Transfer Syntax Sub-Item.
Table 9-18. Presentation Context Item Fields
This reserved field shall be sent with a value 00H but not tested to this value when received. |
||
This Item-length shall be the number of bytes from the first byte of the following field to the last byte of the Transfer Syntax Sub-Item. It shall be encoded as an unsigned binary number. |
||
Presentation-context-ID values shall be odd integers between 1 and 255, encoded as an unsigned binary number. For a complete description of the use of this field see Section 7.1.1.13. |
||
This reserved field shall be sent with a value 00H but not tested to this value when received. |
||
This Result/Reason field shall contain an integer value encoded as an unsigned binary number. One of the following values shall be used: 2 - no-reason (provider rejection) |
||
This reserved field shall be sent with a value 00H but not tested to this value when received. |
||
This variable field shall contain one Transfer Syntax Sub-Item. When the Result/Reason field has a value other than acceptance (0), this field shall not be significant and its value shall not be tested when received. For a complete description of the use and encoding of this item see Section 9.3.3.2.1. |
The Transfer Syntax Sub-Item shall be made of a sequence of mandatory fixed length fields followed by a variable field. Table 9-19 shows the sequence of the mandatory fields.
Table 9-19. Transfer Syntax Sub-Item Fields
This reserved field shall be sent with a value 00H but not tested to this value when received. |
||
This Item-length shall be the number of bytes from the first byte of the following field to the last byte of the Transfer-syntax-name field. It shall be encoded as an unsigned binary number. |
||
This variable field shall contain the Transfer-syntax-name proposed for this presentation context. A valid Transfer-syntax-name shall be encoded as defined in Annex F. For a description of the use of this field see Section 7.1.1.14. Transfer-syntax-names are structured as UIDs as defined in PS3.5 (see Annex B for an overview of this concept). DICOM Transfer-syntax-names are registered in PS3.5. |
DICOM PS3.8 2024d - Network Communication Support for Message Exchange |
---|