Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Communication Protocols Between Master Controller And Optical Interface

IP.com Disclosure Number: IPCOM000120158D
Original Publication Date: 1991-Mar-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 47K

Publishing Venue

IBM

Related People

Peterson, MJ: AUTHOR [+2]

Abstract

Disclosed is a method of communication between a 220 Mbit/sec optical interface and various logic parts in a fiber optic switch.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 71% of the total text.

Communication Protocols Between Master Controller And Optical Interface

      Disclosed is a method of communication between a 220 Mbit/sec
optical interface and various logic parts in a fiber optic switch.

      The interface between master controller and transmit and
receive logic in the switch is a three-bit bus which is encoded by
transmit and receive logic.  This is used to receive and transmit
frames from/to fiber optic interface. The master controller requests
a specific operation based on the overall state of the switch once
the receive logic reports a valid Start Of Frame Connect delimiter.
The following is a description for this interface:

      NOMTX-
      This signal tells the receive logic to prevent sending any data
to the matrix bus.  However, any delimiter received from the link
will be reported and status bits will be active to record errors.

      FILL-
      This signal signifies to the receive logic that a frame can be
received from the link and it should be captured in the connect
buffer.

      RELFRM-
      Once the appropriate handshake between Port Adapter chip and
Matrix chips are reported to the master controller, the RELFRM signal
tells the receive logic to release the frame to the Matrix chips.

      FIFO-
      This signal tells the receive logic that the captured data
should be read while continuing to write the remaining data stream
coming from the link.  This is possible since the buffer us...