Accepted transfer syntax

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
shahvezakhtar007
Posts: 9
Joined: Tue, 2017-07-04, 09:27

Accepted transfer syntax

#1 Post by shahvezakhtar007 »

Hello,

Could you tell on what basis transfer syntax is accepted by SCP Server?

Consider the example:

From SCU I am sending this in association parameters:-
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=JPEGLossless:Non-hierarchical-1stOrderPrediction
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Context ID: 3 (Proposed)
Abstract Syntax: =VerificationSOPClass
Proposed SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=JPEGLossless:Non-hierarchical-1stOrderPrediction
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit

And in SCP:
cond = ASC_acceptContextsWithPreferredTransferSyntaxes( assoc->params, knownAbstractSyntaxes, DIM_OF(knownAbstractSyntaxes), transferSyntaxes, numTransferSyntaxes);

where transferSyntaxes[0] = LittleEndianExplicit and transferSyntaxes[1] = JPEGLossless:Non-hierarchical-1stOrderPrediction.

So which transferSyntax is accepted in this case?
LEE or JPEGLossless?

Marco Eichelberg
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 1437
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany
Contact:

Re: Accepted transfer syntax

#2 Post by Marco Eichelberg »

I guess the answer comes a bit late, but it's actually quite simple. The algorithm will accept the first transfer syntax from your own list of preferences that was proposed by the caller, so in this case, the result would be LittleEndianExplicit.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest