Browse Prior Art Database

Bus Manager Selection Procedure

IP.com Disclosure Number: IPCOM000112269D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 62K

Publishing Venue

IBM

Related People

Frazier, GR: AUTHOR

Abstract

A common problem in networks or computer system buses in which nodes are interconnected is the selection of a control node. The control node is referred to here as a "monarch" node. The following scheme is a fault-tolerant protocol for selecting the monarch.

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

Bus Manager Selection Procedure

      A common problem in networks or computer system buses in which
nodes are interconnected is the selection of a control node.  The
control node is referred to here as a "monarch" node.  The following
scheme is a fault-tolerant protocol for selecting the monarch.

      This scheme is applicable to any interconnection network in
which each node can determine the identification numbers of all other
nodes.  One example of such a network is the developing industry
standard P1394 Serial Bus [*].  This scheme is described in terms of
that bus, but it can easily be applied to other buses.

Following is the procedure:

1.  During P1394 self-configuration (described in [*]), "self-ID"
    configuration packets flow throughout the network.  These packets
    are used to assign all nodes with identification (ID) values, and
    each node is required to record the ID values of all other nodes.
    The packets also specify if the node is capable of being a bus
    monarch.  In addition to recording the ID values of other nodes,
    this scheme requires that each monarch-capable node determine the
    ID of the monarch-capable node with the next higher ID than
    itself.  Refer to this node as as a MONARCH PARENT.

2.  After self configuration in step 1), if a node recognizes that no
    node with a higher node ID than its own is Monarch-capable, then
    that node has no MONARCH PARENT.  In this case, the node assumes...