Enabling The Effective Sharing of Medical Images over Wide Area and Wireless Networks

PRESENTER AND AGENDA

PRESENTER

Daniel Kumi

Director, New Market Development daniel@asperasoft.com

• Who and Why Aspera?

• WAN & Wireless Transport

• Transfers to/out of the Cloud

• Healthcare Applications

• PACS to PACS

• Health Information Exchange

• On-Demand Access

• Possible Integrations—Hopkins,

McKesson, Vital, WU School of medicine

• Aspera-Intel Discussion

AGENDA

ASPERA’S MISSION

Creating next-generation transport technologies

that move the world’s digital assets at maximum speed,

regardless of file size, transfer distance and network conditions.

Aspera: moving the world’s digital assets at maximum speed

Expanded to Asia PAC and Latin America through direct and channel

50% YOY growth in revenue and employees

Over 10,000 licenses sold, and over 1,500 customers world wide

Patents issued or pending in 32 countries

Continuing to innovate: fasp3™, fasp-MC™, mobile transport, cloud enablement

Aspera Ecosystem of Partners

Life SciencesLife Sciences

BIG DATA TRANSFER CHALLENGE

What Happened to my Bandwidth?

1000 Mbps• 170ms RTT• 0.001% packet loss rate Paris

Seattle

WAN Throughput is 1000Mbps

Max TCP Throughput ~29Mbps

Where’s my 970Mbps?

At 29Mbps50GB transfer will take 4 hrs1TB transfer will take 3.3 days

WAN

BIG-DATA and WAN TRANSFER WITH TCP

TCP WAS DESIGNED IN THE EARLY 80’S

• When data was small & bandwidth was limited

• Fantastic for reliable data delivery

• Not fast enough for big-data

TCP IS THE ENGINE THAT DRIVES

• FTP, HTTP & HTTPS

• RSYNC, SCP & DICOM

• CIFS & NFS

TCP DOES NOT LIKE NETWORK LATENCY/ RTT

• Geographic distance increases latency

• Network congestion increases latency

TCP DOES NOT LIKE PACKET LOSS

• Loss is caused by congestion

• Different network capacity

• Wireless and satellite communications

The Aspera Solution

So if TCP doesn’t work, what’s the answer?

WAN is 1000Mbps

Max TCP Throughput ~29Mbps

Max Aspera Throughput ~995Mbps (gain of x34)

ROI measured in $$ cost of not using 971Mbps

Same WAN Scenario with Aspera

1000 Mbps• 170ms RTT• 0.001% packet loss rate ParisSeattle

WAN

At 995 Mbps

• 50GB transfer will take ~4 hrs

• 50GB transfer will take ~7 mins• 1TB transfer will take 3.3 days

• 1TB transfer will take 2.4 hrs

FASP™ — HIGH-PERFORMANCE DATA TRANSPORT

MAXIMUM LINE-RATE WAN TRANSFER SPEED

• Transfer performance scales with bandwidth independent of transfer distance and resilient to packet loss

• Optimal end-to-end throughput efficiency

CONGESTION AVOIDANCE AND POLICY CONTROL

• Automatic, full utilization of available bandwidth

• On-the-fly prioritization and bandwidth allocation

UNCOMPROMISING SECURITY AND RELIABILITY

• Secure, user/endpoint authentication

• AES-128 cryptography in transit & at-rest

SCALABLE MANAGEMENT, MONITORING AND CONTROL

• Real-time progress, performance and bandwidth utilization

• Detailed transfer history, logging, and manifest

ENTERPRISE-CLASS FILE DELIVERY

• Transfers up to thousands of times faster than FTP/HTTP(S)

• Precise and predictable transfer times

• Extreme scalability (concurrency and throughput)

fasp Bandwidth ROI

FTP Across US US – EU US – ASIA Satellite

1 GB 1 – 2 hrs 2 – 4 hrs 4 – 20 hrs 8 – 20 hrs

10 GB 15 – 20 hrs 20 – 40 hrs Impractical Impractical

100 GB Impractical Impractical Impractical Impractical

fasp™ 2 Mbps 10 Mbps 45 Mbps 100 Mbps 200 Mbps 1 Gbps

1 GB 70 min. 14 min. 3.2 min. 1.4 min. 42 sec. 8.4 sec.

10 GB 11.7 hrs 140 min. 32 min. 14 min. 7 min. 1.4 min.

100 GB 23.3 hrs 5.3 hrs 2.3 hrs 1.2 hrs 14 min.

FTP: Limited by Distance & Packet Loss, Not B/W

Aspera: Scales Linearly with Bandwidth

Distance & Packet Loss Independent

FASP vs TCP PERFORMANCE

6 Gbps Scalable WAN Throughput

~6Gbps Big-Data Throughput• Latency independent

• Loss independent

x3000 improvement vs. TCP• 1TB data moved in 20 min

• 2 days with TCP over LAN conditions

Scale to ~10Gbps with IQ Accelerator

High Speed Mobile Data Transfer with fasp-AIR™

fasp-AIR SDK – maximum data transfer speed and predictability for

mobile devices

• Embeddable software library allows app developers to integrate superior

transport capabilities to their own applications such as faster and more

predictable downloads/uploads.

• Available for Android and iOS on Aspera Developer Network

• Designed for wireless networks with high latency, high packet loss environments

• Integrated transfer queuing, pause, resume and progress reporting

• Achieves significant performance improvements for upload and download

speeds over 3G, 4G and 802.11 g/n.

fasp-AIR Benchmarks on Verizon 4G

In some cases (highlighted in orange), speeds will vary

greatly, depending on available bandwidth and the underlying

condition of the wireless network.

GETTING IN AND OUT OF THE CLOUDKNOWING WHEN TO CHOSE THE RIGHT TOOL

FIRST MAJOR BOTTLENECKS: WAN TRANSFER

SECOND MAJOR BOTTLENECKS: LOCAL HTTP I/O

2nd Bottleneck — Data Center

1st Bottleneck - WAN

CHALLENGES OF STORING BIG FILES IN THE CLOUD?

BEWARE THE OBJECT STORE:• Not like traditional NAS or SAN

• Bigger, better, but possibly much more complex

• a.k.a. Google File System, Amazon S3, Hadoop Distributed File System

• Simple read/write of data “blobs”, indexed by a key

• Multiple replicas are distributed across storage for durability and optimized for access

• Should work well for storing large numbers of files

UNDERSTAND CHUNKS, BLOCKS and BLOBS• You need to deal with chunks, blocks and blobs

• “Chunk” sizes are small (64 MB/128 MB)

• Large media files must be “chunked” (1TB file = transporting and reassembling 10,000+ chunks!)

• Multi-chunk APIs impede workflow and are complex

• Data I/O use the standard HTTP(s) protocol

• VERY SLOW at distance

• Single HTTP stream slow even locally (<100 Mbps).

M&E/ BIG-DATA SERVICES WILL NEED A HIGH-SPEED BRIDGE TO THE CLOUD• Large files moved at full bandwidth capacity with global access

• Overcome the WAN and storage bottleneck

• Support files of any size or quantity

• Transparent to the end user/data owner (GUI, command line, API, browser, etc.)

• No hardware to support B2B, B2C, C2B workflow

S3 & BIG-DATA: UNDERSTAND THE CONTRAINTS

S3 & BIG-DATA: MEET ASPERA’s DIRECT-TO-S3

client cargo downloader

mobile apps

connect plug-in

point-to-point

ASPERA DIRECT-TO-S3 — LINE RATE ACCESS TO THE CLOUD

UNRIVALED ASPERA PERFORMANCE

• Built on Aspera fasp™ technology for maximum transfer speed

• Regardless of file size, transfer distance and network conditions

• Precise bandwidth control ensures the available bandwidth is utilized to achieve maximum transfer speeds, while

being fair to other business-critical network traffic

SEAMLESS INTEGRATION WITH S3

• Integrated with S3 multi-part HTTP for maximum “last foot” performance

• Simple configuration of S3 credentials, for both shared and dedicated docroot

• Transfers directly into S3 are seamless and transparent to user

ENTERPRISE-GRADE SECURITY AND RELIABILITY

• Secure authentication with encryption in transit & at rest (AES-128, FIPS 140-2, HIPPA Compliant)

• Packet-level data integrity verification

• Automatic resume of partial or failed transfers

• Full support for AWS S3 Service-side-encryption at rest

INTEROPERATES WITH ALL ASPERA HOST OPTIONS

• Any platform (Windows, Linux, MAC, UNIX, iOS, Android)

• Any Aspera Clients (CLI, Desktop, Point-to-Point, Mobile, Web, Embedded)

• Any Aspera Servers (Enterprise, Connect, faspex)

Aspera fasp™ software environment

ASPERA DEVELOPER NETWORK

A complete set of SDKs provides developers with guides, reference information, and sample code to assist them with integrating Aspera technology into their own applications. Aspera fasp™ technology can be used in desktop, network-based, and web applications in place of FTP, HTTP, or custom TCP-based copy protocols.

ASPERA MOBILE APIs

Android SDKAspera Android SDK provides a Java API to transfer files using

fasp-AIR™.

iPhone SDKAspera iPhone SDK provides an Objective C API to transfer files

using fasp-AIR.

ASPERA APPLICATION APIs

faspex™ Web APIThe Aspera faspex Web API provides a set of services that enables

users to create and receive digital deliveries via a Web interface, while

taking advantage of fasp high-speed transfer technology.

OTHER INFORMATION

Supporting Tools and LibrariesSupporting tools and libraries let you perform other common tasks

surrounding file transfers.

General ReferenceReference on error codes, log file locations, configuration files

and more.

ASPERA TRANSFER APIs

Aspera Web ServicesA SOAP based web service API that allows initiation,

monitoring and controlling of fasp based file transfers.

Aspera WebJavascript API exposed by Aspera Connect client. It allows

integration of fasp based file transfers into web

applications.

Connect 2.8 developer Preview 2Introducing the new Connect 2.8 developer preview!

Integrate the functionality of Aspera Connect 2.8, a fasp-

based file transfer client, into your own web applications,

while customizing it to your unique brand.

fasp ManagerA class library that allows intiations, monitoring and

controlling of fasp based file transfers.

Aspera Multicast SDKA Java class library that allows initiation and management

of IP multicast based data transmissions using Aspera

fasp-MC™.

BIG-DATA: ACCESSED & DELIVERED BY ASPERA

Media File transfer

HEALTHCARE APPLICATIONS

High-Speed Transfers Between DICOM Devises: Example: Archive-to-Archive Transfers (fasp3 socket-based solution)

DICOMPACS, Archive…

Socket

Usual DICOM(TCP)

fasp3

DICOMPACS, Archive…

Socket

Usual DICOM(TCP)

fasp3Regular sockets selected by fasp

Regular sockets selected by fasp

Sender Receiver

Aspera Fasp Sockets Overview

TCP

FASP3

TCP

FASP-Pipe Proxy Client

ApplicationData Source

WAN

Java

C/C++

.NET

Socket

FASPFASP3

FASP-Pipe Proxy Server

WebSocketServer

Java.NET

C/C++SocketHTML 5WS DataSSE Data

Client Application

TCP

Stream

MessageFASP

FASP

FASP

Stream

Message

Use Case : On-Demand Access to Medical Images

Image Access Over Wireless or WAN links

• Doctors will download medical images on demand

• Images are kept ONLY in memory (compliance to regulations)

• Aspera server would interface to WADO server to pull DICOM images using http/https requests to

WADO server.

• Option for Direct Access to Images Using fasp

Use Case : Server-Side Rendering & Remote Viewing of Medical Images Over WAN and Wireless Networks

• Server side rendering, and delivery of rendered images to Viewing applications.

• Thin Client

• Thick Client

Use Case : Health Information Exchange

• Drop in Replacement of HTTP with fasp for XDS-I

POSSIBLE INTEGRATIONS

Possible Integration

• Peake Healthcare --Joint Venture Between Johns Hopkins and Harris Corporation

• McKesson

• Vital (MINT Use case)

• Washington University School of Medicine

ASPERA-INTEL DISCUSSION

THANK YOU!

Daniel KumiDirector, New Market Development

daniel@asperasoft.com

FOR MORE INFORMATION ON ANY ASPERA PRODUCT, PLEASE CONTACT:

sales@asperasoft.com