Question for ppsscpfs

Questions regarding other OFFIS DICOM tools

Moderator: Moderator Team

Post Reply
Posts: 3
Joined: Tue, 2014-07-01, 13:56

Question for ppsscpfs

#1 Post by allers » Tue, 2014-07-01, 14:42


I am using the ppsscpfs tool with the following command line:

ppsscpfs.exe -v -d +xb -od "c:\test" --allow-unknown -pdu 16384 -csa 4444

My MPPS SCU is sending an N-CREATE-RQ to the MPPS SCP, which stores the request locally in "C:\test". During association negotiation "Big Endian Explicit" Transfer Syntax is negotiated for MPPS SOP Class. Hence the MPPS SCU should send the N-CREATE-RQ in "Big Endian Explicit".

My questions is, how the ppsscpfs tool stores the files in the output directory. When doing a "dcmdump" on these file I get "LittleEndianExplicit" as Transfer Syntax:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianExplicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0060) CS [MR] # 2, 1 Modality

I assume that the tool does not use the negotiated Transfer Syntax for writing MPPS files as it is possible with storescp, right?

The tool shows the following version: ppsscpfs.exe -h

ppsscpfs v3.5.4a 2007-08-10

Thanks and Best Regards,

Marco Eichelberg
Posts: 1280
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany

Re: Question for ppsscpfs

#2 Post by Marco Eichelberg » Wed, 2014-07-02, 11:00

Correct. The MPPS SCP (ppsscpfs) always stores MPPS datasets in Explicit VR Little Endian transfer syntax, independent from the transfer syntax that was used during the network connection. Please also note that each file created by the MPPS SCP represents one MPPS SOP instance, not one message. If you send an N-SET to update an MPPS object, the file will be re-written to reflect the updated status of the MPPS object. Since different N-CREATE and N-SET message could, at least in theory, be sent using different network connections with different transfer syntaxes, there is no real point in keeping the transfer syntax in the file.

Note that there is another MPPS related tool (also not part of the public toolkit) named "PPS manager", which implements the IHE Scheduled Workflow actor of the same name. That tool stores and forwards individual N-CREATE and N-SET messages and also keeps the transfer syntax in the file consistent with the transfer syntax used in the incoming network association. But I guess that won't help you much.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest