The DICOM Communication Protocol outlines the requirements for transferring DICOM data and messages across an associated network connection. For more information about the DICOM Communication Protocol, refer to LEADTOOLS DICOM Network Communication Support for Message Exchange, or the DICOM Standard.
In order to transfer DICOM data and messages from one Application Entity (AE) to another, a network connection must be established. Once this connection has been established, the connection must be associated (also referred to as establishing an Associate connection). When the Associate connection has been established, then DICOM data and messages can be transferred between AEs.
AEs can have the role of Service Class Provider (SCP), Service Class User (SCU), or both. An SCU makes requests for data or services, and may also receive data. An SCP listens for incoming connection requests from SCUs. Once these connections are established (and an associate connection created), the SCP processes requests and provides data or services requested by SCUs.
In this documentation the basic network connection will be referred to as a DICOM Network connection or a DICOM Network. Information concerning a DICOM Network connection will be maintained in and accessed through a DICOM Network object.
When creating either an SCU or an SCP application, a DICOM Network connection (a DICOM network object) must be created. In addition, for every connection request accepted by an SCP, the SCP must create a DICOM Network object in which to maintain information about that specific SCU-SCP connection.
LEADTOOLS provides a number of class members for creating and initializing a DICOM Network and for transferring DICOM data and messages.
For creating a DICOM Network connection, use the following methods:
When a DICOM Network connection is no longer needed, it should be closed. The following methods may be used in closing the DICOM Network connection:
LEADTOOLS provides methods for sending DICOM messages. These include both low-level and high-level methods. The message sending methods can be divided into two groups.
For sending DICOM Connection messages, including messages used in establishing a DICOM Associate connection, use the following:
DicomNet.OnReceiveAssociateRequest
DicomNet.OnReceiveAssociateAccept
DicomNet.OnReceiveAssociateReject
DicomNet.OnReceiveReleaseRequest
DicomNet.OnReceiveReleaseResponse
For sending data messages, LEADTOOLS provides the following methods:
DicomNet.OnReceiveCStoreRequest
DicomNet.OnReceiveCStoreResponse
DicomNet.OnReceiveCFindRequest
DicomNet.OnReceiveCFindResponse
DicomNet.OnReceiveCGetResponse
DicomNet.OnReceiveCMoveRequest
DicomNet.OnReceiveCMoveResponse
DicomNet.OnReceiveCCancelRequest
DicomNet.OnReceiveCEchoRequest
DicomNet.OnReceiveCEchoResponse
DicomNet.OnReceiveNReportRequest
DicomNet.OnReceiveNReportResponse
DicomNet.OnReceiveNGetResponse
DicomNet.OnReceiveNSetResponse
DicomNet.OnReceiveNActionRequest
DicomNet.ONReceiveNActionResponse
DicomNet.OnReceiveNCreateRequest
DicomNet.OnReceiveNCreateResponse
DicomNet.OnReceiveNDeleteRequest
DicomNet.OnReceiveNDeleteResponse
Finally, you can retrieve information about a DICOM Network connection using these methods:
DicomNet.Association
For more information about the DICOM Associate connection, refer to Working with DICOM Associate Connections.
Help Collections
Raster .NET | C API | C++ Class Library | HTML5 JavaScript
Document .NET | C API | C++ Class Library | HTML5 JavaScript
Medical .NET | C API | C++ Class Library | HTML5 JavaScript
Medical Web Viewer .NET
Multimedia
Direct Show .NET | C API | Filters
Media Foundation .NET | C API | Transforms
Supported Platforms
.NET, Java, Android, and iOS/macOS Assemblies
Imaging, Medical, and Document
C API/C++ Class Libraries
Imaging, Medical, and Document
HTML5 JavaScript Libraries
Imaging, Medical, and Document