Intel aspera-medical-v1


Published on

Aspera Slide Deck for Intel

Published in: Technology
  • Be the first to comment

Intel aspera-medical-v1

  1. 1. Enabling The Effective Sharing ofMedical Images over Wide Area andWireless Networks
  2. 2. PRESENTER AND AGENDAPRESENTER AGENDADaniel KumiDirector, New Market Development • 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
  3. 3. 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.
  4. 4. Aspera: moving the world’s digital assets at maximum speed 50% YOY growth in revenue and employees Over 10,000 licenses sold, and over 1,500 customers world wide Expanded to Asia PAC and Latin America through direct and channel Patents issued or pending in 32 countriesContinuing to innovate: fasp3™, fasp-MC™, mobile transport, cloud enablement
  5. 5. Aspera Ecosystem of Partners
  6. 6. Life SciencesLife Sciences
  8. 8. What Happened to my Bandwidth? WAN 1000 Mbps Seattle • 170ms RTT • 0.001% packet loss rate ParisWAN Throughput is 1000MbpsMax TCP Throughput ~29MbpsWhere’s my 970Mbps? At 29Mbps 50GB transfer will take 4 hrs 1TB transfer will take 3.3 days
  9. 9. BIG-DATA and WAN TRANSFER WITH TCPTCP WAS DESIGNED IN THE EARLY 80’S • When data was small & bandwidth was limited • Fantastic for reliable data delivery • Not fast enough for big-dataTCP IS THE ENGINE THAT DRIVES • FTP, HTTP & HTTPS • RSYNC, SCP & DICOM • CIFS & NFSTCP DOES NOT LIKE NETWORK LATENCY/ RTT • Geographic distance increases latency • Network congestion increases latencyTCP DOES NOT LIKE PACKET LOSS • Loss is caused by congestion • Different network capacity • Wireless and satellite communications
  10. 10. So if TCP doesn’t work, what’s the answer?The Aspera Solution
  11. 11. Same WAN Scenario with Aspera WAN 1000 Mbps • 170ms RTT Seattle • 0.001% packet loss rate ParisWAN is 1000MbpsMax TCP Throughput ~29MbpsMax Aspera Throughput ~995Mbps (gain of x34)ROI measured in $$ cost of not using 971Mbps At 995 Mbps • 50GB transfer will take ~4 hrs • 1TB transfer will take 3.3 days • 50GB transfer will take ~7 mins • 1TB transfer will take 2.4 hrs
  12. 12. FASP™ — HIGH-PERFORMANCE DATA TRANSPORTMAXIMUM LINE-RATE WAN TRANSFER SPEED • Transfer performance scales with bandwidth independent of transfer distance and resilient to packet loss • Optimal end-to-end throughput efficiencyCONGESTION AVOIDANCE AND POLICY CONTROL • Automatic, full utilization of available bandwidth • On-the-fly prioritization and bandwidth allocationUNCOMPROMISING SECURITY AND RELIABILITY • Secure, user/endpoint authentication • AES-128 cryptography in transit & at-restSCALABLE MANAGEMENT, MONITORING AND CONTROL • Real-time progress, performance and bandwidth utilization • Detailed transfer history, logging, and manifestENTERPRISE-CLASS FILE DELIVERY • Transfers up to thousands of times faster than FTP/HTTP(S) • Precise and predictable transfer times • Extreme scalability (concurrency and throughput)
  13. 13. FASP vs TCP PERFORMANCEfasp Bandwidth ROI FTP: Limited by Distance & Packet Loss, Not B/W 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 Aspera: Scales Linearly with Bandwidth 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. Distance & Packet Loss Independent
  14. 14. 6 Gbps Scalable WAN Throughput~6Gbps Big-Data Throughput x3000 improvement vs. TCP • Latency independent • 1TB data moved in 20 min • Loss independent • 2 days with TCP over LAN conditions Scale to ~10Gbps with IQ Accelerator
  15. 15. High Speed Mobile Data Transfer with fasp-AIR™fasp-AIR SDK – maximum data transfer speed and predictability formobile 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.
  16. 16. fasp-AIR Benchmarks on Verizon 4GIn some cases (highlighted in orange), speeds will varygreatly, depending on available bandwidth and the underlyingcondition of the wireless network.
  19. 19. SECOND MAJOR BOTTLENECKS: LOCAL HTTP I/O1st Bottleneck - WAN 2nd Bottleneck — Data Center
  20. 20. 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 filesUNDERSTAND 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
  22. 22. S3 & BIG-DATA: MEET ASPERA’s DIRECT-TO-S3 client cargo downloaderpoint-to-point mobile appsconnect plug-in
  23. 23. ASPERA DIRECT-TO-S3 — LINE RATE ACCESS TO THE CLOUDUNRIVALED 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 trafficSEAMLESS 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 userENTERPRISE-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 restINTEROPERATES 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)
  24. 24. Aspera fasp™ software environment
  25. 25. ASPERA DEVELOPER NETWORKA complete set of SDKs provides developers with guides, reference information, and sample code to assist them withintegrating 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 TRANSFER APIs ASPERA MOBILE APIs Aspera Web Services Android SDK A SOAP based web service API that allows initiation, Aspera Android SDK provides a Java API to transfer files using monitoring and controlling of fasp based file transfers. fasp-AIR™. iPhone SDK Aspera Web Aspera iPhone SDK provides an Objective C API to transfer files Javascript API exposed by Aspera Connect client. It allows using fasp-AIR. integration of fasp based file transfers into web applications. ASPERA APPLICATION APIs Connect 2.8 developer Preview 2 Introducing the new Connect 2.8 developer preview! faspex™ Web API Integrate the functionality of Aspera Connect 2.8, a fasp- The Aspera faspex Web API provides a set of services that enables based file transfer client, into your own web applications, users to create and receive digital deliveries via a Web interface, while while customizing it to your unique brand. taking advantage of fasp high-speed transfer technology. fasp Manager A class library that allows intiations, monitoring and OTHER INFORMATION controlling of fasp based file transfers. Supporting Tools and Libraries Aspera Multicast SDK Supporting tools and libraries let you perform other common tasks A Java class library that allows initiation and management surrounding file transfers. of IP multicast based data transmissions using Aspera General Reference fasp-MC™. Reference on error codes, log file locations, configuration files and more.
  26. 26. BIG-DATA: ACCESSED & DELIVERED BY ASPERA Media File transfer
  28. 28. High-Speed Transfers Between DICOM Devises: Example: Archive-to-Archive Transfers (fasp3 socket-based solution) DICOM DICOMPACS, Archive… PACS, Archive… Usual UsualDICOM DICOM (TCP) (TCP) Regular sockets Regular sockets selected by fasp selected by faspSocket fasp3 fasp3 Socket Sender Receiver
  29. 29. Aspera Fasp Sockets OverviewClient Application FASP-Pipe Proxy Application FASP-Pipe Proxy Server Data Source Client Java Java .NET Stream F F Stream FASP FASP A T C/C++ A .NET Socket TCP WebSocket Server S WAN S C TCP HTML 5 P FASP FASP P P C/C++ WS Data 3 Message Message 3 SSE Data Socket
  30. 30. Use Case : On-Demand Access to Medical ImagesImage 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
  31. 31. 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
  32. 32. Use Case : Health Information Exchange• Drop in Replacement of HTTP with fasp for XDS-I
  34. 34. Possible Integration• Peake Healthcare --Joint Venture Between Johns Hopkins and Harris Corporation• McKesson• Vital (MINT Use case)• Washington University School of Medicine
  36. 36. THANK YOU! Daniel Kumi Director, New Market Development daniel@asperasoft.comFOR MORE INFORMATION ON ANY ASPERA PRODUCT, PLEASE CONTACT: