virtual L_VOID LDicomNet::OnReceiveCStoreRequest(nPresentationID, nMessageID, pszClass, pszInstance, nPriority, pszMoveAE, nMoveMessageID, pDS)
Presentation ID. The presentation ID provides information about both the class type of the data and the transfer syntax to use when transferring the data.
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.
Class affected by the request. This will be an SOP Class or an SOP MetaClass.
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.
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. Possible values are:
|COMMAND_PRIORITY_LOW||[0x0002] Low priority message.|
|COMMAND_PRIORITY_MEDIUM||[0x0000] Medium priority message.|
|COMMAND_PRIORITY_HIGH||[0x0001] High priority message.|
Character string that contains the name of the application entity that originally requested the move. For a simple storage request from a client to a server, this should be ". When the request is a sub-operation of a C-MOVE, this will contain the name of the AE that requested the move.
The ID of the original move request message. For a simple storage request from a client to a server, this should 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.
Pointer to the data set to be stored.
A call to this function is generated on a peer member of a connection when LDicomNet::SendCStoreRequest is called.
To customize this function, you must derive a class from LDicomNet and override this function.
When an SCU requests a Move (C-MOVE-REQ), the SCP may have to call LDicomNet::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.
In this example:
m_pDicomNet points to a valid LMyDicomNet object
A connection exists between client and server
L_VOID LMyDicomNet::OnReceiveCStoreRequest(L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_TCHAR *pszInstance, L_UINT16 nPriority, L_TCHAR *pszMoveAE, L_UINT16 nMoveMessageID, LDicomDS *pDS)
strMsg.Format(TEXT("*** OnReceiveCStoreRequest ***\nnPresentationID[%d]\nnMessageID[%d]\npszClass[%s]\npszInstance[%s]\nnPriority[%d]\npszMoveAE[%s]\nnMoveMessageID[%d]"),
//...Do the store here
//...nStatus = status of the store
if (pDS != NULL)
strMsg += TEXT("Saving[");
strMsg += strFileName;
strMsg += TEXT("]");
L_UINT16 nStatus = COMMAND_STATUS_SUCCESS;
strMsg += TEXT("SendCStoreResponse\n");
SendCStoreResponse(nPresentationID, nMessageID, pszClass, pszInstance, nStatus);
Medical Web Viewer .NET
.NET, Java, Android, and iOS/macOS Assemblies
C API/C++ Class Libraries