|
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
Page 51 |
|
|
Table 9-18. Presentation Context Item Fields |
|
|
Item bytes |
Field name |
Description of field |
|
1 |
Item-type |
21H |
|
2 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value when |
|
|
|
received. |
|
3-4 |
Item-length |
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. |
|
5 |
Presentation-context-ID |
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. |
|
6 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value when |
|
|
|
received. |
|
7 |
Result/Reason |
This Result/Reason field shall contain an integer value encoded as an unsigned binary |
|
|
|
number. One of the following values shall be used: |
|
|
|
0 - acceptance |
|
|
|
1 - user-rejection |
|
|
|
2 - no-reason (provider rejection) |
|
|
|
3 - abstract-syntax-not-supported (provider rejection) |
|
|
|
4 - transfer-syntaxes-not-supported (provider rejection) |
|
8 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value when |
|
|
|
received. |
|
9-xxx |
Transfer syntax sub-item |
ThisvariablefieldshallcontainoneTransferSyntaxSub-Item.WhentheResult/Reason |
|
|
|
fieldhasavalueotherthanacceptance(0),thisfieldshallnotbesignificantanditsvalue |
|
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.
9.3.3.2.1 Transfer Syntax Sub-Item Structure
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
Item bytes |
Field name |
Description of field |
1 |
Item-type |
40H |
2 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value when |
|
|
received. |
3-4 |
Item-length |
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. |
5-xxx |
Transfer-syntax-name |
ThisvariablefieldshallcontaintheTransfer-syntax-nameproposedforthispresentation |
|
|
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. |
- Standard -
Page 52 |
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
9.3.3.3 User Information Item Structure
The User Information Item shall be made of a sequence of mandatory length fields followed by a variable field. Table 9-20 shows the sequence of the mandatory fields.
The variable field shall consist of one or more User-Data Sub-Items.
Note
The User-Data Sub-Items may be present in any order within the User-Information Item. No significance should be placed ontheorderofUser-DataSub-ItemswithintheUserInformationItem.Sendingapplicationsshouldbeawarethatsomeolder applications might expect Sub-Items to be encoded in ascending order of Item-type within the enclosing Item.
Table 9-20. User Information Item Fields
Item bytes |
Field name |
Description of field |
1 |
Item-type |
50H |
2 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value when |
|
|
received. |
3-4 |
Item-length |
This Item-length shall be the number of bytes from the first byte of the following |
|
|
field to the last byte of the User-data-information field(s). It shall be encoded as |
|
|
an unsigned binary number. |
5-xxx |
User-data |
This variable field shall contain User-data sub-items as defined by the DICOM |
|
|
ApplicationEntity.Thestructureandcontentofthesesub-itemsisdefinedinAnnex |
|
|
D. |
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 |
|
|
|
byteoftheReason/Diag.field.InthecaseofthisPDU,itshallhavethefixedvalueof00000004H |
|
|
|
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) |
- Standard -
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
Page 53 |
|
PDU bytes Field name |
Description of field |
|
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
IftheSourcefieldhasthevalue(3)"DICOMULserviceprovided(Presentationrelatedfunction)", it shall take one of the following:
0 - reserved
1 - temporary-congestio
2 - local-limit-exceeded
3-7 - reserved
Note
ThereservedfieldsareusedtopreservesymmetrywithOSIACSE/PresentationServices
and Protocols.
9.3.5 P-DATA-TF PDU Structure
A P-DATA-TF PDU shall be made of a sequence of mandatory fixed length fields followed by a variable length field. Table 9-22 shows the sequence of the mandatory fields.
The variable data field shall contain one or more Presentation-Data-Value Items.
Table 9-22. P-DATA-TF PDU Fields
PDU bytes |
Field name |
Description of field |
1 |
PDU-type |
04H |
2 |
Reserved |
This reserved field shall be sent with a value 00H but not tested to this value |
|
|
when received. |
3-6 |
PDU-length |
ThisPDU-lengthshallbethenumberofbytesfromthefirstbyteofthefollowing |
|
|
field to the last byte of the variable field. It shall be encoded as an unsigned |
|
|
binary number. |
7-xxx |
Presentation-data-value Item(s)This variable data field shall contain one or more Presentation-data-value |
|
|
|
Items(s). For a complete description of the use of this field see Section 9.3.5.1 |
- Standard -
Page 54 |
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
9.3.5.1 Presentation Data Value Item Structure
The Presentation Data Value Item shall be made of a sequence of mandatory fixed length fields followed by one variable length field. Table 9-23 shows the sequence of the fields.
The variable field shall consist of one Presentation-Data-Value.
Table 9-23. Presentation-Data-Value Item Fields
Item bytes |
Field name |
Description of field |
1-4 |
Item-length |
This Item-length shall be the number of bytes from the first byte of the following field |
|
|
to the last byte of the Presentation-data-value field. It shall be encoded as an |
|
|
unsigned binary number. |
5 |
Presentation-context-ID |
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. |
6-xxx |
Presentation-data-value |
This Presentation-data-value field shall contain DICOM message information |
|
|
(command and/or Data Set) with a message control header. For a complete |
|
|
description of the use of this field see Annex E. |
9.3.6 A-RELEASE-RQ PDU Structure
An A-RELEASE-RQ PDU shall be made of a sequence of mandatory fields. Table 9-24 shows the sequence of the fields.
Table 9-24. A-RELEASE-RQ PDU Fields
PDU bytes |
Field name |
Description of field |
1 |
PDU-type |
05H |
2 |
Reserved |
Thisreservedfieldshallbesentwithavalue00Hbutnottestedtothisvaluewhen |
|
|
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-10 |
Reserved |
This reserved field shall be sent with a value 00000000H but not tested to this |
|
|
value when received. |
9.3.7 A-RELEASE-RP PDU Structure
An A-RELEASE-RP PDU shall be made of a sequence of mandatory fields. Table 9-25 shows the sequence of the fields.
Table 9-25. A-RELEASE-RP PDU Fields
PDU bytes |
Field name |
Description of field |
1 |
PDU-type |
06H |
2 |
Reserved |
Thisreservedfieldshallbesentwithavalue00Hbutnottestedtothisvaluewhen |
|
|
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-10 |
Reserved |
This reserved field shall be sent with a value 00000000H but not tested to this |
|
|
value when received. |
- Standard -
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
Page 55 |
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.
- Standard -