Parameters

presentationID
The Presentation Context ID. The ID provides information about both the class type of the data and the Transfer Syntax to use when transferring the data.

messageID
The Message ID. Each message sent by a member of a connection should have a unique ID. Since a member of a connection may send several messages, this ID allows that member to identify when a specific request has been completed.

affectedClass
The class affected by the request. This will be a SOP Class or a Meta SOP Class.

instance
The instance of the class. A server may, for example, have three instances of the Nuclear Medicine Class. This value identifies the data with a specific instance.

priority
The priority level of the message. The Service Class Provider may or may not support priority. Therefore, setting this parameter may or may not have any effect.

moveAE
The name of the Application Entity that originally requested the move. For a simple storage request from a client to a server, this will be an empty string. When the request is a sub-operation of a C-MOVE, this will contain the name of the AE that requested the move.

moveMessageID
The ID of the original move request message. For a simple storage request from a client to a server, this will be 0. When the request is a sub-operation of a C-MOVE, this will contain the original message ID of the C-MOVE request.

dataSet
A DicomDataSet object that contains the Data Set to be stored.

Remarks

A call to this method is generated on a peer member of a connection when SendCStoreRequest is called.
To customize this method, you must derive a class from DicomNet and override this method.

When an SCU requests a Move (C-MOVE-REQ), the SCP may have to call SendCStoreRequest to request one or more C-STORE-REQ sub-operations to complete the storage. The series of calls and information transfer in a C-MOVE-REQ is complicated. For more information, refer to Moving Composite Data.