Материал: part08
Page 46 |
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
b.Each byte within the PDU shall consist of eight bits that, when represented, are numbered 7 to 0, where bit 0 is the low order bit. c.When consecutive bytes are used to represent a string of characters, the lowest byte numbers represent the first character. d.When consecutive bytes are used to represent a binary number, the lower byte number has the most significant value. e.The lowest byte number is placed first in the transport service data flow.
f. An overview of the PDUs is shown in Figure 9-1 and Figure 9-2. The detailed structure of each PDU is specified in the following sections.
Note
A number of parameters defined in the UL Service are not reflected in these PDUs (e.g., service parameters, fixed values, values not used by DICOM Application Entities.)
A-ASSOCIATE-RQ PDU/A-ASSOCIATE-AC PDU
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PDU |
|
|
PDU |
Protocol |
|
Called |
|
Calling |
|
|
(Variable Field) |
|
|
|
|
|
|
|
Entity |
|
Entity |
|
|
Contains one or more |
|
|
|
|||
|
Type |
|
|
Length |
Version |
|
|
|
|
|
|
|
|||
|
|
|
|
Title |
|
Title |
|
|
Items shown below |
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
1 |
|
1 |
4 |
2 |
2 |
16 |
16 |
|
32 |
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Application |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Item |
|
Item |
|
|
|
|
|
|
|
|
|
|
||
|
Context |
|
|
|
Application Context Name |
|
(only one) |
|
|
||||||
|
|
Type |
|
Length |
|
|
|
|
|||||||
|
Item |
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
1 |
2 |
|
|
<= 64 |
|
|
|
|
|
|
|
|
Presentation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Item |
|
Item |
Pres. |
|
|
Result/ |
|
(Variable Field) |
|
|
|||||
|
Context |
|
|
|
Reason |
|
Contains one or more |
(one or more) |
|||||||
|
Type |
|
Length |
Context ID |
|
|
|
||||||||
|
Item |
|
|
|
(used for AC) |
|
Items shown below |
|
|
||||||
|
|
|
|
|
|
|
|
|
|
||||||
|
|
|
1 |
1 |
2 |
1 |
1 |
1 |
|
1 |
|
|
|
|
|
Abstract |
Item |
|
Item |
|
Syntax |
|
Abstract Syntax |
||
Type |
|
Length |
||
IItem |
|
|
||
|
|
|
|
|
|
1 |
1 |
2 |
<= 64 |
Transfer |
|
|
|
|
Item |
|
Item |
Transfer Syntax |
|
Syntx |
|
|||
Type |
|
Length |
||
Item |
|
|
||
|
|
|
|
|
|
1 |
1 |
2 |
<= 64 |
(only one in RQ) (not present in AC)
(one or more in RQ) (only one in AC)
User |
Item |
|
|
|
Item |
|
|
|
(Variable Field) |
|
|
Info |
|
|
|
|
|
Contains one or more |
(only one) |
||||
Type |
|
|
Length |
|
|
||||||
Item |
|
|
|
|
Items shown below |
|
|
||||
|
|
|
|
|
|
|
|
|
|||
|
1 |
|
1 |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Maximum |
|
|
|
|
|
|
|
|
|
|
|
Item |
|
|
|
Item |
|
Max. Length |
|
|
||
|
Length |
|
|
|
|
|
(only one) |
||||
|
Type |
|
|
|
Length |
|
Received |
|
|||
|
Item |
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
||
|
|
|
1 |
1 |
2 |
4 |
|
|
|||
Note: All field sizes in bytes
Figure 9-1. Protocol Data Units Structure and Encoding
- Standard -
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
Page 47 |
||||||||||
|
A-ASSOCIATE-RJ PDU/A-RELEASE-RQ PDU/A-RELEASE-RP PDU/A-ABORT PDU |
|
|||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PDU |
|
PDU |
|
Result * |
Source * |
Reason/ |
|
|
|
|
|
Type |
|
Length |
|
Diag * |
|
|
|
||
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
1 |
4 |
1 |
1 |
1 |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Note: Depending on the specific PDU this field may be used or reserved.
P-DATA-TF PDU
|
|
|
|
|
|
|
|
|
|
PDU |
|
PDU |
|
(Variable Field) |
|
|
|
|
|
|
Contains one or more |
|
|
|
||
|
Type |
|
Length |
|
|
|
|
|
|
|
Presentation Data Value Items shown below |
|
|
|
|||
|
|
|
|
|
|
|
||
|
1 |
1 |
4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Item |
Pres. |
Presentation-data-Values (PDV) |
|
|
|
|
|
|
DICOM message |
|
|
|||
|
|
|
Length |
Context ID |
|
|
||
|
|
|
Command or Data Set Information |
|
|
|||
|
|
|
|
|
|
|
||
|
|
|
4 |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: All field sizes in bytes
Figure 9-2. Protocol Data Units Structure and Encoding
9.3.2 A-ASSOCIATE-RQ PDU Structure
An A-ASSOCIATE-RQ PDU shall be made of a sequence of mandatory fields followed by a variable length field. Table 9-11 shows the sequence of the mandatory fields.
The variable field shall consist of one Application Context Item, one or more Presentation Context Items, and one User Information Item. Sub-Items shall exist for the Presentation Context and User Information Items.
|
|
Table 9-11. ASSOCIATE-RQ PDU Fields |
PDU bytes |
Field name |
Description of field |
1 |
PDU-type |
01H |
2 |
Reserved |
Thisreservedfieldshallbesentwithavalue00Hbutnottestedtothisvaluewhenreceived. |
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 variable field. It shall be encoded as an unsigned binary number |
7-8 |
Protocol-version |
This two byte field shall use one bit to identify each version of the DICOM UL protocol |
|
|
supported by the calling end-system. This is Version 1 and shall be identified with bit 0 |
|
|
set. A receiver of this PDU implementing only this version of the DICOM UL protocol shall |
|
|
only test that bit 0 is set. |
9-10 |
Reserved |
This reserved field shall be sent with a value 0000H but not tested to this value when |
|
|
received. |
11-26 |
Called-AE-title |
Destination DICOM Application Name. It shall be encoded as 16 characters as defined |
|
|
by the ISO 646:1990-Basic G0 Set with leading and trailing spaces (20H) being |
|
|
non-significant. The value made of 16 spaces (20H) meaning "no Application Name |
|
|
specified" shall not be used. For a complete description of the use of this field, see |
|
|
Section 7.1.1.4. |
27-42 |
Calling-AE-title |
Source DICOM Application Name. It shall be encoded as 16 characters as defined by the |
|
|
ISO 646:1990-Basic G0 Set with leading and trailing spaces (20H) being non-significant. |
|
|
The value made of 16 spaces (20H) meaning "no Application Name specified" shall not |
|
|
be used. For a complete description of the use of this field, see Section 7.1.1.3. |
43-74 |
Reserved |
This reserved field shall be sent with a value 00H for all bytes but not tested to this value |
|
|
when received |
75-xxx |
Variable items |
This variable field shall contain the following items: one Application Context Item, one or |
|
|
morePresentationContextItemsandoneUserInformationItem.Foracompletedescription |
|
|
of the use of these items see Section 7.1.1.2, Section 7.1.1.13, and Section 7.1.1.6. |
- Standard -
Page 48 |
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
9.3.2.1 Application Context Item Structure
An Application Context Item shall be made of a sequence of mandatory fields followed by a variable length field. Table 9-12 shows the sequence of the mandatory fields.
Table 9-12. Application Context Item Fields
Item bytes |
Field name |
Description of field |
1 |
Item-type |
10H |
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 Application-context-name field. It shall be encoded as an |
|
|
unsigned binary number. |
5-xxx |
Application-context-name |
A valid Application-context-name shall be encoded as defined in Annex F. For a |
|
|
description of the use of this field see Section 7.1.1.2. Application-context-names |
|
|
are structured as UIDs as defined in PS3.5 (see Annex A for an overview of this |
|
|
concept). DICOM Application-context-names are registered in PS3.7. |
9.3.2.2 Presentation Context Item Structure
The Presentation Context Item shall be made of a sequence of mandatory fixed length fields followed by a variable field. Table 9-13 shows the sequence of the mandatory fields.
The variable field shall consist of one Abstract Syntax Sub-Item followed by one or more Transfer Syntax Sub-Items.
Table 9-13. Presentation Context Item Fields
Item bytes |
Field name |
Description of field |
1 |
Item-type |
20H |
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 last Transfer Syntax 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 |
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-xxx |
Abstract/Transfer Syntax |
This variable field shall contain the following sub-items: one Abstract Syntax and |
|
Sub-Items |
oneormoreTransferSyntax(es).Foracompletedescriptionoftheuseandencoding |
|
|
of these sub-items see Section 9.3.2.2.1 and Section 9.3.2.2.2. |
9.3.2.2.1 Abstract Syntax Sub-Item Structure
The Abstract Syntax Sub-Item shall be made of a sequence of mandatory fixed length fields followed by a variable field. Table 9-14 shows the sequence of the mandatory fields.
- Standard -
|
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
Page 49 |
|
|
Table 9-14. Abstract Syntax Sub-Item Fields |
|
|
Item bytes |
Field name |
Description of field |
|
1 |
Item-type |
30H |
|
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 Abstract-syntax-name field. It shall be encoded as an unsigned |
|
|
|
binary number. |
|
5-xxx |
Abstract-syntax-name |
This variable field shall contain the Abstract-syntax-name related to the proposed |
|
|
|
presentation context. A valid Abstract-syntax-name shall be encoded as defined in |
|
|
|
Annex F. For a description of the use of this field see Section 7.1.1.13. |
|
Abstract-syntax-names are structured as UIDs as defined in PS3.5 (see Annex B for an overview of this concept). DICOM Abstract-syntax-names are registered in PS3.4.
9.3.2.2.2 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-15 shows the sequence of the mandatory fields.
Table 9-15. 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 |
|
|
tothelastbyteoftheTransfer-syntax-namefield(s).Itshallbeencodedasanunsigned |
|
|
binary numbers |
5-xxx |
Transfer-syntax-name(s) 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.13. 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.
9.3.2.3 User Information Item Structure
The User Information Item shall be made of a sequence of mandatory fixed length fields followed by a variable field. Table 9-16 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-16. 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. |
- Standard -
Page 50 |
DICOM PS3.8 2020a - Network Communication Support for Message Exchange |
|
Item bytes |
Field name |
Description of field |
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 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.3 A-ASSOCIATE-AC PDU Structure
An A-ASSOCIATE-AC PDU shall be made of a sequence of mandatory fields followed by a variable length field. Table 9-17 shows the sequence of the mandatory fields.
The variable field consist of one Application Context Item, one or more Presentation Context Items, and one User Information Item. Sub-Items shall exist for the Presentation Context and User Information Items.
|
|
Table 9-17. ASSOCIATE-AC PDU Fields |
PDU bytes |
Field name |
Description of field |
1 |
PDU-type |
02H |
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 variable field. It shall be encoded as an unsigned binary number. |
7-8 |
Protocol-version |
This two byte field shall use one bit to identify each version of the DICOM UL protocol |
|
|
supported by the calling end-system. This is Version 1 and shall be identified with bit 0 |
|
|
set. A receiver of this PDU implementing only this version of the DICOM UL protocol |
|
|
shall only test that bit 0 is set. |
9-10 |
Reserved |
This reserved field shall be sent with a value 0000H but not tested to this value when |
|
|
received. |
11-26 |
Reserved |
This reserved field shall be sent with a value identical to the value received in the same |
|
|
field of the A-ASSOCIATE-RQ PDU, but its value shall not be tested when received. |
27-42 |
Reserved |
This reserved field shall be sent with a value identical to the value received in the same |
|
|
field of the A-ASSOCIATE-RQ PDU, but its value shall not be tested when received. |
43-74 |
Reserved |
This reserved field shall be sent with a value identical to the value received in the same |
|
|
field of the A-ASSOCIATE-RQ PDU, but its value shall not be tested when received. |
75-xxx |
Variable items |
This variable field shall contain the following items: one Application Context Item, one |
|
|
or more Presentation Context Item(s) and one User Information Item. For a complete |
|
|
description of these items see Section 7.1.1.2, Section 7.1.1.14, and Section 7.1.1.6. |
9.3.3.1 Application Context Item Structure
An Application Context Item shall be made of a sequence of mandatory fields followed by a variable length field. Table 9-12 shows the sequence of mandatory fields.
9.3.3.2 Presentation Context Item Structure
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.
- Standard -