# US 2004/0064623 A1 · Interface for bus independent core

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0064623 A1
- Document ID: US20040064623A1
- Status: Published application
- Kind: A1
- Application number: 10/261,311
- Filed: 2002-09-30
- Published: 2004-04-01
- Earliest claimed: 2002-09-30
- Assignees: LSI Logic Corporation
- Inventors: Richard L. Solomon
- Web page: https://patentgrep.com/patent/US20040064623A1

## CPC

- G06F 13/4031: {with arbitration}
- G06F 2213/0024: Peripheral component interconnect [PCI]
- G06F 2213/0036: Small computer system interface [SCSI]
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention is directed to an interface. In an aspect of the present invention, an interface system suitable for coupling a bus interface controller with a back-end device includes a bus interface controller and a back-end device in which the back-end device is coupled to the bus interface controller via an interface. The interface includes a command queuing interface suitable for enqueueing a transaction, a command completion interface suitable for reporting transaction completion and a data transfer interface suitable for transferring data. The data transfer interface includes an inbound data transfer interface suitable for transferring data and an outbound data transfer interface suitable for transferring data. The inbound data transfer interface and the outbound data transfer interface are suitable for processing commands simultaneously.

## Claims

### Claim 1

An interface system suitable for coupling a bus interface controller with a back-end device, comprising:
a bus interface controller; and
a back-end device coupled to the bus interface controller via an interface, the interface including
a command queuing interface suitable for enqueueing a transaction;
a command completion interface suitable for reporting transaction completion; and
a data transfer interface including an inbound data transfer interface suitable for transferring data and an outbound data transfer interface suitable for transferring data, wherein the inbound data transfer interface and the outbound data transfer interface are suitable for processing commands simultaneously.

### Claim 2 (depends on 1)

The interface system as described in claim 1, wherein command and control information are suitable for being exchanged on at least one of the command queuing interface and command completion interface while data is exchanged on the data transfer interface.

### Claim 3 (depends on 1)

The interface system as described in claim 1, wherein data for a transaction is suitable for being moved without respect to a current transaction being requested on a control bus.

### Claim 4 (depends on 1)

The interface system as described in claim 1, wherein the backend master device enqueues a transaction on the command queuing interface, at least one transfer of data is accomplished corresponding to the transaction queued on the command queuing interface, and completion status of the transaction is reported on the command completion interface.

### Claim 5 (depends on 1)

The interface system as described in claim 1, wherein a plurality of transactions are queued, the transaction are completed without regard to an order the transactions are queued.

### Claim 6 (depends on 1)

The interface system as described in claim 1, wherein the bus interface controller conforms to at least one of a USB standard, SCSI standard, fiber standard and the back-end device conforms to at least one of a PCI standard and PCI-X standard.

### Claim 7 (depends on 1)

The interface system as described in claim 1, wherein a plurality of data transfers on the data transfer interface are executed, the plurality of data transfers corresponding to a transaction queued on the command queuing interface.

### Claim 8

A method of transferring data, comprising:
enqueueing a first transaction on a command queuing interface;
transferring data corresponding to the first transaction on a data transfer interface while simultaneously transferring data corresponding to a second transaction on the data transfer interface; and
receiving notification of completion of the first transfer of data corresponding to the transaction, the notification reported on a command completion interface.

### Claim 9 (depends on 8)

The method as described in claim 8, wherein a plurality of transactions are queued, the transaction are completed without regard to an order the transactions are queued.

### Claim 10 (depends on 8)

The method as described in claim 8, wherein command and control information are suitable for being exchanged on at least one of the command queuing interface and command completion interface while data is exchanged on the data transfer interface.

### Claim 11 (depends on 8)

The method as described in claim 8, wherein data for a transaction is suitable for being moved without respect to a current transaction being requested on a control bus.

### Claim 12 (depends on 8)

The method as described in claim 8, wherein a backend master device enqueues a transaction on the command queuing interface, at least one transfer of data is accomplished corresponding to the transaction queued on the command queuing interface, and completion status of the transaction is reported on the command completion interface.

### Claim 13

An interface system suitable for coupling a first bus interface controller with a second bus interface controller, comprising:
a first bus interface controller suitable for coupling to a backend device; and
a second bus interface controller suitable for coupling to an internal bus of an information handling system, wherein the second bus interface controller is coupled to the first bus interface controller via an interface including
a command queuing interface suitable for enqueueing a transaction;
a command completion interface suitable for reporting transaction completion; and
a data transfer interface including a separate inbound data transfer interface suitable for transferring data and a separate outbound data transfer interface suitable for transferring data.

### Claim 14 (depends on 13)

The interface system as described in claim 13, wherein the inbound data transfer interface and the outbound data transfer interface are suitable for processing commands simultaneously.

### Claim 15 (depends on 13)

The interface system as described in claim 13, wherein command and control information are suitable for being exchanged on at least one of the command queuing interface and command completion interface while data is exchanged on the data transfer interface.

### Claim 16 (depends on 13)

The interface system as described in claim 13, wherein data for a transaction is suitable for being moved without respect to a current transaction being requested on a control bus.

### Claim 17 (depends on 13)

The interface system as described in claim 13, wherein a backend master device enqueues a transaction on the command queuing interface, at least one transfer of data is accomplished corresponding to the transaction queued on the command queuing interface, and completion status of the transaction is reported on the command completion interface.

### Claim 18 (depends on 13)

The interface system as described in claim 13, wherein a plurality of transactions are queued, the transaction are completed without regard to an order the transactions are queued.

### Claim 19 (depends on 13)

The interface system as described in claim 13, wherein the first bus interface controller conforms to at least one of a USB standard, SCSI standard, fiber standard and the second bus interface conforms to at least one of a PCI standard and PCI-X standard.

### Claim 20 (depends on 13)

The interface system as described in claim 13, wherein a plurality of data transfers on the data transfer interface are executed, the plurality of data transfers corresponding to a transaction queued on the command queuing interface.
