TubeTK/OpenIGTLink

Introduction

OpenIGTLink is a communication protocol designed to work on the TCP/IP application layer to handle image, tracking data, transform, device control and monitoring command, and other user-defined data types. Example use cases

1. Interfacing a tracking device: A computer running IGSTK based navigation application and a computer running Slicer are connected using a network cable. The IGSTK application gathers pose information of surgical instruments and packages them in OpenIGTLink message format and then sends the data over the network connection using OpenIGTLink protocol to the computer running Slicer for visualization and/or further processing
2. Integration with a commercial navigation system: A computer running tubetk based vessel segmentation application is connected to a BrainLab VectorVision machine using a network cable. VectorVisison fetches Ultrasound images, packages them as OpenIGTLink image message and sends them to the computer running the tubetk application.

Description

OpenIGTLink is designed for use in the application layer on the TCP/IP stack. A message, the minimum data unit of OpenIGTLInk protocol contains all the information necessary for interpretation by the receiver. The message begins with a 58-byte header section that contains protocol version, message type, device name, time stamp, body size and cyclic redundancy check. The body section varies according to the message type being sent.

Typical Workflow

Client

1. Establish connection with server side
2. Generate OpenIGTLink message (data-to-be-sent ) and package in Open IGT Link format.
3. Send data through TCP/IP socket connection

Server side

1. Create a server socket and wait for the client to connect
2. When connection is established with a client, get into a "Ready" state to start receiving messages.
3. When a message is received, error check and unpack the header and identify the message type and prepare to receive the message body
4. Receive, error check, unpack and parse the message body according to the message type.

Versions

There are two versions of the protocol available.

Version 1

Message types

1. Transform
2. Image
3. Position
4. Status message

Version 2

In addition to the above message types, Version 2 provides a simple querying scheme.

1. Client can request the server side to send a data contained in a single message
2. Client can start and stop data streaming from the server

Implementation

Surgical Navigation and Robotics Lab at BWH has developed a C++ library implementation of this protocol. The library is composed of

1. C-based library defining structures and utility functions to serialize data into OpenIGTLinkMessage
2. A set of high-level C++ classes wrapping the C-based library that provide a safer and more convenient way to implement OpenIGTLink messaging function into software
3. Multi-platform C++ classes to handle sockets and threads.

Version 1 http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink

Version 2 http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink2_beta/

Reference

1. NAMIC OpenIGTLink wiki page
2. Internet socket
3. Socket Programming C++
4. TCP/IP Introduction
5. BSD socket
6. CTK effort