or
Bookmark and Share
Two-pin distributed ethernet bus architecture
   
Document Number
US Patent 6061737
Issued Date
May 9, 2000
Link
Inventors
Fite; Elaine H. (Northborough, MA)
Salett; Ron (Framingham, MA)
Map
Abstract
An intermodule network bus architecture using only two bus wires to transmit data and module state information. A two-pin bus interface in each network module connected to the bus provides for a distributed arbitration procedure in the event that two or more modules are competing for bus access, and provides a coding scheme under which both data signals and collision announcements are transmitted from module to module through the two-wire bus. The architecture handles multiple distributed repeater modules, as well as other network components such as bridges and routers connected to the same bus. An important aspect of the invention is that multiple bus interfaces function as a distributed state machine, to handle the arbitration process and to provide a consistent framework for detecting and processing data signals and various types of collisions, including receive collisions detected on a single local module port, and transmit collisions involving activity on multiple local ports of one or more modules.
Drawing
Two-pin distributed ethernet bus architecture - US Patent 6061737 Drawing
Drawing from US Patent 6061737
Tags:
Description:
Amusing 0%
Clever 0%
Complex 0%
Efficient 0%
Historic 0%
Important 0%
Innovative 0%
Interesting 0%
Practical 0%
Simple 0%
Number of Claims:
1
Comments:
no comments yet
Owner
Cabletron System, Inc. (Rochester, NH)
Published
May 9, 2000
Application Number
09/227,800
Filed
January 8, 1999
US Classification
709/243   709/225 709/250
Int'l Classification
H04L   12/407   (20060101)   H04L   12/44   (20060101)   H04L   12/413   (20060101)   H04L   12/46   (20060101)  
Attorney/Law Firm
Parent Case
This is a continuation of Ser. No. 08/589,512, filed Jan. 22, 1996, now U.S. Pat. No. 5,963,719.
USPTO Field of Search
709/243   709/225   709/250  
Related Patents
7353484 - Methods and apparatus for variable latency support - Owned by Altera Corporation (San Jose, CA)

Methods and apparatus are provided for interconnecting primary components with secondary components on a programmable chip. Control, data, and address lines are automatically generated to connect primary components and secondary components with an interconnection module. The interconnection connection module manages interaction between primary components and secondary components and provides support for fixed latency and variable latency secondary components.

7260530 - Enhanced go-back feature system and method for use in a voice portal - Owned by BeVocal, Inc. (Mountain View, CA)

A system, method and computer program product are provided for transitioning among states during use of a voice browser. Initially, a script is received at a voice browser from a web server utilizing a network. Next, the script is executed utilizing the voice browser. A plurality of states is then automatically tracked during the execution of the script utilizing the voice browser. Upon receiving a request from a user during the execution of the script to transition to a previous state, the voice browser automatically transitions to the previous state of the script.

7539154 - Method and apparatus to detect and break loop configuration - Owned by Cisco Technology, Inc. (San Jose, CA)

In a system having a plurality of nodes such as Ethernet repeaters, coupled by communication links such as cables, systems and protocols are provided for detecting and/or breaking loops. In one aspect, in response to an added link, a repeater sends a "detect loop" message containing its address to at least one neighbor. Each repeater which receives the "detect loop" message, in turn, sends it to its own neighbor, with the lesser of the received address and its own address. A repeater which receives a "detect loop" message containing its own address declares itself a master loop breaker and can isolate one of its ports to break the loop. In one aspect, a previously intentionally-isolated port can be re-activated, e.g., in response to the loss of a communication link which could potentially isolate one or more nodes.

Claims
Description
About| FAQs| Terms & Disclaimer| Link to Us| Contact Us