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

Token Ring Switch

IP.com Disclosure Number: IPCOM000111498D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 4 page(s) / 125K

Publishing Venue

IBM

Related People

Hobgood, R: AUTHOR [+5]

Abstract

One of the requirements of the IBM AAS contract with the FAA is for the FAA Technical Center (FAATC) in Atlantic City to support the FAA In Route Centers, during the three major elements of the contract (ISSS, TAAS, ACCC). Also, in an effort to reduce costs, the FAATC hardware complement, for those devices which would be part of the Token Ring Networks (TRN), would need to be shared between the three major elements. Further, the software that was being developed at the FAATC would have to be 100 percent identical to the software that would run at the In Route Centers.

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

Token Ring Switch

      One of the requirements of the IBM AAS contract with the FAA is
for the FAA Technical Center (FAATC) in Atlantic City to support the
FAA In Route Centers, during the three major elements of the contract
(ISSS, TAAS, ACCC).  Also, in an effort to reduce costs, the FAATC
hardware complement, for those devices which would be part of the
Token Ring Networks (TRN), would need to be shared between the three
major elements.  Further, the software that was being developed at
the FAATC would have to be 100 percent identical to the software that
would run at the In Route Centers.

      The above mentioned requirements presented a problem for the
workstations (WS) that would be connected to the Token Ring Networks
(TRNs).  The problem was that the quantity of WS required to support
the TRNs was less than was needed for a full replication of the In
Route Centers.  The contractual plan was for the WS to be shared
between TRNs, and combined as required to form larger TRNs.  This
sharing was also bound by the requirement that the sharing had to be
accomplished in an artifact-free way.

      Token Ring Networking - The current available technology to
accomplish interconnecting TRNs are through bridges, gateways, etc.
This approach to communicating between TRNs introduces hardware and
software whose only function is to pass the data between the
individual networks.  This approach to networking introduces a
hierarchy of protocols to handle the network routing.  It also
introduces into the network unit addresses, for the bridges, etc.

      This type of solution was incompatible with the FAATC
requirement that the software used at the FAATC had to be identical
to the software used at any one of the In Route Centers.  The In
Route Centers have a sufficient number of WS to perform their tasks.
The FAATC has to be able to duplicate the tasks at any one of the In
Route Centers.  The FAATC was left with the problem that if they used
bridges, etc. to mimic an In Route Center, those bridges, etc. would
occupy an address space on the TRN.  From the requirements that the
software had to be identical, the current available technology
solution cannot be used.

      A method was required of switching TRNs in such a manner that
the switching methodology had to be totally transparent to the
operational software.  That is, the software at the FAATC had to
match the software that would run at the In Route Centers, and that
extra addresses on the TRN such as bridges, etc., for supporting the
FAATC was unacceptable.  Further, there is no product in the market
today that will allow TRNs to be switched together in a transparent
manner.

      Token Ring Switch - Disclosed is a design that allows multiple
independent Token Ring Networks (TRNs) to be switched together such
that the resultant network appears as a single Token Ring Network.

      The token ring switch is a transparent hardware device, and as
such do...