Transcript A DICOM mechanism for multicast streaming

A DICOM mechanism
for multicast streaming
Rafael MAYORAL, Adrián VÁZQUEZ, Stefan BOHN,
Oliver BURGERT
Innovation Center Computer Assisted Surgery,
University of Leipzig
2
Outline
 Motivation
 Isolated systems
 Goal
 Continuous data transmission




Modeling the system
A general framework
DICOM implementation
Our first implementation
 Conclusion
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
Motivation: Isolated systems
Display
3
Display
App
App
Patient
App
Display
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
4
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
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
5
Goal
Patient
Sensors/Actuators/Modalities
Communication infrastructure
Workstation
Display
App
App
App
App
Display
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
6
Goal
Patient
Sensors/Actuators/Modalities
Communication infrastructure
Workstation
Display
App
Display
App
App
App
 Similar to PACS
 Several heterogeneous devices
 Communication infrastructure
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
7
Continuous data transmission
Patient
Sensors/Actuators/Modalities
Communication infrastructure
Workstation
Display
App
Display
App
App
App
But …
Continuous data transmission
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
Modeling the system
8
 Use case:
get continuous data
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
Modeling the system




9
Client/Server
Device description
Use functionalities
Two interfaces: Management and Data Access
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
10
A general framework
 Describe devices and use functionalities
Device Description
Common attributes
Name
Client
Server
Manufacturer
Initiate/Terminate
connection
Accept/reject connections
Serial Number
Request device description
Maintain/serve the device
description
Subscribe/unsubscribe to a
specific data source
Manage the data sources
Specific Attributes
General data information
Interpret status reports
Generate/send status
reports
Type
Source 1 description
Source 2 description
Start/stop receiving data
…
Source n description
Services
Description
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
11
DICOM implementation
 Describe devices and use functionalities
Device Description
Common attributes
Name
Client
Server
Manufacturer
Initiate/Terminate
connection
Accept/reject connections
Serial Number
Request device description
Maintain/serve the device
description
Manage the data sources
Specific Attributes
Subscribe/unsubscribe to a
specific data source
General data information
Interpret status reports
Generate/send status
reports
Type
Source 1 description
Source 2 description
Start/stop receiving data
…
Source n description
DIMSE Services
DICOM IOD
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
12
DICOM implementation
DIMSE Services
DICOM IOD
Data-specific
protocol
Possibly several different communication technologies
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
13
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
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
14
DICOM implementation
 DIMSE services implement required services
Client
Initiate/terminate connection
Request device description
Subscribe/unsubscribe to a
specific data source
Interpret status reports
Server
Accept/reject
connections
A-ASSOCIATE
Maintain/serve the
device description
N-GET
Manage the data
sources
N-ACTION
N-EVENT-REPORT
Generate/send status
reports
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
15
DICOM implementation
 DICOM IOD describes the devices
 Devices modeled as IODs
 Composed of different modules
 Modules may be reused
Device Description
Common attributes
Name
Manufacturer
Module
Reference
Module Description
SOP
Common
C.12.1
Contains SOP Common information
Streaming
Device
Common
Module
X.XX.X
Contains general information relevant to
all types of streaming devices
Tracking
Streaming
Device
Configuration
Module
X.XX.X
Serial Number
Type
Specific Attributes
General data information
Describes key configuration
characteristics of a tracking device as a
streaming source
Source 1 description
Source 2 description
…
Source n description
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
16
Our first implementation
 What are we working on?
Endoscope
Navigation
application
Tracking
Communication infrastructure
Ultrasound
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
17
Our first implementation
 What are we working on?
Endoscope
Navigation
application
Tracking
Communication infrastructure
Ultrasound
Data streaming using RTP over an
Ethernet network
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
18
Our first implementation
 DICOM IOD: Example
Attribute Name
Common
attributes
Attribute Description
Streaming Device Name
User defined name identifying the device.
Manufacturer
Manufacturer of the device.
…
Tracking Device Type
Specific
device class
attributes
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
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
19
Our first implementation
 DICOM IOD: Example
Attribute Name
Common
attributes
Attribute Description
Streaming Device Name
User defined name identifying the device.
Manufacturer
Manufacturer of the device.
…
Tracking Device Type
Specific
device class
attributes
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
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
Our first implementation
20
 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
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China
Conclusion
21
 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 & SEMINAR
April 8-10, 2008 Chengdu, China
Thank you
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.
DICOM INTERNATIONAL CONFERENCE & SEMINAR
April 8-10, 2008 Chengdu, China