Google cloud platform 我尝试使用dcmsend get“发送dicom文件；关联请求失败：0006:0321无法识别的PDU类型：53“；

我尝试使用dcmsend发送dicom文件

“关联请求失败：0006:0321无法识别的PDU类型：53”

得到如下回应

D: $dcmtk: dcmsend v3.6.3+ DEV $
D: 
I: checking input files ...
D: adding DICOM file '/Users/at009/Downloads/Dicom-3.dcm'
D: getting SOP Class UID, SOP Instance UID and Transfer Syntax UID from DICOM file
D: DcmMetaInfo::checkAndReadPreamble() TransferSyntax="Little Endian Explicit"
D: trying to get SOP Class UID, SOP Instance UID and Transfer Syntax UID from meta-header
D: successfully added SOP instance 1.2.840.114191.3.6817226.2247938.26.1.5.1.1558014084 to the transfer list
D: in total, there are 1 SOP instances to be sent, 0 invalid files are ignored
D: multiple associations allowed (option --multi-associations used)
D: preparing presentation context for SOP Class / Transfer Syntax: DigitalMammographyXRayImageStorageForPresentation / Little Endian Explicit
D: added new presentation context with ID 1
D: -----------------------------------------------------------------
D: starting association #1
I: initializing network ...
D: Configured a total of 1 presentation contexts for SCU
I: negotiating network association ...
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.3
D: Our Implementation Version Name:   OFFIS_DCMTK_363
D: Their Implementation Class UID:    
D: Their Implementation Version Name: 
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    Test
D: Called Application Name:     IMPORTADAPTER
D: Responding Application Name: IMPORTADAPTER
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  0
D: Presentation Contexts:
D:   Context ID:        1 (Proposed)
D:     Abstract Syntax: =DigitalMammographyXRayImageStorageForPresentation
D:     Proposed SCP/SCU Role: Default
D:     Proposed Transfer Syntax(es):
D:       =LittleEndianExplicit
D:       =BigEndianExplicit
D:       =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation:  none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response:  none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: setting network send timeout to 60 seconds
D: setting network receive timeout to 60 seconds
D: Constructing Associate RQ PDU
D: Association Request Failed: 0006:0321 Unrecognized PDU type: 53
F: cannot negotiate network association: Unrecognized PDU type: 53
D: Cleaning up internal association and network structures
11:06:49 Send job terminated with result: 61

查看日志中的“无法识别的PDU类型”，这看起来与错误的网络密切相关；网络上的一个非常错误的数据

您确定要发送到正确的目标节点吗？您要发送到的节点是否能够接收DICOM

查看您的“google-…”标记，侦听器可能期望HTTP，而您正在推DICOM

请注意，“数据格式/协议”和“网络协议”是两个不同的东西。您的“google-…”工具可能支持DICOM作为数据格式，但网络协议可能不同；说HTTP

---

有多种方法可以在网上交流DICOM数据；但这是完全不同的主题。

您使用的是什么GCP产品？目前尚不清楚您的具体设置，因此社区中的任何人都很难提供帮助。我建议根据我推荐的URL:“”为您的问题添加更多详细信息。使用Google Kubernetes引擎创建dicom存储并部署dicom适配器。在gcp中创建了VM实例。使用虚拟机的ssh，可以使用DCMSEND命令发送DCM文件，但当我尝试使用虚拟机的外部ip发送dicom映像时，它给出了上述错误。