a dicom mechanism for multicast streaming rafael mayoral, adrián vÁzquez, stefan bohn, oliver...
TRANSCRIPT
A DICOM mechanismfor multicast streaming
Rafael MAYORAL, Adrián VÁZQUEZ, Stefan BOHN, Oliver BURGERT
Innovation Center Computer Assisted Surgery, University of Leipzig
2
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Outline
Motivation Isolated systems Goal
Continuous data transmission Modeling the system A general framework DICOM implementation Our first implementation
Conclusion
3
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Motivation: Isolated systems
App App
Display Display
App
Display
Patient
4
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Goal
Operating Room of the future
More integration Easy sharing of sensors/actuators/modalities Improve workflow Combine data into a single data space Support the concept of Patient Model Create advanced functionalities
5
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Goal
Communication infrastructure
Sensors/Actuators/Modalities
Patient
Workstation
App App AppDisplay
Display
App
6
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Goal
Communication infrastructure
Sensors/Actuators/Modalities
Patient
Workstation
App App AppDisplay
Display
App
Similar to PACS Several heterogeneous devices Communication infrastructure
7
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Continuous data transmission
Communication infrastructure
Sensors/Actuators/Modalities
Patient
Workstation
App App AppDisplay
Display
App
But …
Continuous data transmission
8
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Modeling the system
Use case:get continuous data
9
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Modeling the system
Client/Server Device description Use functionalities Two interfaces: Management and Data Access
10
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
A general framework
Describe devices and use functionalities
Source n description
General data information
…
Source 2 description
Source 1 description
Specific Attributes
Type
Serial Number
Manufacturer
Name
Common attributes
Device Description
Start/stop receiving data
Generate/send status reports
Interpret status reports
Manage the data sourcesSubscribe/unsubscribe to a specific data source
Maintain/serve the device description
Request device description
Accept/reject connectionsInitiate/Terminate connection
ServerClient
Description
Services
11
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
DICOM implementation
Describe devices and use functionalities
Source n description
General data information
…
Source 2 description
Source 1 description
Specific Attributes
Type
Serial Number
Manufacturer
Name
Common attributes
Device Description
Start/stop receiving data
Generate/send status reports
Interpret status reports
Manage the data sourcesSubscribe/unsubscribe to a specific data source
Maintain/serve the device description
Request device description
Accept/reject connectionsInitiate/Terminate connection
ServerClient
DICOM IOD
DIMSE Services
12
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
DICOM implementation
DIMSE ServicesDICOM IOD
Data-specific protocol
Possibly several different communication technologies
13
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
DICOM implementation
Why DICOM? At every point of the process the data will be within
the PACS logical domain The data becomes an integrated part of the patient’s
files Tight integration with the other hospital areas
These concepts already present in DICOM Use of appropriate external protocols
Referenced pixel data transfer syntax Use of the JPEG 2000 Interactive Protocol (JPIP)
Describe devices & use DIMSE N-Services to perform operations Print Management Service Media Creation Management Service
14
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
DICOM implementation
DIMSE services implement required services
Generate/send status reports
Interpret status reports
Manage the data sources
Subscribe/unsubscribe to a specific data source
Maintain/serve the device description
Request device description
Accept/reject connections
Initiate/terminate connection
ServerClient
A-ASSOCIATE
N-GET
N-ACTION
N-EVENT-REPORT
15
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
DICOM implementation
DICOM IOD describes the devices Devices modeled as IODs Composed of different modules Modules may be reused
Source n description
General data information
…
Source 2 description
Source 1 description
Specific Attributes
Type
Serial Number
Manufacturer
Name
Common attributes
Device Description
Describes key configuration characteristics of a tracking device as a streaming source
X.XX.XTracking Streaming Device Configuration Module
Contains general information relevant to all types of streaming devices
X.XX.XStreaming Device Common Module
Contains SOP Common informationC.12.1SOP Common
Module DescriptionReferenceModule
16
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Our first implementation
What are we working on?
Communication infrastructure
Navigation application
Endoscope
Tracking
Ultrasound
17
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Our first implementation
What are we working on?
Communication infrastructure
Navigation application
Endoscope
Tracking
Ultrasound
Data streaming using RTP over an Ethernet network
18
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Our first implementation
DICOM IOD: Example
Attribute Name Attribute Description
Streaming Device Name User defined name identifying the device.
Manufacturer Manufacturer of the device.
…
Tracking Device Type Type of tracking device. Enumerated:OPTICAL, IR, MAGNETIC
Stream source sequence
> Stream Source ID
…
> Streaming protocol Enumerated:RTP
> Coding Enumerated:ICCASTRACKPROTOCOL
> Pixel Data Provider URL Location where to find the data
Common attributes
Specific device class attributes
19
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Our first implementation
DICOM IOD: Example
Attribute Name Attribute Description
Streaming Device Name User defined name identifying the device.
Manufacturer Manufacturer of the device.
…
Tracking Device Type Type of tracking device. Enumerated:OPTICAL, IR, MAGNETIC
Stream source sequence
> Stream Source ID
…
> Streaming protocol Enumerated:RTP
> Coding Enumerated:ICCASTRACKPROTOCOL
> Pixel Data Provider URL Location where to find the data
Common attributes
Specific device class attributes
20
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Our first implementation
What’s next? Integrate dedicated video distribution infrastructure
How to model the video router? How to model the video sources? What technologies?
Thorough analysis with increasingly complex scenarios
21
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Conclusion
Continuous data transmission is a critical feature of the Operating Room of the future
An appropriate architecture needs to deal with data and requirements that are heterogeneous
DICOM possesses the mechanisms to accommodate transmission of heterogeneous continuous data
We have created an experimental implementation using DICOM and RTP for streaming
Future work will include handling additional data types with different requirements
DICOM INTERNATIONAL CONFERENCE & SEMINARApril 8-10, 2008 Chengdu, China
Acknowledgement
The Innovation Center Computer Assisted Surgery (ICCAS) at the Faculty of Medicine at the University of Leipzig is funded by the German Federal Ministry for Education and Research (BMBF) and the Saxon Ministry of Science and the Fine Arts (SMWK) in the scope of the initiative “Unternehmen Region” with the grant numbers 03 ZIK 031 and 03 ZIK 032.
Thank you