[This is preliminary documentation and is subject to change.]
The Protocol Data Units (PDUs) are the message formats exchanged
between peer entities within a layer.
Declaration Syntax| C# | Visual Basic | Visual C++ |
public abstract class DulMessage : Message, IDvtDetailToXml
Public MustInherit Class DulMessage _ Inherits Message _ Implements IDvtDetailToXml
public ref class DulMessage abstract : public Message, IDvtDetailToXml
Members| All Members | Constructors | Methods | Properties | ||
| Icon | Member | Description |
|---|---|---|
 | DulMessage()()() | Initializes a new instance of the DulMessage class |
 | DvtDetailToXml(StreamWriter, Int32) |
Serialize DVT Detail Data to Xml.
|
| Equals(Object) | Determines whether the specified Object is equal to the current Object. (Inherited from Object.) |
| Finalize()()() | Allows an Object to attempt to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.) |
| GetHashCode()()() | Serves as a hash function for a particular type. GetHashCode()()() is suitable for use in hashing algorithms and data structures like a hash table. (Inherited from Object.) |
| GetType()()() | Gets the Type of the current instance. (Inherited from Object.) |
| MemberwiseClone()()() | Creates a shallow copy of the current Object. (Inherited from Object.) |
 | PduType |
Protocol Data Unit - Type Identifier.
|
| ToString()()() | Returns a String that represents the current Object. (Inherited from Object.) |
Remarks
A PDU shall consist of protocol control information and user data.
PDUs are constructed by PS 3.8-2003 Page 31 mandatory fixed fields followed by
optional variable fields which contain one or more items and/or sub-items.
Remarks
Items of unrecognized types shall be ignored and skipped.
Items shall appear in an increasing order of their item types.
Several instances of the same item shall be acceptable or shall
not as specified by each item.
Remarks
The DICOM UL protocol consists of seven Protocol Data Units:
a) A-ASSOCIATE-RQ PDU
b) A-ASSOCIATE-AC PDU
c) A-ASSOCIATE-RJ PDU
d) P-DATA-TF PDU
e) A-RELEASE-RQ PDU
f) A-RELEASE-RP PDU
g) A-ABORT PDU
a) A-ASSOCIATE-RQ PDU
b) A-ASSOCIATE-AC PDU
c) A-ASSOCIATE-RJ PDU
d) P-DATA-TF PDU
e) A-RELEASE-RQ PDU
f) A-RELEASE-RP PDU
g) A-ABORT PDU
Remarks
The encoding of the DICOM UL PDUs is defined as follows (Big Endian byte ordering):
Remarks
Note: The Big Endian byte ordering has been chosen for consistency with the
OSI and TCP/IP environment.
This pertains to the DICOM UL PDU headers only. The encoding of the PDV message fragments is
defined by the Transfer Syntax negotiated at association establishment.
Remarks
a) Each PDU type shall consist of one or more bytes that when represented, are numbered
sequentially, with byte 1 being the lowest byte number.
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 Figures 9-1 and 9-2. The detailed structure of each PDU is specified in the following sections.
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 Figures 9-1 and 9-2. The detailed structure of each PDU is specified in the following sections.
Remarks
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.)
Inheritance Hierarchy| Object | |||
 | Message | ||
| DulMessage | ||
 | A_ABORT | ||
| A_ASSOCIATE_AC | ||
| A_ASSOCIATE_RJ | ||
| A_ASSOCIATE_RQ | ||
| A_RELEASE_RP | ||
| A_RELEASE_RQ | ||
| P_DATA_TF | ||