DICOM @ OFFIS

Discussion Forum for OFFIS DICOM Tools - For registration, send email with desired user name to the OFFIS DICOM team
It is currently Mon, 2017-09-25, 05:13

All times are UTC + 1 hour




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: Problem with storescp
PostPosted: Tue, 2008-06-24, 20:39 
Offline

Joined: Tue, 2005-02-01, 22:53
Posts: 35
Hello,

I am currently having a siemens cath lab digitizer system sending XA (angiography sequence) to storescp.
The store scp receives association and negociate transfer syntax very well. But soon afterwards the remote peer sends an association release signal (DUL Peer requested release) instead of sending C-Store command. The errors comes from the ProcessCommand function after DIMSE_receiveCommand. The returning condition of this function is equal to DUL_PEERREQUESTEDRELEASE.

Is this behaviour correct ?
I strictly got no error on storescp.

Here is the log :

Code:
PDU Type: Associate Request, PDU Length: 339 + 6 bytes PDU header
  01  00  00  00  01  53  00  01  00  00  48  43  49  5f  58  41
  5f  31  20  20  20  20  20  20  20  20  41  4e  5f  30  34  36
  35  34  20  20  20  20  20  20  20  20  00  00  00  00  00  00
  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
  00  00  00  00  00  00  00  00  00  00  10  00  00  15  31  2e
  32  2e  38  34  30  2e  31  30  30  30  38  2e  33  2e  31  2e
  31  2e  31  20  00  00  3b  01  00  00  00  30  00  00  1c  31
  2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  35  2e  31
  2e  34  2e  31  2e  31  2e  31  32  2e  31  40  00  00  13  31
  2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32
  2e  31  20  00  00  39  03  00  00  00  30  00  00  1c  31  2e
  32  2e  38  34  30  2e  31  30  30  30  38  2e  35  2e  31  2e
  34  2e  31  2e  31  2e  31  32  2e  31  40  00  00  11  31  2e
  32  2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32  20
  00  00  3e  05  00  00  00  30  00  00  1c  31  2e  32  2e  38
  34  30  2e  31  30  30  30  38  2e  35  2e  31  2e  34  2e  31
  2e  31  2e  31  32  2e  31  40  00  00  16  31  2e  32  2e  38
  34  30  2e  31  30  30  30  38  2e  31  2e  32  2e  34  2e  37
  30  50  00  00  34  51  00  00  04  00  00  70  00  52  00  00
  15  31  2e  33  2e  31  32  2e  32  2e  31  31  30  37  2e  35
  2e  34  2e  33  2e  32  55  00  00  0f  53  49  45  4d  45  4e
  53  3a  44  43  52  20  33  2e  30
Association Received
Parameters:
Our Implementation Class UID:    1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:    1.3.12.2.1107.5.4.3.2
Their Implementation Version Name: SIEMENS:DCR 3.0
Application Context Name:    1.2.840.10008.3.1.1.1
Calling Application Name:    AN_04654
Called Application Name:     HCI_XA_1
Responding Application Name:
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 28672
Presentation Contexts:
  Context ID:        1 (Proposed)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
    Proposed Transfer Syntax(es):
      =LittleEndianExplicit
  Context ID:        3 (Proposed)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
    Proposed Transfer Syntax(es):
      =LittleEndianImplicit
  Context ID:        5 (Proposed)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
    Proposed Transfer Syntax(es):
      =JPEGLossless:Non-hierarchical-1stOrderPrediction
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
called AE:  HCI_XA_1
calling AE: AN_04654
Constructing Associate AC PDU
Association Acknowledged (Max Send PDV: 28660)
Our Implementation Class UID:    1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:    1.3.12.2.1107.5.4.3.2
Their Implementation Version Name: SIEMENS:DCR 3.0
Application Context Name:    1.2.840.10008.3.1.1.1
Calling Application Name:    AN_04654
Called Application Name:     HCI_XA_1
Responding Application Name: STORESCP
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 28672
Presentation Contexts:
  Context ID:        1 (Accepted)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
    Accepted Transfer Syntax: =LittleEndianExplicit
  Context ID:        3 (Accepted)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
    Accepted Transfer Syntax: =LittleEndianImplicit
  Context ID:        5 (Transfer Syntaxes Not Supported)
    Abstract Syntax: =XRayAngiographicImageStorage
    Proposed SCP/SCU Role: Default
    Accepted SCP/SCU Role: Default
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
DIMSE receiveCommand
Association Release



Could the problem come from the responding AETitle which is not the same as the called AETitle ?

Thanks in advance.


Top
 Profile  
 
 Post subject:
PostPosted: Wed, 2008-06-25, 09:22 
Offline
ICSMED DICOM Services
ICSMED DICOM Services

Joined: Fri, 2004-10-29, 21:38
Posts: 2217
Location: Oldenburg, Germany
To me it seems that the SCU (Siemens Cath Lab System) is proposing to send XA images either uncompressed or JPEG Lossless compressed but then expecting the SCP to always accept JPEG Lossless (which is not the case for the storescp in the standard configuration). You could try to start storescp with option +xs (--prefer-lossless). Maybe this helps ...

Anyway, if my assumption is correct, the behavior of the SCU is not DICOM conformant.

Quote:
Could the problem come from the responding AETitle which is not the same as the called AETitle ?

You could check this by setting the AE Title of the storescp accordingly with option -aet (--aetitle).


Top
 Profile  
 
 Post subject: Store error
PostPosted: Wed, 2008-06-25, 12:51 
Offline

Joined: Tue, 2005-02-01, 22:53
Posts: 35
Hello,

Thanks a lot for your analyse.
Setting to +xs make storescp to receive images correctly.

What are the consequences in this case ?
Images are in lossless format ?

Thanks in advance


Top
 Profile  
 
 Post subject:
PostPosted: Wed, 2008-06-25, 13:25 
Offline
ICSMED DICOM Services
ICSMED DICOM Services

Joined: Fri, 2004-10-29, 21:38
Posts: 2217
Location: Oldenburg, Germany
Quote:
What are the consequences in this case ? Images are in lossless format ?

Yes, images are received with JPEG Lossless compression as provided by the SCU. Btw, this is the standard compression scheme for XA images.


Top
 Profile  
 
 Post subject: Store scp
PostPosted: Wed, 2008-06-25, 15:01 
Offline

Joined: Tue, 2005-02-01, 22:53
Posts: 35
Hello,

Thanks again for your quick answer.

For information, can i find the list of the standard compression scheme according to sop class uid into the dicom standards pages (from acrnema website) ?


Top
 Profile  
 
 Post subject:
PostPosted: Thu, 2008-06-26, 10:01 
Offline
ICSMED DICOM Services
ICSMED DICOM Services

Joined: Fri, 2004-10-29, 21:38
Posts: 2217
Location: Oldenburg, Germany
No, there is no such list in the standard. By "standard compression scheme" I meant that this is the usual transfer syntax which is used in practice. In cardiology, XA images are typically archived and exchanged on CD media. The DICOM standard defines application profiles for this purpose which require XA images to be encoded in JPEG lossless transfer syntax.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group