WO2002021822A2 - Methods and apparatus for streaming dicom images through data element sources and sinks - Google Patents
Methods and apparatus for streaming dicom images through data element sources and sinks Download PDFInfo
- Publication number
- WO2002021822A2 WO2002021822A2 PCT/US2001/027465 US0127465W WO0221822A2 WO 2002021822 A2 WO2002021822 A2 WO 2002021822A2 US 0127465 W US0127465 W US 0127465W WO 0221822 A2 WO0221822 A2 WO 0221822A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- data element
- dicom
- bytes
- values
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H30/00—ICT specially adapted for the handling or processing of medical images
- G16H30/20—ICT specially adapted for the handling or processing of medical images for handling medical images, e.g. DICOM, HL7 or PACS
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H30/00—ICT specially adapted for the handling or processing of medical images
- G16H30/40—ICT specially adapted for the handling or processing of medical images for processing medical images, e.g. editing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/18—End to end
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/613—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
Definitions
- the present invention relates in general to image transmission, and relates more particularly to methods and apparatus for streaming DICOM images through data element sources and sinks.
- Medical images can be communicated between computers using a network protocol standard named Digital Imaging and Communications in Medicme
- DICOM computed tomography
- MR magnetic resonance
- ultrasound ultrasound
- the DICOM network protocol defines a format used to store, receive, and transmit digital image data and objects.
- the DICOM object format typically contains a header and image data.
- the header contains information about the patient's name, type of medical procedure or scan, image dimensions, etc.
- a DICOM image file includes a header which contains data that describe the physical dimensions of a medical image.
- the header can also include data that contains textual information about a scan contained in the image.
- the size of a header may vary depending upon the amount of information that is stored in the image.
- the data in a header can be organized as one or more groups. One group may be a meta file information group which defines one or more data elements such as a group length, a file version, and a transfer syntax. The number of data elements depends upon the image type and the characteristics of the particular image type.
- Object data typically follows the header data.
- the object data can have data elements which define characteristics of the particular object type and the object data associated with the particular object type.
- the object data can include information obtained in a medical scan performed in two and/or three dimensions.
- a magnetic resonance image (MRI) may have DICOM image data that includes a data element that specifically defines the MRI echo time.
- image data may be compressed or encapsulated to reduce the image file size.
- DICOM data elements are small and bounded in size by the type of data that they can contain. For example, integer data elements may only contain a few integers. These data elements are always relatively small and do not have a significant or large impact on the performance and scalability of a network because of their relatively small size. Other types of DICOM data elements such as image data can be relatively large in comparison. Two types of DICOM data elements warrant special attention since they can be large: sequences and pixel data. Sequences in DICOM are a type of data element that can recursively contain other data sets. Since they can contain other data sets, they could potentially be relatively large if they contain a very large number of small data elements, or if they contain pixel data.
- Pixel data is a type of data element that corresponds to actual image data.
- Pixel data is a type of data element that can be relatively large, and in some cases, extremely large. In cases where a very large data set is being communicated, almost all of the bytes in the data set may be pixel data. Most other types of data elements communicate information about the image (metadata) such as the patient name, type of image, and image date and time.
- DICOM communicates by transmitting data sets.
- a data set is an ordered set of data elements, such as sequence data, pixel data, or other types of data.
- Each data element represents information that is being communicated.
- Each data element has a particular type, and can vary in size depending upon the data element type. For example, by way of illustration of the different range in the size of an image file, the file size of a DICOM image can range from approximately 128 kilobytes (KB) for a single DICOM image, or up to approximately 600 megabytes (MB) for a time- sequence or multi-frame DICOM image.
- KB kilobytes
- MB megabytes
- DICOM data sets are communicated using one or more transfer syntaxes.
- a transfer syntax specifies a type of encoding of the data for the particular data set.
- the DICOM network protocol can support at least three types of transfer syntax: little endian explicit value representation, little endian implicit value representation, and big endian explicit value representation.
- a unique feature of DICOM network protocol allows data to be transformed into a different form when transported. This unique feature of DICOM data transformation during the transmission of DICOM images over a conventional DICOM network creates a relatively large demand for the memory resources in a DICOM network.
- the DICOM network protocol consists of multiple layers.
- the DICOM network protocol can also be built on top of a standard TCP/IP protocol.
- the DICOM protocol breaks a data set into one or more data packets before sending it across the network.
- Each data packet defines one or more protocol data units (PDUs).
- PDUs protocol data units
- the DICOM protocol requires that the data sets being communicated across the network also be packaged as protocol data units (PDUs). For example, when the DICOM network protocol runs on top of the TCP/IP protocol, this effectively double packetizes the data. That is, DICOM packages the data sets as protocol data units (PDUs) and TCP/IP packages the data sets as data packets.
- This type of DICOM/TCP/IP layered protocol structure creates a relatively large demand for memory resources in a conventional DICOM network. Moreover, the transmission of DICOM images through multiple layers of the DICOM network protocol can also create a relatively large demand for memory resources in a conventional DICOM network.
- the DICOM protocol follows a strict order for establishing and maintaining communications.
- a state machine operated by the Upper Service Level layer of the DICOM protocol specifies a strict order for establishing and maintaining communications between two devices in a DICOM network. For example, since the DICOM protocol is connection oriented, no communication of DICOM data can occur until a DICOM association or connection has been established between two devices. That is, at least two DICOM protocol-based devices must be in communication with each other in order to establish a DICOM association or connection. After a DICOM association or connection has been established, communication must continue to follow a strict order, and then the DICOM association or connection must be closed in an orderly fashion.
- Such a strict order dictated by the DICOM network protocol can create a relatively large demand for memory resources in a conventional DICOM network.
- DICOM association or connection can be used to perform DICOM data operations in the DICOM network.
- DICOM operations can be performed sequentially, or one after another, or concurrently.
- Concurrent operations are called asynchronous operations per association in DICOM.
- Conventional DICOM networks typically handle multiple concurrent or asynchronous operations involving DICOM data, and large DICOM file sizes can create a relatively large demand for memory resources in a conventional DICOM network.
- DICOM communication networks suffer a significant drop in the speed and performance when handling relatively large DICOM object files. Since DICOM objects tend to be relatively large, communication of DICOM objects can quickly overwhelm a communications network that is not designed to accommodate such large image objects. Conventional DICOM communication networks rely upon servers to handle multiple and simultaneous DICOM operations. In cases where a single DICOM file or storage operation could consume a large portion of a server's resources such as a memory and processing time, a DICOM server may suffer from poor scalability and performance when handling such large objects. The network and server performance problems can worsen significantly when multiple clients attempt to simultaneously or concurrently use the network.
- the invention addresses the problems above by providing methods and apparatus for streaming DICOM objects in a network through data element sources and data element sinks.
- Methods and apparatus according to the present invention limit the consumption of memory resources during the handling of DICOM objects in a network.
- methods and apparatus according to the present invention permit one or more applications in a DICOM communications network to limit memory usage regardless of the size of DICOM objects to be communicated in the network.
- methods and apparatus according to the present i ention permit transmission digital data between two devices in a communications network.
- methods and apparatus according to the present invention permit transmission of DICOM objects in a network while maintaining or improving the performance of one or more applications operating in the network.
- Methods and apparatus according to the present invention permit the transmission of digital data between two devices in a communications network using a fixed amount of memory.
- methods and apparatus according to the present invention permit streaming DICOM objects of relatively large file size between two devices in a DICOM network using only a limited, fixed size of memory.
- methods and apparatus according to the present invention apportion the object into small, fixed portions of data elements.
- the methods and apparatus according to the present invention then limit the number of data elements that can be stored in memory at a single time for a single operation. Each data element is then handled incrementally by a data element source or data element sink to avoid using too much memory for a single operation.
- the methods and apparatus according to the present invention permit a DICOM communications network to stream a DICOM object or image using only a small, fixed amount of memory regardless of the size of the DICOM object or image that is being communicated.
- a first exemplary method for communicating digital data from a first device to a second device using a fixed amount of memory the method initially defines a limited number of data values to be stored in a data stream. Next, the method incrementally reads a set of data elements from a first device so that each data element is read one at a time. Subsequently, a data value is extracted from each data element. If a data element is larger than a threshold size, then the data can be transmitted in relatively small, fixed size portions of data. Finally, the method transmits the data stream containing a predefined limited number of data values to a second device so that data values can be encoded to the second device.
- the present invention may receive a file containing digital data from a first device. Next, the method creates a data stream containing data values for the file containing digital data. Based on the data stream, the present invention creates a data element source. The method can then incrementally process the data elements one at a time from the data stream through the data element source. Finally, the data elements are transmitted to a data element sink which encodes the data elements to a second device.
- An exemplary embodiment of an apparatus of the present invention includes a communications module for streaming digital data between two devices in a network using a fixed amount of memory.
- the communications module includes a data element source and a communications engine.
- the data element source is configured for receiving a set of data elements from a first device.
- the data element source is also configured for incrementally processing a single data element at a time from the set of data elements.
- the communications engine is configured for extracting data values from the data elements and creating a data stream from the extracted data values by passing them to the data element sink which encodes them to the second device.
- the communications engine is further configured for transmitting the data stream containing the extracted data values to a second device.
- Another exemplary embodiment of an apparatus of the present invention includes a communications module for streaming digital data between two devices in a network using a fixed amount of memory.
- the communications module includes a data element sink and a communications engine.
- the data element sink is configured for receiving a set of data elements from a first device.
- the data element sink is also configured for incrementally writing a single data element at a time from the set of data elements.
- the communications engine is configured for extracting data values from the data elements and creating a data stream from the extracted data values.
- the communications engine is further configured for transmitting the data stream containing the extracted data values to a second device.
- the use of data element sources and data element sinks to incrementally process data elements and data values one at a time minimizes the amount of memory needed to perform a DICOM operation.
- the methods and apparatus according to the present invention limit the consumption of memory resources while providing a relatively small, fixed amount of memory for handling a relatively large DICOM object, while maintaining the performance of applications operating in the DICOM network.
- FIG. 1 is a functional block diagram of a system according to an exemplary embodiment of the present invention.
- FIG. 2 illustrates a data flow diagram of an exemplary embodiment of the present invention.
- FIGs. 3a-c illustrate an exemplary method of the present invention.
- FIGs. 4a-b illustrate a second exemplary method of the present invention.
- FIG. 5 illustrates a third exemplary method of the present invention.
- FIG. 6 illustrates a fourth exemplary method of the present invention.
- FIG. 7 shows a representative illustration of data contained in a DICOM image file.
- FIG. 8 illustrates data contained in a DICOM image file.
- the method initially defines a limited number of data values to be stored in a data stream.
- the method incrementally reads a set of data elements from a first device so that each data
- element is read one at a time. Subsequently, a data value is extracted from each data element. If a data element is larger than a threshold size, then the data can be transmitted in relatively small, fixed size portions of data. Finally, the method transmits the data stream containing a predefined limited number of data values to a second device so that data values can be encoded to the second device.
- the present invention may receive a file containing digital data from a first device. Next, the method creates a data stream containing data values for the file containing digital data. Based on the data stream, the present invention creates a data element source. The method can then
- the 20 incrementally process the data elements one at a time from the data stream through the data element source. Finally, the data elements are transmitted to a data element sink which encodes the data elements to a second device.
- the communications module includes a data element source and a communications engine.
- the data element source is configured for receiving a set of data elements from a first device.
- the data element source is also configured for incrementally processing a single data element at a time from the set of data elements.
- the communications engine is configured for extracting data values from the data elements and creating a data stream from the extracted data values by passing them to the data element sink which encodes them to the second device.
- the communications engine is further configured for transmitting the data stream containing the extracted data values to a second device.
- the communications module includes a data element sink and a communications engine.
- the data element sink is configured for receiving a set of data elements from a first device.
- the data element sink is also configured for incrementally writing a single data element at a time from the set of data elements.
- the communications engine is configured for extracting data values from the data elements and creating a data stream from the extracted data values.
- the communications engine is further configured for transmitting the data stream containing the extracted data values to a second device.
- FIG. 1 illustrates a functional block diagram of a system according to an exemplary embodiment of present invention.
- the system comprises a communications module 100.
- the communications module 100 is configured for the transmission or streaming of objects between an associated application program 101 and another application program via a network.
- the communications module 100 is configured for the transmission or streaming of DICOM objects including DICOM image files or other similar types of digital images between an associated application program 101 and another application program via a network.
- the communications module 100 can communicate between an associated application program 101 and an application program 130 via a communications network such as a DICOM network 102 to send or receive DICOM objects including DICOM image files or other similar types of digital objects.
- the communications module 100 generally communicates between a Service Class Provider (SCP) and a Service Class User (SCU).
- SCP Service Class Provider
- SCU Service Class User
- a SCP receives a request for a DICOM network protocol-defined service, while a SCU initiates a request for a DICOM network protocol-defined service.
- an associated application program 101 can be a SCU, and a server 128a-n executing an application program 130 can be a SCP.
- An associated application program 101 can be a DICOM application program such as a medical imaging program or an application program capable of communicating with the communications module 100 using a DICOM communications protocol or DICOM standard.
- the associated application program 101 may execute on one or more clients, medical imaging devices, storage devices, information systems, databases, printers, workstations, acquisition modules, modalities, viewing systems, DICOM media, digital archives, or other types of devices capable of operating using a DICOM communications protocol or DICOM standard. Representative examples of DICOM image files and associated information contained in a DICOM image file are shown in FIGs. 7-8.
- the communications module 100 includes a communications engine 104, a data element source 106, a data element sink 108, a state machine 110, a buffer 112, and a multiple-layer protocol such as a DICOM protocol 114.
- a communications engine 104 is configured for handling data and associated data elements between the associated application program 101 and the communications module 100, as well as between the communications module 100 and the DICOM network 102.
- the communications engine 104 can also be configured to transmit data and associated data elements between the various components of the communications module 100 as well as between the multiple layers of the DICOM protocol 114.
- a communications module according to other embodiments may have a fewer or greater number of elements providing similar features.
- the data element source 106 is a conceptual source for data elements.
- a data element source 106 can function as a forward iterator over a conceptual set of data elements.
- a data element source 106 can provide data elements one at a time, or in a block, to a Service Class User (SCU) or a Service Class Provider (SCP) such as client or server 128a-n.
- SCU Service Class User
- SCP Service Class Provider
- a data element source 106 can handle sequence data (SQ) elements.
- a data element source 106 can also include a pixel data decoder.
- a pixel data decoder handles pixel data incrementally, or one at a time.
- a pixel data decoder handles pixel data (PD) elements. Since a single pixel data element can contain several megabytes of data, a pixel data decoder permits the reading of the pixel data in relatively small, fixed size chunks of data. When a pixel data element is encountered, the pixel data decoder does not read the entire data element at once, but instead the pixel data is read incrementally into a fixed size buffer, such as the buffer shown as 112.
- a data element source 106 can include streaming data elements. Similarly, streaming data elements can be handled incrementally.
- the data element sink 108 is a conceptual storage for data elements.
- a data element sink 108 can write data elements one at a time, or in a block, to a Service Class User (SCU) such as client or server 128a-n.
- SCU Service Class User
- a data element sink 108 can handle sequence data (SQ) elements.
- a data element sink 108 can also include a pixel data encoder.
- a pixel data encoder handles pixel data incrementally, or one at a time.
- a pixel data encoder handles pixel data (PD) elements. Since a single pixel data element can contain several megabytes of data, a pixel data encoder permits the writing of the pixel data in relatively small, fixed size chunks of data. When a pixel data element is encountered, the pixel data encoder does not write the entire data element at once, but instead the pixel data is written incrementally into a fixed size buffer, such as the buffer shown as 112.
- a data element sink 108 can include streaming data elements. Similarly, streaming data elements can be handled incrementally.
- the state machine 110 initiates, monitors, and handles an association or connection between a Service Class Provider (SCP) and a Service Class User (SCU).
- SCP Service Class Provider
- SCU Service Class User
- the buffer 112 is a memory storage device configured to store data elements, data values, or other types of data.
- the buffer 112 can also include one or more smaller buffers or similar types of memory storage devices for storing data elements, data values, or other types of data.
- the DICOM protocol 114 contains multiple layers including a Transport layer 116, an Upper Level Service layer 118, a Data Service Layer 120, and a Service Class layer 122.
- the specifications, functionality, and more detailed description of the DICOM protocol and the associated layers 116-122 are set forth in the standards document Digital Imaging and Communications in Medicine (DICOM), PS 3.1-2000, National Electrical Manufacturers Association, 2000, which is incorporated herein by reference.
- the communications module 100 communicates with the associated application program 101.
- the communications module 100 can also communicate with another application program 130 through a communications network such as the DICOM network 102.
- another application program 130 will communicate via the DICOM network with the communications module 100 through an interface such as a physical layer 124, i.e. ETHERNET, ATM, FDDI, etc.
- the DICOM network 102 can utilize Transmission Control Protocol/Internet Protocol (TCP/IP) 126 to further facilitate communication with other networks, computers, platforms, and applications.
- TCP/IP Transmission Control Protocol/Internet Protocol
- the communications module 100 can be positioned with the Transport layer 112 adjacent to the TCP/IP 126, thus creating an interface between the DICOM network 102 and the communications module 100.
- a DICOM network 102 can include one or more servers 128a-n connected in a network configuration as shown. In some instances, a DICOM network 102 will be setup to operate in a local area network or LAN configuration.
- a server 128a-n can include platforms such as clients, medical imaging devices, storage devices, information systems, databases, printers, workstations, acquisition modules, modalities, viewing systems, DICOM media, digital archives, or other types of devices capable of operating using a DICOM communications protocol or DICOM standard.
- a server 128a-n can be a Service Class Provider (SCP) or a Service Class User (SCU).
- SCP Service Class Provider
- SCU Service Class User
- An application program 130 can be configured to execute on a server 128a-n.
- an application program 130 can be a DICOM application program such as a medical imaging program or an application program capable of communicating with the communications module 100 using a DICOM communications protocol or DICOM standard.
- An application program 130 may execute on other platforms such as clients, medical imaging devices, storage devices, information systems, databases, printers, workstations, acquisition modules, modalities, viewing systems, each of which may connected to the DICOM network 102.
- the communications module 100 can also communicate with a media storage module 132 and a meta database module 134.
- the media storage module 132 is configured to communicate with the communications module 100, and to store digital image data on a temporary or permanent basis.
- the media storage module 132 can include a storage medium such as a hard drive, a magneto-optical disk drive, a CD- RW drive, a CD-ROM drive, or other similar type of storage medium.
- the application program 130 can also be configured to be executed from the media storage module 132.
- the meta database module 134 is also configured to communicate with the communications module 100, and to store digital image data on a temporary or permanent basis.
- the meta database module 134 can include a storage medium such as a conventional database for storing digital data.
- FIG. 2 illustrates a generalized data flow diagram of an exemplary embodiment of the present invention.
- This Figure illustrates an exemplary embodiment of the data flow 200 through multiple layers of the DICOM protocol during transmission of an object or image file between a network and an application.
- the network is represented by the network level 202
- the application is represented by the application level 204.
- the network level 202 can include a DICOM network 102 with a server 128a-n.
- the application level 204 can include an associated application program 101 such as a medical imaging program associated with the communications module 100.
- the application level can include an application program 130 executing on another server 128a-n, i.e.
- the communications module 100 facilitates data communication between an associated application program 101 and the server 128a-n by creating an association or connection between the associated application program 101 and the server 128a-n.
- the communications module 100 then handles standard DICOM network protocol details such as determining which Service Object Pair (SOP) classes will be used, defining the roles of the SCP and SCU, negotiating the type of transfer syntax used to communicate between protocol layers, and determining other communication parameters according to a DICOM network protocol or similar type of protocol for handling objects or digital images.
- SOP Service Object Pair
- other devices may be function as a SCP, SCU, or may function as both a SCP and SCU.
- the communications module 100 can be used to transmit or stream digital data between two devices, such as memory storage devices, hard drives, CDR, CD-RW, or any other combinations of two different memory storage devices. Those skilled in the art will realize that the communications module 100 can also be used to transmit digital data between other configurations such as between a network-to- device, or device-to-network, wherein the device can include memory storage devices, hard drives, CD-R, CD-RW, or any other similar types of devices.
- the communications module 100 negotiates with the associated application program 101 and the server 128a-n to define a maximum size of protocol data unit (PDU) that will be transmitted between the associated application program 101 and server 128a-n.
- the maximum size of the PDU can depend upon the current size of the memory storage available and the overall performance of the communication network.
- the communications module 100 can negotiate to define a predefined or limited number of presentation data values (PDVs) that can be read into a presentation data value input stream.
- the predefined or limited number of presentation data values (PDVs) can depend upon the current size of the memory storage available and/or the overall performance of the communication network.
- the communications module 100 can negotiate to define a predefined or limited size of data elements that can be read into a data input stream. The predefined or limited size of data elements can depend upon the current size of the memory storage available and/or the overall performance of the communication network.
- a presentation data value includes a header and a payload that can be an array of bytes.
- the communications module 100 proceeds to transmit data 206 from the network level 202 to the application level 204. That is, the communications module 100 processes data 206 received from the server 128a-n (acting as a SCP in this example) and sends the processed data to the associated application program 101 (acting as a SCU in this example).
- data 206 is a DICOM object or DICOM image file that includes one or more data elements.
- the data 206 is first handled by at the network level 202 by the server 128a-n.
- the server 128a-n transmits the data 206 through a standard network physical layer 208 such as ETHERNET, ATM, FDDI, etc.
- the data 206 is transmitted from the standard network physical layer through TCP/IP 210 in the form of one or more data packets 212.
- TCP/IP 210 converts the data 206 including the DICOM object or DICOM image file into one or more data packets 212. Those skilled in the art will recognize the methods and systems needed to perform this conversion.
- the TCP/IP 210 transmits the data packets 212 to a DICOM protocol layer 214 using sockets 216.
- the DICOM protocol layer 214 contains multiple layers including Transport 218, Upper Level Service 220, Data Service 222, and Service Class 224.
- Sockets 216 is an application program interface (API) that facilitates communication between TCP/IP 210 and other network protocols such as the DICOM network protocol.
- API application program interface
- TCP/IP 210 transmits the data packets 212 to the first layer of the DICOM protocol layer 214, known as the Transport layer 216.
- the communications module 100 receives the data packets 212 in the Transport layer 216, and incrementally reads each of the data packets 212 from TCP/IP 210. That is, a communications engine (shown in FIG. 1 as 104) associated with the communications module 100 reads the data packets 212 one at a time using the Transport layer 216.
- the communications engine 104 converts the data packets 208 to protocol data units 226.
- Protocol data units (PDUs) 226 can include a header 228 and one or more presentation data values (PDVs) 230.
- Each PDU 226 is then passed from the Transport layer 218 to the Upper Level Service layer 220 by the communications engine 104.
- the PDU can then be transmitted to the Data Service layer 222.
- the communications engine 104 then extracts the presentation data values (PDVs) 230 from each PDU 226 received by the Data Service layer 222. Generally, the communications engine 104 creates a Presentation Data Value Input Stream (PDVIS) 232 from the PDVs 230. The communications engine 104 forms a message 234 using the PDVIS 232.
- PDVs presentation data values
- PDVIS Presentation Data Value Input Stream
- the communications engine 104 transmits the message 234 containing the PDVIS 232 to the Service Class layer 224.
- a data element source 236 extracts the data elements from the Presentation Data Value Input Stream (PDVIS) 232 from each message.
- the data element source 236 becomes the new input transfer syntax (ITS) 238 that can be used to parse the data contained in the PDVIS 232.
- ITS new input transfer syntax
- the input transfer syntax 238 extracts data elements 240 from the input stream of bytes and utilizes the data elements 240 as needed by the associated application program 101.
- the input transfer syntax 238 has an attribute called a streaming threshold. If the extracted data element is longer than the streaming threshold, then the data element 240 will be a streaming data element.
- the streaming data element is a proxy for the actual data element 240 which is still present in the input transfer syntax 238.
- the streaming data element allows incremental access to its value using the input transfer syntax 238. The incremental access is provided by a block of data which the streaming data element fills.
- a data element source 236 is first moved through the Service class 224.
- the data element source 236 then passes to the Data Service 222.
- a packetizer 244 takes the data element source 236 and creates an output transfer syntax 238.
- the output transfer syntax 238 processes each of the data elements from the data element source 236, and passes the encoded data elements to the packetizer 244.
- the packetizer 244 then takes the encoded data elements and creates a presentation data value (PDV).
- PDV presentation data value
- the PDV When PDV is created, the PDV is passed to the DICOM state machire 246 to be processed. The PDV is then handed to the Transport level 218 by the DICOM state machine 246. The Transport level 218 writes out the PDV to the TCP/IP layer 210 via an output stream of bytes 248 which is the network connection.
- a DICOM object sent from the network level to the application level can be approximately 600 megabytes (MB) in size of which approximately 599 MB may be pixel data (PD) elements.
- a maximum protocol data unit (PDU) size is negotiated during the association or connection, for a maximum size of approximately 20 kilobytes (KB).
- the association or coimection can define the maximum number of presentation data values (PDVs) in the presentation data value input stream (PDVIS) as a predefined limit, i.e. a maximum number of five (5).
- the predefined limit can be selected depending upon the size of a buffer or memory storage device used to store presentation data values (PDVs). If the PDVIS limits the number of PDVs to five (5), the maximum amount of memory required to read the DICOM object from the network is (5 X 20 KB) + 20 KB, or 120KB. The "+ 20 KB" accounts for the PDUs waiting to be placed in the PDVIS.
- the application program will then write the incoming DICOM object to a file, passing the input transfer syntax (ITS) as a data element source to the output transfer syntax (OTS) for the file.
- ITS input transfer syntax
- OTS output transfer syntax
- the OTS will use approximately 10KB to encode the pixel data elements. All other data elements can be encoded individually as a whole, except for sequence data (SQ) elements. Since all other data elements are normally relatively smaller than 10 KB, the maximum amount of memory used to decode the data elements to file should be 10 KB.
- FIGs. 3-6 illustrate flowchart diagrams of exemplary embodiments of methods utilized by the present invention.
- FIGs. 3a-c and FIGs. 4a-b depict network operations such as reading from and writing to a network
- FIGs. 5 and 6 show file operations such as reading from and writing to a file. Utilization of the methods shown in FIGs. 3-6 permit handling of all possible DICOM data interactions using only a relatively small, fixed amount of memory.
- FIGs. 3a-c depict a method 300 for reading digital data from a network to an application.
- the digital data is a DICOM object or image file
- the network is a DICOM communications network
- the application is a medical imaging application program capable of communicating using a DICOM network protocol.
- the method 300 begins at 302.
- a communications engine 104 negotiates the size of protocol data units (PDUs). Establishing the size of PDUs permits the communications engine 104 to monitor the amount of memory in the buffer 112 needed or desired to process the digital data. Furthermore, a predefined number, limit, or size of presentation data values (PDVs) or another type of data element or quality can also be established by the communications engine 104 depending upon the amount of memory storage in the buffer 112 needed or desired to process the digital data. Typically, these steps are executed in conjunction with the establishment of an association or connection between a Service Control Provider (SCP) and a Service Control Unit (SCU) by the state machine 110.
- SCP Service Control Provider
- SCU Service Control Unit
- the communications engine 104 incrementally reads digital data from a network.
- the communications engine 104 requests digital data such as a DICOM image file from a server 128a-n in a DICOM network 102.
- the DICOM image file can include one or more sets of digital image data.
- the server 128a-n transmits the digital image data sets to the communications engine 104 through TCP/IP 126 via sockets, an application program interface.
- the communications engine 104 receives the digital image data sets in the form of DICOM packets or protocol data units (PDUs) from the server 128a-n.
- PDUs protocol data units
- protocol data units and DICOM packets are defined under the DICOM network protocol previously described above.
- 306 is followed by 308, in which the communications engine 104 incrementally reads each PDU or DICOM packet. That is, the communications engine 104 initiates a read thread (not shown) through the Transport layer 116 of the DICOM protocol 114. The read thread incrementally reads and transmits each of the PDUs or DICOM packets, one at a time, across the Transport layer 116 of the DICOM protocol 114. The read thread continues processing the PDUs or DICOM packets until all of the PDUs or DICOM packets of the digital data to be transmitted from the network have been handled.
- the communications engine 104 transmits the PDUs to the Upper Level Service layer 118.
- the PDUs arrive at the appropriate time during the association or connection, the PDUs are then transmitted to the Data Service layer 120 by the communications engine 104.
- Each protocol data unit includes one or more presentation data values.
- subroutine 312 is followed by subroutine 314, in which a presentation data value input stream is created for an operation message.
- Subroutine 314 is described in greater detail with reference to FIG. 3c.
- subroutine 314 begins at 350.
- the communications engine 104 creates a presentation data value input stream using presentation data values.
- extracted presentation data values (PDVs) received by the communications engine 104 are used to create a presentation data value input stream (PDVIS).
- PDVIS presentation data value input stream
- the extracted PDVs can be inserted into an existing presentation data value input stream or a new presentation data value input stream is created when needed.
- a presentation data value input stream is essentially a string of presentation data values (PDVs) from one or more PDUs that can be transmitted using a relatively small, fixed amount of memory.
- the presentation data value input stream (PDVIS) forms the basis of an operation message.
- the communications engine 104 continues to transmit each extracted PDV incrementally or one at a time to the Data Service layer 120.
- the Data Service Layer 120 inserts each PDV in a presentation data value input stream (PDVIS) as described above .
- PDVIS can be limited to storing a predefined or limited number of PDVs at any given instant of time. Typically, the PDVIS is limited to storing five (5) PDVs at a time. Note that the predefined or limited number can be set according to the size of a buffer or other memory storage device to store the PDVs and/or PDVIS.
- decision block 352 in which the Data Service layer determines whether the predefined or limited number of PDVs has been reached. In this manner, the transmission of image data can be controlled incrementally to minimize the amount of memory storage space needed to process all of the image data.
- the data element source 106 processes PDVs incrementally or one at a time, and transmits each PDV to the PDVIS. If a predefined or limited number of PDVs is reached, then the "YES" branch is followed to 354. For example, if the predefined or limited number of PDVs is previously set to five (5), and there is already the predefined or limited number of PDVs in a particular PDVIS, then the limit has been reached.
- the invention can monitor and limit the use of memory to a relatively small, fixed amount of memory that can be used for the transmission of digital data such as DICOM data.
- a predefined or limited size may be set depending upon the size of the buffer 112 or memory storage device.
- pixel data (PD) elements and relatively larger DICOM objects may be handled in relatively small, fixed size portions of data.
- the communications engine 104 delays further processing of presentation data values until a presentation data value can be read from the presentation data value input stream.
- the communications engine 104 instructs the Data Service layer 120 to wait until a presentation data value (PDV) is read from the presentation data value input stream (PDVIS). That is, the communications engine 104 sends a command to the Data Service layer 120 that temporarily prevents the Transport layer 116 from reading any further PDVs to the PDVIS, until a PDV is read from the PDVIS.
- the communications engine 104 instructs the Data Service layer 120 to permit the Transport layer 116 to continue to pass PDVs to the PDVIS until the predefined or limited number of PDVs is reached.
- decision block 352 if a predefined or limited number of PDVs is not reached, then the "NO" branch is followed, in which the subroutine 314 ends and the method 300 continues at 316.
- the Message Service determines which operation the operation message corresponds to. Typically, once an operation message is created by the communications engine 104 in subroutine 314, the communications engine 104 sends the operation message including the PDVs and PDVIS to a Message Service (not shown).
- the Message Service is a component of the Data Service Layer 120 of the DICOM protocol 114.
- an operation is defined by a Service Object Pair (SOP).
- SOP Service Object Pair
- the Message Service determines whether a message has a matching or corresponding operation.
- 316 is followed by 318, in which the Message Service transmits the operation message to the corresponding operation.
- the Message Service transmits the operation message to the corresponding operation.
- 318 is followed by 320, in which the operation message is queued by the corresponding operation for subsequent processing.
- the method 300 continues at 320 in FIG. 3c.
- 320 is followed by 322, in which the queued messages are processed by each respective operation. All of the operations that receive at least one queued operation message will initiate a thread. For each operation, each thread then processes each queued operation message one at a time. Each queued operation message is then passed to the corresponding Service that the operation message was created for. Note that each operation has a corresponding Service or SOP, as defined by the DICOM network protocol. Each thread continues to process each operation message until each queued message for each respective operation has been processed.
- 322 is followed by 324, in which the Service extracts data elements from the presentation data value input stream (PDVIS).
- 324 is followed by 326, in which the Service creates a new Input Transfer Syntax (ITS).
- the Service utilizes the presentation data value input stream (PDVIS) to create a new ITS that can be used to parse the data contained in the PDVIS.
- the data contained in the PDVIS will be a series of presentation data values (PDVs).
- the data values are encoded, and the input transfer syntax can be used to convert the coding to a representation that can be understood as a standard memory representation for the data elements.
- the parsed data can then be streamed by the communications engine 104 to a data element source 106.
- Each Service utilizes the data element source 106 to read one block of data elements at a time from the data stream contained in the presentation data value input stream (PDVIS).
- the input transfer syntax (ITS) can also be utilized to incrementally read the data elements through the data element source 106.
- At least two types of data elements can be handled by the Service at the data element source 106: sequence data (SQ) and pixel data (PD).
- SQ data element can be a data element that contains one or more sets of data elements. SQ data elements can be processed recursively. That is, a set of data elements can be processed one data element at a time.
- the PD element is one of the largest data elements in a DICOM object or image file.
- the PD elements can be composed of a raw data array of bytes (8-bit) or words (16-bit). This type of data element allows additional layers of streaming.
- the Service can obtain pixel data incrementally, thus minimizing the need to obtain all of the PD values in memory at a single instance of time.
- pixel data (PD) elements and other DICOM objects can be relatively large.
- the invention allows pixel data (PD) elements and DICOM objects of all sizes to be handled in relatively small portions over time.
- FIGs. 4a-b illustrate a second exemplary method of the present invention.
- FIGs. 4a-b describe a method 400 for writing data from an application to a network or to another application.
- the data is a DICOM object or image file
- the network is a DICOM communications network
- the application is a medical imaging application program capable of communicating using a DICOM network protocol.
- the method 400 begins.
- a data set can be one or more data sets, each data set comprising one or more data elements.
- the data set for a DICOM object or image can be stored in an associated memory device such as a media storage module 132 or meta database module 134.
- OTS output transfer syntax
- ITS input transfer syntax
- DES data element source
- 406 is followed by 408, in which the Service creates a governed data set input stream (GDSIS).
- the Service uses the output transfer syntax, the Service creates a governed data set input stream (GDSIS).
- GDSIS governed data set input stream
- a GDSIS can then convert a data set or data element source to a data stream such as a byte stream using the output transfer syntax.
- the GDSIS can convert the data set or data element source to a data stream using only a relatively small, fixed amount of memory.
- the output transfer syntax takes each data element one at a time from the data set or data element source and encodes each data element into a series of data elements or a data stream.
- At least two different types of data elements can be processed by the output transfer syntax: sequence data (SQ) elements and pixel data (PD) elements.
- SQ elements SQ elements contain sets of data elements.
- OTS output transfer syntax
- the OTS recursively processes one data element at a time from one particular set of data elements.
- PD elements contain a large array of bytes or words.
- OTS output transfer syntax
- the OTS processes these as chunks or small, fixed sizes of data elements.
- pixel data (PD) elements and other DICOM objects can be relatively large.
- the invention allows pixel data (PD) elements and other DICOM objects of all sizes to be handled in relatively small portions over time.
- 410 is followed by 412, in which the Service sends the message to a Message Service.
- 414 is followed by 416, in which the Message Service determines the corresponding operation for the message.
- 416 is followed by 418, in which the Message Service passes the message to the Data Service layer 120.
- the Data Service layer 120 decodes the governed data set input stream from the message.
- the Data Service layer 120 receives the message from the Message Service.
- the Message Service extracts the governed data set input stream (GDSIS) from the message and reads bytes from the GDSIS.
- the Message Service continues to read bytes from the GDSIS until the Message Service can construct a protocol data unit (PDU).
- PDU protocol data unit
- 420 is followed by 422, in which the Message Service sends a protocol data unit (PDU) to the Transport layer 116.
- PDU protocol data unit
- the Message Service can send the PDU through the Upper Service Level layer 118 to the Transport layer 116.
- 422 is followed by 424, in which the Transport layer 116 transmits the protocol data unit to a receiving application.
- the Transport layer 116 transmits the protocol data unit (PDU) through the TCP/IP layer 126, and then through the DICOM network 102 to the application program 130.
- PDU protocol data unit
- decision block 426 in which the Message Service determines whether all of the data elements have been converted to a byte stream by the data element source 106. If all of the data elements have been converted, then the "YES" branch is followed to 428.
- FIG. 5 illustrates a third exemplary method of the present invention.
- FIG. 5 describes a method 500 for reading data from a file.
- the data is a DICOM object or image file
- the file can be associated with an associated application program 101 or application program 130 such as a medical imaging program capable of communicating using a DICOM protocol.
- the file may be previously stored on a storage device or system such as a server 128a-n operating in conjunction with a communications network such as DICOM network 102, or a media storage module 132, or meta database module 134 as described previously.
- the method500 begins at 502.
- a file input stream can be an input stream of bytes.
- an associated application program 101 can permit a user to select a command to read a file containing a DICOM object or image file.
- the associated application program 101 then creates a file input stream for the DICOM object or image file to be read in a system containing the DICOM object or image file.
- the file input stream is a forward iterator over a portion of bytes or data elements in a file.
- the file input sfream can be read from the beginning to the end in a single direction.
- the system can be a server 128a-n, media storage module 132, or meta database module 134 as defined previously.
- 504 is followed by 506, in which the communications engine 104 creates an input transfer syntax (ITS) to read the image file.
- ITS input transfer syntax
- the communications engine 104 creates an input transfer syntax (ITS) using the previously created file input stream.
- the input transfer syntax can then be used to read data elements from the corresponding object or image file.
- the data element source 106 incrementally reads each data element from the file input stream.
- the data element source 106 utilizes the input transfer syntax (ITS) to incrementally read one data element or one block of data elements at a time from the file input sfream.
- ITS input transfer syntax
- At least two different types of data elements can be processed: sequence data (SQ) elements and pixel data (PD) elements.
- SQ elements SQ elements contain sets of data elements.
- ITS input transfer syntax
- the ITS recursively processes one data element at a time from one particular set of data elements.
- PD elements contain a large array of bytes or words.
- the ITS processes these as chunks or small, fixed sizes of data elements. In any case, only a relatively small, fixed size of memory is used by the ITS to process the data elements. 508 is followed by 510, in which the communications engine 104 closes the input transfer syntax (ITS). That is, after all of the data elements have been read by the data element source, the communications engine closes the input transfer syntax is closed and no further processing of the data elements is performed by the data element source 106.
- ITS input transfer syntax
- FIG. 6 illustrates a fourth exemplary method of the present invention.
- FIG. 6 describes a method 600 for writing data to a file.
- the data is a DICOM object or image file
- the file can be associated with an application such as a medical imaging program capable of communicating using a DICOM protocol.
- the file may be previously stored on a storage device or system such as a server operating in conjunction with a network such as DICOM communications network.
- the method 600 begins at 602.
- a file output stream can be a output stream of bytes.
- an associated application program 101 can permit a user to select a command to write image data to a file configured for storing a DICOM object or image.
- the application program 130 then creates a file output stream for the image data to be written to a system containing the DICOM object or image file.
- the system can be a serverl28a- n, media storage module 132, or meta database module 134 as defined previously.
- 604 is followed by 606, in which the application program 130 creates an output transfer syntax (OTS) to write the image data to the object or image file.
- OTS output transfer syntax
- the associated application program 101 or application program 130 creates an output transfer syntax (OTS) using the previously created file output stream.
- OTS output transfer syntax
- the file output stream is one argument used to create the output transfer syntax.
- the OTS can then be used to write the image data to the corresponding object or image file.
- a data element sink 108 incrementally writes each data element to the file output stream. That is, the data element sinkl08 utilizes the output transfer syntax (OTS) to incrementally write one data element or one block of data elements at a time to the file output sfream.
- OTS output transfer syntax
- SQ sequence data
- PD pixel data
- SQ elements contain sets of data elements.
- OTS output transfer syntax
- the OTS recursively processes one data element at a time from one particular set of data elements.
- PD elements contain a large array of bytes or words.
- OTS processes these as chunks or small, fixed sizes of data elements. In any case, only a relatively small, fixed size of memory is used by the output transfer syntax (OTS) to process the data elements.
- OTS output transfer syntax
- FIG. 7 shows a representative illustration of data contained in a DICOM image file.
- This particular example is a magnetic resonance image (MRI) DICOM image file 700.
- the first 794 bytes are used for a DICOM format header 702.
- the format header 702 describes the image dimensions and retains other text information about the scan.
- the size of this header 702 varies depending upon how much header information is stored.
- the example shows the dimensions of the image as 109x91x2 pixels, with a resolution of 1 byte per pixel, thus the total image size will be approximately 19,838 bytes.
- Image data 704 is stored in the file portion following the header 702. The image data is also stored in the same file as the header 702 and associated information.
- FIG. 8 illustrates data contained in a DICOM image file.
- the DICOM header format requires a 128-byte preamble.
- the 128-byte preamble is usually set to zero.
- the 128-byte preamble is then followed by the letters "D", "I", "C”, and "M”. Header information then follows the last letter "M”.
- the header information can be organized into one or more portions called "groups". For example, a group "0002hex" can designate the file meta information group. This group can define three elements such as group length, file version, and transfer syntax.
- the DICOM data elements defined in each group depends upon the image type. A representative sample of data elements that can be defined is listed in Part 3 of the 2000 DICOM standard. For example, a magnetic resonance (MR) image file can be designated by element 0008,0060. This type of image file can include one or more elements to describe MRI echo time.
- MR magnetic resonance
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002526106A JP2004523931A (en) | 2000-09-02 | 2001-09-04 | Method and apparatus for streaming DICOM images through a source and a receiver of a data element |
AU2002238152A AU2002238152A1 (en) | 2000-09-02 | 2001-09-04 | Methods and apparatus for streaming dicom images through data element sources and sinks |
EP01984616A EP1338129B1 (en) | 2000-09-02 | 2001-09-04 | Method and communication module for transmission of dicom objects through data element sources |
DE60124946T DE60124946T2 (en) | 2000-09-02 | 2001-09-04 | METHOD AND COMMUNICATION MODULE FOR TRANSFERRING DICOM OBJECTS THROUGH DATA ELEMENT SOURCES |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US22956200P | 2000-09-02 | 2000-09-02 | |
US60/229,562 | 2000-09-02 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2002021822A2 true WO2002021822A2 (en) | 2002-03-14 |
WO2002021822A3 WO2002021822A3 (en) | 2002-09-19 |
Family
ID=22861770
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/027465 WO2002021822A2 (en) | 2000-09-02 | 2001-09-04 | Methods and apparatus for streaming dicom images through data element sources and sinks |
Country Status (7)
Country | Link |
---|---|
US (1) | US7426567B2 (en) |
EP (1) | EP1338129B1 (en) |
JP (2) | JP2004523931A (en) |
AT (1) | ATE347225T1 (en) |
AU (1) | AU2002238152A1 (en) |
DE (1) | DE60124946T2 (en) |
WO (1) | WO2002021822A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113489718A (en) * | 2021-07-02 | 2021-10-08 | 哈尔滨工业大学(威海) | Method for generating image by recombining transmission flow of DICOM (digital imaging and communications in medicine) protocol |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020091659A1 (en) * | 2000-09-12 | 2002-07-11 | Beaulieu Christopher F. | Portable viewing of medical images using handheld computers |
DE10141834A1 (en) * | 2001-08-27 | 2003-04-03 | Siemens Ag | data converter |
DE10211950B4 (en) * | 2002-03-18 | 2006-01-26 | Siemens Ag | A medical planning facility that can be subdivided into a planning medical system and a medical planable medical system |
US6733449B1 (en) * | 2003-03-20 | 2004-05-11 | Siemens Medical Solutions Usa, Inc. | System and method for real-time streaming of ultrasound data to a diagnostic medical ultrasound streaming application |
US8292811B2 (en) * | 2003-03-20 | 2012-10-23 | Siemens Medical Solutions Usa, Inc. | Advanced application framework system and method for use with a diagnostic medical ultrasound streaming application |
US6932767B2 (en) * | 2003-03-20 | 2005-08-23 | Siemens Medical Solutions Usa, Inc. | Diagnostic medical ultrasound system having a pipes and filters architecture |
AU2003902423A0 (en) * | 2003-05-19 | 2003-06-05 | Intellirad Solutions Pty. Ltd | Apparatus and method |
EP1629396A2 (en) * | 2003-06-04 | 2006-03-01 | The Trustees of The University of Pennsylvania | Ndma socket transport protocol |
US20050075537A1 (en) * | 2003-10-06 | 2005-04-07 | Eastman Kodak Company | Method and system for real-time automatic abnormality detection for in vivo images |
US7664299B2 (en) * | 2004-04-02 | 2010-02-16 | Kabushiki Kaisha Toshiba | Apparatus that prepares information relating to image data |
DE102004036488A1 (en) * | 2004-07-28 | 2006-03-23 | Siemens Ag | Method, apparatus and system for the adaptive optimization of transport protocols in the transmission of images |
US9535912B2 (en) * | 2006-09-15 | 2017-01-03 | Oracle International Corporation | Techniques for checking whether a complex digital object conforms to a standard |
JP2009022626A (en) * | 2007-07-23 | 2009-02-05 | Ge Medical Systems Global Technology Co Llc | Ultrasonic imager and image diagnostic system |
US8229191B2 (en) * | 2008-03-05 | 2012-07-24 | International Business Machines Corporation | Systems and methods for metadata embedding in streaming medical data |
DE102008022570B4 (en) * | 2008-05-07 | 2014-05-28 | Siemens Aktiengesellschaft | Method for exporting image data in a medical image information system |
FR2931570B1 (en) * | 2008-05-26 | 2010-07-30 | Etiam Sa | METHODS FOR CONVERTING MEDICAL DOCUMENTS, DEVICES AND CORRESPONDING COMPUTER PROGRAMS |
JP5106359B2 (en) * | 2008-11-21 | 2012-12-26 | 株式会社富士通アドバンストエンジニアリング | Computer program, data capturing apparatus, data capturing method, and data management system |
US8520920B2 (en) * | 2009-11-11 | 2013-08-27 | Siemens Corporation | System for dynamically improving medical image acquisition quality |
US8775205B2 (en) * | 2010-06-29 | 2014-07-08 | True North Consulting & Associates Inc. | Imaging device information system and method |
US9449380B2 (en) * | 2012-03-20 | 2016-09-20 | Siemens Medical Solutions Usa, Inc. | Medical image quality monitoring and improvement system |
CN107181794B (en) * | 2017-04-27 | 2020-11-17 | 广州慧扬健康科技有限公司 | DICOM network transmission method based on DIMSE message sending and receiving |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0876033A1 (en) * | 1997-04-25 | 1998-11-04 | Philips Patentverwaltung GmbH | Transmission system with data streams synchronization |
EP0964559A1 (en) * | 1998-06-08 | 1999-12-15 | THOMSON multimedia | Method for transmitting asynchronous data in a home network |
Family Cites Families (125)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4835532A (en) * | 1982-07-30 | 1989-05-30 | Honeywell Inc. | Nonaliasing real-time spatial transform image processing system |
US4663591A (en) * | 1985-08-16 | 1987-05-05 | General Electric Company | Method for reducing image artifacts due to periodic signal variations in NMR imaging |
US4817050A (en) * | 1985-11-22 | 1989-03-28 | Kabushiki Kaisha Toshiba | Database system |
DE3722075A1 (en) | 1986-07-02 | 1988-03-17 | Toshiba Kawasaki Kk | Image diagnostics system |
US4833625A (en) * | 1986-07-09 | 1989-05-23 | University Of Arizona | Image viewing station for picture archiving and communications systems (PACS) |
US5119444A (en) * | 1986-07-22 | 1992-06-02 | Schlumberger Technologies, Inc. | System for expedited computation of laplacian and gaussian filters and correlation of their outputs for image processing |
DE3823259C2 (en) * | 1987-07-08 | 1994-09-01 | Toshiba Kawasaki Kk | Device for archiving and transmitting medical image data |
US5384900A (en) * | 1988-03-14 | 1995-01-24 | Canon Kabushiki Kaisha | Method of managing an image memory by a process independent of an image processing process |
FI83329C (en) * | 1988-03-31 | 1991-06-25 | Neste Oy | Process for preparing a supported polymerization catalyst and apparatus for use in the process |
US5016193A (en) * | 1988-04-07 | 1991-05-14 | General Electric Company | Pixel and line enhancement method and apparatus |
US5117351A (en) * | 1988-10-21 | 1992-05-26 | Digital Equipment Corporation | Object identifier generator for distributed computer system |
US5025396A (en) * | 1989-03-21 | 1991-06-18 | International Business Machines Corporation | Method and apparatus for merging a digitized image with an alphanumeric character string |
JP2690782B2 (en) * | 1989-05-30 | 1997-12-17 | 富士写真フイルム株式会社 | Image filing system |
US5150427A (en) * | 1989-09-29 | 1992-09-22 | General Electric Company | Three dimensional disarticulation |
US5241472A (en) * | 1990-10-15 | 1993-08-31 | University Of Pittsburgh Of The Commonwealth System Of Higher Education | Method of identifying and archiving medical images |
US5319777A (en) * | 1990-10-16 | 1994-06-07 | Sinper Corporation | System and method for storing and retrieving information from a multidimensional array |
US5581460A (en) | 1990-11-06 | 1996-12-03 | Kabushiki Kaisha Toshiba | Medical diagnostic report forming apparatus capable of attaching image data on report |
NL9002593A (en) | 1990-11-28 | 1992-06-16 | Koninkl Philips Electronics Nv | IMAGE STORAGE DEVICE AND IMAGE PROCESSING DEVICE EQUIPPED WITH IMAGE STORAGE DEVICE. |
US5233299A (en) * | 1991-03-25 | 1993-08-03 | General Electric Company | Projection methods for producing two-dimensional images from three-dimensional data |
US5313567A (en) * | 1991-06-13 | 1994-05-17 | At&T Bell Laboratories | Arrangement for determining and displaying volumetric data in an imaging system |
GB2257595B (en) * | 1991-07-11 | 1995-08-09 | Matsushita Electric Ind Co Ltd | An image processing system |
JP3228972B2 (en) | 1991-10-31 | 2001-11-12 | 株式会社東芝 | Medical image storage communication system |
US5235418A (en) * | 1991-11-19 | 1993-08-10 | Scientific-Atlanta, Inc. | Method and apparatus for low frequency removal in vector quantization |
US5415167A (en) * | 1992-01-10 | 1995-05-16 | Wilk; Peter J. | Medical system and associated method for automatic diagnosis and treatment |
US5321776A (en) * | 1992-02-26 | 1994-06-14 | General Electric Company | Data compression system including successive approximation quantizer |
US5408659A (en) * | 1992-03-05 | 1995-04-18 | International Business Machines Corporation | Link pane class and application framework |
US5359724A (en) | 1992-03-30 | 1994-10-25 | Arbor Software Corporation | Method and apparatus for storing and retrieving multi-dimensional data in computer memory |
US5276735A (en) * | 1992-04-17 | 1994-01-04 | Secure Computing Corporation | Data enclave and trusted path system |
US5261012A (en) | 1992-05-11 | 1993-11-09 | General Electric Company | Method and system for thinning images |
US5384862A (en) * | 1992-05-29 | 1995-01-24 | Cimpiter Corporation | Radiographic image evaluation apparatus and method |
US5289577A (en) * | 1992-06-04 | 1994-02-22 | International Business Machines Incorporated | Process-pipeline architecture for image/video processing |
US5347384A (en) * | 1992-06-30 | 1994-09-13 | Loral Aerospace Corp. | Fiber optic distribution of image data |
US5331552A (en) * | 1992-07-14 | 1994-07-19 | General Electric Company | Method and apparatus for projecting diagnostic images from non-isotropic volumed diagnostic data |
US5321520A (en) * | 1992-07-20 | 1994-06-14 | Automated Medical Access Corporation | Automated high definition/resolution image storage, retrieval and transmission system |
WO1994005112A1 (en) * | 1992-08-25 | 1994-03-03 | Bell Communications Research, Inc. | System and method for creating, transferring, and monitoring services in a telecommunication system |
JP3428046B2 (en) * | 1992-11-02 | 2003-07-22 | 富士通株式会社 | Data acquisition control device |
GB9224076D0 (en) * | 1992-11-17 | 1993-01-06 | Ibm | Communication in a computer network |
US5339433A (en) * | 1992-11-19 | 1994-08-16 | Borland International, Inc. | Symbol browsing in an object-oriented development system |
US5583656A (en) | 1992-12-31 | 1996-12-10 | Eastman Kodak Company | Methods and apparatus for attaching compressed look-up table (LUT) representations of N to M-dimensional transforms to image data and for processing image data utilizing the attached compressed LUTs |
US5884016A (en) * | 1993-01-11 | 1999-03-16 | Sun Microsystems, Inc. | System and method for displaying a selected region of a multi-dimensional data object |
US5544302A (en) * | 1993-06-03 | 1996-08-06 | Taligent, Inc. | Object-oriented framework for creating and using container objects with built-in properties |
US5557542A (en) * | 1993-08-13 | 1996-09-17 | Kabushiki Kaisha Toshiba | Image storage apparatus |
US5485507A (en) * | 1993-08-20 | 1996-01-16 | Gateway Technologies, Inc. | Integrated commissary system |
US5542003A (en) * | 1993-09-13 | 1996-07-30 | Eastman Kodak | Method for maximizing fidelity and dynamic range for a region of interest within digitized medical image display |
US5452287A (en) * | 1993-09-20 | 1995-09-19 | Motorola, Inc. | Method of negotiation of protocols, classes, and options in computer and communication networks providing mixed packet, frame, cell, and circuit services |
CA2117846C (en) * | 1993-10-20 | 2001-02-20 | Allen Reiter | Computer method and storage structure for storing and accessing multidimensional data |
US5469353A (en) * | 1993-11-26 | 1995-11-21 | Access Radiology Corp. | Radiological image interpretation apparatus and method |
US5666522A (en) * | 1994-01-28 | 1997-09-09 | Micron Electronics, Inc. | Variable speed controller |
US5737549A (en) * | 1994-01-31 | 1998-04-07 | Ecole Polytechnique Federale De Lausanne | Method and apparatus for a parallel data storage and processing server |
CN1152365A (en) | 1994-06-06 | 1997-06-18 | 诺基亚电信公司 | Method for storing and retrieving data and memory arrangement |
CA2156141A1 (en) * | 1994-09-28 | 1996-03-29 | Kaveh Azar | Interactive scanning device or system |
AU3415595A (en) | 1994-10-04 | 1996-04-26 | Banctec, Inc. | An object-oriented computer environment and related method |
US5838906A (en) | 1994-10-17 | 1998-11-17 | The Regents Of The University Of California | Distributed hypermedia method for automatically invoking external application providing interaction and display of embedded objects within a hypermedia document |
US5782762A (en) * | 1994-10-27 | 1998-07-21 | Wake Forest University | Method and system for producing interactive, three-dimensional renderings of selected body organs having hollow lumens to enable simulated movement through the lumen |
US5592666A (en) * | 1994-10-31 | 1997-01-07 | Sinper Corporation | Method and system for storing and retrieving data from a multidimensional array using database pointers |
US5537630A (en) * | 1994-12-05 | 1996-07-16 | International Business Machines Corporation | Method and system for specifying method parameters in a visual programming system |
US5740428A (en) * | 1995-02-07 | 1998-04-14 | Merge Technologies, Inc. | Computer based multimedia medical database management system and user interface |
JPH08223548A (en) | 1995-02-17 | 1996-08-30 | Hitachi Ltd | Digital audio image data distribution method and its distribution system |
US5835735A (en) * | 1995-03-03 | 1998-11-10 | Eastman Kodak Company | Method for negotiating software compatibility |
US5668998A (en) * | 1995-04-26 | 1997-09-16 | Eastman Kodak Company | Application framework of objects for the provision of DICOM services |
US5619571A (en) * | 1995-06-01 | 1997-04-08 | Sandstrom; Brent B. | Method for securely storing electronic records |
US5944659A (en) * | 1995-11-13 | 1999-08-31 | Vitalcom Inc. | Architecture for TDMA medical telemetry system |
US5966463A (en) | 1995-11-13 | 1999-10-12 | Meta Holding Corporation | Dataform readers using interactive storage and analysis of image data |
US5845018A (en) | 1996-01-30 | 1998-12-01 | Sunrise Imaging, Inc. | Method and apparatus for transferring multiple scanned images from a first medium to a second medium |
US5671353A (en) * | 1996-02-16 | 1997-09-23 | Eastman Kodak Company | Method for validating a digital imaging communication standard message |
JPH09233335A (en) * | 1996-02-20 | 1997-09-05 | Mita Ind Co Ltd | Image data processor and image data processing method |
US5851186A (en) | 1996-02-27 | 1998-12-22 | Atl Ultrasound, Inc. | Ultrasonic diagnostic imaging system with universal access to diagnostic information and images |
US5603323A (en) * | 1996-02-27 | 1997-02-18 | Advanced Technology Laboratories, Inc. | Medical ultrasonic diagnostic system with upgradeable transducer probes and other features |
JPH09270897A (en) * | 1996-04-02 | 1997-10-14 | Canon Inc | Image reader |
US5923789A (en) * | 1996-08-07 | 1999-07-13 | General Electric Company | Band limited interpolation and projection of spatial 3-D images |
JP3688822B2 (en) * | 1996-09-03 | 2005-08-31 | 株式会社東芝 | Electronic medical record system |
US5986662A (en) | 1996-10-16 | 1999-11-16 | Vital Images, Inc. | Advanced diagnostic viewer employing automated protocol selection for volume-rendered imaging |
US6115486A (en) | 1996-11-06 | 2000-09-05 | Quinton Instrument Company | Teleradiology system for the storage and transmission of angiographic and related image sequences |
JPH10145583A (en) * | 1996-11-14 | 1998-05-29 | Casio Comput Co Ltd | Image processor |
US5883985A (en) * | 1996-12-10 | 1999-03-16 | General Electric Company | Method for compensating image data to adjust for characteristics of a network output device |
US5751783A (en) * | 1996-12-20 | 1998-05-12 | General Electric Company | Detector for automatic exposure control on an x-ray imaging system |
US6137527A (en) | 1996-12-23 | 2000-10-24 | General Electric Company | System and method for prompt-radiology image screening service via satellite |
JP3193947B2 (en) * | 1997-01-08 | 2001-07-30 | 株式会社ディジタル・ビジョン・ラボラトリーズ | Data transmission system and data transmission method |
US6157929A (en) | 1997-04-15 | 2000-12-05 | Avid Technology, Inc. | System apparatus and method for managing the use and storage of digital information |
US5943668A (en) | 1997-06-30 | 1999-08-24 | International Business Machines Corporation | Relational emulation of a multi-dimensional database |
US6008813A (en) * | 1997-08-01 | 1999-12-28 | Mitsubishi Electric Information Technology Center America, Inc. (Ita) | Real-time PC based volume rendering system |
US6108697A (en) * | 1997-10-06 | 2000-08-22 | Powerquest Corporation | One-to-many disk imaging transfer over a network |
US6047081A (en) * | 1997-10-24 | 2000-04-04 | Imation Corp. | Image processing software system having configurable communication pipelines |
CA2333583C (en) * | 1997-11-24 | 2005-11-08 | Everette C. Burdette | Real time brachytherapy spatial registration and visualization system |
US5918232A (en) * | 1997-11-26 | 1999-06-29 | Whitelight Systems, Inc. | Multidimensional domain modeling method and system |
IL122361A0 (en) * | 1997-11-29 | 1998-04-05 | Algotec Systems Ltd | Image compression method |
US6171244B1 (en) * | 1997-12-31 | 2001-01-09 | Acuson Corporation | Ultrasonic system and method for storing data |
US5971923A (en) | 1997-12-31 | 1999-10-26 | Acuson Corporation | Ultrasound system and method for interfacing with peripherals |
US6262749B1 (en) * | 1997-12-31 | 2001-07-17 | Acuson Corporation | Ultrasonic system and method for data transfer, storage and/or processing |
US6047324A (en) * | 1998-02-05 | 2000-04-04 | Merrill Lynch & Co. Inc. | Scalable distributed network controller |
US6003036A (en) | 1998-02-12 | 1999-12-14 | Martin; Michael W. | Interval-partitioning method for multidimensional data |
US6101407A (en) * | 1998-02-13 | 2000-08-08 | Eastman Kodak Company | Method and system for remotely viewing and configuring output from a medical imaging device |
US6204853B1 (en) * | 1998-04-09 | 2001-03-20 | General Electric Company | 4D KAPPA5 Gaussian noise reduction |
US6014671A (en) * | 1998-04-14 | 2000-01-11 | International Business Machines Corporation | Interactive retrieval and caching of multi-dimensional data using view elements |
US6731798B1 (en) * | 1998-04-30 | 2004-05-04 | General Electric Company | Method for converting digital image pixel values including remote services provided over a network |
JPH11341496A (en) * | 1998-05-28 | 1999-12-10 | Matsushita Electric Ind Co Ltd | Image processing method, image processing unit and data storage medium |
US6055000A (en) * | 1998-05-28 | 2000-04-25 | Snk Corporation | Storage memory for images |
US6260021B1 (en) * | 1998-06-12 | 2001-07-10 | Philips Electronics North America Corporation | Computer-based medical image distribution system and method |
JP4328397B2 (en) * | 1998-07-03 | 2009-09-09 | 富士通株式会社 | Image data processing method and apparatus, and storage medium |
US6587641B1 (en) * | 1998-07-21 | 2003-07-01 | Matsushita Electric Industrial Co., Ltd. | Apparatus for simultaneously writing and outputting data stream |
US6141398A (en) | 1998-08-25 | 2000-10-31 | General Electric Company | Protocol driven image reconstruction, display, and processing in a multislice imaging system |
US6195093B1 (en) * | 1998-09-14 | 2001-02-27 | Fuji Xerox Co., Ltd. | Systems and method for controlling a presentation using physical objects |
US6198283B1 (en) * | 1998-09-18 | 2001-03-06 | Ge Medical Systems Global Technology Llc | System and method of phase sensitive MRI reconstruction using partial k-space data and including a network |
US6954802B2 (en) * | 1998-09-29 | 2005-10-11 | Tdk Electronics Corporation | Removable media recording station for the medical industry |
US6266733B1 (en) * | 1998-11-12 | 2001-07-24 | Terarecon, Inc | Two-level mini-block storage system for volume data sets |
US6042545A (en) * | 1998-11-25 | 2000-03-28 | Acuson Corporation | Medical diagnostic ultrasound system and method for transform ultrasound processing |
US6272469B1 (en) * | 1998-11-25 | 2001-08-07 | Ge Medical Systems Global Technology Company, Llc | Imaging system protocol handling method and apparatus |
US6603494B1 (en) * | 1998-11-25 | 2003-08-05 | Ge Medical Systems Global Technology Company, Llc | Multiple modality interface for imaging systems including remote services over a network |
US6434572B2 (en) * | 1998-11-25 | 2002-08-13 | Ge Medical Technology Services, Inc. | Medical diagnostic system management method and apparatus |
US6137856A (en) | 1998-12-14 | 2000-10-24 | General Electric Company | Generic architectures for backprojection algorithm |
US6215903B1 (en) * | 1998-12-31 | 2001-04-10 | General Electric Company | Compression method and apparatus |
US6224551B1 (en) * | 1998-12-31 | 2001-05-01 | General Electric Company | Ultrasound image data archiving and communication techniques |
US6157337A (en) | 1999-01-29 | 2000-12-05 | Sony Corporation | 3D image acquiring and viewing systems and methods |
US7028182B1 (en) * | 1999-02-19 | 2006-04-11 | Nexsys Electronics, Inc. | Secure network system and method for transfer of medical information |
US6210327B1 (en) * | 1999-04-28 | 2001-04-03 | General Electric Company | Method and apparatus for sending ultrasound image data to remotely located device |
US6117079A (en) | 1999-04-28 | 2000-09-12 | General Electric Company | Method and apparatus for handling image data after unsuccessful transfer to remotely located device |
US6178225B1 (en) * | 1999-06-04 | 2001-01-23 | Edge Medical Devices Ltd. | System and method for management of X-ray imaging facilities |
US6243441B1 (en) * | 1999-07-13 | 2001-06-05 | Edge Medical Devices | Active matrix detector for X-ray imaging |
US6213945B1 (en) * | 1999-08-18 | 2001-04-10 | Acuson Corporation | Ultrasound system and method for generating a graphical vascular report |
US6287258B1 (en) * | 1999-10-06 | 2001-09-11 | Acuson Corporation | Method and apparatus for medical ultrasound flash suppression |
US6912317B1 (en) * | 1999-11-24 | 2005-06-28 | General Electric Company | Medical image data compression employing image descriptive information for optimal compression |
US6584461B1 (en) * | 1999-12-28 | 2003-06-24 | General Electric Company | Default operator preference processing for a picture archiving and communication system |
US6836558B2 (en) * | 2000-03-28 | 2004-12-28 | Arch Development Corporation | Method, system and computer readable medium for identifying chest radiographs using image mapping and template matching techniques |
AU2001253563A1 (en) * | 2000-04-18 | 2001-10-30 | Rtimage Inc. | System and method for the lossless progressive streaming of images over a communication network |
US6775346B2 (en) * | 2002-10-21 | 2004-08-10 | Koninklijke Philips Electronics N.V. | Conebeam computed tomography imaging |
-
2001
- 2001-09-04 JP JP2002526106A patent/JP2004523931A/en not_active Withdrawn
- 2001-09-04 AT AT01984616T patent/ATE347225T1/en not_active IP Right Cessation
- 2001-09-04 US US09/947,055 patent/US7426567B2/en not_active Expired - Lifetime
- 2001-09-04 AU AU2002238152A patent/AU2002238152A1/en not_active Abandoned
- 2001-09-04 DE DE60124946T patent/DE60124946T2/en not_active Revoked
- 2001-09-04 EP EP01984616A patent/EP1338129B1/en not_active Revoked
- 2001-09-04 WO PCT/US2001/027465 patent/WO2002021822A2/en active IP Right Grant
-
2008
- 2008-03-13 JP JP2008064423A patent/JP2008178140A/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0876033A1 (en) * | 1997-04-25 | 1998-11-04 | Philips Patentverwaltung GmbH | Transmission system with data streams synchronization |
EP0964559A1 (en) * | 1998-06-08 | 1999-12-15 | THOMSON multimedia | Method for transmitting asynchronous data in a home network |
Non-Patent Citations (5)
Title |
---|
LIU J C L ET AL: "FLEXIBLE STORAGE PLACEMENT OF DIGITAL VIDEO MEDIA" PROCEEDINGS OF INFOCOM '95 - CONFERENCE ON COMPUTER COMMUNICATIONS. FOURTEENTH ANNUAL JOINT CONFERENCE OF THE IEEE COMPUTER AND COMMUNICATIONS SOCIETIES, BOSTON APR. 2 - 6, 1995, LOS ALAMITOS, IEEE COMP. SOC. PRESS, US, vol. 2 CONF. 14, 2 April 1995 (1995-04-02), pages 788-795, XP000580649 ISBN: 0-7803-2524-9 * |
NEGISHI Y ET AL: "A portable communication system for video-on-demand applications using the existing infrastructure" PROCEEDINGS OF IEEE INFOCOM 1996. CONFERENCE ON COMPUTER COMMUNICATIONS. FIFTEENTH ANNUAL JOINT CONFERENCE OF THE IEEE COMPUTER AND COMMUNICATIONS SOCIETIES. NETWORKING THE NEXT GENERATION. SAN FRANCISCO, MAR. 24 - 28, 1996, PROCEEDINGS OF INFOCOM, L, vol. 2 CONF. 15, 24 March 1996 (1996-03-24), pages 18-26, XP010158050 ISBN: 0-8186-7293-5 * |
NEMA: "DICOM Part 5: Data Structures and encoding"" NATIONAL ELECTRICAL MANUFACTURER ASSOCIATION, [Online] 20 August 1999 (1999-08-20), pages i-80, XP002203932 Retrieved from the Internet: <URL:ftp://medical.nema.org/medical/Dicom/ 1999/draft/99_05DR.PDF> [retrieved on 2002-06-28] * |
NEMA: "DICOM Part 8: Network Communication Support for Message Exchange" NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION, [Online] 20 August 1999 (1999-08-20), pages i-57, XP002203931 Retrieved from the Internet: <URL:ftp://medical.nema.org/medical/Dicom/ 1999/draft/99_08DR.PDF> [retrieved on 2002-06-28] * |
See also references of EP1338129A2 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113489718A (en) * | 2021-07-02 | 2021-10-08 | 哈尔滨工业大学(威海) | Method for generating image by recombining transmission flow of DICOM (digital imaging and communications in medicine) protocol |
CN113489718B (en) * | 2021-07-02 | 2023-04-07 | 哈尔滨工业大学(威海) | Method for generating image by recombining transmission flow of DICOM (digital imaging and communications in medicine) protocol |
Also Published As
Publication number | Publication date |
---|---|
AU2002238152A1 (en) | 2002-03-22 |
US20030149680A9 (en) | 2003-08-07 |
DE60124946T2 (en) | 2007-05-31 |
EP1338129A2 (en) | 2003-08-27 |
US7426567B2 (en) | 2008-09-16 |
US20020052866A1 (en) | 2002-05-02 |
ATE347225T1 (en) | 2006-12-15 |
WO2002021822A3 (en) | 2002-09-19 |
DE60124946D1 (en) | 2007-01-11 |
JP2008178140A (en) | 2008-07-31 |
EP1338129B1 (en) | 2006-11-29 |
JP2004523931A (en) | 2004-08-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7426567B2 (en) | Methods and apparatus for streaming DICOM images through data element sources and sinks | |
EP1335561B1 (en) | Method for document viewing | |
US6981045B1 (en) | System for redirecting requests for data to servers having sufficient processing power to transcast streams of data in a desired format | |
US7339993B1 (en) | Methods for transforming streaming video data | |
US7114174B1 (en) | Computer program product for transforming streaming video data | |
US7716345B2 (en) | Client to server streaming of multimedia content using HTTP | |
US7143432B1 (en) | System for transforming streaming video data | |
EP1297676B1 (en) | Methods and apparatuses for transferring data | |
US6961754B2 (en) | Interactive access, manipulation, sharing and exchange of multimedia data | |
JP5081868B2 (en) | Method and apparatus for media data transmission | |
US6457054B1 (en) | System for reducing user-visibility latency in network transactions | |
US7373418B2 (en) | Wire protocol for a media server system | |
EP2786265B1 (en) | Improved bandwidth optimization for remote desktop protocol | |
EP3654607A1 (en) | Data transmission method, device, server and storage medium | |
EP3269110B1 (en) | Method of communicating data packets within data communication systems | |
US8145001B2 (en) | Methods and systems for proxy medical image compression and transmission | |
WO2007044562A1 (en) | Media data processing using distinct elements for streaming and control processes | |
US6466987B2 (en) | Wire protocol for a media server system | |
US20050187960A1 (en) | Stream server | |
JP2002540504A (en) | Method of file transmission in data communication network | |
US20040073953A1 (en) | Audio/video apparatus for use with a cable television network | |
US20030210711A1 (en) | Data transfer method and apparatus | |
US20070220432A1 (en) | Isochronous Audio Network Software Interface | |
CA2385344A1 (en) | Data transfer method and apparatus | |
US20020039149A1 (en) | System and method for streaming video over a network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002526106 Country of ref document: JP |
|
ENP | Entry into the national phase |
Ref document number: 2003108528 Country of ref document: RU Kind code of ref document: A Format of ref document f/p: F |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2001984616 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 2001984616 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 2001984616 Country of ref document: EP |