# US 2010/0165841 A9 · QUALITY OF SERVICE FOR iSCSI

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

- Number: US 2010/0165841 A9
- Document ID: US20100165841A9
- Status: Published application
- Kind: A9
- Application number: 12/061,671
- Filed: 2008-04-03
- Published: 2010-07-01
- Earliest claimed: 2002-12-31
- Assignees: International Business Machines Corporation
- Inventors: Tsipora Barzilai; John Marberg
- Web page: https://patentgrep.com/patent/US20100165841A9

## CPC

- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 47/193: at the transport layer, e.g. TCP related
- H04L 47/22: Traffic shaping
- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 47/31: by tagging of packets, e.g. using discard eligibility [DE] bits
- H04L 67/61: taking into account QoS or priority requirements
- H04L 69/161: {Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields}
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/329: in the application layer [OSI layer 7]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system adapted to provide quality of service (QoS) for an iSCSI environment including one or more initiators and one or more targets. Each initiator includes an iSCSI initiator and a TCP layer. The iSCSI initiator includes a QoS shaper for shaping one or more iSCSI PDUs according to QoS policies. The TCP layer includes a QoS marker for marking the PDUs according to the QoS policies. The target includes a first and second QoS component. The first QoS component is in an iSCSI target and handles I/O resources. The first QoS component shapes read commands and write commands according to QoS policies. The second QoS component is in a TCP layer and handles network resources. iSCSI PDUs are shaped and marked according to QoS policies of iSCSI. The QoS policies used by the initiators and targets include policies for network resources and policies for I/O resources.

## Claims

### Claim at position 1

-2. (canceled)

### Claim 3

An initiator node adapted to provide quality of service (QoS) for an Internet Small Computer System Interface (iSCSI) environment, the initiator node comprising:
an iSCSI initiator comprising a QoS shaper, said QoS shaper for shaping one or more Protocol Data Units (PDUs) according to QoS policies and providing shaped PDUs; and
a Transmission Control Protocol (TCP) layer for receiving said shaped PDUs from said iSCSI initiator and comprising a QoS marker for marking said shaped PDUs according to said QoS policies, wherein said PDUs are command PDUs and wherein said shaper shapes said command PDUs before said command PDUs receive command sequence numbers.

### Claim 4 (depends on 1)

The initiator node of claim 1, wherein said PDUs are data PDUs and command PDUs, wherein said data PDUs and said command PDUs are shaped before being received in said TCP layer.

### Claim 5 (depends on 1)

The initiator node of claim 1 and further comprising:
a second shaper in the TCP layer for shaping network traffic of applications other than iSCSI.

### Claim 6

A target node adapted to provide quality of service (QoS) for an Internet Small Computer System Interface (iSCSI) environment, the target node comprising:
a first QoS component in an iSCSI target, said first QoS component for handling I/O resources and for shaping one or more read commands and one or more write commands according to QoS policies, thereby providing QoS for traffic from a non-compliant initiator; and
a second QoS component in a Transmission Control Protocol (TCP) layer for handling network resources, wherein iSCSI Protocol Data Units (PDUs) are shaped and marked according to QoS policies of iSCSI.

### Claim 7 (depends on 6)

The target node of claim 6, wherein said QoS policies include one or more of the following: policies for network resources and policies for I/O resources.

### Claim 8 (depends on 6)

The target node of claim 6, wherein said target node provides access to a plurality of logical units (LU), each said LU having multiple task-sets, each said task-set having an associated class of service, wherein two or more of said associated classes of service are the same.

### Claim 9 (depends on 8)

The target node of claim 8, wherein two or more of said associated classes of service are different one from the other.

### Claim 10

A system adapted to provide quality of service (QoS) for an Internet Small Computer System Interface (iSCSI) environment, the system comprising:
one or more initiator nodes, each said initiator node comprising;
an iSCSI initiator comprising an initiator QoS shaper, said initiator QoS shaper for shaping one or more Protocol Data Units (PDUs) using QoS policies and providing shaped PDUs; and
a Transmission Control Protocol (TCP) layer for receiving said shaped PDUs from said iSCSI initiator, and comprising a QoS marker for marking said shaped PDUs using to said QoS policies; and
one or more target nodes for receiving said PDUs from said initiator node over an IP network, each said target node comprising;
a first QoS component in an iSCSI target for handling I/O resources, said first QoS component for shaping one or more read commands and one or more write commands extracted from said PDUs using QoS policies; and
a second QoS component in a TCP layer for handling network resources, wherein iSCSI PDUs are shaped and marked using QoS polices for iSCSI.

### Claim 11 (depends on 10)

The system of claim 10, wherein said QoS policies include one or more of the following: policies for network resources and policies for I/O resources.

### Claim 12 (depends on 10)

The system of claim 10, wherein said QoS policies used by said initiator QoS shaper are different from said QoS policies used by said first and second QoS components in said target node.

### Claim 13 (depends on 10)

The system of claim 10, and further comprising:
a service level agreement (SLA) agent in communication with said initiator nodes and said target nodes, wherein said SLA agent provides said initiator nodes and said target nodes with said QoS policies.

### Claim 14 (depends on 10)

The system of claim 10, wherein said initiator nodes and said target nodes support a multiplicity of separate connections for a multiplicity of classes of service per an iSCSI session.

### Claim 15 (depends on 10)

The system of claim 10 and also comprising:
a plurality of filter specification attributes, wherein one or more of said filter specification attributes are adapted to reflect iSCSI traffic types.

### Claim 16 (depends on 15)

The system of claim 15, wherein said filter specification attributes include one or more of the following: TCP four-tuple, iSCSI session id, logical unit number (LUN), initiator user id and application identification attributes.

### Claim 17 (depends on 15)

The system of claim 15, wherein said filter specification attributes are adapted to provide QoS for network resources and I/O resources.

### Claim 18 (depends on 15)

The system of claim 15, wherein said filter specification attributes are used by one or more of said initiator nodes and by one or more of said target nodes, and wherein said filter specification attributes used by said initiator nodes are different from said filter specification attributes used by said target nodes.

### Claim 19 (depends on 10)

The system of claim 10 and also comprising:
a plurality of flow specification parameters, wherein one or more of said flow specification parameters are adapted for iSCSI traffic types.

### Claim 20 (depends on 19)

The system of claim 19, wherein said flow specification parameters include one or more of the following: I/O rate, byte rate and I/O flow excess.

### Claim 21 (depends on 19)

The system of claim 19, wherein said flow specification parameters are adapted to provide QoS for network resources and I/O resources.

### Claim 22 (depends on 19)

The system of claim 19, wherein said flow specification parameters are used by one or more of said initiator nodes and by one or more of said target nodes, and wherein said flow specification parameters used by said initiator nodes are different from said flow specification parameters used by said target node.

### Claim 23

A quality of service (QoS) system adapted for an Internet Small Computer System Interface (iSCSI) environment, said QoS system comprising:
a QoS shaper in an iSCSI initiator, for shaping one or more Protocol Data Units (PDUs) according to QoS policies and providing shaped PDUs;
a QoS marker in a Transmission Control Protocol (TCP) layer at an initiator node, for receiving said PDUs from said iSCSI initiator, and for marking said shaped PDUs according to said QoS policies; and
a first target QoS component in an iSCSI target node, for receiving one or more read commands and one or more write commands extracted from said PDUs, and for shaping said commands according to QoS policies.

### Claim 24 (depends on 23)

The QoS system of claim 23, wherein said first target QoS component handles I/O resources, and further comprising:
a second target QoS component in a TCP layer for handling network resources, wherein iSCSI PDUs are shaped and marked according to QoS policies for iSCSI.
of the coverage in the cross-product space.

### Claim at position 24

-35. (canceled)

### Claim 36

A system for providing quality of service (QoS) for an Internet Small Computer System Interface (iSCSI) environment, the system comprising:
means for shaping one or more Protocol Data Units (PDUs) in an iSCSI initiator according to QoS policies; and
means for marking in a Transmission Control Protocol (TCP) layer at an initiator node said shaped PDUs according to said QoS policies, wherein said PDUs are command PDUs, and wherein shaping of said command PDUs occurs before assigning command sequence numbers to said command PDUs.

### Claim 37 (depends on 36)

The system of claim 36, wherein said PDUs are data PDUs and command PDUs, and wherein shaping of said data PDUs and said command PDUs in said iSCSI initiator occurs before sending said data PDUs and said command PDUs to said TCP layer.

### Claim 38 (depends on 36)

The system of claim 36, and further comprising:
means for receiving over an IP network said PDUs at a target node; and
means for shaping in an iSCSI target one or more read commands and one or more write commands extracted from said PDUs according to QoS policies, thereby providing QoS for non-compliant traffic.

### Claim at position 28

-40. (canceled)

### Claim 41

A computer program embodied on computer readable medium software, the computer program comprising:
a first segment operative to shape one or more Protocol Data Units (PDUs) in an Internet Small Computer System Interface (iSCSI) initiator at an initiator node according to quality of service (QoS) policies; and
a second segment operative to mark in a Transmission Control Protocol (TCP) layer at an initiator node said shaped PDUs according to said QoS policies, and further comprising:
a third segment operative to receive over an IP network said PDUs at a target node; and
a fourth segment operative to shape in an iSCSI target one or more read commands and one or more write commands extracted from said PDUs according to QoS policies, thereby providing QoS for non-compliant traffic.
