DICOM C-GET vs C-MOVE

阅读更多

DICOM中C-Get 和C-Move的区别。

C-Move操作基本上都包含了C-Get的功能，而且有些地方，C-Get无法替代C-Move。

比如：

 

1、C-Move可以实现从一个AE将DICOM文件发送另外一个AE。而C-Get只能实现从SCP获取dicom到自身。从这个方面来说，C-Get功能有点多余。

2、从系统安全角度，C-Get随机开放了一个未绑定的端口来接收服务端图像。C-Move却需要两步连接，在发出C-MoveRequest后，必须采用C-Store来监听接收服务端的图像数据。而对于C-Store操作，都是绑定固定端口的，比较安全。C-Get就相当于电子邮箱，有了账号和密码，任何人都可以登陆操作。而是C-Move还有一个绑定目标计算机的操作，相当于授权目标计算机才能接收数据。

 

DICOM C-GET vs C-MOVE

I have to develop a SCU (Service Class User) application for querying PACS and retrieve the DICOM images. Should I use C-GET or C-MOVE DICOM protocol to retrieve the images?

3 Answers

active oldest votes

You can use either, but the preferred is C-Move.

Do we have any reasons for why C-Move is preferred. –  Ramakrishna  Dec 24 '09 at 6:40 3 I think there are two reasons for this. 1) With C-Move you can also request sending images from one AET to some other AET. This is not possible if you only have C-Get. With C-Move, C-Get becomes redundant. 2)IT security issues. With C-Get, the client opens a random inbound port to recieve images. C-Move involves two associations with the second association being a C-Store from server to client. C-Store happens over well defined server port and is more trusted by the IT support. –  Canopus  Dec 24 '09 at 8:16 2 Correct. In security terms, a C-GET is as secure as retrieving your email... anyone can do it from anywhere if they have your username and password. A C-MOVE requires that the server recognizes YOUR COMPUTER as an authorized machine to receive information, so without explicit access, even if you have all the information to QUERY the server, you still can't retrieve anything. You CAN implement "promiscuous" mode, where if the DestinationAE isn't recognized, it sends the requested information back to the caller, but it's highly discouraged from all I've seen. –  Nathan Wheeler  Sep 8 '10 at 17:55

The point is not only about security, but about implementation. In C-MOVE, the SCP list the supported transfer syntaxes for each image matching the previous query. Then the SCU agree with any. On the other side, in the C-GET, the SCU list its supporting transfer syntaxes before any query is made, and the SCP has to pick any and compromise to send whatever the SCU ask for in that format. So, the C-GET implementation for PACS is harder and more complex since it has to be able to encode anything to anything. While in the C-MOVE is the client who has to be able to decode and show anything which is much easier...

DICOM - SCU (Service Class User) application for querying PACS DICOM The Digital Imaging and Communications in Medicine is a standard which is used for the exchange of images and related information. The DICOM standard can be thought of as having several levels of support, such as the support for image exchange for both senders and receivers, the underlying information model and information management services. This blog provides a rich information / overview of the characteristic elements of the DICOM standard. I have found a link which contains all of its detail with coding. It may be helpful for you. Complete description of DICOM - Just at single page.