The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Mar. 08, 2005
Filed:
Mar. 03, 2000
Robert F. Kalman, Cupertino, CA (US);
Jason C. Fan, Mountain View, CA (US);
Charles F. Barry, Campbell, CA (US);
Prasad P. Jogalekar, Sunnyvale, CA (US);
Vinay K. Bannai, Mountain View, CA (US);
Robert F. Kalman, Cupertino, CA (US);
Jason C. Fan, Mountain View, CA (US);
Charles F. Barry, Campbell, CA (US);
Prasad P. Jogalekar, Sunnyvale, CA (US);
Vinay K. Bannai, Mountain View, CA (US);
Luminous Networks, Inc., Cupertino, CA (US);
Abstract
The disclosed network includes two rings, wherein a first ring transmits data in a clockwise direction, and the other ring transmits data in a counterclockwise direction. The traffic is removed from the ring by the destination node. During normal operations (i.e., all spans operational), data between nodes flows on the ring that would provide the minimum number of hops to the destination node. Thus, both rings are fully utilized during normal operations. The nodes periodically test the bit error rate of the links (or the error rate is constantly calculated) to detect a fault in one of the links. The detection of such a fault sends a broadcast signal to all nodes to reconfigure a routing table within the node so as to identify the optimum routing of source traffic to the destination node after the fault. Since the available links will now see more data traffic due to the failed link, traffic designated as 'unprotected' traffic is given lower priority and may be dropped or delayed in favor of the 'protected' traffic. Specific techniques are described for identifying a failed link, communicating the failed link to the other nodes, differentiating between protected and unprotected classes of traffic, and updating the routing tables.