LDicomNet::SendCStoreRequest
#include "ltdic.h"
L_INT LDicomNet::SendCStoreRequest(nPresentationID, nMessageID, pszClass, pszInstance, nPriority, pszMoveAE, nMoveMessageID, pDS)
L_UCHAR nPresentationID; |
/* presentation ID */ |
L_UINT16 nMessageID; |
/* message ID */ |
L_TCHAR * pszClass; |
/* class type */ |
L_TCHAR * pszInstance; |
/* instance */ |
L_UINT16 nPriority; |
/* priority of the message */ |
L_TCHAR * pszMoveAE; |
/* name of the application entity */ |
L_UINT16 nMoveMessageID; |
/* message ID */ |
LDicomDS *pDS; |
/* data set to be stored */ |
Sends a C-STORE-REQ message to a peer member of a connection. This function is available in the Medical Suite Toolkit.
Parameter |
Description |
|
nPresentationID |
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. |
|
nMessageID |
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. |
|
pszClass |
Class affected by the request. This will be an SOP Class or an SOP MetaClass. |
|
pszInstance |
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. |
|
nPriority |
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: |
|
|
Value |
Meaning |
|
COMMAND_PRIORITY_LOW |
[0x0002] Low priority message. |
|
COMMAND_PRIORITY_MEDIUM |
[0x0000] Medium priority message. |
|
COMMAND_PRIORTY_HIGH |
[0x0001] High priority message. |
pszMoveAE |
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. |
|
nMoveMessageID |
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. |
|
pDS |
Pointer to the data set to be stored. |
Returns
0 |
SUCCESS |
>0 |
An error occurred. Refer to Return Codes. |
Comments
When an SCU requests a Move (C-MOVE-REQ), the SCP may have to call this function 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.
Calling this function generates a call to LDicomNet::OnReceiveCStoreRequest on the SCP. The SCP should respond by calling LDicomNet::SendCStoreResponse which will generate a call to LDicomNet::OnReceiveCStoreResponse.
Required DLLs and Libraries
LTDIC For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application |
See Also
Example
L_INT LDicomNet__SendCStoreRequestExample(LMyDicomNet *m_pDicomNet) { //This example sends an C-Store Request to a server //In this example: // //1. LMyDicomNet is a class derived from LDicomNet //2. LMyDicomNet has the following member variables: // m_nClientOrServer: can be (STATUS_NONE, STATUS_SERVER, STATUS_CLIENT) // identifieds the LMyDicomNet object as a server or a client // m_nDataCommand: can be (COMMAND_C_MOVE,COMMAND_C_GET) // set so the server knows how a C-Store Response was generated // //3. m_pDicomNet points to a valid LMyDicomNet object // LMyDicomNet *m_pDicomNet // //4. A connection exists between client and server //5. An association exists between the client and server L_INT nRet; pDICOMELEMENT pDicomElement; CString strMsg= TEXT("C-Store\n"); //Pick a dicom file to send as the data set LDicomDS DicomDS; nRet =DicomDS.LoadDS(TEXT("C:\\Program Files\\LEAD Technologies, Inc\\LEADTOOLS 15.0\\Images\\work\\images\\dicom16.dic"),0); if(nRet > 0) return nRet; //Find element with TAG == TAG_SOP_INSTANCE_UID pDicomElement = DicomDS.FindFirstElement(NULL, TAG_SOP_INSTANCE_UID, FALSE); //Get first string in Value Field of dicom element CString strInstanceUID = DicomDS.GetStringValue(pDicomElement, //dicom element 0, //index 1 //count ); //Get first element pDicomElement = DicomDS.FindFirstElement(NULL, TAG_SOP_CLASS_UID, FALSE); CString strClassUID = DicomDS.GetStringValue(pDicomElement, 0, 1); //Get the associate object LDicomAssociate *pDicomAssociate = m_pDicomNet->GetAssociate(); //See if class is supported in the assocation L_UCHAR nPresentationID = pDicomAssociate->FindAbstract((L_TCHAR *)(LPCTSTR)strClassUID); //nPresentationID must be odd--0 indicates failure if (nPresentationID==0) { CString strTmp; strTmp.Format(TEXT("Abstract Syntax[%s] Not Included in the Association"), strClassUID); strMsg = strMsg + strTmp; } else { L_UINT16 uUniqueID = 99; m_pDicomNet->m_FileCount = 0; //used for file name in OnReceiveCStoreRequest event nRet =m_pDicomNet->SendCStoreRequest( nPresentationID, uUniqueID, (L_TCHAR *)(LPCTSTR)strClassUID, (L_TCHAR *)(LPCTSTR)strInstanceUID, COMMAND_PRIORITY_MEDIUM, TEXT(""), 0, &DicomDS); if(nRet > 0) return nRet; } AfxMessageBox(strMsg); return DICOM_SUCCESS; }