RESTful Tape Interface Hides SCSI Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for writing data to or reading from tape media require complex SCSI interface logic, making it difficult for applications to perform these operations without extensive coding and understanding of SCSI interfaces.

Innovation Solution

A system utilizing a RESTful interface that allows client applications to initiate requests to a REST daemon for writing to or reading from tape media, which then interacts with a data mover using SCSI interfaces, thereby hiding the complexity of SCSI logic and allowing simplified data management through RESTful calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a SCSI interface is used for direct tape access, then data can be written to and read from tape media, but the system complexity increases significantly due to required SCSI logic and protocols

Engineering Contradiction:
Improveease of data accessVSAvoidcomplexity of interface logic
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a RESTful API as an intermediary layer between the client application and the SCSI tape interface. This mediator translates simple REST requests into complex SCSI commands, shielding the user from SCSI complexity while enabling tape access. The RESTful interface acts as a buffer that handles the translation and protocol conversion automatically.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct functional layers: a simplified user-facing RESTful interface layer and a backend SCSI interface layer. This segmentation allows each layer to handle its specific complexity independently, with the REST layer presenting simplicity to users while the SCSI layer manages the complex protocol requirements behind the scenes.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If a RESTful interface is introduced to simplify tape access, then the ease of operation improves, but an additional interface layer is added to the system

Engineering Contradiction:
Improveease of data accessVSAvoidnumber of interface layers
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The RESTful interface is designed as a universal access point that can handle multiple tape operations (read, write, status queries) through standardized HTTP methods. This multi-functional interface consolidates various tape access needs into a single unified entry point, making the system easier to use despite the added layer.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The RESTful interface serves as a smart intermediary that actively manages the complexity translation between user applications and the SCSI subsystem. Rather than simply passing through requests, it interprets high-level REST commands and converts them into appropriate SCSI sequences, effectively managing the interface layer addition as a value-adding transformation layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11961541B2System and method for writing data to tape and reading data from tape using a restful interface
Publication Date: 2024.04.16 ALTER DOMUS (US) LLC AS AGENT FOR THE SECURED PARTIES
  • US11961541B2 patent drawing
  • US11961541B2 patent drawing

AI summary

A system (200) for at least one of writing data to tape media (204) and reading data from the tape media (204) includes a client application (202); and a RESTful interface (212) through which the client application (202) transmits a request to at least one of write data to the tape media (204) and read data from the tape media (204) to a REST daemon (214), the RESTful interface (212) being integrated with a SCSI interface (210). The REST daemon (214) subsequently passes the request on to a data mover (208), which opens a second RESTful interface (220) with the client application (202). The client application (202) then sends the request to the data mover (208) via the second RESTful interface (220). The data mover (208) then performs the request by moving the data between the client application (202) and the tape media (204), with the data never landing on primary storage during such movement.