Great River Technology, Inc. - High Performance Custom Digital Video Solutions


	Putting it all together: Fibre Channel Frame Format and Ordered Sets The Fibre Channel transport layer is comprised of frames as defined below. The basic unit of transport for video and header data will be FC frame. Each FC frame has the structure shown below (and as described in the referenced FC-PH specification) IDLE Words IDLE ordered sets, such as K28.5, D21.4, D21.5, D21.5, are transmitted between FC frames, it is typical that a minimum of six IDLE ordered sets between each Fibre Channel frame is needed. When transmitting, the number of IDLE ordered sets between FC frames can be varied to adjust the video frame time (to adjust the horizontal blanking). It is possible for the system designers to control horizontal and vertical blanking using IDLEs, however this is not typically done in FC-AV. Start of Frame FC-AV is independent of Class of Service. Currently class 1 and class 3 implementations exist. Data Payloads The first frame of an FC-AV container data sequence contains the container header and Object 0 ancillary data as its data payload. Subsequent frames of the FC-AV container sequence contain the Object 2 video pixel data. Cyclic Redundancy Check (CRC) After a video frame has been transmitted, a 4 byte CRC for error checking ins included that uses the following 32-bit polynomial: X32 + X26 + X23 + X22 + X16 + X12 + X11 + X10 + X8 + X7 + X5 + X4 + X2 + X + 1 End of Frame All frames except the last frame of an FC-AV container data transfer sequence use the End of Frame Normal EOFn ordered set (beginning RD Negative - K28.5, D21.4, D21.6, D21.6 or beginning RD Positive - K28.5, D21.5, D21.6, D21.6). The last frame of an FC-AV container data transfer sequence uses the End of Frame Terminate EOFt ordered set (beginning RD Negative - K28.5, D21.4, D21.3, D21.3 or beginning RD Positive - K28.5, D21.5, D21.3, D21.3). Fibre Channel Containers FC-AV employs a container system of transport as described in Clause 5 of the standard. A container is simply the set of Fibre Channel frames used to transport a single video frame. For uncompressed progressive scanned video, only two container objects are required Object 0 which contains header information, and Object 2 which carries the video payload. Object 1, by definition, is restricted to Audio and is not used in SPDV. In some video profiles, container Object 0 is a single Fibre Channel frame. This frame is the first frame of the sequence and uses the SOFi. All subsequent frames (Object 2) carry video payload. The Object 0 Fibre Channel frame is comprised of 32 long words (128 bytes) as follows: The FC frame header is that same as that defined in section 5. FC-AV Container Header The standard definition of the Container Header is shown below. FC-AV Object 0 Ancillary Data Also included in the Object 0 FC frame are 16 bytes of Ancillary Data (as shown in tables below) The ancillary data contains required information, like the number of rows and columns in a video frame, whether it is a field or a frame, color information, and sub pixel information. User defined data can also be entered into the 3rd and 4th words. FC-AV Object 2 Video Data In all video profiles, container Object 2 is a set of Fibre Channel frames. These frames use the SOFn and carry up to 2112 bytes video of video payload. The exact number of bytes per FC frame, and the total number of FC frames, depends on the video profiles, and example of a 480x480, monochrome image is shown in the table below.

Putting it all together: Fibre Channel Frame Format and Ordered Sets

The Fibre Channel transport layer is comprised of frames as defined below.

The basic unit of transport for video and header data will be FC frame. Each FC frame has the structure shown below (and as described in the referenced FC-PH specification)

IDLE Words

IDLE ordered sets, such as K28.5, D21.4, D21.5, D21.5, are transmitted between FC frames, it is typical that a minimum of six IDLE ordered sets between each Fibre Channel frame is needed.

When transmitting, the number of IDLE ordered sets between FC frames can be varied to adjust the video frame time (to adjust the horizontal blanking).

It is possible for the system designers to control horizontal and vertical blanking using IDLEs, however this is not typically done in FC-AV.

Start of Frame

FC-AV is independent of Class of Service. Currently class 1 and class 3 implementations exist.

Data Payloads

The first frame of an FC-AV container data sequence contains the container header and Object 0 ancillary data as its data payload.

Subsequent frames of the FC-AV container sequence contain the Object 2 video pixel data.

Cyclic Redundancy Check (CRC)

After a video frame has been transmitted, a 4 byte CRC for error checking ins included that uses the following 32-bit polynomial:

X32 + X26 + X23 + X22 + X16 + X12 + X11 + X10 + X8 + X7 + X5 + X4 + X2 + X + 1

End of Frame

All frames except the last frame of an FC-AV container data transfer sequence use the End of Frame Normal EOFn ordered set (beginning RD Negative - K28.5, D21.4, D21.6, D21.6 or beginning RD Positive - K28.5, D21.5, D21.6, D21.6).

The last frame of an FC-AV container data transfer sequence uses the End of Frame Terminate EOFt ordered set (beginning RD Negative - K28.5, D21.4, D21.3, D21.3 or beginning RD Positive - K28.5, D21.5, D21.3, D21.3).

Fibre Channel Containers

FC-AV employs a container system of transport as described in Clause 5 of the standard.

A container is simply the set of Fibre Channel frames used to transport a single video frame. For uncompressed progressive scanned video, only two container objects are required Object 0 which contains header information, and Object 2 which carries the video payload. Object 1, by definition, is restricted to Audio and is not used in SPDV. In some video profiles, container Object 0 is a single Fibre Channel frame. This frame is the first frame of the sequence and uses the SOFi. All subsequent frames (Object 2) carry video payload.

The Object 0 Fibre Channel frame is comprised of 32 long words (128 bytes) as follows:

The FC frame header is that same as that defined in section 5.

FC-AV Container Header

The standard definition of the Container Header is shown below.

FC-AV Object 0 Ancillary Data

Also included in the Object 0 FC frame are 16 bytes of Ancillary Data (as shown in tables below) The ancillary data contains required information, like the number of rows and columns in a video frame, whether it is a field or a frame, color information, and sub pixel information. User defined data can also be entered into the 3rd and 4th words.

FC-AV Object 2 Video Data

In all video profiles, container Object 2 is a set of Fibre Channel frames. These frames use the SOFn and carry up to 2112 bytes video of video payload. The exact number of bytes per FC frame, and the total number of FC frames, depends on the video profiles, and example of a 480x480, monochrome image is shown in the table below.